HI Nathan,

On 1/1/20, Nathan Hartman <hartman.nat...@gmail.com> wrote:
> On Wed, Jan 1, 2020 at 1:14 PM Alan Carvalho de Assis <acas...@gmail.com>
> wrote:
>> On 1/1/20, Gregory Nutt <spudan...@gmail.com> wrote:
>> >   * Brennan has done the Confluence pages, investigated Jira, create
>> > the
>> >     initial workflow page
>> >   * Nathan have been staying busy with the workflow
>> >   * Abdelatif has been working a lot with PPMC/committer membership,
>> >     monthly status report
>> >   * I have been doing all of the commits.
>> >
>> > What about the remaining seven people?  Is there no one who wants to
>> > get
>> > their feet wet?  If we are going survive the next months, we all have
>> > to
>> > pitch in and work together.
>> >
>>
>> I want to help reviewing the patches and be guided by you to do it well.
>>
>> In this mean time I took a look at the Workflow page
>> (https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton)
>> and I think it is not describing the Process, so I will try to get
>> your suggested steps and include it there.
>>
>> We could use the Mynewt page as reference:
>>
>> https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests
>>
>> Not their process, but their structure more direct to the goal.
>
> Thank you Alan.
>
> I will greatly appreciate help in getting the workflow complete.
>
> Feel free to edit and reorganize anything in that document to help
> make it more readable and helpful.
>
> Please keep in mind that our document addresses more things that
> aren't discussed in MYNEWT's workflow:
>

Yes, it is true.

After comparing things I think the "NuttX Workflow" will be to much
for a newcomer read if he/she just want to submit a patch/PR.

I think we could have the Workflow document (mostly focused on
Committer) and a document simpler to explain how to submit patches/PR.
We could recommend reading but Workflow, but it could be optional.

> * Where is the code and how to get a copy of it
>
> * The workflow itself (currently lacks all details)
>
> * Criteria for acceptance, which currently is very basic and has no
> details but it will gradually develop over time
>
> * A reference for us committers, to guide us in merging the
> contributions safely to git without messing up the repositories
>
> Any area(s) where you can help, we'll all appreciate it very much.
>

Ok, I will keep getting feedbacks and editing it.

Thank you very much!

BR,

Alan

Reply via email to