Re: [VOTE] Release Apache Trafodion 2.0.1 (incubating)

[Suresh Subbiah]

Hi

+1 (non-binding from Trafodion PPMC)
Downloaded client package and checked the ODBC client with readelf
readelf -d  *.so | grep ssl
 0x0001 (NEEDED) Shared library: [libssl.so.10]
 0x0001 (NEEDED) Shared library: [libssl.so.10]

Thanks
Suresh



On Wed, Jun 15, 2016 at 11:48 PM, Justin Mclean 
wrote:

> Hi,
>
> Not having a good day and responded to the wrong vote thread. Correcting.
>
> Sorry but it's-1 (binding) from me as:
> The LICENSE issue raised with last release re the 4 clause BSD license has
> not been dealt wth.
> The installer, client and server packages are missing a DISCLAIMER file.
> [1]
>
> The license issue is for swsprintf.cpp and swscanf.cpp files. I can see
> the OpenSSL issue has been fixed.
>
> One other minor thing I notice the binaries expand to client / installer
> directories or the current directory in the case of the sever package. IMO
> it would be better if they expanded to a directory including the words
> “Apache Trafodion”.
>
> Thanks,
> Justin
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [ANNOUNCE] Release Apache Trafodion 2.0.0-incubating

[Justin Mclean]

Hi,

And I stuffed and and posted that to the wrong vote thread - please ignore.

Thanks,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Trafodion 2.0.1 (incubating)

[Justin Mclean]

Hi,

Not having a good day and responded to the wrong vote thread. Correcting.

Sorry but it's-1 (binding) from me as:
The LICENSE issue raised with last release re the 4 clause BSD license has not 
been dealt wth.
The installer, client and server packages are missing a DISCLAIMER file. [1]

The license issue is for swsprintf.cpp and swscanf.cpp files. I can see the 
OpenSSL issue has been fixed.

One other minor thing I notice the binaries expand to client / installer 
directories or the current directory in the case of the sever package. IMO it 
would be better if they expanded to a directory including the words “Apache 
Trafodion”.

Thanks,
Justin
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [ANNOUNCE] Release Apache Trafodion 2.0.0-incubating

[Justin Mclean]

Hi,

Say but it's-1 (binding) from me as:
The LICENSE issue raised with last release re the 4 clause BSD license has not 
been dealt wth.
The installer, client and server packages are missing a DISCLAIMER file. [1]

The license issue is for swsprintf.cpp and swscanf.cpp files, I can see the 
OpenSSL issue has been fixed.

I notice the binaries expand to directories or the current directory in the 
case of sever. IMO it would be better if they expanded to a directory including 
the words “ApacheTrafodion”.

Thanks,
Justin

1. See 3.1 in http://incubator.apache.org/guides/release.html


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache SystemML 0.10.0-incubating released

[Luciano Resende]

The Apache SystemML team is pleased to announce the release of Apache
SystemML version 0.10.0-incubating.

Apache SystemML provides declarative large-scale machine learning (ML) that
aims at flexible specification of ML algorithms and automatic generation of
hybrid runtime plans ranging from single-node, in-memory computations, to
distributed computations on Apache Hadoop MapReduce and Apache Spark.

Extensive updates have been made to the release in several areas. These
include APIs, data ingestion, optimizations, language and runtime
operators, new algorithms, testing, and online documentation. For detailed
information about the updates, please access the release notes available at
:

http://systemml.apache.org/0.10.0-incubating/release_notes.html

To download the distribution, please go to :

http://systemml.apache.org/

The Apache SystemML Team

---
Apache SystemML is an effort undergoing Incubation
 at The Apache Software Foundation
(ASF), sponsored by the Incubator. Incubation is required of all newly
accepted projects until a further review indicates that the infrastructure,
communications, and decision making process have stabilized in a manner
consistent with other successful ASF projects. While incubation status is
not necessarily a reflection of the completeness or stability of the code,
it does indicate that the project has yet to be fully endorsed by the ASF.

RE: Trafodion podling needs more mentors

[Dave Birdsall]

Hi John,

Thanks for the comments. These help.

Speaking only for myself, I'm not far from retirement age and I'm likely to
continue contributing after I retire, simply because I've worked on this
code base for 20 years now and I love it. I'm always surprised to get paid
to do this stuff.

I'll take a look at the Esgyn web site for branding issues.

Dave

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Wednesday, June 15, 2016 4:05 PM
To: general@incubator.apache.org
Subject: Re: Trafodion podling needs more mentors

Dave,

For some reason, I feel like I commented on that thread as well, but don't
see it, so I'm either thinking of something else or its inlined somewhere
that I didn't see (e.g. the emails back and forth with Pierre).

The question to always ask with company alliances is if someone would
contribute to the project if they weren't paid by $dayjob to do so.  The
beauty of the Apache Way is by focusing on individuals, this problem becomes
more apparent.  Of the new contributors you added that work for Esgyn, which
of them would realistically contribute to Trafodion if they weren't employed
by Esgyn?  Likewise, if Esgyn stopped building a product on top of
Trafodion, would those contributors remain?

In addition, with such tight company affiliation, does the PMC represent a
reasonable cross section so that they can assert their iP claims?  For
example, based on looking at the usage of Trafodion vs Apache Trafodion on
https://esgyn.com/ would the PMC send an email to some representative of
Esgyn asking them to correct the branding errors? (To be clear, a cursory
look around the website only gives me one minor error, nothing crazy like
we've seen with other projects, you've done a great job keeping branding in
line with guidelines on both the ASF site and here)

These are the reasons, at least from my POV, why community diversity is
important.  To be honest, I don't see any of the typical warning signs I see
with company backed ASF projects that I see here.  Its clear that its ASF
developed first.  I see great communication and collaboration via email
(heck, I wish my $dayjob communicated this well via email).

