You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fluo.apache.org by Christopher <ct...@apache.org> on 2018/03/07 20:13:18 UTC
[DISCUSS] Migrate remaining astralway repos
For much of Fluo's early life, it was hosted at https://github.com/fluo-io
As many will be aware, this was renamed to https://github.com/astralway to
satisfy concerns about trademark use during Fluo's transition through the
Apache Incubator.
The astralway repo still contains some Fluo-related code repositories
(developer tools and examples), which I think should be migrated over now
that Fluo is an established top-level project and can organize itself into
multiple repos.
Specifically, I'd like to:
1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
fluo-muchos, respectively; their names don't really need to change in our
everyday usage... just the repo names).
2. create a fluo-examples repository to contain phrasecount, webindex, and
stresso (and maybe quickstart, if that is still relevant)
Initially none of these repos would be "released", since they are really
just developer tools not intended for general use or (in the case of the
examples) closer to documentation. But, we could vote on releases at some
point in the future.
Please let me know if there's any objections to this community taking over
those repos formally. (If this happens, those of us maintaining astralway
can shut that down.)
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Christopher <ct...@apache.org>.
Okay, I'm revisiting this this week. All the contributors to the astralway
repos are ASF committers with ICLAs on file, so that should make any IP
CLEARANCE process easy. I've frozen the astralway repos, and will initiate
a vote thread on whether to accept the code donation to the Fluo project.
This vote can happen in parallel to the IP CLEARANCE process, which I will
also initiate.
On Tue, Mar 13, 2018 at 12:35 AM Christopher <ct...@apache.org> wrote:
> No problem. These are simple projects, under Apache 2.0 since inception,
> and all but one contributor (jmark99) are already Apache committers with
> ICLAs filed. I can follow up with jmark99 to ask him if he's willing to
> file one.
>
> The IP clearance process for donations like this is here:
> https://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> I'll volunteer as the managing member, once we've agreed to accept the
> donations. For that, I'll start a [VOTE] thread so we can formally decide
> on whether to accept the donation.
>
> On Mon, Mar 12, 2018 at 10:47 AM Josh Elser <el...@apache.org> wrote:
>
>> Don't forget to execute the IP clearance process, please!
>>
>> https://incubator.apache.org/guides/ip_clearance.html
>>
>> On 3/7/18 3:16 PM, Christopher wrote:
>> > In case "migration" is a confusing term for what I'm proposing, I'm
>> > proposing that the astralway maintainers (of which, I am one) donate
>> these
>> > repos to Apache Fluo to maintain. The question here is essentially: is
>> the
>> > Apache Fluo community (of which, I am also one) willing to accept these
>> > contributions?
>> >
>> > On Wed, Mar 7, 2018 at 3:13 PM Christopher <ct...@apache.org> wrote:
>> >
>> >> For much of Fluo's early life, it was hosted at
>> https://github.com/fluo-io
>> >> As many will be aware, this was renamed to
>> https://github.com/astralway to
>> >> satisfy concerns about trademark use during Fluo's transition through
>> the
>> >> Apache Incubator.
>> >>
>> >> The astralway repo still contains some Fluo-related code repositories
>> >> (developer tools and examples), which I think should be migrated over
>> now
>> >> that Fluo is an established top-level project and can organize itself
>> into
>> >> multiple repos.
>> >>
>> >> Specifically, I'd like to:
>> >>
>> >> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
>> >> fluo-muchos, respectively; their names don't really need to change in
>> our
>> >> everyday usage... just the repo names).
>> >> 2. create a fluo-examples repository to contain phrasecount, webindex,
>> and
>> >> stresso (and maybe quickstart, if that is still relevant)
>> >>
>> >> Initially none of these repos would be "released", since they are
>> really
>> >> just developer tools not intended for general use or (in the case of
>> the
>> >> examples) closer to documentation. But, we could vote on releases at
>> some
>> >> point in the future.
>> >>
>> >> Please let me know if there's any objections to this community taking
>> over
>> >> those repos formally. (If this happens, those of us maintaining
>> astralway
>> >> can shut that down.)
>> >>
>> >
>>
>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Christopher <ct...@apache.org>.
No problem. These are simple projects, under Apache 2.0 since inception,
and all but one contributor (jmark99) are already Apache committers with
ICLAs filed. I can follow up with jmark99 to ask him if he's willing to
file one.
The IP clearance process for donations like this is here:
https://incubator.apache.org/ip-clearance/ip-clearance-template.html
I'll volunteer as the managing member, once we've agreed to accept the
donations. For that, I'll start a [VOTE] thread so we can formally decide
on whether to accept the donation.
On Mon, Mar 12, 2018 at 10:47 AM Josh Elser <el...@apache.org> wrote:
> Don't forget to execute the IP clearance process, please!
>
> https://incubator.apache.org/guides/ip_clearance.html
>
> On 3/7/18 3:16 PM, Christopher wrote:
> > In case "migration" is a confusing term for what I'm proposing, I'm
> > proposing that the astralway maintainers (of which, I am one) donate
> these
> > repos to Apache Fluo to maintain. The question here is essentially: is
> the
> > Apache Fluo community (of which, I am also one) willing to accept these
> > contributions?
> >
> > On Wed, Mar 7, 2018 at 3:13 PM Christopher <ct...@apache.org> wrote:
> >
> >> For much of Fluo's early life, it was hosted at
> https://github.com/fluo-io
> >> As many will be aware, this was renamed to https://github.com/astralway
> to
> >> satisfy concerns about trademark use during Fluo's transition through
> the
> >> Apache Incubator.
> >>
> >> The astralway repo still contains some Fluo-related code repositories
> >> (developer tools and examples), which I think should be migrated over
> now
> >> that Fluo is an established top-level project and can organize itself
> into
> >> multiple repos.
> >>
> >> Specifically, I'd like to:
> >>
> >> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
> >> fluo-muchos, respectively; their names don't really need to change in
> our
> >> everyday usage... just the repo names).
> >> 2. create a fluo-examples repository to contain phrasecount, webindex,
> and
> >> stresso (and maybe quickstart, if that is still relevant)
> >>
> >> Initially none of these repos would be "released", since they are really
> >> just developer tools not intended for general use or (in the case of the
> >> examples) closer to documentation. But, we could vote on releases at
> some
> >> point in the future.
> >>
> >> Please let me know if there's any objections to this community taking
> over
> >> those repos formally. (If this happens, those of us maintaining
> astralway
> >> can shut that down.)
> >>
> >
>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Josh Elser <el...@apache.org>.
Don't forget to execute the IP clearance process, please!
https://incubator.apache.org/guides/ip_clearance.html
On 3/7/18 3:16 PM, Christopher wrote:
> In case "migration" is a confusing term for what I'm proposing, I'm
> proposing that the astralway maintainers (of which, I am one) donate these
> repos to Apache Fluo to maintain. The question here is essentially: is the
> Apache Fluo community (of which, I am also one) willing to accept these
> contributions?
>
> On Wed, Mar 7, 2018 at 3:13 PM Christopher <ct...@apache.org> wrote:
>
>> For much of Fluo's early life, it was hosted at https://github.com/fluo-io
>> As many will be aware, this was renamed to https://github.com/astralway to
>> satisfy concerns about trademark use during Fluo's transition through the
>> Apache Incubator.
>>
>> The astralway repo still contains some Fluo-related code repositories
>> (developer tools and examples), which I think should be migrated over now
>> that Fluo is an established top-level project and can organize itself into
>> multiple repos.
>>
>> Specifically, I'd like to:
>>
>> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
>> fluo-muchos, respectively; their names don't really need to change in our
>> everyday usage... just the repo names).
>> 2. create a fluo-examples repository to contain phrasecount, webindex, and
>> stresso (and maybe quickstart, if that is still relevant)
>>
>> Initially none of these repos would be "released", since they are really
>> just developer tools not intended for general use or (in the case of the
>> examples) closer to documentation. But, we could vote on releases at some
>> point in the future.
>>
>> Please let me know if there's any objections to this community taking over
>> those repos formally. (If this happens, those of us maintaining astralway
>> can shut that down.)
>>
>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Keith Turner <ke...@deenlo.com>.
+1
On Wed, Mar 7, 2018 at 3:16 PM, Christopher <ct...@apache.org> wrote:
> In case "migration" is a confusing term for what I'm proposing, I'm
> proposing that the astralway maintainers (of which, I am one) donate these
> repos to Apache Fluo to maintain. The question here is essentially: is the
> Apache Fluo community (of which, I am also one) willing to accept these
> contributions?
>
> On Wed, Mar 7, 2018 at 3:13 PM Christopher <ct...@apache.org> wrote:
>
>> For much of Fluo's early life, it was hosted at https://github.com/fluo-io
>> As many will be aware, this was renamed to https://github.com/astralway to
>> satisfy concerns about trademark use during Fluo's transition through the
>> Apache Incubator.
>>
>> The astralway repo still contains some Fluo-related code repositories
>> (developer tools and examples), which I think should be migrated over now
>> that Fluo is an established top-level project and can organize itself into
>> multiple repos.
>>
>> Specifically, I'd like to:
>>
>> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
>> fluo-muchos, respectively; their names don't really need to change in our
>> everyday usage... just the repo names).
>> 2. create a fluo-examples repository to contain phrasecount, webindex, and
>> stresso (and maybe quickstart, if that is still relevant)
>>
>> Initially none of these repos would be "released", since they are really
>> just developer tools not intended for general use or (in the case of the
>> examples) closer to documentation. But, we could vote on releases at some
>> point in the future.
>>
>> Please let me know if there's any objections to this community taking over
>> those repos formally. (If this happens, those of us maintaining astralway
>> can shut that down.)
>>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Christopher <ct...@apache.org>.
In case "migration" is a confusing term for what I'm proposing, I'm
proposing that the astralway maintainers (of which, I am one) donate these
repos to Apache Fluo to maintain. The question here is essentially: is the
Apache Fluo community (of which, I am also one) willing to accept these
contributions?
On Wed, Mar 7, 2018 at 3:13 PM Christopher <ct...@apache.org> wrote:
> For much of Fluo's early life, it was hosted at https://github.com/fluo-io
> As many will be aware, this was renamed to https://github.com/astralway to
> satisfy concerns about trademark use during Fluo's transition through the
> Apache Incubator.
>
> The astralway repo still contains some Fluo-related code repositories
> (developer tools and examples), which I think should be migrated over now
> that Fluo is an established top-level project and can organize itself into
> multiple repos.
>
> Specifically, I'd like to:
>
> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
> fluo-muchos, respectively; their names don't really need to change in our
> everyday usage... just the repo names).
> 2. create a fluo-examples repository to contain phrasecount, webindex, and
> stresso (and maybe quickstart, if that is still relevant)
>
> Initially none of these repos would be "released", since they are really
> just developer tools not intended for general use or (in the case of the
> examples) closer to documentation. But, we could vote on releases at some
> point in the future.
>
> Please let me know if there's any objections to this community taking over
> those repos formally. (If this happens, those of us maintaining astralway
> can shut that down.)
>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by Mike Walch <mw...@apache.org>.
+1 Sounds like a good plan.
On Wed, Mar 7, 2018 at 3:13 PM, Christopher <ct...@apache.org> wrote:
> For much of Fluo's early life, it was hosted at https://github.com/fluo-io
> As many will be aware, this was renamed to https://github.com/astralway to
> satisfy concerns about trademark use during Fluo's transition through the
> Apache Incubator.
>
> The astralway repo still contains some Fluo-related code repositories
> (developer tools and examples), which I think should be migrated over now
> that Fluo is an established top-level project and can organize itself into
> multiple repos.
>
> Specifically, I'd like to:
>
> 1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
> fluo-muchos, respectively; their names don't really need to change in our
> everyday usage... just the repo names).
> 2. create a fluo-examples repository to contain phrasecount, webindex, and
> stresso (and maybe quickstart, if that is still relevant)
>
> Initially none of these repos would be "released", since they are really
> just developer tools not intended for general use or (in the case of the
> examples) closer to documentation. But, we could vote on releases at some
> point in the future.
>
> Please let me know if there's any objections to this community taking over
> those repos formally. (If this happens, those of us maintaining astralway
> can shut that down.)
>
Re: [DISCUSS] Migrate remaining astralway repos
Posted by kenneth mcfarland <ke...@gmail.com>.
+1
On Mar 7, 2018 12:13 PM, "Christopher" <ct...@apache.org> wrote:
For much of Fluo's early life, it was hosted at https://github.com/fluo-io
As many will be aware, this was renamed to https://github.com/astralway to
satisfy concerns about trademark use during Fluo's transition through the
Apache Incubator.
The astralway repo still contains some Fluo-related code repositories
(developer tools and examples), which I think should be migrated over now
that Fluo is an established top-level project and can organize itself into
multiple repos.
Specifically, I'd like to:
1. put in a request to INFRA to migrate uno and muchos (fluo-uno and
fluo-muchos, respectively; their names don't really need to change in our
everyday usage... just the repo names).
2. create a fluo-examples repository to contain phrasecount, webindex, and
stresso (and maybe quickstart, if that is still relevant)
Initially none of these repos would be "released", since they are really
just developer tools not intended for general use or (in the case of the
examples) closer to documentation. But, we could vote on releases at some
point in the future.
Please let me know if there's any objections to this community taking over
those repos formally. (If this happens, those of us maintaining astralway
can shut that down.)