Re: Source code dumps via JIRA?

[Chris Mattmann]

Hi All,

 For OODT, we think we want to import the prior history of the project
 into the podling via a Subversion dump file. However, in:
 
 http://incubator.apache.org/guides/mentor.html#initial-import-code-dump
 
 it says:
 
 ---
 In either case, the code to be imported should be attached to a JIRA
 and then imported. It is recommended that the previous version control
 system is tagged so that the imported version is precisely known.
 
 A public record MUST be made of the code imported. If the import is
 not attached to JIRA then it MUST be committed to version control.
 ---
 
 I can understand the rationale for having a public record, but I'm not
 seeing the reasoning for JIRA.
 
 Can someone please shed some light on this?  Is this really reflective
 of actual best practices?
 
 As a counter-example, I'd believe providing a URL to the dump (or
 uploading it to people.a.o) and providing a SHA checksum via email
 (PGP-signed?) would be sufficient for our purposes.  -- justin

My (non-binding) +1 to this.

Cheers,
Chris




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

Re: Clerezza, Stanbol, Jena, Semantic Commons, WDYT?

[Chris Mattmann]

Correction: actually not sure about 2003 but seems like we been using it for 
that long!

Cheers,
Chris 
Sent from my Verizon Wireless BlackBerry

-Original Message-
From: Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov
Date: Mon, 8 Nov 2010 07:09:13 
To: general@incubator.apache.orggeneral@incubator.apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Clerezza, Stanbol, Jena, Semantic Commons, WDYT?

Wow! Jena is proposing to come to Apache??! Sweet! We've used it in OODT since 
2003...looking forward to it!

Cheers,
Chris


On 11/8/10 7:04 AM, Ross Gardler rgard...@apache.org wrote:

As champion for Jena I agree in principle. I can't speak for the Jena team if 
course, but representatives are tracking this list and have started discussing 
in their project list.

I will be making the formal Jena proposal here very soon (just as soon as I'm 
not limited to the iPhone) - its in the wiki if people want a preview.

Ross



Sent from my mobile device.

On 8 Nov 2010, at 14:54, Bertrand Delacretaz bdelacre...@apache.org wrote:

 Hi,

 I'm following up on discussions here regarding relationships between
 the incubating Clerezza podling and incoming Stanbol and Jena podlings
 (see proposals at http://wiki.apache.org/incubator).

 Do people agree with the following structure?

 1. Clerezza, Stanbol and Jena are independent podlings, each aiming
 for top-level status

 2. A Semantic Commons area is created for common code between these
 (and other) projects. Details to be discussed, this does probably not
 warrant a separate Apache project, but might be managed by Clerezza,
 as they were here first.

 3. It is expected that those projects will have a number of committers
 in common, as there are many collaboration possibilities.

 WDYT?

 -Bertrand

 -
 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




++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

Re: [PROPOSAL] Aurora for Incubation

[Chris Mattmann]

 team and Apache Mesos means there is an awareness of the
incubation process and a willingness to embrace The Apache Way.

== Homogenous Developers ==

The initial set of committers are from a single organization, however we
expect that once approved for incubation the project will attract
contributors from more organizations. We have already had conversations
with other companies who have expressed an interest in Aurora.

== Reliance on Salaried Developers ==

Initial Aurora committers are salaried developers at Twitter, however
shortly after open sourcing the code we plan to diversify the project¹s
core committers and contributors.

== Relationships with Other Apache Products ==

Initially, Aurora has been developed as a scheduler for Apache Mesos.
Additionally, it relies on ZooKeeper for service discovery, allowing
servers to register at a location and clients to subsequently discover the
servers.

== An Excessive Fascination with the Apache Brand ==

While we respect the reputation of the Apache brand and have no doubts
that
it will attract contributors and users, our interest is primarily to give
Aurora a solid home as an open source project following an established
development model. We have also given reasons in the Rationale and
Alignment sections.

= Documentation =

This proposal exists online as
http://wiki.apache.org/incubator/AuroraProposal. Project documentation
exists and will be released at the same time as an initial code push.

= Initial Source =

JIRA Aurora (AURORA)

Source and Intellectual Property Submission Plan
The current codebase is available upon request.

= External Dependencies =

All Aurora dependencies have Apache compatible licenses, except cron4j
(LGPL). An alternative library, most likely Quartz (Apache Public License
2.0) will be used prior to an initial code push.

= Cryptography =
Not applicable.

= Required Resources =

== Mailing Lists ==

 * aurora-private for private PMC discussions
 * aurora-dev
 * aurora-commits
 * aurora-user
 * aurora-issues

== Subversion Directory ==

We prefer to use Git as our source control system: git://
git.apache.org/aurora

== Issue Tracking ==

JIRA Aurora (AURORA)

= Initial Committers =

 * William Farner (bill at twitter dot com)
 * Brian Wickman (wickman at twitter dot com)
 * Kevin Sweeney (ksweeney at twitter dot com)
 * Sathya Hariesh (sathya at twitter dot com)
 * Jonathan Boulle (jon at twitter dot com)
 * Maxim Khutornenko (mkhutornenko at twitter dot com)
 * Suman Karumuri (skarumuri at twitter dot com)
 * Dave Lester (dlester at twitter dot com)

= Affiliations =

Twitter

= Interested Parties =

 * Airbnb
 * Foursquare
 * Mesosphere

= Sponsors =

== Champion ==

Ben Hindman

== Nominated Mentors ==

 * Chris Mattmann
 * Ben Hindman

== Sponsoring Entity ==
Incubator PMC



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

[ANNOUNCE] Ben Hindman as Apache Incubator PMC member!

[Chris Mattmann]

Hi Folks,

The IPMC has VOTEd to add Ben Hindman as an Apache Incubator PMC
member. Welcome Ben!

Please feel free to say a bit about yourself.

Cheers,
Chris



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

Re: [ANNOUNCE] Andrei Savu joins the IPMC

[Chris Mattmann]

Welcome, Andrei!



-Original Message-
From: Marvin Humphrey mar...@rectangular.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Tuesday, September 10, 2013 9:17 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: [ANNOUNCE] Andrei Savu joins the IPMC

Greets,

The Incubator PMC has VOTEd to add new member Andrei Savu.

Welcome, Andrei!

Marvin Humphrey, on behalf of the Incubator PMC

-
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] Usergrid BaaS Stack for Apache Incubator

[Chris Mattmann]

+1 from me (binding).

G'luck!

Cheers,
Chris


-Original Message-
From: Jim Jagielski j...@jagunet.com
Reply-To: general@incubator.apache.org general@incubator.apache.org,
general@incubator.apache.org general@incubator.apache.org
Date: Monday, September 23, 2013 5:44 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: [VOTE] Usergrid BaaS Stack for Apache Incubator

After a useful and successful proposal cycle, I would like to propose
a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service
stack for web  mobile applications based on RESTful APIs, as an Apache
Incubator podling.

Voting to run for 72+ hours...

Here is a link to the proposal:
  https://wiki.apache.org/incubator/UsergridProposal

It is also pasted below:

= Usergrid Proposal =

== Abstract ==

Usergrid is a multi-tenant Backend-as-a-Service stack for web  mobile
applications, based on RESTful APIs.


== Proposal ==

Usergrid is an open-source Backend-as-a-Service (³BaaS² or ³mBaaS²)
composed
of an integrated distributed NoSQL database, application layer and client
tier with SDKs for developers looking to rapidly build web and/or mobile
applications. It provides elementary services (user registration 
management, data storage, file storage, queues) and retrieval features
(full
text search, geolocation search, joins) to power common app features.

It is a multi-tenant system designed for deployment to public cloud
environments (such as Amazon Web Services, Rackspace, etc.) or to run on
traditional server infrastructures so that anyone can run their own
private
BaaS deployment.

For architects and back-end teams, it aims to provide a distributed,
easily
extendable, operationally predictable and highly scalable solution. For
front-end developers, it aims to simplify the development process by
enabling them to rapidly build and operate mobile and web applications
without requiring backend expertise.


== Background ==

Developing web or mobile applications obviously necessitates writing and
maintaining more than just front-end code. Even simple applications can
implicitly rely on server code being run to store users, perform database
queries, serve images and video files, etc. Developing and maintaining
such
backend services requires skills not always available or expected of app
development teams. Beyond that, the proliferation of apps inside of
companies leads to the creation of many different, ad-hoc, unequally
maintained backend solutions created by employees and contractors alike
and
hosted on a wide variety of environments. This is causing poor resource
usage, operational issues, as well as security, privacy  compliance
concerns.

In response to this problem, companies have long tried to standardize
their
server-side stack or unify them behind an ESB or API strategy.
Backends-as-a-Service follow a similar approach but their unique
characteristic is strongly tying  1) a persistence tier (typically a
database), 2) a server-side application tier delivering a set of common
services and 3) a set of client-side application interface mechanisms. For
example, a BaaS could package 1) MongoDB with 2) a node.js application
that
offers access through 3) WebSockets. In the case of Usergrid, the trifecta
is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.

The Backend-as-a-Service approach has steadily gained popularity in the
last
few years with cloud providers such Parse.com, Stackmob.com and
Kinvey.com,
each operating tens of thousands of apps for tens of thousands of
developers. The trend has already reached large organizations as well,
with
global companies such as Korea Telecom internally building a privately-run
BaaS platform. But so far, there have been limited options for developers
that want a non-proprietary, open option for hosting and providing these
services themselves, or for enterprise and government users who want to
provide these capabilities from their own data centers, especially on a
very
large scale.


== Rationale ==

The issue this proposal deals with is implicit in the name.
Backend-as-a-Service platforms are usually offered solely as proprietary
cloud services. They are typically closed sourced, hosted on public
clouds,
and require subscription payment. Usergrid opens the playing field, by
making a fully-featured BaaS platform freely available to all. This
includes
developers that previously could not afford them, such as mobile
enthusiasts, small boutiques, and cost-sensitive startups. This also
includes large companies that benefit from a reference implementation they
can deploy in trust, or extend to their needs without losing time writing
less-vetted, less-performant boilerplate functionality.

Usergrid has been open source since 2011 and has grown as an independent
project, garnering 11 primary committers, 35 total contributors, 260+
participants on its mailing list, with 3,700+ commits, 200+ external
contributions, 350+ stars and 100+ forks on Github, not to mention several

Re: [VOTE] Accept Aurora for Apache Incubation

[Chris Mattmann]

.

== Relationships with Other Apache Products ==

Initially, Aurora has been developed as a scheduler for Apache Mesos.
Additionally, it relies on ZooKeeper for service discovery, allowing
servers to register at a location and clients to subsequently discover the
servers.

== An Excessive Fascination with the Apache Brand ==

While we respect the reputation of the Apache brand and have no doubts
that
it will attract contributors and users, our interest is primarily to give
Aurora a solid home as an open source project following an established
development model. We have also given reasons in the Rationale and
Alignment sections.

= Documentation =

This proposal exists online as
http://wiki.apache.org/incubator/AuroraProposal. Basic build instructions
are included in the existing github repository, and the source code has
thorough documentation. User documentation exists internally to Twitter,
and as part of incubation will be adapted to share and improve user
documentation overall.

= Initial Source =

JIRA Aurora (AURORA)

= Source and Intellectual Property Submission Plan =

A snapshot of the Aurora scheduler has been posted on github for review:
https://github.com/twitter/aurora

= External Dependencies =

All Aurora dependencies have Apache compatible licenses.

= Cryptography =
Not applicable.

= Required Resources =

== Mailing Lists ==

 * aurora-private for private PMC discussions
 * aurora-dev
 * aurora-commits

== Subversion Directory ==

We prefer to use Git as our source control system: git://
git.apache.org/aurora

== Issue Tracking ==

JIRA Aurora (AURORA)

= Initial Committers =

 * Jonathan Boulle (jon at twitter dot com)
 * William Farner (bill at twitter dot com)
 * Suman Karumuri (skarumuri at twitter dot com)
 * Maxim Khutornenko (mkhutornenko at twitter dot com)
 * Dave Lester (dlester at twitter dot com)
 * Kevin Sweeney (ksweeney at twitter dot com)
 * Brian Wickman (wickman at twitter dot com)

= Affiliations =

Twitter

= Sponsors =

== Champion ==

 * Benjamin Hindman (benh at apache dot org)

== Nominated Mentors ==

 * Jake Farrell (jfarrell at apache dot org)
 * Benjamin Hindman (benh at apache dot org)
 * Chris Mattmann (mattmann at apache dot org)
 * Henry Saputra (hsaputra at apache dot org)

== Sponsoring Entity ==
Incubator PMC



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

Re: [RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Chris Mattmann]

Hi David,

Just an FYI I also VOTEd +1 on this.
Congrats and good luck!

Cheers,
Chris


-Original Message-
From: David Crossley cross...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, October 4, 2013 5:08 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: [RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised
proposal)

Adjusting the email Subject to [RESULT][VOTE] ...
to enable the voting status monitor:
http://incubator.apache.org/facilities.html#voting-status

-David

Dave wrote:
 I am officially closing the vote. We have 11 binding +1 votes, 4
 non-binding votes and no -1 notes. Usergrid is now officially part of
the
 Apache Incubator. Thanks to everybody who helped put together the
proposal,
 those who joined the discussion, those who voted and the Usergrid
community.
 
 +1 binding votes
 
Afkham Azeez
Alan D. Cabrera
Alex Karasulu
Ate Douma
Bertrand Delacretaz
Chip Childers
David Nalley
Henry Saputra
Jim Jagielski
Luciano Resende
Marvin Humphrey
 
 +1 non-binding
 
Larry McCay
Lewis John Mcgibbney
Lieven Govaerts
Raminder Singh
 
 Totals
 
11 binding +1 votes
4 non-binding +1 votes
0 -1 votes
 
 Thanks,
 Dave
 
 
 PS. this also happens to be the 2nd anniversary of the day that Usergrid
 was released on Github. Happy Birthday Usergrid!

-
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] Release Apache Stratos 3.0.0 Incubating RC4

[Chris Mattmann]

+1 from me (binding):

SIGS/checksums pass:

[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% stage_apache_rc
apache-stratos 3.0.0-incubating-source-release
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100 5889k  100 5889k0 0   685k  0  0:00:08  0:00:08 --:--:--
990k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   836  100   8360 0745  0  0:00:01  0:00:01 --:--:--
780
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10085  100850 0 76  0  0:00:01  0:00:01 --:--:--
 80
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10093  100930 0 81  0  0:00:01  0:00:01 --:--:--
 85
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% curl -O
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c1/KEYS
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  9531  100  95310 0   8822  0  0:00:01  0:00:01 --:--:--
9244
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% gpg --import  KEYS
gpg: key 06569264: public key Lahiru (lahiru-wso2-key)
lahi...@wso2.com imported
gpg: key DC627E6F: public key Deependra Ariyadewa (Free as in Freedom)
deepen...@gmail.com imported
gpg: key 44BBC719: public key Lahiru Sandaruwan (Opensource GPG key)
lahi...@apache.org imported
gpg: Total number processed: 3
gpg:   imported: 3  (RSA: 2)
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   3  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: next trustdb check due at 2015-08-18
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% stage_apache_rc
apache-stratos agent-3.0.0-incubating
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100 83.8M  100 83.8M0 0   772k  0  0:01:51  0:01:51 --:--:--
725k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   836  100   8360 0773  0  0:00:01  0:00:01 --:--:--
810
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10076  100760 0 68  0  0:00:01  0:00:01 --:--:--
 71
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10084  100840 0 74  0  0:00:01  0:00:01 --:--:--
 78
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% stage_apache_rc
apache-stratos cc-3.0.0-incubating
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  135M  100  135M0 0   745k  0  0:03:05  0:03:05 --:--:--
1144k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   836  100   8360 0757  0  0:00:01  0:00:01 --:--:--
793
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10073  100730 0 67  0  0:00:01  0:00:01 --:--:--
 70
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10081  100810 0 73  0  0:00:01  0:00:01 --:--:--
 76
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% stage_apache_rc
apache-stratos cli-3.0.0-incubating
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
 15 12.6M   15 2064k0 0  46923  0  0:04:43  0:00:45  0:03:58
  0^C
[terra:~/tmp/apache-stratos-3.0.0-RC4] mattmann% stage_apache_rc
apache-stratos cli-3.0.0-incubating
https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-r
c4/
  % Total% Received % Xferd 

Re: Cultivating Outstanding IP Stewards

[Chris Mattmann]

Hey Guys,

I agree with Ted below -- and also what I've seen you do Marvin
as well -- let's nominate folks to the IPMC and get them binding
VOTEs and get them rewarded as much as possible.

Cheers,
Chris




-Original Message-
From: Ted Dunning ted.dunn...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Thursday, November 7, 2013 12:20 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Cultivating Outstanding IP Stewards

On Thu, Nov 7, 2013 at 11:13 AM, Marvin Humphrey
mar...@rectangular.comwrote:

 The Incubator has a fundamental structural flaw: it lacks a mechanism to
 reward merit earned by individual podling contributors.  Instead, we
teach
 people to hate the Incubator by placing their projects at the mercy of
 Mentors.  Our Mentors care, but they don't care enough.  They don't care
 like
 core developers care.


Nominate these meritorious contributors as IPMC members.



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

Re: Cultivating Outstanding IP Stewards

[Chris Mattmann]

-Original Message-

From: Jim Jagielski j...@jagunet.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Thursday, November 7, 2013 12:31 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Cultivating Outstanding IP Stewards


On Nov 7, 2013, at 2:13 PM, Marvin Humphrey mar...@rectangular.com
wrote:

 
 The Incubator has a fundamental structural flaw: it lacks a mechanism to
 reward merit earned by individual podling contributors.

Idea: Allow for podlings to nominate, and elect, Podling chairs
which can cast Mentor-like votes.

+1 to me this is the Champion role, and ultimately gets us closer to my
proposal that podlings are just (*)TLPs as well :) Eventually over time
people will realize that it's a faux asterisk, IMO.

Cheers,
Chris



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

Re: Cultivating Outstanding IP Stewards

[Chris Mattmann]

Oooh, OK Jim, gotcha I didn't understand the first time.


-Original Message-
From: Jim Jagielski j...@jagunet.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Thursday, November 7, 2013 12:49 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Cultivating Outstanding IP Stewards


On Nov 7, 2013, at 1:37 PM, Chris Mattmann mattm...@apache.org wrote:

 -Original Message-
 
 From: Jim Jagielski j...@jagunet.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Thursday, November 7, 2013 12:31 PM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: Cultivating Outstanding IP Stewards
 
 
 On Nov 7, 2013, at 2:13 PM, Marvin Humphrey mar...@rectangular.com
 wrote:
 
 
 The Incubator has a fundamental structural flaw: it lacks a mechanism
to
 reward merit earned by individual podling contributors.
 
 Idea: Allow for podlings to nominate, and elect, Podling chairs
 which can cast Mentor-like votes.
 
 +1 to me this is the Champion role

No, I mean someone from the PPMC. For example, in the Allura
case, the podling could nominate and elect Dave as podling
chair and he would have Mentor powers.


-
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] Accept Log4cxx for Incubation

[Chris Mattmann]

+1 from me (binding). Good luck dudes!

Cheers,
Chris



-Original Message-
From: Christian Grobmeier grobme...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Wednesday, December 4, 2013 11:48 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: [VOTE] Accept Log4cxx for Incubation

Dear all,

please cast your vote to accept Log4cxx for incation.
The proposal is pasted below, but can be found here too:
https://wiki.apache.org/incubator/Log4cxxProposal

This vote will close in 72 hours.

[ ] +1 Accept Log4cxx into the Incubator
[ ] -1 Don't accept Log4cxx because...

Thanks,

Christian




Log4cxx

Proposal

Apache log4cxx is a subproject of Apache Logging Services. It is a
logging framework for C++ patterned after Apache log4j. Apache log4cxx
uses Apache Portable Runtime for most platform-specific code and should
be usable on any platform supported by APR.

The current website is visible at: http://logging.apache.org/log4cxx/

The original developers of the project went inactive and the project was
not maintained for quite a while. The Logging PMC thought about moving
the project to the attic but a few users were objecting.

This proposal is to create a new community around Log4cxx.

