ApacheCon Europe 2019 talks which are relevant to incubating projects

[myrle]

Dear Apache Incubator mentors and incubating projects,

In a little over 2 weeks time, ApacheCon Europe is taking place in 
Berlin. Join us from October 22 to 24 for an exciting program and lovely 
get-together of the Apache Community.


We are also planning a hackathon.  If your project is interested in 
participating, please enter yourselves here: 
https://cwiki.apache.org/confluence/display/COMDEV/Hackathon At 
ApacheCon in Vegas, Dave Fisher leveraged the hackathon space was used 
for a very interesting discussion on Open Source in China.  So topics 
can go beyond coding.


The following talks should be especially relevant for you:

**

 * *

   https://aceu19.apachecon.com/session/idea-apache-tlp

 *

   https://aceu19.apachecon.com/session/podlings-shark-tank

 *

   https://aceu19.apachecon.com/session/navigating-asf-incubator-process

   *

**

Furthermore there will be a whole conference track on community topics: 
Learn how to motivate users to contribute patches, how the board of 
directors works, and much more: ApacheCon Europe 2019 Community track 



Tickets are available here  – 
for Apache Committers (including committers of incubating projects) we 
offer discounted tickets.  Prices will be going up on October 7th, so 
book soon.


Please also help spread the word and make ApacheCon Europe 2019 a success!

We’re looking forward to welcoming you at #ACEU19!

Best,

Your ApacheCon team

Re: Podlings & IP Clearance

[Alex Harui]

IIRC, the main thing that matters is that all incoming code that was developed 
outside the ASF gets cleared.  For podlings, there is frequently one big code 
donation that eventually gets turned into a release.  The podling gets to put 
the code in a repo and then clear it.  I believe that's mainly to help get the 
community going with the least delay.  Podlings often do that one release and 
then graduate to TLP.

But once you have clean code in your repo, before you mix a bunch of other code 
into it, it is advised to clear it before mixing that code.  The IP Clearance 
process is the main way to do that and the Incubator is the central log of 
these big donations being cleared.

I don't think Weex had to go through IP Clearance if the mentors felt they 
could inspect and clear the code, but it doesn't hurt to ask for more eyes on 
it.

At least, that's how I remember it from my podling days.  Flex received several 
donations before and after graduation.

My 2 cents,
-Alex

On 10/4/19, 12:36 AM, "申远"  wrote:

Hi

As a PPMC member of Weex, I didn’t find any documentation about the IP
clearance process for Podlling project, so I just followed what other PPMC
did after asking in this mailing list [4]. I am Ok to do it in another way
if it’s written in the documentation clearly.

IMO, the problem here is that we don’t have an IP clearance process for
podllings, so podllings have no other way but follow the standard IP
process of TLP project.

[4]

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fincubator-general%2F201909.mbox%2F%253cDAEE7CD2-C05A-4A09-867C-37F1C1B19DF8%40classsoftware.com%253edata=02%7C01%7Caharui%40adobe.com%7Cb9f970fbe1274b9a4d5608d7489da1b4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057714181342086sdata=Ak%2BXNWhu2ltjgGm7vksfmzyyxcbWHhwHNyUnuv8FjB4%3Dreserved=0

Dave Fisher 于2019年10月4日 周五13:18写道：

> Hi -
>
> > On Oct 3, 2019, at 9:12 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> >> The recent vote from Weex [1] made me think about the IP Clearance
> >> process.  Per [2], podlings should not follow this process and instead
> are
> >> directed to look at [3].
> >
> > I always assumed that that was advised about the initial codebase and
> don’t see an issue with following [2] past that. It certainly could be 
made
> clearer.
>
> I’ve always considered it to be the mentor’s job to assure IP was
> considered for podlings donations.
>
> A greybeard told me recently that the board added IP clearance to the IPMC
> for TLPs
>
> Regards,
> Dave
>
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Best Regards
York Shen
申远

Re: Podlings & IP Clearance

[申远]

Hi

As a PPMC member of Weex, I didn’t find any documentation about the IP
clearance process for Podlling project, so I just followed what other PPMC
did after asking in this mailing list [4]. I am Ok to do it in another way
if it’s written in the documentation clearly.

IMO, the problem here is that we don’t have an IP clearance process for
podllings, so podllings have no other way but follow the standard IP
process of TLP project.

[4]
https://mail-archives.apache.org/mod_mbox/incubator-general/201909.mbox/%3cdaee7cd2-c05a-4a09-867c-37f1c1b19...@classsoftware.com%3e

Dave Fisher 于2019年10月4日 周五13:18写道：

> Hi -
>
> > On Oct 3, 2019, at 9:12 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> >> The recent vote from Weex [1] made me think about the IP Clearance
> >> process.  Per [2], podlings should not follow this process and instead
> are
> >> directed to look at [3].
> >
> > I always assumed that that was advised about the initial codebase and
> don’t see an issue with following [2] past that. It certainly could be made
> clearer.
>
> I’ve always considered it to be the mentor’s job to assure IP was
> considered for podlings donations.
>
> A greybeard told me recently that the board added IP clearance to the IPMC
> for TLPs
>
> Regards,
> Dave
>
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Best Regards
York Shen
申远