Re: Josh's weekly pestering

[Seetharam Venkatesh]

We use maven generated docs with doxia plugin and works well. You'd need to 
maintain a twiki style docs and maven provides a lot of skins for website 
generation. 

Sent from my iPhone,
Venkatesh

> On Oct 26, 2015, at 7:06 PM, Josh Elser  wrote:
> 
> Cool. Thanks for the update, Adina. Would be great to hear from Puja or Aaron.
> 
> Some projects use a the Maven-generated site, some projects use Markdown and 
> CMS [1], and some projects just use static-site generation tools like Jekyll.
> 
> Personally, I'd advocate either of the latter two, favoring the third. I 
> think infra is slowly moving towards static site generation tools over CMS, 
> but the ability to use your web-browser to update the site is nice for easy 
> changes.
> 
> [1] http://www.apache.org/dev/project-site.html
> 
> Adina Crainiceanu wrote:
>> I know Puja is working on getting the code cleaned up for import.
>> Maybe Puja or Aaron have suggestions for documents to go on JIRA or Wiki?
>> 
>> Another big thing we need is a website with information on it. Are there
>> any suggestions where to start from? Is there a template for the Apache
>> projects sites? Any suggestions for tools to generate the site (or just
>> write HTML)?
>> 
>> Thanks,
>> Adina
>> 
>>> On Sat, Oct 24, 2015 at 4:39 PM, Josh Elser  wrote:
>>> 
>>> I'm doing my regular "catch up on the rest of the world" and am trying to
>>> remember where we currently stand.
>>> 
>>> All necessary parties should have Apache accounts and everyone should have
>>> the necessary karma to commit.
>>> 
>>> The next big thing on my mind is getting the code imported. *Puja*, have
>>> you made any progress here?
>>> 
>>> Do the initial committers (as listed on the incubator proposal) have any
>>> other project planning documents that should go into JIRA or a Wiki?
>>> 
>>> - JOsh
>> 
>> 
>> 

Fwd: Google Summer of Code 2016 is coming

[Seetharam Venkatesh]

Hi folks,

This is a very good opportunity to welcome additional contributors to the
project.

Thanks!
Venkatesh

-- Forwarded message -
From: Ulrich Stärk 
Date: Wed, Feb 10, 2016 at 12:17 PM
Subject: Google Summer of Code 2016 is coming
To: 


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and project
ideas, and in return have
the chance to get new code developed and - most importantly - to identify
and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply
separately.

If you want to participate with your project we ask you to do the following
things as soon as
possible but by no later than 2016-02-19:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2016, and they will show up
at [3]. Please be as
specific as possible when describing your idea. Include the programming
language, the tools and
skills required, but try not to scare potential students away. They are
supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...) and record them at [5].