So to answer your question, no, I don't think Trafodion needs more mentors.
Maybe you need some help with the graduation process, but from my POV you
seem like TLP material to me.

John

On Wed, Jun 15, 2016 at 5:02 PM Dave Birdsall 
wrote:

> John,
>
> When we first entered incubation, we had nine committers, all
> Hewlett-Packard employees. A couple of months later, four of those
> decamped to a new company, Esgyn Corporation, while the remainder
> either stayed with HP or moved on to other opportunities. The four
> have remained very active while the remaining five are mostly inactive.
>
> Since then we have added six more committers, of whom five are
> affiliated with Esgyn and one not.
>
> There are many more contributors that are active as well.
>
> Here's a list:
> https://cwiki.apache.org/confluence/display/TRAFODION/Contributors.
> It's not complete; I can think of some contributors who are not
> listed. (We -- the Trafodion podling -- should fix that.)
>
> We recently had a discussion amongst ourselves concerning readiness
> for TLP.
> Community diversity is something we think we need to improve. Advice
> and help in this regard would be welcome.
>
> Dave
>
> -Original Message-
> From: John D. Ament [mailto:johndam...@apache.org]
> Sent: Wednesday, June 15, 2016 1:33 PM
> To: general@incubator.apache.org
> Subject: Re: Trafodion podling needs more mentors
>
> Dave,
>
> Thanks for the very detailed report.  One comment, which I think I
> made earlier, is that we like to see how your community has grown.  So
> the numbers don't provide the full details.
>
> I'm curious, from your point of view, how close are you to graduating?
> Is your developer community diverse enough?
>
> John
>
> On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall
> 
> wrote:
>
> > Hi Martin,
> >
> > The intended audience for our project are users in the Apache Hadoop
> > ecosystem looking for transactional and operational SQL. We provide
> > a transactional and operational SQL engine on top of Apache HBase,
> > with some support for non-transactional operation on Hive tables. By
> > operational, we mean to include large reporting queries that one
> > might do on a transactional database.
> >
> > Here's a pointer to our latest Podling Report (search for the string
> > "Trafodion"): https://wiki.apache.org/incubator/June2016
> >
> > So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was
> > in discussion at the time the podling report was written).
> >
> > Very short-term objectives are we have a patch release 2.0.1 that
> > needs approval. Short-term we are likely to have a Release 2.1
> > within the next few months.
> >
> > Long-term we hope to move to TLP. The biggest issue at the moment is
> > expanding our community, as most of the developers and active
> >

Re: [VOTE] Release Apache Trafodion 2.0.1 (incubating)

[John D. Ament]

Here's my +1

However, I would strongly encourage the PPMC to also cast (non binding
where appropriate) votes on the list to indicate their support as well.

John

On Fri, Jun 10, 2016 at 4:48 PM Steve Varnau  wrote:

> Hello,
>
>
>
> This is a call to vote on the patch release 2.0.1-incubating (Release
> Candidate 1).
>
>
>
> The changes were small, just to address things that came up in the 2.0.0
> reviews, primarily addressing the issue that prevented providing a
> convenience binary of the clients package.
>
>
>
> Changes since 2.0.0:
>
>[TRAFODION-2024] Openssl libraries (ssl & crypto) are linked dynamically
>
>[TRAFODION-2023] Clarify license text; Also small mods to instructions
> on running RAT
>
>Bump release version number to 2.0.1; Also backported a one line change
> to a test expecting specific release number
>
>
>
> The trafodion community has approved RC1 for release.
>
> <
>
> https://lists.apache.org/thread.html/428f04f6f2a3d500f31d059a92a44770d2a2b6f59f2a0f33d6a0c93f@%3Cdev.trafodion.apache.org%3E
> >
>
>
>
> The tag for this candidate is “2.0.1rc1”. Git repository: git://
> git.apache.org/incubator-trafodion.git
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=7f4add54e46bb5395069e2b77bcdfa4024efc006
>
>
>
> Release artifacts are:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.1-RC1
>
> Artifacts are signed with my key (7F14AF20), which is in
>
> https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
>
>
>
> Instructions:
>
>   Setting up build environment:
>
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
>
>
>   Building:
> https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
>
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
>
> Vote will be open for at least 72 hours, unless cancelled.
>
> I will not be available next week, so Roberta Marton will be following up
> on this release.
>
>
>
> Thanks,
>
> --Steve
>

Re: Trafodion podling needs more mentors

[John D. Ament]

Dave,

For some reason, I feel like I commented on that thread as well, but don't
see it, so I'm either thinking of something else or its inlined somewhere
that I didn't see (e.g. the emails back and forth with Pierre).

The question to always ask with company alliances is if someone would
contribute to the project if they weren't paid by $dayjob to do so.  The
beauty of the Apache Way is by focusing on individuals, this problem
becomes more apparent.  Of the new contributors you added that work for
Esgyn, which of them would realistically contribute to Trafodion if they
weren't employed by Esgyn?  Likewise, if Esgyn stopped building a product
on top of Trafodion, would those contributors remain?

In addition, with such tight company affiliation, does the PMC represent a
reasonable cross section so that they can assert their iP claims?  For
example, based on looking at the usage of Trafodion vs Apache Trafodion on
https://esgyn.com/ would the PMC send an email to some representative of
Esgyn asking them to correct the branding errors? (To be clear, a cursory
look around the website only gives me one minor error, nothing crazy like
we've seen with other projects, you've done a great job keeping branding in
line with guidelines on both the ASF site and here)

These are the reasons, at least from my POV, why community diversity is
important.  To be honest, I don't see any of the typical warning signs I
see with company backed ASF projects that I see here.  Its clear that its
ASF developed first.  I see great communication and collaboration via email
(heck, I wish my $dayjob communicated this well via email).

