Re: [DISCUSS] Graduate Apache Rya (incubating) as a TLP

2019-09-03 Thread Adina Crainiceanu
Hi,

5 of the proposed PMC members are from Parsons, all others have different
affiliations (different from Parsons and different from each other).
Thanks,
Adina

On Tue, Sep 3, 2019 at 6:50 PM Justin Mclean 
wrote:

> Hi,
>
> Just out of interest what is the diversity (in terms of company
> affiliation) of the proposed PMC like?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Dr. Adina Crainiceanu
Associate Professor
Computer Science Department
United States Naval Academy
410-293-6822
ad...@usna.edu
http://www.usna.edu/Users/cs/adina/


Incubator podling reports due today

2019-09-03 Thread Justin Mclean
Hi,

Reports are due today, and these podlings are still yet to report and I cannot 
see a report being worked on:
Amaterasu*
Marvin-AI
Omid
PonyMail
SINGA
Spot
Superset
Tamaya*
Taverna
Tephra
Warble

* did not report last month. 

Good to see Toree reports who didn't report last month.

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



Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

2019-09-03 Thread Byung-Gon Chun
If SIGNA started as a university project, which is likely, I think the
university should sign SGA.

I'm a mentor of Nemo (donated from a university project). I helped the Nemo
community file SGA.

Best,
Gon

On Wed, Sep 4, 2019 at 5:51 AM Alan Gates  wrote:

> If I understand correctly, anytime software is brought into Apache as part
> of the incubating process there must be documentation from the previous
> owner of that software stating that they are donating it to Apache.
> Without that Apache's ownership of the code is not clear.  Justin, Dave,
> others, please correct me if this understanding is wrong.
>
> And clearly there was code imported into Apache when Singa entered the
> incubator, since an existing github link (now defunct) is referenced in
> Singa's incubator proposal[1].
>
> So I don't believe that an affirmation from PPMC that no docs are necessary
> is sufficient.  I believe we need a code grant from whoever owned that code
> previously.
>
> Alan.
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal see
> the section on initial source.
>
> On Mon, Sep 2, 2019 at 12:29 AM Justin Mclean  wrote:
>
> > Hi,
> >
> > > The PPMC reached a conclusion on the discussion [1] that there is no
> need
> > > for SGA.
> >
> > The link referred to doesn't give a reason why one is not required. Why
> > was it decided that it wasn’t needed? Even if it not required (which I’m
> > not 100% sure that is the case), would it be difficult to get one? If so
> > why is that?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
Byung-Gon Chun


Re: [PROPOSAL] MetaObjects for Apache Incubator

2019-09-03 Thread Justin Mclean
Hi,

> Cengage wishes to donate the code to Apache, but is unable to do so until the 
> project is accepted as an Incubator project. 

Could you expand a little on why is that?

> The Apache community members looking to approve the project understandably 
> would like to better understand what they are approving and so would like to 
> get access to the code which is to be donated.

I don’t see this a being a big issue, the other code can be donated later, but 
may complicate things in terms of SGAs, ICLAs and IP provenance.

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



Re: [DISCUSS] Graduate Apache Rya (incubating) as a TLP

2019-09-03 Thread Justin Mclean
Hi,

Just out of interest what is the diversity (in terms of company affiliation) of 
the proposed PMC like?

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



Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

2019-09-03 Thread Alan Gates
If I understand correctly, anytime software is brought into Apache as part
of the incubating process there must be documentation from the previous
owner of that software stating that they are donating it to Apache.
Without that Apache's ownership of the code is not clear.  Justin, Dave,
others, please correct me if this understanding is wrong.

And clearly there was code imported into Apache when Singa entered the
incubator, since an existing github link (now defunct) is referenced in
Singa's incubator proposal[1].

So I don't believe that an affirmation from PPMC that no docs are necessary
is sufficient.  I believe we need a code grant from whoever owned that code
previously.

Alan.

1. https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal see
the section on initial source.

On Mon, Sep 2, 2019 at 12:29 AM Justin Mclean  wrote:

> Hi,
>
> > The PPMC reached a conclusion on the discussion [1] that there is no need
> > for SGA.
>
> The link referred to doesn't give a reason why one is not required. Why
> was it decided that it wasn’t needed? Even if it not required (which I’m
> not 100% sure that is the case), would it be difficult to get one? If so
> why is that?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [PROPOSAL] MetaObjects for Apache Incubator

