Re: incubator report for November - please comment

[Adina Crainiceanu <ad...@usna.edu>]

Thank you for all the comments. Below is a revised version. Please feel
free to modify it as you see fit, or comment.

To answer some of the questions:
-The presentation at Duke: I was invited to give a talk in the database
group at Duke Computer Science Department, and I talked about Rya. I did
not think about advertising it on the dev list - I'll do that next time.
The presentation was not recorded, but we can post the slides on the
website, once we have one.
-Biggest roadblock to a fist release: I think it is our lack of familiarity
with the process, so I think we need to become familiar with it. This is
what I found http://incubator.apache.org/guides/releasemanagement.html. Is
there another place we should look?

Thank you,
Adina

==============
Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system built
on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
processing techniques that scale to billions of triples across multiple
nodes.
Rya provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:

  1. Populate the website for the project
  2. Become familiar with the release process and have a first release as
part of the Apache
  3. Create a "how to" document to explain the ways new contributors can
become involved in the project, so we increase the size of the community.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

No

How has the community developed since the last report?

All initial committers submitted their ICLAs and are subscribed to the dev
and private mailing lists. There are 32 subscribers to the dev list.
The initial committers are learning to use the Apache infrastructure and
processes.
We gave a presentation on Rya at Duke University, trying to increase
awareness about the project.

How has the project developed since the last report?

Infrastructure is now set up (mailing lists, repositories, JIRA, etc)
Getting the code reviewed for final publication took about 3 weeks, which
was longer than we expected, but the code is now imported into the Apache
git repository.
We are working on creating a website for the project.

Date of last release:

  Not applicable - the code was just imported into Apache repository

When were the last committers or PMC members elected?

 Not applicable

Signed-off-by:

  [ ](rya) Josh Elser
  [ ](rya) Edward J. Yoon
  [ ](rya) Sean Busbey
  [ ](rya) Venkatesh Seetharam

Shepherd/Mentor notes:




On Sat, Oct 31, 2015 at 4:16 PM, Josh Elser <jo...@gmail.com> wrote:

>
>
> Sean Busbey wrote:
>
>> How has the project developed since the last report?
>>> >
>>> >  Infrastructure is set up (mailing lists, repositories, JIRA, etc)
>>>
>>
>> Have a subscriber count for dev@ handy? did we make a user list?
>>
>
> No user list yet. Currently 32 subscribers to dev@rya (moderators can
> send a msg to dev-list@rya to get this info).
>



-- 
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/

Re: incubator report for November - please comment

[Adina Crainiceanu <ad...@usna.edu>]

All,

The Rya report is now at https://wiki.apache.org/incubator/November2015

Thank you,
Adina

On Mon, Nov 2, 2015 at 12:20 PM, Josh Elser <jo...@gmail.com> wrote:

> Adina Crainiceanu wrote:
>
>> Thank you for all the comments. Below is a revised version. Please feel
>> free to modify it as you see fit, or comment.
>>
>
> Also, looks good. You should feel free to post it on the report on the
> wiki -- the mentors will likely reread before signing off anyways.
>



-- 
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/

Re: incubator report for November - please comment

[Josh Elser <jo...@gmail.com>]

Adina Crainiceanu wrote:
> Thank you for all the comments. Below is a revised version. Please feel
> free to modify it as you see fit, or comment.

Also, looks good. You should feel free to post it on the report on the 
wiki -- the mentors will likely reread before signing off anyways.

Re: incubator report for November - please comment

[Josh Elser <jo...@gmail.com>]

