core-dev write permissions to documentation branches?

[Jeremy Bicha]

On 27 August 2011 02:54, Matthew East <mdke at ubuntu.com> wrote:
> On 27 August 2011 04:51, Jeremy Bicha <jbicha at ubuntu.com> wrote:
>> ScottK asked today whether core-dev should have write access to the
>> documentation branches. He was specifically asking about the server-guide
>> since that is only distributed on help.ubuntu.com so it's relatively low
>> risk.
>>
>> It sounds like a reasonable request to me, seeing as we trust core-dev with
>> nearly everything in Ubuntu.
>>
>> So should core-dev be a member of ubuntu-core-doc?
>
> Yes, I think it is a reasonable request too. I have two possible
> concerns though. First, given that good developers aren't necessarily
> good documentation writers (although they may be!), can we ensure that
> people committing to the branch are following our practices properly
> and validating the documentation markup? Second, if we add core-dev to
> core-doc, would we be exposing the core-dev team to a bunch of bug
> reports, merge requests and commit emails which the core-doc team gets
> on a regular basis, or would those emails not go to a subteam? Does
> anyone know enough about Launchpad's setup to resolve that issue?

Maybe we should just add core-dev members on an as-requested basis.
What should the threshold for membership be? Is one accepted patch
sufficient for core-dev contributors?

Jeremy