Please use the COMDEV JIRA project for recording your ideas if your project
doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2016 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public d...@community.apache.org
list as much as possible
please). Use a recognized address when subscribing (@apache.org or one of
your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we will not get accepted.

Over the years we were able to complete hundreds of projects successfully.
Some of our prior
students are active contributors now! Let's make this year a success again!

Cheers,

Uli

P.S.: Except for the private parts (label spreadsheet mostly), this email
is free to be shared
publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2016ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels

Re: Looking towards our next IPMC report

[Seetharam Venkatesh]

Thanks Adina, report looks good. There are quite a few low hanging issues
that can be addressed quickly.

> Become familiar with the release process and have a first release as part
of the Apache Foundation
I have done about 5 incubating releases and can help if someone can
volunteer as an RM. This is not hard and its an easy win for a podling.

> Expand the "how to" document to explain the ways new contributors can
become involved in the project
This can start simple and can be iterated. You can also look at what other
incubating projects are doing.

> We have a Rya "office hour" teleconference every other week
Can you also please put this on the confluence wiki so its accessible.

Thanks!
Venkatesh

On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu <ad...@usna.edu> wrote:

> I submitted the report. Sorry for waiting till the last minute - I wanted
> to have a website first :)
>
> Thank you,
> Adina
>
> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh <
> venkat...@innerzeal.com
> > wrote:
>
> > Hey folks, the report is to be signed off today and I do not see it being
> > filled at http://wiki.apache.org/incubator/April2016.
> >
> > Appreciate if one of you could take care of this asap.
> >
> > Thanks!
> > Venkatesh
> >
> > On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey <bus...@apache.org> wrote:
> >
> > > For those interested in posting feedback, the website jira is RYA-42
> > >
> > > On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu <ad...@usna.edu>
> > wrote:
> > > > I created a JIRA ticket for the website. If anyone has specific ideas
> > for
> > > > it, please fell free to mention/implement them. Otherwise I'll try to
> > > > use/customize the apache-website-template available at
> > > > https://github.com/apache/apache-website-template/ as soon as
> > possible,
> > > but
> > > > definitely before the next report is due
> > > >
> > > > Adina
> > > >
> > > > On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <puja...@gmail.com>
> > > wrote:
> > > >
> > > >> David and I tried to compile a process for creating a release -- we
> > > didn't
> > > >> get that far.  The main thing blocking us at this point is the whole
> > > >> process for signing a release, no one we knew had a public key and
> > then
> > > >> David and I got lost/confused when trying to generate and register
> > one.
> > > >> All of this sounds borderline embarrassing since there is a lot of
> > > >> documentation out there but we didn't have time to fully digest it
> in
> > > >> time.
> > > >> I'm also not clear on what else we would need to do besides run mvn
> > > >> release, like compile release notes, etc.  I'm sorry if there's a
> lot
> > of
> > > >> documentation exactly detailing what we need to do.
> > > >> Other than that, I think we've made a lot of progress as a community
> > > this
> > > >> past month.  We've had a lot of new contributors, had a lot of new
> > bugs
> > > >> reported by new end users, and have closed out a lot of issues.
> > > >>
> > > >> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bus...@apache.org>
> > wrote:
> > > >>
> > > >> > Heya Rya!
> > > >> >
> > > >> > We're about 5-6 weeks from our next scheduled turn for the IPMC's
> > > board
> > > >> > report.
> > > >> >
> > > >> > How are folks doing? The project sounds a bit quiet to me, but I'm
> > not
> > > >> > sure how much of that is me being sure to look in the right
> places.
> > > >> >
> > > >> > To Review, here are your self-identified three most important
> > > objectives:
> > > >> >
> > > >> >   1. Populate the website for the project
> > > >> >   2. Expand the "how to" document to explain the ways new
> > contributors
> > > >> can
> > > >> >  become involved in the project, so we increase the size of
> the
> > > >> >  community.
> > > >> >   3. Become familiar with the release process and have a first
> > > release as
> > > >> >  part of the Apache Foundation
> > > >> >
> > > >> > At least to me, numbers 1 and 3 seem like big barriers to getting
> > new
> > > >> > folks brought in. Anyone have a list of the blockers keeping us
> from
> > > >> > those two? I tried searching the jira for relevant tickets, but
> > didn't
> > > >> > find any.
> > > >> >
> > > >> > -Sean
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Dr. Adina Crainiceanu
> > > > http://www.usna.edu/Users/cs/adina/
> > >
> >
>
>
>
> --
> Dr. Adina Crainiceanu
> http://www.usna.edu/Users/cs/adina/
>

Re: Looking towards our next IPMC report

[Seetharam Venkatesh]

I have followed this and have been quite successful, thanks to Jarec for
putting this together.
https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2

Thanks!

On Thu, Apr 7, 2016 at 9:00 AM Sean Busbey <bus...@apache.org> wrote:

