[Dune-devel] Private write access for Andreas
Christian Engwer
christian.engwer at uni-muenster.de
Tue May 7 16:31:14 CEST 2013
Hi Markus,
we already have private branches, namely for Robert and Martin. We
explicitly suggested this setup in the proposal for the repository
layout. All I want to do is use what we decided upon.
> If Andreas works on some features that are/might be of a general
> interest, shouldn't we create a feature branch with a speaking name
> for it? Then people/developers at least know the context the commits
> belong to. This would at least allow for meaningfully filtering the commit
> messages. (Filtering on a person's name seems rather inadequate to me).
We will not have feature branches for all the bug fixes. The idea here
is not to have a private repo with all private new features that
nobody else will use. Still a feature branch can only be created by a
developer, while Andreas can create them easily in his own "namespace".
> Additionally, your approach seems to implement another caste to our
> developer system. Before we had: normal people/contributors,
> developers with write access, and core developers. Now there is
> another one (contributors with private write access) in between the
> first two. Thus DUNE might even more be perceived like an elite clube and
> further keep others from contributing. Do we really want this?
That is the reason to add this. We have some "rules" about when to
grant write access. There are good reason for these rules and there
reasons against these rules. in my opinion these branches are making
it easierr to contribute.
> Having said this, I am be no means against giving Andreas write access
> to the repository according to our already established guidelines.
OK :-)
Cheers
Christian
More information about the Dune-devel
mailing list