Re: User Email Account

I think what Justin is saying is that it's going to seem like uncomfortable chaos for a bit, but will eventually settle down into a better state. >From what I know about well-functioning teams, that seems right. Form, storm, norm, perform.

Re: User Email Account

Hi, Some previous discussions for you consideration: https://lists.apache.org/thread.html/a1811e65e31dbd551b2da7429a7617359523cbc5c969827c9a908a6a%40%3Cgeneral.incubator.apache.org%3E https://lists.apache.org/thread.html/e7be60b4fa3086aaa30eb2b09ec990d807bd8cc03256829fe6651276%401283929842%40%3Cge

Re: User Email Account

I'm ok with the way it is right now– once NuttX graduates from incubator status we can make changes if needed. I understand Justin's points about the utility of keeping the lists all in one for now. cheers adam On Wed, Dec 25, 2019 at 3:54 PM Gregory Nutt wrote: > > > +1 > > > > especially for

Re: User Email Account

Hi, Most of those are not current incubating projects. Some of them did not become to level projects. Just about all did not start with user lists. Creating a seperate user list this early in previous incubating projects has slowed or hindered their community growth. You want users involved so tha

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Wed, Dec 25, 2019 at 6:45 PM Justin Mclean wrote: > > People on this list have indicated that they use NuttX released with > Apache SVN. > > The releases are placed in a ASF SVN system to be distributed by the > mirror system yes. I think Greg means that users are getting the release tarball

Re: Why the text displayed by SSD1306 / I2C is reversed along the vertical axis

Thanks, I found a solution. I used the wrong driver chip! BR NiiJyeni > 2019年12月24日 下午4:48，Sebastien Lorquet 写道： > > hello > > IIRC the config menus allow you to flip the display direction. Did you have a > look over there? > > Sebastien > > Le 24/12/2019 à 08:39, Nii Jyeni a écrit : >> Hi~ >

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 acco

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

As long as you stick to git only features you can have everyone work on it, so branch bases workflow would be best. You can still use GitHub only features but just don’t make them compulsory. WRONG! Not also that some more advanced features or options for GItHub that have been discussed he

Re: User Email Account

On 12/25/2019 6:22 PM, Gregory Nutt wrote: On 12/25/2019 5:58 PM, Justin Mclean wrote: Hi, I think the idea has been nix'ed by Justin.  So I am not going to pursue this.  Others may want to buck the system, but I have already caused enough problems. How so? We already have a seperate comm...@

Re: User Email Account

Basic we are making the decision to screw the end user in favor of rules and process.  I concede that and will not bring it up again. It is not just this.  We are advocating other things that effect the end-user and the usability of NuttX.  It is sad, because NuttX has always been a user-ori

Re: User Email Account

On 12/25/2019 5:58 PM, Justin Mclean wrote: Hi, I think the idea has been nix'ed by Justin. So I am not going to pursue this. Others may want to buck the system, but I have already caused enough problems. How so? We already have a seperate comm...@nuttx.apache.org list which is working fin

Re: User Email Account

Hi, > I think the idea has been nix'ed by Justin. So I am not going to pursue > this. Others may want to buck the system, but I have already caused enough > problems. How so? We already have a seperate comm...@nuttx.apache.org list which is working fine from what I can see. 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, peopl

Re: User Email Account

+1 especially for the commits and notifications, so they can be filtered. I'm ok with separate lists for commits and notifications, I just want them to be separate from the lists meant for humans :) I think the idea has been nix'ed by Justin.  So I am not going to pursue this.  Others may w

Re: User Email Account

+1 especially for the commits and notifications, so they can be filtered. I'm ok with separate lists for commits and notifications, I just want them to be separate from the lists meant for humans :) On Wed, Dec 25, 2019 at 9:01 AM Alin Jerpelea wrote: > +1 > this will remove the noise for mos

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi, > The majority of users do not use GIT at all. NuttX distributions are SCM > neutral (all GIT information has been used). User and contributors are different (but overlapping) groups, I believe we were talking about contributors here. Users will be using the releases which are available

