Hi,
> Ownership of the Projects. Once a project enters the Incubator, ASF owns the
> project.
Owns is probably too strong a word, but it expected they follow ASF policies
(and what you listed) by the time they are ready to graduate.
> All trademark/IP around the project belongs to ASF now.
Agreed with that, from a poddling’s respective, I think it’s important that the
community understand the following issues before it enters the incubator:
Governance Model. Projects in Incubator would adopt Meritocracy model, no
exception.
Ownership of the Projects. Once a project enters the
Well, I think a lot of frustration with the Apache incubation process could
be avoided simply by very explicitly asking this question to a community
planning to start incubation: “Are you aware that until you complete
incubation you will not be in full control of your project, for example,
please
Geertjan Wielenga wrote on Sun, Jun 30, 2019 at 18:14:52 +0200:
> Any community joining Apache should be very clear in their own minds that
> the Incubator is there for them to get used to the Apache Way. It is not
> there for getting releases done in the same cadence as before the community
>
Any community joining Apache should be very clear in their own minds that
the Incubator is there for them to get used to the Apache Way. It is not
there for getting releases done in the same cadence as before the community
entered the Incubator, nor does it carry the responsibility for that. Until
Thanks for making this list, Justin.
Next time I mentor a project, I shall probably convert the list into a
presentation (with a few “and here’s the good news” slides at the beginning and
end) and schedule a video meeting with a few of the initial committers, leaving
plenty of time for
You are better about polishing English words than me
The point is only, I received many feedback about the long release
procedure is unexpected.
Justin Mclean 于2019年6月30日 周日下午1:13写道：
> Hi,
>
> > In You will need to change the way you build and distribute software
> >> For instance, you now need
Hi,
> In You will need to change the way you build and distribute software
>> For instance, you now need to vote on releases over a 72 whole cycle, and
>> also have the IPMC vote on your releases.
Thanks for the suggestion, I’ll update that,. BTW I wasn’t trying to make it
comprehensive or
Hi Justin
I like this list.
One suggestion,
In You will need to change the way you build and distribute software
> For instance, you now need to vote on releases over a 72 whole cycle, and
> also have the IPMC vote on your releases.
You need 72 hours pod inside vote, and IPMC vote take at
Hi,
I put down some thoughts to help podling expectations and list some of the
issues a podling may face on it’s incubating journey. [1] Feedback and edits
welcome.
Most projects do not run into serious issues or are good at handling any issue
that do crop up. I think it would be a good idea
10 matches
Mail list logo