> So long as we're plugging other project release guides ;)
>
> http://yetus.apache.org/contribute/releases/
>
> On Thu, Apr 7, 2016 at 8:18 AM, Josh Elser <josh.el...@gmail.com> wrote:
> > Yay. If I can offer my $0.02:
> >
> > * As you go through the process the first time, update the website
> > immediately. Every little step you do, write it down (this will make sure
> > that you're not the only person to be able to make a release).
> > * Automate as much as you possibly can. Ideally, your process should be
> `mvn
> > release:prepare && mvn release:perform` as a Maven project.
> > * Try to take some help from other projects [1], [2], [3] for starters.
> > * Ask questions if you get stuck :)
> >
> > - Josh
> >
> > [1] http://accumulo.apache.org/releasing.html
> > [2] http://accumulo.apache.org/verifying_releases.html
> > [3] http://nifi.apache.org/release-guide.html
> >
> >
> > Aaron D. Mihalik wrote:
> >>
> >> Josh/Venkatesh: I'll take RM for our first release. David put a lot of
> >> effort in researching this process, so I'll look through his notes over
> >> the
> >> weekend, start the process, and ping the dev list with questions.
> >>
> >> Thanks again for your help.
> >>
> >> --Aaron
> >> On Wed, Apr 6, 2016 at 5:55 PM Josh Elser<josh.el...@gmail.com>  wrote:
> >>
> >>> +1 to Venkatesh's overall message (if I can put words in mouths): don't
> >>> get too hung up on "perfect the first time". Showing progress is much
> >>> more important.
> >>>
> >>> Seetharam Venkatesh wrote:
> >>>>
> >>>> Thanks Adina, report looks good. There are quite a few low hanging
> >>>> issues
> >>>> that can be addressed quickly.
> >>>>
> >>>>> Become familiar with the release process and have a first release as
> >>>
> >>> part
> >>>>
> >>>> of the Apache Foundation
> >>>> I have done about 5 incubating releases and can help if someone can
> >>>> volunteer as an RM. This is not hard and its an easy win for a
> podling.
> >>>>
> >>>>> Expand the "how to" document to explain the ways new contributors can
> >>>>
> >>>> become involved in the project
> >>>> This can start simple and can be iterated. You can also look at what
> >>>
> >>> other
> >>>>
> >>>> incubating projects are doing.
> >>>>
> >>>>> We have a Rya "office hour" teleconference every other week
> >>>>
> >>>> Can you also please put this on the confluence wiki so its accessible.
> >>>>
> >>>> Thanks!
> >>>> Venkatesh
> >>>>
> >>>> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
> >>>
> >>> wrote:
> >>>>>
> >>>>> I submitted the report. Sorry for waiting till the last minute - I
> >>>
> >>> wanted
> >>>>>
> >>>>> to have a website first :)
> >>>>>
> >>>>> Thank you,
> >>>>> Adina
> >>>>>
> >>>>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
> >>>>> venkat...@innerzeal.com
> >>>>>>
> >>>>>> wrote:
> >>>>>> Hey folks, the report is to be signed off today and I do not see it
> >>>
> >>> being
> >>>>>>
> >>>>>> filled at http://wiki.apache.org/incubator/April2016.
> >>>>>>
> >>>>>> Appreciate if one of you could take care of this asap.
> >>>>>>
> >>>>>> Thanks!
> >>>>>> Venkatesh
> >>>>>>
> >>>>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bus...@apache.org>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> For those interested in posting feedback, the website jira is
> RYA-42
> >>>>>>>
> >>>>>>> On Wed, Feb

Re: [DISCUSS] Path forward for release

[Seetharam Venkatesh]

Quick question - geotools is a runtime dependency? Are you shipping the source 
code? If not, you should be okay. 

Sent from my iPhone,
Venkatesh