Josh Elser wrote:
> Puja Valiyil wrote:
>> All,
>> We (David Lotts and I) were going to start working on updating the
>> license
>> headers this week. Do we just run the perl scripts referenced here:
>> http://www.apache.org/legal/src-headers.html
>> Is there anything else we should do? I think that Adina already vetted
>> the
>> dependencies. I'd like to get us on the path to cutting our first apache
>> release -- we've been waiting to check some things in until the apache
>> repo
>> is in a good place, and I'd like to just put some of these things to bed.
>
> However you want to skin that cat. Any text manipulation tool (even
> IDEs) has the ability to add the proper header. Getting the LICENSE and
> NOTICE files correct will be more work. If you include any convenience
> artifacts (binary -- e.g. jars) in the release outside of the
> source-release, these are also subject to scrutiny.
>
> Vetting dependencies gets tricky -- this will take some time to get
> correct and will always requires the project's attention. The bar as an
> incubating project is lower than that of a top-level project (TLP) in
> that incubator releases typically need not be 100% correct, but the
> intent is that, as a project, you make forward progress here and
> understand how to apply the ASL and follow ASF policy by the time you
> graduation.
>
> I've tried to condense the information on what I know here[1], and I
> know NiFi also has a great resource [2]. Hopefully these are easier
> applied and concentrated than the foundation-level docs.
>
>
>> Also, is there documentation about what paperwork needs to be filled
>> out to
>> commit changes to Rya?
>
> This is a very important thing to understand here (I apologize for the
> incoming strong wording).
>
> The Apache Software Foundation does _not_ deal in terms of companies.
> Individuals contribute to the ASF. The only reason that companies are at
> all in the picture is because, sometimes, individuals do not always own
> the code that they write. All committers must have a document filed that
> states they donate the copyright on the work they make to the ASF by way
> of the ICLA (as all the committers have already done -- hopefully those
> of you with agreements on copyright with your companies have filed the
> necessary CCLAs). Committers whose companies own the code they wish to
> add to Rya must also have their company file a CCLA. The ICLA and CCLA
> serve the same purpose (copyright assignment to the ASF); the only
> difference is that one is for individuals the other for companies.
>
>> There are some other companies we work with that
>> would like to start committing their changes directly.
>
> This sounds like you're not familiar with the model of roles at the ASF
> [3]. Please start there.
>
> The initial set of committers (and mentors) are the only ones with write
> access to the codebase. Everyone else is a contributor who sends you
> patches/pull-requests which a committer must vet and commit on their
> behalf. At this stage in Rya's lifetime, you want to grow the project by
> attracting contributors, making sure they understand how Rya "does
> business", and then, after some time, adding them as committers to do
> the same (and repeat). The PMC role gets important later, but we can
> cross that bridge later, IMO.

Forgot to add the actual foundation docs for CLAs 
http://www.apache.org/licenses/#clas. It's rather straightforward.

>
> [1]
> http://accumulo.apache.org/verifying_releases.html#apache-software-license-application
>
> [2] https://nifi.apache.org/licensing-guide.html
> [3] http://www.apache.org/foundation/how-it-works.html#roles

Re: incubator report for November - please comment

[Josh Elser <jo...@gmail.com>]

Puja Valiyil wrote:
> All,
> We (David Lotts and I) were going to start working on updating the license
> headers this week.  Do we just run the perl scripts referenced here:
> http://www.apache.org/legal/src-headers.html
> Is there anything else we should do?  I think that Adina already vetted the
> dependencies.   I'd like to get us on the path to cutting our first apache
> release -- we've been waiting to check some things in until the apache repo
> is in a good place, and I'd like to just put some of these things to bed.

However you want to skin that cat. Any text manipulation tool (even 
IDEs) has the ability to add the proper header. Getting the LICENSE and 
NOTICE files correct will be more work. If you include any convenience 
artifacts (binary -- e.g. jars) in the release outside of the 
source-release, these are also subject to scrutiny.

Vetting dependencies gets tricky -- this will take some time to get 
correct and will always requires the project's attention. The bar as an 
incubating project is lower than that of a top-level project (TLP) in 
that incubator releases typically need not be 100% correct, but the 
intent is that, as a project, you make forward progress here and 
understand how to apply the ASL and follow ASF policy by the time you 
graduation.

I've tried to condense the information on what I know here[1], and I 
know NiFi also has a great resource [2]. Hopefully these are easier 
applied and concentrated than the foundation-level docs.


> Also, is there documentation about what paperwork needs to be filled out to
> commit changes to Rya?

This is a very important thing to understand here (I apologize for the 
incoming strong wording).

The Apache Software Foundation does _not_ deal in terms of companies. 
Individuals contribute to the ASF. The only reason that companies are at 
all in the picture is because, sometimes, individuals do not always own 
the code that they write. All committers must have a document filed that 
states they donate the copyright on the work they make to the ASF by way 
of the ICLA (as all the committers have already done -- hopefully those 
of you with agreements on copyright with your companies have filed the 
necessary CCLAs). Committers whose companies own the code they wish to 
add to Rya must also have their company file a CCLA. The ICLA and CCLA 
serve the same purpose (copyright assignment to the ASF); the only 
difference is that one is for individuals the other for companies.

> There are some other companies we work with that
> would like to start committing their changes directly.

This sounds like you're not familiar with the model of roles at the ASF 
[3]. Please start there.

The initial set of committers (and mentors) are the only ones with write 
access to the codebase. Everyone else is a contributor who sends you 
patches/pull-requests which a committer must vet and commit on their 
behalf. At this stage in Rya's lifetime, you want to grow the project by 
attracting contributors, making sure they understand how Rya "does 
business", and then, after some time, adding them as committers to do 
the same (and repeat). The PMC role gets important later, but we can 
cross that bridge later, IMO.


