On Fri, Jun 1, 2012 at 8:41 AM, Chad <innocentkiller(a)gmail.com> wrote: If it isn't easy, let's make it easy. I'm a new developer and not having a repository to develop in has been absolutely paralyzing. (I requested one on May 23, for what it's worth). Gerrit is not just an SCM: there is a rapidly growing ecosystem of services that integrate with it -- and if your code isn't there, you're persona non grata. I've whipped up two iterations of a data collection backend for my team and got it set up on a labs instance, but that was a week ago, and since then things are at a standstill. It's been hard to get anyone to look at it, because everyone's workflow and attentional habits are interwoven with Gerrit now. This particular side-project is a useful illustration of another important point: Git's usefulness isn't limited to managing mature projects like Mediawiki -- it has a crucial role to play in the earliest stages of development, too. I have no idea if what I wrote is usable and scalable, and it would've been good to get some feedback early. In the past, I have found it useful and productive to whip up quick prototypes and put them up on GitHub for feedback, instead of trading in inchoate ideas, or sitting on them until the ideas feel mature (which *never* happens for me until I sit down and start writing code). The ideas that stick get developed into full-fledged products. Using Git in this way has been such a tremendous boon for me as a developer, and not having that has been really frustrating. I don't think expanding git-creation rights to a few more individuals goes far enough, because the point at which you need a repository is antecedent to the point in time at which you feel comfortable describing your work to someone. For cool projects to happen, people need to feel empowered to start repos for projects that seem speculative and maybe even a little silly, and that won't happen when you make it necessary to ask for permission. At this point I expect someone to come along and point out that you don't need Gerrit to start a Git repository -- "git init" will suffice. And that's true, as long as you don't need to collaborate with anyone, or develop on more than one machine (say rsync & I'll bop you on the head!), or have stable urls to share with people.

On Mon, Jun 4, 2012 at 11:00 PM, Jeremy Baron <jeremy(a)tuxmachine.com> wrote: Isn't the same basically true of Wiki articles? I understand the desire to keep things tidy, okay. But what would be the big deal about having ten or even a hundred thousand abandoned repositories, so long as they are hidden, and do not clutter the UI? The repositories that would be candidates for deletion are the ones that got no further than an initial stab, and those measure in kilobytes.

Hi Diederik, Ori, On Mon, Jun 4, 2012 at 11:25 PM, Diederik van Liere <dvanliere(a)gmail.com>wrote;wrote: access 'some day'. We've lost at least a couple of weeks worth of productivity in Ori's case (for E3) since he's been unable to firstly get gerrit access and then wait for someone from the release engineering team to be available to create repos for him. Well - that points to another problem - that of not providing adequate training on Git/Gerrit even to foundation engineers. I understand that every migration takes time but without having a published plan to support and train application developers - this process of learning bit by bit will take forever. And just think of the tough learning curve our volunteer contributors may be having to go through. Agreed. One of the major objectives stated for migrating to Git was to increase developer contributions and make is easier every one to contribute. Right now we seem to be stuck in the world of recreating our old world of svn into Git. We can do better. Alolita

On Tue, Jun 5, 2012 at 5:40 AM, K. Peachey <p858snake(a)gmail.com> wrote: Just as a quick note--I created the E3 repo yesterday. -Chad

On 2012-06-06 00:19, Diederik van Liere wrote: As something of an outsider/newcomer, I hear two very different stories. The first is the story of all the good reasons why Linus Torvalds created git, how it is fully decentralized and asynchronous, and how bad it was to work with SVN. The other story is gerrit, and how everything must now go through this bottleneck of new centralization. There's a conflict here, that needs to be sorted out. Does Linus Torvalds really use gerrit? -- Lars Aronsson (lars(a)aronsson.se) Aronsson Datateknik - http://aronsson.se

On Wed, Jun 6, 2012 at 4:09 AM, Lars Aronsson <lars(a)aronsson.se> wrote: Well, the Wikipedia page says that Gerrit is developed by one of the co-authors of git, so that must say something, right? - Ryan

On Tue, Jun 5, 2012 at 2:40 AM, K. Peachey <p858snake(a)gmail.com> wrote: We already had.

On Tue, Jun 5, 2012 at 8:44 AM, Jeremy Baron <jeremy(a)tuxmachine.com> wrote: I would suggest that we cross that bridge when we get there. AFAIK,Ori and the E3 team would only need a handful of repos in the coming months and the same applies to the Analytics team.

On Mon, Jun 4, 2012 at 11:44 PM, Jeremy Baron &lt;jeremy(a)tuxmachine.com&gt; wrote: Some numbers here: < http://gerrit-documentation.googlecode.com/svn/Documentation/2.4/dev-design…

On Tue, Jun 5, 2012 at 6:33 AM, Diederik van Liere &lt;dvanliere(a)gmail.com&gt; wrote: I've whipped up a quick tutorial for people who want to create new repositories[0]. If people can read and make sure they understand this page (with its various caveats), then yes, we can start handing this out. -Chad [0] https://www.mediawiki.org/wiki/Git/Creating_new_repositories

Dear Chad, This is really helpful! Thanks so much for putting this together! Diederik

On 01/06/12 17:41, Chad wrote: Are current permission groups viewable anywhere?

On Tue, Jun 5, 2012 at 7:55 PM, Bergi &lt;a.d.bergi(a)web.de&gt; wrote: More generally, there's the group listing in gerrit that's viewable to all logged in users[0]. Every group should be publicly viewable and show the users in it (other than LDAP groups, but this is a known bug and very few of our groups are LDAP based) -Chad [0] https://gerrit.wikimedia.org/r/#/admin/groups/