As Nathan Hartman is an ASF member now, you could ask to join the IPMC,
then we could have 2 binding votes when releasing...
And let me contact our champion, he has been really busy recently...
Thanks.
Byron Ellacott 于2021年5月8日周六 下午1:28写道：
> +1 with caveat that I need to backport the compiler
We have enough binding votes from IPMC now, so let's close the vote and
finish the release?
Thanks.
张铎(Duo Zhang) 于2021年5月20日周四 下午4:17写道：
> As Nathan Hartman is an ASF member now, you could ask to join the IPMC,
> then we could have 2 binding votes when releasing...
>
> And l
Skimming our download page, I think the problem is that we use
downloads.apache.org directly on the download page, which is not allowed.
We should use the closer.lua script, this is an example from the hadoop
download page
https://hadoop.apache.org/releases.html
https://www.apache.org/dyn/closer
This is the PR for fixing NuttX download page
https://github.com/apache/incubator-nuttx-website/pull/59
ling miao 于2021年9月16日周四 下午3:06写道：
> Thanks Justin,
>
> I changed the Doris Download page.
> This is the PR: https://github.com/apache/incubator-doris/pull/6677. It
> will be merged later ~
>
We also need to fix the KEYS file link.
-- Forwarded message -
发件人： Justin Mclean
Date: 2021年9月17日周五 上午6:26
Subject: [MENTORS] Download pages and links to KEY files
To:
HI,
Some projects that may have an issue with the KEYS file:
Brpc
Crail
Doris
hHiveMall
Livy
Milagro
MXNet
N
It depends. We need to start a discuss thread on the incubator-general
mailing list to see if IPMC members have any concerns.
Alin Jerpelea 于2022年2月10日 周四01:35写道：
> How long does infra + paperwork take?
> When we are ready with everything I will start the 11.0 release cycle
>
> Best regards
> Ali
This is all the directories in the LICENSE file, and after removing the
files under these directories, I finally get a list with 136 files.
We are very close to finish the license work now :)
张铎(Duo Zhang) 于2022年4月14日周四 20:51写道：
> Oh I must have made some mistakes in the scripts...
>
>
Oh I forgot to paste the directory list...
fs/nfs
fs/spiffs
libs/libc/math
libs/libc/lzf
include/lzf
drivers/video/ov2640
libs/libc/machine/arm/armv8-m
libs/libc/wchar
libs/libc/wctype
wireless/bluetooth
tools/size_report
drivers/wireless/spirit/
arch/arm/src/nrf52/sdk-nrfxlib
张铎(Duo Zhang) 于
m/apache/incubator-nuttx/blob/master/LICENSE#L265
>
> and the others that are not related to a specific folder
>
> Thanks
> Alin
>
>
> On 2022/04/14 13:29:35 "张铎(Duo Zhang)" wrote:
> > What I posted in the email content are the directories listed in the
> &
2022年4月19日周二 02:03写道：
> On Thu, Apr 14, 2022 at 10:39 AM 张铎(Duo Zhang)
> wrote:
> >
> > Ah, then let me just post them as the content. I've removed several files
> > from the list by the information you provided. And I suggested that when
> > you specify a lib
ublish this release, it is a direct sign that NuttX could
> graduate
> > as a TLP :)
> >
> > Nathan Hartman 于2022年4月19日周二 02:03写道：
> >
> > > On Thu, Apr 14, 2022 at 10:39 AM 张铎(Duo Zhang)
> > > wrote:
> > > >
> > > > Ah, then let
-- Forwarded message -
发件人： 张铎(Duo Zhang)
Date: 2022年6月5日周日 16:36
Subject: Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]
To:
I could verify the gpg signature
gpg --verify apache-nuttx-10.3.0-incubating.tar.gz.asc
> gpg: 假定被签名的数据在‘apache-nuttx-10.
Seems the incubating project must have a DISCLAIMER file, which indicates
that it is still 'incubating', and the ASF does not guarantee that it has
no license issues. Not a big problem, we can remove it after we graduate as
a TLP.
Alin Jerpelea 于2022年6月5日周日 17:13写道：
> Hi Duo Zha
nd then a vote thread, and then you are a TLP :)
Good luck.
Alin Jerpelea 于2022年6月5日周日 21:08写道：
> ok. What else is needed for graduation?
> Should I add the DISCLAIMER back and start the RC3 vote?
> Thanks
> Alin
>
> On Sun, 5 Jun 2022, 14:58 张铎(Duo Zhang), wrote:
>
&g
Let's first make sure we have done all the things in the check list?
Abdelatif Guettouche 于2022年7月13日周三 19:40写道：
> It would be nice to hear from the mentors or anyone from the IPMC.
>
> On Wed, Jul 13, 2022 at 12:07 AM Nathan Hartman
> wrote:
> >
> > Hi all,
> >
> > As this [DISCUSS] thread has
+1
Masayuki Ishikawa 于2022年10月20日周四 07:31写道：
>
> +1
> Let's move forward!
>
>
> On Wed, Oct 19, 2022 at 9:07 PM Alan C. Assis wrote:
>
> > +1
> >
> > Please go ahead Nathan!
> >
> > BR,
> >
> > Alan
> >
> > On 10/19/22, David Sidrane wrote:
> > > +1 - The time has come.
> > >
> > > David
> > >
+1: Apache NuttX is ready to graduate to TLP
David Sidrane 于2022年10月21日周五 23:08写道：
>
> +1: Apache NuttX is ready to graduate to TLP
>
> David
>
> On 2022/10/21 12:46:47 Nathan Hartman wrote:
> > Dear Apache NuttX Community,
> >
> > Following the [DISCUSS] thread which has gone 72 hours without an
Hi, Greg. In ASF, usually the discussion about the committer candidates
should happen in the private@nuttx mailing list...
And also, the later vote for the new PPMC members and committers should
also happen in the private mailing list.
Thanks.
Ishikawa, Masayuki (SHES) 于2019年12月11日周三
上午9:05写道：
We could still use bitbucket I think.
Xiang Xiao 于2019年12月11日周三 下午2:09写道：
> Many feature is added, here has the detailed information:
> https://github.com/ARMmbed/littlefs/releases
>
> Should we use dev mail list for patch until the github workflow is ready?
>
> Thanks
> Xiang
>
Things are a bit different in ASF as we can use jenkins instead of travis
ci.
If the code is ready on github, I could help setting up the jenkins job to
pull PR as I've done this for other ASF projects in the past.
Thanks.
Xiang Xiao 于2019年12月16日周一 上午11:35写道：
> Yes, GitHub has the standard wor
git clone --bare
cd
git push --porcelain --mirror
I've done some migrations recently with the commands above.
Justin Mclean 于2019年12月18日周三 下午2:05写道：
> HI,
>
> I think this can be done as simple as using these two commands, but I’ve
> not tried it before.
> git clone —mirror oldrepo
> git p
For HBaseCon, usually the discussion will first be made in the private
mailing list, to get enough PMC members support, and then you can post it
in the public mailing list to get the PC members for reviewing and
accepting the submissions, and also a PMC member must send an email to the
trademarks m
In general, all discussion should happen on the infrastruct hosted by ASF,
like mailing-list, JIRA, etc. This is what I have learned in the past.
And when GitHub becomes popular, the solution is to send the comments on
GitHub to a special mailing list of the project to record them on the
infrastruc
The sync is bidirection.
See this page:
https://gitbox.apache.org/setup/
On https://id.apache.org/ , fill your github username and then there will
be an invitation sent to you on github to let you join the apache
organization on github. And once the MFA status on
https://gitbox.apache.org/setup/
different git repos and test them together.
Thanks.
张铎(Duo Zhang) 于2019年12月21日周六 下午12:19写道：
> The sync is bidirection.
>
> See this page:
>
> https://gitbox.apache.org/setup/
>
> On https://id.apache.org/ , fill your github username and then there will
> be an invitatio
together from existing discussion (if you could
> find it) would be a simple job of an hour or so, if you don't get
> murdered in your sleep for doing so.
>
> Greg
>
> On 12/20/2019 10:46 PM, Brennan Ashton wrote:
> > On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang)
> wrote:
For opening a PR, usually you can just fork the repo and create a branch in
the forked repo, and then open a PR. It is not necessary to create a branch
in the original repo only for a PR.
You can open a branch for a big feature, which usually needs a lot of
commits and also a very long time before
I think we should create a mailing list called commits@nuttx or something
else and let the forwarded github message go there...
GitBox 于2019年12月21日周六 下午11:16写道：
> Apache9 commented on issue #1: imxrt fixes
> URL:
> https://github.com/apache/incubator-nuttx/pull/1#issuecomment-568188369
>
>
>
+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 于2019年12月22日周
y have a commits@nuttx mailing list.
>
>
> On Sat, Dec 21, 2019 at 3:23 PM 张铎(Duo Zhang)
> wrote:
> >
> > I think we should create a mailing list called commits@nuttx or
> something
> > else and let the forwarded github message go there...
> >
> >
I think a PR is more like an issue rather than a commit?
Justin Mclean 于2019年12月22日周日 下午12:40写道：
> HI,
>
> > So if no objections, let's file an infra issue to create an issues@nuttx
> > mailing list and also forward the notification there?
>
> We can create one ourselves, why why have an issues@
You can see that we have already sent the discussions on the PR to the dev
list, and based on the activity of nuttx community, it will soon become
noisy. I agree that we could keep the new PR nofitication to dev list, but
I do not think we should send the comments to dev list.
Justin Mclean 于2019
Please send an email to dev-subscr...@nuttx.apache.org for subscribing.
Nii Jyeni 于2019年12月23日周一 上午5:25写道：
> Hi,
> I want to contribute to Nuttx,
> I want to share some idea to Nuttx.
>
> BR
> NiiJyeni
>
For our Chinese people we do not think starting working when the
requirements are not very clear is a big risk, this is what happens every
day here. You can not plan everything so just have a try, if it does not
work then just drop it and retry, no harm :)
And in my experience, if we can not agree
first.
Thanks.
David Sidrane 于2019年12月23日周一 下午8:58写道：
> Hi Duo,
>
> Well said and I am all for it.
>
> Two questions:
>
> 1 Who will apply the patches?
> 2 Can we use and merge a PR that has been reviewed?
>
> David
>
>
> -Original Message-
> Fro
+1.
I think it is reasonable to just keep the original workflow as is for now,
as we still need to make progress on the project. I do not think the ASF
will 'hate' this, you can not graduate if you keep doing things like this,
that's all, fair enough.
And on the workflow part, I suggest you start
I do not think it is a big deal to force the base branch for a PR. You are
free to choose the way you like, just tell users which branch to use when
creating a PR.
In ASF, like Hadoop and HBase, maser is the dev branch and by default all
PR must be created against the master branch. There are user
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, the whole community is already familiar
> with it.
> Let me summar
an one-for-all rule. NuttX community
has its own culture, and the ‘rule’ will be set up though practice.
Thanks.
Xiang Xiao 于2019年12月25日 周三19:50写道：
> On Wed, Dec 25, 2019 at 2:30 PM 张铎(Duo Zhang)
> wrote:
> >
> > Xiang Xiao 于2019年12月25日周三 下午1:36写道：
> >
> > > Ye
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
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
+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
sues and PR work so well together and are cross linked
> auto-magically.
>
> [1]
>
> https://help.github.com/en/github/managing-your-work-on-github/about-project-boards
>
>
>
> David
>
>
> -Original Message-
> From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com]
heel or use disjoint
> tools (I have used Jira with github - To me, there was not value add that
> made it more it compelling, then issues and Project board in github[1]).
>
> Github issues and PR work so well together and are cross linked
> auto-magically.
>
> [1]
>
> https:
Hey David, could you please explain the above questions a bit?
Since you want to create PR branches at the official repo, then how could a
contributor other than committer contribute code? He/she just does not have
the permission to create a branch.
Thanks.
David Sidrane 于2019年12月26日周四 下午4:45写道
-->
>
> No Write | Have Write access
> Access | Do PR in upstream
> Do PR | on Branches
> Against|
> Upstream|
> On|
> Branches |
> in own |
> account |
>
>
> David
>
> -Original Message-
>
epo like a semaphore and a point of collaboration. Think 24
> hr a day hand offs to get a pr in. We can all help get in a PR.
>
What do you mean by 'help get in a PR'?
>
> David
>
> -Original Message-
> From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com
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 sho
> /Tests to thell them the PR is ready (in our case to Fly) and they
> test
> and put results in PR
> BUT they can also fix something, if need be, and PUSH commits.
> No one is blocked and it is a team effort.
>
> [1]
>
> https://www.google.com/search?q=how+to+
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 v
Yes, feature branch is another story, but I still need to say that, we
should not just exclude normal contributors. They do not have the
permission to push to a feature branch either...
Gregory Nutt 于2019年12月27日 周五07:52写道：
>
> > Still, not every contributors are committers, they do not have the
>
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
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
File an infra issue?
And git-wip-us has been deprecated, now we use gitbox.
https://gitbox.apache.org/repos/asf/incubator-nuttx
https://gitbox.apache.org/repos/asf/incubator-nuttx-apps
Xiang Xiao 于2019年12月27日周五 下午4:59写道：
> https://git-wip-us.apache.org/repos/asf?p=incubator-nuttx.git
> It's
.apache.org/thread.html/98ddb6fcf5a744f3b65f81d850cb535764f16fa207fd883c557fbf4f%40%3Cdev.nuttx.apache.org%3E
>
> David
>
>
>
> -Original Message-
> From: Nathan Hartman [mailto:hartman.nat...@gmail.com]
> Sent: Thursday, December 26, 2019 7:34 PM
> To: dev@nuttx.apache.org
Again, think of you are a contributor, not a commiter. Not all contributors
are committers, you should not use a different (official) workflow
comparing to them. That's my point.
David Sidrane 于2019年12月27日周五 下午10:59写道：
> Hi Greg,
>
> I have used Bit bucket and Github and others SCM. I have had m
Hi, Justin
I think we will just let the gitbox forwarded emails to go to another
mailing list, which we can see on GitHub? No information lost.
And the problem is, actually we are answering the questions on GitHub but
then the answer is sent to this mailing list again with a hard to read
format..
But I think posting so many 'hard to read' emails to the mailing list will
hurt user experience and cause users to leave...
Actually for a committer, or a long term contributor who is familiar with
the community, he/she can just use a filter to filter these emails out,
this is what I have done for
For me I suggest we start with GitHub issues.
For problem #1, the cross repo PRs, I think it is fine to have only one
issue in the main repo? We can reference multiple PRs in an issue and the
PRs could come from other repos.
And for problem #2, once the user sends the patch to this mailing list,
A possible rule is to not make new nxstyle issues.
You can run nxstyle twice, before the patch and after the patch, and check
the difference to see if there are new violations.
It may not be accurate but basiclly works, and committers do not need to
check it manually to find out whether the patch
I think we could ask Infra to set some 'protected' branches, which means we
can not do force push on these branches, but I'm not sure if it is possible
to forbid a simple push...
In my experience, I've pushed wrong commits to the repo when developing
projects in ASF, and usually the solution is to
Hi, NuttX community, I'm Duo Zhang, I would like to self nominate to be a
mentor of Apache Nuttx, since I'm the only person among 3 binding votes who
have successfully built NuttX in the 9.0.0 vote thread. Just joking :)
Last year when Greg and David came to China, we talked about joini
First, congratulations on the 9.1.0 release! Our community has done a great
job.
To be honest, it is not easy to get enough votes from IPMC for a OS project
in ASF, so I asked help from some members I know(yes, all Chinese, you can
see their name format).
They all mentioned that the license heade
es and fix headers? So far it's just
> been Brennnan and me working on this (If I missed anyone, please let me
> know!)
>
> cheers
> adam
>
> On Thu, Jul 23, 2020 at 1:42 AM 张铎(Duo Zhang)
> wrote:
>
> > First, congratulations on the 9.1.0 release! Our communit
IMO we should at least have some numbers about the current status first,
i.e, how many files can be cleared directly, how many can not, etc.
With the numbers in hand, then we can decide whether it is possible for us
to finish the work, and how to finish the work. Even if we want to reach
out for h
OK, there is a sub page, about the status of a module at March
https://cwiki.apache.org/confluence/display/NUTTX/Analysis+March+2020
Let's try to do this on the whole project to get some numbers?
Thanks.
张铎(Duo Zhang) 于2020年7月27日周一 上午11:32写道：
> IMO we should at least have some numbe
Hi Secretary,
Here is the signed SGA for donating the source files owned by Xiaomi of
Apache NuttX[1].
Please see the attached file.
You may find out that the copyright of these files is 'Pinecone Inc.'.
'Pinecone Inc.' is a wholly-owned subsidiary of Xiaomi so there is no
problem.
Best regards
I do not think there is zero progress as at least I’ve signed a SGA to
change all the files from Xiaomi to Apache License.
For the work on cleaning the license for other files, I could ask Peter and
Xiang Xiao again to let them be more aggressive on this task. It is the
long holiday in China, will
68 matches
Mail list logo
