Re: Workflow Development
On Fri, Dec 27, 2019 at 12:24 AM Justin Mclean wrote: > > > A chicken and egg problem: he want to do the contribution become the > > committer, but the contribution need be done with committer' rights. > > No it is not, people can contribute without having a commit bit. Like I said before, people seem to have trouble wrapping their mind around that. Somehow we have to take people by the hand and show them how a non-committer contributes. Nathan
Re: Workflow Development
Hi, > The volunteer could sign ICLA which isn't a problem but the work he > will do require the admin rights(setup jenkins, modify github setting > etc.), how can he finish the job if he isn't a committer? No committers or PMC members have admin rights to GitHub. > A chicken and egg problem: he want to do the contribution become the > committer, but the contribution need be done with committer' rights. No it is not, people can contribute without having a commit bit. Thanks, Justin
Re: Workflow Development
You can help him Xiang, and if it is jenkins I could also help. Xiang Xiao 于2019年12月27日周五 下午12:11写道： > On Fri, Dec 27, 2019 at 5:21 AM Justin Mclean > wrote: > > > > Hi, > > > > > I can add you as an Admin to this organization > > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > collaboration > > > to feed upstream. > > > > I would recommend not to work outside of the ASF repos, moving that to > the ASF then requires a grant and contributors to sign ICLAs, and companies > to give permission for their employees to do so, etc etc Also for > committership recognition you want work to occur at the ASF repos. > > The volunteer could sign ICLA which isn't a problem but the work he > will do require the admin rights(setup jenkins, modify github setting > etc.), how can he finish the job if he isn't a committer? > A chicken and egg problem: he want to do the contribution become the > committer, but the contribution need be done with committer' rights. > > > > > > We can collaborate there. > > > > What's wrong will collaborating in the ASF repos? You don’t need to be a > committer to collaborate and doing so means you are more likely to become > one. > > > > Thanks, > > Justin >
Re: Workflow Development
On Fri, Dec 27, 2019 at 5:21 AM Justin Mclean wrote: > > Hi, > > > I can add you as an Admin to this organization > > https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration > > to feed upstream. > > I would recommend not to work outside of the ASF repos, moving that to the > ASF then requires a grant and contributors to sign ICLAs, and companies to > give permission for their employees to do so, etc etc Also for committership > recognition you want work to occur at the ASF repos. The volunteer could sign ICLA which isn't a problem but the work he will do require the admin rights(setup jenkins, modify github setting etc.), how can he finish the job if he isn't a committer? A chicken and egg problem: he want to do the contribution become the committer, but the contribution need be done with committer' rights. > > > We can collaborate there. > > What's wrong will collaborating in the ASF repos? You don’t need to be a > committer to collaborate and doing so means you are more likely to become one. > > Thanks, > Justin
Re: Workflow Development
Thanks, Duo, I posted this in the Wiki comments on your behalf. Greg On 12/26/2019 7:51 PM, 张铎(Duo Zhang) wrote: Thanks sir. I skimmed the wiki, we have almost the same opinion. For a feature branch, we just use same workflow, the only different is that the PR is against the feature branch, not master or dev. And on merging the branch back, for HBase and Hadoop, we will start a vote in the mailing list. And for me, I will create a big PR on GitHub to let users review the final changes, although no one can review it all but users can review the part he/she interested. And also a design doc will help. And finally if no objections, we can merge the feature branch back. From my understanding, there is no '3 more +1s' rule here, as if someone does not want this to be merged, this means we still have some works to do. I do not have the permission to update the wiki so just post things here. Thanks.
Re: Workflow Development
Thanks sir. I skimmed the wiki, we have almost the same opinion. For a feature branch, we just use same workflow, the only different is that the PR is against the feature branch, not master or dev. And on merging the branch back, for HBase and Hadoop, we will start a vote in the mailing list. And for me, I will create a big PR on GitHub to let users review the final changes, although no one can review it all but users can review the part he/she interested. And also a design doc will help. And finally if no objections, we can merge the feature branch back. From my understanding, there is no '3 more +1s' rule here, as if someone does not want this to be merged, this means we still have some works to do. I do not have the permission to update the wiki so just post things here. Thanks. Gregory Nutt 于2019年12月27日周五 上午8:47写道： > Hi Duo > > For complex feature, in Hadoop and HBase and related big data projects > I’ve > > seen in ASF, we will create a feature branch, and then open PRs against > > this branch. And since it is not master, you are free to apply even half > > done PR if the full one is too large. And finally when you are done, > start > > a vote to merge it back. > > > > Usually we will open an issue on jira, and create a sub task for each > > commit of the branch, and the branch also follow the PR-Review-Merge > > workflow. > > > > What David said many times, open a PR and then everyone push to update > the > > PR, I will not define it as our official workflow. You are free to use > what > > you like to develop a feature in your own repo, but when you want to > merge > > it back, you open a PR and do what every contributor should do. > > As I mentioned in a previous email, I proposed some English for the > feature branch requirements at the bottom of > > https://cwiki.apache.org/confluence/display/NUTTXTEST/Code+Contribution+Workflow+--+Brennan+Ashton > > What I wrote there is essentially the same that you are saying here. > You are welcome to review and comment at that URL (which will be moving > when the website is moved to its final home). > > Greg > > >
Re: Workflow Development
Hi Duo For complex feature, in Hadoop and HBase and related big data projects I’ve seen in ASF, we will create a feature branch, and then open PRs against this branch. And since it is not master, you are free to apply even half done PR if the full one is too large. And finally when you are done, start a vote to merge it back. Usually we will open an issue on jira, and create a sub task for each commit of the branch, and the branch also follow the PR-Review-Merge workflow. What David said many times, open a PR and then everyone push to update the PR, I will not define it as our official workflow. You are free to use what you like to develop a feature in your own repo, but when you want to merge it back, you open a PR and do what every contributor should do. As I mentioned in a previous email, I proposed some English for the feature branch requirements at the bottom of https://cwiki.apache.org/confluence/display/NUTTXTEST/Code+Contribution+Workflow+--+Brennan+Ashton What I wrote there is essentially the same that you are saying here. You are welcome to review and comment at that URL (which will be moving when the website is moved to its final home). Greg
Re: Workflow Development
For complex feature, in Hadoop and HBase and related big data projects I’ve seen in ASF, we will create a feature branch, and then open PRs against this branch. And since it is not master, you are free to apply even half done PR if the full one is too large. And finally when you are done, start a vote to merge it back. Usually we will open an issue on jira, and create a sub task for each commit of the branch, and the branch also follow the PR-Review-Merge workflow. What David said many times, open a PR and then everyone push to update the PR, I will not define it as our official workflow. You are free to use what you like to develop a feature in your own repo, but when you want to merge it back, you open a PR and do what every contributor should do. Thanks. Nathan Hartman 于2019年12月26日 周四23:53写道： > On Thu, Dec 26, 2019 at 9:48 AM Xiang Xiao > wrote: > > > > I need correct something here: > > 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we > > just do the workflow defined by PPMC > > 2.Haitao try the workflow work outside apache just because he don't > > have the right > > 3.Any work done by Haitao even in github.com/nuttx should be reviewed > > by all PPMC before commit > > Okay I think I understand: > > When one person wants to create a change, he will do it in his own > local git clone and then send a PR/patch. > > But if the PR/patch is complex and multiple people are collaborating > on it, then they can use a shared git repo, prepare the work, and then > submit the PR/patch to Apache NuttX, like any other PR/patch. > > From the perspective of Apache NuttX, we don't mind if one person or > multiple people created the PR/patch. We only care that when the > PR/patch is presented to us, it always follows the same workflow: > review/test/etc and then commit. Never pushed directly. > > Do I understand correctly? > > Thanks, > Nathan >
RE: Workflow Development
Hi, I feel two things are being blurred together here. There is a How and a What. The What is NuttX: +1 - There (should be) no uninhibited or unfettered NuttX changes. The How - There should uninhibited and unfettered access to the repo and tools to do our parts (jobs) using today's best practices The "How" is what is being discussed. David -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Thursday, December 26, 2019 1:50 PM To: dev@nuttx.apache.org Subject: Re: Workflow Development >>> I can add you as an Admin to this organization >>> https://github.com/nuttx-to-asf it sole purpose is uninhibited >>> collaboration >>> to feed upstream. >> I would recommend not to work outside of the ASF repos, moving that >> to the ASF then requires a grant and contributors to sign ICLAs, and >> companies to give permission for their employees to do so, etc etc >> Also for committership recognition you want work to occur at the ASF >> repos. Also, if ICLAs are required by contributors, we can certainly do that. I don't that would be an obstacle. The word "uninhibited" in the description of the task (and "unfettered" used in another email thread) IS a problem. There is no uninhibited or unfettered NuttX development. Greg
Re: Workflow Development
Hi, > Of course, all works occurs "outside of the ASF repos" on clones or forks. > There is no real way to work "inside" the ASF repos. Normally, you would work > on a fork of the ASF repos and submit PRs to the ASF repos. Normally on other ASF project, I work on a clone, but that a private local clone, not a shared repo. Thanks, Justin
Re: Workflow Development
I can add you as an Admin to this organization https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration to feed upstream. I would recommend not to work outside of the ASF repos, moving that to the ASF then requires a grant and contributors to sign ICLAs, and companies to give permission for their employees to do so, etc etc Also for committership recognition you want work to occur at the ASF repos. Also, if ICLAs are required by contributors, we can certainly do that. I don't that would be an obstacle. The word "uninhibited" in the description of the task (and "unfettered" used in another email thread) IS a problem. There is no uninhibited or unfettered NuttX development. Greg
OT: Re: Workflow Development
(My statements about dictatorship were also just semantics. But let's let that dead dog lie.) Okay.. I will wake up the dead dog a bit. It was mistake to use the word dictator. I should have simply said "I will handle the PRs and patches until the work flow is ready". No one would have objected to that. The semantics are different, but the actual actions are the same). I was being a little vitrolic. Like Trump when he says he is "the /only /person" that can solve problem. Ha!
Re: Workflow Development
I can add you as an Admin to this organization https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration to feed upstream. I would recommend not to work outside of the ASF repos, moving that to the ASF then requires a grant and contributors to sign ICLAs, and companies to give permission for their employees to do so, etc etc Also for committership recognition you want work to occur at the ASF repos. Of course, all works occurs "outside of the ASF repos" on clones or forks. There is no real way to work "inside" the ASF repos. Normally, you would work on a fork of the ASF repos and submit PRs to the ASF repos. But you know that. Just a semantic thing. But emphasizing "outside of the ASF repos" is not the salient issue. The other things you mention are issues. I don't see an problem with other peopls working in the fork. Wouldn't they just be like any other contributor working on a fork. Using 3rd party code is certainly an issue and would require an SGA. Ultimately, the changes end up as "normal" PRs in the AFS repositories. And people should get the credit that they deserve through those PRs. Or am I missing something? I just don't see some of the problems (I do see some others). (My statements about dictatorship were also just semantics. But let's let that dead dog lie.) We can collaborate there. What's wrong will collaborating in the ASF repos? You don’t need to be a committer to collaborate and doing so means you are more likely to become one. That is really a non-sequitur. You can't collaborate in the ASF repos, you can only collaborate in a clone or a fork of the ASF repos. And, to my understanding, that is what is being proposed. I am not a super-big supporter of the approach either because it takes the visibility of the effort out of the hands of the PPMC and pushes all review and comment to the final as-built PR(s) which isn't how things are supposed to work. The PPMC loses all accountability. Greg
Re: Workflow Development
On Thu, Dec 26, 2019 at 4:21 PM Justin Mclean wrote: > What's wrong will collaborating in the ASF repos? You don’t need to be a > committer to collaborate and doing so means you are more likely to become > one. People seem to have a hard time wrapping their mind around that -- the stumbling block seems to be: how can someone collaborate if they can't create a branch and make commits to it. How can we alleviate that concern? Nathan
Re: Workflow Development
Hi, > I can add you as an Admin to this organization > https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration > to feed upstream. I would recommend not to work outside of the ASF repos, moving that to the ASF then requires a grant and contributors to sign ICLAs, and companies to give permission for their employees to do so, etc etc Also for committership recognition you want work to occur at the ASF repos. > We can collaborate there. What's wrong will collaborating in the ASF repos? You don’t need to be a committer to collaborate and doing so means you are more likely to become one. Thanks, Justin
Re: Workflow Development
As a spectator these mailings are like cabaret ... and I do not have to buy tickets :-) Is a wild discussion without any consensus and everyone seems to know better of have better ideas. But nothings seems to happen. Sorry for putting it this way, but sometimes a mirror helps Do first things first? You are all busy with step whatever, but step 1 is no consensus what so ever Sorry if I misinterpreted it...forget what I am saying here Ben Verstuurd vanaf mijn iPhone > Op 26 dec. 2019 om 17:37 heeft Gregory Nutt het > volgende geschreven: > > >> Just send out the invitation to all PPMC except Alin. >> Alin, could you associate your apache account with github account? > > I suspect Alin may not be available over the holidays. Many people will not > be. > > I believe that Alin's github name is jerpelea. He may have other > preferences, however. See https://github.com/jerpelea > > (nice photo). > >
Re: Workflow Development
Just send out the invitation to all PPMC except Alin. Alin, could you associate your apache account with github account? I suspect Alin may not be available over the holidays. Many people will not be. I believe that Alin's github name is jerpelea. He may have other preferences, however. See https://github.com/jerpelea (nice photo).
Re: Workflow Development
Related trademark issues.. but off-topic. IIRC someone has already said but let me speak it again, NuttX trademarks will be transfer to ASF so you can not use NuttX outside ASF any more, unless you get the permit, by sending an email to the trademarks@apache. Yes, but the trademarks are not transferred to the ASF until we graduate. Until then, I hold the trademark. The transfer will make it awkward for people in future that have named things NuttX. I think it is a legitimate use of the name if say a repository that contains a clean mirror of NuttX uses the name, but nothing that deviates from Apache NuttX should have a different name. I think all use of the name will have to acknowledge that it is a trademark of the ASF. In the meantime, I am very tolerant of the use of the trademark. I only hold it to prevent bad guys from doing bad things with the name, not to limit what the good guys can do. But the ASF will be much more strict We have to be cautious of the use of trademarks ourselves. Many words we toss around in messages and documents are actually trademarked and the use of those trademarks are sometime enforced. Examples: Linux -- trademark of Linus Torvalds POSIX and IEEE -- trademarks of Institute of Electrical and Electronic Engineers, Inc. Unix -- trademark of the Open Group. I try to avoid the use of the word Unix and will usually say "Unix-like". I similarly avoid the use of POSIX which requires certification before you can claim to be a POSIX OS. I usually try to say "the portable POSIX interface" or "NuttX conforms to most POSIX specifications." Saying that NuttX is POSIX or that NuttX is Unix is a trademark violation. Greg
RE: Workflow Development
Hi Nathan, -Original Message- From: Nathan Hartman [mailto:hartman.nat...@gmail.com] Sent: Thursday, December 26, 2019 7:45 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development On Thu, Dec 26, 2019 at 9:48 AM Xiang Xiao wrote: > > I need correct something here: > 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we > just do the workflow defined by PPMC > 2.Haitao try the workflow work outside apache just because he don't > have the right > 3.Any work done by Haitao even in github.com/nuttx should be reviewed > by all PPMC before commit Okay I think I understand: When one person wants to create a change, he will do it in his own local git clone and then send a PR/patch. [DBS] Yes ROLE:Contributor But if the PR/patch is complex and multiple people are collaborating on it, then they can use a shared git repo, prepare the work, and then submit the PR/patch to Apache NuttX, like any other PR/patch. [DBS] Yes ROLE:ContributorS >From the perspective of Apache NuttX, we don't mind if one person or multiple people created the PR/patch. We only care that when the PR/patch is presented to us, it always follows the same workflow: review/test/etc and then commit. Never pushed directly. [DBS] precommit compliance. PR push compliance, then review/test, (loop) then merge. Do I understand correctly? [DBS] Not 100%. The of ROLE:Commiter and the ROLE:PMC have been reduced to Contributor it what you are describing I have explained what collaboration means in many, many emails. Now that you have a GH account play with it. Make a mock ASF org (ADD the PMC to it) and you can see how this works with you sandboxed in your own account. But all of use able to push to your MOCK. David Thanks, Nathan
Re: Workflow Development
On Thu, Dec 26, 2019 at 9:48 AM Xiang Xiao wrote: > > I need correct something here: > 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we > just do the workflow defined by PPMC > 2.Haitao try the workflow work outside apache just because he don't > have the right > 3.Any work done by Haitao even in github.com/nuttx should be reviewed > by all PPMC before commit Okay I think I understand: When one person wants to create a change, he will do it in his own local git clone and then send a PR/patch. But if the PR/patch is complex and multiple people are collaborating on it, then they can use a shared git repo, prepare the work, and then submit the PR/patch to Apache NuttX, like any other PR/patch. >From the perspective of Apache NuttX, we don't mind if one person or multiple people created the PR/patch. We only care that when the PR/patch is presented to us, it always follows the same workflow: review/test/etc and then commit. Never pushed directly. Do I understand correctly? Thanks, Nathan
Re: Workflow Development
IIRC someone has already said but let me speak it again, NuttX trademarks will be transfer to ASF so you can not use NuttX outside ASF any more, unless you get the permit, by sending an email to the trademarks@apache. Yes, but the trademarks are not transferred to the ASF until we graduate. Until then, I hold the trademark. The transfer will make it awkward for people in future that have named things NuttX. I think it is a legitimate use of the name if say a repository that contains a clean mirror of NuttX uses the name, but nothing that deviates from Apache NuttX should have a different name. I think all use of the name will have to acknowledge that it is a trademark of the ASF. In the meantime, I am very tolerant of the use of the trademark. I only hold it to prevent bad guys from doing bad things with the name, not to limit what the good guys can do. But the ASF will be much more strict
Re: Workflow Development
IIRC someone has already said but let me speak it again, NuttX trademarks will be transfer to ASF so you can not use NuttX outside ASF any more, unless you get the permit, by sending an email to the trademarks@apache. Gregory Nutt 于2019年12月26日周四 下午10:50写道： > +1 > > Thank you for stating what should be obvious. > > On 12/26/2019 8:48 AM, Xiang Xiao wrote: > > I need correct something here: > > 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we > > just do the workflow defined by PPMC > > 2.Haitao try the workflow work outside apache just because he don't > > have the right > > 3.Any work done by Haitao even in github.com/nuttx should be reviewed > > by all PPMC before commit > > > > Thanks > > Xiang > >
Re: Workflow Development
+1 Thank you for stating what should be obvious. On 12/26/2019 8:48 AM, Xiang Xiao wrote: I need correct something here: 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we just do the workflow defined by PPMC 2.Haitao try the workflow work outside apache just because he don't have the right 3.Any work done by Haitao even in github.com/nuttx should be reviewed by all PPMC before commit Thanks Xiang
Re: Workflow Development
I need correct something here: 1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we just do the workflow defined by PPMC 2.Haitao try the workflow work outside apache just because he don't have the right 3.Any work done by Haitao even in github.com/nuttx should be reviewed by all PPMC before commit Thanks Xiang On Thu, Dec 26, 2019 at 10:38 PM Gregory Nutt wrote: > > > > Uh what exactly is going on? > > Essentially, they are taking the development of the NuttX workflow > automation outside of the project and developing it independently. > Presumably it would come back into the project at a later date. This is > not in the hands of the PPMC, but we should take takes to make sure that > we have a processes in place to handle the PX4 workflow when they bring > it upstream. > > This means, again, solid, complete, agreed to, workflow requirements. > That is the key to everything... to every difficult issue before the > PPMC now. >
RE: Workflow Development
It unblocks Haitao Liu. Xiami's tool master. -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Thursday, December 26, 2019 6:39 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development > Uh what exactly is going on? Essentially, they are taking the development of the NuttX workflow automation outside of the project and developing it independently. Presumably it would come back into the project at a later date. This is not in the hands of the PPMC, but we should take takes to make sure that we have a processes in place to handle the PX4 workflow when they bring it upstream. This means, again, solid, complete, agreed to, workflow requirements. That is the key to everything... to every difficult issue before the PPMC now.
Re: Workflow Development
I want to avoid upsetting you. Let me be more direct and ask to you be more direct. Greg are you going to be using language like "abuse of power" if we are creating repos, branches pushing to the github NuttX organization? Yes on No? As you put it YES. If must follow the same workflow as all other code that comes into the repository. Nothing can be pushed. Only PRs or patches!! Each must be reviewed and approved by the PPMC. It would indeed be an unacceptable abuse of power to push anything from your out-of-project working directories into NuttX. That must NEVER happen.
Re: Workflow Development
Uh what exactly is going on? Essentially, they are taking the development of the NuttX workflow automation outside of the project and developing it independently. Presumably it would come back into the project at a later date. This is not in the hands of the PPMC, but we should take takes to make sure that we have a processes in place to handle the PX4 workflow when they bring it upstream. This means, again, solid, complete, agreed to, workflow requirements. That is the key to everything... to every difficult issue before the PPMC now.
RE: Workflow Development
I want to avoid upsetting you. Let me be more direct and ask to you be more direct. Greg are you going to be using language like "abuse of power" if we are creating repos, branches pushing to the github NuttX organization? Yes on No? David -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Thursday, December 26, 2019 6:30 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development > You have been granted admin access to NuttX. Admins have full rights to > the > organization and have complete access to all repositories and teams > > Do ALL the PPMC agree that ALL have FULL unfetter access? The PPMC has no direct control of anything that is happening outside of the project. The authority of the PPMC steps in when there is an attempt to move that code upstream. Then the submission must follow the rules of workflow and is subject to review and verification. So it would be wise to keep things coordinated so that the final merge is a no-brainer, slam dunk and not another difficult step. Keeping is good communication would be wise (better communication than the word "unfetter"ed implies). Have as many participants from the PPMC as possible would also be helpful: Brennan, Nathan, Anthony, ... whoever has interest .. Alan, Abdelatif, Alin, Xiao Xian? And also participants outside the PPMC: Haitao Liu, David Alessio, and Duo Zhang.
Re: Workflow Development
All PPMC should have the equal rights. This is the essence of "THE APACHE WAY", do I understand correctly? You will not have equal rights on any development outside of the Apache project. The PPMC authority does not extend to other, external projects.
Re: Workflow Development
Nathan, github.com/nuttx is a sedentary location for thing which can't handle in the official apache repository: 1.Some contributor don't have rights to modify the apache infra to try and prepare the workflow. 2.The companion repo(build, tools ,ucLibc++ etc) need find a location before we can put them into apache Of course, we should try our best to do the work inside the apache, but sometime github.com/nuttx is a suitable place to avoid the work stuck. On Thu, Dec 26, 2019 at 10:21 PM Nathan Hartman wrote: > > On Thu, Dec 26, 2019 at 9:14 AM David Sidrane > wrote: > > > This came to me. > > > > You have been granted admin access to NuttX. Admins have full rights to the > > organization and have complete access to all repositories and teams > > > > Do ALL the PPMC agree that ALL have FULL unfetter access? > > > Uh what exactly is going on? > > Nathan
Re: Workflow Development
You have been granted admin access to NuttX. Admins have full rights to the organization and have complete access to all repositories and teams Do ALL the PPMC agree that ALL have FULL unfetter access? The PPMC has no direct control of anything that is happening outside of the project. The authority of the PPMC steps in when there is an attempt to move that code upstream. Then the submission must follow the rules of workflow and is subject to review and verification. So it would be wise to keep things coordinated so that the final merge is a no-brainer, slam dunk and not another difficult step. Keeping is good communication would be wise (better communication than the word "unfetter"ed implies). Have as many participants from the PPMC as possible would also be helpful: Brennan, Nathan, Anthony, ... whoever has interest .. Alan, Abdelatif, Alin, Xiao Xian? And also participants outside the PPMC: Haitao Liu, David Alessio, and Duo Zhang.
Re: Workflow Development
All PPMC should have the equal rights. This is the essence of "THE APACHE WAY", do I understand correctly? On Thu, Dec 26, 2019 at 10:14 PM David Sidrane wrote: > > This came to me. > > You have been granted admin access to NuttX. Admins have full rights to the > organization and have complete access to all repositories and teams > > Do ALL the PPMC agree that ALL have FULL unfetter access? > > David > > > -Original Message- > From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] > Sent: Thursday, December 26, 2019 5:39 AM > To: dev@nuttx.apache.org > Subject: Re: Workflow Development > > Why we not reuse github.com/nuttx to do the test? > > On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > > > David, my github username liuguo09 liugu...@gmail.com. We could do some > > tests to prepare for final workflow. > > > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > > > Hi Haitao, > > > > > > I can add you as an Admin to this organization > > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > > collaboration > > > to feed upstream. > > > > > > We can collaborate there. We can do all the setup and testing there, > > > perfect > > > it and upstream it to ASF. > > > We can also figure out what we cannot accomplish without admin on the > > > asf-repo > > > We can make a list of the things we them need from infra. > > > > > > What is you git user name? > > > > > > Anyone else want in as admins just ask. > > > > > > David > > > > > > -Original Message- > > > From: Haitao Liu [mailto:liugu...@gmail.com] > > > Sent: Wednesday, December 25, 2019 7:21 PM > > > To: dev@nuttx.apache.org > > > Subject: Re: Workflow Development > > > > > > Hi, > > > > > > I am glad to participate in nuttx workflow development and wourld try my > > > best to make more contributions later : ) > > > > > > Justin, since I'm not a committer for nuttx now, if I want to access > > > nuttx > > > workflow related apache resources(Jenkins CI, Confluence, Release etc ) > > > , > > > what should I do? Email account or sth others in need? > > > > > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > > > Hi, > > > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate > > > > > what > > > > the work on, the PPMC as a whole sets direction and individuals decide > > > > what > > > > they can work on. > > > > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I > > > > meant > > > to > > > > say: > > > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > > > what > > > > they work on, the PPMC as a whole sets direction and individuals > > > > decide > > > > what they can work on. > > > > > > > > Thanks, > > > > Justin > > >
Re: Workflow Development
On Thu, Dec 26, 2019 at 9:14 AM David Sidrane wrote: > This came to me. > > You have been granted admin access to NuttX. Admins have full rights to the > organization and have complete access to all repositories and teams > > Do ALL the PPMC agree that ALL have FULL unfetter access? Uh what exactly is going on? Nathan
RE: Workflow Development
This came to me. You have been granted admin access to NuttX. Admins have full rights to the organization and have complete access to all repositories and teams Do ALL the PPMC agree that ALL have FULL unfetter access? David -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Thursday, December 26, 2019 5:39 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development Why we not reuse github.com/nuttx to do the test? On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > David, my github username liuguo09 liugu...@gmail.com. We could do some > tests to prepare for final workflow. > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > Hi Haitao, > > > > I can add you as an Admin to this organization > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > collaboration > > to feed upstream. > > > > We can collaborate there. We can do all the setup and testing there, > > perfect > > it and upstream it to ASF. > > We can also figure out what we cannot accomplish without admin on the > > asf-repo > > We can make a list of the things we them need from infra. > > > > What is you git user name? > > > > Anyone else want in as admins just ask. > > > > David > > > > -Original Message----- > > From: Haitao Liu [mailto:liugu...@gmail.com] > > Sent: Wednesday, December 25, 2019 7:21 PM > > To: dev@nuttx.apache.org > > Subject: Re: Workflow Development > > > > Hi, > > > > I am glad to participate in nuttx workflow development and wourld try my > > best to make more contributions later : ) > > > > Justin, since I'm not a committer for nuttx now, if I want to access > > nuttx > > workflow related apache resources(Jenkins CI, Confluence, Release etc ) > > , > > what should I do? Email account or sth others in need? > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > Hi, > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate > > > > what > > > the work on, the PPMC as a whole sets direction and individuals decide > > > what > > > they can work on. > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I > > > meant > > to > > > say: > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > > what > > > they work on, the PPMC as a whole sets direction and individuals > > > decide > > > what they can work on. > > > > > > Thanks, > > > Justin > >
RE: Workflow Development
Awesome - We should have done this on the day we landed in ASF. -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Thursday, December 26, 2019 5:53 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development Just send out the invitation to all PPMC except Alin. Alin, could you associate your apache account with github account? Anthony also need update it. BTW, github.com/nuttx is a good place for the remaining repo until we find some way to put them into apache. Thanks Xiang On Thu, Dec 26, 2019 at 9:40 PM David Sidrane wrote: > > The PPMC does not have admin on it > > -Original Message- > From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] > Sent: Thursday, December 26, 2019 5:39 AM > To: dev@nuttx.apache.org > Subject: Re: Workflow Development > > Why we not reuse github.com/nuttx to do the test? > > On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > > > David, my github username liuguo09 liugu...@gmail.com. We could do some > > tests to prepare for final workflow. > > > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > > > Hi Haitao, > > > > > > I can add you as an Admin to this organization > > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > > collaboration > > > to feed upstream. > > > > > > We can collaborate there. We can do all the setup and testing there, > > > perfect > > > it and upstream it to ASF. > > > We can also figure out what we cannot accomplish without admin on the > > > asf-repo > > > We can make a list of the things we them need from infra. > > > > > > What is you git user name? > > > > > > Anyone else want in as admins just ask. > > > > > > David > > > > > > -Original Message- > > > From: Haitao Liu [mailto:liugu...@gmail.com] > > > Sent: Wednesday, December 25, 2019 7:21 PM > > > To: dev@nuttx.apache.org > > > Subject: Re: Workflow Development > > > > > > Hi, > > > > > > I am glad to participate in nuttx workflow development and wourld try > > > my > > > best to make more contributions later : ) > > > > > > Justin, since I'm not a committer for nuttx now, if I want to access > > > nuttx > > > workflow related apache resources(Jenkins CI, Confluence, Release > > > etc ) > > > , > > > what should I do? Email account or sth others in need? > > > > > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > > > Hi, > > > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate > > > > > what > > > > the work on, the PPMC as a whole sets direction and individuals > > > > decide > > > > what > > > > they can work on. > > > > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I > > > > meant > > > to > > > > say: > > > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > > > what > > > > they work on, the PPMC as a whole sets direction and individuals > > > > decide > > > > what they can work on. > > > > > > > > Thanks, > > > > Justin > > >
Re: Workflow Development
Just send out the invitation to all PPMC except Alin. Alin, could you associate your apache account with github account? Anthony also need update it. BTW, github.com/nuttx is a good place for the remaining repo until we find some way to put them into apache. Thanks Xiang On Thu, Dec 26, 2019 at 9:40 PM David Sidrane wrote: > > The PPMC does not have admin on it > > -Original Message- > From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] > Sent: Thursday, December 26, 2019 5:39 AM > To: dev@nuttx.apache.org > Subject: Re: Workflow Development > > Why we not reuse github.com/nuttx to do the test? > > On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > > > David, my github username liuguo09 liugu...@gmail.com. We could do some > > tests to prepare for final workflow. > > > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > > > Hi Haitao, > > > > > > I can add you as an Admin to this organization > > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > > collaboration > > > to feed upstream. > > > > > > We can collaborate there. We can do all the setup and testing there, > > > perfect > > > it and upstream it to ASF. > > > We can also figure out what we cannot accomplish without admin on the > > > asf-repo > > > We can make a list of the things we them need from infra. > > > > > > What is you git user name? > > > > > > Anyone else want in as admins just ask. > > > > > > David > > > > > > -Original Message- > > > From: Haitao Liu [mailto:liugu...@gmail.com] > > > Sent: Wednesday, December 25, 2019 7:21 PM > > > To: dev@nuttx.apache.org > > > Subject: Re: Workflow Development > > > > > > Hi, > > > > > > I am glad to participate in nuttx workflow development and wourld try my > > > best to make more contributions later : ) > > > > > > Justin, since I'm not a committer for nuttx now, if I want to access > > > nuttx > > > workflow related apache resources(Jenkins CI, Confluence, Release etc ) > > > , > > > what should I do? Email account or sth others in need? > > > > > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > > > Hi, > > > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate > > > > > what > > > > the work on, the PPMC as a whole sets direction and individuals decide > > > > what > > > > they can work on. > > > > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I > > > > meant > > > to > > > > say: > > > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > > > what > > > > they work on, the PPMC as a whole sets direction and individuals > > > > decide > > > > what they can work on. > > > > > > > > Thanks, > > > > Justin > > >
Re: Workflow Development
Why we not reuse github.com/nuttx to do the test? That is essentially the same as nuttx-to-asf. Justin did point out that once I grant the NuttX trademark to apache, we will no longer be able to use that name without permission. So bother are only good while are a podling (which will be awhile). I suppose the same goes for the Bitbucket NuttX team.
SGA for the PX4 (was RE: Workflow Development)
I will ask Lorenz for a definitive answer. -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Thursday, December 26, 2019 5:43 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development > Will we get an SGA for the PX4 code that will come in? If not, it > cannot become Apache. I think that all new files will need the Apache source file header: https://www.apache.org/legal/src-headers.html That references special handling for 3rd party files like PX4 (with no SGA).
Re: Workflow Development
Will we get an SGA for the PX4 code that will come in? If not, it cannot become Apache. I think that all new files will need the Apache source file header: https://www.apache.org/legal/src-headers.html That references special handling for 3rd party files like PX4 (with no SGA).
RE: Workflow Development
The PPMC does not have admin on it -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Thursday, December 26, 2019 5:39 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development Why we not reuse github.com/nuttx to do the test? On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > David, my github username liuguo09 liugu...@gmail.com. We could do some > tests to prepare for final workflow. > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > Hi Haitao, > > > > I can add you as an Admin to this organization > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > collaboration > > to feed upstream. > > > > We can collaborate there. We can do all the setup and testing there, > > perfect > > it and upstream it to ASF. > > We can also figure out what we cannot accomplish without admin on the > > asf-repo > > We can make a list of the things we them need from infra. > > > > What is you git user name? > > > > Anyone else want in as admins just ask. > > > > David > > > > -Original Message----- > > From: Haitao Liu [mailto:liugu...@gmail.com] > > Sent: Wednesday, December 25, 2019 7:21 PM > > To: dev@nuttx.apache.org > > Subject: Re: Workflow Development > > > > Hi, > > > > I am glad to participate in nuttx workflow development and wourld try my > > best to make more contributions later : ) > > > > Justin, since I'm not a committer for nuttx now, if I want to access > > nuttx > > workflow related apache resources(Jenkins CI, Confluence, Release etc ) > > , > > what should I do? Email account or sth others in need? > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > Hi, > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate > > > > what > > > the work on, the PPMC as a whole sets direction and individuals decide > > > what > > > they can work on. > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I > > > meant > > to > > > say: > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > > what > > > they work on, the PPMC as a whole sets direction and individuals > > > decide > > > what they can work on. > > > > > > Thanks, > > > Justin > >
RE: Workflow Development
Your invited with full admin! -Original Message- From: Haitao Liu [mailto:liugu...@gmail.com] Sent: Thursday, December 26, 2019 5:34 AM To: dev@nuttx.apache.org Subject: Re: Workflow Development David, my github username liuguo09 liugu...@gmail.com. We could do some tests to prepare for final workflow. David Sidrane 于2019年12月26日周四 下午4:55写道： > Hi Haitao, > > I can add you as an Admin to this organization > https://github.com/nuttx-to-asf it sole purpose is uninhibited > collaboration > to feed upstream. > > We can collaborate there. We can do all the setup and testing there, > perfect > it and upstream it to ASF. > We can also figure out what we cannot accomplish without admin on the > asf-repo > We can make a list of the things we them need from infra. > > What is you git user name? > > Anyone else want in as admins just ask. > > David > > -Original Message- > From: Haitao Liu [mailto:liugu...@gmail.com] > Sent: Wednesday, December 25, 2019 7:21 PM > To: dev@nuttx.apache.org > Subject: Re: Workflow Development > > Hi, > > I am glad to participate in nuttx workflow development and wourld try my > best to make more contributions later : ) > > Justin, since I'm not a committer for nuttx now, if I want to access nuttx > workflow related apache resources(Jenkins CI, Confluence, Release etc ) , > what should I do? Email account or sth others in need? > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > Hi, > > > > > I not sure what you mean by this, peoples $dayjob should dictate what > > the work on, the PPMC as a whole sets direction and individuals decide > > what > > they can work on. > > > > > > Sorry I should check what I wrote before I hit the send button. I meant > to > > say: > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate > > what > > they work on, the PPMC as a whole sets direction and individuals decide > > what they can work on. > > > > Thanks, > > Justin >
Re: Workflow Development
Why we not reuse github.com/nuttx to do the test? On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote: > > David, my github username liuguo09 liugu...@gmail.com. We could do some > tests to prepare for final workflow. > > David Sidrane 于2019年12月26日周四 下午4:55写道： > > > Hi Haitao, > > > > I can add you as an Admin to this organization > > https://github.com/nuttx-to-asf it sole purpose is uninhibited > > collaboration > > to feed upstream. > > > > We can collaborate there. We can do all the setup and testing there, > > perfect > > it and upstream it to ASF. > > We can also figure out what we cannot accomplish without admin on the > > asf-repo > > We can make a list of the things we them need from infra. > > > > What is you git user name? > > > > Anyone else want in as admins just ask. > > > > David > > > > -Original Message----- > > From: Haitao Liu [mailto:liugu...@gmail.com] > > Sent: Wednesday, December 25, 2019 7:21 PM > > To: dev@nuttx.apache.org > > Subject: Re: Workflow Development > > > > Hi, > > > > I am glad to participate in nuttx workflow development and wourld try my > > best to make more contributions later : ) > > > > Justin, since I'm not a committer for nuttx now, if I want to access nuttx > > workflow related apache resources(Jenkins CI, Confluence, Release etc ) , > > what should I do? Email account or sth others in need? > > > > > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > > > Hi, > > > > > > > I not sure what you mean by this, peoples $dayjob should dictate what > > > the work on, the PPMC as a whole sets direction and individuals decide > > > what > > > they can work on. > > > > > > > > > Sorry I should check what I wrote before I hit the send button. I meant > > to > > > say: > > > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate what > > > they work on, the PPMC as a whole sets direction and individuals decide > > > what they can work on. > > > > > > Thanks, > > > Justin > >
Re: Workflow Development
David, my github username liuguo09 liugu...@gmail.com. We could do some tests to prepare for final workflow. David Sidrane 于2019年12月26日周四 下午4:55写道： > Hi Haitao, > > I can add you as an Admin to this organization > https://github.com/nuttx-to-asf it sole purpose is uninhibited > collaboration > to feed upstream. > > We can collaborate there. We can do all the setup and testing there, > perfect > it and upstream it to ASF. > We can also figure out what we cannot accomplish without admin on the > asf-repo > We can make a list of the things we them need from infra. > > What is you git user name? > > Anyone else want in as admins just ask. > > David > > -Original Message- > From: Haitao Liu [mailto:liugu...@gmail.com] > Sent: Wednesday, December 25, 2019 7:21 PM > To: dev@nuttx.apache.org > Subject: Re: Workflow Development > > Hi, > > I am glad to participate in nuttx workflow development and wourld try my > best to make more contributions later : ) > > Justin, since I'm not a committer for nuttx now, if I want to access nuttx > workflow related apache resources(Jenkins CI, Confluence, Release etc ) , > what should I do? Email account or sth others in need? > > > > Justin Mclean 于2019年12月26日周四 上午7:54写道： > > > Hi, > > > > > I not sure what you mean by this, peoples $dayjob should dictate what > > the work on, the PPMC as a whole sets direction and individuals decide > > what > > they can work on. > > > > > > Sorry I should check what I wrote before I hit the send button. I meant > to > > say: > > > > I not sure what you mean by this, peoples $dayjob should NOT dictate what > > they work on, the PPMC as a whole sets direction and individuals decide > > what they can work on. > > > > Thanks, > > Justin >
RE: Workflow Development
We should get a quick read from Justin: is developing substantial code outside of incubator acceptable? And how do we get a proper review againet the workflow requirements before merging upstream?You really should wait for the workflow requirements first or be completely open to rework.Will we get an SGA for the PX4 code that will come in? If not, it cannot beome Apache.Sent from Samsung tablet. null
RE: Workflow Development
Hi Haitao, I can add you as an Admin to this organization https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration to feed upstream. We can collaborate there. We can do all the setup and testing there, perfect it and upstream it to ASF. We can also figure out what we cannot accomplish without admin on the asf-repo We can make a list of the things we them need from infra. What is you git user name? Anyone else want in as admins just ask. David -Original Message- From: Haitao Liu [mailto:liugu...@gmail.com] Sent: Wednesday, December 25, 2019 7:21 PM To: dev@nuttx.apache.org Subject: Re: Workflow Development Hi, I am glad to participate in nuttx workflow development and wourld try my best to make more contributions later : ) Justin, since I'm not a committer for nuttx now, if I want to access nuttx workflow related apache resources(Jenkins CI, Confluence, Release etc ) , what should I do? Email account or sth others in need? Justin Mclean 于2019年12月26日周四 上午7:54写道： > Hi, > > > I not sure what you mean by this, peoples $dayjob should dictate what > the work on, the PPMC as a whole sets direction and individuals decide > what > they can work on. > > > Sorry I should check what I wrote before I hit the send button. I meant to > say: > > I not sure what you mean by this, peoples $dayjob should NOT dictate what > they work on, the PPMC as a whole sets direction and individuals decide > what they can work on. > > Thanks, > Justin
Re: Workflow Development
Hi, I am glad to participate in nuttx workflow development and wourld try my best to make more contributions later : ) Justin, since I'm not a committer for nuttx now, if I want to access nuttx workflow related apache resources(Jenkins CI, Confluence, Release etc ) , what should I do? Email account or sth others in need? Justin Mclean 于2019年12月26日周四 上午7:54写道： > Hi, > > > I not sure what you mean by this, peoples $dayjob should dictate what > the work on, the PPMC as a whole sets direction and individuals decide what > they can work on. > > > Sorry I should check what I wrote before I hit the send button. I meant to > say: > > I not sure what you mean by this, peoples $dayjob should NOT dictate what > they work on, the PPMC as a whole sets direction and individuals decide > what they can work on. > > Thanks, > Justin
Re: Workflow Development
Hi, > I not sure what you mean by this, peoples $dayjob should dictate what the > work on, the PPMC as a whole sets direction and individuals decide what they > can work on. Sorry I should check what I wrote before I hit the send button. I meant to say: I not sure what you mean by this, peoples $dayjob should NOT dictate what they work on, the PPMC as a whole sets direction and individuals decide what they can work on. Thanks, Justin
Re: Workflow Development
HI, > * Staffing. There should be multiple people working on the workflow. > Haitao Liu is the dedicated resource for workflow development and > long term support. ASF projects tend not to have set roles, anything who has teh time, knowledge and effort can contribute. > Haitao must be involved, that is his job. I not sure what you mean by this, peoples $dayjob should dictate what the work on, the PPMC as a whole sets direction and individuals decide what they can work on. Thanks, Justin
Re: Workflow Development
HI, > Haitao Liu was once proposed as a committer only so that he could have access > to repositories in order to do his job. We were told that we should not do > that because he does not have a demonstrated track record of contributions to > the Apache NuttX project. That would be correct, but it not a hard issue to solve have them show up and do stuff. Anyone shovel be able to become a committer in a short period of time by interacting on the mailing list and making contributions. > But we were also told that there was another mechanism for granting github > access to Haitao so the he was not need to be an official committer. We can give other people access to confluence but not github only committers have access to that. > Can any mentor please expand on this and provide us with the steps that we > need to do to grant github access to Haitao. Make contributions, and be voting in as a committer is the best path. > An option might be to mirror that incubator-nuttx* repositories at > github.com/NuttX. Work on an Apache project should happen in Apache repos. Thanks, Justin
Re: 3rd party code (Re: Workflow Development)
HI, > Now I am wondering if this might not also be a good place to move some of the > 3rd party software in apps/ (nuttx/ 3rd party code is minimal and not so > modular that it could be easily extracted). incubator-nuttx-apps would be > reduced to a build environment with most applications installable at build > time from github.com/NuttX. You need to carefully consider trademark and branding policies. [1][2] If there is a repo called “NuttX” will that cure any confusion with users is that part of the Apache project or not? Thanks, Justin 1. https://www.apache.org/foundation/marks/pmcs 2. https://www.apache.org/foundation/marks/
Re: Workflow Development
* Staffing. There should be multiple people working on the workflow. Haitao Liu is the dedicated resource for workflow development and long term support. Haitao must be involved, that is his job. Other interested parties, inside or outside the PPMC can also participate. Within the PPMC, I think that DavidS, Brennan, and Anthony Merlino might have an interest in participating. David Alessio also has expressed an interest in working with the workflow. Please! We need help! Anyone who wants to participate and doesn't have an account, Justin said that access to the Confluence can be arranged. If we want additional help outside of the core team, then we have no option. Justin said that new committers must a history of contribuions to Apache NuttX, not just NuttX. So there probably wont' be any new committers for a few months. Tic toc the game is locked. So I think we are going to have to so something like this. NOTE: A good thing about this is then those people HAVE made Apache NuttX contributions and can be be made committers. Greg
Re: Workflow Development
On Wed, Dec 25, 2019 at 11:16 AM Gregory Nutt wrote: > > > > * Staffing. There should be multiple people working on the > > workflow. Haitao Liu is the dedicated resource for workflow > > development and long term support. Haitao must be involved, that > > is his job. Other interested parties, inside or outside the PPMC > > can also participate. Within the PPMC, I think that DavidS, > > Brennan, and Anthony Merlino might have an interest in participating. > > > David Alessio also has expressed an interest in working with the workflow. Please! We need help! Anyone who wants to participate and doesn't have an account, Justin said that access to the Confluence can be arranged.
3rd party code (Re: Workflow Development)
At one point I suggested that maybe we could used the non-Apache NuttX repository to do workflow development since would not restrict access to the key player, Haitao Liu. An option might be to mirror that incubator-nuttx* repositories at github.com/NuttX. Haitao does have access there. That might be a good open proving ground for workflow changes. Good workflow fixes could then be pulled into github/apache/NuttX. Now I am wondering if this might not also be a good place to move some of the 3rd party software in apps/ (nuttx/ 3rd party code is minimal and not so modular that it could be easily extracted). incubator-nuttx-apps would be reduced to a build environment with most applications installable at build time from github.com/NuttX. It is premature to decide since SGAs may not be required anyway. But let's see how that goes. This is one option that can go on the list.
Re: Workflow Development
* Staffing. There should be multiple people working on the workflow. Haitao Liu is the dedicated resource for workflow development and long term support. Haitao must be involved, that is his job. Other interested parties, inside or outside the PPMC can also participate. Within the PPMC, I think that DavidS, Brennan, and Anthony Merlino might have an interest in participating. David Alessio also has expressed an interest in working with the workflow.
Re: Workflow Development
Mentors... * Haitao Liu is the dedicated resource for workflow development and long term support. Haitao must be involved, that is his job. ... Haitao Liu was once proposed as a committer only so that he could have access to repositories in order to do his job. We were told that we should not do that because he does not have a demonstrated track record of contributions to the Apache NuttX project. But we were also told that there was another mechanism for granting github access to Haitao so the he was not need to be an official committer. Can any mentor please expand on this and provide us with the steps that we need to do to grant github access to Haitao. An option might be to mirror that incubator-nuttx* repositories at github.com/NuttX. Haitao does have access there. That might be a good open proving ground for workflow changes. Good workflow fixes could then be pulled into github/apache/NuttX. Thanks, Greg
RE: Workflow Development
+1 Agree I have not seen any WF proposals from Haitao Liu (other then on the submodule discussion) Haitao Liu please chime in. Have any of you used this? https://www.visual-paradigm.com/download/community.jsp Awesome tool with a super efficient UI This is an activity diagram David -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Wednesday, December 25, 2019 7:27 AM To: dev@nuttx.apache.org Subject: Workflow Development Once we have the workflow requirements in place we need to discuss how to manage to the workflow development. I expect it will be a couple of weeks before those requirements are in place, but it is not too early to talk about the development. There are at least two things we can consider now: * Staffing. There should be multiple people working on the workflow. Haitao Liu is the dedicated resource for workflow development and long term support. Haitao must be involved, that is his job. Other interested parties, inside or outside the PPMC can also participate. Within the PPMC, I think that DavidS, Brennan, and Anthony Merlino might have an interest in participating. * Branch/Repository. I think that there should be a common branch in github... or perhaps a new nuttx-testing repository as we have talked about in the past. The develop should be conducted in the open with the full participation of the development team and with full visibility to the community. No backroom cooked up code. Thoughts? Greg