So to answer your question, no, I don't think Trafodion needs more
mentors.  Maybe you need some help with the graduation process, but from my
POV you seem like TLP material to me.

John

On Wed, Jun 15, 2016 at 5:02 PM Dave Birdsall 
wrote:

> John,
>
> When we first entered incubation, we had nine committers, all
> Hewlett-Packard employees. A couple of months later, four of those decamped
> to a new company, Esgyn Corporation, while the remainder either stayed with
> HP or moved on to other opportunities. The four have remained very active
> while the remaining five are mostly inactive.
>
> Since then we have added six more committers, of whom five are affiliated
> with Esgyn and one not.
>
> There are many more contributors that are active as well.
>
> Here's a list:
> https://cwiki.apache.org/confluence/display/TRAFODION/Contributors. It's
> not
> complete; I can think of some contributors who are not listed. (We -- the
> Trafodion podling -- should fix that.)
>
> We recently had a discussion amongst ourselves concerning readiness for
> TLP.
> Community diversity is something we think we need to improve. Advice and
> help in this regard would be welcome.
>
> Dave
>
> -Original Message-
> From: John D. Ament [mailto:johndam...@apache.org]
> Sent: Wednesday, June 15, 2016 1:33 PM
> To: general@incubator.apache.org
> Subject: Re: Trafodion podling needs more mentors
>
> Dave,
>
> Thanks for the very detailed report.  One comment, which I think I made
> earlier, is that we like to see how your community has grown.  So the
> numbers don't provide the full details.
>
> I'm curious, from your point of view, how close are you to graduating?  Is
> your developer community diverse enough?
>
> John
>
> On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall 
> wrote:
>
> > Hi Martin,
> >
> > The intended audience for our project are users in the Apache Hadoop
> > ecosystem looking for transactional and operational SQL. We provide a
> > transactional and operational SQL engine on top of Apache HBase, with
> > some support for non-transactional operation on Hive tables. By
> > operational, we mean to include large reporting queries that one might
> > do on a transactional database.
> >
> > Here's a pointer to our latest Podling Report (search for the string
> > "Trafodion"): https://wiki.apache.org/incubator/June2016
> >
> > So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was
> > in discussion at the time the podling report was written).
> >
> > Very short-term objectives are we have a patch release 2.0.1 that
> > needs approval. Short-term we are likely to have a Release 2.1 within
> > the next few months.
> >
> > Long-term we hope to move to TLP. The biggest issue at the moment is
> > expanding our community, as most of the developers and active
> > committers are at one company.
> >
> > Our SDLC is a comprehensive branch model. We actively merge up any
> > patches to older branches onto the latest branch. We use git for our
> > source control. We use Jenkins to automate build and test of changes
> > before they are committed. There is a culture within the podling of
> > quick and thorough reviews of code changes. Small changes tend to be
> > committed quickly while larger changes take longer. See
> > https://github.com/apache/incubator-trafodion.
> >
> > We have produced a comprehensive set of 

Re: Trafodion podling needs more mentors

[Tom Barber]

Just for the record, I was asked to help out as a mentor and said I would
happily get involved when I get back from vacation next week.

Tom

On Wed, Jun 15, 2016 at 11:19 PM, Pierre Smits 
wrote:

> Hi John,
>
> The question you're asking with respect to how diverse our developer
> community is a wrong one. Focussing on just that is negating our
> contributors of the other kind.
>
> So coming back to the diversity of our community I would say that though it
> is not optimal with respect to the minimalisation of a potential risk of a
> single external entity pressuring a majority of contributors with binding
> votes. Yet, participating in this community from early on in the incubation
> process I can say that the community is mature and know how to separate
> issues revolving around the product of the affiliated party/parties from
> the vision and goals of the project.
>
> Your question regarding how much our community has grown is valid, but in
> al the years lurking and participating in this ml I have never witnessed an
> absolute threshold being referenced as what the size of the community. Nor
> have I ever seen that a podling was told to bring in more diversity when
> the majority of its privileged contributors was affiliated with one
> external party.
>
> The community feels there is a chicken and egg situation here. Adoption is
> expected to grow at a higher rate (thus bringing in more contributors from
> other directions, enabling the community have a more diverse segment of
> those with privileges), when it has a higher status within the ASF than it
> now has. We want to be a TLP, we want more contributors. But we can't
> coerce. Marketing the product and the project is easier when the status of
> the project reflects the resolve of it community. And this community is
> here for the long run.
>
> John, you have also raised your concerns regarding the diversity in the
> thread with subject '[DISCUSS] Trafodion for TLP. Though this should go
> there, I am providing my 2 cents here.
>
> But it seems to me that this Incubator project has an issue of its own. The
> Trafodion podling is yet another one emerging in a short period of time
> notifying this ml of having an issue regarding the participation of its
> mentors. Current active Incubator contributors with privileges seem to have
> a workload to big. Hence the voting on the Trafodion r2.0.1 release is
> already running for 6 day, without any of those, who can cast a binding
> vote, engaging.
> Apart from other aspects this seems (to me) to be a diversity issue as
> well. Can you tell me how long ago the PMC onboarded a contributor to have
> privileges, that was not an ASF Member?
>
> Best regards,
>
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Wed, Jun 15, 2016 at 10:33 PM, John D. Ament 
> wrote:
>
> > Dave,
> >
> > Thanks for the very detailed report.  One comment, which I think I made
> > earlier, is that we like to see how your community has grown.  So the
> > numbers don't provide the full details.
> >
> > I'm curious, from your point of view, how close are you to graduating?
> Is
> > your developer community diverse enough?
> >
> > John
> >
> > On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall 
> > wrote:
> >
> > > Hi Martin,
> > >
> > > The intended audience for our project are users in the Apache Hadoop
> > > ecosystem looking for transactional and operational SQL. We provide a
> > > transactional and operational SQL engine on top of Apache HBase, with
> > some
> > > support for non-transactional operation on Hive tables. By operational,
> > we
> > > mean to include large reporting queries that one might do on a
> > > transactional database.
> > >
> > > Here's a pointer to our latest Podling Report (search for the string
> > > "Trafodion"): https://wiki.apache.org/incubator/June2016
> > >
> > > So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was in
> > > discussion at the time the podling report was written).
> > >
> > > Very short-term objectives are we have a patch release 2.0.1 that needs
> > > approval. Short-term we are likely to have a Release 2.1 within the
> next
> > > few months.
> > >
> > > Long-term we hope to move to TLP. The biggest issue at the moment is
> > > expanding our community, as most of the developers and active
> committers
> > > are at one company.
> > >
> > > Our SDLC is a comprehensive branch model. We actively merge up any
> > patches
> > > to older branches onto the latest branch. We use git for our source
> > > control. We use Jenkins to automate build and test of changes before
> they
> > > are committed. There is a culture within the podling of quick and
> > thorough
> > > reviews of code changes. Small changes tend to be committed quickly
> while
> > > larger changes take longer. See
> > > https://github.com/apache/incubator-trafodion.
> > >
> > > We have produced a comprehensiv