> On Oct 6, 2016, at 7:52 AM, Puja Valiyil  wrote:
> 
> Hi everyone,
> Talking with Aaron, it seems like there were two paths forward for
> refactoring in order to create a release.  To refresh everyone's memory,
> the issue was that the geo-indexing extensions to Rya pull in geotools,
> which prohibits us from releasing Rya under an Apache 2 license.  There may
> be some more particulars that I'm glossing over -- someone please chime in
> if they feel it is key to the discussion.
> The two paths forward we had were:
> 1.  Make all of the indexing project and its downstream dependencies
> optional and exclude them from a release
> -- The indexing project includes several "optional" extensions to Rya
> (advanced indexing strategies).  Prior to Rya becoming an apache project,
> these indexing extensions were optional and there was a separate profile
> for including them.  This option involves reverting back to that mindset.
> The main argument against this is that these indexing strategies/extensions
> are not in fact optional but are "core" to Rya and can't be excluded.
> 
> 2.  Refactor Rya to pull geoindexing into a separate project and exclude
> that project from the release.
> - We could refactor Rya to have geoindexing be its own project and add a
> profile to include that in the build.  This would invovle moving the class
> mvm.rya.indexing.GeoIndexer and packages mem.rya.indexing.accumulo.geo and
> mvm.rya.indexing.mongodb.geo to a separate project and then removing/moving
> references to geoindexing anywhere else.  Another option is to refactor the
> GeoIndexer interface to remove the geotools dependency.
> 
> I think #1 is a good immediate path for a release and that #2 is a good
> longer term path forward.  Since it's probably in our best interests as a
> community to get an apache release sooner rather than later, I'd rather us
> go with #1 since it would quicker.  I also think that most users of Rya
> would be ok with excluding the indexing project since it is not core
> functionality for Rya.  While #2 is a better long term plan, it involves
> some pretty extensive refactoring that would be difficult to do well in a
> timely manner.
> 
> Any thoughts?

Re: [DISCUSS] Path forward for release

[Seetharam Venkatesh]

If it's a runtime dependency, you are fine. Apache only supports source 
releases. We vote on source tar ball and not binary artifacts. 

Makes sense?

Sent from my iPhone,
Venkatesh

> On Oct 6, 2016, at 12:40 PM, David Lotts <dlo...@gmail.com> wrote:
> 
> Yes, geotools is a runtime dependency.  No geotools source code is
> distributed.
> 
> By that I mean: Geotools source code is not in our source code repository.
> Only references: imports in our *.java files and dependencies entries in
> our pom.xml.   Because of this maven will package geotools JARs (binaries)
> in our shaded/uber JAR and WAR files that we distribute.
> 
> With option 1 or 2 as discussed, maven will exclude the geotools jars in
> our JARs and WARs.  Users of Rya can follow some instructions that we
> provide to add "-P indexing" (or similar) to their Maven build command
> create their own jar/war containing the optional Rya features and geotools
> binaries.
> 
> Your "you should be okay." mean which of these
> A. option 1 and option 2 will work around the issue and we should proceed
> before we release,
> - OR -
> B.  We are already in compliance and this is not a blocker for release as
> long as we are not redistributing geotools source code.
> 
> Hopeful for interpretation B, but expecting and happy with A.
> 
> david.
> 
> On Thu, Oct 6, 2016 at 1:22 PM, Seetharam Venkatesh <vseetha...@gmail.com>
> wrote:
> 
>> Quick question - geotools is a runtime dependency? Are you shipping the
>> source code? If not, you should be okay.
>> 
>> Sent from my iPhone,
>> Venkatesh
>> 
>>> On Oct 6, 2016, at 7:52 AM, Puja Valiyil <puja...@gmail.com> wrote:
>>> 
>>> Hi everyone,
>>> Talking with Aaron, it seems like there were two paths forward for
>>> refactoring in order to create a release.  To refresh everyone's memory,
>>> the issue was that the geo-indexing extensions to Rya pull in geotools,
>>> which prohibits us from releasing Rya under an Apache 2 license.  There
>> may
>>> be some more particulars that I'm glossing over -- someone please chime
>> in
>>> if they feel it is key to the discussion.
>>> The two paths forward we had were:
>>> 1.  Make all of the indexing project and its downstream dependencies
>>> optional and exclude them from a release
>>> -- The indexing project includes several "optional" extensions to Rya
>>> (advanced indexing strategies).  Prior to Rya becoming an apache project,
>>> these indexing extensions were optional and there was a separate profile
>>> for including them.  This option involves reverting back to that mindset.
>>> The main argument against this is that these indexing
>> strategies/extensions
>>> are not in fact optional but are "core" to Rya and can't be excluded.
>>> 
>>> 2.  Refactor Rya to pull geoindexing into a separate project and exclude
>>> that project from the release.
>>> - We could refactor Rya to have geoindexing be its own project and add a
>>> profile to include that in the build.  This would invovle moving the
>> class
>>> mvm.rya.indexing.GeoIndexer and packages mem.rya.indexing.accumulo.geo
>> and
>>> mvm.rya.indexing.mongodb.geo to a separate project and then
>> removing/moving
>>> references to geoindexing anywhere else.  Another option is to refactor
>> the
>>> GeoIndexer interface to remove the geotools dependency.
>>> 
>>> I think #1 is a good immediate path for a release and that #2 is a good
>>> longer term path forward.  Since it's probably in our best interests as a
>>> community to get an apache release sooner rather than later, I'd rather
>> us
>>> go with #1 since it would quicker.  I also think that most users of Rya
>>> would be ok with excluding the indexing project since it is not core
>>> functionality for Rya.  While #2 is a better long term plan, it involves
>>> some pretty extensive refactoring that would be difficult to do well in a
>>> timely manner.
>>> 
>>> Any thoughts?
>> 

