Re: [DISCUSS] S2Graph Incubator Proposal

[Seetharam Venkatesh]

Hi Hyunsik,

The proposal looks interesting and want to know how is this different from
existing solutions in the same space such as Titan, etc.

Thanks!
Venkatesh


On Fri, Nov 6, 2015 at 1:36 PM Hyunsik Choi  wrote:

> Hi folks,
>
> We would like to start a discussion on S2Graph as an incubation project.
>
> S2Graph is a distributed and scalable OLTP graph database built on
> HBase. It provides interactive queries for vertex/edge/sub-graphs on
> extremely large graph data sets as well as insertion and update
> operations.
>
> S2Graph was already introduced in Apache BigData and HBaseCon this year.
>
> The proposal is available at :
> https://wiki.apache.org/incubator/S2GraphProposal
>
> We are looking forward to any feedback. In addition, we are looking
> for volunteers as mentors.
>
> Best regards,
> Hyunsik
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[larry mccay]

Hi Rich -

I have read it and I think that it is really good.
My concern isn't with the document at all - I think that it would have been
great to have earlier.
IMHO, it should not be a measuring stick as much as a teaching tool.

Mentors helping podlings learn what is meant by The Apache Way and what
sorts of things can be seen in successful podlings and TLPs.

Once the mentors feel that a podling has achieved this understanding this
document doesn't really need to be used as criteria.
As soon as it does then the metrics begin to lose their meaning.

The concerns about adding of PPMC members began to feel like we were going
down that road even though that doesn't seem to be in the maturity model
explicitly. It just highlighted a concern that I have about such metrics.

I don't want to take away from the value of the maturity model and the work
that has been put into it in any way.
The 7 Habits of Successful Podlings really is a great idea and would make
an interesting article. :)

Thanks,

--larry

On Fri, Nov 6, 2015 at 2:55 PM, Rich Bowen  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 11/05/2015 12:49 PM, larry mccay wrote:
> > +1 - I am concerned by the trend that I see developing here.
> >
> > A set of interview questions for evaluation is one thing but
> > criteria checkboxes that will encourage behaviors by rote will not
> > actually develop more healthy communities just communities that can
> > get the boxes checked.
> >
> > While certain metrics like adding PMC members may be indicators of
> > natural growth they should not be required otherwise they will be
> > done artificially.
>
> Given your comments, I'm curious if you've read the document we're
> discussing. It's here:
> https://community.apache.org/apache-way/apache-project-maturity-model.ht
> ml
>
> It's a set of interview questions for evaluation. None of them can
> really be considered checkboxes, since every one of them requires
> quite a bit of research and thought to fill out, and hardly any of
> them will have a clear yes or no answer, but are rather a goal that we
> all continually strive towards. (Sure, some of them are clearly yes or
> no, but most are not.)
>
>
> >
> > On Thu, Nov 5, 2015 at 7:30 AM, Justin Erenkrantz
> >  wrote:
> >
> >> On Wed, Nov 4, 2015 at 12:50 PM, Roman Shaposhnik
> >>  wrote:
> >>> Correct. It is a tool, but not a requirement (at least not
> >>> yet). And since I repeatedly suggested this tool on this thread
> >>> let me explain
> >> why.
> >>
> >> And, this is the root of my concern expressed in the other
> >> general@ thread: I fear that this is going to quickly evolve to
> >> yet another bureaucratic form that the IPMC is going to quickly
> >> require all projects to complete.
> >>
> >> We should not be trying to force rote learning.  Every community
> >> is different.
> >>
> >> Trust the mentors or don't - but, I am very much opposed to more
> >> overhead.  Forcing projects to feel like they have to report
> >> monthly is against what we should be about.  I believe that the
> >> IPMC should be imposing the barest amount of overhead to what the
> >> Board requires from the full projects.  To that end, having
> >> mentors explicitly sign-off is fair - but, additional paperwork
> >> is not.  -- justin
> >>
> >> -
> >>
> >>
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail:
> >> general-h...@incubator.apache.org
> >>
> >>
> >
>
>
> - --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iEYEARECAAYFAlY9BcIACgkQXP03+sx4yJPiSgCeJCN75hYHUk4ZQFsSGgq/yKsw
> nIsAnRM7MS6FmrRJfNvZL3f3Hi8TzdIm
> =QDyV
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] S2Graph Incubator Proposal

[Hyunsik Choi]

Hi Seetharam,

