from:"Alan Cabrera"

Re: [VOTE] Accept Gearpump into the Apache Incubator

2016-03-02 Thread Alan Cabrera

+1 (binding)


Regards,
Alan

> On Mar 1, 2016, at 4:53 PM, Andrew Purtell  wrote:
> 
> Greetings,
> 
> The discussion of the Gearpump proposal has concluded. Please vote to
> accept Gearpump into the Apache Incubator. I will leave this vote open for
> at least the next 72 hours and will aim to close it Monday the 7th of
> March, 2016 at midnight PT. Gearpump is a flexible, efficient, and scalable
> micro-service based real-time big data streaming engine. The text of the
> proposal is included below and is also available at
> https://wiki.apache.org/incubator/GearpumpProposal
> 
> [ ] +1 Accept Gearpump as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because ...
> 
> Note that while votes from Incubator PMC members are binding, all are most
> definitely welcome to vote!
> 
> I am +1 (binding).
> 
> Best regards,
> 
>   - Andy
> 
> -
> 
> = Gearpump Proposal =
> 
> === Abstract ===
> Gearpump is a flexible, efficient and scalable micro-service based
> real-time big data streaming engine developed by Intel Corporation which
> has been licensed by Intel under the Apache License 2.0.
> 
> === Proposal ===
> Gearpump is a reactive real-time streaming engine; completely based on the
> micro-service Actor model. Gearpump provides extremely high performance
> stream processing while maintaining millisecond latency message delivery.
> It enables reusable, composable flows or partial graphs that can be
> remotely deployed and executed in a diverse set of environments, including
> IoT edge devices. These flows may be deployed and modified at runtime -- a
> capability few real time streaming frameworks provide today.
> 
> The goal of this proposal is to incubate Gearpump as an Apache project in
> order to build a diverse, healthy, and self-governed open source community
> around this project.
> 
> === Background ===
> In past decade, there have been many advances within real-time streaming
> frameworks. Despite many advances, users of streaming frameworks often
> complain about flexibility, efficiency, and scalability. Gearpump endeavors
> to solve these challenges by adopting the micro-service Actor model. The
> Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
> actor is a message driven micro-service; actors are the basic building
> blocks of concurrent computation. By leveraging Actor Model’s location
> transparency feature,Gearpump allows a graph to be composed of several
> partial graphs, where, for example, some parts may be deployed to remote
> IoT edge devices, and other parts to a data center. This division and
> deployment model can be changed at runtime to adapt to a changing physical
> environment, providing extreme flexibility and elasticity in solving
> various ingestion and analytics problems. We’ve found Actors to be a much
> smaller computation unit compared with threads, where smaller usually means
> better concurrency, and potentially better CPU utilization.
> 
> === Rationale ===
> Gearpump tightly integrates and enhances the big data community of Apache
> projects. Intel believes Gearpump can bring benefits to the Apache
> community in a number of ways:
> 
> 1. Gearpump complements many existing Apache projects, in particular, those
> commonly found within the big data space. Users of this project are also
> users of other Apache projects, such as Hadoop ecosystem projects. It is
> beneficial to align these projects under the ASF umbrella. In real-time
> streaming, Gearpump offers some special features that are useful for Apache
> users, such as exactly-once processing with millisecond message level
> latency and dynamic DAGs that allow online topology modifications.
> 
> 2. Gearpump tightly integrates with Apache big data projects. It supports
> for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
> scheduling and Apache HDFS as the essential distributed storage system.
> 
> 3. The micro-service model of reusable flows that Gearpump has adopted is
> very unique, and it may become common in the future.Gearpump sets a good
> example about how distributed software can be implemented within a
> micro-service model.  An open project is of best interest to our users. By
> joining Apache, it will be a neutral infrastructure platform that will
> benefit everyone.
> 
> 4. The process and development philosophy of Apache will help Gearpump grow,
> and build a diverse, healthy, and self-governed open source community.
> 
> === Initial Goals ===
> 1. Migrate the existing codebase to Apache.
> 
> 2. Setup Jira, website and other development tools by following Apache best
> practices.
> 
> 3. Start the first release per Apache guidelines as soon as possible.
> 
> === Current Status ===
> Gearpump is hosted on Github. It has 1922 commits, 38284 line of code, and
> 31 major or minor releases, with release notes highlighting the changes for
> every release. It is licensed under

Re: [VOTE] Accept Geode into the Apache Incubator

2015-04-22 Thread Alan Cabrera

+1


Regards,
Alan

Sent from my iPhone

 On Apr 19, 2015, at 10:46 PM, Roman Shaposhnik r...@apache.org wrote:
 
 Following the discussion earlier in the thread:
   http://s.apache.org/Oxt
 
 I would like to call a VOTE for accepting Geode
 as a new incubator project.
 
 The proposal is available at:
https://wiki.apache.org/incubator/GeodeProposal
 and is also included at the bottom of this email.
 
 Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST
 
 [ ] +1 accept Geode in the Incubator
 [ ] ±0
 [ ] -1 because...
 
 Thanks,
 Roman.
 
 == Abstract ==
 Geode is a data management platform that provides real-time,
 consistent access to data-intensive applications throughout widely
 distributed cloud architectures.
 
 Geode pools memory (along with CPU, network and optionally local disk)
 across multiple processes to manage application objects and behavior.
 It uses dynamic replication and data partitioning techniques for high
 availability, improved performance, scalability, and fault tolerance.
 Geode is both a distributed data container and an in-memory data
 management system providing reliable asynchronous event notifications
 and guaranteed message delivery.
 
 == Proposal ==
 The goal of this proposal is to bring the core of Pivotal Software,
 Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software
 Foundation (ASF) in order to build a vibrant, diverse and
 self-governed open source community around the technology. Pivotal
 will continue to market and sell Pivotal GemFire based on Geode. Geode
 and Pivotal GemFire will be managed separately. This proposal covers
 the Geode source code (mainly written in Java), Geode documentation
 and other materials currently available on GitHub.
 
 While Geode is our primary choice for a name of the project, in order
 to facilitate PODLINGNAMESEARCH we have come up with two alternatives:
  * Haptic
  * FIG
 
 == Background ==
 GemFire is an extremely mature and robust product that can trace its
 legacy all the way back to one of the first Object Databases for
 Smalltalk: GemStone. The GemFire code base has been maintained by the
 same group of engineers as a closed source project. Because of that,
 even though the engineers behind GemFire are the de-facto knowledge
 leaders for distributed in-memory management, they have had little
 exposure to the open source governance process.The original
 company developing GemStone and GemFire was acquired by VMWare in 2010
 and later spun off as part of Pivotal Software in 2013. Today GemFire
 is used by over 600 enterprise customers. An example deployment
 includes China National Railways that uses Pivotal GemFire to run
 railway ticketing for the entire country of China with a 10 node
 cluster that manages 2 gigabytes hot data in memory, and 10 backup
 nodes for high availability and elastic scale.
 
 == Rationale ==
 Modern-day data management architectures require a robust in-memory
 data grid solution to handle a variety of use cases, ranging from
 enterprise-wide caching to real-time transactional applications at
 scale. In addition, as memory size and network bandwidth growth
 continues to outpace those of disk, the importance of managing large
 pools of RAM at scale increases. It is essential to innovate at the
 same pace and Pivotal strongly believes that in the Big Data space,
 this can be optimally achieved through a vibrant, diverse,
 self-governed community collectively innovating around a single
 codebase while at the same time cross-pollinating with various other
 data management communities. ASF is the ideal place to meet these
 ambitious goals.
 
 == Initial Goals ==
 Our initial goals are to bring Geode into the ASF, transition internal
 engineering processes into the open, and foster a collaborative
 development model according to the Apache Way. Pivotal plans to
 develop new functionality in an open, community-driven way. To get
 there, the existing internal build, test and release processes will be
 refactored to support open development.
 
 == Current Status ==
 Currently, the project code base is licensed for evaluation purposes
 and is available for download from Pivotal.io
 (https://network.pivotal.io/products/project-geode). The documentation
 and wiki pages are available as public GitHub repositories under
 Project Geode organization on GitHub
 (https://github.com/project-geode). Although Pivotal GemFire was
 developed as a proprietary, closed-source product, the internal
 engineering practices adopted by the development team lend themselves
 well to an open, collaborative and meritocratic environment.
 
 The Pivotal GemFire team has always focused on building a robust end
 user community of paying and non-paying customers. The existing
 documentation along with StackOverflow and other similar forums are
 expected to facilitate conversions between our existing users so as to
 transform them into an active community of Geode members, stakeholders
 and developers.

Re: [VOTE} Climate Model Diagnostic Analyzer

2015-04-19 Thread Alan Cabrera

+1

Sent from my iPhone

 On Apr 18, 2015, at 10:00 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 OK all, discussion has died down, we have 3 mentors, I think itâ€™s
 time to proceed to a VOTE.
 
 I am calling a VOTE now to accept the Climate Model Diagnostic
 Analyzer (CMDA) into the Apache Incubator. The VOTE is open for
 at least the next 72 hours:
 
 [ ] +1 Accept Apache Climate Model Diagnostic Analyzer into the Apache
 Incubator.
 [ ] +0 Abstain.
 [ ] -1 Donâ€™t accept Apache Climate Model Diagnostic Analyzer into the
 Apache Incubator
 becauseâ€¦
 
 Iâ€™ll try and close the VOTE out on Friday.
 
 Of course I am +1!
 
 P.S. the text of the latest wiki proposal is pasted below:
 
 Cheers,
 Chris
 
 
 = Apache ClimateModelDiagnosticAnalyzer Proposal =
 
 == Abstract ==
 
 The Climate Model Diagnostic Analyzer (CMDA) provides web services for
 multi-aspect physics-based and phenomenon-oriented climate model
 performance evaluation and diagnosis through the comprehensive and
 synergistic use of multiple observational data, reanalysis data, and model
 outputs.
 
 == Proposal ==
 
 The proposed web-based tools let users display, analyze, and download
 earth science data interactively. These tools help scientists quickly
 examine data to identify specific features, e.g., trends, geographical
 distributions, etc., and determine whether a further study is needed. All
 of the tools are designed and implemented to be general so that data from
 models, observation, and reanalysis are processed and displayed in a
 unified way to facilitate fair comparisons. The services prepare and
 display data as a colored map or an X-Y plot and allow users to download
 the analyzed data. Basic visual capabilities include 1) displaying
 two-dimensional variable as a map, zonal mean, and time series 2)
 displaying three-dimensional variableâ€™s zonal mean, a two-dimensional
 slice at a specific altitude, and a vertical profile. General analysis can
 be done using the difference, scatter plot, and conditional sampling
 services. All the tools support display options for using linear or
 logarithmic scales and allow users to specify a temporal range and months
 in a year. The source/input datasets for these tools are CMIP5 model
 outputs, Obs4MIP observational datasets, and ECMWF reanalysis datasets.
 They are stored on the server and are selectable by a user through the web
 services.
 
 === Service descriptions ===
 
 1. '''Two dimensional variable services'''
 
 * Map of two-dimensional variable:  This services displays a two
 dimensional variable as a colored longitude and latitude map with values
 represented by a color scheme. Longitude and latitude ranges can be
 specified to magnify a specific region.
 
 * Two dimensional variable zonal mean:  This service plots the zonal mean
 value of a two-dimensional variable as a function of the latitude in terms
 of an X-Y plot.
 
 * Two dimensional variable time series:  This service displays the average
 of a two-dimensional variable over the specific region as function of time
 as an X-Y plot.
 
 2. '''Three dimensional variable services'''
 
 * Map of a two dimensional slice of a three-dimensional variable:  This
 service displays a two-dimensional slice of a three-dimensional variable
 at a specific altitude as a colored longitude and latitude map with values
 represented by a color scheme.
 
 * Three dimensional zonal mean:  Zonal mean of the specified
 three-dimensional variable is computed and displayed as a colored
 altitude-latitude map.
 
 * Vertical profile of a three-dimensional variable:  Compute the area
 weighted average of a three-dimensional variable over the specified region
 and display the average as function of pressure level (altitude) as an X-Y
 plot.
 
 3. '''General services'''
 
 * Difference of two variables:  This service displays the differences
 between the two variables, which can be either a two dimensional variable
 or a slice of a three-dimensional variable at a specified altitude as
 colored longitude and latitude maps
 
 * Scatter and histogram plots of two variables:  This service displays the
 scatter plot (X-Y plot) between two specified variables and the histograms
 of the two variables. The number of samples can be specified and the
 correlation is computed. The two variables can be either a two-dimensional
 variable or a slice of a three-dimensional variable at a specific altitude.
 
 * Conditional sampling:  This service lets user to sort a physical
 quantity of two or dimensions according to the values of another variable
 (environmental condition, e.g. SST) which may be a two-dimensional
 variable or a slice of a three-dimensional variable at a specific
 altitude. For a two dimensional quantity, the plot is displayed an X-Y
 plot, and for a two-dimensional quantity, plot is displayed as a
 colored-map.
 
 
 == Background and Rationale ==
 
 The latest Intergovernmental Panel on Climate Change (IPCC) Fourth

Re: Do we need @ASFIncubator ?

2015-03-23 Thread Alan Cabrera

+1

Sent from my iPhone

 On Mar 23, 2015, at 2:05 PM, Roman Shaposhnik r...@apache.org wrote:
 
 Hi!
 
 while trying to spread the good news that the Groovy
 vote has passed, I've realized that we don't have
 a dedicate Incubator Twitter account.
 
 Question for all: should we leverage @TheASF for
 the incubator-level announcements or should we
 establish our own handle?
 
 WDYGT?
 
 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: [POLL] Using this list to discuss pTLP proposals, ok?

2015-03-22 Thread Alan Cabrera

I am very much in favor for provisional TLP's and direct-to-TLP's here at the 
Apache Software Foundation.

With that said I am very much against the noise here on our incubator lists and 
wiki.  We should really create a list in the wiki for this kind of endeavor. It 
really it should take place on members, since this is ultimately the purvey of 
the foundation members not the incubator, and a new wiki For general 
discussions should be made.

Just my two cents.

Sent from my iPhone

 On Mar 22, 2015, at 5:59 AM, Bertrand Delacretaz bdelacre...@apache.org 
 wrote:
 
 Hi,
 
 In the recent discussions about provisional TLPs and direct-to-TLP
 projects we're missing a public place where the proposals (board
 resolutions etc) for such projects are discussed and worked on.
 
 Are people ok with using this list and the Incubator wiki for those things?
 
 The Incubator PMC won't have a say in how those projects proceed, but
 as this is about creating new projects, and as a number of steps are
 similar to incoming or graduating podlings, I think working here makes
 sense.
 
 Thoughts?
 -Bertrand
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Groovy into the Apache Incubator

2015-03-19 Thread Alan Cabrera

+1

Sent from my iPad

 On Mar 18, 2015, at 11:55 PM, Roman Shaposhnik r...@apache.org wrote:
 
 Following the discussion earlier in the thread:
   http://s.apache.org/KWE
 
 I would like to call a VOTE for accepting Groovy
 as a new incubator project.
 
 The proposal is available at:
