Incubator Lists

[Christopher]

Hi all,

I'm just getting familiar with the incubator project, because I am
anticipating working with some future projects which might submit proposals
to go through incubation, and I'd like to gain some greater familiarity
with how things operate in this space. I've already started reading through
all the stuff linked on the incubator site, and I've subscribed to this
list.

Are there any other lists or areas of collaboration (JIRA, etc.) I should
know about, in order to get more involved, or is this the main incubator
list where most things get discussed for projects going through the process?

Re: Incubator Lists

[Gaurav Shukla]

Hi Christopher,

Thanks for your interest in incubator community, I am also quite new to the
community but here's what I've figured out so far.


   - All the project proposals and general discussion regarding incubator
   projects happen at general@incubator.apache.org
   - Each podling has a dev mailing list, issues mailing list and commits
   mailing list  of the form d...@podlingname.incubator.apache.org example -
   d...@concerted.incubator.apache.org

To get started, you can subscribe to general@incubator.apache.org.




Sent with MailTrack


On Sat, Feb 6, 2016 at 12:14 PM, Christopher  wrote:

> Hi all,
>
> I'm just getting familiar with the incubator project, because I am
> anticipating working with some future projects which might submit proposals
> to go through incubation, and I'd like to gain some greater familiarity
> with how things operate in this space. I've already started reading through
> all the stuff linked on the incubator site, and I've subscribed to this
> list.
>
> Are there any other lists or areas of collaboration (JIRA, etc.) I should
> know about, in order to get more involved, or is this the main incubator
> list where most things get discussed for projects going through the
> process?
>



-- 
Regards !
Gaurav Shukla
gauravshukla.xyz

Re: Confusion over NOTICE vs LICENSE files

[Sean Busbey]

Encouraging use of Whisker from the Apache Creadur project is another
avenue:

http://creadur.apache.org/whisker/

On Thu, Feb 4, 2016 at 5:54 PM, Justin Mclean 
wrote:

> Hi,
>
> >> But better conventions on the format and content of the files that would
> >> make automated processing easier would also be a great thing, but that
> >> might be too late already.
> >
> > Right, the hardest part of this problem is the spec, which SPDX provides.
>
> SPDX looks good - how there been any interest to implement this at Apache?
>
> BTW I see their NOTICE file has a few issues :-) [1] (It mentions Apache,
> MIT and BSD software). What we put in NOTICE is policy right rather than a
> legal requirement so I guess 3rd parties can do just about anything and
> that’s OK?
>
> A fair number of non ASF Apache software is usually missing a NOTICE file
> or has other issues. What do we do when you bundle a non ASF Apache license
> software that is missing a NOTICE file? Nothing or be a little more polite
> or assume a minimal NOTICE file and add that to ours?
>
> Thanks,
> Justin
>
> 1. https://github.com/spdx/tools/blob/master/NOTICE
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sean

Re: Making license adjustment tools publicly available

[sebb]

On 5 February 2016 at 00:14, Roman Shaposhnik  wrote:
> Hi!
>
> a podling recently asked me why:
> https://svn.apache.org/repos/private/committers/relicense/
> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
> are only available to commiters. I see
> no reason why, but of course I'm appreciative
> of the warning here:
> https://svn.apache.org/repos/private/committers/README
>
> Two questions:
>1. Is there any disagreement that making this tool publically
> available would be a 'good thing' ?

Yes, there are caveats:
- as I recall, the tools are not perfect, and have not seen any recent
development.
- is it safe to automate the update of license headers? This is
generally something that needs to be addressed file by file.

> 2. Who should bless the svn mv if we all agree?
>
> Thanks,
> Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

Hi,

> When I saw this topic in the past, the answer was "nothing" [1]

What we’re legally required to do (i.e. nothing) is reasonably clear, but what 
policy or culturally is the best option is perhaps unclear. 

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Making license adjustment tools publicly available

[Roman Shaposhnik]

On Fri, Feb 5, 2016 at 11:24 AM, sebb  wrote:
> On 5 February 2016 at 00:14, Roman Shaposhnik  wrote:
>> Hi!
>>
>> a podling recently asked me why:
>> https://svn.apache.org/repos/private/committers/relicense/
>> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
>> are only available to commiters. I see
>> no reason why, but of course I'm appreciative
>> of the warning here:
>> https://svn.apache.org/repos/private/committers/README
>>
>> Two questions:
>>1. Is there any disagreement that making this tool publically
>> available would be a 'good thing' ?
>
> Yes, there are caveats:
> - as I recall, the tools are not perfect, and have not seen any recent
> development.
> - is it safe to automate the update of license headers? This is
> generally something that needs to be addressed file by file.