Thank you for a good question. That seem to be a frequent question to
this project.

Here is the answer to your question.
https://steamshon.gitbooks.io/s2graph-book/content/what_is_different_to_titan.html

I hope that this link is helpful to your understanding.

Best regards,
Hyunsik



On Fri, Nov 6, 2015 at 3:07 PM, Seetharam Venkatesh
 wrote:
> Hi Hyunsik,
>
> The proposal looks interesting and want to know how is this different from
> existing solutions in the same space such as Titan, etc.
>
> Thanks!
> Venkatesh
>
>
> On Fri, Nov 6, 2015 at 1:36 PM Hyunsik Choi  wrote:
>
>> Hi folks,
>>
>> We would like to start a discussion on S2Graph as an incubation project.
>>
>> S2Graph is a distributed and scalable OLTP graph database built on
>> HBase. It provides interactive queries for vertex/edge/sub-graphs on
>> extremely large graph data sets as well as insertion and update
>> operations.
>>
>> S2Graph was already introduced in Apache BigData and HBaseCon this year.
>>
>> The proposal is available at :
>> https://wiki.apache.org/incubator/S2GraphProposal
>>
>> We are looking forward to any feedback. In addition, we are looking
>> for volunteers as mentors.
>>
>> Best regards,
>> Hyunsik
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ali Lown]

Hi Ian,

I am not sure about the best way to import this into eclipse, I have
always used the CLI tools directly. I have CC'd the dev-list in case
they have a better answer for you.

The inability to find  ${build.classpath.path}, ${build.macros.path}
suggests that you are missing/failed-to-import/failed-to-reference the
build.properties file which contains the values for these macros.

The follow-up problem about missing define-gxpc is to be expected
because of the above problem resulting in it not importing
build-macros.xml, which defines "define-gxpc" amongst other things.

Ali

On 6 November 2015 at 14:51, Ian Dunlop  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> I'll give it at 0 the moment since I encountered a build issue. I
> downloaded the src zip and imported the code into Eclipse Mars (4.50)
> with jdk 1.7.0_79 & ANT 1.9.4 but found the following issues:
>
> 1)
> BUILD FAILED
> C:\Users\idunlop\workspace\waveinabox\build.xml:28: Cannot find
> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path} imported
> from C:\Users\idunlop\workspace\waveinabox\build.xml
>
> Resolved by commenting out
>
>   
>
>   
>   
>
> and tried again
>
> 2)
>
> BUILD FAILED
> Target "define-gxpc" does not exist in the project "waveinabox". It is
> used from target "gen-gxp".
>
> Resolved by removing define-gxpc from
>
>  depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp">
>  destdir="${gen.dir}/gxp"
> target="org.waveprotocol.box.server.gxp" />
> 
>   
>
> 3)
>
> BUILD FAILED
> C:\Users\idunlop\workspace\waveinabox\build.xml:120: Problem: failed
> to create task or type buildproto
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken
> place.
>
> At that point I figured it best to report the issues here:
>
> Is there a procedure for building in eclipse, am I missing an ant
> setting somewhere?
>
> So, apart fromn the compile issue everything else looks good:
>
> signatures are good
> artifact/hashes good
> DISCLAIMER OK
> LICENCE OK
> NOTICE OK
>
> Cheers,
>
> Ian
>
>
>
> On 04/11/2015 07:14, Justin Mclean wrote:
>> Hi,
>>
>> +1 binding.
>>
>> Could you please fix the LICENCE Appendix in the next release. The
>> text should be "Copyright [] [name of copyright owner]” not
>> "Copyright 2013 The Apache Software Foundation”.
>>
>> I checked: - artefact has incubating in name - signatures and
>> hashes good - DISCLAIMER exists - LICENSE  has minor issue with the
>> copyright in the appendix. Not required but it could also use the
>> sort form in LICENSE [1] particularly as you bundle the software
>> LICENSE files. - NOTICE good. - All source files have Apache
>> headers - No unexpected binary file in source release (but see
>> below) - can compile from source - test pass
>>
>> I notice there’s a couple of photographs in the source release, I
>> assume you have permission from the person who took them to use
>> these? IF so you may want to put that in the LICENSE.
>>
>> There's a number of binary file without extensions in
>> /thumbnail_patterns/ but they all look to be PNGs is this the case?
>> Where did these images come from?
>>
>> I had a quick look at the binary release and the LICENCE and NOTICE
>> appear comprehensive. I didn;t do a though check. I did notice that
>> the year is incorrect in the NOTICE file and LICENSE appendix has
>> the same issue.  It’s actually wrong here as non ASF Apache
>> licensed software is mentioned. There no need to mean Apache
>> licensed software in the LICENCE but no harm is done by donning so.
>> [2]
>>
>> Thanks, Justin
>>
>> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
>>
>>
>>
>> -
>>
>>
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> - --
> Ian Dunlop, eScience Lab
> School of Computer Science
> The University of Manchester
> http://orcid.org/-0001-7066-3350
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJWPL6FAAoJEPK45GBX+Cy5agYH/3yPH2vLCltvOqIZlv70TJ9R
> EmdbRL6rvpJjcah+GH9BPpsYEeENXw5WTARH42RVZT4gFUz62GBIkZhhqFks0/qx
> ubL+bekcivMI2P/eZ3T6S/mKw52d8esRaDvrMKaUZ3Ax3tdkYt/dPaYoXGxAMNS4
> 5IolSgvMaTT2qKlcx0fmCh+gdfmxHFo0ZTvZ55V9ucnmsvQY8orGqZt7SJ+jdySz
> vp9AIvnxStMCorZ8tKSLDVo1H+ciQOXxCZWymFlAlm7nQAw5KoLQYMp/OBUrw6Lk
> urdolruKU7YGgdwh5uV8WHi+cCfpIyQIRaIz8nFlXYTFx/VL8Dm7vrgFpcH1jyw=
> =d5Aa
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [ANNOUNCE] Six new Incubator PMC members