Re: Trafodion podling needs more mentors

[Pierre Smits]

Hi John,

The question you're asking with respect to how diverse our developer
community is a wrong one. Focussing on just that is negating our
contributors of the other kind.

So coming back to the diversity of our community I would say that though it
is not optimal with respect to the minimalisation of a potential risk of a
single external entity pressuring a majority of contributors with binding
votes. Yet, participating in this community from early on in the incubation
process I can say that the community is mature and know how to separate
issues revolving around the product of the affiliated party/parties from
the vision and goals of the project.

Your question regarding how much our community has grown is valid, but in
al the years lurking and participating in this ml I have never witnessed an
absolute threshold being referenced as what the size of the community. Nor
have I ever seen that a podling was told to bring in more diversity when
the majority of its privileged contributors was affiliated with one
external party.

The community feels there is a chicken and egg situation here. Adoption is
expected to grow at a higher rate (thus bringing in more contributors from
other directions, enabling the community have a more diverse segment of
those with privileges), when it has a higher status within the ASF than it
now has. We want to be a TLP, we want more contributors. But we can't
coerce. Marketing the product and the project is easier when the status of
the project reflects the resolve of it community. And this community is
here for the long run.

John, you have also raised your concerns regarding the diversity in the
thread with subject '[DISCUSS] Trafodion for TLP. Though this should go
there, I am providing my 2 cents here.

But it seems to me that this Incubator project has an issue of its own. The
Trafodion podling is yet another one emerging in a short period of time
notifying this ml of having an issue regarding the participation of its
mentors. Current active Incubator contributors with privileges seem to have
a workload to big. Hence the voting on the Trafodion r2.0.1 release is
already running for 6 day, without any of those, who can cast a binding
vote, engaging.
Apart from other aspects this seems (to me) to be a diversity issue as
well. Can you tell me how long ago the PMC onboarded a contributor to have
privileges, that was not an ASF Member?

Best regards,


Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jun 15, 2016 at 10:33 PM, John D. Ament 
wrote:

> Dave,
>
> Thanks for the very detailed report.  One comment, which I think I made
> earlier, is that we like to see how your community has grown.  So the
> numbers don't provide the full details.
>
> I'm curious, from your point of view, how close are you to graduating?  Is
> your developer community diverse enough?
>
> John
>
> On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall 
> wrote:
>
> > Hi Martin,
> >
> > The intended audience for our project are users in the Apache Hadoop
> > ecosystem looking for transactional and operational SQL. We provide a
> > transactional and operational SQL engine on top of Apache HBase, with
> some
> > support for non-transactional operation on Hive tables. By operational,
> we
> > mean to include large reporting queries that one might do on a
> > transactional database.
> >
> > Here's a pointer to our latest Podling Report (search for the string
> > "Trafodion"): https://wiki.apache.org/incubator/June2016
> >
> > So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was in
> > discussion at the time the podling report was written).
> >
> > Very short-term objectives are we have a patch release 2.0.1 that needs
> > approval. Short-term we are likely to have a Release 2.1 within the next
> > few months.
> >
> > Long-term we hope to move to TLP. The biggest issue at the moment is
> > expanding our community, as most of the developers and active committers
> > are at one company.
> >
> > Our SDLC is a comprehensive branch model. We actively merge up any
> patches
> > to older branches onto the latest branch. We use git for our source
> > control. We use Jenkins to automate build and test of changes before they
> > are committed. There is a culture within the podling of quick and
> thorough
> > reviews of code changes. Small changes tend to be committed quickly while
> > larger changes take longer. See
> > https://github.com/apache/incubator-trafodion.
> >
> > We have produced a comprehensive set of documentation both of the project
> > code itself and of the development process. The former can be found here
> > http://trafodion.apache.org (see the Documentation tab), and the latter
> in
> > our wiki
> >
> https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion+Hom
> > e (see Trafodion Contributor Guide).
> >
> > Thanks,
> >
> > Dave
> >
> > -Original Message-
> > From: Ma

RE: Trafodion podling needs more mentors

[Dave Birdsall]

John,

When we first entered incubation, we had nine committers, all
Hewlett-Packard employees. A couple of months later, four of those decamped
to a new company, Esgyn Corporation, while the remainder either stayed with
HP or moved on to other opportunities. The four have remained very active
while the remaining five are mostly inactive.

Since then we have added six more committers, of whom five are affiliated
with Esgyn and one not.

There are many more contributors that are active as well.

Here's a list:
https://cwiki.apache.org/confluence/display/TRAFODION/Contributors. It's not
complete; I can think of some contributors who are not listed. (We -- the
Trafodion podling -- should fix that.)

