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