2019-09-03 Thread Nygard, Carl J
Justin,

I'm running into a bit of chicken/egg problem in terms of process for donating 
source code.  

To frame the problem:  Part of the code is already released as open-source, 
which is available in the github repository.  Part of the code is yet to be 
released since it was developed internally by Cengage.  Cengage wishes to 
donate the code to Apache, but is unable to do so until the project is accepted 
as an Incubator project.  The Apache community members looking to approve the 
project understandably would like to better understand what they are approving 
and so would like to get access to the code which is to be donated.

I'm sure you've seen similar issues in the past and I'm looking for some 
advice/options to be able to move forward.

--carl



From: Justin Mclean 
Sent: Tuesday, July 30, 2019 4:35 AM
To: general@incubator.apache.org 
Subject: Re: [PROPOSAL] MetaObjects for Apache Incubator

 Hi,

> Currently most development is happening within Cengage.  The core library 
> hasn't changed much, aside from some bug fixes.  Most of the recent 
> innovation has occurred in other libraries built upon the draagon-metaobjects 
> foundations.  That code is part of
 what is proposed to be donated to the apache-metaobjects project.

Thanks for that, I still a little unclear what code base is being donated. I’m 
just asking as that may make the IP transfers process easier or harder, you 
might have to get ICLA from people who have worked on it in the past for 
instance.

> Regarding the mentor list, I saw the Apache committer list included Heath, 
> but misunderstood that being a committer did not imply ASF membership, which 
> was my mistake.  However, Johan Edstrom and James Carman are members of the 
> IPMC, and Jamie mentioned to
 me that he has requested IPMC membership as well.  In addition, James has 
mentored a few projects in the past.  We would welcome another mentor if anyone 
is interested in helping build a community around the project.

I think it would be best for a project if you had an mentor with some more 
experience. It can be difficult if you mentors go missing or if they may not be 
familiar with recent changes in infrastructure or the incubator.

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



Re: [DISCUSS] Graduate Apache Rya (incubating) as a TLP

2019-09-03 Thread Josh Elser
As one of their mentors, the community as been doing a great job of 
steering themselves for some time now (year+). I've prodded them a bit 
to start this process, and I'm super excited to see them working towards 
graduation now.


They have my +1

- Josh

On 8/31/19 7:16 PM, Adina Crainiceanu wrote:

The Apache Rya (incubating) community would like to start the discussion on
general@ about graduating to a top level project.

-We completed all the tasks documented in the status file [1]
-The name Apache Rya was approved by the Brand Management COmmittee [2]
-We had four Apache releases with three different release managers
-Our community grew during incubation and we learned to function following
the Apache Way
-We discussed on the dev@ list about our readiness for graduation [3], we
voted [4], and the result of the vote was positive [5]
-We went through the process of assessing our project against the Apache
Maturity model [6] and we believe we are ready to graduate and continue to
grow as a Top Level Project.
-We worked on creating a graduation resolution and we selected a Chair [7].
The draft resolution is appended below.

Please provide your opinion on whether Rya is ready to graduate to a top
level project.

Thank you,
Adina, on behalf of Apache Rya (incubating) community