We recently had a discussion amongst ourselves concerning readiness for TLP.
Community diversity is something we think we need to improve. Advice and
help in this regard would be welcome.

Dave

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Wednesday, June 15, 2016 1:33 PM
To: general@incubator.apache.org
Subject: Re: Trafodion podling needs more mentors

Dave,

Thanks for the very detailed report.  One comment, which I think I made
earlier, is that we like to see how your community has grown.  So the
numbers don't provide the full details.

I'm curious, from your point of view, how close are you to graduating?  Is
your developer community diverse enough?

John

On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall 
wrote:

> Hi Martin,
>
> The intended audience for our project are users in the Apache Hadoop
> ecosystem looking for transactional and operational SQL. We provide a
> transactional and operational SQL engine on top of Apache HBase, with
> some support for non-transactional operation on Hive tables. By
> operational, we mean to include large reporting queries that one might
> do on a transactional database.
>
> Here's a pointer to our latest Podling Report (search for the string
> "Trafodion"): https://wiki.apache.org/incubator/June2016
>
> So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was
> in discussion at the time the podling report was written).
>
> Very short-term objectives are we have a patch release 2.0.1 that
> needs approval. Short-term we are likely to have a Release 2.1 within
> the next few months.
>
> Long-term we hope to move to TLP. The biggest issue at the moment is
> expanding our community, as most of the developers and active
> committers are at one company.
>
> Our SDLC is a comprehensive branch model. We actively merge up any
> patches to older branches onto the latest branch. We use git for our
> source control. We use Jenkins to automate build and test of changes
> before they are committed. There is a culture within the podling of
> quick and thorough reviews of code changes. Small changes tend to be
> committed quickly while larger changes take longer. See
> https://github.com/apache/incubator-trafodion.
>
> We have produced a comprehensive set of documentation both of the
> project code itself and of the development process. The former can be
> found here http://trafodion.apache.org (see the Documentation tab),
> and the latter in our wiki
> https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion
> +Hom
> e (see Trafodion Contributor Guide).
>
> Thanks,
>
> Dave
>
> -Original Message-
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Sent: Wednesday, June 15, 2016 1:06 PM
> To: general@incubator.apache.org
> Subject: RE: Trafodion podling needs more mentors
>
> what have you accomplished thus far?
> what are your short-term objectives..(what do you need by the end of
> 2016)?
>
> what are the long term objectives?
> what is your SDLC...submit jira ..submit patch and testcase and hope
> integration works OR comprehensive branch cut for major new release
> and then hopefully merge sometime later
>
> who is the intended audience for Trafodion?
> Thanks Dave!
> Martin
> __
>
>
>
> > From: dave.birds...@esgyn.com
> > Date: Wed, 15 Jun 2016 12:58:31 -0700
> > Subject: Trafodion podling needs more mentors
> > To: general@incubator.apache.org
> >
> > Hello Incubator community,
> >
> > The incubating Trafodion project needs more mentors. The project is
> > in reasonably good shape from an infrastructure and work-habits
> > point of
> view.
> > We have done two releases now, learning many lessons from that
> experience.
> > But we need more help checking out our release candidates. Our
> > current mentors have been pressed for time. (We started with five,
> > two have
> since
> > resigned due to other obligations.) Anyone game?
> >
> > Kind regards,
> >
> > Dave Birdsall (member of Trafodion podling PMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

--

Re: Trafodion podling needs more mentors

[John D. Ament]

Dave,

Thanks for the very detailed report.  One comment, which I think I made
earlier, is that we like to see how your community has grown.  So the
numbers don't provide the full details.

I'm curious, from your point of view, how close are you to graduating?  Is
your developer community diverse enough?

John

On Wed, Jun 15, 2016 at 4:27 PM Dave Birdsall 
wrote:

> Hi Martin,
>
> The intended audience for our project are users in the Apache Hadoop
> ecosystem looking for transactional and operational SQL. We provide a
> transactional and operational SQL engine on top of Apache HBase, with some
> support for non-transactional operation on Hive tables. By operational, we
> mean to include large reporting queries that one might do on a
> transactional database.
>
> Here's a pointer to our latest Podling Report (search for the string
> "Trafodion"): https://wiki.apache.org/incubator/June2016
>
> So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was in
> discussion at the time the podling report was written).
>
> Very short-term objectives are we have a patch release 2.0.1 that needs
> approval. Short-term we are likely to have a Release 2.1 within the next
> few months.
>
> Long-term we hope to move to TLP. The biggest issue at the moment is
> expanding our community, as most of the developers and active committers
> are at one company.
>
> Our SDLC is a comprehensive branch model. We actively merge up any patches
> to older branches onto the latest branch. We use git for our source
> control. We use Jenkins to automate build and test of changes before they
> are committed. There is a culture within the podling of quick and thorough
> reviews of code changes. Small changes tend to be committed quickly while
> larger changes take longer. See
> https://github.com/apache/incubator-trafodion.
>
> We have produced a comprehensive set of documentation both of the project
> code itself and of the development process. The former can be found here
> http://trafodion.apache.org (see the Documentation tab), and the latter in
> our wiki
> https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion+Hom
> e (see Trafodion Contributor Guide).
>
> Thanks,
>
> Dave
>
> -Original Message-
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Sent: Wednesday, June 15, 2016 1:06 PM
> To: general@incubator.apache.org
> Subject: RE: Trafodion podling needs more mentors
>
> what have you accomplished thus far?
> what are your short-term objectives..(what do you need by the end of
> 2016)?
>
> what are the long term objectives?
> what is your SDLC...submit jira ..submit patch and testcase and hope
> integration works OR comprehensive branch cut for major new release and
> then hopefully merge sometime later
>
> who is the intended audience for Trafodion?
> Thanks Dave!
> Martin
> __
>
>
>
> > From: dave.birds...@esgyn.com
> > Date: Wed, 15 Jun 2016 12:58:31 -0700
> > Subject: Trafodion podling needs more mentors
> > To: general@incubator.apache.org
> >
> > Hello Incubator community,
> >
> > The incubating Trafodion project needs more mentors. The project is in
> > reasonably good shape from an infrastructure and work-habits point of
> view.
> > We have done two releases now, learning many lessons from that
> experience.
> > But we need more help checking out our release candidates. Our current
> > mentors have been pressed for time. (We started with five, two have
> since
> > resigned due to other obligations.) Anyone game?
> >
> > Kind regards,
> >
> > Dave Birdsall (member of Trafodion podling PMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

RE: Trafodion podling needs more mentors

[Dave Birdsall]

Hi Martin,

The intended audience for our project are users in the Apache Hadoop
ecosystem looking for transactional and operational SQL. We provide a
transactional and operational SQL engine on top of Apache HBase, with some
support for non-transactional operation on Hive tables. By operational, we
mean to include large reporting queries that one might do on a
transactional database.

Here's a pointer to our latest Podling Report (search for the string
"Trafodion"): https://wiki.apache.org/incubator/June2016

