Hi everyone,
I was wondering what people thought of marking /trunk/extensions in SVN as read only. Pretty much every active extension (as far as I can tell) has been moved out already. It doesn't preclude us from migrating any of these extensions to Git at a later date, and nothing is being deleted.
Thoughts?
-Chad
+1. Go for (g)it!
Sent from my HTC one X.
On 24/10/12 21:21, Chad wrote:
Hi everyone,
I was wondering what people thought of marking /trunk/extensions in SVN as read only. Pretty much every active extension (as far as I can tell) has been moved out already. It doesn't preclude us from migrating any of these extensions to Git at a later date, and nothing is being deleted.
Thoughts?
-Chad
I don't see the need for making it r/o. And if there's an issue with one of them, it could be fixed immediatly, instead of waiting for an import.
On Wed, Oct 24, 2012 at 6:52 PM, Platonides Platonides@gmail.com wrote:
On 24/10/12 21:21, Chad wrote:
Hi everyone,
I was wondering what people thought of marking /trunk/extensions in SVN as read only. Pretty much every active extension (as far as I can tell) has been moved out already. It doesn't preclude us from migrating any of these extensions to Git at a later date, and nothing is being deleted.
Thoughts?
-Chad
I don't see the need for making it r/o. And if there's an issue with one of them, it could be fixed immediatly, instead of waiting for an import.
Keeps new extensions from being committed to SVN. If something is still being maintained, it should be moved to Git.
-Chad
On Thu, Oct 25, 2012 at 2:28 PM, Chad innocentkiller@gmail.com wrote:
On Wed, Oct 24, 2012 at 6:52 PM, Platonides Platonides@gmail.com wrote:
On 24/10/12 21:21, Chad wrote:
I was wondering what people thought of marking /trunk/extensions in SVN as read only.
Thoughts?
I don't see the need for making it r/o. And if there's an issue with one of them, it could be fixed immediatly, instead of waiting for an import.
Keeps new extensions from being committed to SVN. If something is still being maintained, it should be moved to Git.
+1
On 25/10/12 14:28, Chad wrote:
Keeps new extensions from being committed to SVN. If something is still being maintained, it should be moved to Git.
-Chad
Where new extensions committed in svn since git migration? People with a svn account should know git is prefered now, and new people isn't getting one for creating extensions, so that doesn't seem to me like a problem to be solved.
On 10/25/2012 09:56 AM, Platonides wrote:
People with a svn account should know git is prefered now
Finding out the old SVN repo is now read-only is a good way for that target group to learn about the now official gerrit.mediwiki.org , isn't it.
We have enough confusion for contributors with Gerrit vs GitHub. Removing SVN from the mix helps a bit, or at least doesn't help getting things worse.
My 2c.
-- Quim
On 25/10/12 19:20, Quim Gil wrote:
On 10/25/2012 09:56 AM, Platonides wrote:
People with a svn account should know git is prefered now
Finding out the old SVN repo is now read-only is a good way for that target group to learn about the now official gerrit.mediwiki.org , isn't it.
My point is that people with write access (the only ones who can find out the hard way) already know.
See https://www.mediawiki.org/w/index.php?path=%2Ftrunk%2Fextensions&title=S...
Applying a bugfix patch (from bugzilla) to SelectCategory on September 5th (r115705). Daniel Kinzler knows perfectly about git. Was it worth migrating the extension to git? Probably not. Is it good to have one bug less, even on an almost unmaintained extension? Yes.
There were also commits to a few extensions in August.
We have enough confusion for contributors with Gerrit vs GitHub.
Don't use GitHub. It would be possible to do, but that creates confusion so it's better to pretend it doesn't exist. It should be possible to contribute to mediawiki-related projects without using GitHub at all.
Removing SVN from the mix helps a bit, or at least doesn't help getting things worse.
Is it really hard?
If an extension is in gerrit but not in svn: It has clearly to be improved in gerrit. If an extension is in svn but not in gerrit: It could be improved in svn, but for any serious work on it, you should request it migrated to gerrit. If an extension is in svn and in gerrit: it has een migrated to gerrit, so contribute to it there. In fact, you will find it is already read-only in svn.
Maybe the most interesting commit to svn in the last months is r115676, a one-file new extension. «Git makes it hard to work with locally modified files, so turned it into an extension. Putting on svn because i just want somewhere to stuff it, and i think there is some rigamarole with getting a new extension in git. Its a pretty useless extension, so I'm ok with it being on svn» If the gerrit process leads people away (svn, GitHub...) then that is a problem.
For what is worth, thanks to Federico we have now nice stats showing the activity in the SVN repository:
https://www.ohloh.net/p/mediawiki-extensions-wmf-hosted-svn https://www.ohloh.net/p/mediawiki-extensions-wmf-hosted-svn/contributors?sor...
The contribution trend is clearly pointing to zero. You can read this in two ways:
- Nobody is contributing now, we can change to read-only. - Nobody is contributing anyway, we can leave it as it is.
:)
-- Quim
wikitech-l@lists.wikimedia.org