Re: [Boost-maint] Process for the Community Maintenance Team

Subject: Re: [Boost-maint] Process for the Community Maintenance Team
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2014-02-01 11:45:07

Le 01/02/14 13:33, Beman Dawes a écrit :
> On Sat, Feb 1, 2014 at 1:04 AM, Vicente J. Botet Escriba <
> vicente.botet_at_[hidden]> wrote:
>
>> Le 27/01/14 02:17, Marshall Clow a écrit :
>>
>>   I’ve put up a set of procedures for the Boost Community Maintenance Team
>>> (CMT)
>>> on the wiki at:         https://svn.boost.org/trac/boost/wiki/
>>> CommunityMaintenance
>>>
>>> Comments welcomed.
>>>
>>>   I don't know Git well.
>> How to provide a patch? Should I checkout the develop branch of the
>> library and post here a patch/diff? How I will do then a pull request? do
>> we mean here a Git pull request?
>> Or should I create a bugfix branch of the develop branch? Do I need some
>> specifics rights to do this?
>>
> See https://help.github.com/articles/using-pull-requests
>
> It fully explains GitHub pull requests.
>
>
The link doesn't answer my question that more about how the CMT would 
organize the work to do.
Anyway, I would use the tems on this link. Could a member of the CMT use 
the Shared repository model? I don't want to do a fork and pool for each 
provided patch.

Vicente