Rationale

Currently Log4cxx appears to be pretty stable without many competitors.
It has a small but dedicated user base.

Current Status

Meritocracy

Log4cxx was developed at the Apache Software Foundation. Its SVN history
reaches back to 2003 but there was even previous development on CVS.
While the interested developers were not involved in the past efforts
there is consens that Apache Logging Services is the best place for the
future development of Log4cxx.

Alignment

Goal of the incubation is to reboot the community around log4cxx.

Known Risks

Orphaned Products

With six interested developers and one of them being a committer to
Apache Logging Services the risk can be considered low.

Inexperience with Open Source

One of the committers is already committer to Apache Logging. The others
were already subscribed to the mailing list and actively participating
on the discussions.

Homogeneous Developers

The list of initial committers are geographically distributed across the
world with no one company being associated with a majority of the
developers.

Reliance on Salaried Developers

None of the initial committers is paid to develop code for this project.
However it has been expressed that the framework is in use at the
companies of the developers. CCLAs will be submitted were relevant.

Relationships with Other Apache Products

So far no other Apache products are known which use Log4cxx. Apache
Log4j was the prototype for creating Log4cxx.

An Excessive Fascination with the Apache Brand

n/a. Log4cxx was developed at the ASF.

Initial Source

The initial source was developed at the ASF and has already a clean IP
and is distributed with AL 2.0.

Source and Intellectual Property Submission Plan

The source code is available here:
https://svn.apache.org/repos/asf/logging/log4cxx

External Dependencies

None.

Cryptography

The project does not handle cryptography in any way.

Required Resources

We would like to use the already existing mailinglists:
http://logging.apache.org/log4cxx/mail-lists.html

We would like to move the source code folder from:
https://svn.apache.org/repos/asf/logging/log4cxx

to: https://svn.apache.org/repos/asf/incubator/log4cxx

Issue tracking: We would like to use:
https://issues.apache.org/jira/browse/LOGCXX which already exists.

We would like to move the current website to:
http://incubator.apache.org/log4cxx/ As the main Logging site is created
with the Apache CMS, we would like to establish a similar process for
log4cxx.

Initial Committers

Names of initial committers - in alphabetical order - with current ASF
status:

Florian Seydoux florianseyd...@gmail.com (ICLA signed)
chand priyankara ch...@engineering.com (ICLA signed)
Nick Williams nickwilli...@apache.org (Apache Logging Committer)
Thorsten Schöning tschoen...@am-soft.de
Rhys Ulerich rhys.uler...@gmail.com (ICLA signed)
Joseph Southwell jos...@southwell.org (ICLA signed)
Alexandru Zbârcea zbarce...@gmail.com (ICLA signed)
Sponsors

Champion

Christian Grobmeier grobmeier at apache dot org (Member)
Nominated Mentors

Christian Grobmeier grobmeier at apache dot org
Scott Deboy sdeboy at apache dot org
Sponsoring Entity

Apache Logging PMC


-
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] Release Apache Spark 0.8.0-incubating (rc4)

[Chris Mattmann]

Hi Patrick,

In fact, Sonatype will let you publish non o.a.xx dependencies since
they are an approved forge as well for Central sync. So you can sign
up for an account there, but it's always good to get the buy in of the
specific community of the upstream dependency so they are aware.

These types of things though can be addressed over time and as each
release improves. 

Cheers,
Chris




-Original Message-
From: Patrick Wendell pwend...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Saturday, December 14, 2013 10:39 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [VOTE] Release Apache Spark 0.8.0-incubating (rc4)

Thanks Marvin and Joe,

Do you know which other projects/people we might reach out to for
institutional knowledge of how this is done?

Our specific issue is that while 99% of our dependencies are in maven,
there are a small # of dependencies that don't publish anywhere via
maven. One solution would be if apache let us publish these to maven
central - but I'm guessing Apache limits us to publishing o.i.a.XXX
artifacts.

- Patrick

On Sat, Dec 14, 2013 at 10:31 PM, Marvin Humphrey
mar...@rectangular.com wrote:
 On Sat, Dec 14, 2013 at 9:24 PM, Patrick Wendell pwend...@gmail.com
wrote:
 We are planning to do our next major release (Spark 0.9.0) while still
 under incubation in the next few weeks. Could I propose that we create
 a parallel discussion about how we might re-tool or build process with
 the aim towards satisfying whatever policy exists in that release?

 +1

 That seems reasonable to me.

 We're winging it a bit, since discussions about under what
circumstances to
 relax policy are ongoing (see the IP Clearance before releasing
thread).
 However, you've taken the initiative to make a constructive proposal.
We
 should work with you.

 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




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

Re: [VOTE] Release Apache Spark 0.8.0-incubating (rc4)

[Chris Mattmann]

Hi Guys,

+1 from me (binding):

SIGS pass, CHECKSUMS pass:

[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/stage_apache_rc spark 0.8.1-incubating-bin-hadoop1
http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  131M  100  131M0 0  1754k  0  0:01:16  0:01:16 --:--:--
1165k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   490  100   4900 0   6965  0 --:--:-- --:--:-- --:--:--
13611
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   129  100   1290 0   1839  0 --:--:-- --:--:-- --:--:--
3583
[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/stage_apache_rc spark 0.8.1-incubating-bin-hadoop2
http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  215M  100  215M0 0  1815k  0  0:02:01  0:02:01 --:--:--
1826k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   490  100   4900 0   6831  0 --:--:-- --:--:-- --:--:--
13611
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   129  100   1290 0   1819  0 --:--:-- --:--:-- --:--:--
3583
[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/stage_apache_rc spark 0.8.1-incubating-bin-cdh
http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/
[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/stage_apache_rc spark 0.8.1-incubating-bin-cdh4
http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  136M  100  136M0 0  1757k  0  0:01:19  0:01:19 --:--:--
1502k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   490  100   4900 0   6892  0 --:--:-- --:--:-- --:--:--
13611
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   123  100   1230 0   1702  0 --:--:-- --:--:-- --:--:--
3514
[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/stage_apache_rc spark 0.8.1-incubating
http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100 4565k  100 4565k0 0  1636k  0  0:00:02  0:00:02 --:--:--
1656k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   490  100   4900 0   6949  0 --:--:-- --:--:-- --:--:--
13611
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10077  100770 0   1109  0 --:--:-- --:--:-- --:--:--
2200
[chipotle:~/tmp/apache-spark-0.8.1-incubating-rc4] mattmann%
$HOME/bin/verify_gpg_sigs
Verifying Signature for file spark-0.8.1-incubating-bin-cdh4.tgz.asc
gpg: Signature made Tue Dec 10 15:03:24 2013 PST using RSA key ID 9E4FE3AF
gpg: Good signature from Patrick Wendell pwend...@gmail.com
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 5AA9 0E72 812F F246 7904  277D 548F 5FEE 9E4F E3AF
Verifying Signature for file spark-0.8.1-incubating-bin-hadoop1.tgz.asc
gpg: Signature made Tue Dec 10 14:58:15 2013 PST using RSA key ID 9E4FE3AF
gpg: Good signature from Patrick Wendell pwend...@gmail.com
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 5AA9 0E72 812F F246 7904  277D 548F 5FEE 9E4F E3AF
Verifying Signature for file spark-0.8.1-incubating-bin-hadoop2.tgz.asc
gpg: Signature made Tue Dec 10 15:09:16 2013 PST using RSA key ID 9E4FE3AF
gpg: Good signature from Patrick Wendell pwend...@gmail.com
gpg: WARNING: This key is not certified with a trusted signature!
gpg: 

[VOTE] Graduation of Apache Open Climate Workbench from the Incubator

[Chris Mattmann]

Hi Folks,

The Apache Open Climate Workbench community has VOTEd to graduate
from the Apache Incubator.

I'm now calling an official IPMC VOTE to make this happen as well.
Here's the community tally:

+1
--
Chris Mattmann*
Michael Joyce
Denis Nadeau
Cameron Goodale
Paul Ramirez*
Chris Douglas*
Andrew Hart*

+0
-

-1
-


* - indicates IPMC member

We've made 3 releases of the software, have added new committers and
PPMC members and in general done great work to build this community
in the Apache way. 

Please VOTE to graduate Apache Open Climate Workbench from the Incubator.
I'll leave the VOTE open for the next week and tally the results after
then.
The graduation resolution is pasted below.

Thanks!

Cheers,
Chris


---snip
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 preparation, evaluation and analysis of massive
climate remote sensing and model output data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Open Climate Workbench
Project, be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further

RESOLVED, that the Apache Open Climate Workbench Project be and hereby
is
responsible for the creation and maintenance of software
related to preparation, evaluation and analysis of massive
climate remote sensing and model output data; and be it further

RESOLVED, that the office of Vice President, Apache Open Climate
Workbench, be
and hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Apache Open Climate Workbench Project, and to have primary
responsibility for
management of the projects within the scope of responsibility
of the Apache Open Climate Workbench Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Open Climate Workbench Project:

* Andrew Hart ah...@apache.org
* Maziyar Boustani boust...@apache.org
* Christopher Douglas cdoug...@apache.org
* Chris Jack cj...@apache.org
* Dan Crichton crich...@apache.org
* Denis Nadeau nad...@apache.org
* estani est...@apache.org
* Cameron Goodale good...@apache.org
* Alex Goodman good...@apache.org
* Huikyo Lee huiky...@apache.org
* Jason Peter Evans jasonev...@apache.org
* Jinwon Kim j...@apache.org
* Michael James Joyce jo...@apache.org
* Laura Carriere lcarri...@apache.org
* Lluis Fita Borrell lfitaborr...@apache.org
* Luca Cinquini ll...@apache.org
* Chris Mattmann mattm...@apache.org
* Nick Kew n...@apache.org
* Paul Loikith ploik...@apache.org
* Paul Michael Ramirez prami...@apache.org
* Paul Zimdars pzimd...@apache.org
* M. V. S. Rama Rao rama...@apache.org
* J Sansay san...@apache.org
* Shakeh Khudikyan skhud...@apache.org
* Suresh Marru sma...@apache.org
* Duane Waliser wali...@apache.org
* Kim Whitehall whiteh...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Michael Joyce be
   appointed to the office of Vice President, Apache Open Climate
Workbench,
to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification, or
   until a successor is appointed; and be it further

   RESOLVED, that the Apache Open Climate Workbench Project be and hereby
is
   tasked with the migration and rationalization of the Apache
   Incubator Open Climate Workbench podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Open Climate Workbench podling encumbered upon the Apache
Incubator
   Project are hereafter discharged.


---snip




-Original Message-
From: Michael Joyce jo...@apache.org
Reply-To: d...@climate.incubator.apache.org
d...@climate.incubator.apache.org
Date: Wednesday, January 15, 2014 9:41 AM
To: dev d...@climate.incubator.apache.org
Subject: Re: [VOTE] Graduation of Apache Open Climate Workbench from the
Incubator

Hay everyone,

Just a quick follow up to provide a summary of the vote.

+1
--
Chris Mattmann
Michael Joyce
Denis Nadeau
Cameron Goodale
Paul Ramirez
Chris Douglas
Andrew Hart

+0
-

-1
-

Unfortunately, I don't think everything will get done in time for todays
board meeting. However we have plenty of time to get everything taken care
of for February!

Thanks everyone!


-- Joyce


On Sun, Jan 12, 2014 at 10:05 AM, Andrew Hart ah...@apache.org wrote:

 +1,

 Andrew.


 On 12/16/13 9:14 AM, Chris Mattmann wrote:

 Hi Folks,


 OK, DISCUSS thread here: http://s.apache.org/22I

 Here's a draft resolution to VOTE on:

 ---snip
 WHEREAS, the Board

[RESULT] [VOTE] Graduation of Apache Open Climate Workbench from the Incubator

[Chris Mattmann]

Hi Folks,

This VOTE has passed with the following tallies:


+1
--
Chris Mattmann*
Michael Joyce
Denis Nadeau
Cameron Goodale
Paul Ramirez*
Chris Douglas*
Andrew Hart*
Henry Saputra*
Suresh Marru*

+0
-

-1
-


* - indicates IPMC member

I will go ahead and paste the board resolution into the board agenda.
Thanks to everyone for VOTE'ing!

Cheers,
Chris


-Original Message-
From: Chris Mattmann mattm...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Wednesday, January 15, 2014 9:46 AM
To: general@incubator.apache.org general@incubator.apache.org
Cc: d...@climate.incubator.apache.org d...@climate.incubator.apache.org
Subject: [VOTE] Graduation of Apache Open Climate Workbench from the
Incubator

Hi Folks,

The Apache Open Climate Workbench community has VOTEd to graduate
from the Apache Incubator.

I'm now calling an official IPMC VOTE to make this happen as well.
Here's the community tally:

+1
--
Chris Mattmann*
Michael Joyce
Denis Nadeau
Cameron Goodale
Paul Ramirez*
Chris Douglas*
Andrew Hart*

+0
-

-1
-


* - indicates IPMC member

We've made 3 releases of the software, have added new committers and
PPMC members and in general done great work to build this community
in the Apache way.

Please VOTE to graduate Apache Open Climate Workbench from the Incubator.
I'll leave the VOTE open for the next week and tally the results after
then.
The graduation resolution is pasted below.

Thanks!

Cheers,
Chris


---snip
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 preparation, evaluation and analysis of massive
climate remote sensing and model output data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Open Climate Workbench
Project, be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further

RESOLVED, that the Apache Open Climate Workbench Project be and hereby
is
responsible for the creation and maintenance of software
related to preparation, evaluation and analysis of massive
climate remote sensing and model output data; and be it further

RESOLVED, that the office of Vice President, Apache Open Climate
Workbench, be
and hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Apache Open Climate Workbench Project, and to have primary
responsibility for
management of the projects within the scope of responsibility
of the Apache Open Climate Workbench Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Open Climate Workbench Project:

* Andrew Hart ah...@apache.org
* Maziyar Boustani boust...@apache.org
* Christopher Douglas cdoug...@apache.org
* Chris Jack cj...@apache.org
* Dan Crichton crich...@apache.org
* Denis Nadeau nad...@apache.org
* estani est...@apache.org
* Cameron Goodale good...@apache.org
* Alex Goodman good...@apache.org
* Huikyo Lee huiky...@apache.org
* Jason Peter Evans jasonev...@apache.org
* Jinwon Kim j...@apache.org
* Michael James Joyce jo...@apache.org
* Laura Carriere lcarri...@apache.org
* Lluis Fita Borrell lfitaborr...@apache.org
* Luca Cinquini ll...@apache.org
* Chris Mattmann mattm...@apache.org
* Nick Kew n...@apache.org
* Paul Loikith ploik...@apache.org
* Paul Michael Ramirez prami...@apache.org
* Paul Zimdars pzimd...@apache.org
* M. V. S. Rama Rao rama...@apache.org
* J Sansay san...@apache.org
* Shakeh Khudikyan skhud...@apache.org
* Suresh Marru sma...@apache.org
* Duane Waliser wali...@apache.org
* Kim Whitehall whiteh...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Michael Joyce be
   appointed to the office of Vice President, Apache Open Climate
Workbench,
to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification, or
   until a successor is appointed; and be it further

   RESOLVED, that the Apache Open Climate Workbench Project be and hereby
is
   tasked with the migration and rationalization of the Apache
   Incubator Open Climate Workbench podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Open Climate Workbench podling encumbered upon the Apache
Incubator
   Project are hereafter discharged.


---snip




-Original Message-
From: Michael Joyce jo...@apache.org
Reply-To: d...@climate.incubator.apache.org
d...@climate.incubator.apache.org
Date: Wednesday, January 15, 2014 9:41 AM
To: dev d

Re: [VOTE] Graduation of Apache Spark from the Incubator

[Chris Mattmann]

Hi Bertrand, and Craig,

Thanks for the catch. Matei is working the updated PMC members.

I just wanted to address the point about commitment to the project.
Spark was a UCB AMP Lab project that operated very much like an Apache
project (which is why I was able to convince them that the ASF was a
great fit). As far as demonstrating commitment to the project, these
folks that were part of the original proposal *did* demonstrate their
commitment to the project -- just as we ask podlings to absorb our
ASF mentality that merit doesn't expire that same thing is true upstream
of the project communities that come into the ASF, so long as the ASF
Spark community members agree (which they overwhelmingly did through
at least one round of VOTE'ing so far).

From my mentor perspective, I wouldn't go around suggesting who's
demonstrated commitment to the project and who hasn't - that's really
something that the PPMC can speak to and the mentors of the project.

We're also proactively working this (Matei responded uber quickly and
is handling stuff like a VP which is awesome!) so it should be resolved
shortly. Thanks for your patience.

Cheers,
Chris



-Original Message-
From: Bertrand Delacretaz bdelacre...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Wednesday, February 5, 2014 1:34 AM
To: Incubator General general@incubator.apache.org
Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator

On Tue, Feb 4, 2014 at 5:12 PM, Craig L Russell
craig.russ...@oracle.com wrote:
 ...Some of the proposed PMC members have filed ICLAs but are not
committers; some have not
 even filed ICLAs; some appear to have been part of the original
proposal but have not contributed
 to the project during incubation...

Ouch...thanks for catching that, Craig.

Here's my -1 as well, we'll need to see an updated list of PMC members
consisting of people who have demonstrated their commitment to the
project.

-Bertrand

-
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] Graduation of Apache Spark from the Incubator

[Chris Mattmann]

Jake, yep thanks for suggesting moving this to another thread :)

In a few days I plan on tallying the VOTEs from the Spark VOTE thread
which at current count is overwhelmingly passing.

I'll keep it open through at least Monday and then in time to add
it to the agenda for the Feb 2014 meeting of the board for consideration
should the current count and trend continue to hold.

Thanks to everyone for their thoughtful discussion. Clearly this is a
great use case and discussion point for lots of improvement in the ASF,
the Incubator, in my own mentorship and others, and in how we can
serve our communities best at the ASF.

Cheers all.

Chris





-Original Message-
From: Jake Farrell jfarr...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org,
jfarr...@apache.org jfarr...@apache.org
Date: Thursday, February 6, 2014 10:58 AM
To: Matei Zaharia matei.zaha...@gmail.com
Cc: general@incubator.apache.org general@incubator.apache.org,
jfarr...@apache.org jfarr...@apache.org
Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator

Matei
multiple TLPs using it as their main reviewing system? Outside of JClouds
I
am unaware of any others using it currently.

I think this is a good discussion to have, but we should start another
thread with it so as to not hijack the Apache Spark graduation thread with
it.

-Jake


On Thu, Feb 6, 2014 at 1:43 PM, Matei Zaharia
matei.zaha...@gmail.comwrote:

 I like the idea of sending these to the dev list. I'm going to open an
 INFRA ticket for it.

 While it seems that the current web hook only sends events when a pull
 request is opened or closed, GitHub *can* email watchers for comments as
 well. I'm watching the project on GitHub and I get an email for every
 comment, even on pull requests I never looked at. So maybe we can
 investigate adding this to the GitHub hook -- I'm sure it's not a big
burden
 from their side.

 The other option would be to somehow subscribe dev@ through the standard
 GitHub watcher framework by making it the notification address for some
 account watching the repo, but this requires confirming the address and
I
 think anyone on dev might be able to unsubscribe it or take ownership of
 that account if we do so. Maybe GitHub can help us do this without going
 through the confirm address process. Did you guys have a contact over
 there helping with the mirroring, or was it all done through their API?
I
 imagine it's in their interest to make GitHub work with the ASF process
 because there are now multiple TLPs using it as their main reviewing
system.

 Matei

 On Feb 6, 2014, at 10:13 AM, Jake Farrell jfarr...@apache.org wrote:

  Once the mirror is setup and synced to github (24hr window for this
  potentially to occur) then one of the Github Apache org admins can
setup
  the webhook. The project just needs to put in an infra ticket asking
for
 it
 
  -Jake
 
 
 
  On Thu, Feb 6, 2014 at 1:06 PM, Henry Saputra henry.sapu...@gmail.com
 wrote:
 
  HI Marvin,
 
  The automatic email to dev@ list for github mirror PR, does it happen
  for all ASF github mirrors or each podling need to do some setup to
  make it work?
 
 
  - Henry
 
  On Thu, Feb 6, 2014 at 9:53 AM, Marvin Humphrey
mar...@rectangular.com
 
  wrote:
  On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce jo...@apache.org
 wrote:
  How is doing a review on Github any different than doing a review
on
  Review
  Board?
 
  One is captured to Apache controlled channels and the other is not.
 
  If there's concern that work on Github isn't being adequately
mirrored
  on
  the mailing lists then that sounds like an Infra problem to me.
 
  It's not an Infra problem.  It's the problem of any PMC which fails
to
  ensure
  that all of its communications are properly archived.
 
  If anyone here is interested in contributing towards this feature, I
  encourage
  you to subscribe to the infrastructure-dev@apache list.  I also
  encourage
  everyone to ponder carefully:
 
  *   How to ensure that no information is lost when capturing
  communications
 in GitHub channels through notifications to our dev lists.
  *   The impact of adding GitHub integration features on long-term
ASF
  Infra
 labor costs.
 
  There are plenty of hooks [1] that makes this easy to do and, if
I'm
 not
  mistaken, pull requests through Github are already supposed to mail
 dev@
  .
 
  That's right.  I've actually worked on the specific hook that does
  that[1][2].
 
  I would assume that any comment on them should as well.
 
  Why would you assume that GitHub comments are being mailed to dev
  lists?
  They are not.
 
  Every Apache PMC member is tasked with oversight of their project,
and
  that
  includes ensuring that all decisions happen on the dev list and are
  properly
  documented.  It is not enough to assume that Infra is taking care
of
  archival -- ensuring that the archival actually happens is the PMC's
  direct
  responsibility.
 
  Marvin Humphrey
 
  [1] 

[VOTE] Graduation of Apache Knox from the Incubator

[Chris Mattmann]

Hi Everyone,

The Apache Knox Incubating podling has VOTEd to graduate from the
Incubator.
The community VOTE has passed below with the provided tallies. The
graduation
resolution draft is pasted below. We welcome your VOTE'ing on Knox's
graduation
from the Incubator.

I will leave this VOTE open for at least 72 hours.

[ ] +1 Recommend graduation of Apache Knox from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't recommend graduation of Apache Knox from the Incubator
because..

Thanks for your VOTE!

Cheers,
Chris



-Original Message-
From: Chris Mattmann mattm...@apache.org
Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Date: Thursday, February 6, 2014 8:38 PM
To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator

Hi Guys,


Sorry it took forever for me to close this VOTE! :)

Here are the tallies:

+1

Chris Mattmann*
Alan Gates*
Larry McCay
Dilli Arumugam
Kevin Minder

* - indicates IPMC

This VOTE has passed. I'll now take it to general@incubator.apache.org.

Thanks for VOTE'ing!

Cheers,
Chris

-Original Message-
From: Chris Mattmann mattm...@apache.org
Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Date: Thursday, December 19, 2013 2:41 PM
To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Subject: [VOTE] Graduation of Apache Knox from the Incubator

Hi Folks,


Time to VOTE on the following resolution to graduate
Apache Knox from the Apache Incubator. Here's a draft
resolution to VOTE on (with Kevin listed as PMC chair).

I'll leave the VOTE open for the next week. If all goes
well here, I'll take it to general@incubator.a.o and if
all goes well there, we'll take it to the Apache board
for consideration in their January 2014 board meeting.

Thanks!

[ ] +1 Graduate Apache Knox from the Incubator
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Knox from the Incubator because..

Thanks and here's my enthusiastic +1!

Cheers,
Chris

--draft resolution

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 secure access for Apache Hadoop clusters.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Knox Project be
  and hereby is established pursuant to Bylaws of the Foundation;
  and be it further

  RESOLVED, that the Apache Knox Project be and hereby is
  responsible for the creation and maintenance of software
  related to secure access for Apache Hadoop clusters; and be it further

  RESOLVED, that the office of Vice President, Apache Knox, be
  and hereby is created, the person holding such office to serve
  at the direction of the Board of Directors as the chair of the
  Apache Knox Project, and to have primary responsibility for
management of the projects within the scope of responsibility
  of the Apache Knox Project; and be it further

  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Knox Project:

* Christopher Douglas cdoug...@apache.org
* Chris Mattmann mattm...@apache.org
* Devaraj Das d...@apache.org
* Dilli Dorai dillido...@apache.org
* Alan Gates ga...@apache.org
* John Speidelkminder jspei...@apache.org
* Kevin Minder kmin...@apache.org
* Larry McCay lmc...@apache.org
* Mahadev Konar maha...@apache.org
* Owen O'Malley omal...@apache.org
* Sumit Mohanty smoha...@apache.org
* Tom Beerbower tbeerbo...@apache.org
* Thomas White tomwh...@apache.org
* Venkatesh Seetharam venkat...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kevin Minder be
 appointed to the office of Vice President, Apache Knox,
to serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification, or
 until a successor is appointed; and be it further

 RESOLVED, that the Apache Knox Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Knox podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Knox podling encumbered upon the Apache
Incubator Project are hereafter discharged.










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

[DISCUSS] [VOTE] Graduation of Apache Spark from the Incubator (was Re: [VOTE] Graduation of Apache Spark from the Incubator)

[Chris Mattmann]

Hi Bertrand,

(changing this to DISCUSS thread to avoid continuing hijacking
the VOTE thread)

Of Spark's IPMC direct mentorship, 5 of the 7 mentors
have all VOTEd for its graduation:

Chris Mattmann
Andrew Hart
Henry Saputra

Roman Shaposhnik
Suresh Marru

Still waiting on +1s from:

Paul Ramirez
Thomas Dudziak

That's 71% of Spark's IPMC mentors have already VOTEd +1
for this project to graduate.

Note also the 12 +1s from other members of the IPMC.

Sebastian Schelter 

Jean-Baptiste Onofré
Ted Dunning
Patrick Hunt
Chris Douglas
Alan Cabrera
Jake Ferrell
Leif Hedstrom 
Sergio Fernández 
Sebastian Schelter 
Marvin Humphrey
Alex Karasulu 

Further note that there are over 34 community +1s for this project.

Of the 3 IPMC -1s:

Bertrand Delacretaz
Craig Russell
sebb

Bertrand, you originally VOTEd +1 until Craig mentioned his concerns
about accounts not having been filed. Matei and others immediately
stepped up (including myself), and explained the situation, and
filed the accounts. Sebb's concerns were originally related to the
resolution and mix of Apache ids/other mail Ids, etc.

If you are suggesting in some thinly veiled way that the
board is going to reject both the overwhelming majority of the
direct paying attention mentors to the project; along with majority
of other members of the IPMC; along with the members of the community who
also 
recommended its graduation, because a minority of IPMC members
and others identified issues with people having their accounts,
or some others with the use of Git, and/or accusations of not
all conversation making it to the list, considering all of the
positive things that goes on in Spark, or the 100s of messages
PER day that make it to the list, along with conversation and
great work and Apache mentality that's being demonstrated by
their developers, then I'm disappointed and frankly, I disagree
and let's put it to a VOTE at the board level. I'll be there,
ready and willing to discuss this with real data and not innuendo,
along with the real history of watching the awesomeness of this project
and all of the things they have gotten right about the Apache
community.

Cheers,
Chris


-Original Message-
From: Bertrand Delacretaz bdelacre...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, February 7, 2014 5:12 AM
To: Incubator General general@incubator.apache.org
Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator

On Fri, Feb 7, 2014 at 4:05 AM, David Nalley da...@gnsa.us wrote:
 ...The part that disturbs me is that after the vote passed in the
 community, and came to the IPMC a mentor is still having to remind
 folks that things like strategy and roadmap discussions need to happen
 on the mailing list...

Yes - considering the worrying aspects that this thread brought to the
surface, I would recommend that the Spark mentors take another look
and make a solid case to demonstrate that the project is actually
ready to graduate.

Remember that the Incubator PMC's vote is only about *recommending*
that the board accepts the incoming project, if there's no strong
consensus I'd assume that the board is likely to reject the resolution
until that strong consensus for graduation is established here.

-Bertrand

-
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: [DISCUSS] [VOTE] Graduation of Apache Spark from the Incubator (was Re: [VOTE] Graduation of Apache Spark from the Incubator)

[Chris Mattmann]

Thanks Bertrand, for your feedback and as I have mentioned, we filed
the account requests, and have explained from the community perspective
the issues at hand (Matei has done so grandly in the last day and
don't have time now to look up the exact thread pointer but look
for some replies by Matei over the past day or so). Furthermore,
there have been some great recent replies from IPMC members as of
last night that summarize my overall feeling with the podling as
well.

BTW, your comment below about very wrong list of PMC members, I
take exception to and disagree with. It wasn't a wrong list -- it's
that some people in that list had not completed the due diligence
to obtain their Apache accounts (though in all cases but 1, for
Kay, ICLAs had been filed and that has now been remedied). This is
no fault of the members of that PPMC -- it was an oversight on my
part and the other mentors part; I take full responsibility for
that. However, I will make it very clear that the issue
was caught, and now it's been dealt with and is in the process of
being dealt with. Once the account requests I filed are complete,
all of those members on that list will have Apache accounts, but
more importantly ICLAs on file.

Trusting the mentors too much isn't a bad thing by the way. I myself
have done this. You have to be able to mix precision with recall
in these situations and you have to have people like Craig and/or
sebb that can catch things -- very valuable tools to catch even
when mentors like myself miss some of the details. You know, being
a Director; a Treasurer; combined with all the list of other things
I do? ;)

Regardless, like I said, the issues are being dealt with -- the
facts have been stated by me below with pure numbers and data that
again show an overwhelming majority of IPMC mentors for Spark; of
IPMC members who VOTED in the graduation VOTE; along with community
members have VOTEd to graduate this project, and to recommend its
graduation to the board.  I am going to still leave this VOTE open
until Monday in the hopes that seeing the diligence performed by
the Spark community in the face of these discussions and the very
real need to address the raised issues are precisely the spirit of
the Apache way and the communities that we grow here and that those
acts change the mind of the minority who issued their -1s.

Beyond that, I am not going to leave the VOTE open indefinitely,
and I am not going to concern myself with what-ifs at the board
level. The facts are here. The discussion is here. Neither change
the very real fact that Spark deserves TLP status, and I wholeheartedly
recommend its graduation to the board; as do the other IPMC members;
community members, and others cited in the data I gathered below.

Cheers, 
Chris



-Original Message-
From: Bertrand Delacretaz bdelacre...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, February 7, 2014 7:35 AM
To: Incubator General general@incubator.apache.org
Subject: Re: [DISCUSS] [VOTE] Graduation of Apache Spark from the
Incubator (was Re: [VOTE] Graduation of Apache Spark from the Incubator)

Hi Chris,

On Fri, Feb 7, 2014 at 4:20 PM, Chris Mattmann mattm...@apache.org
wrote:
... Bertrand, you originally VOTEd +1 until Craig mentioned his concerns
 about accounts not having been filed. Matei and others immediately
 stepped up (including myself), and explained the situation, and
 filed the accounts. Sebb's concerns were originally related to the
 resolution and mix of Apache ids/other mail Ids, etc

Fact is, the mentors let the resolution go through with a very wrong
list of PMC members. Which I didn't spot either at first...trusting
the mentors too much maybe? ;-)