[1] https://incubator.apache.org/projects/rya.html
[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-135
[3]
https://lists.apache.org/thread.html/dd09c2060a754e69e093404e0d57239a555ab5e7d702cf76fd02f820@%3Cdev.rya.apache.org%3E
[4]
https://lists.apache.org/thread.html/10f04a55e0f6d4c09d3ffeac487b0bf309eb8e5058f950778214faeb@%3Cdev.rya.apache.org%3E
[5]
https://lists.apache.org/thread.html/d1664b17d8a6bf3d3e4e5f28382bc360fe974f1db8f880c6d97ff278@%3Cdev.rya.apache.org%3E
[6]
https://cwiki.apache.org/confluence/display/RYA/Apache+Maturity+Evaluation+for+Rya
[7]
https://lists.apache.org/thread.html/3007163bc654df45109c38b4d9a53c7b2137ad0fef660429938a282b@%3Cprivate.rya.apache.org%3E

Proposed graduation resolution:

Establish the Apache Rya Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to scalable storage, retrieval, and analysis of RDF data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Rya Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache Rya Project be and hereby is responsible for
the creation and maintenance of software related to scalable storage,
retrieval, and analysis of RDF data; and be it further

RESOLVED, that the office of "Vice President, Apache Rya" be and hereby
is created, the person holding such office to serve at the direction of
the Board of Directors as the chair of the Apache Rya Project, and to
have primary responsibility for management of the projects within the
scope of responsibility of the Apache Rya Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Rya Project:

  * Aaron Mihalik 
  * Adina Crainiceanu 
  * Billie Rinaldi
  * Caleb Meier   
  * David Lotts   
  * David Rapp
  * Jennifer Brown
  * Josh Elser
  * Puja Valiyil  
  * Roshan Punnoose   
  * Steve R Wagner

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina Crainiceanu be
appointed to the office of Vice President, Apache Rya, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the Apache Rya Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Rya podling; and
be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Rya podling encumbered upon the Apache Incubator PMC are hereafter
discharged.



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



Re: IP Clearance Process for Incubating projects

2019-09-03 Thread York Shen
Thanks, that’s clear enough for me.

> 在 2019年9月3日,19:10,Justin Mclean  写道:
> 
> Hi,
> 
>> There is another question during the donation. If some contributors of the 
>> donated code repo already signed ICLA in other projects, do they have to 
>> submit ICLA again for the new project? My understanding is that they don’t.
> 
> Correct, they do not, one ICLA for the ASF is enough, it’s not required per 
> project or per donation.
> 
> 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



Re: IP Clearance Process for Incubating projects

2019-09-03 Thread Justin Mclean
Hi,

> There is another question during the donation. If some contributors of the 
> donated code repo already signed ICLA in other projects, do they have to 
> submit ICLA again for the new project? My understanding is that they don’t.

Correct, they do not, one ICLA for the ASF is enough, it’s not required per 
project or per donation.

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



Re: IP Clearance Process for Incubating projects

2019-09-03 Thread York Shen
Thanks.

There is another question during the donation. If some contributors of the 
donated code repo already signed ICLA in other projects, do they have to submit 
ICLA again for the new project? My understanding is that they don’t.

Best Regards,
York Shen

申远

> 在 2019年9月2日,23:54,Matt Sicker  写道:
> 
> Don’t forget to file the forms with the secretary.
> 
> On Mon, Sep 2, 2019 at 04:53, York Shen  wrote:
> 
>>> Just to be clear the ICLAs need to be be from all the contributors, not
>> just one person.
>> 
>> Understood, that’s why I use plural form of ICLAs.
>> 
>> I shall collected ICLAs/SGAs and send them to the mailing list by the end
>> of this weekend if everything is fine. But I’m confused about what I shall
>> do next to transfer those Git repo to ASF, maybe creating a JIRA issue to
>> INFRA?
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远
>> 
>>> 在 2019年9月2日,17:43,Justin Mclean  写道:
>>> 
>>> Just to be clear the ICLAs need to be be from all the contributors, not
>> just one person.
>> 
>> --
> Matt Sicker 



Adding two new committers to Apache Druid (incubating)

2019-09-03 Thread Roman Leventov
Apache Druid (incubating) PMC voted to accept two new committers: Fokko
Driesprong (
https://mail-search.apache.org/pmc/private-arch/druid-private/201909.mbox/%3CCAAMLo%3Da-zYUdQdfvAKX7F-DnO%3Do0uySmwfyjmd6gfaRC-W4Q%2Bw%40mail.gmail.com%3E)
and Furkan Kamaci (
https://mail-search.apache.org/pmc/private-arch/druid-private/201909.mbox/%3CCAAMLo%3DZRW_5FaUQsSq%3D-7fThQJPujX-UR67_dpzzH3JSUEVhxg%40mail.gmail.com%3E).
They are committers to other Apache projects (their Apache IDs are fokko
and kamaci, respectively). I think we now need assistance from the
Incubator PMC Chair to grant them access to Druid's repositories:
incubator-druid, incubator-druid-website, and incubator-druid-website-src.

Thanks.