[Jacques Nadeau]

Thanks! Looking forward to helping out in new ways.

On Fri, Nov 6, 2015 at 9:57 PM, Henry Saputra 
wrote:

> Welcome!
>
> On Fri, Nov 6, 2015 at 8:43 PM, Marvin Humphrey 
> wrote:
> > Greetings,
> >
> > I'm delighted to welcome six new members of the Incubator PMC!
> >
> > *   Tom Barber (magicaltrout), PMC Chair of OODT.
> > *   Patrick Wendell (pwendell), PMC member of Spark and committer
> > on Avro and Flume.
> > *   Reynold Xin (rxin), PMC member of Spark.
> > *   Phil Sorber (sorber), PMC member for TrafficServer.
> > *   Julien Le Dem (julien), PMC Chair of Parquet, PMC member of Pig and
> Tez.
> > *   Jacques Nadeau (jacques), PMC Chair of Drill, PMC member of Calcite.
> >
> > Welcome aboard -- we can't wait to see how you will help our podling
> > communities succeed!
> >
> > Marvin Humphrey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [ANNOUNCE] Six new Incubator PMC members

[Jean-Baptiste Onofré]

Welcome aboard guys !

Regards
JB

On 11/07/2015 05:43 AM, Marvin Humphrey wrote:

Greetings,

I'm delighted to welcome six new members of the Incubator PMC!

*   Tom Barber (magicaltrout), PMC Chair of OODT.
*   Patrick Wendell (pwendell), PMC member of Spark and committer
 on Avro and Flume.
*   Reynold Xin (rxin), PMC member of Spark.
*   Phil Sorber (sorber), PMC member for TrafficServer.
*   Julien Le Dem (julien), PMC Chair of Parquet, PMC member of Pig and Tez.
*   Jacques Nadeau (jacques), PMC Chair of Drill, PMC member of Calcite.

Welcome aboard -- we can't wait to see how you will help our podling
communities succeed!

Marvin Humphrey

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



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Greg Stein]

My belief is that committer != PMC is the ideal choice, based on my long
history of watching communities at the ASF. It allows for onboarding
committers rapidly and with a lower bar. That helps to draw them further
into the community, reduces the workload of others (who would otherwise
need to review/apply their work), and provides a mechanism to review
bringing them onto the PMC.

As Greg Reddin notes, separation of the two roles provides a mechanism for
distinguishing between "enable contributions" and "enable governance". As
an old-timer, I've observed (unfortunately) too many problems in
governance. An extra step is advisable (with a higher bar, while keeping
the low bar for contributions).

Cheers,
-g


On Fri, Nov 6, 2015 at 11:34 AM, Dennis E. Hamilton  wrote:

