This might seem a little pedantic, but this whole discussion about "commit access" seems inaccurate given the way that bzr and other distributed VCSes were developed. Rather than deciding who can push changes, we should be talking about pulling changes from other branches. That means that anyone can start a branch and work on changes, and then if their feature is approved, the changes can be pulled into trunk, or some other feeder branch.
Again, this doesn't really change the content of the discussion, but the launchpad site doesn't support the idea of "commit access" because bzr isn't built with that concept in mind. This caused me a lot of confusion back when I was trying to start contributing. Owen On Fri, 2010-03-26 at 10:02 -0700, Albert Santoni wrote: > On Fri, Mar 26, 2010 at 1:36 AM, Adam Davison <[email protected]> wrote: > > Hi, > > > > Sounds good. But do we really need core developers and developers? I > > was thinking just core developers and contributors would be enough. I > > mean developers and contributors will both have the same bzr access > > (i.e. not to trunk) right? I guess it might mean some people would get > > moved from developers to contributors which sounds nasty. > > > > I was thinking contributors would not commit have access to the > ~mixxxdevelopers branches. Eg. I might not want random new people > committing into the features_sqlite branch without a merge request > first. We might be able to give them permissions for the bug tracker > though. > > If we could organize ourselves with less teams, I'd be happy, but I > don't see a way to do it... ?? > > Albert > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
