Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Repo and Gerrit Discussion
Home
+ new post
About this group
Join this group
Message from discussion Gerrit newbie question: non-administrators creating projects?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Shawn Pearce  
View profile  
 More options Apr 27 2012, 12:55 pm
From: Shawn Pearce <s...@google.com>
Date: Fri, 27 Apr 2012 09:55:24 -0700
Local: Fri, Apr 27 2012 12:55 pm
Subject: Re: Gerrit newbie question: non-administrators creating projects?
Print | View thread | Show original | Report this message | Find messages by this author

On Fri, Apr 27, 2012 at 09:49, Nasser Grainawi <nas...@codeaurora.org> wrote:
> On Apr 27, 2012, at 10:22 AM, Magnus Bäck wrote:

>> On Friday, April 27, 2012 at 12:08 EDT,
>>     Martin Fick <mf...@codeaurora.org> wrote:

>>> For that matter, I think I recall someone requesting a way
>>> to review branch creation also.  Perhaps what we need is
>>> some sort of pseudo changes.  We could have a CREATE_PROJECT
>>> pseudo change and a CREATE_BRANCH pseudo change, perhaps a
>>> DELETE_BRANCH also?

>> Ah, yes. Even for organizations that are liberal with branch
>> creations, non fast-forward ref updates might be limited to
>> a very small number of people. Right now they're getting the
>> requests via email or some outside ticket system.

>> (I'm getting a tingling sense of featuritis here. But it would
>> be cool stuff, and certainly useful for several companies using
>> Gerrit.)

> Yeah, it does start to encroach on the "Gerrit as an issue tracker" idea that Shawn originally pushed away from. At the same time, Gerrit is awesome for reviewing git operations and seems we should try to leverage that...

I am OK with Gerrit reviewing Git operations like project creation,
branch/tag creation/deletion, or non-fast-forward updates to
branch/tag.

I am NOT OK with Gerrit becoming a general purpose issue tracker. I
don't want too much feature creep in the product. We have a hard
enough time as it is just dealing with the features we do support, or
are trying to support, that general purpose issue tracking would
probably kill us.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google