So far we have accomplished two releases: 1.3.0 and 2.0.0 (which was in
discussion at the time the podling report was written).

Very short-term objectives are we have a patch release 2.0.1 that needs
approval. Short-term we are likely to have a Release 2.1 within the next
few months.

Long-term we hope to move to TLP. The biggest issue at the moment is
expanding our community, as most of the developers and active committers
are at one company.

Our SDLC is a comprehensive branch model. We actively merge up any patches
to older branches onto the latest branch. We use git for our source
control. We use Jenkins to automate build and test of changes before they
are committed. There is a culture within the podling of quick and thorough
reviews of code changes. Small changes tend to be committed quickly while
larger changes take longer. See
https://github.com/apache/incubator-trafodion.

We have produced a comprehensive set of documentation both of the project
code itself and of the development process. The former can be found here
http://trafodion.apache.org (see the Documentation tab), and the latter in
our wiki
https://cwiki.apache.org/confluence/display/TRAFODION/Apache+Trafodion+Hom
e (see Trafodion Contributor Guide).

Thanks,

Dave

-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Wednesday, June 15, 2016 1:06 PM
To: general@incubator.apache.org
Subject: RE: Trafodion podling needs more mentors

what have you accomplished thus far?
what are your short-term objectives..(what do you need by the end of
2016)?

what are the long term objectives?
what is your SDLC...submit jira ..submit patch and testcase and hope
integration works OR comprehensive branch cut for major new release and
then hopefully merge sometime later

who is the intended audience for Trafodion?
Thanks Dave!
Martin
__



> From: dave.birds...@esgyn.com
> Date: Wed, 15 Jun 2016 12:58:31 -0700
> Subject: Trafodion podling needs more mentors
> To: general@incubator.apache.org
>
> Hello Incubator community,
>
> The incubating Trafodion project needs more mentors. The project is in
> reasonably good shape from an infrastructure and work-habits point of
view.
> We have done two releases now, learning many lessons from that
experience.
> But we need more help checking out our release candidates. Our current
> mentors have been pressed for time. (We started with five, two have
since
> resigned due to other obligations.) Anyone game?
>
> Kind regards,
>
> Dave Birdsall (member of Trafodion podling PMC)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Myriad 0.2.0 (incubating)

[John D. Ament]

Darin,

To determine if a vote is binding, easiest way is to check
http://home.apache.org/phonebook.html

Search for the committer's name (mine is listed as John D. Ament).  If
they're listed as PMC on the incubator, they're binding.

So yes, I'm binding.

John

On Wed, Jun 15, 2016 at 4:05 PM Darin Johnson 
wrote:

> John, just to clarify is your vote binding?
>
> Thanks,
> Darin
>
> On Fri, Jun 10, 2016 at 9:51 AM, John D. Ament 
> wrote:
>
> > That might be the issue then (line length).  I only did a cursory glance
> > looking at line endings and saw diffs.  Either way its a non-issue since
> I
> > was fine with the key provided (having it listed in ldap isn't a
> > requirement).
> >
> > John
> >
> > On Fri, Jun 10, 2016 at 9:49 AM Darin Johnson 
> > wrote:
> >
> > > I just diff'd the second cert in listed in ldap against the key at
> > > https://home.apache.org/~darinj/gpg/2AAE9E3F.asc they were identical
> > > modulo
> > > the header and newlines.  Column widths differ 65 from 73. I'll look
> into
> > > it though.
> > >
> > > Darin
> > >
> > > On Fri, Jun 10, 2016 at 8:03 AM, John D. Ament 
> > > wrote:
> > >
> > > > Nope that's the key on the release, it's an Apache email but not on
> his
> > > > ldap account.  I questioned it when he sent a link.
> > > > On Jun 10, 2016 07:59, "Justin Mclean" 
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > > Just as a note, you have two PGP keys listed in LDAP.  Neither of
> > > which
> > > > > > appears to be the key used to sign this release.
> > > > >
> > > > > Odd I get:
> > > > > gpg: Signature made Wed 25 May 12:20:06 2016 AEST using RSA key ID
> > > > 2AAE9E3F
> > > > > gpg: Good signature from "Darin Johnson (CODE SIGNING KEY) <
> > > > > dar...@apache.org>" [unknown]
> > > > >
> > > > > Guess I must of got the KEY from a previous release / somewhere
> else?
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > > >
> > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>

RE: Trafodion podling needs more mentors

[Martin Gainty]

what have you accomplished thus far?
what are your short-term objectives..(what do you need by the end of 2016)?

