On Sat, Dec 21, 2019 at 11:19 PM 张铎(Duo Zhang) <palomino...@gmail.com>
wrote:

> +1
>
> We should get things done first, and then try to make it better.
>
> For now I agree that the most important thing is to let people contribute,
> although the automate CI is not ready, the committers could do the check
> manually and start to accept patches/PRs.
>
> Thanks.
>
> Brennan Ashton <bash...@brennanashton.com> 于2019年12月22日周日 上午10:06写道:
>
> > I really want to let people to contribute (myself included) ASAP so I was
> > to propose this as an option to get going and can be amended later. I
> know
> > it does not resolve all the issues, but offers what I think is a
> reasonable
> > avenue to get started.
> >
> > Submit a PR on GitHub against master if it is approved by one commiter
> > (that did not propose it) it can be merged.  The approval is done via the
> > GitHub approval system.
> >
> > A commiter may create a PR on behalf of a patch submitted to the mailing
> > list.
> >
> > Commiters can ask for others to review or approve.  But at the end of the
> > day they are the ones who approve and merge.
> >
> > We can and should amend this later, it is likely not enough long term.
> >
> > Could people vote if they think this is fine to start. If you don't agree
> > just note that and we can review where we are at.
> >
> > --Brennan
> >


*PROVIDED* that we continue to hash out the workflow procedures, I would
support that FOR A LIMITED TIME -- TWO WEEKS. By January 1st we had better
have a polished workflow document ready for the PMC to vote on.

Nathan

Reply via email to