https://wiki.apache.org/incubator/GroovyProposal
 and is also included at the bottom of this email.
 
 Vote is open until at least Saturday, 21st March 2015, 23:59:00 PST
 
 [ ] +1 accept Groovy in the Incubator
 [ ] ±0
 [ ] -1 because...
 
 Thanks,
 Roman.
 
 == Abstract ==
 Groovy is an object-oriented programming language for the Java
 platform. It is a language with features similar to those of Python,
 Ruby, Java, Perl, and Smalltalk.
 Groovy, if accepted by Incubator, will be a first major programming
 language developed under the umbrella of Apache Software Foundation.
 
 == Proposal ==
 Groovy is a programming language for the Java platform. It is a
 primarily dynamic language with features similar to those of Python,
 Ruby, Perl, and Smalltalk. It also has optional static type checking
 and static compilation facilities. It can be used as a scripting
 language for the Java Platform or to write complete applications, is
 compiled to Java Virtual Machine (JVM) bytecode, and interoperates
 with other Java code and libraries. Groovy uses a Java-like
 curly-bracket syntax. Most Java code is also syntactically valid
 Groovy, although semantics may be different. Groovy has long been
 developed under an Apache License v2.0 under an open governance
 community management process. However, so far Groovy has been a
 project mostly sponsored by a single company. This proposal aims at
 bringing Groovy community under the umbrella of the Apache Software
 Foundation.
 
 It must be explicitly noted, that a few sister projects such as Groovy
 Eclipse and others (some of them hosted under
 https://github.com/groovy and listed at
 http://groovy-lang.org/ecosystem.html) are not covered by this
 proposal. It is possible that these other projects will be joining ASF
 either independently or as sub-projects of Apache Groovy in the
 future. For now, we are only proposing groovy-core.
 
 == Background ==
 Groovy 1.0 was released on January 2, 2007, and Groovy 2.0 in July,
 2012. Groovy 2.5 is planned for release in 2015. Groovy 3.0 is planned
 for release in 2016, with support for a new Meta Object Protocol.
 Since version 2, Groovy can also be compiled statically, offering type
 inference and performance very close to that of Java. Groovy 2.4 will
 be the last major release under Pivotal Software's sponsorship, which
 is scheduled to end on March 31, 2015.
 
 == Rationale ==
 Groovy is a pretty mature language. After 12 years of development, it
 has grown from being primarily a dynamic scripting language on the JVM
 to an optionally statically compiled language allowing the same
 performance level as Java applications. With the release of Groovy
 2.4, the language targets the largest pool of mobile developers with
 native Android support. Groovy has been integrated in a large number
 of applications, including well known open-source projects like
 Jenkins, Gradle, ElasticSearch, Spring and more.
 
 There are multiple alternative languages on the JVM: Scala, Clojure,
 Ceylon, Kotlin, JRuby, Golo and others but Groovy is the only one
 which has proved to be very easy to integrate with Java in both ways:
 Groovy code using Java code, but also Java code using Groovy code.
 Groovy even provides a joint compiler which allows interdependent Java
 and Groovy classes to compile together. Groovy also supports dynamic
 code generation, that is to say classes at runtime, making it a
 perfect fit for scripting. With a very lightweight and malleable
 syntax, it is also easy to build internal Domain Specific Languages
 (DSLs) which integrate smoothly within applications.
 
 Groovy provides a number of unique features, like builders (Java 8 has
 lambdas but still has syntactic overhead and no notion of delegate),
 AST transformations (compile-time metaprogramming) or type checking
 extensions (which allows the developer to bring the compiler to levels
 of type checking and type inference that go far beyond what other
 languages do). Groovy also provides powerful integration options and
 customizations which set it apart from other languages. Groovy is also
 unique in the way it allows the developer to choose between various
 paradigms without compromise: functional vs object-oriented,
 statically compiled vs dynamic, scripting vs applications, etc.
 
 Despite all those advantages, and the fact that Groovy is widely
 adopted (4.5 million downloads in 2014 for Groovy alone), only a few
 Apache projects include Groovy and not a lot of them leverage its full
 power. Some developers tend to choose Scala for example to build DSLs
 without even knowing that the learning curve is much easier with
 Groovy, or that they can leverage powerful type inference in

Re: Next steps for various proposals (mentor re-boot, pTLP, etc.)

2015-01-20 Thread Alan Cabrera


 On Jan 20, 2015, at 6:46 AM, Bertrand Delacretaz bdelacre...@apache.org 
 wrote:
 
 On Tue, Jan 20, 2015 at 3:35 PM, Alan D. Cabrera l...@toolazydogs.com 
 wrote:
 ...Isn’t it obvious what the above and IncubatorV2 proposal are about?  
 Consolidating
 like minded individuals into a new IPMC and shutting out the other 
 inconvenient
 members until they come to their senses”
 
 I don't buy that conspiracy theory, for me it's just very difficult to
 build consensus in the Incubator as the goal is much fuzzier than
 producing software.
 
 But maybe I'm too candid ;-)

I am not espousing a conspiracy theory; there is no secret cabal formed after 
an ApaceCon pub crawl. 

I too am being candid. I am merely providing an unvarnished distillation of 
what the proposals virtually are.

Garnering consensus is difficult here, in part because of the fuzziness you 
mention, but also because members have such different opinions as to what the 
Incubator function is and what it means to be an Apache project.

Under the above proposals, that necessarily messy, frustrating, exhausting, 
process of garnering consensus on the above thorny issues will not take place 
as philosophically compatible IPM v2 members turn out Apache projects that fit 
their view.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Incubator report sign-off

2015-01-05 Thread Alan Cabrera

This statement confuses the lack of active mentors with the sheer size of the
IPMC. The problem is not the size of the IPMC. The problem is that mentors are
not doing their jobs

Sent from my iPhone

On Jan 5, 2015, at 3:41 PM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:

Yep and let all from that 170+ person committee be tracked down for
responsibility. Talk about s fun activity it's simply not scalable

Sent from my iPhone

On Jan 5, 2015, at 1:08 PM, Ross Gardler (MS OPEN TECH)
ross.gard...@microsoft.com wrote:

But the board is not responsible for any actions resulting from those
reviews, the IPMC is.

Ross

-Original Message-
From: Mattmann, Chris A (3980) [mailto:chris.a.mattm...@jpl.nasa.gov]
Sent: Monday, January 5, 2015 9:31 AM
To: general@incubator.apache.org
Subject: Re: Incubator report sign-off

Itâ€™s not a pawning off to the board - the board is already responsible for
reviewing the IPMC report which includes *all of the same detail* that the
IPMC also .. reviews.

Cheers,
Chris

-Original Message-
From: Alan D. Cabrera l...@toolazydogs.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Monday, January 5, 2015 at 8:59 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: Incubator report sign-off

On Jan 5, 2015, at 8:22 AM, Roman Shaposhnik ro...@shaposhnik.org wrote:

On Mon, Jan 5, 2015 at 5:05 AM, Alan D. Cabrera
l...@toolazydogs.com
wrote:

On Dec 22, 2014, at 8:42 AM, Roman Shaposhnik r...@apache.org wrote:

1. get rid of IPMC altogether and move to the pTLP model

This is effectively an IPMC reboot. I donâ€™t really see anything
substantially different.

At this point, I'm convinced this is the only fruitful path forward,
the rest is a shell game with responsibility. See the other thread.

3. patch the current process with starting to drop the mentors from
the project who don't sign off. This will essentially serve
as a heartbeat for mentors (now, in my opinion it'll quickly
deteriorate into mindless tick-offs -- but at least it does
not harm).

How is it that a mentor became an IPMC member and do such an
unethical thing such as a mindless tick-off?

We're talking about human being here. The one who never ever cut
corners in his life can cast the first stone.

I think that you misunderstood my rhetorical question. It is my
experience/understanding that if a mentor makes an effort to review
reports/releases then this mentor is actually doing a good job at it.
It is my experience/understanding that the overwhelming problem is that
mentors simply go MIA and do nothing at all.

I am in favor of #3 since it holds mentors accountable. #1 is simply a
washing of our hands and pawning the problem off on the board simple
because some of us are unwilling to do uncomfortable things.

Regards,
Alan

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

B CB
[ X ÜšX KK[XZ[
[ \ [
][ X ÜšX P[ X ]Ü‹ \X K Ü™ B ÜˆY][Û˜[ [X[ K[XZ[
[ \ [
Z[[ X ]Ü‹ \X K Ü™ B

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Ð¢ÐÐ¥FòVç7V'67–RÂRÖÖ–Ã¢vVæWÂ×Vç7V'67–T–æ7VF÷æ6†Ræ÷pÐ¤f÷FF—F–öæÂ6öÖÖæG2ÂRÖÖ–Ã¢vVæWÂÖ†VÇ–æ7VF÷æ6†Ræ÷pÐ

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

Re: Podlings should be in charge of their mentors (was: Incubator report sign-off)

2015-01-05 Thread Alan Cabrera

A champion is merely a mentor who has publicly committed to being an active 
mentor, in some significant capacity, of a podling.  

The creation of such a role is symptomatic of a dysfunctional organization 
where responsibility and accountability has been diluted so much it's not at 
all clear who will actually follow through with their responsibilities.

IMO, all that's needed is two active mentors.  To get that we need to hold 
mentors accountable.  If we do that then things become simpler and we can get 
rid of champions and shepherds; two role that were created to fill the gaps 
left by unaccountable mentors.

 On Jan 5, 2015, at 3:41 PM, Benson Margulies bimargul...@gmail.com wrote:
 
 Back in 2013, I suggested asking the Champion to accept a very clear
 level of reporting responsibility: to write a sentence or two _every
 month_ or find someone else to do it. That's one person whom I wanted
 to ask to sign up, for the duration of an incubation, to pay enough
 attention to be able to report a basic heartbeat.
 
 ?
 
 
 On Mon, Jan 5, 2015 at 3:57 PM, Upayavira u...@odoko.co.uk wrote:
 
 
 On Mon, Jan 5, 2015, at 08:18 PM, jan i wrote:
 On 5 January 2015 at 20:06, Alan D. Cabrera l...@toolazydogs.com wrote:
 
 
 On Jan 5, 2015, at 10:26 AM, jan i j...@apache.org wrote:
 
 On Monday, January 5, 2015, Alan D. Cabrera l...@toolazydogs.com
 javascript:_e(%7B%7D,'cvml','l...@toolazydogs.com'); wrote:
 
 
 On Jan 5, 2015, at 9:21 AM, Roman Shaposhnik ro...@shaposhnik.org
 wrote:
 
 The tracking part is easy, though. What's difficult is the part
 that would require us to do something with poddlings put
 on hold. Unless we come up with clear exit criteria for
 this new state -- I don't think we're solving any real problems
 here.
 
 There’s no silver bullet here, if a podling cannot whip up a mentor it’s
 because:
 the podling is not popular and should probably be retired anyway, being
 put on hold will provide impetus for the podling to seek out a new venue
 there are not enough mentors
 There is no way to magically solve the latter.
 
 
 You mean popular within the pool of mentors (IPMC), the project can still
 be popular on several other scales.
 
 I’m not speaking of popularity of mentors; I regret that choice of words.
 I am stating that active and healthy podlings seem to have no trouble
 attracting active mentors.
 
 The converse seems to be true.  Unhealthy podlings seem to attract mentors
 who have signed up out of pity and subsequently go MIA.
 I agree with the last part, I still have to see mentors volunteer for
 small
 active and healthy projects which might not be main road. Of course it
 depends on how active and healthy is defined, but as an example my little
 project Corinthia barely managed to get 2 mentors, while in the same time
 span we got 3 committers.
 
 
 Before anyone replies, I understand this is not a hard and fast rule but
 an imperfect qualitative observation on my part.
 
 Anyway, active and responsible mentors will eventually get to all podlings.
 
 I might lack experience, but why do more active mentors guarantee that
 the
 podling will be a better TLP ?
 
 I’m not sure who’s making that assertion.
 Well its because I cannot see why a podling need more than 1 active
 mentor
 at all timeshaving multiple is fine, to cover each other, but it
 should
 not take more than 1 mentor to learn a podling, what it needs to
 understand. The suggestion implicit says 2 mentors is the minimum needed
 for at podling to become a successful TLP.
 
 
 
 We try to solve the problem of mentors not being active but adding more
 volume. I don't believe that is the right cure.
 
 We’re not adding volume.  The volume is already there.  We’re just making
 the state of affairs more explicit and transparent and adding culpability
 for MIA mentors.
 Do we have a rule today that a podling needs at least 2 active mentors
 (if
 we have that, then we would not have a problem with sign offs, or a lot
 of
 dead podlings), at least I have not seen itthat is what I mean by
 adding volume.
 
 If just 1 mentor is active and sign off the reports, then I do not see
 the
 problem.
 
 
 
 
 I do agree with bernard that it is the podling that should ask for
 helpbut the IPMC should solve it.,
 
 Yes, it should help solve problems but if there are no mentors available
 there are no mentors available.
 Then the IPMC should not have accepted the podling in the first place!
 
 It is simply not fair to make the life of a podling, depending on whether
 or not we have mentors available (REMARK after accepting the proposal) !
 If
 the podling have a healthy community and are active, we cannot and should
 not close it down, just because we have a mentor problem.
 
 To me telling a podling it cannot grow its community nor make releases,
 is
 the same as closing it down.
 
 Jan,
 
 From an idealistic perspective, you are completely right. Apache should,
 once a project has been accepted, provide the support needed.

Re: Incubator report sign-off

2015-01-05 Thread Alan Cabrera

Yes which is why I am proposing for less change than what others are proposing.

Sent from my iPhone

 On Jan 5, 2015, at 5:07 PM, Ross Gardler (MS OPEN TECH) 
 ross.gard...@microsoft.com wrote:
 
 Careful... most mentors do a great job. The problem is when all mentors fade 
 away (which as volunteers they are entitled to do) and the IPMC doesn't 
 notice.
 
 Ross
 
 Microsoft Open Technologies, Inc.
 A subsidiary of Microsoft Corporation
 
 -Original Message-
 From: Alan Cabrera [mailto:l...@toolazydogs.com] 
 Sent: Monday, January 5, 2015 4:50 PM
 To: general@incubator.apache.org
 Subject: Re: Incubator report sign-off
 
 This statement confuses the lack of active mentors with the sheer size of the 
 IPMC.  The problem is not the size of the IPMC. The problem is that mentors 
 are not doing their jobs
 
 Sent from my iPhone
 
 On Jan 5, 2015, at 3:41 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Yep and let all from that 170+ person committee be tracked down for 
 responsibility. Talk about s fun activity it's simply not scalable
 
 Sent from my iPhone
 
 On Jan 5, 2015, at 1:08 PM, Ross Gardler (MS OPEN TECH) 
 ross.gard...@microsoft.com wrote:
 
 But the board is not responsible for any actions resulting from those 
 reviews, the IPMC is.
 
 Ross
 
 -Original Message-
 From: Mattmann, Chris A (3980) [mailto:chris.a.mattm...@jpl.nasa.gov]
 Sent: Monday, January 5, 2015 9:31 AM
 To: general@incubator.apache.org
 Subject: Re: Incubator report sign-off
 
 ItÃ¢â‚¬â„¢s not a pawning off to the board - the board is already 
 responsible for reviewing the IPMC report which includes *all of the same 
 detail* that the IPMC also .. reviews.
 
 Cheers,
 Chris
 
 
 
 -Original Message-
 From: Alan D. Cabrera l...@toolazydogs.com
 Reply-To: general@incubator.apache.org
 general@incubator.apache.org
 Date: Monday, January 5, 2015 at 8:59 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: Incubator report sign-off
 
 
 On Jan 5, 2015, at 8:22 AM, Roman Shaposhnik ro...@shaposhnik.org wrote:
 
 On Mon, Jan 5, 2015 at 5:05 AM, Alan D. Cabrera 
 l...@toolazydogs.com
 wrote:
 
 On Dec 22, 2014, at 8:42 AM, Roman Shaposhnik r...@apache.org wrote:
 
 1. get rid of IPMC altogether and move to the pTLP model
 
 This is effectively an IPMC reboot.  I donÃ¢â‚¬â„¢t really see anything 
 substantially different.
 
 At this point, I'm convinced this is the only fruitful path 
 forward, the rest is a shell game with responsibility. See the other 
 thread.
 
 3. patch the current process with starting to drop the mentors from
the project who don't sign off. This will essentially serve
as a heartbeat for mentors (now, in my opinion it'll quickly
   deteriorate into mindless tick-offs -- but at least it does 
 not harm).
 
 How is it that a mentor became an IPMC member and do such an 
 unethical thing such as a mindless tick-off?
 
 We're talking about human being here. The one who never ever cut 
 corners in his life can cast the first stone.
 
 I think that you misunderstood my rhetorical question.  It is my 
 experience/understanding that if a mentor makes an effort to review 
 reports/releases then this mentor is actually doing a good job at it.
 It is my experience/understanding that the overwhelming problem is 
 that mentors simply go MIA and do nothing at all.
 
 I am in favor of #3 since it holds mentors accountable.  #1 is 
 simply a washing of our hands and pawning the problem off on the 
 board simple because some of us are unwilling to do uncomfortable things.
 
 
 Regards,
 Alan
 
 
 
 
 
 
 
 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 B 
 C
 B  [  X  ÃœÅ¡X KK[XZ[  [ \ [ ][  X  ÃœÅ¡X P[  X ]Ãœâ€¹ \X K Ãœâ„¢ 
 B  
 ÃœË†Y][Ã›Ëœ[  [X[  K[XZ[  [ \ [ Z[[  X ]Ãœâ€¹ \X K Ãœâ„¢ B
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 ÃÂ¢Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’Ã’
 ÃÃÂ¥FÃ² 
 VÃ§7V'67â€“RÃ‚RÃ–Ã–â€“ÃƒÂ¢vVÃ¦WÃ‚Ã—VÃ§7V'67â€“Tâ€“Ã¦7VFÃ·Ã¦6â€
  RÃ¦Ã·pÃÂ¤fÃ·FF
 â€”Fâ€“Ã¶Ã¦Ã‚6Ã¶Ã–Ã–Ã¦G2Ã‚RÃ–Ã–â€“ÃƒÂ¢vVÃ¦WÃ‚Ã–â€ 
 VÃ‡â€“Ã¦7VFÃ·Ã¦6â€ RÃ¦Ã·pÃ
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 Ð¢ÐÐ¥FòVç7V'67–RÂRÖÖ–Ã¢vVæWÂ×Vç7V'67–T–æ7VF÷æ6†Ræ÷pÐ¤f÷FF—F–öæÂ6öÖÖæG2ÂRÖÖ–Ã¢vVæWÂÖ

Re: Board reports - public or private

2015-01-04 Thread Alan Cabrera

Board reports are always public, as are a project's/podling's discussions about 
what should go in their report.

It's the mentors job to clear up any confusion there may be for a podling 
writing its first report.

Sent from my iPhone

 On Jan 4, 2015, at 5:25 AM, John D. Ament johndam...@apache.org wrote:
 
 Hi all,
 
 Just wondering, should we tell podlings that a board report is considered
 public while in draft and can be discussed on their dev list, or its
 private and should be discussed on their private list?
 
 I had always assumed public, but could hear someone say its private.
 
 John

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

Re: Board reports - public or private

2015-01-04 Thread Alan Cabrera

Imnsho, that is a poor practice.

Sent from my iPhone

 On Jan 4, 2015, at 7:18 AM, Mark Struberg strub...@yahoo.de wrote:
 
 I know many projects (TLP) which discuss/draft the report in private and only 
 later make it public.
 
 LieGrue,
 strub
 
 
 
 
 
 On Sunday, 4 January 2015, 16:10, Alan Cabrera l...@toolazydogs.com wrote:
 Board reports are always public, as are a project's/podling's
 discussions about what should go in their report.
 
 It's the mentors job to clear up any confusion there may be for a podling 
 writing its first report.
 
 Sent from my iPhone
 
 
 On Jan 4, 2015, at 5:25 AM, John D. Ament johndam...@apache.org
 wrote:
 
 Hi all,
 
 Just wondering, should we tell podlings that a board report is considered
 public while in draft and can be discussed on their dev list, or its
 private and should be discussed on their private list?
 
 I had always assumed public, but could hear someone say its private.
 
 John
 
 -
 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: Proposals - wiki required?

2014-11-23 Thread Alan Cabrera


 On Nov 23, 2014, at 8:40 AM, jan i j...@apache.org wrote:
 
 I dont want to criminalize anybody, but on the other hand I would like to
 have 1 common place where to look for accepted proposals.
 
 Having the proposals, at least after acceptance, in one place should be
 beneficial to everyone, so how about wording it as a strong suggestion.

Let's look at how the proposal process works. It starts with a proposal email.  
We don't troll a particular web space looking for new proposals.  Dictating 
that the proposals start in one place needlessly adds rules that don't solve 
any problems.

As for storing them in one place after acceptance, why? 

Adding strongly worded shoulds dilutes guidelines and adds to the reading 
homework of new podlings that will already have the good sense to use a wiki, 
or something better that us old folk haven't thought of.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wiki Access

2014-07-10 Thread Alan Cabrera


On Jul 10, 2014, at 12:30 AM, Nick Burch apa...@gagravarr.org wrote:

 On Wed, 9 Jul 2014, Rob Weir wrote:
 On Tue, Jul 8, 2014 at 5:11 AM, Svante Schubert
 Can somebody please give me (user svanteschubert) access to the Wiki 
 
 Anyone?
 
 Karma granted.
 
 (I guess everyone else was like me and off on holiday for a few days! We do 
 normally manage to turn these round quicker)
 
 Nick

Does one have to be a infrastructure team member to grant access or can IPMC 
members provide that?


Regards,
Alan


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

Re: [VOTE] Graduate Apache Tez from Apache Incubator to TLP

2014-07-01 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On Jun 30, 2014, at 9:16 PM, Hitesh Shah hit...@apache.org wrote:

 Hello folks
 
 Tez entered incubation in February, 2013. Since then, we have made progress 
 towards graduation[1]. The Tez community recently voted positively towards 
 graduation[2] with 27 +1s.
 Of the 27, there were 5 IPMC votes from our mentors:
   - Alan Gates
- Arun C. Murthy
- Chris Mattman
- Chris Douglas
- Jakob Homan
 
 Now, I would like to ask the IPMC to vote for the graduation of Apache Tez.
 
 Please VOTE to indicate if Apache Tez is ready to graduate as a Top Level 
 Project. The board resolution is included below. 
 
 [ ] +1 Graduate Apache Tez as a TLP
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Tez as a TLP because…
 
 The vote will remain open for 72 hours. 
 
 thanks
 — Hitesh Shah ( on behalf of Tez PPMC )
 
 [1] 
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccfc4fef8.16337a%25chris.a.mattm...@jpl.nasa.gov%3E
 [2] 
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccaoapips7pjs_6hinkwk0uv0hnnrydqcg639dpf9vojeuto9...@mail.gmail.com%3E
 
 Board Resolution:
 --
 X. Establish the Apache Tez Project
 
 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 Tez Project, be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further
 
 RESOLVED, that the Apache Tez Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficient cluster management, resource isolation
 and sharing across distributed applications; and be it further
 RESOLVED, that the office of Vice President, Apache Tez 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 Tez Project, and to have primary responsibility for
 management of the projects within the scope of responsibility
 of the Apache Tez 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 Tez Project:
 
 * Alan Gates ga...@apache.org
 * Arun C. Murthy acmur...@apache.org
 * Ashutosh Chauhan hashut...@apache.org
 * Bill Graham billgra...@apache.org
 * Bikas Saha bi...@apache.org
 * Chris Douglas cdoug...@apache.org
 * Chris Mattmann mattm...@apache.org
 * Daryn Sharp da...@apache.org
 * Devaraj Das d...@apache.org
 * Gopal Vijayaraghavan gop...@apache.org
 * Gunther Hagleitner gunt...@apache.org
 * Hitesh Shah hit...@apache.org
 * Jitendra Pandey jiten...@apache.org
 * Jason Lowe jl...@apache.org
 * Jakob Homan jgho...@apache.org
 * Julien Le Dem jul...@apache.org
 * Kevin Wilfong kevinwilf...@apache.org
 * Mike Liddell mlidd...@apache.org
 * Mohammad Kamrul Islam kam...@apache.org
 * Namit Jain na...@apache.org
 * Nathan Roberts nrobe...@apache.org
 * Owen O’Malley omal...@apache.org
 * Rajesh Balamohan rbalamo...@apache.org
 * Robert Evans bo...@apache.org
 * Rohini Palaniswamy roh...@apache.org
 * Siddharth Seth ss...@apache.org
 * Tassapol Athiapinya tassap...@apache.org
 * Thomas Graves tgra...@apache.org
 * Tom White tomwh...@apache.org
 * Vikram Dixit vik...@apache.org
 * Vinod Kumar Vavilapalli vino...@apache.org
 
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hitesh Shah be
 appointed to the office of Vice President, Apache Tez, 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 Tez Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Tez podling; and be it further
 
 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Tez 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
 


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

Re: [VOTE] Release of Apache MRQL 0.9.2 incubating (RC2)

2014-06-25 Thread Alan Cabrera

Awesome!  Thanks!!

We need just one more vote!


Regards,
Alan

On Jun 25, 2014, at 1:12 AM, Justin Mclean jus...@classsoftware.com wrote:

 Hi,
 
 +1 binding
 
 I checked:
 - vote looks good
 - incubating in artefact name
 - signatures and hashes all good
 - DISCLAIMER good
 - NOTICE and LICENSE correct
 - all source files have Apache headers
 - no binary files in source package
 - can compile from source
 
 I didn't run any test as I was not sure how to.
 
 Some things you may want to fix in future releases
 - add apache to artefact name
 - there a few test files (.txt, .xml, .tbl, .json) missing Apache headers
 - basic installation / compile / test instructions added to README
 
 Thanks,
 Justin
 
 -
 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 Storm 0.9.2-incubating

2014-06-22 Thread Alan Cabrera

I'm looking at the release vote result and I'm seeing only one binding vote 
from a IPMC member.  Am I comparing the vote results against the wrong IPMC 
roster?

http://people.apache.org/committers-by-project.html#incubator-pmc


Regards,
Alan
P.S. Apologies if this is a duplicate email.


On Jun 19, 2014, at 11:37 AM, P. Taylor Goetz ptgo...@apache.org wrote:

 This is a call for a vote to release Apache Storm (incubating) version 0.9.2. 
 This will be the 2nd release of Apache Storm.
 
 A vote was held on the developer mailing list, and passed with 3 binding +1 
 votes, no 0 votes, and no -1 votes.
 
 Release vote:
 
 http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c5045a732-a2f6-4a12-a57f-c330d9e9e...@gmail.com%3e
 
 Release vote result:
 
 http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c0f81f852-eeb9-4025-80ab-1f0e92470...@gmail.com%3e
 
 The full list of changes in this release:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob;f=CHANGELOG.md;h=95024dad910d12eb3e14772f46a2d28675669b61;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087
 
 The tag to be voted upon is v0.9.2-incubating:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=24d4a14de310cbbfebdc4a50d8cc9d86f9943087;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087
 
 The specific source archive being voted upon can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz
 
 Other release files, signatures and digests can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/
 
 The release artifacts are signed with the key available here:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
 
 The staging repository for this release can be found here:
 
 https://repository.apache.org/content/repositories/orgapachestorm-1008
 
 The generated reports and documentation for this release can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/report/
 
 Please vote on releasing this package as Apache Storm 0.9.2-incubating.
 
 This vote will be open for at least 72 hours.
 
 [ ] +1 Release this package as Apache Storm 0.9.2-incubating
 [ ]  0 No opinion
 [ ] -1 Do not release this package because …
 
 Thanks,
 Taylor

Re: [VOTE] Release of Apache MRQL 0.9.2 incubating (RC2)

2014-06-22 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On Jun 19, 2014, at 11:54 PM, Leonidas Fegaras fega...@cse.uta.edu wrote:

 Hello,
 This is a call for a vote on Apache MRQL 0.9.2 incubating.
 Apache MRQL is a query processing and optimization system for
 large-scale, distributed data analysis, built on top of Apache Hadoop,
 Apache Hama, and Apache Spark. This is our second release.
 A vote was held on the MRQL developer mailing list and it passed with
 four +1 PPMC votes, no -1 votes, and no 0 votes (see the vote thread
 [1] and result thread [2]), and now requires a vote on this list.
 The vote will be open for at least 72 hours and passes if a majority
 of at least three +1 IPMC votes are cast.
 
 [ ] +1 Release this package as Apache MRQL 0.9.2-incubating
 [ ] -1 Do not release this package because ...
 
 The release tarballs, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.2-incubating-RC2/
 The release candidate consists of the following source distribution archives:
 - mrql-dist-0.9.2-incubating-src.[tar.gz|zip]
  SHA1 of TGZ: 9209 735B CAE2 D431 71BE  EB6F 985B 07F7 B0A3 E4A6
  SHA1 of ZIP: 180F 0CE1 D09E 9B21 A08F  1BED 495E 8BB2 6486 CAF9
 You can compile the sources using 'mvn clean install'.
 In addition, the following supplementary binary distributions are
 provided for user convenience at the same location:
 - mrql-dist-0.9.2-incubating-bin.[tar.gz|zip]
  SHA1 of TGZ: AC77 F97F 0C3C FACA C312  8C68 50B5 5474 DBFE 93C1
  SHA1 of ZIP: F552 021C 2FF0 7343 5098  C16B 18B8 1AF8 9820 9675
 
 A staged Maven repository is available for review at:
 https://repository.apache.org/content/repositories/orgapachemrql-1001/
 
 The release candidate has been signed through the key 798764F1 in:
 http://www.apache.org/dist/incubator/mrql/KEYS
 
 The release candidate is based on the sources tagged with
 MRQL-0.9.2-incubating-RC2 at:
 https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=f80a1e6fcb1e2a31063e568508ada3d9ef3466e3
 
 The list of fixed issues:
 https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=blob_plain;f=RELEASE_NOTES;hb=f80a1e6fcb1e2a31063e568508ada3d9ef3466e3
 
 To learn more about Apache MRQL, please visit:
 http://wiki.apache.org/mrql/
 Thanks,
 Leonidas Fegaras
 
 [1] http://markmail.org/message/eiqz44qovjy6f6sl
 [2] http://markmail.org/message/eo3d64jx24v6oir2
 
 
 -
 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 Storm 0.9.2-incubating

2014-06-22 Thread Alan Cabrera

There are some Thrift generated files that don't seem to have the AL prepended. 
 I'm not sure if that's important since the files were automatically generated; 
imo, it's not.

+1 binding


Regards,
Alan

On Jun 19, 2014, at 11:37 AM, P. Taylor Goetz ptgo...@apache.org wrote:

 This is a call for a vote to release Apache Storm (incubating) version 0.9.2. 
 This will be the 2nd release of Apache Storm.
 
 A vote was held on the developer mailing list, and passed with 3 binding +1 
 votes, no 0 votes, and no -1 votes.
 
 Release vote:
 
 http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c5045a732-a2f6-4a12-a57f-c330d9e9e...@gmail.com%3e
 
 Release vote result:
 
 http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c0f81f852-eeb9-4025-80ab-1f0e92470...@gmail.com%3e
 
 The full list of changes in this release:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob;f=CHANGELOG.md;h=95024dad910d12eb3e14772f46a2d28675669b61;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087
 
 The tag to be voted upon is v0.9.2-incubating:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=24d4a14de310cbbfebdc4a50d8cc9d86f9943087;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087
 
 The specific source archive being voted upon can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz
 
 Other release files, signatures and digests can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/
 
 The release artifacts are signed with the key available here:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
 
 The staging repository for this release can be found here:
 
 https://repository.apache.org/content/repositories/orgapachestorm-1008
 
 The generated reports and documentation for this release can be found here:
 
 http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/report/
 
 Please vote on releasing this package as Apache Storm 0.9.2-incubating.
 
 This vote will be open for at least 72 hours.
 
 [ ] +1 Release this package as Apache Storm 0.9.2-incubating
 [ ]  0 No opinion
 [ ] -1 Do not release this package because …
 
 Thanks,
 Taylor

Re: [VOTE] Release Apache Storm 0.9.2-incubating

2014-06-22 Thread Alan Cabrera

Only IPMC members' votes are binding until the podling is out of the incubator.
This release will need at least 3 of those votes. However, any IPMC +1 votes
will carry over to this current vote.

If I counted correctly, this release has one from the earlier vote plus mine.
I think it needs one more IPMC member's vote.

Regards,
Alan

On Jun 22, 2014, at 1:47 PM, P. Taylor Goetz ptgo...@gmail.com wrote:

Alan,

That was the result of the PPMC vote on the dev@ list. Arvind is a mentor.

-Taylor

On Jun 22, 2014, at 2:51 PM, Alan Cabrera l...@toolazydogs.com wrote:

I'm looking at the release vote result and I'm seeing only one binding vote
from a IPMC member. Am I comparing the vote results against the wrong IPMC
roster?

http://people.apache.org/committers-by-project.html#incubator-pmc

Regards,
Alan
P.S. Apologies if this is a duplicate email.

On Jun 19, 2014, at 11:37 AM, P. Taylor Goetz ptgo...@apache.org wrote:

This is a call for a vote to release Apache Storm (incubating) version
0.9.2. This will be the 2nd release of Apache Storm.

A vote was held on the developer mailing list, and passed with 3 binding +1
votes, no 0 votes, and no -1 votes.

Release vote:

http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c5045a732-a2f6-4a12-a57f-c330d9e9e...@gmail.com%3e

Release vote result:

http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c0f81f852-eeb9-4025-80ab-1f0e92470...@gmail.com%3e

The full list of changes in this release:

https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob;f=CHANGELOG.md;h=95024dad910d12eb3e14772f46a2d28675669b61;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087

The tag to be voted upon is v0.9.2-incubating:

https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=24d4a14de310cbbfebdc4a50d8cc9d86f9943087;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087

The specific source archive being voted upon can be found here:

http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz

Other release files, signatures and digests can be found here:

http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/

The release artifacts are signed with the key available here:

https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The staging repository for this release can be found here:

https://repository.apache.org/content/repositories/orgapachestorm-1008

The generated reports and documentation for this release can be found here:

http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/report/

Please vote on releasing this package as Apache Storm 0.9.2-incubating.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 0.9.2-incubating
[ ] 0 No opinion
[ ] -1 Do not release this package because …

Thanks,
Taylor

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

Re: [VOTE] Graduate Apache Celix as Top Level Project

2014-06-22 Thread Alan Cabrera

+1 binding


Regards,
Alan

On Jun 19, 2014, at 7:26 AM, Alexander Broekhuis a.broekh...@gmail.com wrote:

 Hi All,
 
 Since entering Incubation in November 2010, the Celix podling been working
 towards graduation. The community has grown, releases have been made and
 new committers have been added.
 Over the last couple of months all items on the checklist for graduation
 have been ticked of [1].
 This resulted in a, positive, vote on te dev list of Celix itself [2]. Also
 the namesearch has been performed [3].
 As far as we can tell the project status is up to date [4], and Celix is
 ready for graduation.
 
 After the discussion in the [DISCUSS] thread on [5], some changes were made
 to the PMC list to have enough members for binding votes etc.
 
 Now I'd like to ask the IPMC to vote for the graduation of Celix.
 
 Please cast your vote:
 
 [ ] +1 Graduate the Apache Celix podling from Apache Incubator as a TLP
 [ ] +0 Indifferent to the graduation status of Apache Celix podling
 [ ] -1 Reject graduation of Apache Celix podling from Apache Incubator
 because ...
 
 The vote will be open for 72 hours, after which I will tally and post the
 results.
 
 Thanks in advance,
 
 Alexander Broekhuis
 (PPMC member of Apache Celix)
 
 [1]: http://incubator.apache.org/guides/graduation.html#checklist
 [2]: http://markmail.org/thread/7y3a2l6qqm56cvud
 [3]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-50
 [4]: http://incubator.apache.org/projects/celix.html
 [5]: http://markmail.org/thread/7udzxyd7ey2nyqsr
 
 
 X. Establish the Apache Celix Project
 
   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 a native implementation of the OSGi
   specification.
 
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Celix Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further
 
   RESOLVED, that the Apache Celix Project be and hereby is
   responsible for the creation and maintenance of software
   related to a native implementation of the OSGi
   specification;
   and be it further
 
   RESOLVED, that the office of Vice President, Apache Celix 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 Celix Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Celix 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 Celix Project:
 
 * Alexander Broekhuis   abroekh...@apache.org
 * Pepijn Noltes  pnol...@apache.org
 * Bjoern Petribpe...@apache.org
 * Erik Jansman ejans...@apache.org
 * Marcel Offermans   ma...@apache.org
 * Roman Shaposhnik r...@apache.org
 * Konstantin Boudnik c...@apache.org
 
 
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alexander Broekhuis
   be appointed to the office of Vice President, Apache Celix, 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 initial Apache Celix PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Celix Project; and be it further
 
   RESOLVED, that the Apache Celix Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Celix podling; and be it further
 
   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Celix podling encumbered upon the Apache Incubator
   Project are hereafter discharged.
 
 -- 
 Met vriendelijke groet,
 
 Alexander Broekhuis


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

Re: [VOTE] Release Apache Storm 0.9.2-incubating

2014-06-22 Thread Alan Cabrera


On Jun 22, 2014, at 10:30 PM, Alan Cabrera l...@toolazydogs.com wrote:

 If I counted correctly, this release has one from the earlier vote plus mine. 
  I think it needs one more IPMC member's vote.

NM, I just read Marvin's email about the new release process that I was unaware 
of.  :)

Regards,
Alan

Re: [VOTE] Retire the S4 podling

2014-06-14 Thread Alan Cabrera

+1 - binding

Regards,
Alan

On Jun 13, 2014, at 11:36 AM, Joe Brockmeier j...@zonker.net wrote:

 Hi all,
 
 Per recent discussions on general@[1] and s4-dev@ [2], I went ahead and
 called for a VOTE on the S4 dev@ mailing list [3] about retiring the
 podling. That VOTE has passed with no -1s and 4 (binding) +1s from the
 podling PMC/committers. (S4 only has committers, and doesn't distinguish
 between PPMC/committer.)
 
 We didn't get a weigh-in from all mentors/PPMC on the retirement VOTE,
 so I'm going ahead and asking for a vote here.
 
 This VOTE will be open for at least 72 hours. Please indicate (binding)
 or (non-binding) when casting your VOTE.
 
 +1 [ ] Yes, I am in favor of retiring S4 from the Apache Incubator.
 +0 [ ]
 -1 [ ] No, I am not in favor of retiring S4 because...
 
 Note that we have one IPMC vote from Patrick already.
 
 [1] http://s.apache.org/7Gz
 [2] http://s.apache.org/ig
 [3] http://s.apache.org/OAU
 -- 
 Joe Brockmeier
 j...@zonker.net
 Twitter: @jzb
 http://www.dissociatedpress.net/
 
 -
 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 Optiq into the incubator

2014-05-12 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On May 9, 2014, at 11:03 AM, Ashutosh Chauhan hashut...@apache.org wrote:

 [ ] +1 Accept Optiq into the Incubator
 [ ] +0 Indifferent to the acceptance of Stratosphere
 [ ] -1 Do not accept Optiq because ...

Re: [VOTE] Graduate Apache Stratos as a TLP

2014-05-03 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On May 1, 2014, at 8:03 PM, Suresh Marru sma...@apache.org wrote:

 Please VOTE to indicate if Apache Stratos is ready to graduate as a Top Level 
 Project. The board resolution is included below. 
 
 [ ] +1 Graduate Apache Stratos as a TLP
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Stratos as a TLP because…
 
 Cheers,
 Suresh

Re: [VOTE] Accept Brooklyn into the Incubator

2014-04-28 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On Apr 28, 2014, at 6:49 AM, Chip Childers chipchild...@apache.org wrote:

 Based on the previous discussion of accepting Brooklyn into the Apache
 Incubator as a podling, I'd like to call a vote for this now.
 
 [ ] +1 Accept Brooklyn into the Incubator
 [ ] +/-0 Indifferent to the acceptance of Brooklyn
 [ ] -1 Do not accept Brooklyn because...
 
 The proposal can be found here:
 https://wiki.apache.org/incubator/BrooklynProposal
 
 (For the IPMC members, I believe we typically lock the proposal page
 making it read-only during the voting.  I'm not sure how to do this, or
 if I'm remembering correctly.  Can someone clarify?  I'll watch that
 page to be sure there are no changes during the voting process.)
 
 -chip
 
 -
 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: [RESULT][VOTE] Graduation of Apache Olingo from the Incubator

2014-03-22 Thread Alan Cabrera

Congrats all!

Here is where I sign off as a mentor.  

Again, congratulations, you have an awesome community here.


Regards,
Alan

On Mar 20, 2014, at 5:18 AM, Klevenz, Stephan stephan.klev...@sap.com wrote:

 Dear all,
 
 Maybe you have received Apache board meeting report already. Apache Olingo
 now a TLP :-)
 
 Thank you all for the great support from Apaches incubator. That Olingo is
 now a TLP is also your result.
 
 Olingo has learned a lot from incubation and is now happy to continue on
 the Apache Way as TLP
 
 
 
 Greetings,
 Stephan
 (VP Apache Olingo)
 
 
 
 
 On 17.03.14 10:27, Florian Müller f...@apache.org wrote:
 
 Hi all,
 
 The vote has passed with three binding +1 votes, no +0, and no -1
 votes.
 
 +1 votes:
 
 * Dave Fisher
 * Alan Cabrera
 * Florian Müller
 
 I will ask the board to add the resolution to the agenda of the next
 board meeting.
 
 
 Thanks!
 
 Florian
 
 
 
 Hi all,
 
 The Apache Olingo community has VOTEd to graduate from the incubator
 [1][2].
 
 Apache Olingo entered the Incubator in July 2013, has done two
 releases,
 has added new contributors, received code contributions, and has an
 active community.
 
 Please find the proposed board resolution below.
 
 
 Please VOTE below on the graduation of Apache Olingo from the
 Incubator. The graduation resolution is pasted below.
 I'll leave the VOTE open for at least 72 hours:
 
 [ ] +1 Graduate Apache Olingo podling from Apache Incubator
 [ ] +0 Indifferent to the graduation status of Apache Olingo podling
 [ ] -1 Reject graduation of Apache Olingo podling from Apache
 Incubator
 because ...
 
 
 
 My vote is +1 (binding).
 
 
 Thanks,
 
 Florian
 
 
 
 [1] http://s.apache.org/olingo-graduation-vote
 [2] http://s.apache.org/olingo-graduation-vote-result
 
 
 Resolution:
 
   Establish the Apache Olingo Project
 
   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 providing an implemention of the
   OASIS OData (Open Data Protocol) specifications, in
   server and client form.
 
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Olingo Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further
 
   RESOLVED, that the Apache Olingo Project be and hereby is
   responsible for the creation and maintenance of software
   related to providing an implemention of the OASIS OData
   (Open Data Protocol) specifications, in server and client
   form; and be it further
 
   RESOLVED, that the office of Vice President, Olingo 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 Olingo Project, and to have primary
 responsibility
   for management of the projects within the scope of
   responsibility of the Apache Olingo 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 Olingo Project:
 
 * Florian Mueller   f...@apache.org
 * Dave Fisher   w...@apache.org
 * Christian Amend   chri...@apache.org
 * Francesco Chicchiriccòilgro...@apache.org
 * Jens Huesken  jhues...@apache.org
 * Michael Bolz  m...@apache.org
 * Stephan Klevenz   sklev...@apache.org
 * Tamara Boehm  tbo...@apache.org
 * Challen Hechall...@apache.org
 * Chandan V A   chanda...@apache.com
 * Eduard Koller edua...@apache.com
 
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Klevenz
   be appointed to the office of Vice President, Olingo, 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 initial Apache Olingo PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Olingo Project; and be it further
 
   RESOLVED, that the Apache Olingo Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Olingo podling; and be it further
 
   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Olingo podling encumbered upon the Apache Incubator
   Project are hereafter

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

2014-03-15 Thread Alan Cabrera

All the binding votes made at Onlingo’s original graduation vote carry over to 
this one but I’ll still add my

+1 - binding


Regards,
Alan


On Mar 13, 2014, at 2:17 AM, Florian Müller f...@apache.org wrote:

 Hi all,
 
 The Apache Olingo community has VOTEd to graduate from the incubator [1][2].
 
 Apache Olingo entered the Incubator in July 2013, has done two releases,
 has added new contributors, received code contributions, and has an
 active community.
 
 Please find the proposed board resolution below.
 
 
 Please VOTE below on the graduation of Apache Olingo from the
 Incubator. The graduation resolution is pasted below.
 I'll leave the VOTE open for at least 72 hours:
 
 [ ] +1 Graduate Apache Olingo podling from Apache Incubator
 [ ] +0 Indifferent to the graduation status of Apache Olingo podling
 [ ] -1 Reject graduation of Apache Olingo podling from Apache Incubator
 because ...
 
 
 
 My vote is +1 (binding).
 
 
 Thanks,
 
 Florian
 
 
 
 [1] http://s.apache.org/olingo-graduation-vote
 [2] http://s.apache.org/olingo-graduation-vote-result
 
 
 Resolution:
 
   Establish the Apache Olingo Project
 
   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 providing an implemention of the
   OASIS OData (Open Data Protocol) specifications, in
   server and client form.
 
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Olingo Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further
 
   RESOLVED, that the Apache Olingo Project be and hereby is
   responsible for the creation and maintenance of software
   related to providing an implemention of the OASIS OData
   (Open Data Protocol) specifications, in server and client
   form; and be it further
 
   RESOLVED, that the office of Vice President, Olingo 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 Olingo Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Olingo 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 Olingo Project:
 
 * Florian Mueller   f...@apache.org
 * Dave Fisher   w...@apache.org
 * Christian Amend   chri...@apache.org
 * Francesco Chicchiriccòilgro...@apache.org
 * Jens Huesken  jhues...@apache.org
 * Michael Bolz  m...@apache.org
 * Stephan Klevenz   sklev...@apache.org
 * Tamara Boehm  tbo...@apache.org
 * Challen Hechall...@apache.org
 * Chandan V A   chanda...@apache.com
 * Eduard Koller edua...@apache.com
 
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Klevenz
   be appointed to the office of Vice President, Olingo, 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 initial Apache Olingo PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Olingo Project; and be it further
 
   RESOLVED, that the Apache Olingo Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Olingo podling; and be it further
 
   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Olingo 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: Tool to generate disclaimer, NOTICE, etc. files

2014-02-11 Thread Alan Cabrera

The goal that I’m hoping to realistically attain is to have tooling 
automatically generate these files, thus alleviating a lot of scut work done by 
podlings and mentors.  Maybe not a realistic goal but a pretty good dream.  :)

On to the details:

On Feb 8, 2014, at 7:42 PM, sebb seb...@gmail.com wrote:

 On 8 February 2014 16:49, Alan Cabrera l...@toolazydogs.com wrote:
 Do you think it would be helpful if we had a tool that generated these 
 files?  It could work like a command line wizard that prompts the person for 
 licensing information and then generates a valid disclaimer, notice, etc. 
 files.
 
 AIUI the disclaimer file is the same for every project - only the
 project name changes.
 Seems unnecessary to automate this, though it should be trivial to implement.

Agreed, though it would be handy for podlings that are starting out, imo.

 The NOTICE file is much harder to automate, as it depends on knowing
 what is actually going to be shipped and reading and interpreting all
 the relevant licenses.
 However it might be possible to create a sort of expert system that
 asked the right questions and guided the user to create the NOTICE
 file.

That’s my thinking.  We would have relevant metadata on 3rd party projects

 If this is a good idea, what files should we generate?  Currently, all I can 
 think of is disclaimer and notice.
 
 Maybe it could add the info into the project's DOAP file.  If we worked out 
 the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file 
 and insert these files into the correct places in the distributions.  Apache 
 RAT could also use this info as well.
 
 The DOAP could certainly be used to create the DISCLAIMER.
 
 It seems wrong to include any dependency information in the DOAP.
 
 Dependencies must be present somewhere in the build scripts, however
 even in Maven (which has very structured info) it's not at all easy to
 determine which dependencies are actually included in the release
 artifacts (and remember that source and binary artifacts may need
 different NOTICE files)
 
 Note also that some source files may require attribution in the NOTICE file.
 These won't be documented in any build system; the info has to be
 added to the NOTICE file manually when the code is added to SCM.
 
 WDYT?
 
 Non-trivial; maintaining the meta-data needed to accurately generate
 the NOTICE file is likely to require more effort than writing the
 NOTICE file itself.
 
 
 Regards,
 Alan
 
 
 -
 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: Tool to generate disclaimer, NOTICE, etc. files

2014-02-11 Thread Alan Cabrera

Whoops, accidentally prematurely sent my reply.

The goal that I’m hoping to realistically attain is to have tooling 
automatically generate these files, thus alleviating a lot of scut work done by 
podlings and mentors. Maybe not a realistic goal but a pretty good dream.  :)

On to the details:

On Feb 8, 2014, at 7:42 PM, sebb seb...@gmail.com wrote:

 On 8 February 2014 16:49, Alan Cabrera l...@toolazydogs.com wrote:
 Do you think it would be helpful if we had a tool that generated these 
 files?  It could work like a command line wizard that prompts the person for 
 licensing information and then generates a valid disclaimer, notice, etc. 
 files.
 
 AIUI the disclaimer file is the same for every project - only the
 project name changes.
 Seems unnecessary to automate this, though it should be trivial to implement.

Agreed, though it would be handy for podlings that are starting out, imo.

 The NOTICE file is much harder to automate, as it depends on knowing
 what is actually going to be shipped and reading and interpreting all
 the relevant licenses.
 However it might be possible to create a sort of expert system that
 asked the right questions and guided the user to create the NOTICE
 file.

That’s my thinking.  The tool would ask various questions about their project.  
Maybe even introspect maven POMs, gradle files, etc. to collect information.  
Then generate appropriate NOTICE files.  

I think that the real work would be creating and maintaining a database of 
licenses for 3rd party products.  This could be incrementally created by the 
above tool.

 If this is a good idea, what files should we generate?  Currently, all I can 
 think of is disclaimer and notice.
 
 Maybe it could add the info into the project's DOAP file.  If we worked out 
 the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file 
 and insert these files into the correct places in the distributions.  Apache 
 RAT could also use this info as well.
 
 The DOAP could certainly be used to create the DISCLAIMER.
 
 It seems wrong to include any dependency information in the DOAP.
 
 Dependencies must be present somewhere in the build scripts, however
 even in Maven (which has very structured info) it's not at all easy to
 determine which dependencies are actually included in the release
 artifacts (and remember that source and binary artifacts may need
 different NOTICE files)

All the more reason to having tooling take care of this.

 Note also that some source files may require attribution in the NOTICE file.
 These won't be documented in any build system; the info has to be
 added to the NOTICE file manually when the code is added to SCM.
 
 WDYT?
 
 Non-trivial; maintaining the meta-data needed to accurately generate
 the NOTICE file is likely to require more effort than writing the
 NOTICE file itself

Yeah but that effort is amortized over many projects and release reviewers.


Regards,
Alan

Re: Tool to generate disclaimer, NOTICE, etc. files

2014-02-11 Thread Alan Cabrera


On Feb 8, 2014, at 10:47 PM, Ted Dunning ted.dunn...@gmail.com wrote:

 On Sat, Feb 8, 2014 at 7:42 PM, sebb seb...@gmail.com wrote:
 
 WDYT?
 
 Non-trivial; maintaining the meta-data needed to accurately generate
 the NOTICE file is likely to require more effort than writing the
 NOTICE file itself.
 
 
 
 Actually, this sounds like a case where the effort for any individual
 project outweighs the benefit of saving the time, but the total effort
 across many projects would make the effort somewhat worth while.  In
 particular, something that enhances the communication between projects and
 between the author of the dependency and the users of that dependency would
 be very helpful.
 
 As such, this sounds like a great thing to add to maven.  If it provided me
 with a way to look at all my dependencies and examine my notices file for
 missing acknowledgments, that would be helpful.  Moreover, if there were a
 way for the community of users to upload sample acknowledgements and for
 the owners of such packages to reject or accept these acknowledgments, this
 would crowdsource the effort of approval.

Maven and other build tools.  If we had a canonical database then people would 
be free to create any kind of tooling they wished.

 My guess is that since getting NOTIFICATIONS right is a largely one shot
 deal, it wouldn't be enough appeal to encourage somebody to actually
 implement the system, but it would certainly make one's life easier in
 small installments.

That’s the predicament of a tool smith.


Regards,
Alan


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

Re: Tool to generate disclaimer, NOTICE, etc. files

2014-02-11 Thread Alan Cabrera


On Feb 10, 2014, at 12:48 PM, Marvin Humphrey mar...@rectangular.com wrote:

 On Sat, Feb 8, 2014 at 8:49 AM, Alan Cabrera l...@toolazydogs.com wrote:
 Do you think it would be helpful if we had a tool that generated these
 files?  It could work like a command line wizard that prompts the person for
 licensing information and then generates a valid disclaimer, notice, etc.
 files.
 
 If this is a good idea, what files should we generate?  Currently, all I can
 think of is disclaimer and notice.
 
 Maybe it could add the info into the project's DOAP file.  If we worked out
 the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file
 and insert these files into the correct places in the distributions.  Apache
 RAT could also use this info as well.
 
 WDYT?
 
 I concur with sebb on the extreme challenges of auto-generating NOTICE --
 which is a shame because I'd really love it if the Incubator could benefit
 when you're inspired to write tooling.

Yeah, when we were sorting things out in a podling the idea hit me in the head.

 One thing I think we could use is a tool which parses mbox archives in
 people.apache.org:/home/apmail/ and generates statistics:
 
 *   Total emails sent per list (a measure of activity)
 *   Unique addresses participating (a measure of diversity)
 *   Emails sent by Mentors (a measure of Mentor engagement)

Yeah, I’m working on that as we speak.  I have a project called Panopticon in 
Apache Labs.  I’m currently working on mailing list moderator tools that allow 
moderation at the command line.  Go check it out! 

 We expend a lot of volunteer energy on shepherding each month, and I think
 such an automated tool could help to free up some of that energy for other
 tasks.  There are two main functions for shepherding:
 
 1.  Alert the IPMC to podlings which have gone adrift.
 2.  Provide an outsider view.
 
 (I'd add a #3: being exposed to new communities benefits the shepherd, but
 that varies by individual.)
 
 I think that purpose #1 could largely be accomplished using email stats.
 
 I don't know if this is something you'd feel motivated to work on, but I
 thought it was worth mentioning because your original proposal would save time
 and energy and so would this.
 
 Marvin Humphrey
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


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

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

2014-02-11 Thread Alan Cabrera

+1 - binding

Regards,
Alan

On Feb 10, 2014, at 8:27 PM, Chris Mattmann mattm...@apache.org wrote:

 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
 


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

Re: Tool to generate disclaimer, NOTICE, etc. files

2014-02-11 Thread Alan Cabrera


On Feb 11, 2014, at 9:01 AM, Marvin Humphrey mar...@rectangular.com wrote:

 On Tue, Feb 11, 2014 at 7:42 AM, Alan Cabrera l...@toolazydogs.com wrote:
 
 One thing I think we could use is a tool which parses mbox archives in
 people.apache.org:/home/apmail/ and generates statistics:
 
 *   Total emails sent per list (a measure of activity)
 *   Unique addresses participating (a measure of diversity)
 *   Emails sent by Mentors (a measure of Mentor engagement)
 
 Yeah, I'm working on that as we speak.  I have a project called Panopticon
 in Apache Labs.  I'm currently working on mailing list moderator tools that
 allow moderation at the command line.  Go check it out!
 
 What would be ideal is if Panopticon could generate these stats and then the
 Incubator's clutch2report.py script could embed them in the report wiki
 template for each month.  I see that Panopticon is envisioned as a web UI, but
 for our purposes it would probably need to run on a cron on people.apache.org
 and cache the stats, because reading all those mboxes on the fly each request
 would be too expensive.
 
 Is that feature request compatible with your work?


A lot of data would have to be collected incrementally in the background.

All data that Panopticon collects will be available via a JSON REST API.


Regards,
Alan


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

Tool to generate disclaimer, NOTICE, etc. files

2014-02-08 Thread Alan Cabrera

Do you think it would be helpful if we had a tool that generated these files?  
It could work like a command line wizard that prompts the person for licensing 
information and then generates a valid disclaimer, notice, etc. files.

If this is a good idea, what files should we generate?  Currently, all I can 
think of is disclaimer and notice.

Maybe it could add the info into the project's DOAP file.  If we worked out the 
kinks then we could create sbt/gradle/mvn plugins to read the DOAP file and 
insert these files into the correct places in the distributions.  Apache RAT 
could also use this info as well.

WDYT?


Regards,
Alan


-
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

2014-02-01 Thread Alan Cabrera

+1


Regards,
Alan

On Jan 31, 2014, at 6:04 PM, Matei Zaharia matei.zaha...@gmail.com wrote:

 The Apache Spark community has VOTEd to graduate from the Apache incubator 
 (vote thread: http://s.apache.org/kq, discussion 
 thread:http://s.apache.org/aEQ).
 
 I’m now calling an official IPMC VOTE to make this happen as well. Here’s the 
 community tally:

Re: ApacheCon Denver CFP

2014-01-25 Thread Alan Cabrera

There was a question on a podling as to whether developers on podlings could 
submit proposals about their project.  Can they or can’t they?


Regards,
Alan


On Jan 24, 2014, at 1:38 PM, Marvin Humphrey mar...@rectangular.com wrote:

 Hi everyone,
 
 ApacheCon Denver will take place April 7-9, 2014.  The call-for-proposals
 went out on Tuesday:
 
  http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
 
 The CFP closes on February 1 -- one week from tomorrow -- so get those
 proposals in!
 
 Marvin Humphrey
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


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

Re: [DISCUSS] jbatch impl @Apache?

2013-08-26 Thread Alan Cabrera

Is there enough interest to generate an active community for this?  Would it 
make more sense to do this work under Geronimo or TomEE?


Regards,
Alan


On Aug 26, 2013, at 7:01 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:

 Hi
 
 As you probably know JavaEE 7 proposes a new spec called JBatch (aka JSR
 352).
 
 I'd love to see an implementation @Apache.
 
 There is ATM only one implementation (spring-batch doesn't pass the full
 TCKs): the RI (done by IBM).
 
 AFAIK they doesn't aim to create a community about this spec but their
 implementation is under the license Apache v2 and starting to implement it
 from scratch i started to get something very close to them (i just started
 but seeing my classes so close i decided to stop my impl from scratch and
 see if forking wouldn't be a better/easier solution).
 
 Personally my plan would be to fork their code and clean/update it and
 create a community around it.
 
 About it i have some questions:
 1) does it sound good?
 2) any interested people?
 3) how to process exactly?
 
 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*


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

Re: [PROPOSAL] Creation of the Incubator Ombudsman

2013-07-31 Thread Alan Cabrera


On Jul 30, 2013, at 8:44 AM, Bertrand Delacretaz bdelacre...@apache.org wrote:

 On Tue, Jul 30, 2013 at 5:55 AM, Marvin Humphrey mar...@rectangular.com 
 wrote:
 ...Bertrand was skeptical about an ASF-wide ombud, but didn't raise any 
 objection
 to an Incubator-specific position.
http://s.apache.org/NAa
 ...
 
 Just laziness on my part...what I said there also applies to an
 Incubator ombudsman, I'll repeat it here: I don't think we need it -
 people should feel
 free to contact people that they trust (IPMC members, mentors, ASF
 members) privately if there's a need, and not having someone elected
 in the ombudsman role means people are free to talk to whoever *they*
 think will help.


An ombudsman is there when all the normal processes don't work.  It alleviates 
an organization from from having to heavily codify what to do in all manner of 
situations, thus keeping things simple.

I'll note that most of those who seem to think that the position is not needed 
are those who are well established and well connected in the ASF community.

I'll also mention a point I made a while back, sometimes it's better to have an 
ombudsman look into things rather than a random ASF member.


Regards,
Alan


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

Re: [VOTE] Accept Olingo proposal as an incubating project

2013-07-01 Thread Alan Cabrera

+1 binding

Regards,
Alan

On Jul 1, 2013, at 3:38 AM, Florian Müller f...@apache.org wrote:

 Hi all,
 
 I'd like to call a VOTE for acceptance of Olingo into the Apache incubator.
 
 The proposal is pasted at the bottom on this email.
 The corresponding wiki page is: 
 http://wiki.apache.org/incubator/OlingoProposal
 
 [ ] +1 Accept Olingo into the Apache incubator
 [ ] +0 Don't care.
 [ ] -1 Don't accept Olingo into the incubator because...
 
 +1 from me (binding)
 
 I'll close the VOTE next Sunday.
 
 
 Thanks,
 
 Florian
 
 
 
 = Apache Olingo Proposal =
 
 === Abstract ===
 
 Apache Olingo is a generic Java language implementation of the OData 2.0 
 specification which will serve as a code base for the upcoming OASIS OData 
 specification.
 
 === Proposal ===
 
 The Open Data Protocol (OData) [1] is a Web protocol for querying and 
 updating data that provides a way to unlock your data and free it from silos 
 that exist in applications today. OData does this by applying and building 
 upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and 
 JSON to provide access to information from a variety of applications, 
 services, and stores.
 
 The Apache Olingo is a library which enables developers to implement OData 
 producers and OData consumers. Basic principles of the library are to provide 
 an OData 2.0 specification compliant OData Library, enhancements shall be 
 possible in a compatible manner, have a clear separation between Core and 
 API, to provide an option to build extensions on top. This library should be 
 base for implementing future releases of the specification.
 
 === Background ===
 
 OData was originally developed by Microsoft and is released in a version 2.0 
 under an Open Specification Promise [2]. A lot of companies did show 
 interests in this protocol, used it in products and gave feedback back to 
 Microsoft. This joined effort resulted in a new release OData 3.0 in 2012, 
 this version became the basis for the OASIS technical committee [3] which is 
 currently working on a new version of the specification. This OASIS standard 
 release is expected this year.
 
 The initial Java code of this project was developed by a development team 
 that had already experience with other OData 2.0 and 3.0 implementations at 
 SAP AG. The current code base implements OData 2.0 and because of this 
 version is widely used it is a good starting point to build an open source 
 community for the OData standard.
 
 The current code also comes up with an implementation of an OData sample 
 service. On the one side this is an example for users which want to use the 
 library to expose their own data and on the other side it illustrates how 
 implemented features work.
 
 Additionally, the code base includes an extension which is called JPA 
 processor. With this extension it is easy to expose any JPA persistence model 
 via OData protocol without a lot of coding.
 
 === Rationale ===
 
 More software vendors moving to OData means more choice for customers who 
 will be able to use different implementations. For the standard to succeed, 
 however, ensuring interoperability is paramount: in order to manage an ever 
 growing context and leverage the enormous portability and interoperability 
 issues that a globally adopted standard brings, it is necessary to think 
 about how to make the related ecosystem healthy and sustainable. Successful 
 modern standards are driven by:
 
 Clear documentation, built iteratively with continuous feedback from 
 stakeholders
 A clearly defined compatibility process, enforced by tools that allow to 
 gauge how implementations can be compatible and interoperable
 Accurate compliance criteria, documented in writing as well as in actual 
 testing code that measure how tools and libraries are able to interoperate
 A sample implementation to clear up potential doubts and ensure that the 
 standard can actually be implemented in real life scenarios
 The above mentioned pieces are able to make the development activity, towards 
 an OData implementation, easier and more successful. Having an healthy 
 ecosystem will ensure a smoother implementation process, more compliant 
 products, and ultimately, a wider adoption of the standard.
 
 The OData ecosystem has been successful in creating and documenting early 
 versions of the standard, yet it might potentially lack two very important 
 aspects, that is a exhaustive implementation of the complete protocol that 
 can be used productively and to ensure interoperability. As much as such 
 artifacts can be developed independently by any OData proponent, the value of 
 having a neutral party as a steward of actual code is to be considered. The 
 Apache Software Foundation has been playing this kind of role for many years, 
 and can provide the perfect environment to foster contributions on the OData 
 theme with a great amount of expertise.
 
 === Initial Goals ===
 
 Implement OData 2.0, make it final and

Re: personal expectations for ombudsman role

2013-06-30 Thread Alan Cabrera


On Jun 30, 2013, at 7:42 AM, Joe Schaefer joe_schae...@yahoo.com wrote:

 Now that things have settled down a bit,
 I'd like to talk about some of the things
 I'm looking for out of the ombudsman post.
 
 1) proactively solicits opinions of exiting podlings
about their experiences in the form of interviews
and surveys.
 
 2) make anonymized results of (1) available to the IPMC
on a regular basis.
 
 3) provides advocacy and facilitates solutions for
committers who report issues with their podling's
mentors.

I might change 3 to state:

provides advocacy and facilitates solutions for podling, and IPMC members, who 
report issues that cannot normally be solved through normal established 
processes.

I thought it would be good to extend the help to anyone related to the 
Incubator and be clear that the problems the ombudsman would work to resolve 
would be extraordinary issues and that most, if not all, problems would be 
solved through normal established processes.

 That's pretty much it- what are your expectations
 for the ombudsman role?


Nice and simple.  I like it.


Regards,
Alan


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

Re: [DISCUSSION] Apache Olingo next steps

2013-06-28 Thread Alan Cabrera


On Jun 28, 2013, at 6:43 AM, Florian Müller f...@apache.org wrote:

 Hi,
 
 About two weeks ago, Stephan presented the Apache Olingo (OData) proposal [1].
 There has been a bit of a discussion about the name and the diversity of the 
 initial committers. The name has been changed from OData to Olingo and one 
 new initial committer from a different company has been added. We assume that 
 the topic will attract a diverse community over time.
 
 Can anyone think of a reason not to move forward with a vote?

While these are all good things to do, none of those issues needed to be 
resolved before the vote.  They just needed to be attended to before the 
podling graduates.

It should be ok to start the vote.


Regards,
Alan


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

Re: [VOTE] Release Curator 2.1.0-incubating

2013-06-28 Thread Alan Cabrera

+1 - binding

Regards,
Alan

On Jun 26, 2013, at 8:12 PM, Jordan Zimmerman randg...@apache.org wrote:

 Hello,
 
 This is a vote for the release of Apache Curator, version 2.1.0-incubating. 
 
 This has been voted on via the d...@curator.incubator.apache.org mailing 
 list and now requires a vote on @general.
 
 2 IPMC votes have already been cast on the vote held on dev@curator:
 
 +1 (PPMC / binding) 
 * Patrick Hunt
 * Luciano Resende
 
 There were also 2 non-binding votes:
 
 +1
 * Jordan Zimmerman
 * Eric Tschetter
 
 *** Please download, test and vote within 3 working days
 
 Note that we are voting upon the source (tag), binaries are provided for 
 convenience.
 
 Link to release notes:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425version=12324401
 
 Staging repo:
 https://dist.apache.org/repos/dist/dev/incubator/curator/2.1.0-incubating/
 
 Binary artifacts:
 https://repository.apache.org/content/repositories/orgapachecurator-041/
 
 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-curator.git;a=tag;h=apache-curator-2.1.0-incubating
 
 Curator's KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/incubator/curator/KEYS
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 Thank you!
 


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

Re: [PROPOSAL] Creation of the Incubator Ombudsman

2013-06-19 Thread Alan Cabrera

I would prefer to use well known names for well known roles.  Ombudsman is a 
roll that's been around for quite a while and the person filling that role for 
the ASF will be doing roughly the same thing as ombudsman in other 
organizations.

With that said, I will agree that if everything is running fine, the ombudsman 
is pretty much watching Oprah re-runs.  Hopefully we will all work hard so this 
person will have the time to catch up.  ;)

However, I will point out that my proposal has come about from concrete 
personal experience and the experiences that others have personally related to 
me.  I will also point out that it seems to me that those who are opposed or, 
at best, lukewarm to the idea are well established and well connected 
individuals in the ASF sphere.


Regards,
Alan



On Jun 18, 2013, at 10:50 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote:

 Hello,
 
 Why one would need an additional alias? Existing questions are sent to
 general@ or dev@community or (please add here), and one in the superhero
 role should timely answer them or facilitate an answer. [Complex question]
 tag in the subject line should be sufficient, or just no answer to some
 mail for 72 hours.
 
 If titles are important, we can simply assign nice titles to guys who
 answer to 10 of these complex issues.
 
 Maybe some discussion on facilitation means can be useful to avoid calling
 the guy impolite.
 
 I have one particular problem to deal with. New projects which come outside
 of Apache, cannot find Apache champion. The request is too wide to reach
 someones ear. One possibe way to address it is to assign an eco-champion to
 the new project who performs the project evaluation. The champion comes
 from the Apache project of the same area. Sometimes we may end up with
 community merges by going this way.
 19.06.2013 3:03 пользователь Ross Gardler rgard...@opendirective.com
 написал:
 
 On 18 June 2013 23:53, Joe Schaefer joe_schae...@yahoo.com wrote:
 Why so much reluctance to just honor the request such as it is
 instead of looking for different ways of modifying it to taste?
 
 ISSUE 03 at work I think - perhaps it is my fault for thinking aloud
 about how the role might also help solve a different problem from the
 one it was originally designed to solve. Maybe I set the wrong tone
 for discussion. Lets forget that.
 
 Please just go ahead and do it the way you are suggesting. There is no
 harm. The worst that can happen is someone sends an email to the alias
 and there is no response. The next worst is that nobody ever uses it.
 In either case we will eventually reverse this step.
 
 And please also go ahead with your bill of rights - I'll comment in
 that thread in a moment.
 
 Ross
 
 -
 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: [PROPOSAL] Creation of the Incubator Ombudsman

2013-06-17 Thread Alan Cabrera


On Jun 17, 2013, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote:

 A paradox:
 
 The VP is not supposed to exercise authority in normal circumstances.
 Projects are supposed to have mentors that advocate for them. If a
 project comes 'to the ombudsman', whether that's the VP or not, what
 can this person do? All they can do is bring the matter to the
 community. If it's sensitive enough, to private@. The mentors can and
 should be doing this.
 
 So, if you ask me, this is just another way to avoid the problem of
 mentor-shortage.

Unless the problem is with an over active mentor or absentee/problem VP.

An ombudsman frees the Incubator from having to enumerate and codify every 
single circumstance where things go wrong and what would the official remedy 
be.  The ombudsman would be the go to person when podlings are having problems 
w/ the management that everyone on this thread seems to think should be the 
point people to begin with.


Regards,
Alan


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

Re: [PROPOSAL] Creation of the Incubator Ombudsman

2013-06-16 Thread Alan Cabrera


On Jun 15, 2013, at 10:52 AM, Joseph Schaefer joe_schae...@yahoo.com wrote:

 This is a suggestion that has come up in the past, and the typical 
 counter-argument is that this is something the chair needs to provide 
 themselves.
 
 Sent from my iPhone

The usual reason for an ombudsman is to have a safe third party to bring up 
issues up privately.  Podling members may feel too intimidated to complain to 
mentors/IPMC chairs to complain.  Maybe the complaint may be an absentee, or 
problem, mentor or chair.  One never knows.


Regards,
Alan

Re: [PROPOSAL] Creation of the Incubator Ombudsman

2013-06-16 Thread Alan Cabrera

I think that it would be a great idea to have an ASF wide ombudsman instead.

There's been a few times where I've been personally asked to watch the goings 
on in another project by a committer, or ASF member, to provide an outside 
opinion as to what's going on, only to receive the ire of the project that's 
being watched.  I'd much rather refer the concerned person to a ombudsman.



Regards,
Alan


On Jun 16, 2013, at 1:26 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote:

 Let me add that a TLP sometimes get confused when it faces a problem. :-)
 
 Why these problem solving superheroes should limit themselves to the
 incubator?
 15.06.2013 19:53 пользователь Alan Cabrera a...@toolazydogs.com написал:
 
 
 Problem: podlings are confused on where to go when there's a problem.
 
 Cause: we seem to collect/handle/organize problems in an ad hoc manner
 and sometimes mentors are the problem.
 
 Solution: we create an elected Incubator Ombudsman.
 
 
 Regards,
 Alan
 
 
 -
 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: [PROPOSAL] Creation of the Incubator Ombudsman

2013-06-16 Thread Alan Cabrera

Not a lot of power.  Just a designated safe person to bring issues up with.  I 
trust the relevant, empowered, parties in the ASF to work with the ombudsman to 
resolve the issues in a confidential safe manner.
  

Regards,
Alan

On Jun 16, 2013, at 10:41 AM, Joe Schaefer joe_schae...@yahoo.com wrote:

 Yeah I get that, but I'm wondering what sort of power we'd
 impart to the position besides information gathering.  It
 might make an interesting complementary position to the
 chair that's more directly focused on the Incubator as it
 presents itself to podlings, which is something we recently
 discussed in relation to the recent chair vote.
 
 
 - Original Message -
 From: Alan Cabrera l...@toolazydogs.com
 To: general@incubator.apache.org
 Cc: 
 Sent: Sunday, June 16, 2013 1:36 PM
 Subject: Re: [PROPOSAL] Creation of the Incubator Ombudsman
 
 
 On Jun 15, 2013, at 10:52 AM, Joseph Schaefer joe_schae...@yahoo.com 
 wrote:
 
 This is a suggestion that has come up in the past, and the typical 
 counter-argument is that this is something the chair needs to provide 
 themselves.
 
 Sent from my iPhone
 
 The usual reason for an ombudsman is to have a safe third party to bring up 
 issues up privately.  Podling members may feel too intimidated to complain 
 to 
 mentors/IPMC chairs to complain.  Maybe the complaint may be an absentee, or 
 problem, mentor or chair.  One never knows.
 
 
 Regards,
 Alan
 
 
 -
 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 Stratos proposal as an incubating project

2013-06-15 Thread Alan Cabrera

+1 binding


Regards,
Alan

On Jun 14, 2013, at 2:49 PM, Ross Gardler rgard...@opendirective.com wrote:

 I would like to invite the IPMC vote to accept the Stratos proposal [1].
 
 I want to clarify that this vote is for the Stratos project to enter
 the incubator as a standard podling under the existing incubation
 policy. The acceptance or otherwise of the probationary TLP idea is a
 separate issue that will be explored during the first month of
 incubation, potentially resulting in a further IPMC vote.
 
 This vote is *only* for accepting the Stratos project as a podling.
 
 [ ] +1 Accept the Stratos project as an incubating project
 [ ] +0
 [ ] -1 Do not accept the Stratos project as an incubating project
 because... (provide reason)
 
 It's late on Friday evening here in the UK. I'll let this vote run
 well into next week to allow for the weekend.
 
 Thank you for your votes.
 Ross
 
 -
 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: Incubator reorg ideas: sub-groups per technology?

2013-06-15 Thread Alan Cabrera


On Jun 15, 2013, at 7:16 AM, Upayavira u...@odoko.co.uk wrote:

 I think there's merit in the idea of multiple, smaller incubators, so
 long as it is set up in a way that doesn't involve prospective podlings
 playing the incubators against each other.

Can you provide detail on what you mean by prospective podlings playing the 
incubators against each other?  I'm not sure what that means.

 Smaller groups, with smaller membership, gives the chance of a greater
 sense of ownership and identification, which are important to community
 building.

Is that really our problem?  Who needs this greater sense of ownership and 
identification?  

In short, I'd like proponents of this thread to explain in concrete detail:
What is the problem to be solved?
What is the base cause of that problem?
How does splitting the Incubator in to sub-groups of technology solves the 
cause of this problem?


Regards,
Alan

Re: Incubator reorg ideas: sub-groups per technology?

2013-06-15 Thread Alan Cabrera


On Jun 14, 2013, at 3:58 PM, Shane Curcuru a...@shanecurcuru.org wrote:

 I.e. while the IPMC or ComDev or whoever would still set policy and provide 
 community best practice guidance.  But then separate mailing lists/groups 
 would provide actual oversight of podlings (incoming, mentoring, graduating). 
  These would be based on rough technology areas: java, hadoop, servers, UI, 
 whatever.

Mmmm, more mailing lists.  There's a selling point.  ;)

You know, when I mentor a podling, I should't care what the technology is.  (I 
learned the hard way about having an interest in the actual technology of the 
podling and have generated ill will as a result)

A mentor can tell if a community gets it without having to know the 
technology.  If anything, mentors who know the technology should not be allowed 
to mentor that project; an academic position, to be sure, given the dearth of 
active mentors.


Regards,
Alan

Re: Incubator reorg ideas: sub-groups per technology?

2013-06-15 Thread Alan Cabrera

On Jun 15, 2013, at 8:08 AM, Joe Schaefer joe_schae...@yahoo.com wrote:

 What we really need for podlings is a bill of
 rights towards what they can expect of their
 mentors, because too few of them actually are
 willing to question the participation of the
 people who signed up to mentor them and that's
 not helping anybody.

Great idea.  

This spring I sent out personal messages to various podling members and asked 
them what they thought were problems with the incubator, if there were any.  
(There's a novel idea, ask the podlings what they think the problems are.  
Sorry, but slogging through all these emails instead of watching re-runs of 
Firefly irritates me.  :) )  I got an earful.

Other than their  concern for diversity/activity, the two biggest reported 
problems are timely resolution infrastructure requests and they way we seem 
to chronically make up and debase shit in the middle of voting.  As a podling 
incubates we seem to compulsively debate processes, rules, etc., ten feet ahead 
of the podling train.

We're working on the automation bits.  

Your document on what podlings can expect, in terms of to expect and what 
noise they can ignore during incubation would be fantastic.  I will commit to 
helping you out with this.


Regards,
Alan


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

Re: Incubator reorg ideas: sub-groups per technology?

2013-06-15 Thread Alan Cabrera

Brother, you hit the nail on the head.  I am so there  :)


Regards,
Alan



On Jun 15, 2013, at 8:34 AM, Joe Schaefer joe_schae...@yahoo.com wrote:

 I'll let it stew for a coupla days before
 I start charging in, but yeah something
 along these lines will surely address the
 palpable feeling of disempowerment we too
 often dish out.
 
 From: Alan Cabrera l...@toolazydogs.com
 To: general@incubator.apache.org; Joe Schaefer joe_schae...@yahoo.com 
 Sent: Saturday, June 15, 2013 11:29 AM
 Subject: Re: Incubator reorg ideas: sub-groups per technology?
 
 On Jun 15, 2013, at 8:08 AM, Joe Schaefer joe_schae...@yahoo.com wrote:
 
  What we really need for podlings is a bill of
  rights towards what they can expect of their
  mentors, because too few of them actually are
  willing to question the participation of the
  people who signed up to mentor them and that's
  not helping anybody.
 
 Great idea.  
 
 This spring I sent out personal messages to various podling members and asked 
 them what they thought were problems with the incubator, if there were any.  
 (There's a novel idea, ask the podlings what they think the problems are.  
 Sorry, but slogging through all these emails instead of watching re-runs of 
 Firefly irritates me.  :) )  I got an earful.
 
 Other than their  concern for diversity/activity, the two biggest reported 
 problems are timely resolution infrastructure requests and they way we seem 
 to chronically make up and debase shit in the middle of voting.  As a podling 
 incubates we seem to compulsively debate processes, rules, etc., ten feet 
 ahead of the podling train.
 
 We're working on the automation bits.  
 
 Your document on what podlings can expect, in terms of to expect and what 
 noise they can ignore during incubation would be fantastic.  I will commit 
 to helping you out with this.
 
 
 Regards,
 Alan

[PROPOSAL] Mandatory podling exit interviews

2013-06-15 Thread Alan Cabrera


Problem: we seem to have unclear and conflicting ideas as to what the areas of 
improvement are for the Incubator.

Cause: we have no concrete, anonymized, information on what the podlings' 
experiences were during incubation.

Solution: require all podlings to submit anonymous exit interviews as part of 
the graduation requirements.  These exit interviews will be suitably scrubbed 
and organized by the Incubator Ombudsman; see next proposal.  


Regards,
Alan


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

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

2013-06-13 Thread Alan Cabrera


On Jun 13, 2013, at 1:10 AM, Ross Gardler rgard...@opendirective.com wrote:

 On 13 June 2013 04:56, Alan Cabrera l...@toolazydogs.com wrote:
 
 On Jun 12, 2013, at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote:
 
 So here's a thought...
 
 ...
 
 I would therefore like to propose that we use Apache Stratos as a test
 case for the probationary TLP idea. I've already talked to Chris
 (who is driving the deconstruct the IPMC case) and Ant (who is less
 keen on dismantling the IPMC but wants to see how a probationary TLP
 model will play out). Both have agreed to help with this experiment if
 the IPMC and the Board wish it to proceed. I have not, however,
 discussed it with all the initial comitters or even mentors - I'm
 expecting them to speak up now.
 
 ...
 
 So, what do you think?
 
 I don't see the need to force Stratos through the Incubator given the 
 current proposed membership.  Some points:
 Who's responsible for monitoring the probation, the IPMC or the board?  I 
 think it should be the IPMC.
 
 I think we should come up with a concrete plan then go to the board.
 If the board is OK with taking it on then it should be board as this
 will be closer to Chris' defined end goal.
 
 In either case I undertake, as I noted in my original mail, to be the
 one that steps up to fix things if it all goes wrong. That's true
 whether it is IPMC or Board.

I guess the details of how this governance will work, what are the roles, and 
who will fill them, will need to be ironed out.

 What bits must absolutely be done before probation begins?
 
 That needs to be defined. Given the fact the next board meeting is
 only a week away I suggest we first make this a podling to allow us to
 start the project here at the ASF. We can then work with the various
 committees to work out what the right set-up process is (i.e. don't
 set up as a podling, set up as a pTLP). We can then shoot for
 submitting a board resolution next month.
 
 I have already made it clear to the proposers of the project that
 taking this route will result in a slightly longer set-up period
 (because of the need to define new policies along the way). They are
 comfortable trading slower set-up for potentially faster graduation.

It would probably be good to be clear on what are the exact characteristics 
that make this podling pTLP worthy for the future.  For example, the number of 
ASF veterans in its ranks.

 What minimum criteria does a probationary TLP have to meet to stay in good 
 graces?
 
 Exactly the same as any other TLP.
 
 What happens if the probationary TLP is not in good graces?
 
 Exactly the same as any other TLP. The board says fix it. If it
 isn't fixed the board kicks out the problem element(s) and invites
 remaining PMC to fix it. If that failes the pTLP is sent packing.
 
 What bits must absolutely be done before probation completes?
 
 Same as graduation from the Incubator (a release, demonstration of a
 healthy community, approval of the board)

Nice and simple.

 Fleshing out these and, I'm sure, others' concerns on a wiki, as Joe pointed 
 out, would be a great idea.
 
 Yes, but please note my proposal to do this as a standard podling
 rather than in this discussion phase. I don't think we need everything
 in a row before the team can get to work.
 
 If it should prove impossible to find a sensible process then we can
 simply leave the project as a standard podling.

Makes sense.

 So to recap the proposed timeline:
 
 - IPMC votes on accepting the podling with the intention of moving it to a 
 pTLP
 - mentors (with Chris' assistance) guide project committers in working
 with the various committees to define incubation/probation process
 - submit a board resolution in July to create the pTLP
  - if project is not ready to do so this can be delayed until August
 - If the board are unhappy with the project then I am called in to
 clear up the mess I made
 - If the board are happy with progress submit a resolution to become a
 TLP in 12 months (target 6 months)

+1

Though I wouldn't put a date on TLP; keep things simple.  We don't for podlings 
and since the pTLP will be filled with trustworthy ASF members we can trust 
they will do the right thing.


Regards,
Alan



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

Re: Change of Chair

2013-06-13 Thread Alan Cabrera


On Jun 13, 2013, at 2:03 PM, Benson Margulies bimargul...@gmail.com wrote:

 Incubator community,
 
 I have tendered my resignation as VP, Incubator. The PMC has recommend
 Marvin Humphrey as my successor in a motion submitted to the
 Foundation board for consideration at the meeting next week.

Thanks, Benson, for all your hard work!


Regards,
Alan


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

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

2013-06-12 Thread Alan Cabrera


On Jun 12, 2013, at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote:

 So here's a thought...
 
 There have been many discussions about different ways to incubate
 projects. One of the most radical ideas is to dismantle the incubator
 and replace the podling concept with probationary TLPs reporting to
 the board. As readers of this list will know I do not support the idea
 of dismantling the IPMC. I believe it does a great job that is not
 easily replaced by a board of nine directors. However, I have always
 acknowledged that the idea has merit under a certain set of
 circumstances.
 
 For me those circumstances are present in the Apache Stratos proposal.
 That is there are sufficient mentors and initial committers who are
 ASF Members that we can be reasonably certain that this project will
 succeed here at the ASF.
 
 I would therefore like to propose that we use Apache Stratos as a test
 case for the probationary TLP idea. I've already talked to Chris
 (who is driving the deconstruct the IPMC case) and Ant (who is less
 keen on dismantling the IPMC but wants to see how a probationary TLP
 model will play out). Both have agreed to help with this experiment if
 the IPMC and the Board wish it to proceed. I have not, however,
 discussed it with all the initial comitters or even mentors - I'm
 expecting them to speak up now.
 
 For my part my intention is to get the project set-up and then
 dissolve into the background. I do not intend to monitor the project
 on a day-to-day basis. However, I do promise to help pick up the
 pieces if the experiment should go horribly wrong.
 
 Of course running a single experiment will only allow us to define the
 incubation process for probationary TLPs, It is not going to solve all
 the problems Chris sees in the IPMC. However it will give us an
 opportunity to define the process, ask the board to approve this
 process and thus lay the foundations for other projects wishing to
 follow this path.
 
 So, what do you think?

I don't see the need to force Stratos through the Incubator given the current 
proposed membership.  Some points:
Who's responsible for monitoring the probation, the IPMC or the board?  I think 
it should be the IPMC.
What bits must absolutely be done before probation begins?
What minimum criteria does a probationary TLP have to meet to stay in good 
graces?
What happens if the probationary TLP is not in good graces?
What bits must absolutely be done before probation completes?
Fleshing out these and, I'm sure, others' concerns on a wiki, as Joe pointed 
out, would be a great idea.


Regards,
Alan

Re: [VOTE] Accept Apache HotdoG into the Incubator

2013-06-12 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On Jun 12, 2013, at 11:22 AM, Ramirez, Paul M (398J) 
paul.m.rami...@jpl.nasa.gov wrote:

 All,
 
 I'd like to call a VOTE for the acceptance of Apache HotdoG into the 
 Incubator. I'll leave the VOTE open for the rest of the week and close it out 
 Monday, June 17th early am PT.
 
 [ ] +1 Accept Apache HotdoG into the Incubator
 [ ] +0 Don't care.
 [ ] -1 Don't accept Apache HotdoG because...
 
 Full Proposal is pasted at the end of this email. Only VOTEs from Incubator 
 PMC members are binding, but all are welcome to express their thoughts.
 
 This is a second pass at this vote as I canceled it to pull in more mentors. 
 The following people voted on the first pass:
 
 Henry Saputra +1 (binding)
 Chris Mattmann + 1 (binding)
 
 Thanks!
 Paul Ramirez
 
 P.S. +1 from me (binding)
 
 
 = HotdoG Proposal =
 
 == Abstract ==
 
 The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
 format into GeoTIFF format. This is the first of a potential series of 
 incoming projects originating from The HDF Group -- the non-profit 
 organization is interested in evaluating the ASF as a potential home for many 
 of its projects. The HDF Group is an independently funded organization that 
 started many years ago with major investment from NASA as the Hierarchical 
 Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote 
 sensing data format for NASA missions, and an increasing number of other 
 disciplines including bio medicine, radio astronomy, climate science, and 
 other domains.
 
 HDF is both a data and metadata format, as well as a model for representing 
 and access information. There are numerous downstream tools that can read and 
 write HDF data, including a growing number of Geospatial data tools 
 (ESRI-based, and also OpenGeo and other community led efforts). In addition, 
 major interoperability efforts are also occurring between the remote sensing 
 community and the climate modeling community (which has traditionally favored 
 NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
 data format and model.
 
 HotdoG is poised to be a first of its kind in the form of bringing one of the 
 major 2 data formats for science to the ASF (the other being the NetCDF 
 format).
 
 == Proposal ==
 HotdoG is a software converter that converts Earth Science data in 
 HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of 
 remote sensing data to interoperate with common GIS tools (like WebGIS, Web 
 Processing, image analysis, and geo computational tools). We feel that the 
 project is an incremental step, and an appropriate focus with tangible 
 success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF 
 conversion.
 
 There are numerous interesting paths that we can take the toolkit in -- as 
 conversion from remotely sensed data to GeoTIFF involves ensuring that the 
 HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
 headers, and the associated format. Furthermore, capturing the HDF's 
 appropriate geo datum in GeoTIFF will be another important challenge.
 
 == Background ==
 
 GeoTIFF is a data and metadata standard for Earth science applications. It is 
 based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has 
 geographic (or cartographic) data embedded as tags within the TIFF file that 
 are used to geo-locate the image. This is required for correct integration of 
 the image in Geographic Information Systems (GIS) and other popular tools 
 like Google Earth Pro.
 
 In the recent years, GeoTIFF has gained popularity as a visualization format 
 among NASA HDF Earth science user communities according to the NASA data 
 user's survey. However, the conversion from HDF to GeoTIFF is not 
 straightforward for end users because NASA HDF data products are diverse and 
 organized in many different ways. For example, go to http://hdfeos.org/zoo 
 and you'll see many scripting language examples because no single script can 
 correctly visualize all NASA HDF data.
 
 == Rationale ==
 
 The HEG tool is limited to some NASA HDF-EOS2 products (no support for 
 HDF-EOS5 products) and it is not an open-source tool. The latest GDAL 
 (version 1.9.2 and above) is an open-source tool but it cannot handle many 
 non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure 
 HDF5) correctly and automatically.
 
 == Initial Goals ==
 
 We'll improve GDAL to support NASA HDF products better by handling 
 geo-location information and physical meaning of data correctly and 
 automatically.
 
 We'll handle NASA products intelligently so novice users don't have to supply 
 many options or figure out the details about the data products. For advanced 
 users, we'll give a full control of accessing HDF products in many different 
 ways so that the converted GeoTIFF file is scientifically valid and 
 meaningful.
 
 We aim to provide command line tools first and evolve

Re: [VOTE] Graduation of Apache Mesos

2013-06-12 Thread Alan Cabrera

+1 binding


Regards,
Alan

On Jun 12, 2013, at 1:03 PM, Mattmann, Chris A (398J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi All,
 
 The Apache Mesos community is ready to graduate. They have added
 committers and PPMC members while in the Incubator; have made a
 few releases; are discussing their issues on list and in the Apache
 way, and are inclusive and representative of Apache's goals as a
 Foundation.
 
 I'm extremely happy to put them up for Incubator graduation.
 We've VOTEd as a community to move forward with this:
 
 DISCUSS thread here: http://s.apache.org/XAu
 VOTE thread here: http://s.apache.org/K8C
 VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov
 
 Project Incubator status page here:
 http://incubator.apache.org/projects/mesos.html
 
 Board resolution pasted at bottom of email.
 
 Existing tallies from the community VOTE:
 
 +1
 Chris Mattmann*
 Vinod Kone
 Benjamin Hindman
 Benjamin Mahler
 Yan Xiu
 Deepal Jayasinghe
 Brenden Matthews
 Matei Zaharia
 Ant Elder*
 Konstantin Boudnik
 
 * - indicates IPMC
 
 Please VOTE to graduate Apache Mesos from the Incubator. Though
 only Incubator PMC member VOTEs are binding, all are welcome to
 voice your opinion. I'll leave the VOTE open for at least 72 hours,
 and hopefully can get enough VOTEs in time to close it by Saturday
 or Sunday in time for the board meeting on 6/19.
 
 [ ] +1 Graduate Apache Mesos from the Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Mesos from the Incubator because..
 
 Thanks everyone!
 
 Cheers,
 Chris
 
 
 ---board 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 efficient cluster management, resource
 isolation and sharing across distributed applications.
 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Mesos Project, be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further
 
 RESOLVED, that the Apache Mesos Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficient cluster management, resource isolation
 and sharing across distributed applications; and be it further
 RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for
 management of the projects within the scope of responsibility
 of the Apache Mesos 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 Mesos Project:
 
 * Ali Ghodsi a...@apache.org
 * Andy Konwinski and...@apache.org
 * Benjamin Hindhman b...@apache.org
 * Benjamin Mahler bmah...@apache.org
 * Brian McCalister bri...@apache.org
 * Ian Holsman i...@apache.org
 * Matei Alexandru Zahari ma...@apache.org
 * Chris Mattmann mattm...@apache.org
 * Tom White tomwh...@apache.org
 * Vinod Kone vinodk...@apache.org
 * Brenden Matthews bren...@apache.org
 * Thomas Marshall tmarsh...@apache.org
 * Charles Reiss wog...@apache.org
 
 
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
 appointed to the office of Vice President, Apache Mesos, 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 Mesos Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Mesos podling; and be it further
 
 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Mesos podling encumbered upon the Apache Incubator
 Project are hereafter discharged.
 
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


-
To unsubscribe, e-mail:

Re: [VOTE] Apache Spark for the Incubator

2013-06-08 Thread Alan Cabrera

+1 binding


Regards,
Alan

On Jun 7, 2013, at 10:34 PM, Mattmann, Chris A (398J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Folks,
 
 OK discussion has died down, time to VOTE to accept Spark into the
 Apache Incubator. I'll let the VOTE run for at least a week.
 
 So far I've heard +1s from the following folks, so no need for them
 to VOTE again unless they want to change their VOTE:
 
 +1
 
 Chris Mattmann*
 Konstantin Boudnik
 Henry Saputra*
 Reynold Xin
 Pei Chen
 Roman Shaposhnik*
 Suresh Marru*
 
 * -indicates IPMC
 
 [ ] +1 Accept Spark into the Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't accept Spark into the Apache Incubator because..
 
 Proposal text is below.
 
 === Abstract ===
 Spark is an open source system for large-scale data analysis on clusters.
 
 === Proposal ===
 Spark is an open source system for fast and flexible large-scale data
 analysis. Spark provides a general purpose runtime that supports
 low-latency execution in several forms. These include interactive
 exploration of very large datasets, near real-time stream processing, and
 ad-hoc SQL analytics (through higher layer extensions). Spark interfaces
 with HDFS, HBase, Cassandra and several other storage storage layers, and
 exposes APIs in Scala, Java and Python.
 Background
 Spark started as U.C. Berkeley research project, designed to efficiently
 run machine learning algorithms on large datasets. Over time, it has
 evolved into a general computing engine as outlined above. Spark¹s
 developer community has also grown to include additional institutions,
 such as universities, research labs, and corporations. Funding has been
 provided by various institutions including the U.S. National Science
 Foundation, DARPA, and a number of industry sponsors. See:
 https://amplab.cs.berkeley.edu/sponsors/ for full details.
 
 === Rationale ===
 As the number of contributors to Spark has grown, we have sought for a
 long-term home for the project, and we believe the Apache foundation would
 be a great fit. Spark is a natural fit for the Apache foundation: Spark
 already interoperates with several existing Apache projects (HDFS, HBase,
 Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar
 with the Apache process and and subscribes to the Apache mission - the
 team includes multiple Apache committers already. Finally, joining Apache
 will help coordinate the development effort of the growing number of
 organizations which contribute to Spark.
 
 == Initial Goals ==
 The initial goals will most likely be to move the existing codebase to
 Apache and integrate with the Apache development process. Furthermore, we
 plan for incremental development, and releases along with the Apache
 guidelines.
 
 === Current Status ===
 == Meritocracy ==
 The Spark project already operates on meritocratic principles. Today,
 Spark has several developers and has accepted multiple major patches from
 outside of U.C. Berkeley. While this process has remained mostly informal
 (we do not have an official committer list), an implicit organization
 exists in which individuals who contribute major components act as
 maintainers for those modules. If accepted, the Spark project would
 include several of these participants as committers from the onset. We
 will work to identify all committers and PPMC members for the project and
 to operate under the ASF meritocratic principles.
 
 === Community ===
 Acceptance into the Apache foundation would bolster the already strong
 user and developer community around Spark. That community includes dozens
 of contributors from several institutions, a meetup group with several
 hundred members, and an active mailing list composed of hundreds of users.
 Core Developers
 The core developers of our project are listed in our contributors and
 initial PPMC below. Though many exist at UC Berkeley, there is a
 representative cross sampling of other organizations including Quantifind,
 Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends.
 
 
 === Alignment ===
 Our proposed effort aligns with several ongoing BIGDATA and U.S. National
 priority funding interests including the NSF and its Expeditions program,
 and the DARPA XDATA project. Our industry partners and collaborators are
 well aligned with our code base.
 
 There are also a number of related Apache projects and dependencies, that
 will be mentioned in the Relationships with Other Apache products section.
 
 == Known Risks ==
 
 === Orphaned Products ===
 Given the current level of investment in Spark - the risk of the project
 being abandoned is minimal. There are several constituents who are highly
 incentivized to continue development. The U.C. Berkeley AMPLab relies on
 Spark as a platform for a large number of long-term research projects.
 Several companies have build verticalized products which are tightly
 dependent on Spark. Other companies have devoted significant internal
 infrastructure investment in Spark.
 
 ===

Re: [VOTE] Accept Apache MetaModel into the Apache incubator

2013-06-08 Thread Alan Cabrera

+1 - binding


Regards,
Alan

On Jun 6, 2013, at 3:30 PM, Henry Saputra henry.sapu...@gmail.com wrote:

 Hi All,
 
 I'd like to call a VOTE for acceptance of MetaModel into the Apache
 incubator.
 The vote will close on June 12, 2013 at 6:00 PM (PST).
 
 [] +1 Accept MetaModel into the Apache incubator
 [] +0 Don't care.
 [] -1 Don't accept MetaModel into the incubator because...
 
 Full proposal is pasted at the bottom on this email, and the corresponding 
 wiki
 is:
 http://wiki.apache.org/incubator/MetaModelProposal.
 
 Only VOTEs from Incubator PMC members are binding, but all are welcome to
 express their thoughts.
 
 Thanks,
 
 Henry Saputra
 Champion for Apache MetaModel
 
 
 P.S. Here's my +1 (binding)
 
 
 -
 
 = MetaModel – uniform data access across datastores =
 
 Proposal for Apache Incubator
 
 == Abstract ==
 
 MetaModel is a data access framework, providing a common interface for
 exploration and querying of different types of datastores.
 
 == Proposal ==
 
 MetaModel provides a uniform meta-model for exploring and querying the
 structure of datastores, covering but not limited to relational databases,
 various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
 more. The scope of the project is to stay domain-agnostic, so the
 meta-model will be concerned with schemas, tables, columns, rows,
 relationships etc.
 
 On top of this meta-model a rich querying API is provided which resembles
 SQL, but built using compiler-checked Java language constructs. For
 datastores that do not have a native SQL-compatible query engine, the
 MetaModel project also includes an abstract Java-based query engine
 implementation which individual datastore-modules can adapt to fit the
 concrete datastore.
 
 === Background ===
 
 The MetaModel project was initially developed by eobject.dk to service the
 DataCleaner application (http://datacleaner.org). The main requirement was
 to perform data querying and modification operations on a wide range of
 quite different datastores. Furthermore a programmatic query model was
 needed in order to allow different components to influence the query plan.
 
 In 2009, Human Inference acquired the eobjects projects including
 MetaModel. Since then MetaModel has been put to extensive use in the Human
 Inference products. The open source nature of the project was reinforced,
 leading to a significant growth in the community.
 
 MetaModel has successfully been used in a number of other open source
 projects as well as mission critical commercial software from Human
 Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org.
 
 === Rationale ===
 
 Different types of datastores have different characteristics, which always
 lead to the interfaces for these being different from one another.
 Standards like JDBC and the SQL language attempt to standardize data
 access, but for some datastore types like flat files, spreadsheets, NoSQL
 databases and more, such standards are not even implementable.
 
 Specialization in interfaces obviously has merit for optimized usage, but
 for integration tools, batch applications and or generic data modification
 tools, this myriad of specialized interfaces is a big pain. Furthermore,
 being able to query every datastore with a basic set of SQL-like features
 can be a great productivity boost for a wide range of applications.
 
 === Initial goals ===
 
 MetaModel is already a stable project, so initial goals are more oriented
 towards an adaption to the Apache ecosystem than about functional changes.
 
 We are constantly adding more datastore types to the portfolio, but the
 core modules have not had drastic changes for some time.
 
 Our focus will be on making ties with other Apache projects (such as POI,
 Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
 to something more rememberable.
 This includes comply with Apache Software Foundation license for third
 party dependencies.
 
 == Current status ==
 
 === Meritocracy ===
 
 We intend to do everything we can to encourage a meritocracy in the
 development of MetaModel. Currently most important development and design
 decisions have been made at Human Inference, but with an open window for
 anyone to participate on mailing lists and discussion forums. We believe
 that the approach going forward should be more encouraging by sharing all
 the design ideas and discussions in the open, not only just the topics that
 have been “dragged” into the open by third parties.  We believe that
 meritocracy will be further stimulated by granting the control of the
 project to an independent committee.
 
 === Community ===
 
 The community around MetaModel already exists, but we believe it will grow
 substantially by becoming an Apache project. With MetaModel used in a wide
 range of both open and closed source application, both at Human Inference
 (HIquality MDM), it’s open source projects DataCleaner,

Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera

Mentors come and go.  Is there an explicit rule that a podling needs three 
mentors before it can start to be incubated?


Regards,
Alan

On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Paul, guys; I just noticed that HotdoG only has 2 mentors right now
 (myself, and pramirez).
 
 Is there another IPMC mentor that would be willing to sign up
 for the project? I think we should probably cancel the VOTE Paul,
 and restart it with another mentor.
 
 Besides that, Adam Estrada (VP, SIS) has expressed interest also
 in the proposal. So we should sort that out. Sorry for the delay,
 hopefully we can restart the VOTE shortly when we have a 3rd mentor
 and sort out Adam's participation.
 
 Paul can you send a [CANCEL] [VOTE] thread?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 11:21 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
 
 Hey Jim,
 
 I think it should probably read:
 
 We're looking for people interested in HotDog and to move the proposal
 into the Apache Community. The project is moving from a previously
 open source external community into Apache.
 
 
 I've updated the proposal on the wiki as such:
 
 https://wiki.apache.org/incubator/HotdoGProposal
 
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Jim Jagielski j...@jagunet.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 10:55 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator
 
 
 On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J)
 paul.m.rami...@jpl.nasa.gov wrote:
 
 We're looking for developers and sponsors.
 
 
 Sponsors??
 
 
 -
 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
 


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

Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera

Let's keep things simple and let the vote proceed.  

It's in the podling's interest to get three active mentors for the reasons you 
mention below.

Please, let's keep things simple.


Regards,
Alan

On Jun 5, 2013, at 7:51 AM, Ross Gardler rgard...@opendirective.com wrote:

 There is no explicit rule (to my knowledge). The number 3 came about
 because that's how many votes are needed for a release. With 3
 mentors on the project it means the project needs to come to the IPMC
 for additional votes. As we've seen this can become very messy.
 
 Ross
 
 On 5 June 2013 15:48, Alan Cabrera l...@toolazydogs.com wrote:
 Mentors come and go.  Is there an explicit rule that a podling needs three 
 mentors before it can start to be incubated?
 
 
 Regards,
 Alan
 
 On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Paul, guys; I just noticed that HotdoG only has 2 mentors right now
 (myself, and pramirez).
 
 Is there another IPMC mentor that would be willing to sign up
 for the project? I think we should probably cancel the VOTE Paul,
 and restart it with another mentor.
 
 Besides that, Adam Estrada (VP, SIS) has expressed interest also
 in the proposal. So we should sort that out. Sorry for the delay,
 hopefully we can restart the VOTE shortly when we have a 3rd mentor
 and sort out Adam's participation.
 
 Paul can you send a [CANCEL] [VOTE] thread?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 11:21 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
 
 Hey Jim,
 
 I think it should probably read:
 
 We're looking for people interested in HotDog and to move the proposal
 into the Apache Community. The project is moving from a previously
 open source external community into Apache.
 
 
 I've updated the proposal on the wiki as such:
 
 https://wiki.apache.org/incubator/HotdoGProposal
 
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Jim Jagielski j...@jagunet.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 10:55 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator
 
 
 On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J)
 paul.m.rami...@jpl.nasa.gov wrote:
 
 We're looking for developers and sponsors.
 
 
 Sponsors??
 
 
 -
 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
 
 
 
 -
 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: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera

Please, let's not make up new rules as we go along.

To be sure as IPMC members we should proactively inform the prospective podling 
of the potential problems they will encounter entering the Incubator with less 
than 3 mentors.  It would commendable if IPMC members actively hunted such 
mentors down for the potential podling.

But let's not do ad hoc tweaking to our processes.  Let's keep things simple 
and let the vote continue.


Regards,
Alan

On Jun 5, 2013, at 7:54 AM, Mattmann, Chris A (398J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hey Alan,
 
 Great question if there is an official policy here. My read is
 that no it's based on tribal knowledge and informal assumption.
 
 That said, let's take a simple data point: how many proposals
 over the past few years have been accepted with less than 3
 mentors (not considering like you mentioned that mentors do
 go AWOL from time to time and that over the life of a podling,
 there may be less than 3 active at a given time)?
 
 It's Paul's proposal as Champion so, up to him, but my recommendation
 would be to find 1 more wiling IPMC $victim..err mentor!
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Alan Cabrera l...@toolazydogs.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Wednesday, June 5, 2013 7:48 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
 
 Mentors come and go.  Is there an explicit rule that a podling needs
 three mentors before it can start to be incubated?
 
 
 Regards,
 Alan
 
 On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 Paul, guys; I just noticed that HotdoG only has 2 mentors right now
 (myself, and pramirez).
 
 Is there another IPMC mentor that would be willing to sign up
 for the project? I think we should probably cancel the VOTE Paul,
 and restart it with another mentor.
 
 Besides that, Adam Estrada (VP, SIS) has expressed interest also
 in the proposal. So we should sort that out. Sorry for the delay,
 hopefully we can restart the VOTE shortly when we have a 3rd mentor
 and sort out Adam's participation.
 
 Paul can you send a [CANCEL] [VOTE] thread?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 11:21 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
 
 Hey Jim,
 
 I think it should probably read:
 
 We're looking for people interested in HotDog and to move the proposal
 into the Apache Community. The project is moving from a previously
 open source external community into Apache.
 
 
 I've updated the proposal on the wiki as such:
 
 https://wiki.apache.org/incubator/HotdoGProposal
 
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Jim Jagielski j...@jagunet.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Tuesday, June 4, 2013 10:55 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator
 
 
 On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J)
 paul.m.rami...@jpl.nasa.gov wrote:
 
 We're

Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera


On Jun 5, 2013, at 8:21 AM, Greg Reddin gred...@gmail.com wrote:

 Added my name to the proposal. I'm willing to mentor.

Benson,

One of my podling tools doesn't see that Greg is on the IPMC though he is an 
ASF member.  I think we need to update the LDAP entries if he's already been 
ACK'd.


Regards,
Alan


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

Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera


On Jun 5, 2013, at 8:37 AM, Greg Reddin gred...@gmail.com wrote:

 On Wed, Jun 5, 2013 at 10:26 AM, Alan Cabrera l...@toolazydogs.com wrote:
 
 
 On Jun 5, 2013, at 8:21 AM, Greg Reddin gred...@gmail.com wrote:
 
 Added my name to the proposal. I'm willing to mentor.
 
 Benson,
 
 One of my podling tools doesn't see that Greg is on the IPMC though he is
 an ASF member.  I think we need to update the LDAP entries if he's already
 been ACK'd.
 
 
 Greg Stein pointed out yesterday that the ACK date was  3/15/2010

Great, just need someone with the karmic powers to do the needful.   :)


Regards,
Alan


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

Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator

2013-06-05 Thread Alan Cabrera

+ infra-dev

On Jun 5, 2013, at 8:45 AM, Mattmann, Chris A (398J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Looking at:
 
 http://people.apache.org/committers-by-project.html#incubator-pmc
 
 
 It would seem that there would be a cn for incubator-pmc in LDAP.
 So I tried running modify_committee.pl on mino and got back:
 
 No LDAP groups found with cn=incubator-pmc!
 
 So either I'm doing that wrong or don't have the karma.
 
 Cheers,
 Chris
 
 -Original Message-
 From: Alan Cabrera l...@toolazydogs.com
 Reply-To: general@incubator.apache.org general@incubator.apache.org
 Date: Wednesday, June 5, 2013 8:40 AM
 To: general@incubator.apache.org general@incubator.apache.org
 Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
 
 
 On Jun 5, 2013, at 8:37 AM, Greg Reddin gred...@gmail.com wrote:
 
 On Wed, Jun 5, 2013 at 10:26 AM, Alan Cabrera l...@toolazydogs.com
 wrote:
 
 
 On Jun 5, 2013, at 8:21 AM, Greg Reddin gred...@gmail.com wrote:
 
 Added my name to the proposal. I'm willing to mentor.
 
 Benson,
 
 One of my podling tools doesn't see that Greg is on the IPMC though he
 is
 an ASF member.  I think we need to update the LDAP entries if he's
 already
 been ACK'd.
 
 
 Greg Stein pointed out yesterday that the ACK date was  3/15/2010
 
 Great, just need someone with the karmic powers to do the needful.   :)
 
 
 Regards,
 Alan
 
 
 -
 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: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-04 Thread Alan Cabrera


On Jun 3, 2013, at 5:12 PM, Greg Stein gst...@gmail.com wrote:

 As I said, it does look good. But I don't see the LinkedIn Copyright
 in any files under tools/. The copyright/license header should remain
 in the files that you copied into our repos. It is impossible to tell
 what is from LinkedIn.
 

I'll add the copyright to those files.


Regards,
Alan

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-04 Thread Alan Cabrera


On Jun 4, 2013, at 5:58 AM, Kevan Miller kevan.mil...@gmail.com wrote:

 
 On Jun 4, 2013, at 8:46 AM, Greg Stein gst...@gmail.com wrote:
 
 On Jun 4, 2013 4:22 AM, ant elder ant.el...@gmail.com wrote:
 
 This when in doubt leave it out approach has gone a long way at
 smoothing podling release reviews compared to the olden days.
 
 Seriously? The inserted code uses our own license! Go look at 4(d) and tell
 me we should not insert a notice. It is both Right, and what is demanded by
 our own license.
 
 I haven't seen a description of where this code is coming from. Is it a 
 contribution from LinkedIn? Is it some open source code from LinkedIn that we 
 are copying into our svn from some other project?
 
 If it's the former and LinkedIn has requested attribution for their 
 contribution, then let's observe their request and add attribution to the 
 NOTICE.
 
 If it's the latter *and* the subject code has a NOTICE file, then we 
 absolutely must include the relevant portions of their NOTICE in our NOTICE. 
 Otherwise, 4 (d) doesn't require us to do anything. Agreed?


The code is internal LinkedIn code that I copied with the appropriate 
permissions.  Attribution was requested.


Regards,
Alan




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

Re: svn commit: r1489076 - in /incubator/public/trunk/tools: src/asf/incubator/podlings.py tests/test_podlings.py

2013-06-04 Thread Alan Cabrera


On Jun 3, 2013, at 2:47 PM, sebb seb...@gmail.com wrote:

 On 3 June 2013 18:43,  a...@apache.org wrote:
 Author: adc
 Date: Mon Jun  3 17:43:51 2013
 New Revision: 1489076
 
 URL: http://svn.apache.org/r1489076
 Log:
 Minor sketch of some podling code before I forget to check it in.
 
 And perhaps add some comments explaining what the purpose is?

Definitely will.


Regards,
Alan


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

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-04 Thread Alan Cabrera


On Jun 4, 2013, at 6:34 AM, Alan Cabrera l...@toolazydogs.com wrote:

 
 On Jun 3, 2013, at 5:12 PM, Greg Stein gst...@gmail.com wrote:
 
 As I said, it does look good. But I don't see the LinkedIn Copyright
 in any files under tools/. The copyright/license header should remain
 in the files that you copied into our repos. It is impossible to tell
 what is from LinkedIn.
 
 
 I'll add the copyright to those files.

This was what was in my head when I checked in my code:

http://www.apache.org/legal/src-headers.html#header-existingcopyright

More specifically:

move them to the NOTICE file associated with each applicable project release


Regards,
Alan

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-03 Thread Alan Cabrera


On Jun 3, 2013, at 2:23 PM, sebb seb...@gmail.com wrote:

 On 3 June 2013 05:10, Greg Stein gst...@gmail.com wrote:
 On Sun, Jun 2, 2013 at 11:08 PM, Alan Cabrera l...@toolazydogs.com wrote:
 ...
 
 Apache Incubator tools
 Copyright 2013 The Apache Software Foundation
 
 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).
 
 This distribution contains code from the LinkedIn Corporation:
 
Copyright (c) 2013 LinkedIn Corp. All rights reserved.
Licensed under the Apache License, Version 2.0
 
 
 WDYT?
 
 Looks good. And given that the LinkedIn stuff is under ALv2, then 4(d)
 comes into play, requesting attribution. It is Right and Proper that
 they get a couple lines in our NOTICE file.
 
 I'm not convinced of that.
 If their attribution request is not in the NOTICE file, does it have
 to go in ours?
 
 Attribution could be added in a CREDITS file as per
 
 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/CREDITS.txt

A credits file does not seem to be the appropriate place for a copyright 
declaration.


Regards,
Alan


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

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-02 Thread Alan Cabrera


On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote:

 Modified: incubator/public/trunk/tools/NOTICE.txt
 URL: 
 http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff
 ==
 --- incubator/public/trunk/tools/NOTICE.txt (original)
 +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun  2 16:21:24 2013
 @@ -1,5 +1,21 @@
 =
 ==  NOTICE file corresponding to section 4(d) of the Apache License,   ==
 -==  Version 1.0.0, in this case for the LiveTribe Utilities==
 +==  Version 2.0.0, in this case for the ASF Incubator tools==
 ==  distribution.  ==
 =
 +
 +This distribution contains code from the LinkedIn Corporation:
 +
 + Copyright (c) 2013 LinkedIn Corp. All rights reserved.
 +
 + Licensed under the Apache License, Version 2.0 (the License);
 + you may not use this file except in compliance with the License.
 + You may obtain a copy of the License at
 +
 + http://www.apache.org/licenses/LICENSE-2.0
 +
 + Unless required by applicable law or agreed to in writing, software
 + distributed under the License is distributed on an AS IS BASIS,
 + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 + See the License for the specific language governing permissions and
 + limitations under the License.
 
 That does not look like a standard NOTICE file.
 The part between === should not be present, and the AL 2.0 should not
 be there either.
 
 Is the notice entry even required by the Linked In license?
 
 Remember that NOTICE files are like poems - they are only correct when
 nothing more can be removed!

Would this suffice:

begin
This distribution contains code from the LinkedIn Corporation:

Copyright (c) 2013 LinkedIn Corp. All rights reserved.
endj


Regards,
Alan



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

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-02 Thread Alan Cabrera


On Jun 2, 2013, at 5:29 PM, sebb seb...@gmail.com wrote:

 On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote:
 
 On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote:
 
 Modified: incubator/public/trunk/tools/NOTICE.txt
 URL: 
 http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff
 ==
 --- incubator/public/trunk/tools/NOTICE.txt (original)
 +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun  2 16:21:24 2013
 @@ -1,5 +1,21 @@
 =
 ==  NOTICE file corresponding to section 4(d) of the Apache License,   ==
 -==  Version 1.0.0, in this case for the LiveTribe Utilities==
 +==  Version 2.0.0, in this case for the ASF Incubator tools==
 ==  distribution.  ==
 =
 +
 +This distribution contains code from the LinkedIn Corporation:
 +
 + Copyright (c) 2013 LinkedIn Corp. All rights reserved.
 +
 + Licensed under the Apache License, Version 2.0 (the License);
 + you may not use this file except in compliance with the License.
 + You may obtain a copy of the License at
 +
 + http://www.apache.org/licenses/LICENSE-2.0
 +
 + Unless required by applicable law or agreed to in writing, software
 + distributed under the License is distributed on an AS IS BASIS,
 + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 + See the License for the specific language governing permissions and
 + limitations under the License.
 
 That does not look like a standard NOTICE file.
 The part between === should not be present, and the AL 2.0 should not
 be there either.
 
 Is the notice entry even required by the Linked In license?
 
 Remember that NOTICE files are like poems - they are only correct when
 nothing more can be removed!
 
 Would this suffice:
 
 begin
 This distribution contains code from the LinkedIn Corporation:
 
 Copyright (c) 2013 LinkedIn Corp. All rights reserved.
 endj
 
 IMO, no.
 
 It's not a standard NOTICE file - the ASF header is missing.


Can you point to a canonical example for me to emulate?


Regards,
Alan



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

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-02 Thread Alan Cabrera

On Jun 2, 2013, at 7:45 PM, Kevan Miller kevan.mil...@gmail.com wrote:

On Jun 2, 2013, at 10:09 PM, Alan Cabrera l...@toolazydogs.com wrote:

On Jun 2, 2013, at 5:29 PM, sebb seb...@gmail.com wrote:

On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote:

On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote:

Modified: incubator/public/trunk/tools/NOTICE.txt
URL:
http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff
==
--- incubator/public/trunk/tools/NOTICE.txt (original)
+++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013
@@ -1,5 +1,21 @@
=
== NOTICE file corresponding to section 4(d) of the Apache License, ==
-== Version 1.0.0, in this case for the LiveTribe Utilities
==
+== Version 2.0.0, in this case for the ASF Incubator tools
==
== distribution. ==
=
+
+This distribution contains code from the LinkedIn Corporation:
+
+ Copyright (c) 2013 LinkedIn Corp. All rights reserved.
+
+ Licensed under the Apache License, Version 2.0 (the License);
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an AS IS BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.

That does not look like a standard NOTICE file.
The part between === should not be present, and the AL 2.0 should not
be there either.

Is the notice entry even required by the Linked In license?

Remember that NOTICE files are like poems - they are only correct when
nothing more can be removed!

Would this suffice:

begin
This distribution contains code from the LinkedIn Corporation:

IMO, no.

It's not a standard NOTICE file - the ASF header is missing.

Can you point to a canonical example for me to emulate?

How about the following:

http://www.apache.org/legal/src-headers.html#notice
and
http://www.apache.org/dev/licensing-howto.html

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

This distribution contains code from the LinkedIn Corporation:

WDYT?

Regards,
Alan

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

Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/init.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf

2013-06-02 Thread Alan Cabrera


On Jun 2, 2013, at 8:51 PM, Kevan Miller kevan.mil...@gmail.com wrote:

 
 On Jun 2, 2013, at 11:08 PM, Alan Cabrera l...@toolazydogs.com wrote:
 
 Apache Incubator tools
 Copyright 2013 The Apache Software Foundation
 
 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).
 
 This distribution contains code from the LinkedIn Corporation:
 
   Copyright (c) 2013 LinkedIn Corp. All rights reserved.
   Licensed under the Apache License, Version 2.0
 
 
 WDYT?
 
 There is still Sebb's outstanding question:
 
 Anyway, does the LinkedIn license REQUIRE attribution in a NOTICE file? 

I was asked to provide attribution.  The NOTICE file seemed to be a reasonable 
plea to put it.


Regards,
Alan


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

Re: [VOTE] Release Apache jclouds 1.6.1-incubating, RC2

2013-06-01 Thread Alan Cabrera

How many binding votes are there from the PPMC vote?


Regards,
Alan

On May 31, 2013, at 4:13 PM, Andrew Bayer aba...@apache.org wrote:

 Hello,
 
 This is the second release candidate for Apache jclouds 1.6.1-incubating,
 the first jclouds release at Apache.
 
 The PPMC has approved the release at this point, so this is an IPMC vote.
 
 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412styleName=HtmlprojectId=12314430
 
 *** Please download, test and vote by Monday, June 3nd, 5pm PDT.
 
 Note that we are voting upon the source (tag), binaries are provided for
 convenience.
 
 Source and binary files:
 http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-2
 
 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachejclouds-043
 
 The tags to be voted upon:
 - jclouds -
 https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=5123403cd8e146861be8b94d1b5ec2c4574ed810
 - jclouds-labs -
 https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=5e78e6ed2343e84cc48492edc1147f4c68f2d0e3
 - jclouds-chef -
 https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=665a98fa04f313645aa484acd7959c721583f808
 - jclouds-karaf -
 https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=fc357921782db55e01d27ad3cc1a392825978ef2
 - jclouds-cli -
 https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=c7f3509bbcb40a5cd35f917fbcf2c05222542de4
 
 jclouds KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/incubator/jclouds/KEYS
 
 [ ] +1
 [ ] 0
 [ ] -1 (explain why)
 
 A.


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

Re: What's the difference between dormant and retired?

2013-05-30 Thread Alan Cabrera


On May 30, 2013, at 12:08 AM, ant elder ant.el...@gmail.com wrote:

 Looking in poddling.xml there are 3 poddlings marked dormant and nearly
 30 marked retired. The 3 dormant ones are from ages ago and looking back
 in the archives its from when there wasn't a documented retirement process
 and people didn't really know what to call it. IMHO the simplest thing to
 avoid this confusion would be to just change the status of Juice,
 SocialSite, and TripleSoup in podling.xml from dormant to retired. If it
 maters at all, AFAICT the main thing back then was some status that stopped
 the poddling getting included in the reporting schedule, and either status
 does that.

Frankly, I don't see the need for the distinction and, IMNSHO, is symptomatic 
of the over organization of the Incubator.


Regards,
Alan


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

Re: [PROPOSAL] MetaModel for the Apache Incubator

2013-05-30 Thread Alan Cabrera


On May 29, 2013, at 12:33 AM, ant elder ant.el...@gmail.com wrote:

 From the subject line I thought this was going to be another attempt to
 sort out the incubator  :-/

LOL, so did I!


Regards,
Alan


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

Re: Podling not Poddling

2013-05-30 Thread Alan Cabrera

Do it!  Thanks!


Regards,
Alan

On May 30, 2013, at 8:32 AM, sebb seb...@gmail.com wrote:

 I keep seeing the word Poddling being used in mail and now the Wiki
 [1]; however I thought the original and correct name was Podling?
 
 I think we should stick to Podling for all the documentation.
 Anyone mind if I rename the Wiki page?
 
 [1] https://wiki.apache.org/incubator/OlderPoddlingsWithARelease
 
 -
 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: What's the difference between dormant and retired?

2013-05-30 Thread Alan Cabrera


On May 30, 2013, at 7:27 AM, Alan Cabrera l...@toolazydogs.com wrote:

 
 On May 30, 2013, at 12:08 AM, ant elder ant.el...@gmail.com wrote:
 
 Looking in poddling.xml there are 3 poddlings marked dormant and nearly
 30 marked retired. The 3 dormant ones are from ages ago and looking back
 in the archives its from when there wasn't a documented retirement process
 and people didn't really know what to call it. IMHO the simplest thing to
 avoid this confusion would be to just change the status of Juice,
 SocialSite, and TripleSoup in podling.xml from dormant to retired. If it
 maters at all, AFAICT the main thing back then was some status that stopped
 the poddling getting included in the reporting schedule, and either status
 does that.
 
 Frankly, I don't see the need for the distinction and, IMNSHO, is symptomatic 
 of the over organization of the Incubator.

Done.  I've cleaned up the podlings.xml file and all the site generating code.


Regards,
Alan


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

Re: What's the difference between dormant and retired?

2013-05-29 Thread Alan Cabrera

If no one minds I will change them all to dormant, since all are welcome back 
to the fold, should they so desire.


Regards,
Alan

On May 27, 2013, at 12:58 PM, Christian Grobmeier grobme...@gmail.com wrote:

 On Mon, May 27, 2013 at 9:17 PM, John D. Ament john.d.am...@gmail.com wrote:
 I think the terms mean different things, from the incubator perspective.
 
 Dormant - we're not active enough right now for a full community, but
 believe later on we can build it back up.
 Retired - we've given up all hope of becoming a TLP, instead we think it's
 best to archive the code/move it to github/move it to bitbucket and allow
 others who want to work on it to just grab it and go.
 
 The difference is one goes to github and one does not?
 
 After this interpretation I would expect dormant projects to retire.
 Retired projects
 can be revived too. It does not matter if there was something on GitHub or 
 not.
 
 Not enough for me to maintain two terms.
 
 
 Just my 2 cents..
 
 
 On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier 
 grobme...@gmail.comwrote:
 
 On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera l...@toolazydogs.com
 wrote:
 Yeah, I like the word dormant as well.  Should we rename them all to
 dormant?
 
 +1 from me. So far I don't see any difference in the end.
 
 
 
 
 Regards,
 Alan
 
 On May 27, 2013, at 10:32 AM, Upayavira u...@odoko.co.uk wrote:
 
 I think it was just a question of 'retiring' sounding too final. Using
 the word 'dormant' was less threatening, and made it more feasible for
 the podlings to go, well, dormant.
 
 Upayavira
 
 On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
 They kinda sound the same.  Why didn't podlings want to retire?  Does
 anyone know?
 
 
 Regards,
 Alan
 
 On May 27, 2013, at 9:14 AM, Christian Grobmeier grobme...@gmail.com
 wrote:
 
 I asked the same question in july 2011, and got a response from Henri
 Yandell which I repost here:
 
 Given the PPMC is closed down, I think it has to be retired.
 
 Dormant implies a PPMC is taking some time off.
 
 Basically this is a larger version of don't be afraid to delete a
 line of code; it's in version control.
 
 Hen
 
 
 
 
 
 On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera a...@toolazydogs.com
 wrote:
 Looking at the podlings.xml and it's not clear to me what the
 difference is.  I'm sure I neglected to read some documentation bit.
 
 
 Regards,
 Alan
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 --
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 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
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 --
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 
 --
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 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

[jira] [Created] (INCUBATOR-126) Sometimes its not clear that the who vets the podling name

2013-05-27 Thread Alan Cabrera (JIRA)

Alan Cabrera created INCUBATOR-126:
--

 Summary: Sometimes its not clear that the who vets the podling name
 Key: INCUBATOR-126
 URL: https://issues.apache.org/jira/browse/INCUBATOR-126
 Project: Incubator
  Issue Type: Improvement
Reporter: Alan Cabrera


We should make it more clear in the documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (INCUBATOR-126) Sometimes its not clear that the who vets the podling name

2013-05-27 Thread Alan Cabrera (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667806#comment-13667806
 ] 

Alan Cabrera commented on INCUBATOR-126:


That's a good idea.  I think we should prefer concrete nouns instead of vague 
pronouns, i.e. the podling's PPMC and community.

 Sometimes its not clear that the who vets the podling name
 --

 Key: INCUBATOR-126
 URL: https://issues.apache.org/jira/browse/INCUBATOR-126
 Project: Incubator
  Issue Type: Improvement
Reporter: Alan Cabrera

 We should make it more clear in the documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

What's the difference between dormant and retired?

2013-05-27 Thread Alan Cabrera

Looking at the podlings.xml and it's not clear to me what the difference is.  
I'm sure I neglected to read some documentation bit.


Regards,
Alan


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

Re: What's the difference between dormant and retired?

2013-05-27 Thread Alan Cabrera

They kinda sound the same.  Why didn't podlings want to retire?  Does anyone 
know?


Regards,
Alan

On May 27, 2013, at 9:14 AM, Christian Grobmeier grobme...@gmail.com wrote:

 I asked the same question in july 2011, and got a response from Henri
 Yandell which I repost here:
 
 Given the PPMC is closed down, I think it has to be retired.
 
 Dormant implies a PPMC is taking some time off.
 
 Basically this is a larger version of don't be afraid to delete a
 line of code; it's in version control.
 
 Hen
 
 
 
 
 
 On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera a...@toolazydogs.com wrote:
 Looking at the podlings.xml and it's not clear to me what the difference is. 
  I'm sure I neglected to read some documentation bit.
 
 
 Regards,
 Alan
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 -- 
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 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: What's the difference between dormant and retired?

2013-05-27 Thread Alan Cabrera

Yeah, I like the word dormant as well.  Should we rename them all to dormant?


Regards,
Alan

On May 27, 2013, at 10:32 AM, Upayavira u...@odoko.co.uk wrote:

 I think it was just a question of 'retiring' sounding too final. Using
 the word 'dormant' was less threatening, and made it more feasible for
 the podlings to go, well, dormant.
 
 Upayavira
 
 On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
 They kinda sound the same.  Why didn't podlings want to retire?  Does
 anyone know?
 
 
 Regards,
 Alan
 
 On May 27, 2013, at 9:14 AM, Christian Grobmeier grobme...@gmail.com
 wrote:
 
 I asked the same question in july 2011, and got a response from Henri
 Yandell which I repost here:
 
 Given the PPMC is closed down, I think it has to be retired.
 
 Dormant implies a PPMC is taking some time off.
 
 Basically this is a larger version of don't be afraid to delete a
 line of code; it's in version control.
 
 Hen
 
 
 
 
 
 On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera a...@toolazydogs.com wrote:
 Looking at the podlings.xml and it's not clear to me what the difference 
 is.  I'm sure I neglected to read some documentation bit.
 
 
 Regards,
 Alan
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 -- 
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 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
 


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

Re: The Only Thing Wrong - Execution of Process

2013-05-15 Thread Alan Cabrera

I think there's some good ideas here.  You should capture them in

http://wiki.apache.org/incubator/IncubatorIssues2013 


Regards,
Alan

On May 15, 2013, at 7:51 AM, Dave Fisher dave2w...@comcast.net wrote:

 Hi -
 
 I've been incredibly busy, but to me the main thing wrong in the Incubator is 
 focusing on what might be wrong rather than executing on the process we 
 already have (or had).
 
 Shepherds worked when they were assigned at random by the IPMC chair well in 
 advance of the report. This helps to focus on the actual podling reports. 
 They don't work when self-selected.
 
 Rather than discussing specific issues with podlings that are mentor-less or 
 report-less we are engaging in distracting discussions.
 
 Can we please just execute on reporting for the first two weeks of every 
 month?
 
 Regards,
 Dave
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: Writing some tooling

2013-05-14 Thread Alan Cabrera


On May 10, 2013, at 10:58 AM, Alan Cabrera a...@toolazydogs.com wrote:

 I'm currently writing some tooling to help with the incubation process as 
 well as mail list moderator tools.
 
 The first thing that I'm writing is a command that will print out who is the 
 owner of an email alias and what projects they belong to and if they are ASF 
 members.  This will help me vet subscription requests since people rarely use 
 their ASF email accounts.
 
 The tools will be written in Python. 


I'm done with this tool.  It also sends a rejected email to the user informing 
them that they are not allowed to subscribe.  Things I need in this email are:

URL of a web page describing out to add an alias to an account
URL of a web page describing mailing list membership policies

If these don't exist I am happy to write them.

A bunch of the Python utilities that I'm using are from LinkedIn and I'm in the 
process of vetting the code.  I'll check it in as soon as that's done:

https://svn.apache.org/repos/asf/incubator/public/trunk/tools

I'm now going to replace the mentors' names in podling.xml with their usernames 
and fix the corresponding web/reporting generation bits.  Any pointers would be 
welcome.


Regards,
Alan

Re: [ANNOUNCE] Joe Brockmeier joins the Incubator PMC

2013-05-13 Thread Alan Cabrera

Welcome aboard!


Regards,
Alan

On May 13, 2013, at 5:06 PM, Noah Slater nsla...@apache.org wrote:

 Dear community,
 
 I am pleased to announce that Joe Brockmeier joins the Incubator PMC.
 
 Please join me in extending a warm welcome to Joe!
 
 On behalf of the Incubator PMC,
 
 -- 
 NS


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

Re: [VOTE] Release JSPWiki version 2.9.1-incubating (2nd RC)

2013-05-13 Thread Alan Cabrera

Don't let me stop the vote but I'm getting 

java.lang.OutOfMemoryError: Java heap space

when I run the tests, mvn clean install.  My MAVEN_OPTS is:

-Xms2G -Xmx2G -XX:PermSize=1G -XX:MaxPermSize=1G

Am I doing something wrong?  


Regards,
Alan

On May 7, 2013, at 2:16 PM, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi all,
 
 We've held a vote on jspwiki-dev for a 2nd RC of Apache JSPWiki
 2.9.1-incubating [#1].
 
 The vote on release candidate has been open for more than 72 hours on the
 developer mailing list. After the voting timeframe, we have 3 non-binding
 votes (from jspwiki developers).
 
 I'd therefore like to ask now the general incubator to check our release
 candidate. The release notes (fixed issues) are available at the Jira Issue
 Tracker [#2].
 
 Please find attached below the concrete details on the release and on the
 vote.
 
 thanks in advance,
 juan pablo
 
 
 [#1] http://s.apache.org/UDD
 [#2]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249
 ===
 
 Note that we are voting upon the source (subversion tag and signed
 artifacts). Binaries are provided for convenience only.
 
 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc2
 
 Source and binary files, with RAT report:
 http://people.apache.org/~juanpablo/releases/2.9.1-incubating-4-rc2/
 
 Checksums:
 
 JSPWiki-2.9.1-incubating-4-bin.zip
 MD5:58b7e2fd9290612762825683e81ca22d
 SHA1:   5eb4cfa7c7b00e2a002573c72f1e83c15f708e2b
 SHA512:
 0e1487d09044e0ce900194b42ff3e465ee96ebde1a75c0603715ec42bbf425b950c901bff87bbadf43173d3c91ced170ab0eebe4525706344642e68db069ba18
 
 JSPWiki-2.9.1-incubating-4-src.zip
 MD5:707b52ce9ca32fe012bcc3b1a79d8f96
 SHA1:   41619359a04d49a2f5b58b8ba1a5d0c186fbbb1c
 SHA512:
 2c4f6e0b9e163d2b3ae60a091993598ed6e315a7f7b4c08a9232cbd0c1eccba4259818e0e9ab8a86350a0109924be21cc0627e8a549bbd52b14ca7b40dcccee0
 
 JSPWiki's KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/incubator/jspwiki/KEYS
 
 [ ] +1 Release this package as Apache JSPWiki 2.9.1-incubating
 [ ]  0 I don't feel strongly about it, but I'm okay with the release
 [ ] -1 Do not release this package because...


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

Re: [ANNOUNCE] Release Curator 2.0.0-incubating released

2013-05-12 Thread Alan Cabrera

Sebb you are awesome and correct.

But I have to say, I think that when we make suggestions to podlings, we should
make it clear that we are making suggestions and are not pointing out some ASF
Incubator transgression. This is one such cases where Sebb us making a very
useful suggestion.

Again, Sebb you are awesome.

Regards,
Alan

On May 11, 2013, at 1:00 AM, sebb seb...@gmail.com wrote:

Congrats.

However, what is Curator?

The mail does not say anything about it.

Please ensure that any announcement e-mails about Curator include a
brief description of what it is.

On 10 May 2013 17:47, Jordan Zimmerman randg...@apache.org wrote:
Hello,

The Apache Curator team is pleased to announce the release of version
2.0.0-incubating from the Apache Incubator.

Curator was originally open sourced by Netflix via Github. This is the first
Apache release of Curator. I'd like to thank the mentors for their help in
getting to this milestone. In particular, Patrick Hunt and Luciano Resende
have been incredibly helpful and patient.

Link to release notes:
https://issues.apache.org/jira/browse/CURATOR#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel

The most recent source release can be obtained from an Apache Mirror:
http://www.apache.org/dyn/closer.cgi/incubator/curator/
(mirror sync times may vary)

The binary artifacts for Curator are available from Maven Central and its
mirrors.

For general information on Apache Curator, please visit the project website:
http://curator.incubator.apache.org

Disclaimer:
Apache Curator is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Incubator PMC.

Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process
have stabilized in a manner consistent with other successful ASF projects.

While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

-Jordan

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

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-11 Thread Alan Cabrera


On May 11, 2013, at 7:26 AM, ant elder ant.el...@gmail.com wrote:

 I also agree that there isn't consensus in the Incubator PMC to do
 this, but I'm not sure we need it. 

Lovely.


Regards,
Alan

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-11 Thread Alan Cabrera


On May 11, 2013, at 5:40 AM, Benson Margulies bimargul...@gmail.com wrote:

 A real experiment with 'probationary projects' would have to model the
 entire process of a new project launching with  _no IPMC_ to
 participate in any way.

Can you explain what problem launching new projects with _no IPMC_ to 
participate in any way solves?  Maybe this is where the disconnect is.  Is the 
IPMC the problem or is it the lack of mentors the problem?

What are the core problems that you are trying to solve?

 Taking a proposal that has been groomed and
 vetted at the IPMC and then launching the resulting project to the
 board is purely an experiment in board supervision.

Can you explain what is it about the board that's better than having the board 
members with the spare bandwidth coming over to the IPMC to help?  What is it 
about the auspices of the board that improves things?  What is the exact 
problem that this solves?

 My personal thought is this: new project creation is not a 'project',
 it's a function of the Foundation. If the committee currently
 constituted by the board to handle this isn't working well enough, and
 can't agree on what to do, it is an issue for the board to consider.
 The board could decide to keep what we are, arguments and all. It
 could constitute a small (and thus consensus-prone) committee to
 survey the terrain and make a recommendation. It could tell the whiney
 VP to JFDI -- make some decisions and get on with it. (Consensus is
 desirable, but read one of the board resolutions that installs a VP.)

That depends on what the problem is.  If the IPMC is paralyzed then yes, the 
board should step in.  I didn't realize that we're there already.  If we are 
then please be explicit about it.

But I don't understand why we can't go through the simple exercise that I 
propose to see where we have points in common.  I think that doing so will go a 
long way to generating good will, as people's positions will be analyzed down 
to their core, and provide better transparency as to what people's motivations 
are.

I'm saying this because I really don't understand why people are espousing 
these various solutions.  I want to understand but at the moment it just seems 
that people are holding on to their positions without explaining their thoughts 
down to the core problems that they think they are trying to solve.

In the end, I think if we're really serous about this we'll end up with bits of 
everyone's proposals.


Regards,
Alan

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-11 Thread Alan Cabrera


On May 11, 2013, at 9:44 AM, Benson Margulies bimargul...@gmail.com wrote:

 Violating my 24 hour rule just this one, and worse yet to repeat myself:

IMO, I think this is fine so long as it occurs on the weekend.  :)

 +1 Joe, Ross, etc.
 
 I rather regret mentioning the direct launch alternative in my most
 recent email. We have some weakness in _mentoring_,

Agreed.

 and more weakness
 in _supervising_ (or at least in documenting supervision).

Could tooling help here?

 We have a
 few competing proposals for changes to address these, especially
 supervision weakness.

Is the reporting problem the sole issue?

 I wish that I felt confident as Joe does that
 just electing more people from inside the projects was all we needed
 to do; maybe Alan's idea combined with that is the way to go.

I'm not sure which way to go but I'm really liking the direction of this email. 
 I feel that I'm getting a sense of what you feel are the core problems we're 
trying to solve.

 Recently we had a situation on private where I felt that there was a
 consensus to be had, but some people needed to be nudged a bit to
 allow it to emerge. That's not what I see here when considering the
 choices of using more or less of shepherds, champions, and mentors.

I think that a lot of members didn't read it, thinking that there was yet 
another email storm to ignore.

This was the point that I was trying to make in my earlier emails.  *It is the 
constant churning of roles and processes that is exhausting this IPMC, not the 
actual work.*  It is this bureaucratic churning that's sapping the emotional 
energy if the IPMC members.

Why are we churning?  Because we are not holding members/mentors up to their 
commitments.  Because we are constantly coming up w/ new ad hoc exceptions for 
every policy we have.

We need less process.  Less roles.  More accountability.  More tooling.

 One possible path is that, at some point, I as VP pick one. I plan to
 let this discussion continue for at least a week, if not more, before
 I remotely consider taking that step.

Ultimately we voted you in to be our VP.  I feel that you are listening to our 
concerns.  I'll support what ever your decision is even if I don't agree. 

 I think it's clear, though, that _this committee_ does not believe in
 the 'direct-to-PMC' model, so anyone interested in that alternative
 should talk elsewhere and/or with the board, as per Ant's message.

What this direct to PMC model?


Regards,
Alan



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

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-11 Thread Alan Cabrera


On May 11, 2013, at 7:33 AM, Joseph Schaefer joe_schae...@yahoo.com wrote:

 Frankly I find the notion that the board will do a better job of MENTORING
 these projects than the IPMC to be batshit insane, but that's just me.
 We need manpower, and there is plenty of that available amongst the competent
 volunteers who actively participate in these projects.  Let's just do
 what's easiest for once and promote these folks to the IPMC in order
 to get the job done right.  It's a proven model that we need to stop
 fighting.


Yes, shuttling the kids off the the grandparents is not going to solve 
anything.  If individuals on the board have the bandwidth to help they should 
come over here. There's nothing specific about the auspices of the board that 
would improve the situation.

I personally think that we have almost enough people to mentor.  I think that 
the burnout comes from our constant churning of policy and lack of tooling to 
make mundane tasks easier.

For example, maybe
better reminders for reports
automatic nudging of mentors who have not signed reports
dead pilot buttons to detect inactive mentors (Is it called a dead pilot button)
maybe a standard to podling releases to make vetting easier - i.e. apply tooling
changes/additions to vetting procedures taking place outside of release votes. 
(ok not a tooling issue)


Regards,
Alan

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-11 Thread Alan Cabrera


On May 11, 2013, at 11:03 AM, Dennis E. Hamilton dennis.hamil...@acm.org 
wrote:

 It's often called a dead-man's switch.  I think the term applied originally 
 to locomotive engineers and also metro car drivers.  (I'm not sure what a 
 dead pilot switch could accomplish in an aircraft.)
 
 I think having mentors review and sign PPMC status reports is an effective 
 dead mentor's switch [;).

Ahh, yeah, that was it.  I was also thinking that voting releases would be it 
as well.  The tooling would make the tracking automatic so the mundane task of 
tracking all the mentors for all the podlings would be automatic.


Regards,
Alan


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

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-10 Thread Alan Cabrera


On May 10, 2013, at 9:25 AM, Benson Margulies bimargul...@gmail.com wrote:

 So, here we have:
 
 Alan's idea of removing champions and shepherds and demanding mentor
 recommitment, with the 'teeth' of putting podlings on ice if they
 can't muster an adequate mentor squad.
 
 My idea of asking champions to step up to some specific supervision
 responsibility, thus allowing some flexibility for some mentors to be
 more 'supervisory' than others.
 
 Ross' ideas about shepherds,
 
 Chris' proposal to push the self-destruct button.
 
 Does anyone have a suggestion for a decision procedure?  I don't see,
 or foresee, a consensus for any of these.
 
 My draft board report says that if we don't find a way forward in time
 for the June board meeting, I propose to discuss the situation with
 the board.

When ever I'm in a situation like this, I find it helpful to write down what 
are the core problems that we're trying to solve.  The trick is to use 
something like 5 whys to get down to the core set w/out getting distracted.

Once you get down to the core problems you weight them.

Break down people's proposals into as small as possible, self contained, 
actionable, bits.

Grade each bit as to how well it solves a core problem.

By then, it's obvious what bits to pick up; the simplest ones at the top.


Regards,
Alan

Re: [META DISCUSS] talking about the overall state of this PMC

2013-05-10 Thread Alan Cabrera

Lean startup approaches make sense when you do not know the problem that you're 
solving.  You perform experiments and pivot as you blindly search for a domain 
whose problems you can solve and make money doing it.

Here, we know what our problems are.

This is not to say that we should not collect metrics.  

However, we barely have enough energy to keep things going as it is.  We don't 
have the bandwidth to perform multiple experiments. 


Regards,
Alan


On May 10, 2013, at 9:33 AM, Eric Johnson e...@tibco.com wrote:

 If this was a software project, and the appropriate answer was unknown, they 
 you might apply a lean startup approach, and figure out how to run tests to 
 see which way works best.
 
 Given the number of incubating projects, should be easy to run some 
 experiments. Then you just need to build up some consensus on how to run the 
 experiments. And how to evaluate the results. Essential to establish some 
 metrics that will correlate with success. Then run the experiments for a 
 while (three months, six months?). At the end, you'll have actual data that 
 will inform a decision.
 
 Eric.
 
 On 5/10/13 9:25 AM, Benson Margulies wrote:
 So, here we have:
 
 Alan's idea of removing champions and shepherds and demanding mentor
 recommitment, with the 'teeth' of putting podlings on ice if they
 can't muster an adequate mentor squad.
 
 My idea of asking champions to step up to some specific supervision
 responsibility, thus allowing some flexibility for some mentors to be
 more 'supervisory' than others.
 
 Ross' ideas about shepherds,
 
 Chris' proposal to push the self-destruct button.
 
 Does anyone have a suggestion for a decision procedure?  I don't see,
 or foresee, a consensus for any of these.
 
 My draft board report says that if we don't find a way forward in time
 for the June board meeting, I propose to discuss the situation with
 the board.
 
 


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

Re: May 2013 Report

2013-05-10 Thread Alan Cabrera

I think that you should make it clear that the Marvin machinery broke down and 
projects did not get their notifications.


Regards,
Alan

On May 10, 2013, at 9:21 AM, Benson Margulies bimargul...@gmail.com wrote:

 I wrote some text at the front. I plan to fill in things like PMC
 members coming and going tomorrow morning, and commit to svn.
 
 -
 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

1 2 >

1 - 100 of 192 matches

Mail list logo