> I think there is a difference between what TLPs do and what the
> recommended approach for Podlings is.
>
> My impression, based on limited podling experience, is that the default
> tends to be PPMC == committer.
>
> Thanks for raising the notion of looking at why committers are *not* moved
> to the PMC of a TLP after some period of time, though.  My question, as a
> PMC member, would be whether or not we are holding the reins too tight at
> the expense of both community and sustainability.  An useful danger sign,
> that.
>
>  - Dennis
>
> > -Original Message-
> > From: Greg Reddin [mailto:gred...@gmail.com]
> > Sent: Friday, November 6, 2015 06:22
> > To: general@incubator.apache.org
> > Subject: Re: Concerning Sentry: A disagreement over the Apache Way and
> > graduation
> >
> > On Fri, Nov 6, 2015 at 7:58 AM, Rich Bowen  wrote:
> > > On 11/05/2015 12:02 AM, Joe Schaefer wrote:
> > >> Committership is the right to do work on the project. PMC membership
> > is the
> > >> right to participate in governance.  People left in the nebulous
> > state
> > >> between
> > >> committership and PMC membership for long periods of time more than
> > likely
> > >> will give up in frustration for not being trusted enough to govern
> > their
> > >> own work.
> > >
> > >
> > > Most of the older projects at the Foundation do not have PMC ==
> > > Committer. Notably, httpd. The notion that committers are
> > automatically
> > > PMC is a fairly new innovation. As it happens, it's an innovation that
> > I
> > > wholeheartedly support and recommend, but it's a minority of projects
> > > that have this policy. If you follow board reports, you'll notice that
> > > PMC additions and Committer additions are seldom coincident.
> >
> > In further support of Joe's point, for most of the projects I've been
> > involved with, the PMC promotion was almost automatic and occurred
> > within about 6 months of committership. The committer-only period was
> > just a probationary period to make sure a person was not going to
> > abuse his/her privileges. An invite to committership comes with an
> > unspoken assumption that we want you to help govern the project, but
> > let's start with giving you access. I don't know that I ever saw
> > anyone stay as committer-only for an extended period of time.
> >
> > Greg
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [ANNOUNCE] Six new Incubator PMC members

[Henry Saputra]

Welcome!

On Fri, Nov 6, 2015 at 8:43 PM, Marvin Humphrey  wrote:
> Greetings,
>
> I'm delighted to welcome six new members of the Incubator PMC!
>
> *   Tom Barber (magicaltrout), PMC Chair of OODT.
> *   Patrick Wendell (pwendell), PMC member of Spark and committer
> on Avro and Flume.
> *   Reynold Xin (rxin), PMC member of Spark.
> *   Phil Sorber (sorber), PMC member for TrafficServer.
> *   Julien Le Dem (julien), PMC Chair of Parquet, PMC member of Pig and Tez.
> *   Jacques Nadeau (jacques), PMC Chair of Drill, PMC member of Calcite.
>
> Welcome aboard -- we can't wait to see how you will help our podling
> communities succeed!
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

[ANNOUNCE] Six new Incubator PMC members

[Marvin Humphrey]

Greetings,

I'm delighted to welcome six new members of the Incubator PMC!

*   Tom Barber (magicaltrout), PMC Chair of OODT.
*   Patrick Wendell (pwendell), PMC member of Spark and committer
on Avro and Flume.
*   Reynold Xin (rxin), PMC member of Spark.
*   Phil Sorber (sorber), PMC member for TrafficServer.
*   Julien Le Dem (julien), PMC Chair of Parquet, PMC member of Pig and Tez.
*   Jacques Nadeau (jacques), PMC Chair of Drill, PMC member of Calcite.

Welcome aboard -- we can't wait to see how you will help our podling
communities succeed!

Marvin Humphrey

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

Re: maturity guidelines (was Re: Concerning Sentry: A disagreement over the Apache Way and graduation)

[Bertrand Delacretaz]

On Thu, Nov 5, 2015 at 10:33 PM, Joe Schaefer  wrote:
> I don't think anybody is pining to make compliance with Bertrand's very nice
> document into a policy document

As a sidenote the maturity model is not "my" document. I did initiate
that effort but it's been greatly enhanced by contributions from
various people on the comdev list. There's a link to those discussions
at the top of 
https://community.apache.org/apache-way/apache-project-maturity-model.html
if you're curious.

-Bertrand

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

Re: [DISCUSS] Graduate REEF

[Marvin Humphrey]