what are the long term objectives?
what is your SDLC...submit jira ..submit patch and testcase and hope 
integration works OR
comprehensive branch cut for major new release and then hopefully merge 
sometime later

who is the intended audience for Trafodion?
Thanks Dave!
Martin 
__ 



> From: dave.birds...@esgyn.com
> Date: Wed, 15 Jun 2016 12:58:31 -0700
> Subject: Trafodion podling needs more mentors
> To: general@incubator.apache.org
> 
> Hello Incubator community,
> 
> The incubating Trafodion project needs more mentors. The project is in
> reasonably good shape from an infrastructure and work-habits point of view.
> We have done two releases now, learning many lessons from that experience.
> But we need more help checking out our release candidates. Our current
> mentors have been pressed for time. (We started with five, two have since
> resigned due to other obligations.) Anyone game?
> 
> Kind regards,
> 
> Dave Birdsall (member of Trafodion podling PMC)
  

Re: [VOTE] Release Apache Myriad 0.2.0 (incubating)

[Darin Johnson]

John, just to clarify is your vote binding?

Thanks,
Darin

On Fri, Jun 10, 2016 at 9:51 AM, John D. Ament 
wrote:

> That might be the issue then (line length).  I only did a cursory glance
> looking at line endings and saw diffs.  Either way its a non-issue since I
> was fine with the key provided (having it listed in ldap isn't a
> requirement).
>
> John
>
> On Fri, Jun 10, 2016 at 9:49 AM Darin Johnson 
> wrote:
>
> > I just diff'd the second cert in listed in ldap against the key at
> > https://home.apache.org/~darinj/gpg/2AAE9E3F.asc they were identical
> > modulo
> > the header and newlines.  Column widths differ 65 from 73. I'll look into
> > it though.
> >
> > Darin
> >
> > On Fri, Jun 10, 2016 at 8:03 AM, John D. Ament 
> > wrote:
> >
> > > Nope that's the key on the release, it's an Apache email but not on his
> > > ldap account.  I questioned it when he sent a link.
> > > On Jun 10, 2016 07:59, "Justin Mclean" 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > > Just as a note, you have two PGP keys listed in LDAP.  Neither of
> > which
> > > > > appears to be the key used to sign this release.
> > > >
> > > > Odd I get:
> > > > gpg: Signature made Wed 25 May 12:20:06 2016 AEST using RSA key ID
> > > 2AAE9E3F
> > > > gpg: Good signature from "Darin Johnson (CODE SIGNING KEY) <
> > > > dar...@apache.org>" [unknown]
> > > >
> > > > Guess I must of got the KEY from a previous release / somewhere else?
> > > >
> > > > Thanks,
> > > > Justin
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Trafodion podling needs more mentors

[Dave Birdsall]

Hello Incubator community,

The incubating Trafodion project needs more mentors. The project is in
reasonably good shape from an infrastructure and work-habits point of view.
We have done two releases now, learning many lessons from that experience.
But we need more help checking out our release candidates. Our current
mentors have been pressed for time. (We started with five, two have since
resigned due to other obligations.) Anyone game?

Kind regards,

Dave Birdsall (member of Trafodion podling PMC)

Re: [ALL] Volunteers for a Math IPMC?

[Ted Dunning]

On Wed, Jun 15, 2016 at 10:21 AM, John D. Ament 
wrote:

> Yep absolutely.  I don't think the incubator has ever rejected a project?
>

We have discouraged some submissions. But I have never seen a formal
submission be denied.

Re: [ALL] Volunteers for a Math IPMC?

[John D. Ament]

On Wed, Jun 15, 2016 at 1:17 PM Ted Dunning  wrote:

> Jochen,
>
> The need to build the community (nearly) from scratch is definitely NOT a
> reason for rejection. It is simply a risk factor that must be mitigated to
> succeed in incubation.
>

Yep absolutely.  I don't think the incubator has ever rejected a project?


