For what it is worth that is no longer my proposal which is fine (someone should likely drop my name from the title). Also the last few days have been holiday time for many people. I for instance left my laptop at home, and editing docs on a phone did not seem like a great use of time.
With confluence you can comment easily on specific lines, just highlight it and you will see the comment option. As I mentioned in the confluence page once it stabilizes it should probably move to the contributing.md file. It would be nice if there was a single place or at least platform we did this work on, but long as it is public I guess I don't care too much. --Brennan On Thu, Dec 26, 2019, 6:51 AM Anthony Merlino <anth...@vergeaero.com> wrote: > Hi all, > > I would like to propose a method of collaboration for the workflow > requirements. Nathan and Brennan have done some legwork that is now on the > Wiki - which is a great starting point. Unfortunately, it hasn't seen much > collaboration other than a few comments. > > I believe part of the issue here is that no one wants to go in and change > someone else's proposal. The wiki is also not the most friendly to use for > collaboration and has no method of tracking changes (at least to my > knowledge). > > I have started a CONTRIBUTORS.md file in a personal fork of > incubator-nuttx: > > > https://github.com/antmerlino/incubator-nuttx/blob/antmerlino-contributors-md/CONTRIBUTORS.md > > For those not familiar, CONTRIBUTORS.md is a common file found in many > other open source projects that tells interested parties how to contribute > to the project. It is essentially the workflow document. > > I have asked David to show me the ropes of suggesting changes in the Github > UI. The suggested changes land as separate commits, which allows us to > track changes and authorship while developing this document. You can also > pull the repo, make changes, and open a PR against the branch too, if you > don't want to work in Github. Of course we can squash it all together at > the end when/if we merge it in. This is a much more collaborative way of > working. We can make comments in context, see what others are suggesting, > and integrate that feedback quickly into the deliverable. Otherwise we are > waiting for some poor soul to do 90% of the work themselves and then do the > extra 10% work of integrating people's feedback from the emails. That's not > a good collaboration method. > > If others are keen on this idea, I propose that we move this branch and PR > from my personal fork, to the incubator-nuttx repository, collaborate on > the PR, and land when we are all happy. Based on the discussion here, I > will call a vote to move the PR and branch. > > Best, > Anthony >
