On Fri, 14 Oct 2022 at 14:31, Alex Bennée wrote:
>
>
> Markus Armbruster writes:
>
> > Mark Cave-Ayland writes:
> >
> >> On 12/10/2022 13:11, Alex Bennée wrote:
> >
> > [...]
> >
> >>> +Becoming a maintainer
> >>> +-
> >>> +
> >>> +Maintainers are volunteers who put
Markus Armbruster writes:
> Mark Cave-Ayland writes:
>
>> On 12/10/2022 13:11, Alex Bennée wrote:
>
> [...]
>
>>> +Becoming a maintainer
>>> +-
>>> +
>>> +Maintainers are volunteers who put themselves forward to keep an eye
>>> +on an area of code. They are generally
Mark Cave-Ayland writes:
> On 12/10/2022 13:11, Alex Bennée wrote:
[...]
>> +Becoming a maintainer
>> +-
>> +
>> +Maintainers are volunteers who put themselves forward to keep an eye
>> +on an area of code. They are generally accepted by the community to
Do you mean
On 12/10/2022 13:11, Alex Bennée wrote:
We don't currently have a clear place in the documentation to describe
the rolls and responsibilities of a maintainer. Lets create one so we
can. I've moved a few small bits out of other files to try and keep
everything in one place.
Signed-off-by: Alex
Alex Bennée writes:
> We don't currently have a clear place in the documentation to describe
> the rolls and responsibilities of a maintainer. Lets create one so we
> can. I've moved a few small bits out of other files to try and keep
> everything in one place.
>
> Signed-off-by: Alex Bennée
>
On Wed, Oct 12, 2022 at 01:11:49PM +0100, Alex Bennée wrote:
> We don't currently have a clear place in the documentation to describe
> the rolls and responsibilities of a maintainer. Lets create one so we
s/roll/role/ in the commit description and the patch.
> can. I've moved a few small bits
We don't currently have a clear place in the documentation to describe
the rolls and responsibilities of a maintainer. Lets create one so we
can. I've moved a few small bits out of other files to try and keep
everything in one place.
Signed-off-by: Alex Bennée
---
docs/devel/code-of-conduct.rst