>
>
> On Tue, Jun 14, 2016 at 10:51 PM, Jochen Wiedmann <
> jochen.wiedm...@gmail.com
> > wrote:
>
> > On Tue, Jun 14, 2016 at 11:29 PM, John D. Ament 
> > wrote:
> >
> > > We generally expect some kind of backing community to bring this to.
> We
> > > have seen pretty consistently that starting from an empty community
> > doesn't
> > > work.  It doesn't mean that it's impossible, but very hard to do.
> >
> > Understood. On the other hand: Would that be sufficient reason for
> > rejecting a proposal? ("It didn't
> > work in the past" != "It won't work in this case")
> >
> >
> > --
> > The next time you hear: "Don't reinvent the wheel!"
> >
> >
> >
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [ALL] Volunteers for a Math IPMC?

[Ted Dunning]

Jochen,

The need to build the community (nearly) from scratch is definitely NOT a
reason for rejection. It is simply a risk factor that must be mitigated to
succeed in incubation.


On Tue, Jun 14, 2016 at 10:51 PM, Jochen Wiedmann  wrote:

> On Tue, Jun 14, 2016 at 11:29 PM, John D. Ament 
> wrote:
>
> > We generally expect some kind of backing community to bring this to.  We
> > have seen pretty consistently that starting from an empty community
> doesn't
> > work.  It doesn't mean that it's impossible, but very hard to do.
>
> Understood. On the other hand: Would that be sufficient reason for
> rejecting a proposal? ("It didn't
> work in the past" != "It won't work in this case")
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

RE: [VOTE] Release Apache Trafodion 2.0.1 (incubating)

[Roberta Marton]

This is a reminder that there is a vote for Apache Trafodion release 2.0.1
(incubating) in progress.
This patch release made a change to now dynamically link in the SSL library.
Thanks for your attention to this matter

Regards,
Roberta


-Original Message-
From: Steve Varnau [mailto:steve.var...@esgyn.com]
Sent: Friday, June 10, 2016 1:47 PM
To: general@incubator.apache.org
Subject: [VOTE] Release Apache Trafodion 2.0.1 (incubating)

Hello,


This is a call to vote on the patch release 2.0.1-incubating (Release
Candidate 1).



The changes were small, just to address things that came up in the 2.0.0
reviews, primarily addressing the issue that prevented providing a
convenience binary of the clients package.



Changes since 2.0.0:

   [TRAFODION-2024] Openssl libraries (ssl & crypto) are linked dynamically

   [TRAFODION-2023] Clarify license text; Also small mods to instructions on
running RAT

   Bump release version number to 2.0.1; Also backported a one line change
to a test expecting specific release number



The trafodion community has approved RC1 for release.

<
https://lists.apache.org/thread.html/428f04f6f2a3d500f31d059a92a44770d2a2b6f59f2a0f33d6a0c93f@%3Cdev.trafodion.apache.org%3E
>



The tag for this candidate is “2.0.1rc1”. Git repository: git://
git.apache.org/incubator-trafodion.git

https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=7f4add54e46bb5395069e2b77bcdfa4024efc006



Release artifacts are:

https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.1-RC1

Artifacts are signed with my key (7F14AF20), which is in

https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS



Instructions:

  Setting up build environment:
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment


  Building:
https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source



[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)



Vote will be open for at least 72 hours, unless cancelled.

I will not be available next week, so Roberta Marton will be following up on
this release.



Thanks,

--Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Pirk into the Apache Incubator

[Tim Ellison]

+1

Tim

On 14/06/16 21:10, Billie Rinaldi wrote:
> Since discussion has died down and we have gotten a couple of additional
> mentor volunteers, I would like to call a VOTE on accepting Pirk into the
> Apache Incubator.
> 
> Proposal: https://wiki.apache.org/incubator/PirkProposal
> 
> [ ] +1 Accept Pirk into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Pirk into the Apache Incubator because…
> 
> This vote will be open for at least 72 hours.
> 
> Here is my +1 (binding).
> 
> Billie
> --
> 
> Pirk Proposal
> 
> Abstract
> 
> Pirk is a framework for scalable Private Information Retrieval (PIR).
> 
> Proposal
> 
> Pirk is a software framework for scalable Private Information Retrieval and
> is meant to provide a landing place for robust, scalable, and practical
> implementations of PIR algorithms. The initial scalable PIR algorithms of
> Pirk were developed at the National Security Agency.
> 
> Background
> 
> Private Information Retrieval (PIR) is an area of computer science and
> mathematics that enables a user/entity to privately and securely obtain
> information from a dataset, to which they have been granted access, without
> revealing, to the dataset owner or to an observer, any information
> regarding the questions asked or the results obtained. Employing
> homomorphic encryption techniques, PIR enables datasets to remain resident
> in their native locations while giving the ability to query the datasets
> with sensitive terms.
> 
> Rationale
> 
> Although PIR has been in existence for over twenty years, it has largely
> remained an academic discipline with very little robust or scalable
> implementation. Pirk not only provides implementations of novel scalable
> PIR algorithms, but it provides a framework into which robust, scalable,
> and practical PIR may be developed.
> 
> Pirk fits well within the Apache Software Foundation (ASF) family as it
> depends on numerous ASF projects and integrates with several others such as
> Hadoop and Spark. We also anticipate developing extensions/adaptors for
> several other ASF projects such as Kafka, Storm, HBase, and Accumulo in the
> near future.
> 
> Initial Goals
> 
> Ensure all dependencies are compliant with Apache License version 2.0
> and that all code and documentation artifacts have the correct Apache
> licensing markings and notice.
> Establish a formal release process and schedule, allowing for
> dependable release cycles in a manner consistent with the Apache
> development process.
> Establish a process which allows different release cycles for the core
> framework, extensions/adaptors, and additional algorithms.
> Grow the community to establish diversity of background and expertise.
> 
> Current Status
> 
> Meritocracy
> 
> We will actively seek help and encourage promotion of influence in the
> project through meritocracy. We will discuss the requirements in an open
> forum. We will encourage and monitor community participation so that
> privileges can be extended to those that contribute.
> 
> Community
> 
> Pirk currently has a community of developers within the U.S. government. In
> open sourcing Pirk we plan to grow the community to a broader base of
> industries and will work to align the interaction of our existing community.
> 
> Core Developers
> 
> The initial core developers are employed by the US Government. We will work
> to grow the community among a more diverse set of developers and industries.
> 
> Alignment
> 
> Pirk was developed with an open source philosophy in mind and the Apache
> way is consistent with the approach we have taken to date. Further, Pirk
> depends on numerous ASF libraries and projects including Hadoop, Spark,
> Commons, and Maven. We also anticipate extensions and dependencies with
> several more ASF projects, including Accumulo, Avro, HBase, Storm, Kafka,
> and others. This existing alignment with Apache and the desired community
> makes the Apache Incubator a good fit for Pirk.
> 
> Known Risks
> 
> Orphaned Products
> 
> Risk of orphaning is limited though it is important to grow the community.
> The project user and developer base is growing and there is already
> operational use of Pirk.
> 
> Inexperience with Open Source
> 
> The initial committers to Pirk have limited experience with true open
> source software development. However, despite the project origins being
> from closed source development we have modeled our behavior and community
> development on The Apache Way to the greatest extent possible. We are
> committed to the ideals of open source software and will eagerly seek out
> mentors and sponsors who can help us quickly come up to speed.
> 
> Homogenous Developers
> 
> The initial committers of Pirk come from a limited set of entities though
> we are committed to recruiting and developing additional committers from a
> broad spectrum of industries and backgrounds.
> 
> Reliance on Salaried Developers
> 
> We expect Pirk development to continue on salar