Re: salsa.debian.org: merge requests and such
Jonathan Dowland <firstname.lastname@example.org> wrote:
> On Tue, Nov 06, 2018 at 08:06:38PM +0100, Andreas Metzler wrote:
>> Could we document this a little bit better in the wiki? This is
>> completely different than on alioth, where collab-maint was suggested
>> for basically everything that did not need a mailinglist.
> The rules were basically the same for collab-maint as they are for
> Salsa's Debian group, it even says so on that very page you linked:
> "Thanks to ACL, all Debian developers have write access on those
alioth's collab-maint was a zero-admin way to have a Debian hosted GIT
repository, without implying a specific commit-policy. e.g.:
| If a maintainer wants to maintain his/her package within a VCS, (s)he
| can use the collab-maint repository even if the package is not (yet)
| collaboratively maintained. This is always useful since contributors
| are more likely to propose patch if they can be sure that the work has
| not yet been done.
i.e. e.g. for this use case patch-submitting instead of direct
committing was expected.
And this was the way it was used, although DD had commit-rights, they
would not do uncoordinated commits to master. There was no technical
barrier but a social one. Similar to package uploading. Technically
every DD has upload rights for everything, but we have a common ground
what is accepted there. The technical barriers are the same on salsa
as they were on alioth, the implicit barriers obviously have changed,
probably because forking and merge request for private projects is
> But of course, the wiki docs can be improved, including by you :-)
I have updated the wiki, I am little bit more awake than yesterday.
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'