Re: Podling Nuttx Report Reminder - January 2020

Thank you Greg, I appreciate it. > That’s a good start, but a few sections are missing and a little more detail > is needed in a few places. What sections are missing? I took the template from the incubator. Or do you mean content is missing? If that's the case, yes, there are quite some gaps. Th

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

As long as you stick to git only features you can have everyone work on it, so branch bases workflow would be best. You can still use GitHub only features but just don’t make them compulsory. WRONG! Not also that some more advanced features or options for GItHub that have been discussed he

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 in

Re: Podling Nuttx Report Reminder - January 2020

HI, > I put in a draft to start with > (https://cwiki.apache.org/confluence/display/NUTTXTEST/January+2020) That’s a good start, but a few sections are missing and a little more detail is needed in a few places. 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, b

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

This page explicitly says ‘your project’. For contributors other than committers, especial it is not their projects, the repo is not writable to them, and how can they create branches on the repo? David Sidrane 于2019年12月26日 周四03:18写道： > Hi Duo, > > > What is the well known and documented WF of g

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi, As long as you stick to git only features you can have everyone work on it, so branch bases workflow would be best. You can still use GitHub only features but just don’t make them compulsory. Not also that some more advanced features or options for GItHub that have been discussed here e.g

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

David Sidrane 于2019年12月26日 周四03:18写道： > Hi Duo, > > > What is the well known and documented WF of github? I've never heard > about > >it. Please be specific. > > https://guides.github.com/introduction/flow/ > > All I add on top of the above is the naming to keep it easy for me to > remember where

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 inst

Re: Mentor SGA Question

Hi, > The incubator-nuttx project contains only a small amount of 3rd part > software. The incubator-nuttx-apps repository contains considerably more. > This is not raw, 3rd party code but highly modified and highly adapted code. > Third party copyrights are retained out of respect respect

Re: User Email Account

Hi, The user list is usually only created once a project graduates, but sometimes it is before if there too much noise. Some reasons for not creating a user account so early: - User questions tend to be ignored if they are on a seperate list - Users don’t participate in other activities so you m

Re: Podling Nuttx Report Reminder - January 2020

It’s a good idea to work on the report in the open, you can do this this wiki [1] or this mailing list, it’s also a good idea to work on it well before the due date. Your first report is due 1st January. I put in a draft to start with (https://cwiki.apache.org/confluence/display/NUTTXTEST/Ja

Re: Podling Nuttx Report Reminder - January 2020

Hi, > > It’s a good idea to work on the report in the open, you can do this this wiki > [1] or this mailing list, it’s also a good idea to work on it well before the > due date. Your first report is due 1st January. I put in a draft to start with (https://cwiki.apache.org/confluence/display/NUTT

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 participat

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 inter

Re: Accessing Apache GitHub as a Committer

On Wed, Dec 25, 2019 at 10:53 AM Gregory Nutt wrote: > > We need to have a clone of this page in our Confluence: > https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer > In general I would like to have some kind of section for on-boarding for new committers

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

That is a great question. I am not the one to answer it. Perhaps one of the people who cannot get to github can answer it for you. David -Original Message- From: Nathan Hartman [mailto:hartman.nat...@gmail.com] Sent: Wednesday, December 25, 2019 12:30 PM To: dev@nuttx.apache.org Subject:

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Wed, Dec 25, 2019 at 2:18 PM David Sidrane wrote: > Github issues and PR work so well together and are cross linked > auto-magically. Justin points out that some people cannot use GitHub and Apache strives to include everyone. I have no opposition to using GitHub and the tools and conven

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi Duo, > What is the well known and documented WF of github? I've never heard about >it. Please be specific. https://guides.github.com/introduction/flow/ All I add on top of the above is the naming to keep it easy for me to remember where the contributions was from and where it will go. (I have

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

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

What is https://codersrank.io/ ? I am not failure with it. Do you have a screen shot that relates to this discussion? -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Wednesday, December 25, 2019 7:58 AM To: dev@nuttx.apache.org Subject: Re: Software release life

Mentor SGA Question

Hi, Mentors, The incubator-nuttx project contains only  a small amount of 3rd part software.  The incubator-nuttx-apps repository contains considerably more.  This is not raw, 3rd party code but highly modified and highly adapted code.  Third party copyrights are retained out of respect respe

[GitHub] [incubator-nuttx] wingunder opened a new pull request #9: Fixed STM32L4_NUSART for STM32L433XX.

wingunder opened a new pull request #9: Fixed STM32L4_NUSART for STM32L433XX. URL: https://github.com/apache/incubator-nuttx/pull/9 STM32L4_NUSART was set to 4. The spec at https://www.st.com/resource/en/datasheet/stm32l433cc.pdf states the following on page 1: - 4x USARTs (I

Re: User Email Account

+1 this will remove the noise for most users On Wed, Dec 25, 2019, 17:27 David Sidrane wrote: > +1 > > >* notificati...@nuttx.apache.org: For all notifications from GitHub, > GitBox, Confluence, Jira, etc., etc., etc. > > But I would separates commits@ from notifications@ > > I made similar sugg

Re: Accessing Apache GitHub as a Committer

Done. Hopefully the links are correct some require being a commiter to access so I pattern matched. https://cwiki.apache.org/confluence/display/NUTTXTEST/Accessing+Apache+GitHub+as+a+Committer Great!  Thank you.  I fixed a couple of copy-paste errors: OpenWhisk->NuttX

Re: Accessing Apache GitHub as a Committer

Done. Hopefully the links are correct some require being a commiter to access so I pattern matched. https://cwiki.apache.org/confluence/display/NUTTXTEST/Accessing+Apache+GitHub+as+a+Committer --Brennan On Wed, Dec 25, 2019, 7:53 AM Gregory Nutt wrote: > We need to have a clone of this page in

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.  Wi

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Doesn't do any good at social bragging sites like https://codersrank.io/ On 12/25/2019 9:47 AM, David Sidrane wrote: Even on a squashed merge there is traceability back to the PR and therefore ALL the history will be on the mailing list and publically available on GH. This is why a rebase work

Accessing Apache GitHub as a Committer

We need to have a clone of this page in our Confluence: https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Even on a squashed merge there is traceability back to the PR and therefore ALL the history will be on the mailing list and publically available on GH. This is why a rebase work flow has to stop after review. (With some exceptions) but we always attribute to the Authors -Original Message

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Branch protection https://help.github.com/en/github/administering-a-repository/about-protected-branches About protected branches. Protected branches ensure that collaborators on your repository cannot make irrevocable changes to branches. Enabling protected branches also allows you to enable othe

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

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

+1 -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Wednesday, December 25, 2019 6:41 AM To: dev@nuttx.apache.org Subject: Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer) > Why does the authors matter. There i

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 Da

RE: User Email Account

+1 >* notificati...@nuttx.apache.org: For all notifications from GitHub, GitBox, Confluence, Jira, etc., etc., etc. But I would separates commits@ from notifications@ I made similar suggestions but it appears flood has swept away the key points. -Original Message- From: Nathan Hartman

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:

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

-Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Wednesday, December 25, 2019 6:55 AM To: dev@nuttx.apache.org Subject: Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer) On Wed, Dec 25, 2019 at 9:55 PM David

Re: User Email Account

(By the way, I expect that once the dust settles, we have consensus on a workflow, and we "find our groove," the volume of organizational emails should drop substantially and most emails on dev will center around technical discussions once again. But it might take a while...) I expect it to d

Re: User Email Account

On Wed, Dec 25, 2019 at 9:34 AM Gregory Nutt wrote: > > There have been quite a few NuttX users who have been put of by the > volume and content of emails on this list. December is not quite over > and there have been close to 850 emails so far this month. And the > majority of the community is

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi Duo, I am sorry I broke my own rule. I should have defined it. BD: Benevolent dictator for life (BDFL) is a title given to a small number of open-source software development leaders, typically project founders who retain the final say in disputes or arguments within the community. On 2019/

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Wed, Dec 25, 2019 at 9:55 PM David Sidrane wrote: > > Hi Xiang, > > On 2019/12/25 05:36:14, Xiang Xiao wrote: > > Yes, I agree that we shouldn't make the workflow too hard to scare > > people for contribution. > > NuttX isn't a new project, it's open source for more than ten years > > and has

Re: User Email Account

Definitely a good idea. I believe David also suggested that gitbox messages will be redirected to their own pr@ mailing list. There is just too much traffic in dev@ I tried to create the email account at https://selfserve.apache.org/, but it says I have can't do that because I am not a PMC

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

If they are related / dependent on each other, then I think those kinds of patchsets should be encapsulated in one branch. That would work fine provided that the branch is not squashed to master.  That loses authorship of individual contributions.

Re: User Email Account

Definitely a good idea. I believe David also suggested that gitbox messages will be redirected to their own pr@ mailing list. There is just too much traffic in dev@ On Wed, Dec 25, 2019 at 2:38 PM 张铎(Duo Zhang) wrote: > > +1 on a user@nuttx mailing list. > > Gregory Nutt 于2019年12月25日周三 下午10:34写

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Why does the authors matter. There is no reason a patchset or PR needs to be squashed into a single commit, they just should not be broken along the way. It does not matter to the project.  But it matters very much to some contributors.  Especially young or newbie contributors who see this a

Re: User Email Account

+1 on a user@nuttx mailing list. Gregory Nutt 于2019年12月25日周三 下午10:34写道： > There have been quite a few NuttX users who have been put of by the > volume and content of emails on this list. December is not quite over > and there have been close to 850 emails so far this month. And the > majority

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

David Sidrane 于2019年12月25日周三 下午9:55写道： > Hi Xiang, > > On 2019/12/25 05:36:14, Xiang Xiao wrote: > > Yes, I agree that we shouldn't make the workflow too hard to scare > > people for contribution. > > NuttX isn't a new project, it's open source for more than ten years > > and has a mature workfl

User Email Account

There have been quite a few NuttX users who have been put of by the volume and content of emails on this list.  December is not quite over and there have been close to 850 emails so far this month.  And the majority of the community is only interested is discussion technical issues and do not e

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Pardon me, what is a BD model? I do not get your point why requiring users to send a patch or open a PR against master will hindered the community growth? Or you say #3 and #4? These are what we want to change. Thanks. David Sidrane 于2019年12月25日周三 下午9:55写道： > Hi Xiang, > > On 2019/12/25 05:36:1

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi Xiang, On 2019/12/25 05:36:14, Xiang Xiao wrote: > Yes, I agree that we shouldn't make the workflow too hard to scare > people for contribution. > NuttX isn't a new project, it's open source for more than ten years > and has a mature workflow, the whole community is already familiar > with it

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

> For me on HBase, this depends on lots of things. If it is only a typo then > I will merge it immediately. If it is a simple bug fix, I will wait a bit > long and if some committers are familiar with this part, I will try to ask > their opinions. And if this is a very big new feature, sometimes pe

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

What I mean is that, nobody wants its patch to be reverted right? So you will find a proper way to archive this. There is no straight forward rule on how much time to wait. For me on HBase, this depends on lots of things. If it is only a typo then I will merge it immediately. If it is a simple bug

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Wed, Dec 25, 2019 at 2:30 PM 张铎(Duo Zhang) wrote: > > Xiang Xiao 于2019年12月25日周三 下午1:36写道： > > > Yes, I agree that we shouldn't make the workflow too hard to scare > > people for contribution. > > NuttX isn't a new project, it's open source for more than ten years > > and has a mature workflow,

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi, > Usually one committer is enough, the only different is that, if the patch > is proposed by a committer, then you need another committer to approve it. > We need to make sure that a patch has to be reviewed by a committer other > than the author. This depends on the projects, some don’t have