And the discussions in the vote thread show some worrying
uncertainties about the project's readyness to graduate. I have not
analyzed everything in detail so far, maybe everything's clear if one
rereads the full thread. But the perception is here.

 ...If you are suggesting in some thinly veiled way that the
 board is going to reject both the overwhelming majority of the
 direct paying attention mentors to the project; along with majority
 of other members of the IPMC; along with the members of the community
who
 also
 recommended its graduation...

There was nothing behind my comment that the board can reject a
graduation resolution - suggesting things in some thinly veiled way is
not my style.

It's just that a board member who hasn't followed the project or the
details of this discussion, but knows that the vote thread here raised
lots of questions, might very well recommend to reject the resolution
until everything's clear.

So, my recommendation is that mentors identify and address the
concerns raised in the vote thread in a way that reassures us that the
project is indeed ready to graduate. Maybe just as some concise
comments in the vote thread once the updated the Spark resolution is
fixed.

-Bertrand

Re: [VOTE] Graduation of Apache Spark from the Incubator

[Chris Mattmann]

Thank you so much Craig and it feels good to work to gain your
support. 

Cheers and have a fantastic weekend.

Cheers,
Chris


-Original Message-
From: Craig L Russell craig.russ...@oracle.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, February 7, 2014 2:28 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator

I'm happy to see that my concerns about Spark are being actively
addressed in a professional non-confrontational manner.

The mismatch between committers and proposed PMC members has been
resolved. I guess the only missing bit is updating the graduation
resolution.

The use of git for pull request and comments is being worked on and I
have confidence in the leadership to pursue this to an agreeable solution.

I've reviewed the private list and see that it is being used
appropriately to discuss and vote new committers and PPMC members.

So I'm changing my vote to +1 subject only to the update of the proposed
PMC roster to include only committers.

Congratulations to the Spark community.

Craig

On Feb 6, 2014, at 10:01 PM, Marvin Humphrey wrote:

 On Thu, Feb 6, 2014 at 7:05 PM, David Nalley da...@gnsa.us wrote:
 
 The part that disturbs me is that after the vote passed in the
 community, and came to the IPMC a mentor is still having to remind
 folks that things like strategy and roadmap discussions need to happen
 on the mailing list. That's a pretty foundational concept in my mind
 for an Apache project.
 
 Thanks for your thoughtful, constructive commentary, David.
 
 The issue of GitHub integration is complex, unresolved, and as today's
thread
 demonstrates, controversial.  I considered voting -1 because I don't
want to
 hand a hot potato to the Board.
 
 However, as you note Spark comes highly recommended, and I am impressed
by
 what I've seen on general@incubator, especially today and in the thread
on
 dealing with binaries in their 0.8 release.  I believe that Spark is
likely to
 play a highly constructive role in realizing the promise of integrating
the
 Community over Code ASF with Social Coding GitHub.
 
 +1 (binding) to graduate.
 
 Marvin Humphrey
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!


-
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

[DISCUSS] [VOTE] Graduation of Apache Knox from the Incubator

[Chris Mattmann]

Any idea why Sebb?

This page exists:
http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/kno
x.xml


And has been updated.

As has:

http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml


Cheers,
Chris



-Original Message-
From: sebb seb...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Saturday, February 8, 2014 7:24 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [VOTE] Graduation of Apache Knox from the Incubator

The knox incubation status page website link generates a 404.

On 7 February 2014 04:49, Chris Mattmann mattm...@apache.org wrote:
 Hi Everyone,

 The Apache Knox Incubating podling has VOTEd to graduate from the
 Incubator.
 The community VOTE has passed below with the provided tallies. The
 graduation
 resolution draft is pasted below. We welcome your VOTE'ing on Knox's
 graduation
 from the Incubator.

 I will leave this VOTE open for at least 72 hours.

 [ ] +1 Recommend graduation of Apache Knox from the Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't recommend graduation of Apache Knox from the Incubator
 because..

 Thanks for your VOTE!

 Cheers,
 Chris



 -Original Message-
 From: Chris Mattmann mattm...@apache.org
 Reply-To: d...@knox.incubator.apache.org
d...@knox.incubator.apache.org
 Date: Thursday, February 6, 2014 8:38 PM
 To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
 Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator

Hi Guys,


Sorry it took forever for me to close this VOTE! :)

Here are the tallies:

+1

Chris Mattmann*
Alan Gates*
Larry McCay
Dilli Arumugam
Kevin Minder

* - indicates IPMC

This VOTE has passed. I'll now take it to general@incubator.apache.org.

Thanks for VOTE'ing!

Cheers,
Chris

-Original Message-
From: Chris Mattmann mattm...@apache.org
Reply-To: d...@knox.incubator.apache.org
d...@knox.incubator.apache.org
Date: Thursday, December 19, 2013 2:41 PM
To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Subject: [VOTE] Graduation of Apache Knox from the Incubator

Hi Folks,


Time to VOTE on the following resolution to graduate
Apache Knox from the Apache Incubator. Here's a draft
resolution to VOTE on (with Kevin listed as PMC chair).

I'll leave the VOTE open for the next week. If all goes
well here, I'll take it to general@incubator.a.o and if
all goes well there, we'll take it to the Apache board
for consideration in their January 2014 board meeting.

Thanks!

[ ] +1 Graduate Apache Knox from the Incubator
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Knox from the Incubator because..

Thanks and here's my enthusiastic +1!

Cheers,
Chris

--draft resolution

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 secure access for Apache Hadoop clusters.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Knox Project be
  and hereby is established pursuant to Bylaws of the Foundation;
  and be it further

  RESOLVED, that the Apache Knox Project be and hereby is
  responsible for the creation and maintenance of software
  related to secure access for Apache Hadoop clusters; and be it
further

  RESOLVED, that the office of Vice President, Apache Knox, be
  and hereby is created, the person holding such office to serve
  at the direction of the Board of Directors as the chair of the
  Apache Knox Project, and to have primary responsibility for
management of the projects within the scope of responsibility
  of the Apache Knox Project; and be it further

  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Knox Project:

* Christopher Douglas cdoug...@apache.org
* Chris Mattmann mattm...@apache.org
* Devaraj Das d...@apache.org
* Dilli Dorai dillido...@apache.org
* Alan Gates ga...@apache.org
* John Speidelkminder jspei...@apache.org
* Kevin Minder kmin...@apache.org
* Larry McCay lmc...@apache.org
* Mahadev Konar maha...@apache.org
* Owen O'Malley omal...@apache.org
* Sumit Mohanty smoha...@apache.org
* Tom Beerbower tbeerbo...@apache.org
* Thomas White tomwh...@apache.org
* Venkatesh Seetharam venkat...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kevin Minder be
 appointed to the office of Vice President, Apache Knox,
to serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification, or
 until a successor is appointed; and be it further

 RESOLVED, that the Apache Knox Project be and hereby is
 tasked with the migration and rationalization of the Apache

Re: [DISCUSS] [VOTE] Graduation of Apache Knox from the Incubator

[Chris Mattmann]

Fixed:

[chipotle:~/tmp/podlings-content] mattmann% svn commit -m Update knox WWW
link per sebb.
Sendingprojects/knox.xml
Transmitting file data .
Committed revision 1566209.
[chipotle:~/tmp/podlings-content] mattmann%

Should be: knox.incubator.apache.org


Cheers,
Chris



-Original Message-
From: sebb seb...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Saturday, February 8, 2014 7:43 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [DISCUSS] [VOTE] Graduation of Apache Knox from the Incubator

On 9 February 2014 03:26, Chris Mattmann mattm...@apache.org wrote:
 Any idea why Sebb?

 This page exists:
 
http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/k
no
 x.xml

This includes:

a 
href=http://incubator.apache.org/knox/;http://incubator.apache.org/knox/
/a

which does not exist


 And has been updated.

 As has:

 
http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.x
ml


 Cheers,
 Chris



 -Original Message-
 From: sebb seb...@gmail.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Saturday, February 8, 2014 7:24 PM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [VOTE] Graduation of Apache Knox from the Incubator

The knox incubation status page website link generates a 404.

On 7 February 2014 04:49, Chris Mattmann mattm...@apache.org wrote:
 Hi Everyone,

 The Apache Knox Incubating podling has VOTEd to graduate from the
 Incubator.
 The community VOTE has passed below with the provided tallies. The
 graduation
 resolution draft is pasted below. We welcome your VOTE'ing on Knox's
 graduation
 from the Incubator.

 I will leave this VOTE open for at least 72 hours.

 [ ] +1 Recommend graduation of Apache Knox from the Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't recommend graduation of Apache Knox from the Incubator
 because..

 Thanks for your VOTE!

 Cheers,
 Chris



 -Original Message-
 From: Chris Mattmann mattm...@apache.org
 Reply-To: d...@knox.incubator.apache.org
d...@knox.incubator.apache.org
 Date: Thursday, February 6, 2014 8:38 PM
 To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
 Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator

Hi Guys,


Sorry it took forever for me to close this VOTE! :)

Here are the tallies:

