State of Bitbucket Repsitories

I am continuing to accept changes to the (deprecated) NuttX repositories on Bitbucket.org.  Can someone please inform me when INFRA is ready to instantiate the Apache Github repositories?  I will then make the the Bitbucket repositories read-only and prohibit forks and PRs.  Let's try to make t

Re: State of Bitbucket Repsitories

I can see this INFRA issue for NuttX: https://issues.apache.org/jira/browse/INFRA-19542 But that does not talk about creating a gitbox repo. Justin, do we need to create a new INFRA ticket? -Flavio > On 10 Dec 2019, at 15:25, Gregory Nut

Re: State of Bitbucket Repsitories

On Tue, Dec 10, 2019 at 9:34 AM Gregory Nutt wrote: > I am continuing to accept changes to the (deprecated) NuttX repositories > on Bitbucket.org. Can someone please inform me when INFRA is ready to > instantiate the Apache Github repositories? I will then make the the > Bitbucket repositories

Re: State of Bitbucket Repsitories

I am continuing to accept changes to the (deprecated) NuttX repositories on Bitbucket.org.  Can someone please inform me when INFRA is ready to instantiate the Apache Github repositories?  I will then make the the Bitbucket repositories read-only and prohibit forks and PR

Re: State of Bitbucket Repsitories

On Tue, Dec 10, 2019 at 10:16 AM Gregory Nutt wrote: > > >> I am continuing to accept changes to the (deprecated) NuttX repositories >> on Bitbucket.org. Can someone please inform me when INFRA is ready to >> instantiate the Apache Github repositories? I will then make the the >> Bitbucket repos

Re: State of Bitbucket Repsitories

Hi, just wanted to mention that there's also an automatic mirror on Gitlab at: https://gitlab.com/nuttx Best, Matias On Tue, Dec 10, 2019, at 12:24, Nathan Hartman wrote: > On Tue, Dec 10, 2019 at 10:16 AM Gregory Nutt wrote: > > > > > >> I am continuing to accept changes to the (deprecated) Nu

Re: State of Bitbucket Repsitories

just wanted to mention that there's also an automatic mirror on Gitlab at: https://gitlab.com/nuttx There are dozens of mirrors of the NuttX Bitbucket repositories. Google nuttx+mirror to see some of them. An alternative disposition of the Bitbucket repositories might be to make them manu

Re: State of Bitbucket Repsitories

On Tue, Dec 10, 2019 at 10:43 AM Gregory Nutt wrote: > > > > just wanted to mention that there's also an automatic mirror on Gitlab at: > > > > https://gitlab.com/nuttx > > > There are dozens of mirrors of the NuttX Bitbucket repositories. Google > nuttx+mirror to see some of them. > > An alternat

Re: State of Bitbucket Repsitories

I think we need to ask our mentors what is the generally accepted thing to do with the project's earlier incarnation. 100% agreed.  We need guidance.

Re: State of Bitbucket Repsitories

I don't think you need to get rid of the earlier incarnation of the project. As per the ASF legal documentation, we need to make sure that the copyright holders sign either CLAs or software grants: https://www.apache.org/foundation/how-it-works/legal.html

Re: State of Bitbucket Repsitories

I don't think you need to get rid of the earlier incarnation of the project. ... Skimming the documents, it appears that ASF has no position on the disposition of the earlier incarnations of the.  I think that maintaining them as mirrors of the Apache code would be best option for the comm

Re: State of Bitbucket Repsitories

I don't think you need to get rid of the earlier incarnation of the project. ... Skimming the documents, it appears that ASF has no position on the disposition of the earlier incarnations of the.  I think that maintaining them as mirrors of the Apache code would be best option for the co

Re: [Test] Joined

[Test] Joined Verstuurd vanaf mijn iPhone > Op 10 dec. 2019 om 01:00 heeft david.sidr...@gmail.com het volgende > geschreven: > >  [Test] Joined > > Is it alive? > > David

Re: State of Bitbucket Repsitories

Hi Greg, On 12/10/19, Gregory Nutt wrote: >> >> Certainly there are other forks of NuttX all over the internet (not >> mirrors, but usually older clones), but I think people would always >> want to go to the authoritative source and currently the world >> believes that the Bitbucket repository is

Re: State of Bitbucket Repsitories

The right bitbucket url for hooks: https://www.atlassian.com/git/tutorials/git-hooks On 12/10/19, Alan Carvalho de Assis wrote: > Hi Greg, > > On 12/10/19, Gregory Nutt wrote: >>> >>> Certainly there are other forks of NuttX all over the internet (not >>> mirrors, but usually older clones), but

Re: State of Bitbucket Repsitories

The right bitbucket url for hooks: https://www.atlassian.com/git/tutorials/git-hooks I don't think I can trigger any scripts in the Bitbucket repository based on events in a Github repository. There is a mirror plug-in for Bitbucket: https://marketplace.atlassian.com/apps/1211351/reposit

Re: State of Bitbucket Repsitories

On Tue, Dec 10, 2019 at 1:07 PM Gregory Nutt wrote: > > If we are smart, we can tag the initial > > Apache import to make that easier. > +1 to tagging the initial import Nathan

RE: State of Bitbucket Repsitories

The history will be intact no matter where it is. It will remain BSD until the license changes. The change should be on a branch than a single commit. Then it is a knife edge -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Tuesday, December 10, 2019 7:44 AM To: de

Candidate Committers

Given that we want to open up the first committer spots to all significant NuttX contributors, I made a list.  I went through the top 20 or so all time contributors to NuttX and made a list of potential committers.  I have excluded already identified initial committers.  I have also excluded an

Re: Candidate Committers

HI Greg, I think these guys are good options and it is very nice to see them aboard! BR, Alan On 12/10/19, Gregory Nutt wrote: > Given that we want to open up the first committer spots to all > significant NuttX contributors, I made a list. I went through the top > 20 or so all time contribut

Re: Candidate Committers

Dear Greg, Thanks for adding me to the list. On 2019/12/11 9:41, "Gregory Nutt" wrote: Given that we want to open up the first committer spots to all significant NuttX contributors, I made a list. I went through the top 20 or so all time contributors to NuttX and made a list of

Re: Candidate Committers

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写道：

Re: Candidate Committers

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. Okay... thanks!  Still learning how things work. Greg

Re: Candidate Committers

Hi, > Given that we want to open up the first committer spots to all significant > NuttX contributors, I made a list. I went through the top 20 or so all time > contributors to NuttX and made a list of potential committers. I have > excluded already identified initial committers. I have also

Update LittleFS to version 2.1.4

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