Re: [VOTE] Release Apache Rya (Incubating) version 3.2.10 RC3

[Seetharam Venkatesh]

+1 (binding)

-Venkatesh

On Tue, Oct 25, 2016 at 3:04 PM Josh Elser  wrote:

> (Forwarding from ppmc)
>
> +1 (binding)
>
> Aaron D. Mihalik wrote:
> > The Apache Rya community has voted and approved the proposed release of
> > Apache Rya 3.2.10 (Incubating) RC3.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > 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 Apache 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. More
> > information can be found at http://rya.incubator.apache.org/
> >
> > [VOTE] Thread:
> >
> https://lists.apache.org/thread.html/01d692717b2ee088253fa96c42759309a2a4d2aaf9867905bc473fa7@%3Cdev.rya.apache.org%3E
> >
> > [VOTE] [RESULT] Thread:
> >
> https://lists.apache.org/thread.html/e58e7456987d74f11a0698fd5d4dde436bd83016baa269c149f03511@%3Cdev.rya.apache.org%3E
> >
> > The source zip, including signatures, digests, etc. can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3.2.10-rc3/
> >
> >
> > Ancillary artifacts such as poms, jars, wars, ect. can be found here:
> >
> https://repository.apache.org/content/repositories/orgapacherya-1004/org/apache/rya/rya-project/3.2.10-incubating/
> >
> >
> > The Git tag is rya-incubating-3.2.10-rc3
> >
> > The Git commit ID is 66d8b7f060bddeeb7c50cb0918f98ce3b265c564
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=66d8b7f060bddeeb7c50cb0918f98ce3b265c564
> >
> >
> > Checksums of rya-project-3.2.10-incubating-source-release.zip:
> > SHA1: 4468f55b9f381e9103ca1e2e9c25b30e1cad4ed0
> > MD5: a28d9a146857576903ff4fc3f7dae908
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mihalik.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
> >
> > Issues that were closed/resolved for this release are here:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334209=Html=12319020
> >
> > The vote will be open for 72 hours and closes at Fri Oct 28 16:00 EDT
> 2016.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > Then please vote:
> > [ ] +1 Release this package as rya-project-3.2.10-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
> >
> > --Aaron
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Rya (Incubating) version 3.2.10 RC3

[Seetharam Venkatesh]

+1.

Thanks!

On Thu, Oct 20, 2016 at 10:28 PM Aaron D. Mihalik 
wrote:

> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.10.
>
> The source zip, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3.2.10-rc3/
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>
> https://repository.apache.org/content/repositories/orgapacherya-1004/org/apache/rya/rya-project/3.2.10-incubating/
>
> The Git tag is rya-incubating-3.2.10-rc3
> The Git commit ID is 66d8b7f060bddeeb7c50cb0918f98ce3b265c564
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=66d8b7f060bddeeb7c50cb0918f98ce3b265c564
>
> Checksums of rya-project-3.2.10-source-release.zip:
> SHA1: 4468f55b9f381e9103ca1e2e9c25b30e1cad4ed0
> MD5: a28d9a146857576903ff4fc3f7dae908
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mihalik.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334209=Html=12319020
>
> Issues resolved between RC1 and RC2 are here:
> https://issues.apache.org/jira/browse/RYA-184
>
> Issues resolved between RC2 and RC3 are here:
> https://issues.apache.org/jira/browse/RYA-209
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  The
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.10
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>