+1

Chris Mattmann*
Alan Gates*
Larry McCay
Dilli Arumugam
Kevin Minder

* - indicates IPMC

This VOTE has passed. I'll now take it to
general@incubator.apache.org.

Thanks for VOTE'ing!

Cheers,
Chris

-Original Message-
From: Chris Mattmann mattm...@apache.org
Reply-To: d...@knox.incubator.apache.org
d...@knox.incubator.apache.org
Date: Thursday, December 19, 2013 2:41 PM
To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org
Subject: [VOTE] Graduation of Apache Knox from the Incubator

Hi Folks,


Time to VOTE on the following resolution to graduate
Apache Knox from the Apache Incubator. Here's a draft
resolution to VOTE on (with Kevin listed as PMC chair).

I'll leave the VOTE open for the next week. If all goes
well here, I'll take it to general@incubator.a.o and if
all goes well there, we'll take it to the Apache board
for consideration in their January 2014 board meeting.

Thanks!

[ ] +1 Graduate Apache Knox from the Incubator
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Knox from the Incubator because..

Thanks and here's my enthusiastic +1!

Cheers,
Chris

--draft resolution

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 secure access for Apache Hadoop clusters.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Knox Project be
  and hereby is established pursuant to Bylaws of the Foundation;
  and be it further

  RESOLVED, that the Apache Knox Project be and hereby is
  responsible for the creation and maintenance of software
  related to secure access for Apache Hadoop clusters; and be it
further

  RESOLVED, that the office of Vice President, Apache Knox, be
  and hereby is created, the person holding such office to serve
  at the direction of the Board of Directors as the chair of the
  Apache Knox Project, and to have primary responsibility for
management of the projects within the scope of responsibility
  of the Apache Knox Project; and be it further

  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Knox Project:

* Christopher Douglas cdoug...@apache.org
* Chris Mattmann mattm...@apache.org
* Devaraj Das d...@apache.org
* Dilli Dorai dillido...@apache.org
* Alan Gates ga...@apache.org
* John Speidelkminder

[VOTE] Graduation of Apache Spark from the Incubator

[Chris Mattmann]

Hi Everyone,

This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.

Thanks!

[ ] +1 Graduate Apache Spark from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Spark from the Incubator because..

Here is my +1 binding for graduation.

Cheers,
Chris

 snip

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 fast and flexible large-scale data analysis
on clusters.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Spark Project, be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further

RESOLVED, that the Apache Spark Project be and hereby is
responsible for the creation and maintenance of software
related to fast and flexible large-scale data analysis
on clusters; and be it further RESOLVED, that the office
of Vice President, Apache Spark be and hereby is created,
the person holding such office to serve at the direction of
the Board of Directors as the chair of the Apache Spark
Project, and to have primary responsibility for management
of the projects within the scope of responsibility
of the Apache Spark Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Spark Project:

* Mosharaf Chowdhury mosha...@apache.org
* Jason Dai jason...@apache.org
* Tathagata Das t...@apache.org
* Ankur Dave ankurd...@apache.org
* Aaron Davidson a...@apache.org
* Thomas Dudziak to...@apache.org
* Robert Evans bo...@apache.org
* Thomas Graves tgra...@apache.org
* Andy Konwinski and...@apache.org
* Stephen Haberman steph...@apache.org
* Mark Hamstra markhams...@apache.org
* Shane Huang shane_hu...@apache.org
* Ryan LeCompte ryanlecom...@apache.org
* Haoyuan Li haoy...@apache.org
* Sean McNamara mcnam...@apache.org
* Mridul Muralidharam mridul...@apache.org
* Kay Ousterhout kayousterh...@apache.org
* Nick Pentreath mln...@apache.org
* Imran Rashid iras...@apache.org
* Charles Reiss wog...@apache.org
* Josh Rosen joshro...@apache.org
* Prashant Sharma prash...@apache.org
* Ram Sriharsha har...@apache.org
* Shivaram Venkataraman shiva...@apache.org
* Patrick Wendell pwend...@apache.org
* Andrew Xia xiajunl...@apache.org
* Reynold Xin r...@apache.org
* Matei Zaharia ma...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
appointed to the office of Vice President, Apache Spark, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed; and be it further

RESOLVED, that the Apache Spark Project be and hereby is
tasked with the migration and rationalization of the Apache
Incubator Spark podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Spark podling encumbered upon the Apache Incubator
Project are hereafter discharged.






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

Re: [VOTE] Release HDT version 0.0.1.incubating (RC3)

[Chris Mattmann]

+1 from me:

bash-3.2$ for type in bin src; do /Users/mattmann/bin/stage_apache_rc hdt
0.0.1.incubating-${type}
http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc3/; done
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100 8823k  100 8823k0 0   394k  0  0:00:22  0:00:22 --:--:--
233k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   836  100   8360 0   4810  0 --:--:-- --:--:-- --:--:--
9086
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10066  100660 0389  0 --:--:-- --:--:-- --:--:--
733
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10074  100740 0450  0 --:--:-- --:--:-- --:--:--
936
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  300k  100  300k0 0   170k  0  0:00:01  0:00:01 --:--:--
199k
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100   836  100   8360 0   5260  0 --:--:-- --:--:-- --:--:--
9609
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10066  100660 0356  0 --:--:-- --:--:-- --:--:--
785
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
10074  100740 0441  0 --:--:-- --:--:-- --:--:--
725
bash-3.2$ $HOME/bin/verify_gpg_sigs
Verifying Signature for file hdt-0.0.1.incubating-bin.tar.gz.asc
gpg: Signature made Sun Mar 30 21:16:42 2014 PDT using RSA key ID 5808BCF5
gpg: Good signature from Rahul Sharma rsha...@apache.org
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 06E1 DBAC 2181 995F C97A  2CFE 3915 5BFD 5808 BCF5
Verifying Signature for file hdt-0.0.1.incubating-src.tar.gz.asc
gpg: Signature made Sun Mar 30 21:16:42 2014 PDT using RSA key ID 5808BCF5
gpg: Good signature from Rahul Sharma rsha...@apache.org
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 06E1 DBAC 2181 995F C97A  2CFE 3915 5BFD 5808 BCF5
bash-3.2$ $HOME/bin/verify_md5_checksums
md5sum: stat '*.bz2': No such file or directory
md5sum: stat '*.zip': No such file or directory
md5sum: stat '*.tgz': No such file or directory
hdt-0.0.1.incubating-bin.tar.gz: OK
hdt-0.0.1.incubating-src.tar.gz: OK
bash-3.2$ 


SIGS and CHECKSUM check out. Great work guys!

Cheers,
Chris



-Original Message-
From: Rahul Sharma rahul0...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, April 18, 2014 7:48 AM
To: d...@hdt.incubator.apache.org d...@hdt.incubator.apache.org,
general@incubator.apache.org general@incubator.apache.org
Subject: [VOTE] Release HDT version 0.0.1.incubating (RC3)

Hi,

I would like to call for a vote for Apache Hadoop Development Tools
(incubating), version 0.0.1.incubating. The vote has happened of the dev
mailing list and the community has approved the forth release
candidate(RC3)
for Apache Hadoop Development Tools (incubating), version
0.0.1.incubating.The release has Zookeper and HDFS features from the
*hadoop-eclipse-merge* codebase.The issues raised for previous release
candidates have been addressed in this release.

Please vote on releasing this package as Apache Hadoop Development Tools
0.0.1.incubating.

[ ] +1 Release this package as Apache HDT 0.0.1.incubating
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

PPMC Vote thread :
*http://apache.markmail.org/message/pm73p3xxcgt4zz6e
http://apache.markmail.org/message/pm73p3xxcgt4zz6e*

Vote Result :
http://apache.markmail.org/message/ykycte3demsxnzz7

Source and binary files:
http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc3/

The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-hdt
.git;a=commit;h=3672346b937b9cec029ac3e362f276ea64f1af92

PGP keys used to sign the release:
https://dist.apache.org/repos/dist/dev/incubator/hdt/KEYS

Some guideline to verify release can be found at :
http://apache.markmail.org/message/qj3srhvozapbwmq6

regards,
Rahul

[VOTE] publish Tika 0.1-incubating

[Chris Mattmann]

Hi Incubator PMC:

The Tika community voted on and has approved a proposal to release
Tika 0-1 incubating. Pursuant to the Releases section of the Incubation
Policy and with the endorsement of Jukka Zitting, one of our mentors we
would now like to request the permission of the Incubator PMC to publish the
tarball on the Tika Download page.

I'd also like to request on behalf of the Tika community that
/www/www.apache.org/dist/incubator/tika, be used as the warehouse for Tika
releases. I apologize for creating this directory ahead of time, without
asking the PMC: it's simply due to this being my first time as an incubator
release manager, and I assure you, it will not happen again.

Please vote by 6 PM PST Wednesday, 1/3/2008.

Thanks!

Proposal:
http://www.nabble.com/Tika-0.1-update-to14452777.html

Vote result:
http://www.nabble.com/-VOTE--Tika-0.1-incubating-Release-Candidate-2-to14522
857.html

Download page:
http://www.apache.org/dyn/closer.cgi/incubator/tika

(will update http://incubator.apache.org/tika/ to have link to above on left
hand navigation bar)

Releases section of the Incubation Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases


Thanks!

Cheers,
 Chris

__
Chris Mattmann, Ph.D.
[EMAIL PROTECTED]
Cognizant Development Engineer
Early Detection Research Network Project
_
Jet Propulsion LaboratoryPasadena, CA
Office: 171-266B Mailstop:  171-246
___

Disclaimer:  The opinions presented within are my own and do not reflect
those of either NASA, JPL, or the California Institute of Technology.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] publish Tika 0.1-incubating

[Chris Mattmann]

Hi Craig:

Thanks for the +1. Incubator PMC, anyone else out there? :)

Thanks!

Cheers,
 Chris



On 1/1/08 3:07 PM, Craig L Russell [EMAIL PROTECTED] wrote:

 +1 to release.
 
 I verified the signature and ran RAT on the artifacts. No issues.
 
 A few notes:
 
 0. Good work for your first release at Apache. Congratulations to the
 team.
 
 1. This message doesn't contain a direct link to the release being
 voted on. It would be good to include the link http://
 people.apache.org/~mattmann/apache-tika-0.1-incubating/rc2 (assuming
 that this is in fact the directory containing the release you want
 approval for). And I assume that the maven artifacts are to be
 uploaded to the central repositories.
 
 2. The release manager should endeavor to get his key signed. This is
 not a blocker for an incubator release but once in the wild, the key
 should become part of Apache's web of trust.
 
 3. No problem with the incubator/tika location for the *approved*
 release artifacts.
 
 Craig
 
 On Dec 31, 2007, at 11:20 AM, Chris Mattmann wrote:
 
 Hi Incubator PMC:
 
 The Tika community voted on and has approved a proposal to release
 Tika 0-1 incubating. Pursuant to the Releases section of the
 Incubation
 Policy and with the endorsement of Jukka Zitting, one of our
 mentors we
 would now like to request the permission of the Incubator PMC to
 publish the
 tarball on the Tika Download page.
 
 I'd also like to request on behalf of the Tika community that
 /www/www.apache.org/dist/incubator/tika, be used as the warehouse
 for Tika
 releases. I apologize for creating this directory ahead of time,
 without
 asking the PMC: it's simply due to this being my first time as an
 incubator
 release manager, and I assure you, it will not happen again.
 
 Please vote by 6 PM PST Wednesday, 1/3/2008.
 
 Thanks!
 
 Proposal:
 http://www.nabble.com/Tika-0.1-update-to14452777.html
 
 Vote result:
 http://www.nabble.com/-VOTE--Tika-0.1-incubating-Release-
 Candidate-2-to14522
 857.html
 
 Download page:
 http://www.apache.org/dyn/closer.cgi/incubator/tika
 
 (will update http://incubator.apache.org/tika/ to have link to
 above on left
 hand navigation bar)
 
 Releases section of the Incubation Policy:
 http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
 
 
 Thanks!
 
 Cheers,
  Chris
 
 __
 Chris Mattmann, Ph.D.
 [EMAIL PROTECTED]
 Cognizant Development Engineer
 Early Detection Research Network Project
 _
 Jet Propulsion LaboratoryPasadena, CA
 Office: 171-266B Mailstop:  171-246
 ___
 
 Disclaimer:  The opinions presented within are my own and do not
 reflect
 those of either NASA, JPL, or the California Institute of Technology.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 Craig Russell
 Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
 408 276-5638 mailto:[EMAIL PROTECTED]
 P.S. A good JDO? O, Gasp!
 

__
Chris Mattmann, Ph.D.
[EMAIL PROTECTED]
Cognizant Development Engineer
Early Detection Research Network Project
_
Jet Propulsion LaboratoryPasadena, CA
Office: 171-266B Mailstop:  171-246
___

Disclaimer:  The opinions presented within are my own and do not reflect
those of either NASA, JPL, or the California Institute of Technology.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] publish Tika 0.1-incubating

[Chris Mattmann]

Hi Jukka,

I just checked the archives. Thanks very much for the pointer to them. I was
expecting everything to be CC'ed to tika-dev, sorry about that.

Looks like we have:

5 +1 Jukka,Craig,ant elder,Niclas,Bertrand
0 +0
0 -1

The vote passes. I'll push out the release to the mirrors.

Thanks to all who voted on the PMC (and to others for voting also!)

Cheers,
 Chris


On 1/6/08 11:49 PM, Jukka Zitting [EMAIL PROTECTED] wrote:

 Hi,
 
 On Jan 7, 2008 3:54 AM, Chris Mattmann [EMAIL PROTECTED] wrote:
 Thanks for the +1. Incubator PMC, anyone else out there? :)
 
 Did you check the general@ archives (I recall you aren't subscribed)?
 We already have enough votes for the release. Will you tally the
 results, or should I?
 
 BR,
 
 Jukka Zitting

__
Chris Mattmann, Ph.D.
[EMAIL PROTECTED]
Cognizant Development Engineer
Early Detection Research Network Project
_
Jet Propulsion LaboratoryPasadena, CA
Office: 171-266B Mailstop:  171-246
___

Disclaimer:  The opinions presented within are my own and do not reflect
those of either NASA, JPL, or the California Institute of Technology.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] publish Tika 0.1-incubating

[Chris Mattmann]

Hi Niall,

Sorry: I checked: 

http://incubator.apache.org/whoweare.html

And it didn't have your name listed on the PMC. However, upon clicking that
other link on that page, I found your name on the file:

https://svn.apache.org/repos/private/committers/board/committee-info.txt

Under the Incubator PMC. Sorry for that omission. However, it may be a good
idea to get that first web page updated seeing as though it looks a bit
outdated. I'm guessing I'm not the only one that's made that mistake! :)

So, to recount, we have 6 +1's from Incubator PMC members. The vote passes
(thanks, Niall!) and I've pushed the release out.

Thanks!

Cheers,
 Chris