On Mon, Nov 2, 2015 at 3:27 PM, Chris Douglas  wrote:
> Heh; yes, you're right. As one of REEF's mentors, I'll add some of my
> observations of its community and development.
>
> The REEF project has built an open, welcoming, and diverse community.
> From my sampling of the dev@ list over the last year or so, all design
> discussions (including infrastructure, build, and coding conventions)
> are at the ASF [1,2,3]. The project also rotates release managers
> [4,5], does solid code reviews, and has taken its IP hygiene
> seriously. The most common affiliations (Microsoft, Seoul National
> University) have not formed cliques, neither have members failed to
> bring discussion to the dev list despite shared affiliation [6] and a
> significant timezone gap.
>
> From all I've observed, the project groks the Apache Way and is ready
> to be a TLP. -C
>
> [1] http://s.apache.org/ys
> [2] http://s.apache.org/OKo
> [3] http://s.apache.org/NQy
> [4] http://s.apache.org/Tb5
> [5] http://s.apache.org/iaD
> [6] http://s.apache.org/DX7

Chris, thanks much for putting together this documented testimonial!  It will
be great to have REEF as a TLP.

I checked over the resolution and it looks good except for one thing I'm not
certain about -- the two scope statements don't agree precisely.  One speaks
of "a software framework" and the other, "ease of development":

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to the ease of development of applications on
 top of resource managers.

 RESOLVED, that the Apache REEF Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for application development on top of resource
 managers; and be it further

In all the other resolutions I've seen, the scope statements are the same.
Common sense tells me that this shouldn't be a big deal -- but common sense
also tells me that the redundant scope statements in these resolutions are
goofy, which is probably the wrong reading for this sort of legalese. :)

Was the discrepancy deliberate?  If not, perhaps pick the one folks like more
and bring the two instances into sync.

Marvin Humphrey

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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Greg Reddin]

On Fri, Nov 6, 2015 at 7:58 AM, Rich Bowen  wrote:
> On 11/05/2015 12:02 AM, Joe Schaefer wrote:
>> Committership is the right to do work on the project. PMC membership is the
>> right to participate in governance.  People left in the nebulous state
>> between
>> committership and PMC membership for long periods of time more than likely
>> will give up in frustration for not being trusted enough to govern their
>> own work.
>
>
> Most of the older projects at the Foundation do not have PMC ==
> Committer. Notably, httpd. The notion that committers are automatically
> PMC is a fairly new innovation. As it happens, it's an innovation that I
> wholeheartedly support and recommend, but it's a minority of projects
> that have this policy. If you follow board reports, you'll notice that
> PMC additions and Committer additions are seldom coincident.

In further support of Joe's point, for most of the projects I've been
involved with, the PMC promotion was almost automatic and occurred
within about 6 months of committership. The committer-only period was
just a probationary period to make sure a person was not going to
abuse his/her privileges. An invite to committership comes with an
unspoken assumption that we want you to help govern the project, but
let's start with giving you access. I don't know that I ever saw
anyone stay as committer-only for an extended period of time.

Greg

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

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

I'll give it at 0 the moment since I encountered a build issue. I
downloaded the src zip and imported the code into Eclipse Mars (4.50)
with jdk 1.7.0_79 & ANT 1.9.4 but found the following issues:

1)
BUILD FAILED
C:\Users\idunlop\workspace\waveinabox\build.xml:28: Cannot find
C:\Users\idunlop\workspace\waveinabox\${build.classpath.path} imported
from C:\Users\idunlop\workspace\waveinabox\build.xml

Resolved by commenting out

  

  
  

and tried again

2)

BUILD FAILED
Target "define-gxpc" does not exist in the project "waveinabox". It is
used from target "gen-gxp".

Resolved by removing define-gxpc from

  


  

3)

BUILD FAILED
C:\Users\idunlop\workspace\waveinabox\build.xml:120: Problem: failed
to create task or type buildproto
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken
place.

At that point I figured it best to report the issues here:

Is there a procedure for building in eclipse, am I missing an ant
setting somewhere?

So, apart fromn the compile issue everything else looks good:

signatures are good
artifact/hashes good
DISCLAIMER OK
LICENCE OK
NOTICE OK

Cheers,

Ian



