2014-11-04, 03:44
(2014-11-03, 21:59)zag Wrote: I doubt many people use SVN any more, its very old. All XBMC devs and most add-on authors use Github these days.
It allows for far more collaboration and social interaction.
Well, plenty still do. Not wanting to get into a discussion of git vs svn (again), but being old doesn't mean svn is not useful - it is still in development and has had considerable improvements regarding merge performance etc. I do use git for most of my current work however. When I came on board it made sense to continue on google code, and work through existing requests on the tracker.
More importantly though is, the project has already existed in two places - which creates a bad workflow for issues etc. It was forked before, and now the current site has plenty of issues on the tracker, as well as info on the wiki. Pushing it to github doesn't make it magically better - it still needs development - what would be good would be if someone wants to spend the time to rework the source rss code to use an alternative (and there are a couple - json as has been hinted at - or scraping - the json solution looks good). It would be advantageous not to lose the current dev site at least until it was officially closed and all issues were migrated. The github pull feature for kodi addons wasn't an issue as I never wanted it in the main repos (I explained this in detail some 50 pages ago ;-) ). I do manage a couple of other addons on github too btw (that are in Kodi)
As many others do too - I often use git locally and use git svn with svn repositories.
I'm now tired of playing cat and mouse with the bbc. I am still happy to merge back patches, and hand over the reigns if someone else wants to take over, but I think it is important to avoid fragmenting the project further (and at least not lose track of previous feature requests etc). Basically - forking to github does not help, unless you have real plans - and if you do - are you willing to take over and manage the project?