On 1/7/08 7:56 AM, Niall Pemberton [EMAIL PROTECTED] wrote:

 On Jan 7, 2008 3:53 PM, Chris Mattmann [EMAIL PROTECTED] wrote:
 Hi Jukka,
 
 I just checked the archives. Thanks very much for the pointer to them. I was
 expecting everything to be CC'ed to tika-dev, sorry about that.
 
 Looks like we have:
 
 5 +1 Jukka,Craig,ant elder,Niclas,Bertrand
 0 +0
 0 -1
 
 Minor nitpick, but I voted +1 as well.
 
 Niall
 
 The vote passes. I'll push out the release to the mirrors.
 
 Thanks to all who voted on the PMC (and to others for voting also!)
 
 Cheers,
  Chris
 
 
 
 On 1/6/08 11:49 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
 
 Hi,
 
 On Jan 7, 2008 3:54 AM, Chris Mattmann [EMAIL PROTECTED] wrote:
 Thanks for the +1. Incubator PMC, anyone else out there? :)
 
 Did you check the general@ archives (I recall you aren't subscribed)?
 We already have enough votes for the release. Will you tally the
 results, or should I?
 
 BR,
 
 Jukka Zitting
 
 
 __
 Chris Mattmann, Ph.D.
 [EMAIL PROTECTED]
 Cognizant Development Engineer
 Early Detection Research Network Project
 _
 Jet Propulsion LaboratoryPasadena, CA
 Office: 171-266B Mailstop:  171-246
 ___
 
 Disclaimer:  The opinions presented within are my own and do not reflect
 those of either NASA, JPL, or the California Institute of Technology.
 
 
 

__
Chris Mattmann, Ph.D.
[EMAIL PROTECTED]
Cognizant Development Engineer
Early Detection Research Network Project
_
Jet Propulsion LaboratoryPasadena, CA
Office: 171-266B Mailstop:  171-246
___

Disclaimer:  The opinions presented within are my own and do not reflect
those of either NASA, JPL, or the California Institute of Technology.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Mentors heartbeat

[Chris Mattmann]

Seriously, give me a break.

This has been discussed ad naseum - It's a quick simple measure
to see if one of the stated requirements for mentors (reading the
monthly report, and *signing that you read it*) has been fulfilled.
It means nothing more than that. I didn't say good. I didn't say bad.
You did.

Statistics are simply that - statistics. Meaning is derived from them
in multiple ways. You showing up on this list simply means at one point
over the past 3-4 years, you thought that putting your name on one of
those wiki pages was important enough to do so, 14 times.

Anyone that would like to let their coding/scripting do the talking,
I invite you to.

Until then, feel free to send more email messages debating this message
and the follow on reply that I won't be sending, and any further messages
to yourself and others after that.




-Original Message-
From: rgard...@opendirective.com rgard...@opendirective.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Thursday, September 4, 2014 12:05 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: RE: Mentors heartbeat

Surely we are not going to start counting signing off on a report as
indicative of good/bad mentoring?

What's important is whether podlings are getting what they need from
their mentors. Besides,  someone who has actively mentored one new
podling through initial setup in a first month will have one tick while
someone else who has done little more than sign off on reports for the
years will have many ticks.

Case in point, I've not actively mentored a project for at least a couple
of years (I just signed up to one this month), yet according to this
measure I am one of the more active mentors.

Lets not demean the work good new mentors are doing by counting a few
characters on a wiki page.

Note, I'm not saying rolling to assist the incubator and mentors is a bad
thing. I'm saying this specific example is a bad thing.

Sent from my Windows Phone

-Original Message-
From: Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov
Sent: ?9/?3/?2014 10:25 PM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Mentors heartbeat

These are the signed off per month mentors per podling over
the last 3 years. So it measures how many times a mentor has
signed off (summed across all podlings) during that time span.

Cheers,
Chris


++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++






-Original Message-
From: Konstantin Boudnik c...@apache.org
Reply-To: general@incubator.apache.org
Date: Wednesday, September 3, 2014 10:11 PM
To: general@incubator.apache.org
Subject: Re: Mentors heartbeat

Arguably, the number of mentored project doesn't reflect the activity
per
se. Unless I am missing something.

Cos

On Mon, Aug 25, 2014 at 04:46AM, Mattmann, Chris A (3980) wrote:
 Guys, +1 to eventually doing this with JSON and YAML. The big problem
 I see is curation (someone has to maintain it). Right now board reports
 and the wiki are what's used to make the report, so feel free to use my
 scripts for now until those are changed over. For example, I just ran
them
 right now (with some major pythonic updates to sniff mentors, and to
 map name to committer ID, and updating years and months to current and
 here's what I get):
 
 29 phunt
   24 tomwhite
   24 rvs
   24 mattmann
   23 cdouglas
   20 hsaputra
   18 bdelacretaz
   18 arvind
   16 adc
   14 smarru
   14 rgardler
   14 olamy
   14 gates
   13 jfarrell
   12 kevan
   11 tdunning
   11 jim
   11 grobmeier
   11 ddas
   10 omalley
9 mfranklin
8 wave
8 lresende
8 jbonofre
8 ate
7 twilliams
7 rfrovarp
7 ke4qqq
7 jukka
6 jzb
6 acmurthy
5 struberg
5 nslater
5 marrs
5 lewismc
5 greddin
5 bodewig
4 thorsten
4 mahadev
4 joes
4 jghoman
4 gsingers
4 fmui
3 upayavira
3 tommaso
3 stevenn
3 ssc
3 snoopdave
3 nick
3 marvin
3 hwright
3 gstein
3 gianugo
3 chipchilders
3 benh
3 apurtell
2 todd
2 larsh
2 jochen
2 jmclean
2 dkulp
2 dennisl
2 dashorst
2 cutting
2 antelder
1 yegor
1 wrowe
1 wavw
1 stack
1 simonetripodi
1 robweir
1 rmannibucau
1 rfeng
1 rbircher
1 nandana
1 mnour
1 jvermillard
1 fchrist
1 enis
1 elecharny
1 cos
1 coheigea
1 brett
1 bmargulies
1

Re: [DISCUSS] Apache Zest pTLP proposal

[Chris Mattmann]

Hi Roman, I can’t seem to comment on the COMDEV wiki page.

Also, great job on writing this up. I have a few amendments,
which I will just put into email since I can’t do so on the
wiki:

bq. Initially, a pTLP's PMC is only allowed to consist of ASF Members.


s/ASF Members/ASF Members and individuals identified as initial
PMC members on the pTLP proposal*/

* - incoming PMC members on the pTLP not already ASF members
will need to be justified in the incoming proposal.

The rest looks good. I would like AsterixDB to also be
considered in this model. Once I get karma I will put the
proposal up on the wiki.

Cheers,
Chris



-Original Message-
From: Roman Shaposhnik r...@apache.org
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Monday, February 9, 2015 at 10:35 PM
To: general@incubator.apache.org general@incubator.apache.org
Cc: Apache Board bo...@apache.org
Subject: [DISCUSS] Apache Zest pTLP proposal

Hi!

an existing open source community seeking
to enter ASF has decided to try an alternative
route and participate in the pTLP experiment.
Please refer to:
   https://cwiki.apache.org/confluence/display/COMDEV/Provisional+TLP
for an up-to-date record and documentation on
what pTLP is and how it relates to the traditional
Incubation process.

At this point we would like to invite IPMC to help
us with shaping up the pTLP proposal to a point
where we can successfully submit it to the ASF board.
Please comment on the Apache Zest pTLP proposal
and feel free to provide your feedback directly on
the ComDev wiki:
 
https://cwiki.apache.org/confluence/display/COMDEV/Proposal+for+Apache+Zes
t+pTLP

Thanks,
Roman.

-
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: my pTLP view

[Chris Mattmann]

+1000. My view too and with my support too.



-Original Message-
From: Greg Stein gst...@gmail.com
Date: Friday, January 23, 2015 at 5:42 AM
To: general@incubator.apache.org general@incubator.apache.org, Chris
Mattmann mattm...@apache.org, Jim Jagielski j...@jagunet.com
Subject: my pTLP view

Roman kicked off a query about  next steps, with links to several wiki
pages on possibilities. The IncubatorV2 page which describes a
probationary TLP is nothing like I have thought about.


In my mind, a pTLP looks *exactly* like any other PMC. They report
directly to the Board, they have infrastructure like any other project
(eg.
FOO.apache.org http://FOO.apache.org). But they have two significant
differences:


1. probationary text is prominent, much like we require incubating to
be prominent in various locations/messages for podlings


2. the initial PMC is comprised of only ASF Members. committers can be
chosen however the community decides. but the *project* is reviewed by
people with (hopefully/theoretically) experience with the Foundation and
its views on communities


That's it. By creating a PMC that understands what is needed, then they
can groom new PMC members, and use the standard process for adding them
to the PMC. The Board doesn't care about committership, so the pTLP can
do whatever it wants in that regard.


The Board might not accept a pTLP resolution because it wants more
greybeards on there, to help the community. Removing the probationary
label, is up to the pTLP to request, and the Board to approve. It is
usually pretty obvious when a community has
 reached that point, if you are talking about active ASF/PMC Members. But
the Board would apply its own level of trust.


There is a big element here, which didn't exist 12 years ago: the Board's
ability to review many projects. Before the Incubator, there weren't that
many projects. The Directors didn't have a lot of experience with a lot
of breadth. Nowadays, we review
 the work of *dozens* of projects every month. If one is a pTLP instead
of a regular TLP? Not a big deal. They have some operational
restrictions, but the report should be showing us a typical Apache
community.


The other aspect is IP clearance and management, which also didn't exist
a dozen years ago (and the Incubator was basically started in response to
some IP problems). We have a much better understanding there. Today, we
have the Incubator performing that,
 but no reason we can't have pTLPs managing that process. We file forms
about clearance with the Incubator, but really: that should be filed
$somehow defined by the VP of Legal Affairs (and *that* position/process
didn't exist until years after the Incubator
 was established).


TLPs are a recognition of a community. We can create probationary
communities, supported by ComDev, Legal, other communities, and reviewed
by the Board.


Speaking as a Director of the ASF, if a Resolution arrived on the Board's
Agenda to create such a pTLP, then I would be supportive. The pTLP
construct is independent of the Apache Incubator. Anybody is free to
define how they want to approach it, and then
 ask the Board if they are willing to try it.


Cheers,
-g








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

Re: [DISCUSS] Kudu incubator proposal

[Chris Mattmann]

Hi Alex,

We don’t have to hear from every author. If we don’t have an ICLA
or SGA on file for them, we’ll remove their code from the initial
import. BTW, that’s a few steps away. We’re also rehashing stuff
that has been discussed many times over, frankly.

Cheers,
Chris



-Original Message-
From: Alex Harui 
Reply-To: "general@incubator.apache.org" 
Date: Monday, November 23, 2015 at 10:46 AM
To: "general@incubator.apache.org" 
Subject: Re: [DISCUSS] Kudu incubator proposal

>
>
>On 11/23/15, 8:23 AM, "Mattmann, Chris A (3980)"
> wrote:
>
>>Alex, 
>>
>>Please re-read my email. As I stated we don’t take code that
>>authors don’t want us to have. So far, we haven’t heard from any of
>>the authors on the incoming Kudu project that that’s the case. If
>>it’s not the case, we go by the license of the project which stipulates
>>how code can be copied, modified, reused, etc.
>
>Yes, but my interpretation of your words is that folks have to opt out,
>not the other way around.  I thought the "take rule" meant that folks have
>to opt in via SGA/CLA or for minor stuff, I'd think an email to dev@ would
>suffice.
>
>So it isn't whether you haven't heard from any of the authors, it is
>whether you have heard from every author.
>
>Thanks,
>-Alex
>



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

Re: [DISCUSS] Metron incubator proposal

[Chris Mattmann]

Hi Bertrand,

Taken in the opposite case, is there someone from OpenSOC
objecting to this code being forked? It doesn’t sound like
there is a community there.


Cheers,
Chris

-Original Message-
From: Bertrand Delacretaz 
Reply-To: "general@incubator.apache.org" 
Date: Tuesday, December 1, 2015 at 2:02 AM
To: Incubator General 
Subject: Re: [DISCUSS] Metron incubator proposal

>Hi Owen,
>
>On Mon, Nov 30, 2015 at 5:55 PM, Owen O'Malley  wrote:
>> ...The
>> condensed version is that the original code base (OpenSOC) was created
>>by a
>> company (Cisco) that put it on github as ALv2, but then hasn't been
>>working
>> on it. We posted a message
>> 
>>>>
>> to the OpenSOC support group a month ago proposing a move to Apache and
>>got
>> a single positive response...
>
>The response I see there ("this is great news - looking forward to
>working with you") does not look to me like approval from whoever owns
>that code to move it to the ASF.
>
>What's needed IMO is approval from whoever owns the code that's at
>https://github.com/OpenSOC/opensoc . As usual, although the license of
>that code would allow us to fork, we only accept voluntary
>contributions.
>
>-Bertrand
>
>-
>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: MADLib "contributors"

[Chris Mattmann]

BTW, Roman, when discussing Spark’s move to Apache, and becoming
Apache Spark, this same question was asked. The things I’ve purported
in these situations is that it is fine to credit pre-Apache work as
simply the project name. Universities by their very nature don’t 
compete with companies, nor do they compete technologically with 501c3
charities and other foundations. I’m not saying they are prohibited
with competing. I’m saying, that there isn’t a competition. Companies can 
put 100-1000 people on a single feature. Universities don’t have the bandwidth
to do that at a University, and they are a different beast, than say,
company X, company Y and Z that have agreed to bring prior project A
now renamed Apache A. We should assume good faith in these situations
dealing with prior use. Clarifications are always welcomed, but we’re 
not going to go back and update 1000+ research papers and change all
references of Spark to Apache Spark it’s not feasible, nor is it desired
because it was Spark first, to start out with, and academic research use
is not competing with its use or name as an Apache project.



On 6/2/16, 5:22 PM, "shaposh...@gmail.com on behalf of Roman Shaposhnik" 
 wrote:

>Please stop putting a public mailing list on the same To: line as a
>private one. This is a pretty dangerous habit.
>
>I'll replace private@madlib with dev@madlib. Please reply to that part
>of the thread.
>
>Thanks,
>Roman.
>
>On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
>> Looking at:
>>
>> http://madlib.incubator.apache.org/community.html
>>
>> I am not sure I like the statement that:
>>
>> "including both individuals and institutions. Amongst our current 
>> contributors:"
>>
>> and then a list of entities.
>>
>> There are only individuals who contribute. Not institutions. In other
>> words, Pivotal is not a "contributor"... nor is ANY institution.
>>
>> Please fix this. Thx!
>>
>> PS: I am not on the private@madlib list
>> -
>> 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
>


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

Re: [ANNOUNCE] Apache Bahir 2.0.0

[Chris Mattmann]

Great work Luciano!



On 8/15/16, 2:19 PM, "Luciano Resende"  wrote:

The Apache Bahir PMC is pleased to announce the release of Apache Bahir
2.0.0  which is our first major release and provides the following
extensions for Apache Spark 2.0.0 :

Akka Streaming
MQTT Streaming and Structured Streaming
Twitter Streaming
ZeroMQ Streaming

For more information about Apache Bahir and to download the release:

http://bahir.apache.org

Thanks,

The Apache Bahir PMC




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

Re: Preliminary NetBeans cost findings (was: [DISCUSS] Apache NetBeans Incubator Proposal)

[Chris Mattmann]

Daniel this is great work. Thank you for outlining this. Wow!

Chris


On 9/24/16, 3:17 AM, "Daniel Gruno"  wrote:

Hi folks,

I've been going over the requirements for NetBeans infrastructure, it's
ballpark costs, bandwidth, machines needed and so forth, and the cliff
notes are as follows:

- 40-50TB/month in traffic required (mostly downloads+plugins)
- 8-13 machines/VMS are required
- Ballpark hardware costs are between $3k and $10k per year, depending
  on how much we can move to existing infrastructure and how close we
  come to the original setup. The most likely figure we are working with
  is $4.9k, but we should be prepared for a larger cost, just in case.
- The maintenance will be split between infra (downloads, web site, CI,
  new build machines) and the project (services, plugins, statistics),
  which will undoubtedly incur additional costs in terms of infra time
  spent on this, possibly to the tune of $10-20k in the initial phase.

Certain services like the plugins hosting will rely on Legal giving the
go-ahead for it, otherwise we'll have to find other people willing to
host this.

Other items like downloads may be offset by CDN providers offering their
assistance, but we should be prepared for this not being the case from
the beginning, thus the 40-50TB/month. Likewise, some machine costs
may be offset by cloud providers offering services for free.

Thus, I would submit to the IPMC that they consider asking the board for
a budget of roughly $10k per year for the NetBeans project, as well as
the additional time required of Infrastructure to implement this into
the existing ASF infra. As we may be able to pool resources and utilize
the new hardware for multiple projects, the cost may go down in the
coming years, but this is the baseline I suggest we consider when
approving NetBeans as a new podling.

With regards,
Daniel.


-
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: [DISCUSS] Olympian Incubation Proposal

[Chris Mattmann]

Yep this thread sounds very similar to those discussions. I think we have the 
story emerging here that we can move forward with.

Cheers,
Chris




On 9/29/16, 11:05 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote:

Hi Chris,

On Thu, Sep 29, 2016 at 7:23 PM, Chris Mattmann <mattm...@apache.org> wrote:
> ...I have a bit of a different understanding. We only accept code 
contributions
> that want to be here

This sounds similar to the discussions we had about Bloodhound back in
early 2012 - Roy had some good comments about what we should or should
not accept, at https://s.apache.org/roy_forks_2012

It's not all black and white, but IMO we do need some form of
agreement from the original authors about the ASF taking control of
their code. Or maybe a demonstration that they really don't care about
it anymore, which some of the info in this thread hints to.

-Bertrand

-
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: [DISCUSS] Olympian Incubation Proposal

[Chris Mattmann]

Ross is correct.

Chris




On 9/29/16, 8:15 AM, "Ross Gardler"  wrote:

OK, if Datastax are not objecting to the move then this is not a hostile 
fork. You should have your champion get clearance from legal@ for accepting 
this code under the open source license it is published under rather than under 
the SGA.

Ross

> -Original Message-
> From: Ted Wilmes [mailto:twil...@gmail.com]
> Sent: Thursday, September 29, 2016 11:12 AM
> To: general@incubator.apache.org; mbruk...@google.com
> Subject: Re: [DISCUSS] Olympian Incubation Proposal
> 
> Hello Ross,
> Per another one of the proposal submitters, Misha Brukman: "Datastax is 
not
> against the move of Titan to ASF but has stated that they will neither 
support
> or block it, as long as it doesn't involve them participating or signing 
the
> software grant"  I've CC'ed him to get him onto this thread.
> 
> Thanks,
> Ted
> 
> On Thu, Sep 29, 2016 at 9:28 AM, Ross Gardler 
> wrote:
> 
> > I see the GitHub code is untouched for over a year. Are Datastax
> > objecting to the proposal or is it just that they are unwilling to
> > actively supporting it?
> >
> > Ross
> >
> > > -Original Message-
> > > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> > > Sent: Thursday, September 29, 2016 10:23 AM
> > > To: general@incubator.apache.org
> > > Subject: Re: [DISCUSS] Olympian Incubation Proposal
> > >
> > > Hi Susan,
> > >
> > > community interest is the key part for sure. But we would like to
> > > avoid
> > any
> > > trouble about the grant agreement, etc.
> > >
> > > Just my $0.01
> > >
> > > Regards
> > > JB
> > >
> > > On 09/29/2016 03:03 PM, Susan Malaika wrote:
> > > > Hi JB
> > > > Datastax know about the incubator effort. As far as I know they
> > > > will
> > not sign
> > > the grant agreement. I was under the impression that the incubator
> > proposal
> > > can proceed after discussion if there is sufficient community 
interest.
> > > > Susan Malaika
> > > >
> > > > -Jean-Baptiste Onofré  wrote: -
> > > > To: general@incubator.apache.org
> > > > From: Jean-Baptiste Onofré 
> > > > Date: 09/29/2016 08:43AM
> > > > Subject: Re: [DISCUSS] Olympian Incubation Proposal
> > > >
> > > > Hi Henry,
> > > >
> > > > Is DataStax know and agree with the fork ?
> > > >
> > > > Else, the Software Grant Agreement won't be possible and it won't
> > > > be able to easy to head to graduation.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 09/29/2016 06:01 AM, Henry Saputra wrote:
> > > >> Hi All,
> > > >>
> > > >> Please find below a proposal for a new incubator podling, Apache
> > > >> Olympian, formerly Titan.
> > > >> Apache Olympian is software designed to support the processing of
> > > >> graphs so large that they require storage and computational
> > > >> capacities beyond what a single machine can provide.
> > > >>
> > > >> This project will be a fork of Titan graph database project (
> > > >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > > >> gith
> > > >>
> > >
> ub.com%2Fthinkaurelius%2Ftitan%2F=01%7C01%7CRoss.Gardler%40mic
> > >
> rosoft.com%7Cbff6cec6c3514332c7ac08d3e87433d0%7C72f988bf86f141af91ab
> > >
> 2d7cd011db47%7C1=J9Ur0GJAXUuWr1pLwivOkykimmgPEoOK5kB1vDJlI
> > > JM%3D=0) that already come with Apache License v2.0.
> > > >> The project was created by company called Aurelius and was
> > > >> acquired by Datstax.
> > > >> Coming to 2016 there has been less activity in the project as the
> > > >> original authors are busy with other software development, but
> > > >> there is significant interest from the community (see
> > > >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > > >> grou
> > > >>
> > >
> ps.google.com%2Fforum%2F%23!msg%2F=01%7C01%7CRoss.Gardler%4
> > > 0micr
> > > >>
> > >
> osoft.com%7Cbff6cec6c3514332c7ac08d3e87433d0%7C72f988bf86f141af91ab
> > > 2d
> > > >>
> > >
> 7cd011db47%7C1=wwJsPajQfTfxZgrF5wwBX04kk4v7iJ0afZ0NDlYWQck%
> > > 3D
> > > >> eserved=0
> > > >> aureliusgraphs/jEN_7QwVXZ4/mz3gik-FAgAJ)
> > > >>
> > > >> The community have tried to reaching out to Datastax to donate
> > > >> the copyright and trademark of project to ASF but it was not 
approved.
> > > >> Because of that, the community has decided to go to ASF with
> > > >> different
> > > >> name: Apache Olympian.
> > > >>
> > > >> The wiki proposal page is located at this URL:
> > > >>
> > > >>
> > > >> 

Re: [DISCUSS] Olympian Incubation Proposal

[Chris Mattmann]

Hi Bertrand,

I have a bit of a different understanding. We only accept code contributions
that want to be here. If the license for this project is ALv2 upstream from 
DataStax
then the community coming here for Olympian may fork the project and so long as
those committers and PMC part of the new project have ICLAs on file, there need 
not
be any informal agreement with any company. The company owns the name, the 
trademark,
etc., but the license allows forks and new communities to be made.

Cheers,
Chris


On 9/29/16, 1:20 AM, "Bertrand Delacretaz"  wrote:

Hi,

On Thu, Sep 29, 2016 at 6:01 AM, Henry Saputra  
wrote:
> ...This project will be a fork of Titan graph database project...
> ...The project was created by company called Aurelius and was acquired by
> Datstax...

We only accept friendly forks, and it looks like Titan belongs to
DataStax, so IMO you need at least an informal agreement from them
before forking at the ASF.

-Bertrand

-
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: [DISCUSS] Olympian Incubation Proposal

[Chris Mattmann]

The precedent set by Bloodhound, and other projects suggest to me that 
you could simply move forward after giving legal@ a heads up and just seeing
if there are any objections..or if lazy consensus just move forward and deal
with it during Incubation.

On 9/29/16, 11:33 AM, "Henry Saputra" <henry.sapu...@gmail.com> wrote:

Thanks for the insights, Ross, Bertrand, JB, and Chris,

As Alan has mentioned before, we have attempted numerous times and channels
to ask DataStax whether they opposed to us taking a fork to Apache with no
avail.

If anyone has connection to Datastax or especially the Titan team here, we
would love to be connected to.

And if it contact or reply is not happening, would moving to legal@ as Ross
mentioned be good solution or next step?


- Henry

On Thu, Sep 29, 2016 at 11:06 AM, Chris Mattmann <mattm...@apache.org>
wrote:

> Yep this thread sounds very similar to those discussions. I think we have
> the
> story emerging here that we can move forward with.
>
> Cheers,
> Chris
>
>
>
>
> On 9/29/16, 11:05 AM, "Bertrand Delacretaz" <bdelacre...@apache.org>
> wrote:
    >
> Hi Chris,
>
> On Thu, Sep 29, 2016 at 7:23 PM, Chris Mattmann <mattm...@apache.org>
> wrote:
> > ...I have a bit of a different understanding. We only accept code
> contributions
> > that want to be here
>
> This sounds similar to the discussions we had about Bloodhound back in
> early 2012 - Roy had some good comments about what we should or should
> not accept, at https://s.apache.org/roy_forks_2012
>
> It's not all black and white, but IMO we do need some form of
> agreement from the original authors about the ASF taking control of
> their code. Or maybe a demonstration that they really don't care about
> it anymore, which some of the info in this thread hints to.
>
> -Bertrand
>
> -
> 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
>
>




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

[DISCUSS] Policy Question: GA for GitHub for Podlings

[Chris Mattmann]

Hi,

As some of you may have seen the OpenWhisk podling being discussed now has
requested to use GitHub as its primary master. Greg Stein our ASF Infra Admin
has OK’ed this for OpenWhisk iff the IPMC is OK with it.

I ask now:

1. Is the IPMC OK with this for OpenWhisk?
2. Is the IPMC OK with this in general availability for Podlings?

I am +1 on both (IPMC hat on).

Thanks.

Cheers,
Chris






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

Re: [VOTE] Release Apache Joshua 6.1 RC#2

[Chris Mattmann]

Justin thanks for your thorough comments. Lewis, Matt & team we should take 
these back onto dev@j.i.a.o and address them.

RE: the language packs, they aren't officially Apache released as of now - they 
are simply on Matt Post's JHU website. Eventually we would like them to be 
Apache released, but we are working with infra@ (or at least were in the past) 
to get that done and we will require some increased space.

Cheers,
Chris


On 2016-11-28 20:40 (-0500), Justin Mclean  wrote: 
> Hi,
> 
> Sorry but it’s -1 (binding) as:
> - Your missing incubating in the release artefacts name. [1]
> - There are a number of binary files in the source release that look to be 
> compiled source code.
> 
> I checked:
> - name doesn’t include incubating
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE is missing a few things (see below)
> - a source file is missing an Apache header [7]
> - Several unexpected binary files are contained in the source release 
> [8][9][10][11]
> - Can compile from source
> 
> License is missing:
> - MIT licensed normalize.css v3.0.3 bundled in [5]
> - glyph icon fonts [6]
> 
> Not an issue but it's a little odd to have LICENSE and NOTICE.txt - usually 
> both are bare or both have .txt extension.
> 
> Also while looking at your site I noticed that the download links of you 
> incubating site [2] points to github, please change to point to the offical 
> release area.
> Also the 6.1 release has already been tagged and it available for public 
> download on github [4]  before this vote is finished. This is IMO against 
> Apache release policy [3] please remove.
> 
> I also notice you recently released the language packs (18th Nov) but there 
> doesn’t seem to have been a vote for that? Any reason for this?
> 
> Thanks,
> Justin
> 
> 1. http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> 2. 
> https://cwiki.apache.org/confluence/display/JOSHUA/Apache+Joshua+%28Incubating%29+Home
> 3. http://www.apache.org/dev/release.html#what
> 4. https://github.com/apache/incubator-joshua/releases
> 5. ./demo/bootstrap/css/bootstrap.min.css
> 6. apache-joshua-6.1/demo/bootstrap/fonts/*
> 7. ./src/test/java/org/apache/joshua/decoder/ff/tm/OwnerMapTest.java
> 8. ./bin/GIZA++
> 9. ./bin/mkcls
> 10. ./bin/snt2cooc.out
> 11. ,/src/test/resources/berkeley_lm/lm.berkeleylm.gz
> 
> 
> -
> 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: [DISCUSS] Apache Distributed Release Audit Tool (DRAT)

[Chris Mattmann]

Yeah, RE: the below (sorry for top post), this already came up in the Creadur 
community
and I encouraged them to contribute to DRAT and told them we’re welcoming. That 
said, I don’t 
want Creadur to be an umbrella project, and frankly DRAT *uses* RAT, but is not 
a fundamental part of 
Creadur and Vice-Versa. In 2 months, we could use NexB scancode [1]. Not saying 
we are 
going to, but the point is DRAT adds tremendous features well beyond what RAT 
does (
full D3 interactive output, interactive cockpit for auditing, incremental 
progress, archival of
audit logs, search of audit logs, etc etc.)

So, while we acknowledge and are thankful to build on top of these great Apache 
projects,
I would expect those communities and contributors to contribute to DRAT and 
earn their
merit the same way folks would anywhere else.

It’s probably also worth noting that DRAT has already been presented at 
ApacheCon, see
this talk [2], and that talk led to this PR (from an Apache member) [3] to 
upgrade RAT,
etc etc. 

Thanks,
Chris

[1] https://github.com/nexB/scancode-toolkit  
[2] 
https://apachecon2016.sched.com/event/6OJS/drat-an-unobtrusive-scalable-approach-to-large-scale-software-license-analysis-karanjeet-singh-university-of-southern-california
[3] https://github.com/chrismattmann/drat/pull/91 





On 8/10/17, 5:44 AM, "Greg Stein"  wrote:

On Thu, Aug 10, 2017 at 6:46 AM, Shane Curcuru  
wrote:

> (note mixed private/public lists)
>
> General questions, since... we haven't actually had any discussion yet.
>
> - Is there a particular hurry to bring this to pTLP faster than the
> traditional general@incubator discussion period is?
>

Didn't realize there were rules about TLPs needing to drop by the
Incubator. Or that timelines were required.

Seems this is simply a TLP resolution proposed to the Board, and the
Incubator has zero input or concern on what DRAT is asking from the Board.


> - Has the Apache Creadur project been consulted about the new project
> proposal, and in particular do they have any comments on using DRAT as
> the name, which subsumes their popular Rat name?
>

These are not the same communities. The Foundation should not "force" them
to work together.

They might logically make sense together, but the *communities* are
disjoint. There is zero reason for those communities to be lumped together.
In fact, it was the disjoint communities under an umbrella project that
spearheaded the Foundation's "blow up umbrellas" campaign a decade ago.

Communities define groupings. Not topic.

And does the DRAT acronym really impose on what the Creadur people are
doing with their Rat tool? Meh. That's a stretch.

>...

Cheers,
-g




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

Re: [DISCUSS] Apache Distributed Release Audit Tool (DRAT)

[Chris Mattmann]

Hi Shane,

On 8/10/17, 4:46 AM, "Shane Curcuru" <a...@shanecurcuru.org> wrote:

(note mixed private/public lists)

General questions, since... we haven't actually had any discussion yet.

- Is there a particular hurry to bring this to pTLP faster than the
traditional general@incubator discussion period is?

Is 2 weeks faster than the traditional general@incubator discussion? I brought 
the
original thread up August 2nd, the Board meeting will be August 16th, so that’s 
 2 full
weeks. I was under the impression that’s an appropriate amount of discussion 
time.
The discussion has already led to folks from the Wicket community submitting and
getting a PR merged to upgrade Proteus [1], and to generally good will about 
the submission.
The Creadur folks and others also have discussed it [2] and I have sent them an 
email in reply.

- Has the Apache Creadur project been consulted about the new project
proposal, and in particular do they have any comments on using DRAT as
the name, which subsumes their popular Rat name?

I don’t believe DRAT (which we’ve on the project also said is more like “D’oh”, 
or
“DRAT!” than it would be a Distributed creature or Creadur) completely subsumes
RAT at all. In fact, RAT itself is a loaded name, especially if you work in the 
CyberSec
community where RAT typically means Remote Access Tool (sharing two common words
with our Apache RAT, etc etc). And in CyberSec land a “RAT” is also kinda a 
“creature” because
it “infects” your computer, etc., etc., Regardless, I don’t think Apache DRAT 
completely subsumes
the name of Apache RAT at all for those reasons stated.

- It's awesome to see ™ included in a proposal (most people forget), but
they're mixed up.  Apache should be ® (when needed; when talking about
individual project names it's usually not needed) and most project names
should be ™.  So it would be either Apache® Rat™ or Apache Rat™.

Fixed.

Thanks for filling out the rest of the proposal.

Anytime!

Chris

[1] https://github.com/chrismattmann/drat/pull/96 
[2] https://s.apache.org/sPWK 


- Shane

    Chris Mattmann wrote on 8/10/17 1:59 AM:
> Hi Everyone,
> 
> Just as an FYI I've added a resolution to establish DRAT to the agenda.
> 
> On item - 2 of the proposed PMC includes members without an Apache 
account. What to do in this situation? If they start only as committers, that's 
fine, but then we would create an account for them after the fact. Is this the 
desire? If so I will update the resolution and we can VOTE them in as PMC after 
the project is establish should the Board agree to do so. 
> 
> Thanks,
> Chris
    > 
> 
> On 2017-08-02 10:35, Chris Mattmann <mattm...@apache.org> wrote: 
>> Hi Board-Chat@,
>>
>> CC/Incubator@
>>
>> We are proposing to bring DRAT (Distributed Release Audit Tool) to the 
ASF.
>> DRAT is a parallelized version of Apache RAT that uses OODT, Solr and 
Tika to
>> compute, visualize and interact with interesting statistics on code 
auditing as
>> output by RAT and Tika. With DRAT you can:
>>
>> • Audit large code repositories (has been tested in 100s of M of lines 
of
>> code, and 1000s of projects)  where RAT fails to complete – an example 
of running it across all of Apache
>> SVN is here: http://drat.dyndns.org:8080/dratviz/ You can also see its 
output
>> for a very large set of NSF funded geosciences code repositories here: 
>> http://drat.dyndns.org:8080/dratontoviz/ 
>> • Visualize and interact with the output from RAT and Tika in a 
dynamic fashion
>> • Get incremental status from code auditing
>> • Audit individual code repos and integrate the results into your 
project
>>
>> DRAT was funded by DARPA, NASA, the NSF and other government entities.
>>
>> We have prepared a preliminary proposal here: 
https://wiki.apache.org/incubator/DRATProposal
>>
>> We are working on flushing it out more, should be done by this weekend. 
We propose 
>> DRAT to be a straight to TLP (pTLP). I will add a resolution into the 
Board agenda for August 2017
>> for its consideration. I am CC’ing the Incubator so that we can 
potentially attract new contributors
>> both seasoned and junior to the project. We also welcome any 
contributors from Creadur interested
>> in learning more about OODT, Solr, Tika, etc. Also any Wicket gurus – 
we are using Wicket for one of
>> DRAT’s key user interfaces, Proteus.
>>
>> OK, thanks!
>>
>> Cheers,
>> Chris
>>

Re: [DISCUSS] Apache Distributed Release Audit Tool (DRAT)

[Chris Mattmann]

Hi Everyone,

Just as an FYI I've added a resolution to establish DRAT to the agenda.

On item - 2 of the proposed PMC includes members without an Apache account. 
What to do in this situation? If they start only as committers, that's fine, 
but then we would create an account for them after the fact. Is this the 
desire? If so I will update the resolution and we can VOTE them in as PMC after 
the project is establish should the Board agree to do so. 

Thanks,
Chris


On 2017-08-02 10:35, Chris Mattmann <mattm...@apache.org> wrote: 
> Hi Board-Chat@,
> 
> CC/Incubator@
> 
> We are proposing to bring DRAT (Distributed Release Audit Tool) to the ASF.
> DRAT is a parallelized version of Apache RAT that uses OODT, Solr and Tika to
> compute, visualize and interact with interesting statistics on code auditing 
> as
> output by RAT and Tika. With DRAT you can:
> 
> • Audit large code repositories (has been tested in 100s of M of lines of
> code, and 1000s of projects)  where RAT fails to complete – an example of 
> running it across all of Apache
> SVN is here: http://drat.dyndns.org:8080/dratviz/ You can also see its output
> for a very large set of NSF funded geosciences code repositories here: 
> http://drat.dyndns.org:8080/dratontoviz/ 
> • Visualize and interact with the output from RAT and Tika in a dynamic 
> fashion
> • Get incremental status from code auditing
> • Audit individual code repos and integrate the results into your project
> 
> DRAT was funded by DARPA, NASA, the NSF and other government entities.
> 
> We have prepared a preliminary proposal here: 
> https://wiki.apache.org/incubator/DRATProposal
> 
> We are working on flushing it out more, should be done by this weekend. We 
> propose 
> DRAT to be a straight to TLP (pTLP). I will add a resolution into the Board 
> agenda for August 2017
> for its consideration. I am CC’ing the Incubator so that we can potentially 
> attract new contributors
> both seasoned and junior to the project. We also welcome any contributors 
> from Creadur interested
> in learning more about OODT, Solr, Tika, etc. Also any Wicket gurus – we 
> are using Wicket for one of
> DRAT’s key user interfaces, Proteus.
> 
> OK, thanks!
> 
> Cheers,
> Chris
> 
> 
> 
> 
> 
> 
> -
> 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: [DISCUSS] Daffodil Incubation Proposal

[Chris Mattmann]

This sounds like a very interesting project. 

I don’t have the time to mentor at the moment but I will keep a close eye on it.

Cheers,
Chris Mattmann




On 7/25/17, 11:53 AM, "McHenry, Kenton Guadron" <mche...@illinois.edu> wrote:

Hi Dave,

The developers that were at NCSA have moved on to other organizations.  
While we still leverage Daffodil and are very much interested in seeing it move 
forward, development is currently done by the Tresys team.  Agreed on the 
synergy with Tika.

Kenton McHenry, Ph.D.
Principal Research Scientist, Adjunct Assistant Professor of Computer 
Science
Deputy Director of the Scientific Software & Applications Division
National Center for Supercomputing Applications, University of Illinois at 
Urbana-Champaign

On Jul 24, 2017, at 1:55 PM, Dave Fisher 
<dave2w...@comcast.net<mailto:dave2w...@comcast.net>> wrote:

Hi Kenton,

Is there any reason that you and others from the NCSA are not Initial 
Committers? That would make this proposal stronger.

Regarding Apache Tika - it relies on other projects including Apache POI 
and Apache PDFBox. They are pragmatic about what is used. If Daffodil works to 
expand then I think that there would be good synergy between the projects. I 
know as a POI PMC member that the POI community has significantly benefited 
from the Tika community some of whom are from Mitre.

To date Tika has not emphasized structured data, although they do extract 
content from Excel and OpenOffice.

I am intrigued.

Regards,
Dave

On Jul 24, 2017, at 10:55 AM, McHenry, Kenton Guadron 
<mche...@illinois.edu<mailto:mche...@illinois.edu>> wrote:

Yes, DFDL and its open source implementation Daffodil are more about file 
formats and getting access to the entirety of a file's contents in a consistent 
way through machine readable specifications.  The work has implications in the 
area of digital preservation allowing one to preserve these machine readable 
specifications rather than all the tools needed to open/save a file in order to 
work with it.  Imagine someone developing graphics software to work with 3D 
models and not having to worry about the hundreds of formats out there for 3D 
meshes (whether there are tools for opening the files and whether they can get 
access to those tools, whether the spec is available and worrying about how 
complex that spec is to implement, etc.), and simply building their code around 
the contents (e.g. vertices, faces, etc.).  One could come up with similar 
scenarios for other data types (documents, images, videos, audio, depth data, 
numeric data).  Ideally tools built supporting DFDL, could someday, support any 
format for that type without the developer having to worry about the details of 
how that data is represented within a file.

Kenton McHenry, Ph.D.
Principal Research Scientist, Adjunct Assistant Professor of Computer 
Science
Deputy Director of the Scientific Software & Applications Division
National Center for Supercomputing Applications, University of Illinois at 
Urbana-Champaign

On Jul 24, 2017, at 10:30 AM, Steve Lawrence 
<stephen.d.lawre...@gmail.com<mailto:stephen.d.lawre...@gmail.com><mailto:stephen.d.lawre...@gmail.com>>
 wrote:

I'll preface this saying that I don't have a ton of experience with
Apache Tika. But based on my understanding, Tika and Daffodil do have
somewhat similar goals, but reach them in different ways. For example,
Tika requires that one writes /code/ to perform data extraction, usually
relying on existing Java libraries to extract the desired metadata. The
downside to this is that code can be buggy, and libraries might not even
exist for formats of interest (especially common with legacy and
military data).

Daffodil, on the other hand, does not require one to write any code.
Instead, one writes a DFDL Schema (similar to XML Schema, with DFDL
annotations) that fully describes the data, which Daffodil then uses to
convert the data to XML/JSON for extraction. So adding support for a new
format means writing a new schema rather than new code. And less code
generally means less bugs. Also, for secure systems that require
certification, generally speaking, it is easier to certify a schema as
compared to code.

We certainly don't believe that Daffodil could replace Tika, but it does
have the potential to add new functionality to Tika for formats that do
not have existing libraries. One of our goals is to look into
integrating Daffodil support into tools like Tika. We'd love to hear
from Tika devs if this is something they'd be interested in.

I'll also add that whereas Tika tends to focus primarily on metadata,
DFDL schemas usually describe an entire file format down to the byt

Re: ZeroMQ licensing in Apache MXNet

[Chris Mattmann]

Hi Hen,

Why not explore the use of Apache Artemis as an alternative?

Cheers,
Chris




On 7/5/17, 11:23 PM, "Henri Yandell"  wrote:

One of the items that is on the list to do before releasing Apache MXNet is
removing ZeroMQ from the codebase/dependencies.

ZeroMQ is licensed under the LGPL 3.0 with an exception for static
compiling.

They have long been interested in relicensing to MPL 2.0, but haven't made
much progress, though they did relicense JeroMQ (Java
wrapper/implementaiton) last year.

In the last few months they've made a lot of progress towards relicensing:
https://github.com/zeromq/libzmq/tree/master/RELICENSE

I'd like to ask on legal-discuss@ for an exception (one year?) to continue
using ZeroMQ, with prominent documentation, in MXNet given the trend
towards MPL 2.0.

Any concerns before I do so?

Thanks,

Hen




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

Re: [DISCUSS] Podlings & Gitbox Usage

[Chris Mattmann]

I am +1 on this.
Thanks.

Cheers,
Chris




On 7/28/17, 9:00 AM, "Mahdi Mohammadi"  wrote:

I agree with this. Providing support for GitHub for all projects makes it
easier for everyone to contribute and follow up the project.

On Fri, Jul 28, 2017 at 4:48 PM, John D. Ament 
wrote:

> All,
>
> As many are aware, Infra has been rolling out a new service that allows
> projects to leverage git repositories dually hosted on github and ASF git
> repositories, commonly known as gitbox.  This effectively allows a project
> to commit directly to Github and have those commits reflect back on the 
ASF
> side.
>
> This has been especially useful to a number of projects, since the github
> interface gives many options for managing repositories.  I've recently 
also
> asked infra to open it up to allow any IPMC member to request a gitbox
> repository for any approved podling that is using gitbox.  Podlings I 
think
> have found this useful, since many of them come from a github background.
> They like using the tool and having it available for all to use.
>
> So with that said, I want to propose some broad incubator wide policies 
for
> gitbox.  I'd like to propose that gitbox usage is approved for all
> podlings, there is nothing to inhibit a podling to request a gitbox
> repository and as long as a podling feels the need to use gitbox, like 
they
> would any other tool that we can integrate with, they should be free to 
use
> it without any additional approvals required.
>
> So please let me know your thoughts.  If I don't hear any -1's I plan to
> submit an infra ticket early next week to enable the access for all
> approved podlings.  Please note that your first conversion may need some
> lead time with infra.
>
> Regards,
>
> John
>




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

[DISCUSS] Apache Distributed Release Audit Tool (DRAT)

[Chris Mattmann]

Hi Board-Chat@,

CC/Incubator@

We are proposing to bring DRAT (Distributed Release Audit Tool) to the ASF.
DRAT is a parallelized version of Apache RAT that uses OODT, Solr and Tika to
compute, visualize and interact with interesting statistics on code auditing as
output by RAT and Tika. With DRAT you can:

• Audit large code repositories (has been tested in 100s of M of lines of
code, and 1000s of projects)  where RAT fails to complete – an example of 
running it across all of Apache
SVN is here: http://drat.dyndns.org:8080/dratviz/ You can also see its output
for a very large set of NSF funded geosciences code repositories here: 
http://drat.dyndns.org:8080/dratontoviz/ 
• Visualize and interact with the output from RAT and Tika in a dynamic fashion
• Get incremental status from code auditing
• Audit individual code repos and integrate the results into your project

DRAT was funded by DARPA, NASA, the NSF and other government entities.

We have prepared a preliminary proposal here: 
https://wiki.apache.org/incubator/DRATProposal

We are working on flushing it out more, should be done by this weekend. We 
propose 
DRAT to be a straight to TLP (pTLP). I will add a resolution into the Board 
agenda for August 2017
for its consideration. I am CC’ing the Incubator so that we can potentially 
attract new contributors
both seasoned and junior to the project. We also welcome any contributors from 
Creadur interested
in learning more about OODT, Solr, Tika, etc. Also any Wicket gurus – we are 
using Wicket for one of
DRAT’s key user interfaces, Proteus.

OK, thanks!

Cheers,
Chris






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

Re: Proper way to retire podlings/madlib.yml

[Chris Mattmann]

Roman thank you and congrats for fulfilling your commitment. 

Sincerely appreciate it, and a model for all to follow.

Cheers,
Chris Mattmann




On 8/22/17, 1:13 PM, "shaposh...@gmail.com on behalf of Roman Shaposhnik" 
<shaposh...@gmail.com on behalf of r...@apache.org> wrote:

Hi!

first of all, I wanted to let y'all know that the MADlib trademark
transferred has finally happened and thus PODLINGNAMESEARCH-125
is now successfully resolved. Thanks to all who helped in the process!

This, in turn, made me go back to Incubator website to clean up
a few things for MADlib. I think we're good, but I've noticed this:
   ./content/podlings/madlib.yml
which I don't quite know how to "retire". Do I just remove it?

Thanks,
Roman.

-
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: ASF hosted binaries collecting user data without an explicit opt-in

[Chris Mattmann]

Makes sense to me.

Cheers,
Chris




On 6/8/17, 1:42 AM, "Greg Stein"  wrote:

On Thu, Jun 8, 2017 at 3:10 AM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Thu, Jun 8, 2017 at 10:01 AM, Raphael Bircher
>  wrote:
> > Am .06.2017, 09:43 Uhr, schrieb Bertrand Delacretaz
> > :
> >> ...Am I missing something?
> >
> > Yea, as far as I know it is in a old version who is in the archive,
> right. I
> > think this makes some difference...
>
> Ah yes you're right, we might want to pull the old binaries from the
> archive as well, in addition to the changes that I suggested.
>

In the specific case of Apache Ignite's invocation of that URL and passing
along certain data ... that is no longer relevant, even for OLD versions,
as the Foundation currently controls the ignite.run domain (and host). That
host will no longer resolve, so no HTTP request will be performed, and
(certainly) no data will be collected from old/new versions of Apache
Ignite.

Cheers,
Greg Stein
Infrastructure Administrator, ASF




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

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

[Chris Mattmann]

+1 from me.

Cheers,
Chris


On 6/4/17, 4:33 PM, "John D. Ament"  wrote:

All,

I want to bring up this discussion to see others opinions.  I would like to
move forward on migrating podling status maintenance into Whimsy.  Some of
the key things I want to improve upon is the overall experience around
managing the podling.  Sam's done a great job with rosters, but we can
start to track other things in whimsy, which mirrors what's in the status
file.  This can include IP Clearance/SGAs, Podling Name Searches, the
various dates we track.

Ultimately, I want to simplify how podlings are managed and make it a bit
easier on an end user.  Rather than needing to svn checkout to get files,
they simply go to a webpage, and assuming they're on that podling's roster
they would have access to update the status.  We could even automate
certain events so that when the board passes a resolution to graduate the
podling, the status file is updated along side any other record the podling
may have.

This does mean that the status file format is likely to change.  It also
means we're likely to move away from the java based build tool that has to
parse the XML templates into web pages and instead rely on a more
structured format for the status.

It doesn't mean you have to change.  If you like using SVN to edit this
stuff that's fine, you would still be able to.  Just what you're editing is
likely to be different.

Thoughts? Opinions?

John




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

Re: Discussion Forums?

[Chris Mattmann]

What’s wrong with lists.apache.org as a forum?

Cheers,
Chris




On 9/15/17, 9:26 PM, "Henri Yandell"  wrote:

The MXNet community have been discussing the possibilities of a discussion
forum. I suspect I'm out of date on the topic. Has there been Incubator
discussion on forums in the past few years? Are there projects running
forums? Discourse seems to be the current fashion.

My dated assumption is that Apache tends to be -1 to forums, but then we
had Nabble eking an existence on top of our lists as a semi-forum, then
StackExchange creating de facto Q forums; so perhaps user forums are a
thing now; or perhaps folk have their user@ mailing lists integrated with
discourse/stackoverflow etc?

Thanks,

Hen




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

Re: Discussion Forums?

[Chris Mattmann]

Thanks, Seb.

 

 

 

From: Seb Kiureghian <sebou...@gmail.com>
Reply-To: "sebou...@gmail.com" <sebou...@gmail.com>
Date: Sunday, September 17, 2017 at 4:30 PM
To: "d...@mxnet.incubator.apache.org" <d...@mxnet.incubator.apache.org>
Cc: "mattm...@apache.org" <mattm...@apache.org>, "general@incubator.apache.org" 
<general@incubator.apache.org>
Subject: Re: Discussion Forums?

 

are you making it so that the default way to interact with *Apache* MXNet (note 
emphasis) to not be on Apache infrastructure?

 

Discourse is open source so we can host it on Apache infrastructure and include 
it on our site. I will suggest PonyMail on the original thread and see what the 
community thinks. Thanks for your feedback Chris.

 

Seb

 

On Sun, Sep 17, 2017 at 4:19 PM, Chris Mattmann <mattm...@apache.org> wrote:

Hi,

I can’t stress this enough – tooling is all fine and dandy, but are you making 
it so that
the default way to interact with *Apache* MXNet (note emphasis) to not be on 
Apache
infrastructure?

There is no official policy other than if it didn’t happen on the list, it 
didn’t happen.
Decisions must be made on the mailing list, and frankly, as a casual observer 
of the dev
list I’m not entirely sure that decisions are occurring on the list right now.

Is there a reason not to use PonyMail? Or at least give it a try?

Chris



On 9/17/17, 4:16 PM, "Seb Kiureghian" <sebou...@gmail.com> wrote:

Hi Chris,

Members of the Apache MXNet community have pointed to the high level of
activity on Pytorch's forum <https://discuss.pytorch.org/> as a reason to

use Discourse. Discourse has a lot of great community features which make
it easier to have a discussion, follow specific questions, and learn
quickly, particularly for users new to deep learning. Discourse is open
source (GNU GPL) API and can also be integrated with the Apache mailing
lists, the way Nabble and PonyMail are. Is there an official stance or set
of guidelines wrt forums? Any guidance is appreciated.

Thanks!
-Seb Kiureghian



On Fri, Sep 15, 2017 at 10:06 PM, Chris Mattmann <mattm...@apache.org>
wrote:

> What’s wrong with lists.apache.org as a forum?
>
> Cheers,
> Chris
>
>
>
>
> On 9/15/17, 9:26 PM, "Henri Yandell" <bay...@apache.org> wrote:
>
> The MXNet community have been discussing the possibilities of a
> discussion
> forum. I suspect I'm out of date on the topic. Has there been 
Incubator
> discussion on forums in the past few years? Are there projects running
> forums? Discourse seems to be the current fashion.
>
> My dated assumption is that Apache tends to be -1 to forums, but then
> we
> had Nabble eking an existence on top of our lists as a semi-forum, 
then
> StackExchange creating de facto Q forums; so perhaps user forums are
> a
> thing now; or perhaps folk have their user@ mailing lists integrated
> with
> discourse/stackoverflow etc?
>
> Thanks,
>
> Hen
>
>
>
>



 

Re: Discussion Forums?

[Chris Mattmann]

Hi,

I can’t stress this enough – tooling is all fine and dandy, but are you making 
it so that
the default way to interact with *Apache* MXNet (note emphasis) to not be on 
Apache
infrastructure?

There is no official policy other than if it didn’t happen on the list, it 
didn’t happen. 
Decisions must be made on the mailing list, and frankly, as a casual observer 
of the dev
list I’m not entirely sure that decisions are occurring on the list right now.

Is there a reason not to use PonyMail? Or at least give it a try?

Chris



On 9/17/17, 4:16 PM, "Seb Kiureghian" <sebou...@gmail.com> wrote:

Hi Chris,

Members of the Apache MXNet community have pointed to the high level of
activity on Pytorch's forum <https://discuss.pytorch.org/> as a reason to
use Discourse. Discourse has a lot of great community features which make
it easier to have a discussion, follow specific questions, and learn
quickly, particularly for users new to deep learning. Discourse is open
source (GNU GPL) API and can also be integrated with the Apache mailing
lists, the way Nabble and PonyMail are. Is there an official stance or set
of guidelines wrt forums? Any guidance is appreciated.

Thanks!
-Seb Kiureghian



On Fri, Sep 15, 2017 at 10:06 PM, Chris Mattmann <mattm...@apache.org>
wrote:

> What’s wrong with lists.apache.org as a forum?
>
> Cheers,
> Chris
>
>
>
>
> On 9/15/17, 9:26 PM, "Henri Yandell" <bay...@apache.org> wrote:
>
> The MXNet community have been discussing the possibilities of a
> discussion
> forum. I suspect I'm out of date on the topic. Has there been 
Incubator
> discussion on forums in the past few years? Are there projects running
> forums? Discourse seems to be the current fashion.
>
> My dated assumption is that Apache tends to be -1 to forums, but then
> we
> had Nabble eking an existence on top of our lists as a semi-forum, 
then
> StackExchange creating de facto Q forums; so perhaps user forums are
> a
> thing now; or perhaps folk have their user@ mailing lists integrated
> with
> discourse/stackoverflow etc?
>
> Thanks,
>
> Hen
>
>
>
>




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

Re: [VOTE] Accept PageSpeed into the Apache Incubator

[Chris Mattmann]

+1 from me. (binding)

Thanks and good luck.

Chris




On 9/27/17, 12:04 PM, "Otto van der Schaaf"  wrote:

Hi All,

I would like to start a VOTE to bring the PageSpeed project in as an Apache
incubator
podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote
for which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept PageSpeed into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept PageSpeed into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PageSpeedProposal

Kind regards,

Otto

= Apache PageSpeed =

== Abstract ==
PageSpeed represents a series of open source technologies to help make the
web faster by rewriting web pages to reduce latency and bandwidth.

== Proposal ==
PageSpeed is an open source library that can be embedded in a web server or
proxy server to perform just-in-time optimization of its output. PageSpeed
has two stable open source implementations: mod_pagespeed (httpd),
ngx_pagespeed (nginx). There is also ats_pagespeed (experimental), and
there are proprietary implementations (Microsoft IIS, OpenLiteSpeed, and
others).

This proposal assumes a single project for the pagespeed library and its
three derived open source implementations:

 * [[https://github.com/pagespeed/mod_pagespeed|mod_pagespeed]]
 * [[https://github.com/pagespeed/ngx_pagespeed|ngx_pagespeed]]
 * [[

https://github.com/apache/trafficserver/tree/master/plugins/experimental/ats_pagespeed|ats_pagespeed
]]

== Background ==
Studies indicate that there is a negative correlation between slow site
speeds and important business metrics, like conversion, retention, and
others. Web performance optimization is a fast moving target, and it is
both hard and expensive for companies to keep up with the current state of
technology. PageSpeed optimization represents an opportunity for website
owners to deliver content up to date with the latest web performance best
practices at reduced costs, without changing development workflows.

== Rationale ==
We think that the ASF offers the ideal environment to foster and grow the
project’s community. Many organizations can benefit from automatic web
optimization.

== Initial Goals ==
The initial goals of the pagespeed project are several-fold:

 * Foster and grow the community
 * Move the existing codebases to Apache and integrate with the Apache
development process.
 * [[https://github.com/pagespeed/mod_pagespeed/issues/1601|Move the docs
into a separate repository]], so we can (more easily) decouple product
releases from documentation updates. (Ideally the process for making small
doc changes is a low friction one).
 * Finish and land [[

https://github.com/pagespeed/mod_pagespeed/issues/876|content-security-policy
support]]
 * Finish and land changes in PageSpeed’s resource fetching infrastructure
(including a change [[
https://github.com/pagespeed/mod_pagespeed/issues/262|that teaches it about
following redirects]]).
 * [[https://github.com/pagespeed/ngx_pagespeed/issues/1181|Add Alpine
Linux]] to the list of supported distributions due to popular demand.
 * Turn the [[

https://github.com/pagespeed/mod_pagespeed/wiki/Design-Doc:-Central-Controller|experimental
central controller process]] on by default. Having a central controller
process is useful when someone wants to implement:
   * Centrally fetching input resources
   * Running phantomjs centrally for implementing more advanced
optimization opportunities
   * Optimizing the file cache cleaning system
   * More efficient handling of compute intensive optimizations (like image
transcoding and (re-)compression)
   * If we do all of the above, a lot of the project’s dependencies would
end up running in a separate process. That offers further advantages from a
security perspective.

With the changes above, we propose releasing a 2.0 version of mod_pagespeed!

Next up would be allowing for intelligent decisions based on protocol
(http/2, quic). (ngx_pagespeed already is capable of doing this (and more)
to some extent with its [[
https://www.modpagespeed.com/doc/system#nginx_script_variables|script
variable support.]])

== Current Status ==
Google launched mod_pagespeed in 2010 to provide free open-source
technology to automate deployment of best practices for web front end
delivery. Since that time, the module has gained 

Re: How to handle exclusions in a software grant?

[Chris Mattmann]

Thanks John, I would clarify this on the contributing organization side, and 
pass
that along to the mentors. Thanks.




On 9/4/17, 8:13 AM, "John D. Ament" <johndam...@apache.org> wrote:

Agreed that the grant in question is missing a proper Exhibit A.  But
perhaps their intention with Exhibit A was to list what was excluded,
rather than what was included?

Considering that the committers in question had CLAs on file, I would be
surprised if 3rd Party Code were brought in.

John

On Mon, Sep 4, 2017 at 11:06 AM Chris Mattmann <mattm...@apache.org> wrote:

> Hi Bertrand,
>
> I believe they were supposed to provide a list to go along with that zip
> file.
>
> Can you double check?
>
> Cheers,
> Chris
>
>
>
>
> On 9/4/17, 3:30 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote:
>
> Hi,
>
> I'm mentoring a podling where a large initial code donation just
> happened.
>
> The corresponding software grant points to a large zip file indicating
> that the donation consists of that file's contents, "excluding any
> third-party and separately licensed material" that it contains.
>
> My understanding is that this puts the burden on the ASF to review
> each and every file found in there, and decide whether we can safely
> include it in an ASF release or if it's third-party and separately
> licensed.
>
> Do people agree with that interpretation?
>
> Have people seen similar cases before, and if yes how were they
> handled?
>
> -Bertrand
>
> -
> 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
>
>




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

Re: How to handle exclusions in a software grant?

[Chris Mattmann]

Hi Bertrand,

I believe they were supposed to provide a list to go along with that zip file. 

Can you double check?

Cheers,
Chris




On 9/4/17, 3:30 AM, "Bertrand Delacretaz"  wrote:

Hi,

I'm mentoring a podling where a large initial code donation just happened.

The corresponding software grant points to a large zip file indicating
that the donation consists of that file's contents, "excluding any
third-party and separately licensed material" that it contains.

My understanding is that this puts the burden on the ASF to review
each and every file found in there, and decide whether we can safely
include it in an ASF release or if it's third-party and separately
licensed.

Do people agree with that interpretation?

Have people seen similar cases before, and if yes how were they handled?

-Bertrand

-
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: [DISCUSS] Accept Science Data Analytics Platform (SDAP) into Apache Incubator

[Chris Mattmann]

Very interesting project Lewis and Thomas and glad to see this coming to the 
Incubator!



On 10/11/17, 11:22 AM, "lewis john mcgibbney"  wrote:

Hi Folks,
I would like to open a DISCUSS thread on the topic of accepting the Science
Data Analytics Platform (SDAP) <
https://wiki.apache.org/incubator/SDAPProposal> Project into the Incubator.
I am CC'ing Thomas Huang from NASA JPL who I have been working with to
build community around a kick-ass set of software projects under the SDAP
umbrella.
At this stage we would very much appreciate critical feedback from general@
community. We are also open to mentors who may have an interest in the
project proposal.
The proposal is pasted below.
Thanks in advance,
Lewis

= Abstract =
The Science Data Analytics Platform (SDAP) establishes an integrated data
analytic center for Big Science problems. It focuses on technology
integration, advancement and maturity.

= Proposal =
SDAP currently represents a collaboration between NASA Jet Propulsion
Laboratory (JPL), Florida State University (FSU), the National Center for
Atmospheric Research (NCAR), and George Mason University (GMU). SDAP brings
together a number of big data technologies including a NASA funded
OceanXtremes (Anomaly detection and ocean science), NEXUS (Deep data
analytic platform), DOMS (Distributed in-situ to satellite matchup), MUDROD
(Search relevancy and discovery) and VQSS (Virtualized Quality Screening
Service) under a single umbrella. Within the original Incubator proposal,
VQSS will not be included however it is anticipated that a future source
code donation will cover VQSS.

= Background and Rationale =
SDAP is a technology software solution currently geared to better enable
scientists involved in advancing the study of the Earth's physical
oceanography. With increasing global temperature, warming of the ocean, and
melting ice sheets and glaciers, the impacts can be observed from changes
in anomalous ocean temperature and circulation patterns, to increasing
extreme weather events and stronger/more frequent hurricanes, sea level
rise and storm surges affecting coastlines, and may involve drastic changes
and shifts in marine ecosystems. Ocean science communities are relying on
data distributed through data centers such as the JPL's Physical
Oceanographic Data Active Archive Center (PO.DAAC) to conduct their
research. In typical investigations, oceanographers follow a traditional
workflow for using datasets: search, evaluate, download, and apply tools
and algorithms to look for trends. While this workflow has been working
very well historically for the oceanographic community, it cannot scale if
the research involves massive amount of data. NASA's Surface Water and
Ocean Topography (SWOT) mission, scheduled to launch in April of 2021, is
expected to generate over 20PB data for a nominal 3-year mission. This will
challenge all existing NASA Earth Science data archival/distribution
paradigms. It will no longer be feasible for Earth scientists to download
and analyze such volumes of data. SDAP was therefore developed primarily as
a Web-service platform for big ocean data science at the PO.DAAC with open
source solutions used to enable fast analysis of oceanographic data. SDAP
has been developed collaboratively between JPL, FSU, NCAR, and GMU and is
rapidly maturing to become the generic platform for the next generation of
big science data solutions. The platform is an orchestration of several
previously funded NASA big ocean data solutions using cloud technology,
which include data analysis (NEXUS), anomaly detection (OceanXtremes),
matchup (DOMS), subsetting, discovery (MUDROD), and visualization (VQSS).
SDAP will enable web-accessible, fast data analysis directly on huge
scientific data archives to minimize data movement and provide access,
including subset, only to the relevant data.

= Science Data Analytics Platform Project Overview =
SDAP consists of several loosely coupled, independently functioning
sub-projects. The graphic below displays an overview of how these
sub-projects fuse together. N.B., although the graphic uses terminology
relating to OceanWorks, essentially the SDAP architecture is identical.

{{attachment:sdap.png}}

== OceanXtremes ==
Oceanographic Data-Intensive Anomaly Detection and Analysis Portal. An
application that allows you to view imagery and perform analysis on sea
level rise data.

'''Objective'''
Develop an anomaly detection system which identifies items, events or
observations which do not conform to an expected pattern.
 * Mature and test domain-specific, multi-scale anomaly and feature
detection algorithms.
 * Identify 

Re: [VOTE] Accept Science Data Analytics Platform (SDAP) into Apache Incubator WAS Re: [DISCUSS] Accept Science Data Analytics Platform (SDAP) into Apache Incubator

[Chris Mattmann]

+1 binding from me…thanks and good luck

Cheers,
Chris





On 10/17/17, 2:04 PM, "lewis john mcgibbney"  wrote:

Hi Folks,
Having secured a mentorship team consisting of the following IPMC Members,
I am happy to open a formal VOTE thread on accepting the Science Data
Analytics Platform (SDAP) into Apache Incubator.

   - Lewis John McGibbney (lewi...@apache.org)
   - Raphael Bircher (bircher at apace dot org)
   - Suneel Marthi (smarthi at apache dot org)

Thank you to both Raphael and Suneel for coming forward. :)
The VOTE will be open for at least 72 hours.

[ ] +1 Accept Science Data Analytics Platform (SDAP) into Apache Incubator
[ ] +/-0 ... just because
[ ] -1 Do NOT Accept Science Data Analytics Platform (SDAP) into Apache
Incubator... because

Thanks in advance to all participants.
Lewis

P.S. Here is a binding +1 from me

On Wed, Oct 11, 2017 at 11:22 AM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I would like to open a DISCUSS thread on the topic of accepting the
> Science Data Analytics Platform (SDAP)  incubator/SDAPProposal> Project into the Incubator.
> I am CC'ing Thomas Huang from NASA JPL who I have been working with to
> build community around a kick-ass set of software projects under the SDAP
> umbrella.
> At this stage we would very much appreciate critical feedback from 
general@
> community. We are also open to mentors who may have an interest in the
> project proposal.
> The proposal is pasted below.
> Thanks in advance,
> Lewis
>
> = Abstract =
> The Science Data Analytics Platform (SDAP) establishes an integrated data
> analytic center for Big Science problems. It focuses on technology
> integration, advancement and maturity.
>
> = Proposal =
> SDAP currently represents a collaboration between NASA Jet Propulsion
> Laboratory (JPL), Florida State University (FSU), the National Center for
> Atmospheric Research (NCAR), and George Mason University (GMU). SDAP 
brings
> together a number of big data technologies including a NASA funded
> OceanXtremes (Anomaly detection and ocean science), NEXUS (Deep data
> analytic platform), DOMS (Distributed in-situ to satellite matchup), 
MUDROD
> (Search relevancy and discovery) and VQSS (Virtualized Quality Screening
> Service) under a single umbrella. Within the original Incubator proposal,
> VQSS will not be included however it is anticipated that a future source
> code donation will cover VQSS.
>
> = Background and Rationale =
> SDAP is a technology software solution currently geared to better enable
> scientists involved in advancing the study of the Earth's physical
> oceanography. With increasing global temperature, warming of the ocean, 
and
> melting ice sheets and glaciers, the impacts can be observed from changes
> in anomalous ocean temperature and circulation patterns, to increasing
> extreme weather events and stronger/more frequent hurricanes, sea level
> rise and storm surges affecting coastlines, and may involve drastic 
changes
> and shifts in marine ecosystems. Ocean science communities are relying on
> data distributed through data centers such as the JPL's Physical
> Oceanographic Data Active Archive Center (PO.DAAC) to conduct their
> research. In typical investigations, oceanographers follow a traditional
> workflow for using datasets: search, evaluate, download, and apply tools
> and algorithms to look for trends. While this workflow has been working
> very well historically for the oceanographic community, it cannot scale if
> the research involves massive amount of data. NASA's Surface Water and
> Ocean Topography (SWOT) mission, scheduled to launch in April of 2021, is
> expected to generate over 20PB data for a nominal 3-year mission. This 
will
> challenge all existing NASA Earth Science data archival/distribution
> paradigms. It will no longer be feasible for Earth scientists to download
> and analyze such volumes of data. SDAP was therefore developed primarily 
as
> a Web-service platform for big ocean data science at the PO.DAAC with open
> source solutions used to enable fast analysis of oceanographic data. SDAP
> has been developed collaboratively between JPL, FSU, NCAR, and GMU and is
> rapidly maturing to become the generic platform for the next generation of
> big science data solutions. The platform is an orchestration of several
> previously funded NASA big ocean data solutions using cloud technology,
> which include data analysis (NEXUS), anomaly detection (OceanXtremes),
> matchup (DOMS), subsetting, discovery (MUDROD), and visualization (VQSS).
> SDAP will enable web-accessible, fast data analysis 

Re: [DISCUSS] Druid incubation proposal

[Chris Mattmann]

+1 from me...

Chris

On 2/21/18, 7:08 PM, "Selvamohan Neethiraj"  wrote:

+1 for adding Druid to ASF

Thanks,
Selva-

> On Feb 21, 2018, at 10:03 PM, Jitendra Pandey  
wrote:
> 
> +1
> Druid will be a great addition to ASF.
> 
> On 2/21/18, 5:06 PM, "Ashutosh Chauhan"  wrote:
> 
>+1 for Druid in ASF.
>I have been involved with Hive Druid integration. If you are looking 
for
>mentors, happy to help.
> 
>Thanks,
>Ashutosh
> 
>On Fri, Feb 16, 2018 at 2:20 PM, Tom Barber  wrote:
> 
>> I can second most of that from the peanut gallery, my high level
>> interactions with a few Druid folk and keeping a watchful eye on a very
>> exciting project over the last few years.
>> 
>> I think the Druid project would make an excellent addition to the ASF
>> portfolio.
>> 
>> Tom
>> 
>> 
>> On 16/02/18 22:17, Julian Hyde wrote:
>> 
>>> As Champion for this proposal, let me say that the Druid project will be
>>> an excellent addition to the ASF. I have been an observer of the project
>>> for a couple of years, and in many respects it is already operating in 
the
>>> Apache Way. Druid had paid developers from a number of companies, some 
of
>>> whom were in competition, and its governance was strong enough to 
navigate
>>> the choppy waters that that can create.
>>> 
>>> A number of Druid committers subsequently started to work on Apache
>>> projects (Gian on Calcite, and Slim and Nishant on Hive) and so already
>>> know what to expect.
>>> 
>>> You can get a sense of the project dynamic by reading the archives of
>>> their dev list: 
https://groups.google.com/forum/#!forum/druid-development
>>> 
>>> 
>>> Julian
>>> 
>>> 
>>> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
 
 Hi all,
 
 I would like to open up a discussion about incubating Druid at Apache.
 I've
 included a proposal in this mail and have also posted a draft at
 https://wiki.apache.org/incubator/DruidProposal. More information about
 Druid is also available on our project web site at: http://druid.io/
 
 Thanks for your consideration!
 
 Gian
 
 = Druid Proposal =
 
 == Abstract ==
 
 Druid is a high-performance, column-oriented, distributed data store.
 
 == Proposal ==
 
 Druid is an open source data store designed for real-time exploratory
 analytics on large data sets. Druid's key features are a 
column-oriented
 storage layout, a distributed shared-nothing architecture, and ability 
to
 generate and leverage indexing and caching structures. Druid is 
typically
 deployed in clusters of tens to hundreds of nodes, and has the ability 
to
 load data from Apache Kafka and Apache Hadoop, among other data 
sources.
 Druid offers two query languages: a SQL dialect (powered by Apache
 Calcite)
 and a JSON-over-HTTP API.
 
 Druid was originally developed to power a slice-and-dice analytical UI
 built on top of large event streams. The original use case for Druid
 targeted ingest rates of millions of records/sec, retention of over a
 year
 of data, and query latencies of sub-second to a few seconds. Many 
people
 can benefit from such capability, and many already have (see
 http://druid.io/druid-powered.html). In addition, new use cases have
 emerged since Druid's original development, such as OLAP acceleration 
of
 data warehouse tables and more highly concurrent applications operating
 with relatively narrower queries.
 
 == Background ==
 
 Druid is a data store designed for fast analytics. It would typically 
be
 used in lieu of more general purpose query systems like Hadoop 
!MapReduce
 or Spark when query latency is of the utmost importance. Druid is often
 used as a data store for powering GUI analytical applications.
 
 The buzzwordy description of Druid is a high-performance,
 column-oriented,
 distributed data store. What we mean by this is:
 
 * "high performance": Druid aims to provide low query latency and high
 ingest rates possible.
 * "column-oriented": Druid stores data in a column-oriented format, 
like
 most other systems designed for analytics. It can also store indexes
 along
 with the columns.
 * "distributed": Druid is deployed in clusters, typically of tens to
 

Re: [VOTE] Accept Druid into the Apache Incubator

[Chris Mattmann]

+1 binding.

Thanks,
Chris



On 2/22/18, 11:04 AM, "Julian Hyde"  wrote:

Hi all,

After some discussion on the Druid proposal[1], I'd like to
start a vote on accepting Druid into the Apache Incubator,
per the ASF policy[2] and voting rules[3].

A vote for accepting a new Apache Incubator podling is a
majority vote for which only Incubator PMC member votes are
binding. Votes from other people are also welcome as an
indication of people's enthusiasm (or lack thereof).

Please do not use this VOTE thread for discussions.  If
needed, start a new thread instead.

This vote will run for at least 72 hours. Please VOTE as
follows:
 [ ] +1 Accept Druid into the Apache Incubator
 [ ] +0 Abstain
 [ ] -1 Do not accept Druid into the Apache Incubator
because ...

The proposal is listed below, but you can also access it on
the wiki[4].

Julian

[1] 
https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E

[2] 
https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor

[3] http://www.apache.org/foundation/voting.html

[4] https://wiki.apache.org/incubator/DruidProposal





= Druid Proposal =

== Abstract ==

Druid is a high-performance, column-oriented, distributed
data store.

== Proposal ==

Druid is an open source data store designed for real-time
exploratory analytics on large data sets. Druid's key
features are a column-oriented storage layout, a distributed
shared-nothing architecture, and ability to generate and
leverage indexing and caching structures. Druid is typically
deployed in clusters of tens to hundreds of nodes, and has
the ability to load data from Apache Kafka and Apache
Hadoop, among other data sources. Druid offers two query
languages: a SQL dialect (powered by Apache Calcite) and a
JSON-over-HTTP API.

Druid was originally developed to power a slice-and-dice
analytical UI built on top of large event streams. The
original use case for Druid targeted ingest rates of
millions of records/sec, retention of over a year of data,
and query latencies of sub-second to a few seconds. Many
people can benefit from such capability, and many already
have (see http://druid.io/druid-powered.html). In addition,
new use cases have emerged since Druid's original
development, such as OLAP acceleration of data warehouse
tables and more highly concurrent applications operating
with relatively narrower queries.

== Background ==

Druid is a data store designed for fast analytics. It would
typically be used in lieu of more general purpose query
systems like Hadoop MapReduce or Spark when query latency is
of the utmost importance. Druid is often used as a data
store for powering GUI analytical applications.

The buzzwordy description of Druid is a high-performance,
column-oriented, distributed data store. What we mean by
this is:

* "high performance": Druid aims to provide low query
  latency and high ingest rates possible.
* "column-oriented": Druid stores data in a column-oriented
  format, like most other systems designed for analytics. It
  can also store indexes along with the columns.
* "distributed": Druid is deployed in clusters, typically of
  tens to hundreds of nodes.
* "data store": Druid loads your data and stores a copy of
  it on the cluster's local disks (and may cache it in
  memory). It doesn't query your data from some other
  storage system.

== Rationale ==

Druid is a mature, active project with a large number of
production installations, dozens of contributors to each
release, and multiple vendors offering professional
support. Given Druid's strong community, its close
integration with many other Apache projects (such as Kafka,
Hadoop, and Calcite), and its pre-existing Apache-inspired
governance structure, we feel that Apache is the best home
for the project on a long-term basis.

== Current Status ==

=== Meritocracy ===

Since Druid was first open sourced the original developers
have solicited contributions from others, including through
our blog, the project mailing lists, and through accepting
GitHub pull requests. We have an Apache-inspired governance
structure with a PMC and committers, and our committer ranks
include a good number of people from outside the original
development team.

=== Community ===

The Druid core developers have sought to nurture a community
throughout the life of the project. We use GitHub as the
focal point for bug reports and code contributions, and the

[HEADS UP] Apache DRAT prototype

[Chris Mattmann]

Hi Incubator@,

 

Just to give you a heads up, over in Apache DRAT land we now have a 
pretty solid UI and a weekly scan process set up to scan all of the Gitbox
repos using our Proteus (new) system UI. You can see our demo/prototype
here:

 

http://drat-vm.apache.org:8080/proteus-new/ 

 

It goes down every now and then as we are making a few last minute 
tweaks to the UI (for example probably the last update we will make before
beginning a 1.0-RC1 process is to update the projects table to be paginated).

 

The UI is based on Vue.js and is the result of amazing work this summer by 
our GSOC 2018 student Ahmed Ifhaam and also work by Tom Barber, and 
others in DRAT.

 

Our intention is to provide this as a service to the ASF community and to set
up weekly or bi-weekly full scans. We haven’t fully decided how often to run 
it (yet) since during the process of it running some elements of the UI are 
inaccessible
for short periods of time. We may do run one week, let it sit for a week, then 
run
another week, etc. There are some interesting visualizations that give you a 
feel 
for how people are doing development at the ASF. Take a gander.

 

Please send any feedback to d...@drat.apache.org Thanks everyone.

 

Cheers,

Chris Mattmann
(on behalf of die-hard Apache DRAT fans everywhere) 

 

 

Re: Poddlings length of time in the incubator

[Chris Mattmann]

I’m game to help with Joshua for sure. I haven’t really been participating in 
Senssoft. 

But I know that community (originally from XDATA) and they want to do well. 

 

I think that the only thing next on Joshua is to post the resolution to 
graduate, which
I never got around to doing.

 

Thanks,

Chris

 

 

 

 

From: Justin Mclean 
Reply-To: "general@incubator.apache.org" 
Date: Friday, August 31, 2018 at 3:39 PM
To: "general@incubator.apache.org" 
Subject: Re: Poddlings length of time in the incubator

 

Hi,

 

Thanks Lewis for that. Lets see if we can get these two projects to graduate. 
If they need help with that (i.e. mentors are missing) please ask for help here.

 

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 SensSoft (Incubating) UserALE.js 1.0.0 RC#1

[Chris Mattmann]

@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: DB7B 5199 121C 08A5 C8F4  052B 3A47 17F0 48BA EBF6
Verifying Signature for file apache-senssoft-useralejs-1.0.0-src.tar.gz.asc
gpg: assuming signed data in 'apache-senssoft-useralejs-1.0.0-src.tar.gz'
gpg: Signature made Tue Feb 20 19:52:20 2018 PST
gpg:using RSA key 3A4717F048BAEBF6
gpg: Good signature from "Lewis John McGibbney (CODE SIGNING KEY) 
<lewi...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: DB7B 5199 121C 08A5 C8F4  052B 3A47 17F0 48BA EBF6
Verifying Signature for file apache-senssoft-useralejs-1.0.0-src.zip.asc
gpg: assuming signed data in 'apache-senssoft-useralejs-1.0.0-src.zip'
gpg: Signature made Tue Feb 20 19:52:20 2018 PST
gpg:using RSA key 3A4717F048BAEBF6
gpg: Good signature from "Lewis John McGibbney (CODE SIGNING KEY) 
<lewi...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: DB7B 5199 121C 08A5 C8F4  052B 3A47 17F0 48BA EBF6
nonas:apache-ss-1.0.0 mattmann$

Great work!

Cheers,
Chris




++++++
Chris Mattmann, Ph.D.
Associate Chief Technology and Innovation Officer, OCIO
Manager, Advanced IT Research and Open Source Projects Office (1761)
Manager, NSF and Open Source Programs and Applications Office (8212)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-322, Mailstop: 171-3rd Floor
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++
 
 
On 2/26/18, 9:05 AM, "lewis john mcgibbney" <lewi...@apache.org> wrote:

Hi Folks,
This thread is an official general@ VOTE to release the Apache SensSoft
(Incubating) UserALE.js 1.0.0 RC#1. The previous SensSoft (Incubating)
community VOTE [0] passed with RESULTS at [1].
This VOTE will be open for at least 72 hours and will pass if at least 3
IPMC members VOTE +1.
Apache SensSoft (Incubating) UserALE.js is released in a number of forms

1) source and binary artifacts which can be found at [2] alongside
accompanying .asc, .md5 and .sha512 accompanying signatures.

2) The tagged source [3] commitId b29542e6cc1e74c4caccdeb9ed4191013498e9ee

All artifacts were signed by 48BAEBF6 2013-10-28 Lewis John McGibbney (CODE
SIGNING KEY) <lewi...@apache.org> included within the SensSoft KEYS file
[4].

Further to the VOTE passing, artifacts will also be published via the NPM
channel for wider distribution.

Lewis

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

P.S. Here is my IPMC-binding +1

[0] https://s.apache.org/ysWS
[1] https://s.apache.org/FHKx
[2] https://dist.apache.org/repos/dist/dev/incubator/senssoft/
apache-senssoft-useralejs-1.0.0/
[3] https://s.apache.org/fzXf
[4] https://dist.apache.org/repos/dist/dev/incubator/senssoft/KEYS

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc




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

Re: [VOTE] - Graduate Apache Joshua (incubating) as a TLP

[Chris Mattmann]

+1 binding.

 

Go Joshua Go!

 

Cheers,
Chris

 

 

 

 

From: Tommaso Teofili 
Reply-To: "d...@joshua.incubator.apache.org" 
Date: Friday, September 21, 2018 at 5:54 AM
To: "general@incubator.apache.org" 
Cc: "d...@joshua.incubator.apache.org" 
Subject: [VOTE] - Graduate Apache Joshua (incubating) as a TLP

 

Hi all,

 

 

The Apache Joshua podling PMC would like the project to graduate to a TLP.

Joshua entered Incubation on February 13th, 2016.

The 6.1 release was the first one done within ASF as an Incubator

project, the PPMC has grown since incubation start.

 

Vote:

[ ] +1 - Recommend Graduation of Apache Joshua as a TLP

[ ] -1 - Do not recommend graduation of Apache Joshua because ….

 

 

The Graduation Proposal was written, discussed and voted on the

project dev@ list [1,2] and here on general@ [3]. As per

recommendations made in [3], the By-Laws Clause was removed [4].

The final resolution can be found at [5].

 

 

Regards,

Tommaso

 

 

[1] : 
https://lists.apache.org/thread.html/2687c75696b61344dadf085c1f48443f71baaf88a9b012f86c35d2e6@%3Cdev.joshua.apache.org%3E

[2] : 
https://lists.apache.org/thread.html/8ef1f4a9919f56979507fae749af691acb011e9ca7da9bc64bbfc8aa@%3Cdev.joshua.apache.org%3E

[3] : 
https://lists.apache.org/thread.html/6c274f2ec6261828c636e950447a2c7d926bcc91f95cc10f183690a7@%3Cdev.joshua.apache.org%3E

[4] : 
https://lists.apache.org/thread.html/7bd8bb062c96cde65c4d7fd4dd1310aed0169d5922b40ec78216d161@%3Cdev.joshua.apache.org%3E

[5] :

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 statistical and other forms of machine

 

translation.

 

NOW, THEREFORE, BE IT RESOLVED, that a Project Management

 

Committee (PMC), to be known as the "Apache Joshua Project",

 

be and hereby is established pursuant to Bylaws of the

 

Foundation; and be it further

 

RESOLVED, that the Apache Joshua Project be and hereby is

 

responsible for the creation and maintenance of software

 

related to statistical and other forms of machine translation;

 

and be it further

 

RESOLVED, that the office of "Vice President, Apache Joshua" be

 

and hereby is created, the person holding such office to

 

serve at the direction of the Board of Directors as the chair

 

of the Apache Joshua Project, and to have primary responsibility

 

for management of the projects within the scope of

 

responsibility of the Apache Joshua Project; and be it further

 

RESOLVED, that the persons listed immediately below be and

 

hereby are appointed to serve as the initial members of the

 

 

Apache Joshua Project:

 

 

* Tom Barber  

 

 

* Thamme Gowda

 

 

* Felix Hieber

 

 

* Lewis John McGibbney

 

 

* Chris Mattmann  

 

 

* Matt Post   

 

 

* Paul Ramirez

 

 

* Henry Saputra   

 

 

* Kellen Sunderland   

 

 

* Tommaso Teofili 

 

 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tommaso Teofili

 

be appointed to the office of Vice President, Apache Joshua to

 

serve in accordance with and subject to the direction of the

 

Board of Directors and the Bylaws of the Foundation until

 

death, resignation, retirement, removal or disqualification,

 

or until a successor is appointed; and be it further

 

RESOLVED, that the Apache Joshua Project be and hereby

 

is tasked with the migration and rationalization of the Apache

 

Incubator Joshua podling; and be it further

 

RESOLVED, that all responsibilities pertaining to the Apache

 

Incubator Joshua podling encumbered upon the Apache Incubator

 

Project are hereafter discharged.