On 04/11/2015 07:14, Justin Mclean wrote:
> Hi,
> 
> +1 binding.
> 
> Could you please fix the LICENCE Appendix in the next release. The
> text should be "Copyright [] [name of copyright owner]” not
> "Copyright 2013 The Apache Software Foundation”.
> 
> I checked: - artefact has incubating in name - signatures and
> hashes good - DISCLAIMER exists - LICENSE  has minor issue with the
> copyright in the appendix. Not required but it could also use the
> sort form in LICENSE [1] particularly as you bundle the software
> LICENSE files. - NOTICE good. - All source files have Apache
> headers - No unexpected binary file in source release (but see
> below) - can compile from source - test pass
> 
> I notice there’s a couple of photographs in the source release, I
> assume you have permission from the person who took them to use
> these? IF so you may want to put that in the LICENSE.
> 
> There's a number of binary file without extensions in
> /thumbnail_patterns/ but they all look to be PNGs is this the case?
> Where did these images come from?
> 
> I had a quick look at the binary release and the LICENCE and NOTICE
> appear comprehensive. I didn;t do a though check. I did notice that
> the year is incorrect in the NOTICE file and LICENSE appendix has
> the same issue.  It’s actually wrong here as non ASF Apache
> licensed software is mentioned. There no need to mean Apache
> licensed software in the LICENCE but no harm is done by donning so.
> [2]
> 
> Thanks, Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps 
> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> 
> 
> 
> -
>
> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

- -- 
Ian Dunlop, eScience Lab
School of Computer Science
The University of Manchester
http://orcid.org/-0001-7066-3350
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWPL6FAAoJEPK45GBX+Cy5agYH/3yPH2vLCltvOqIZlv70TJ9R
EmdbRL6rvpJjcah+GH9BPpsYEeENXw5WTARH42RVZT4gFUz62GBIkZhhqFks0/qx
ubL+bekcivMI2P/eZ3T6S/mKw52d8esRaDvrMKaUZ3Ax3tdkYt/dPaYoXGxAMNS4
5IolSgvMaTT2qKlcx0fmCh+gdfmxHFo0ZTvZ55V9ucnmsvQY8orGqZt7SJ+jdySz
vp9AIvnxStMCorZ8tKSLDVo1H+ciQOXxCZWymFlAlm7nQAw5KoLQYMp/OBUrw6Lk
urdolruKU7YGgdwh5uV8WHi+cCfpIyQIRaIz8nFlXYTFx/VL8Dm7vrgFpcH1jyw=
=d5Aa
-END PGP SIGNATURE-

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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Martijn Dashorst]

On Fri, Nov 6, 2015 at 2:58 PM, Rich Bowen  wrote:
> On 11/05/2015 12:02 AM, Joe Schaefer wrote:
>> Committership is the right to do work on the project. PMC membership is the
>> right to participate in governance.  People left in the nebulous state
>> between
>> committership and PMC membership for long periods of time more than likely
>> will give up in frustration for not being trusted enough to govern their
>> own work.
>
> Most of the older projects at the Foundation do not have PMC ==
> Committer. Notably, httpd. The notion that committers are automatically
> PMC is a fairly new innovation. As it happens, it's an innovation that I
> wholeheartedly support and recommend, but it's a minority of projects
> that have this policy. If you follow board reports, you'll notice that
> PMC additions and Committer additions are seldom coincident.

As a (PMC) Member I've always taken (one of) Roy's mantra to heart:
those that do the work should steer the project. At Wicket we have
committer == PMC, and I'd posit we are now among the 'Older' projects
(given our 8 years here). Wicket just counts as one project so this
doesn't invalidate your point, but adds a datapoint.

Martijn

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

Re: [VOTE] Apache Sirona 0.3-incubating

[Romain Manni-Bucau]

Hi Justin,

thanks, I opened https://issues.apache.org/jira/browse/SIRONA-49

also noted the point about git hashes!


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-11-05 20:54 GMT-08:00 Justin Mclean :

> Hi,
>
> +1 (binding) but only if you raise a JIRA and fix up LICENSE and NOTICE
> issues for the next release.
>
>  Everything here is permissive so it's more a documentation issue than an
> licensing error.
>
> For the next release could you mind mentioning the git/svn hash that the
> released code corresponds to.
>
> I checked:
> - file contains incubating
> - DISCLAIMER exists
> - LICENSE and NOTICE have some issues
> - NOTICE has incorrect year
> - All source file had Apace headers (except a couple of shell scripts)
> - No unexpected binary files
> - Can compile from source
>
> As per [1][2] LICENSE should include:
>  - bootstrap (MIT)
>  - normalize.css (MIT)
>  - datetimepicker (MIT)
>  - fontawesome (MIT)
>  - font awesome fonts (SIL open font licence)
>  - angular (MIT)
>  - JQuery (MIT)
>  - moment.js (MIT)
>  - ng-grid (MIT)
>  - RequireJS (MIT or BSD)
>  - angular-ui-bootstrap (MIT)
>  - jquery.flot (MIT)
>  - raphael (MIT or BSD)
>  - jquery.tablesorter (MIT)
>  - morris.js (BSD)
>  - angular-bootstrap-nav-tree (MIT)
>
> I may of missed one or two from a quick glance I took. Basically anything
> that’s  MIT or BSD licensed that's bundled in this source release needs to
> be added to LICENSE. [2] None of these need to be mentioned in NOTICE. [3]
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 3. http://www.apache.org/dev/licensing-howto.html#mod-notice
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Apache Sirona 0.3-incubating