[1] 
http://accumulo.apache.org/verifying_releases.html#apache-software-license-application
[2] https://nifi.apache.org/licensing-guide.html
[3] http://www.apache.org/foundation/how-it-works.html#roles

Re: incubator report for November - please comment

[Seetharam Venkatesh <ve...@innerzeal.com>]

I have used apache-rat plugin and works quite well.

On Mon, Nov 16, 2015 at 7:16 AM Puja Valiyil <pu...@gmail.com> wrote:

> All,
> We (David Lotts and I) were going to start working on updating the license
> headers this week.  Do we just run the perl scripts referenced here:
> http://www.apache.org/legal/src-headers.html
> Is there anything else we should do?  I think that Adina already vetted the
> dependencies.   I'd like to get us on the path to cutting our first apache
> release -- we've been waiting to check some things in until the apache repo
> is in a good place, and I'd like to just put some of these things to bed.
>
> Also, is there documentation about what paperwork needs to be filled out to
> commit changes to Rya?  There are some other companies we work with that
> would like to start committing their changes directly.
>
> Thanks,
> Puja
>
> On Mon, Nov 2, 2015 at 12:17 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > Adina Crainiceanu wrote:
> >
> >> To answer some of the questions:
> >> -The presentation at Duke: I was invited to give a talk in the database
> >> group at Duke Computer Science Department, and I talked about Rya. I did
> >> not think about advertising it on the dev list - I'll do that next time.
> >> The presentation was not recorded, but we can post the slides on the
> >> website, once we have one.
> >>
> >
> > Sounds great :)
> >
> > -Biggest roadblock to a fist release: I think it is our lack of
> familiarity
> >> with the process, so I think we need to become familiar with it. This is
> >> what I foundhttp://incubator.apache.org/guides/releasemanagement.html.
> Is
> >> there another place we should look?
> >>
> >
> > That's a good reference (although, rather daunting to look at).
> >
> > The things that are probably going to be most relevant:
> >
> > * Applying the ASLv2 to the code
> > ** License headers on files
> > ** Vetting Rya dependencies as being ASLv2 compatible
> > * Creating a source-only release (user can download something and build
> > Rya themselves, tests typically included)
> > * Adopt the Apache parent pom (this will help in automating the release
> > process).
> > * Document the release process _now_ (well, maybe once the site is made
> :D)
> >
> > There will likely be some more INFRA asks (setting up space on dist.a.o
> > comes to mind), but we can deal with those as they arise.
> >
>

Re: incubator report for November - please comment

[Puja Valiyil <pu...@gmail.com>]

All,
We (David Lotts and I) were going to start working on updating the license
headers this week.  Do we just run the perl scripts referenced here:
http://www.apache.org/legal/src-headers.html
Is there anything else we should do?  I think that Adina already vetted the
dependencies.   I'd like to get us on the path to cutting our first apache
release -- we've been waiting to check some things in until the apache repo
is in a good place, and I'd like to just put some of these things to bed.

Also, is there documentation about what paperwork needs to be filled out to
commit changes to Rya?  There are some other companies we work with that
would like to start committing their changes directly.

Thanks,
Puja

On Mon, Nov 2, 2015 at 12:17 PM, Josh Elser <jo...@gmail.com> wrote:

> Adina Crainiceanu wrote:
>
>> To answer some of the questions:
>> -The presentation at Duke: I was invited to give a talk in the database
>> group at Duke Computer Science Department, and I talked about Rya. I did
>> not think about advertising it on the dev list - I'll do that next time.
>> The presentation was not recorded, but we can post the slides on the
>> website, once we have one.
>>
>
> Sounds great :)
>
> -Biggest roadblock to a fist release: I think it is our lack of familiarity
>> with the process, so I think we need to become familiar with it. This is
>> what I foundhttp://incubator.apache.org/guides/releasemanagement.html. Is
>> there another place we should look?
>>
>
> That's a good reference (although, rather daunting to look at).
>
> The things that are probably going to be most relevant:
>
> * Applying the ASLv2 to the code
> ** License headers on files
> ** Vetting Rya dependencies as being ASLv2 compatible
> * Creating a source-only release (user can download something and build
> Rya themselves, tests typically included)
> * Adopt the Apache parent pom (this will help in automating the release
> process).
> * Document the release process _now_ (well, maybe once the site is made :D)
>
> There will likely be some more INFRA asks (setting up space on dist.a.o
> comes to mind), but we can deal with those as they arise.
>

