Hello Community,
The Apache Training (incubating) team is pleased to announce the source
release of Navigating the ASF Incubator Process 1.0 (incubating).
This is a slide deck containing an overview of how to navigate the ASF
incubating process from start to finish.
Apache Training aim is to cre
Hi,
> The language would be:
>
> “For the current status of this project through the Apache Incubator visit
> http://incubator.apache.org/project/${podling}.html
Understand you now I’ve added that to the wiki page.
Thanks,
Justin
Sent from my iPhone
> On Jul 12, 2019, at 7:32 PM, Justin Mclean wrote:
>
> HI,
>
>> +1 if as discussed earlier we enhance both disclaimers to include a link to
>> the podling status page where the podling will provide the most up to date
>> details.
>
> I think the text needs to refer to
HI,
> +1 if as discussed earlier we enhance both disclaimers to include a link to
> the podling status page where the podling will provide the most up to date
> details.
I think the text needs to refer to that release, while the latest is also
useful, it if doesn’t include things that were in
+1 if as discussed earlier we enhance both disclaimers to include a link to the
podling status page where the podling will provide the most up to date details.
We can discuss a new Git based status page in a separate thread. I’d like to
change from the xml/secret yaml files in svn to a straight
+1 from me to have two disclaimers, chosen by podings.
Also, +1 from me, the one they chosen should stay in website and
announcement.
Sheng
Justin Mclean 于2019年7月13日 周六上午9:37写道：
> Hi,
>
> +1 Works for me.
>
> It will need to be made very clear to podlings that different rules apply
> depending
Hi,
+1 Works for me.
It will need to be made very clear to podlings that different rules apply
depending on what disclaimer they have.
Would this also please to the disclaimer on their web site and in announcement
emails?
Thanks,
Justin
Big +1!
On Fri, Jul 12, 2019 at 4:08 PM Matt Sicker wrote:
>
> Agreed, this sounds like a great way to do this. As IPMC members reviewing
> releases, you now have better guidelines on how to go about reviewing a
> podling release.
>
> On Fri, Jul 12, 2019 at 17:59, Jim Jagielski wrote:
>
> > Thi
Agreed, this sounds like a great way to do this. As IPMC members reviewing
releases, you now have better guidelines on how to go about reviewing a
podling release.
On Fri, Jul 12, 2019 at 17:59, Jim Jagielski wrote:
> This is a great idea... +1
>
> > On Jul 12, 2019, at 6:31 PM, Craig Russell w
This is a great idea... +1
> On Jul 12, 2019, at 6:31 PM, Craig Russell wrote:
>
> Hi,
>
> I understand I'm a bit late to this particular discussion, but perhaps we can
> consider two different disclaimers that podlings can choose:
>
> The standard disclaimer that does not disclaim licensing
Hi,
I understand I'm a bit late to this particular discussion, but perhaps we can
consider two different disclaimers that podlings can choose:
The standard disclaimer that does not disclaim licensing issues; or,
The proposed new disclaimer to be used by podlings' first releases until they
sort
Replies inline:
> On Jul 12, 2019, at 3:49 AM, Justin Mclean wrote:
>
> Hi,
>
>> Adding an additional disclaimer that we may have known issues adds
>> additional barriers to adoption and community growth.
>
> I think the question to be asked is does that add barries more than having to
> hav
Hi all,
Apache Celix received a donation which adds an HTTP admin service
to Celix. This HTTP admin service can be used to serve a set of
specified resources over an HTTP endpoint. The HTTP admin supports
the use of websockets as well.
The IP clearance form can be found at:
https://incubator.apac
> I think the question to be asked is does that add barries more than having to
> have 100% compliant releases?
Is this a current requirement that is written down somewhere and
generally practiced?
Am Fr., 12. Juli 2019 um 09:49 Uhr schrieb Justin Mclean
:
>
> Hi,
>
> > Adding an additional disc
HI,
> Dear mentors from general list, could you please review the report we've
> submitted and sign it, if you don't have any objections/comments.
I just checked, non one has signed it off.
> We'd really not want to be blacklisted because no one can review and sign
> reports that are submittin
Hi,
> Adding an additional disclaimer that we may have known issues adds additional
> barriers to adoption and community growth.
I think the question to be asked is does that add barries more than having to
have 100% compliant releases? I think the answer may depend on the podling.
Have does t
Moving general@incubator.apache.org into To field.
Dear mentors from general list, could you please review the report we've
submitted and sign it, if you don't have any objections/comments.
We'd really not want to be blacklisted because no one can review and sign
reports that are submitting on ti
17 matches
Mail list logo
