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.
