You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by da...@gmail.com on 2019/12/09 23:05:25 UTC
[TEST] Joined
[TEST] Joined
Hi Group,
Is this thing live yet?
*David Sidrane*
*David.Sidrane@gmail.com *
Re: State of Bitbucket Repsitories
Posted by Flavio Junqueira <fp...@apache.org>.
I can see this INFRA issue for NuttX:
https://issues.apache.org/jira/browse/INFRA-19542 <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 Nutt <sp...@gmail.com> 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 read-only and prohibit forks and PRs. Let's try to make that transition as "knife-edge" as possible.
>
> Greg
>
>
RE: State of Bitbucket Repsitories
Posted by David Sidrane <Da...@nscdg.com>.
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:spudaneco@gmail.com]
Sent: Tuesday, December 10, 2019 7:44 AM
To: dev@nuttx.apache.org
Subject: 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 manual mirrors of the Apache repositories. AFAIK Bitbucket
does not support automated mirroring without a plug-in. But periodic
manually mirroring of the Apache repositories would help by assuring
that the Apache licensed code is pushed out to all NuttX mirrors as well.
I really don't know what is the best thing to do. I think, ideally,
every user and every mirror should transition to the Apache code and
that there should not be some creeping unsupported BSD version. If
someone decides to start supporting that stranded BSD version, then you
would have a BSD fork to deal with. And trademark issues too. There
cannot be a different OS called NuttX; there can be only one. I just
cannot imagine a positive scenario with retaining an unsupported BSD
version of the RTOS. I doubt the ASF would appreciate that either?
Still just brainstorming..
Re: State of Bitbucket Repsitories
Posted by Gregory Nutt <sp...@gmail.com>.
> 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/repository-mirror-plugin-for-bitbucket?hosting=server&tab=overview
But I think it is only usable if you have Bitbucket on your own server.
Also, I see only references to support mirroring of Bitbucket
repositories on other remotes.
Re: State of Bitbucket Repsitories
Posted by Alan Carvalho de Assis <ac...@gmail.com>.
The right bitbucket url for hooks:
https://www.atlassian.com/git/tutorials/git-hooks
On 12/10/19, Alan Carvalho de Assis <ac...@gmail.com> wrote:
> Hi Greg,
>
> On 12/10/19, Gregory Nutt <sp...@gmail.com> 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 the authoritative source.
>>> Hopefully that will change over time.
>> Certainly, there is no benefit to keep an old static version of the last
>> of the earlier incarnation. Anyone can recover that at will by checking
>> out that last version from GIT. If we are smart, we can tag the initial
>> Apache import to make that easier.
>>
>
> What if we could keep the bitbucket for a while and use the git
> "post-update" to updated the clone repository to the new apache
> repository?
>
> More info:
>
> https://stackoverflow.com/questions/19434605/git-redirections
>
> https://confluence.atlassian.com/bitbucketserver/using-repository-hooks-776639836.html
>
> What do you think?
>
> If you don't agree, then as an way to be helpful for new users, I
> think it should better only removing the repository content and
> putting a README file instructing the user to clone the new apache
> repository.
>
> BR,
>
> Alan
>
Re: State of Bitbucket Repsitories
Posted by Alan Carvalho de Assis <ac...@gmail.com>.
Hi Greg,
On 12/10/19, Gregory Nutt <sp...@gmail.com> 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 the authoritative source.
>> Hopefully that will change over time.
> Certainly, there is no benefit to keep an old static version of the last
> of the earlier incarnation. Anyone can recover that at will by checking
> out that last version from GIT. If we are smart, we can tag the initial
> Apache import to make that easier.
>
What if we could keep the bitbucket for a while and use the git
"post-update" to updated the clone repository to the new apache
repository?
More info:
https://stackoverflow.com/questions/19434605/git-redirections
https://confluence.atlassian.com/bitbucketserver/using-repository-hooks-776639836.html
What do you think?
If you don't agree, then as an way to be helpful for new users, I
think it should better only removing the repository content and
putting a README file instructing the user to clone the new apache
repository.
BR,
Alan
Re: State of Bitbucket Repsitories
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Dec 10, 2019 at 1:07 PM Gregory Nutt <sp...@gmail.com> 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
Posted by Gregory Nutt <sp...@gmail.com>.
>
>> 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 community, for the NuttX trademark, and some protection
> against a fork with a different, incompatible license. That way, there
> is only one NuttX, Apache NuttX.
>
> 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 the authoritative source.
> Hopefully that will change over time.
Certainly, there is no benefit to keep an old static version of the last
of the earlier incarnation. Anyone can recover that at will by checking
out that last version from GIT. If we are smart, we can tag the initial
Apache import to make that easier.
Re: State of Bitbucket Repsitories
Posted by Gregory Nutt <sp...@gmail.com>.
> 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 community, for the NuttX trademark, and some protection against a
fork with a different, incompatible license. That way, there is only one
NuttX, Apache NuttX.
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 the authoritative source. Hopefully that
will change over time.
Re: State of Bitbucket Repsitories
Posted by Flavio Junqueira <fp...@apache.org>.
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 <https://www.apache.org/foundation/how-it-works/legal.html>
This incubator document also talks about the initial code import:
https://incubator.apache.org/guides/transitioning_asf.html <https://incubator.apache.org/guides/transitioning_asf.html>
Finally, as an example, we still have the zookeeper code in sourceforge from before Apache, and I don't that's wrong:
https://sourceforge.net/p/zookeeper/code/ <https://sourceforge.net/p/zookeeper/code/>
-Flavio
> On 10 Dec 2019, at 16:50, Gregory Nutt <sp...@gmail.com> wrote:
>
>
>> 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
Posted by Gregory Nutt <sp...@gmail.com>.
> 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
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Dec 10, 2019 at 10:43 AM Gregory Nutt <sp...@gmail.com> 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 alternative disposition of the Bitbucket repositories might be to
> make them manual mirrors of the Apache repositories. AFAIK Bitbucket
> does not support automated mirroring without a plug-in. But periodic
> manually mirroring of the Apache repositories would help by assuring
> that the Apache licensed code is pushed out to all NuttX mirrors as well.
>
> I really don't know what is the best thing to do. I think, ideally,
> every user and every mirror should transition to the Apache code and
> that there should not be some creeping unsupported BSD version. If
> someone decides to start supporting that stranded BSD version, then you
> would have a BSD fork to deal with. And trademark issues too. There
> cannot be a different OS called NuttX; there can be only one. I just
> cannot imagine a positive scenario with retaining an unsupported BSD
> version of the RTOS. I doubt the ASF would appreciate that either?
>
> Still just brainstorming..
I think we need to ask our mentors what is the generally accepted
thing to do with the project's earlier incarnation.
Nathan
Re: State of Bitbucket Repsitories
Posted by Gregory Nutt <sp...@gmail.com>.
> 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 manual mirrors of the Apache repositories. AFAIK Bitbucket
does not support automated mirroring without a plug-in. But periodic
manually mirroring of the Apache repositories would help by assuring
that the Apache licensed code is pushed out to all NuttX mirrors as well.
I really don't know what is the best thing to do. I think, ideally,
every user and every mirror should transition to the Apache code and
that there should not be some creeping unsupported BSD version. If
someone decides to start supporting that stranded BSD version, then you
would have a BSD fork to deal with. And trademark issues too. There
cannot be a different OS called NuttX; there can be only one. I just
cannot imagine a positive scenario with retaining an unsupported BSD
version of the RTOS. I doubt the ASF would appreciate that either?
Still just brainstorming..
Re: State of Bitbucket Repsitories
Posted by "Matias N." <ma...@imap.cc>.
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 <sp...@gmail.com> 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 read-only and prohibit forks and PRs. Let's try
> >> to make that transition as "knife-edge" as possible.
> >
> >
> > After the bit bucket repos are made read only, I suggest to keep them available indefinitely, both for historical reference and for anyone who wishes to create something based on the original BSD-licensed code.
> >
> > I will follow the recommendation of vote of the PPMC. My plan was to remove them after a grace period to: make it more difficult for people to create something based on the original BSD-licensed code and instead encourage people to use the Apache licensed code, and , more importantly, to make it more difficult to fork the BSD licensed code under a different, license that is incompatible with Apache. Yours and mine are two differing positions. I will follow the will of the PPMC in all things.
>
> Fair enough; it's just a suggestion. :-)
>
> Nathan
>
Re: State of Bitbucket Repsitories
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Dec 10, 2019 at 10:16 AM Gregory Nutt <sp...@gmail.com> 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 read-only and prohibit forks and PRs. Let's try
>> to make that transition as "knife-edge" as possible.
>
>
> After the bit bucket repos are made read only, I suggest to keep them available indefinitely, both for historical reference and for anyone who wishes to create something based on the original BSD-licensed code.
>
> I will follow the recommendation of vote of the PPMC. My plan was to remove them after a grace period to: make it more difficult for people to create something based on the original BSD-licensed code and instead encourage people to use the Apache licensed code, and , more importantly, to make it more difficult to fork the BSD licensed code under a different, license that is incompatible with Apache. Yours and mine are two differing positions. I will follow the will of the PPMC in all things.
Fair enough; it's just a suggestion. :-)
Nathan
Re: State of Bitbucket Repsitories
Posted by Gregory Nutt <sp...@gmail.com>.
> 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 that transition as "knife-edge" as possible.
>
>
> After the bit bucket repos are made read only, I suggest to keep them
> available indefinitely, both for historical reference and for anyone
> who wishes to create something based on the original BSD-licensed code.
I will follow the recommendation of vote of the PPMC. My plan was to
remove them after a grace period to: make it more difficult for people
to create something based on the original BSD-licensed code and instead
encourage people to use the Apache licensed code, and , more
importantly, to make it more difficult to fork the BSD licensed code
under a different, license that is incompatible with Apache. Yours and
mine are two differing positions. I will follow the will of the PPMC in
all things.
Re: State of Bitbucket Repsitories
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Dec 10, 2019 at 9:34 AM Gregory Nutt <sp...@gmail.com> 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 read-only and prohibit forks and PRs. Let's try
> to make that transition as "knife-edge" as possible.
After the bit bucket repos are made read only, I suggest to keep them
available indefinitely, both for historical reference and for anyone who
wishes to create something based on the original BSD-licensed code.
Cheers,
Nathan
State of Bitbucket Repsitories
Posted by Gregory Nutt <sp...@gmail.com>.
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 that transition as "knife-edge" as possible.
Greg
Re: [TEST] Joined
Posted by "Ishikawa, Masayuki (SHES)" <Ma...@sony.com>.
I've just joined too.
On 2019/12/10 9:34, "Disruptive Solutions" <di...@gmail.com> wrote:
It seems alive..
Verstuurd vanaf mijn iPhone
> Op 10 dec. 2019 om 01:11 heeft Alan Carvalho de Assis <ac...@gmail.com> het volgende geschreven:
>
> David,
>
> I think if we still doing it here, Apache people will think we are Nut!
>
> Hehehe
>
> BR,
>
> Alan
>
>> On Monday, December 9, 2019, <da...@gmail.com> wrote:
>> [TEST] Joined
>>
>> Hi Group,
>>
>> Is this thing live yet?
>>
>> *David Sidrane*
>>
>>
>> *David.Sidrane@gmail.com *
>>
Re: [TEST] Joined
Posted by Disruptive Solutions <di...@gmail.com>.
It seems alive..
Verstuurd vanaf mijn iPhone
> Op 10 dec. 2019 om 01:11 heeft Alan Carvalho de Assis <ac...@gmail.com> het volgende geschreven:
>
> David,
>
> I think if we still doing it here, Apache people will think we are Nut!
>
> Hehehe
>
> BR,
>
> Alan
>
>> On Monday, December 9, 2019, <da...@gmail.com> wrote:
>> [TEST] Joined
>>
>> Hi Group,
>>
>> Is this thing live yet?
>>
>> *David Sidrane*
>>
>>
>> *David.Sidrane@gmail.com *
>>
Re: [TEST] Joined
Posted by Alan Carvalho de Assis <ac...@gmail.com>.
David,
I think if we still doing it here, Apache people will think we are Nut!
Hehehe
BR,
Alan
On Monday, December 9, 2019, <da...@gmail.com> wrote:
> [TEST] Joined
>
> Hi Group,
>
> Is this thing live yet?
>
> *David Sidrane*
>
>
> *David.Sidrane@gmail.com *
>