[Romain Manni-Bucau]

and with my +1 the vote passes with:

binding +1:
- Mark, Jean-Baptiste, Olivier, Jean-Louis, Justin, me

and no -1.

I'll promote the binaries now.



Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-11-06 8:47 GMT-08:00 Romain Manni-Bucau :

> Hi Justin,
>
> thanks, I opened https://issues.apache.org/jira/browse/SIRONA-49
>
> also noted the point about git hashes!
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github
>  | LinkedIn
>  | Tomitriber
> 
>
> 2015-11-05 20:54 GMT-08:00 Justin Mclean :
>
>> Hi,
>>
>> +1 (binding) but only if you raise a JIRA and fix up LICENSE and NOTICE
>> issues for the next release.
>>
>>  Everything here is permissive so it's more a documentation issue than an
>> licensing error.
>>
>> For the next release could you mind mentioning the git/svn hash that the
>> released code corresponds to.
>>
>> I checked:
>> - file contains incubating
>> - DISCLAIMER exists
>> - LICENSE and NOTICE have some issues
>> - NOTICE has incorrect year
>> - All source file had Apace headers (except a couple of shell scripts)
>> - No unexpected binary files
>> - Can compile from source
>>
>> As per [1][2] LICENSE should include:
>>  - bootstrap (MIT)
>>  - normalize.css (MIT)
>>  - datetimepicker (MIT)
>>  - fontawesome (MIT)
>>  - font awesome fonts (SIL open font licence)
>>  - angular (MIT)
>>  - JQuery (MIT)
>>  - moment.js (MIT)
>>  - ng-grid (MIT)
>>  - RequireJS (MIT or BSD)
>>  - angular-ui-bootstrap (MIT)
>>  - jquery.flot (MIT)
>>  - raphael (MIT or BSD)
>>  - jquery.tablesorter (MIT)
>>  - morris.js (BSD)
>>  - angular-bootstrap-nav-tree (MIT)
>>
>> I may of missed one or two from a quick glance I took. Basically anything
>> that’s  MIT or BSD licensed that's bundled in this source release needs to
>> be added to LICENSE. [2] None of these need to be mentioned in NOTICE. [3]
>>
>> Thanks,
>> Justin
>>
>> 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
>> 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 3. http://www.apache.org/dev/licensing-howto.html#mod-notice
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

RE: Concerning Sentry: A disagreement over the Apache Way and graduation

[Dennis E. Hamilton]

I think there is a difference between what TLPs do and what the recommended 
approach for Podlings is.

My impression, based on limited podling experience, is that the default tends 
to be PPMC == committer.

Thanks for raising the notion of looking at why committers are *not* moved to 
the PMC of a TLP after some period of time, though.  My question, as a PMC 
member, would be whether or not we are holding the reins too tight at the 
expense of both community and sustainability.  An useful danger sign, that.

 - Dennis

