PMC proposals/Move apertium to github - Revision history

Ilnar.salimzyan: /* See also */

2015-02-23T03:39:12Z

2015-02-23T03:38:50Z

2014-12-05T08:11:03Z

Comments

2014-11-17T09:45:54Z

cat

2014-11-17T09:39:29Z

Comments

2014-11-17T09:28:08Z

Comments

2013-09-24T10:52:56Z

Voting

2013-09-09T18:47:33Z

Comments

2013-09-09T18:47:12Z

Comments

2013-09-09T18:01:12Z

I'm guessing commetn rather than caveat

@@ Line 51: / Line 51: @@
 * [[Using git]]
 * [[Using GIT with Apertium SVN]]
-* [[PMC_proposals/Allow some code under github.com/apertium]]
+* [[PMC proposals/Allow some code under github.com/apertium]]
 [[Category:Project Management Committee]]

@@ Line 51: / Line 51: @@
 * [[Using git]]
 * [[Using GIT with Apertium SVN]]
+* [[PMC_proposals/Allow some code under github.com/apertium]]
 [[Category:Project Management Committee]]

@@ Line 36: / Line 36: @@
 * Another (more git-like?) way of doing this is to simply say "if a language pair/sub-project wants to move off svn, let the committers to that module decide". E.g. apertium-en-hi is already on github. --[[User:Unhammer|unhammer]] 18:47, 9 September 2013 (UTC)
 : To explain a bit more: The "migration strategy" would be that we are open to letting people use git if they want to for their projects. So if $newcontributor wants to make apertium-fie-bar and host it on github, that's fine; they get to use their favourite VC, while people who feel that learning a new VC is a waste of time get to stay with SVN. And they don't have to learn a new VC just because the cool kids say it's what everybody's doing these days (which is a bad reason and very unmotivating). That is, they don't have to learn git until they find an interest in fie-bar and have an ''incentive'' to learn git, in which case motivation is there. (If you're into apertium to do actual work, then cool tricks like being able to do 'git merge --abort --dammit' is not the right motivation.)
+:: as [[User:Sushain]] mentions, it might be nice to have just the "tools" things in git (html-tools, apy, scrapers), since these are typically worked on by people who prefer git, and you don't need to check them out in order to work on language pairs. --[[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 09:11, 5 December 2014 (CET)
 ==Voting==

@@ Line 46: / Line 46: @@
 ===Abstain===
+==See also==
+* [[Using git]]
+* [[Using GIT with Apertium SVN]]
 [[Category:Project Management Committee]]
+[[Category:Git]]

@@ Line 35: / Line 35: @@
 * Another (more git-like?) way of doing this is to simply say "if a language pair/sub-project wants to move off svn, let the committers to that module decide". E.g. apertium-en-hi is already on github. --[[User:Unhammer|unhammer]] 18:47, 9 September 2013 (UTC)
+: To explain a bit more: The "migration strategy" would be that we are open to letting people use git if they want to for their projects. So if $newcontributor wants to make apertium-fie-bar and host it on github, that's fine; they get to use their favourite VC, while people who feel that learning a new VC is a waste of time get to stay with SVN. And they don't have to learn a new VC just because the cool kids say it's what everybody's doing these days (which is a bad reason and very unmotivating). That is, they don't have to learn git until they find an interest in fie-bar and have an ''incentive'' to learn git, in which case motivation is there. (If you're into apertium to do actual work, then cool tricks like being able to do 'git merge --abort --dammit' is not the right motivation.)
 ==Voting==

@@ Line 30: / Line 30: @@
 ==Comments==
 * "Note that apertium can retain its current method of allowing people to commit directly". Yuck. Github makes pulling easy enough that this should never, ever be considered. Also, the biggest benefit of Github is "drive by contributions" -- there's no need to be registered with a project to contribute, and forking is simplified to the point that you can just click 'edit' on a file and it does it transparently (and edit in the browser, without needing to download anything). I think that's a better selling point to most people than things like bisect :) -- [[User:Jimregan|Jimregan]] 15:28, 9 September 2013 (UTC)
+*: +1 – if we use git just like svn, we might as well use svn [[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 10:28, 17 November 2014 (CET)
 * The apertium github organisation is at https://github.com/apertium?tab=members