Or/and the existing mentors could concentrate more on helping the podling they
handle to become a TLP and not stay in the incubator for too long.
Even if that sometimes requires becoming more a PITA to the podlings that are
sort of living in the incubator forever ...
And in the end we should
On 25/02/2019 19:22, Dave Fisher wrote:
To me the main Incubator problem is most podlings do not have three fully
engaged mentors.
+1
52 or 53 Incubating podlings may be too many.
+1
The Incubator may be too lenient in (a) allowing podlings in with minimal
mentors
+1
The tricky
Hi -
I agree with what Myrle wrote I wanted to focus on this paragraph which I think
describes one of the major issues with the IPMC.
> On Feb 25, 2019, at 3:03 AM, Myrle Krantz wrote:
>
> Also, our mentors were not always the most active, so it would have been
> impossible for us to get a
Hi Mick,
The ASF's official Release Policy lives here:
https://www.apache.org/legal/release-policy
The policy text itself is up-to-date and authoritative. (The associated FAQ,
also on that page, does not live up to the same standard.)
On 2019/02/25 09:05:30, "Mick Semb Wever" wrote:
>
Hey Mick,
I see some promise in the approach you outline. I'd like to explain the
advantages my project drew from the current system, so that we don't lose
anything important in the process of change. Then I would like to suggest
a refinement of your approach. I'm top posting here, because I'm
I'll chime in, but on the technical front my experience is rather new in the
incubator, i'm still learning.
> Looking at some of the situations we currently have I think we may need
> some more general guidance for incubating projects and making releases
> after just joining the incubator.
Hi,
Thanks for tech feedback John.
> This is a loaded statement, since PPMC's can never make releases. The IPMC
> approves the release always within the scope of Apache.
I did say above that it does need to be approved by the PPMC and IPMC I’ll see
if I can reword.
>> Ideally within six
Hi Justin
On Tue, Feb 19, 2019 at 5:38 PM Justin Mclean
wrote:
> Hi,
>
> Looking at some of the situations we currently have I think we may need
> some more general guidance for incubating projects and making releases
> after just joining the incubator. In this context “non approved” means
>
Hi,
> (1) Mentor or champion bootstraps the podling files and mailing lists then
> starts:
> (2) Onboard the individuals to join the mailing lists, file ICLAs and get
> their apache ids.
> (3) SGA must be filed. (Or it is determined that ICLA covers everything)
> (Domain transfer?)
> (4)
> On Feb 19, 2019, at 3:10 PM, Kevin A. McGrail wrote:
>
> On 2/19/2019 6:07 PM, Dave Fisher wrote:
>> (5) Go and develop in The Apache Way!
>>
>> Only once these four things happen can we start any timer on the first
>> Apache Release.
>
> Four, no FIVE things! Don't forget the Spanish
On 2/19/2019 6:07 PM, Dave Fisher wrote:
> (5) Go and develop in The Apache Way!
>
> Only once these four things happen can we start any timer on the first Apache
> Release.
Four, no FIVE things! Don't forget the Spanish Inquisition.
Agreed. We need to setup the reason hurdles with a carrot
We have to make sure that the steps that occur before work can proceed are
addressed.
(1) Mentor or champion bootstraps the podling files and mailing lists then
starts:
(2) Onboard the individuals to join the mailing lists, file ICLAs and get their
apache ids.
(3) SGA must be filed. (Or it is
I think this might be a really important faq on the top of the list of
OK, now we are voted in, what's next? and a FAQ about releases.
On 2/19/2019 5:38 PM, Justin Mclean wrote:
> Hi,
>
> Looking at some of the situations we currently have I think we may need some
> more general guidance for
Hi,
Looking at some of the situations we currently have I think we may need some
more general guidance for incubating projects and making releases after just
joining the incubator. In this context “non approved” means releases or
distributions not approved by the PPPM and IPMC (usually by
14 matches
Mail list logo