> -Original Message-
> From: Greg Reddin [mailto:gred...@gmail.com]
> Sent: Friday, November 6, 2015 06:22
> To: general@incubator.apache.org
> Subject: Re: Concerning Sentry: A disagreement over the Apache Way and
> graduation
> 
> On Fri, Nov 6, 2015 at 7:58 AM, Rich Bowen  wrote:
> > On 11/05/2015 12:02 AM, Joe Schaefer wrote:
> >> Committership is the right to do work on the project. PMC membership
> is the
> >> right to participate in governance.  People left in the nebulous
> state
> >> between
> >> committership and PMC membership for long periods of time more than
> likely
> >> will give up in frustration for not being trusted enough to govern
> their
> >> own work.
> >
> >
> > Most of the older projects at the Foundation do not have PMC ==
> > Committer. Notably, httpd. The notion that committers are
> automatically
> > PMC is a fairly new innovation. As it happens, it's an innovation that
> I
> > wholeheartedly support and recommend, but it's a minority of projects
> > that have this policy. If you follow board reports, you'll notice that
> > PMC additions and Committer additions are seldom coincident.
> 
> In further support of Joe's point, for most of the projects I've been
> involved with, the PMC promotion was almost automatic and occurred
> within about 6 months of committership. The committer-only period was
> just a probationary period to make sure a person was not going to
> abuse his/her privileges. An invite to committership comes with an
> unspoken assumption that we want you to help govern the project, but
> let's start with giving you access. I don't know that I ever saw
> anyone stay as committer-only for an extended period of time.
> 
> Greg
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org


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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Rich Bowen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/05/2015 12:49 PM, larry mccay wrote:
> +1 - I am concerned by the trend that I see developing here.
> 
> A set of interview questions for evaluation is one thing but
> criteria checkboxes that will encourage behaviors by rote will not
> actually develop more healthy communities just communities that can
> get the boxes checked.
> 
> While certain metrics like adding PMC members may be indicators of
> natural growth they should not be required otherwise they will be
> done artificially.

Given your comments, I'm curious if you've read the document we're
discussing. It's here:
https://community.apache.org/apache-way/apache-project-maturity-model.ht
ml

It's a set of interview questions for evaluation. None of them can
really be considered checkboxes, since every one of them requires
quite a bit of research and thought to fill out, and hardly any of
them will have a clear yes or no answer, but are rather a goal that we
all continually strive towards. (Sure, some of them are clearly yes or
no, but most are not.)


> 
> On Thu, Nov 5, 2015 at 7:30 AM, Justin Erenkrantz
>  wrote:
> 
>> On Wed, Nov 4, 2015 at 12:50 PM, Roman Shaposhnik
>>  wrote:
>>> Correct. It is a tool, but not a requirement (at least not
>>> yet). And since I repeatedly suggested this tool on this thread
>>> let me explain
>> why.
>> 
>> And, this is the root of my concern expressed in the other
>> general@ thread: I fear that this is going to quickly evolve to
>> yet another bureaucratic form that the IPMC is going to quickly
>> require all projects to complete.
>> 
>> We should not be trying to force rote learning.  Every community
>> is different.
>> 
>> Trust the mentors or don't - but, I am very much opposed to more 
>> overhead.  Forcing projects to feel like they have to report
>> monthly is against what we should be about.  I believe that the
>> IPMC should be imposing the barest amount of overhead to what the
>> Board requires from the full projects.  To that end, having
>> mentors explicitly sign-off is fair - but, additional paperwork
>> is not.  -- justin
>> 
>> -
>>
>> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail:
>> general-h...@incubator.apache.org
>> 
>> 
> 


- -- 
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlY9BcIACgkQXP03+sx4yJPiSgCeJCN75hYHUk4ZQFsSGgq/yKsw
nIsAnRM7MS6FmrRJfNvZL3f3Hi8TzdIm
=QDyV
-END PGP SIGNATURE-

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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Rich Bowen]

On 11/05/2015 12:02 AM, Joe Schaefer wrote:
> Committership is the right to do work on the project. PMC membership is the
> right to participate in governance.  People left in the nebulous state
> between
> committership and PMC membership for long periods of time more than likely
> will give up in frustration for not being trusted enough to govern their
> own work.


Most of the older projects at the Foundation do not have PMC ==
Committer. Notably, httpd. The notion that committers are automatically
PMC is a fairly new innovation. As it happens, it's an innovation that I
wholeheartedly support and recommend, but it's a minority of projects
that have this policy. If you follow board reports, you'll notice that
PMC additions and Committer additions are seldom coincident.


-- 
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

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

[DISCUSS] S2Graph Incubator Proposal

[Hyunsik Choi]

Hi folks,

We would like to start a discussion on S2Graph as an incubation project.

S2Graph is a distributed and scalable OLTP graph database built on
HBase. It provides interactive queries for vertex/edge/sub-graphs on
extremely large graph data sets as well as insertion and update
operations.

S2Graph was already introduced in Apache BigData and HBaseCon this year.

The proposal is available at :
https://wiki.apache.org/incubator/S2GraphProposal

We are looking forward to any feedback. In addition, we are looking
for volunteers as mentors.

Best regards,
Hyunsik

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