e dev list.
On Thu, Aug 11, 2016 at 11:36 AM, Josh Elser wrote:
Josh Elser wrote:
We spent some time talking through Jira and how as a community we need to
document and conform to standard definitions about jira states. We
decided
to increase community involvement by:
1. Establishing WIP
I'd concur with your assessment, Aaron. I would think that you should
just remove that configuration from the maven-release-plugin. One less
command to have to "know about" to make a release (I love projects that
are as simple as "mvn release:prepare; mvn release:perform").
Similarly, allowTim
That "makes it to master" caveat might be problematic here since you're
using the gitflow approach (and things only hit master after a release). FYI
Sean Busbey wrote:
To close a github pr, you have to have a commit that makes it to master
with something like "closes #45", where "#45" is the PR
Actually, everyone else will only receive the message if a moderator
let's it through :)
I think I was feeling cranky when I saw one that just said "YOO" go
through and denied it.
tl;dr Subscribe to the list per the posted instructions, then post to
the list.
Adina Crainiceanu wrote:
Awesome! Thanks for sharing, Aaron.
Aaron D. Mihalik wrote:
Adina/Puja:
I gave an impromptu lighting talk about Rya last night at the DC Graph
Database Meetup. We should add that to the next incubator report.
https://www.meetup.com/graphdb-baltimore/events/233370193/
Thank you Adina for a n
IMO, a flakey test should just be disabled until someone makes time to
fix it. But, why is builds.a.o blocking you from making a release?
You'll be building the release locally anyways [1].
[1] http://www.apache.org/dev/release.html#owned-controlled-hardware
Aaron D. Mihalik wrote:
Caleb and
ep 7, 2016 at 12:41 PM Josh Elser wrote:
IMO, a flakey test should just be disabled until someone makes time to
fix it. But, why is builds.a.o blocking you from making a release?
You'll be building the release locally anyways [1].
[1] http://www.apache.org/dev/release.html#owned-controlled-
I don't see orgapacherya-1000, only 1001 and that one is still open.
Failed Signature Validation sounds like it could not verify the GPG
signatures on the artifacts that we deployed. Is the KEYs file for Rya
published and containing your public signature?
I see http://pgp.mit.edu/pks/lookup?o
Negative, don't worry about it.
I would add an exclusion to the apache-rat-plugin configuration for it.
Aaron D. Mihalik wrote:
Apache rat is failing. Delete .\DEPENDENCIES
It does not have a license header (is that required for that file?)
On Sat, Sep 10, 2016 at 3:11 PM Adina Crainiceanu wr
(thanks for the extension, I started looking at this and then forgot
about it)
-1 (binding)
First off, please include some sort of "RC-X" identifier in the vote
subject so that we can differentiate them in the archives.
- The good
* xsums+sigs match
* Can build from source
* Ran all unit te
reating
these separately). :)
--Aaron
On Mon, Sep 12, 2016 at 11:35 AM Josh Elser wrote:
(thanks for the extension, I started looking at this and then forgot
about it)
-1 (binding)
First off, please include some sort of "RC-X" identifier in the vote
subject so that we can differ
I would have said that this is only kosher when you have an alternative
to the incompatibly licensed software. Is the indexer actually optional
(I don't have enough context)? Are there ways for me to to indexing of
the same type of data that don't require use of these incompatible
dependencies?
se features experimental and they bring in a lot of possibly unwanted
dependencies. Aaron refactored it to not be optional when he was updating
the pond to reference the Apache parent Pom.
So no alternative, but functionality that a typical user may debatably not
want.
Sent from my iPhone
On Sep 14,
Congrats, Caleb!
Adina Crainiceanu wrote:
Hi all,
It is my pleasure to announce that Caleb Meier is now a committer for the
Apache Rya (incubating).
Thank you Caleb for your past and future contributions and we are looking
forward to continue working with you. Welcome!
Best wishes,
Adina (on
candidate did not pass on
dev list. Working on the next release candidate.
When were the last committers or PMC members elected?
New committer Caleb Meier elected on August 31, 2016
The PPMC is currently discussing inviting more active contributors to
become committers.
Signed-off-by:
[
Venkatesh is right in that the only "official" release in the ASF's eyes
is the source release. Any JARs you publish are supplementary and
technically not subject to the rules of Apache releases.
The area I'm still trying to fully grok is that the source-release you
publish must also create ar
smartphone
Original message ----
From: Josh Elser
Date: 10/8/16 3:54 PM (GMT-05:00)
To: dev@rya.incubator.apache.org
Subject: Re: [DISCUSS] Path forward for release
Venkatesh is right in that the only "official" release in the ASF's eyes
is the source release.
be building the optional GeoIndexing support? In
this case, it's a core feature, and not an optional one.
Let me know if #2 is still not clear. I apologize for (likely) making
things more complicated.
Josh Elser wrote:
No, you're correct. I am disagreeing with Venkatesh :). That&#
orrect, it
seems like there is no way around this, other than making the entire indexing
project optional. But that would be like throwing the baby out with the bath
water.
From: Josh Elser [els...@apache.org]
Sent: Monday, October 10, 2016 10:26 AM
To: dev
Convention in other Java-based ASF projects is to have a package of
"org.apache". I was recently reminded that Rya still is using
"mvm.rya...".
Has there been any discussion about ultimately doing an s/package
mvm.rya/package org.apache.rya/ in the future?
I wanted to mention it before w
Uh.. why not just use JIRA?
fixVersion, status=Blocker, and Assignees are there for a reason...
Aaron D. Mihalik wrote:
All,
I'm maintaining a small spreadsheet of issues [1] we need to resolve for
RC2. It is essentially a finer grained copy of what we have in Jira at
RYA-184 [2] (in order to
it would be good to move forward with merging
this and going forward with another release candidate.
On Monday, October 10, 2016, Josh Elser> wrote:
Yup, you got it right, Caleb (given my current interpretation, anyways
:P). The incubator proposal[1] should have called out these depend
Yeah, making a release with a SNAPSHOT version doesn't make any sense
(as SNAPSHOTs are explicitly for non-released versions of software).
At the ASF, the only thing to be aware of is that the final Git tag
should be "rel/deleted.
Meier, Caleb wrote:
What are the conventions for SCM tags? J
A (Maven) repo? It's published central -- you shouldn't have to do
anything extra to get it. Sonatype is automatically mirrored to central
(like Apache is).
Also, Fluo is depending on this directly? Or just transitively? I am
hoping I did not miss it directly depending...
No, it's not ok :).
Also, over in Apache Phoenix, we're using
com.github.stephenc.findbugs:findbugs-annotations:1.3.9-1. Maybe I gave
some bad advice on the GAV to use the first time around :)
Josh Elser wrote:
A (Maven) repo? It's published central -- you shouldn't have to do
anything extra to g
#x27;t want the tag for an RC to be rel in the event that you have
to create a new RC and delete the old tag. Is the convention to just
create an RC tag, and once an RC passes vote then create the "rel/"
tag?
-Original Message-
From: Josh Elser [mailto:josh.el...@gmail.com]
Sorry! I should have been more clear and used fewer emoticons.
I'll try to take a look at rc2 today for some feedback before rc3.
Aaron D. Mihalik wrote:
-1 We're still including findbugs.
I'm sorry everyone. I misread Josh's earlier email [1] and thought it was
okay to continue to include fi
it's
going to be difficult with earlier versions of
c.g.s.f:findbugs-annotations.
I'll take a closer look at it today, though.
--Aaron
On Sun, Oct 16, 2016 at 5:51 PM Josh Elser wrote:
Also, over in Apache Phoenix, we're using
com.github.stephenc.findbugs:findbugs-annotations:1.3.9-1. Ma
Ps, I'd recommend getting this up onto the Rya website :)
David Lotts wrote:
Some additional detail:
Here's a checklist for things to consider when evaluating the release
candidate:
1. Download the sources and verify they compile cleanly.
2. Validate the hashes match.
3. Validate that the s
(disclaimer, I really have no opinion at all about which system is used,
just providing context)
Aaron D. Mihalik wrote:
Devs,
We now have Jenkins (builds.apache.org) building master and all PRs. This
is awesome, but I think we could do a bit more.
How do you all feel about moving to Travis-C
+1
* Sig/Xsums OK, but you have no other signatures on your key to verify
that the key used to sign these artifacts is actually your key, Aaron.
Maybe you can find someone (in person or via phone) or who can your key
for you? [1]
* Verified that geoindexing is "off"
* Cursory glance over depe
(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
otherwise. Has anyone put
together release notes on the website?
Aaron D. Mihalik wrote:
Hello,
The vote to release Rya (Incubating) version 3.2.10 RC3 has passed with 3
+1 votes.
+1 (binding):
Josh Elser
Seetharam Venkatesh
Sergio Fernández
I will promote the artifacts to the central repo and copy them to
dist/release
--Aaron
ator-rya-site
On Mon, Oct 31, 2016 at 12:54 PM Josh Elser wrote:
Congrats on the first release, folks!
Aaron, don't forget to send out the ANNOUNCE message (as the artifacts
should be replicated to the mirrors by now).
Make sure that the announce includes:
* The proper name, something
Aaron D. Mihalik wrote:
Mentors,
We have a PR [1] that imports existing code from another project and the
code is BSD 3-Clause Licensed.
Make sure that the LICENSE file for any artifact that Rya is
re-distributing this code in to include the 3-clause BSD license and
state where you copied i
Also, for reference:
http://www.apache.org/dev/licensing-howto.html#permissive-deps
Aaron D. Mihalik wrote:
Great info. Thanks Josh!
On Wed, Nov 2, 2016 at 4:57 PM, Josh Elser wrote:
Aaron D. Mihalik wrote:
Mentors,
We have a PR [1] that imports existing code from another project and
And for license headers:
https://www.apache.org/legal/src-headers.html#3party
See specifically the comments about "minor" and "major" modifications.
Josh Elser wrote:
Also, for reference:
http://www.apache.org/dev/licensing-howto.html#permissive-deps
Aaron D. Mihali
Hiya folks,
Just an FYI that you'll see a new name around helping out as a mentor:
Billie Rinaldi.
I know that some of you already know/have met Billie in person. I'm very
glad she volunteered to spend some of her precious time with us :)
- Josh
Hiya folks,
I had a coworker ask me over the weekend about Rya. He was a little
confused over why someone might want to use Rya. This is the sort of
thing that is great to write once on the website and refer people to.
It's also a great "recruiting" tool for the project.
These are the types
Yes, direct or transitive dependencies have no bearing on the
application of the license or ASF policy.
Remember, the phrasing of the policy is important: "[you may not bundle
any products which are category-X]" (probably a bad time to not quote
directly, but hopefully my point gets across non
One little trick, if you name your pull request starting with the JIRA
identifier, "RYA-228", the PR will get automatically linked on the JIRA
issue :)
The change LGTM
John Smith wrote:
Jira issue created
https://issues.apache.org/jira/browse/RYA-228
Pull request
https://github.com/apache/in
e it when I
return in Jan.
Happy Holidays to everyone!
Adina
On Thu, Dec 15, 2016 at 2:39 PM, Josh Elser
wrote:
One little trick, if you name your pull request starting with the JIRA
identifier, "RYA-228", the PR will get automatically linked on the JIRA
issue :)
The change LGTM
ed?
New committer and PPMC member David Lotts elected on Oct 25, 2016
Signed-off-by:
[ ](rya) Josh Elser
[ ](rya) Edward J. Yoon
[ ](rya) Venkatesh Seetharam
[ ](rya) Billie Rinaldi
Shepherd/Mentor notes:
Using tweetdeck, you can let multiple people have access to the account.
It's worked well for Accumulo so far.
David Lotts wrote:
Should Rya have a Twitter account?
Lets discuss it.
Who would manage it? How to manage the password?
david.
Since the responses have been mostly positive, I've just gone ahead and
created an account.
I am happy to transfer ownership of the actual account to anyone, as
well as add anyone to the "team" via tweetdeck to be able to interact
with the account.
https://twitter.com/apacherya
Ly, Kiet wro
How did your data-loading job fail? This is a Accumulo server
configuration property -- it has no direct impact on your client.
4G should be fine, just make sure that you have sufficient physical
memory on the Accumulo TabletServer hosts.
Ly, Kiet wrote:
Has anyone used the native memory set
David/Kiet,
Can either of you share the report file that RAT generates (in target/)
for the given module where it failed? This describes what failed the check.
Like Puja says, this shouldn't be happening under normal circumstances.
It's something that was verified before the first release.
LGTM!
I'd think ApacheCon Big Data would be the logical choice, but I'm not
100% sure.
Adina Crainiceanu wrote:
Hi,
The deadline for submitting a talk for ApacheCon is today, and I decided to
submit a talk for Rya. If anyone can offer any comments, please let me
know. This is the first time
So cool, Adina! Thanks for sharing :)
Adina Crainiceanu wrote:
An article about Rya has been posted on the Dept of Navy Innovation page:
http://www.secnav.navy.mil/innovation/Pages/2017/02/ApacheRya.aspx
Thank you to all who made this possible (both Rya and the article).
Adina
Good catch folks! :)
Aaron D. Mihalik wrote:
ah, "asfbot build" builds "with optional" and that masked the rat issues
with just a normal build. gotcha.
On Mon, Mar 13, 2017 at 11:54 AM Puja Valiyil wrote:
Sorry -- this is me. Well, more like this is me trusting the build server
too much --
elected?
New committer and PPMC member David Lotts elected on Oct 25, 2016
New PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[ ](rya) Josh Elser
Comments:
[ ](rya) Edward J. Yoon
Comments:
[ ](rya) Venkatesh Seetharam
Comments:
[ ](rya)
Getting the workflow change likely requires an INFRA ask. If it's
something you all want to pursue, go for it.
Otherwise, we can make sure enough committers have karma to add new
contributors and do it by hand (like this case).
Jonathan Wonders wrote:
The last message I saw on the mailing li
I can help out with the logistics if someone wants to take on the cross
of word-smithing. There are plenty of good previous reports[1] to take
inspiration from :)
[1] https://wiki.apache.org/incubator/January2017
On 6/28/17 2:05 AM, Adina Crainiceanu wrote:
Rya enthusiasts,
Is anyone volunte
https://lists.apache.org/thread.html/14fbb6ec756261cd522a4a17db74453d8382d117041af9995620e44a@%3Cdev.rya.apache.org%3E
;)
On 6/30/17 9:17 AM, Meier, Caleb wrote:
Adina is on vacation until the end of July. So she is unavailable to work on
it.
Caleb A. Meier, Ph.D.
Software Engineer II ♦ Anal
Hi,
Sorry for being a bit more hands-off as of late. Professional and
personal life has been quite ramped up for me :). Looking over the July
2017 report, it made me wonder what the next steps for Rya are and how I
can help push you all in this process!
* What is the next release?
- What w
does not provide ANY
information about your release last October. That really does not help the
project build a community. Please look into your website and give it the care
it needs.
Regards,
Dave
On 2017-07-05 10:32 (-0700), Josh Elser wrote:
Hi,
Sorry for being a bit more hands-off as of
Hi David,
There is no hard-and-fast timeline on how long a project stays in
incubation at the Apache Software Foundation. Some projects graduate in
6-9 months, others incubate for years.
Rya's first release (3.2.10) can be found using the available ASF
mirrors https://www.apache.org/dyn/clos
incubator-rya-site *or do I need to do it from the Apache Git repo?
It has a PR for a bad link that I'd like to merge.
For the download page, I'll do a proper PR so we can review before we merge
and publish it.
david.
On Fri, Jul 7, 2017 at 5:07 PM, Josh Elser wrote:
Oh good catch,
That's pretty cool, Jeff! Thank you for sharing.
This sounds like a great addition to Apache Rya to me. Perhaps I can
convince one of the other devs to step up and try to help shepherd this
in? (otherwise, I'll try to make the time to do it *winks*)
On 7/22/17 8:06 AM, Jeff Zemerick wrote:
I
Hi Matteo,
Thanks for the bug-report. Do you have an interest in making the change
to Rya to address this issue? :)
In open source projects, we like to encourage users to make changes to
"scratch their own itch". Please let us know how we can help enable you
to make this change.
On 8/25/17
-1 (binding)
* rya.export depends on JCalendar which is LGPL [1] (brought in by RYA-123)
* Copyright year in NOTICE needs updating
* Nit: s/RYA/Apache Rya/ in the README
Everything else looks ok at first glance.
[1] https://toedter.com/jcalendar/
On 9/2/17 1:08 AM, David Lotts wrote:
I am ple
Yes, policy states that generated sources can omit license headers.
However, it's also nice to just automate license headers being added and
not have to make goofy exclusions to work around it :)
I think the major concern at the moment is that plugin which is
generating a copyright line too (s
Just catching up -- thanks for turning around those changes so quickly!
The fixes look good to me. Great work!
On 9/8/17 5:38 PM, David Lotts wrote:
Hello,
The vote to release Rya (Incubating) version 3.2.11 RC1 has failed.
-1 (binding): Josh Elser
+0 (non binding): Jeff Dasch
The following
Yep. For the same reason that geoindexing module cannot be built by
default (requires the user to acknowledge that they're using a library
with this license), the benchmark module cannot be built by default.
Good catch folks.
On 9/13/17 3:57 PM, Jeff Dasch wrote:
Created RYA-370 to track the
By the letter of the law, you don't have to resolve license conflicts
until you graduate from the Incubator.
However, the process of identifying bad licensing, finding suitable
replacements, and implementing such changes shows a _lot_ of maturity
from the community (as this is a very real prob
+1
* xsums/sigs OK
* Verified incompatibly licensed modules are optional
* Verified org.json is removed
* Git commit contained in scm
* KEYS contains pubkey of signer
* Can build from source
Good on you all to fix the licensing stuff right away!
On 9/26/17 1:27 PM, David Lotts wrote:
I am plea
This Wednesday, folks :)
On 10/1/17 9:06 AM, johndam...@apache.org wrote:
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled
?
* PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[ ](rya) Josh Elser
Comments:
[ ](rya) Edward J. Yoon
Comments:
[ ](rya) Venkatesh Seetharam
Comments:
[ ](rya) Billie Rinaldi
Comments:
IPMC/Shepherd notes:
Thank you,
Adina
--
Dr. Adina Crainiceanu
munity developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing gra
e to tweet it as
well? I'm configuring my gmail account to send from dlo...@apache.org.
david.
On Thu, Jan 12, 2017 at 11:46 AM, Josh Elser wrote:
Since the responses have been mostly positive, I've just gone ahead and
created an account.
I am happy to transfer ownership of the actu
Done! You're an admin now :)
If you log into https://tweetdeck.twitter.com, you should see a "team"
associated for @ApacheRya which you can manage.
On 10/19/17 12:40 PM, Lotts, David wrote:
Josh,
If you can send me your twitter handle,
@dlotts
Thanks, that'll be great.
David.
Hiya,
(Disclaimer, I have not crunched any numbers yet about diversity,
traffic, etc)
I was thinking the other day that Rya is "old" enough that we should
start thinking about graduation[1], and, if we don't think it's ready,
let's set concrete/actionable goals which people can push towards
hone
On Nov 30, 2017, at 5:20 AM, Erik Bijsterbosch wrote:
Hi all,
Shouldn't code for OpenRDF be refactored to RDF4J for graduation?
Regards,
Erik
2017-11-22 23:55 GMT+01:00 Josh Elser :
Hiya,
(Disclaimer, I have not crunched any numbers yet about diversity, traffic,
etc)
I was thinking t
ing towards first release
[ ] Community building
[x] Nearing graduation
[ ] Other:
Date of last release:
2017-10-10
When were the last committers or PPMC members elected?
* PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[ ](rya) Josh Elser
Comments:
IIRC, the findbugs-annotation artifact is dubious at best in terms of
licensing. I think the "intent" was that it was compatibly licensed, but
the artifacts in Maven totally had it mislabeled.
Not something that needs to block your release now, but you should be
taking this up to make sure are
ur own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[x] Nearing graduation
[ ] Other:
Date of last release:
2018-03-04
When were the last committers or PPMC members elected?
* PPMC member Caleb Meier elected on Jan 3rd, 2017
Si
[ ] Other:
Date of last release:
2018-03-04
When were the last committers or PPMC members elected?
* PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[ ](rya) Josh Elser
Comments:
[ ](rya) Edward J. Yoon
Comments:
[ ](rya) Venkatesh Seetharam
Forwarding this message to the actual mailing list.
On 5/15/18 2:53 PM, b...@bobdc.com wrote:
I am trying to use the Rya Vagrant Example shown at
https://github.com/apache/incubator-rya/tree/master/extras/vagrantExample/src/main/vagrant.
After updating the ACCUMULO_VERSION, HADOOP_VERSION, and
When is it going to happen? IMO, you've been ready for a long time now :)
Talked to Billie about this -- trying to make sure I have the situation
correct. IMO, the question that needs to be answered is: who can assert
copyright ownership over the images.
Typically, copyright assertions are one of two entities: the individual
who created some "work" or a company whic
New contributors are good to mention (as long as they're not "drive-by"
contributions where you don't expect future contributions).
On 10/1/18 11:45 AM, David Lotts wrote:
Would it be appropriate to mention the relatively new involvement of the
good folks at Semantic Web Company?
This increases
: +43-14021235 <+43%201%204021235>
US: (415) 800-3776
Mobile: +43-676-6212710 <+43%20676%206212710>
https://www.poolparty.biz
https://www.semantic-web.com
*Download E-Book*: Introducing Semantic AI
<https://www.poolparty.biz/machine-learning-meets-semantics/>
Am Mo., 1. Okt. 201
ACK. Will investigate.
On 11/3/18 10:38 AM, Adina Crainiceanu wrote:
Hi,
I updated the project status file at
http://incubator.apache.org/projects/rya.html but I'm not sure about the
dates for the "Mentor-related responsibility/oversight" section. Mentors:
is there a way to figure those dates f
No need to find the earliest date. You (or I) can just put the current
date. The purpose is to just record the date that we're sure all of
these things happened by.
I can vouch that all 3 are good. Let me know if you'd prefer that I
update it.
Thanks for driving this home, Adina!
On 11/3/18
>
> Date of last release:
>
>2018-03-04
>
> When were the last committers or PPMC members elected?
>
> * PPMC member Caleb Meier elected on Jan 3rd, 2017
>
> Signed-off-by:
>
> [ ](rya) Josh Elser
> Comments:
> [ ](rya) Billie Rinaldi
> Comments:
>
> IPMC/Shepherd notes:
>
>
> --
> 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/
Meier elected on Jan 3rd, 2017
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Our two mentors are helpful and responsive.
Signed-off-by:
[](rya) Josh Elser
Comments:
Thanks, Craig. Moving you to bcc.
Aaron -- are the steps to making a release doc'ed somewhere where they
could be updated with Craig's suggestions?
Glancing through the website and the user manual, I don't see an obvious
page covering the steps.
On 7/29/19 5:48 PM, Private List Moderation w
only mention this checksum.
I created a Jira issue to update the website:
https://issues.apache.org/jira/browse/RYA-519
Thanks,
Adina
On Tue, Aug 6, 2019 at 4:33 PM Josh Elser wrote:
Thanks, Craig. Moving you to bcc.
Aaron -- are the steps to making a release doc'ed somewhere where they
Looks like http://incubator.apache.org/projects/rya.html is already done!
You have my +1!
On 8/8/19 4:12 PM, Adina Crainiceanu wrote:
Hi,
I would like to start talking again about graduation, After another
successful release, it is time (or past time) to discuss whether we are
ready to graduat
tts
* 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
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
oject:
* 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
Let me send a heart-felt congratulations to the community. Moving a
software project through the ASF Incubator is no small feat.
You should all be extremely proud of what you have accomplished here,
and remain ever-focused on growing and expanding the Rya community.
Well done. Go celebrate :)
Josh Elser created RYA-1:
Summary: Import the code
Key: RYA-1
URL: https://issues.apache.org/jira/browse/RYA-1
Project: Rya
Issue Type: Task
Reporter: Josh Elser
Priority
[
https://issues.apache.org/jira/browse/RYA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962601#comment-14962601
]
Josh Elser commented on RYA-2:
--
bq. Steve Wagner steve.r.wag...@gmail.com swagner (I believe
[
https://issues.apache.org/jira/browse/RYA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated RYA-2:
-
Description:
Please create Apache accounts for the Rya incubator project initial committers.
All ICLAs have been
[
https://issues.apache.org/jira/browse/RYA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved RYA-2.
--
Resolution: Done
Submitted account requests for David, Aaron, Jennifer, Puja, Roshan and Adina
with the listed
[
https://issues.apache.org/jira/browse/RYA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983217#comment-14983217
]
Josh Elser commented on RYA-1:
--
It doesn't appear like you did anything wrong, [~Pujav
[
https://issues.apache.org/jira/browse/RYA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983227#comment-14983227
]
Josh Elser commented on RYA-1:
--
Filed INFRA-10693 (with terrible spelling).
> Import t
[
https://issues.apache.org/jira/browse/RYA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983232#comment-14983232
]
Josh Elser commented on RYA-1:
--
Infra agreed that it was likely due to the size of the co
101 - 200 of 209 matches
Mail list logo