Sure. But the above literally applies to all of our software (there are always
caveats). At any rate, seems like there's enough agreement to make them
publicly available (note I'm not saying advertising them or anything).

I'll let it stew till Mon and then JFDY

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

Hi,

A bit of status. Most of the infrastructure is created. The Jira space 
is waiting for a reboot of the system and will only be available next 
Tue. The git repo is however available and we can start the code grant 
process (by litbit, whom afaik owns the IP). Committers should continue 
to submit the iclas and subcribe to lists.


The project needs to submit a report to the incubator quarterly (monthly 
for the first 3 mo). I took the liberty tho submit the report for this 
month [1], but I expect one or more committers to step up (the ASF is a 
meritocracy) and take care (with help) of admin duties. Once most 
everybody subscribes to the list, such communication should happen on 
the (mailing) lists.


Best,
Hadrian

[1] https://wiki.apache.org/incubator/February2016


On 02/01/2016 12:51 AM, Tony Faustini wrote:

Hi Hadrian, thanks for setting this all up. I have already sent in my ICLA and 
I hope that the other contributors will follow this week. We are working on our 
corporate CLA and that too should be in place soon. We are excited about the 
creation of this community and we look forward to others participating.

Again thanks for setting  up the iota polling we hope this will become a 
vibrant community of interest for many individuals and corporations alike.

-Tony


On Jan 31, 2016, at 4:40 PM, Hadrian Zbarcea  wrote:

Hi Tony, Reza,

I found time this weekend to setup the iota podling. The proposal is now listed 
in the index or proposals [1]. The project status page [2] is setup and listed 
in the incubator list [3]. I will maintain the status page in the early phases. 
I created an issue for infra to create the project resources [4] (mailing 
lists, git repo, etc). This should not take long.

Please review the incubation policy on setting up a new podling [5]. What 
you'll need to do (or complete, because I think you already started) is the 
CLAs (individual and corporate), orientation (it really helps) and the code 
grant and IP clearance.

Feel free to get in touch with me as necessary to coordinate. It'll get easier 
once the mailing list are created.

Best,
Hadrian


[1] https://wiki.apache.org/incubator/ProjectProposals
[2] http://incubator.apache.org/projects/iota.html
[3] http://incubator.apache.org/projects/
[4] https://issues.apache.org/jira/browse/INFRA-11168
[5] 
http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Accept the iota project into the Apache Incubator

[Tony Faustini]

Hi Hadrian, thanks so much for setting up the infrastructure. I will ask the 
remaining individuals to submit their ICLA and also ask Litbit to submit it’s 
CCLA. I will likely volunteer to take care of the initial admin duties until we 
get a flow of communication and a decision making via the mailing lists is 
established. Thanks for submitting the first first monthly report. Is the code 
grant process you are referring to below the CCLA or is it an additional 
requirement?

-Tony


> On Feb 5, 2016, at 8:14 PM, Hadrian Zbarcea  wrote:
> 
> Hi,
> 
> A bit of status. Most of the infrastructure is created. The Jira space is 
> waiting for a reboot of the system and will only be available next Tue. The 
> git repo is however available and we can start the code grant process (by 
> litbit, whom afaik owns the IP). Committers should continue to submit the 
> iclas and subcribe to lists.
> 
> The project needs to submit a report to the incubator quarterly (monthly for 
> the first 3 mo). I took the liberty tho submit the report for this month [1], 
> but I expect one or more committers to step up (the ASF is a meritocracy) and 
> take care (with help) of admin duties. Once most everybody subscribes to the 
> list, such communication should happen on the (mailing) lists.
> 
> Best,
> Hadrian
> 
> [1] https://wiki.apache.org/incubator/February2016
> 
> 
> On 02/01/2016 12:51 AM, Tony Faustini wrote:
>> Hi Hadrian, thanks for setting this all up. I have already sent in my ICLA 
>> and I hope that the other contributors will follow this week. We are working 
>> on our corporate CLA and that too should be in place soon. We are excited 
>> about the creation of this community and we look forward to others 
>> participating.
>> 
>> Again thanks for setting  up the iota polling we hope this will become a 
>> vibrant community of interest for many individuals and corporations alike.
>> 
>> -Tony
>> 
>>> On Jan 31, 2016, at 4:40 PM, Hadrian Zbarcea  wrote:
>>> 
>>> Hi Tony, Reza,
>>> 
>>> I found time this weekend to setup the iota podling. The proposal is now 
>>> listed in the index or proposals [1]. The project status page [2] is setup 
>>> and listed in the incubator list [3]. I will maintain the status page in 
>>> the early phases. I created an issue for infra to create the project 
>>> resources [4] (mailing lists, git repo, etc). This should not take long.
>>> 
>>> Please review the incubation policy on setting up a new podling [5]. What 
>>> you'll need to do (or complete, because I think you already started) is the 
>>> CLAs (individual and corporate), orientation (it really helps) and the code 
>>> grant and IP clearance.
>>> 
>>> Feel free to get in touch with me as necessary to coordinate. It'll get 
>>> easier once the mailing list are created.
>>> 
>>> Best,
>>> Hadrian
>>> 
>>> 
>>> [1] https://wiki.apache.org/incubator/ProjectProposals
>>> [2] http://incubator.apache.org/projects/iota.html
>>> [3] http://incubator.apache.org/projects/
>>> [4] https://issues.apache.org/jira/browse/INFRA-11168
>>> [5] 
>>> http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling
>>> 
>>> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Accept the iota project into the Apache Incubator

[Justin Mclean]

Hi,

>  Is the code grant process you are referring to below the CCLA or is it an 
> additional requirement?

CCLA are optional [1][2], software grants [3][4] are required. So yes that’s an 
additional requirement, SG give the ASF the rights to use to code that is 
donated.

Thanks,
Justin

1. http://www.apache.org/licenses/#clas
2. http://www.apache.org/licenses/icla.txt
3. http://www.apache.org/licenses/#grants
4. http://www.apache.org/licenses/software-grant.txt
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org