Re: incubator report for November - please comment

[Josh Elser <jo...@gmail.com>]

Adina Crainiceanu wrote:
> To answer some of the questions:
> -The presentation at Duke: I was invited to give a talk in the database
> group at Duke Computer Science Department, and I talked about Rya. I did
> not think about advertising it on the dev list - I'll do that next time.
> The presentation was not recorded, but we can post the slides on the
> website, once we have one.

Sounds great :)

> -Biggest roadblock to a fist release: I think it is our lack of familiarity
> with the process, so I think we need to become familiar with it. This is
> what I foundhttp://incubator.apache.org/guides/releasemanagement.html. Is
> there another place we should look?

That's a good reference (although, rather daunting to look at).

The things that are probably going to be most relevant:

* Applying the ASLv2 to the code
** License headers on files
** Vetting Rya dependencies as being ASLv2 compatible
* Creating a source-only release (user can download something and build 
Rya themselves, tests typically included)
* Adopt the Apache parent pom (this will help in automating the release 
process).
* Document the release process _now_ (well, maybe once the site is made :D)

There will likely be some more INFRA asks (setting up space on dist.a.o 
comes to mind), but we can deal with those as they arise.

Re: incubator report for November - please comment

[Sean Busbey <bu...@apache.org>]

Looks good to me. Thanks!
On Nov 1, 2015 8:37 PM, "Adina Crainiceanu" <ad...@usna.edu> wrote:

> Thank you for all the comments. Below is a revised version. Please feel
> free to modify it as you see fit, or comment.
>
> To answer some of the questions:
> -The presentation at Duke: I was invited to give a talk in the database
> group at Duke Computer Science Department, and I talked about Rya. I did
> not think about advertising it on the dev list - I'll do that next time.
> The presentation was not recorded, but we can post the slides on the
> website, once we have one.
> -Biggest roadblock to a fist release: I think it is our lack of familiarity
> with the process, so I think we need to become familiar with it. This is
> what I found http://incubator.apache.org/guides/releasemanagement.html. Is
> there another place we should look?
>
> Thank you,
> Adina
>
> ==============
> Rya
>
> Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
> supports SPARQL queries. Rya is a scalable RDF data management system built
> on
> top of Accumulo. Rya uses novel storage methods, indexing schemes, and
> query
> processing techniques that scale to billions of triples across multiple
> nodes.
> Rya provides fast and easy access to the data through SPARQL, a
> conventional
> query mechanism for RDF data.
>
> Rya has been incubating since 2015-09-18.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Populate the website for the project
>   2. Become familiar with the release process and have a first release as
> part of the Apache
>   3. Create a "how to" document to explain the ways new contributors can
> become involved in the project, so we increase the size of the community.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
>
> No
>
> How has the community developed since the last report?
>
> All initial committers submitted their ICLAs and are subscribed to the dev
> and private mailing lists. There are 32 subscribers to the dev list.
> The initial committers are learning to use the Apache infrastructure and
> processes.
> We gave a presentation on Rya at Duke University, trying to increase
> awareness about the project.
>
> How has the project developed since the last report?
>
> Infrastructure is now set up (mailing lists, repositories, JIRA, etc)
> Getting the code reviewed for final publication took about 3 weeks, which
> was longer than we expected, but the code is now imported into the Apache
> git repository.
> We are working on creating a website for the project.
>
> Date of last release:
>
>   Not applicable - the code was just imported into Apache repository
>
> When were the last committers or PMC members elected?
>
>  Not applicable
>
> Signed-off-by:
>
>   [ ](rya) Josh Elser
>   [ ](rya) Edward J. Yoon
>   [ ](rya) Sean Busbey
>   [ ](rya) Venkatesh Seetharam
>
> Shepherd/Mentor notes:
>
>
>
>
> On Sat, Oct 31, 2015 at 4:16 PM, Josh Elser <jo...@gmail.com> wrote:
>
> >
> >
> > Sean Busbey wrote:
> >
> >> How has the project developed since the last report?
> >>> >
> >>> >  Infrastructure is set up (mailing lists, repositories, JIRA, etc)
> >>>
> >>
> >> Have a subscriber count for dev@ handy? did we make a user list?
> >>
> >
> > No user list yet. Currently 32 subscribers to dev@rya (moderators can
> > send a msg to dev-list@rya to get this info).
> >
>
>
>
> --
> Dr. Adina Crainiceanu
> http://www.usna.edu/Users/cs/adina/
>