Re: Blog policy for poddlings
My understanding is that only TLPs can publish to blogs.a.o. With that said, I know several projects have published their own blogs during incubation (including Apache Mesos and Apache Aurora) on their websites during incubation using Middleman CMS. For example, here's a post that was generated for Aurora when it was still part of the incubator: http://aurora.apache.org/blog/aurora-0-7-0-incubating-released/ The full source of the middleman CMS is available on the Aurora SVN directory: https://svn.apache.org/repos/asf/aurora/site/, with the necessary blog module installed -- happy to help generalize this if it's something you'd like to reuse. Hope that helps! Dave On Thu, May 28, 2015, at 06:36 PM, Roman Shaposhnik wrote: > Hi! > > can someone please remind me what's the policy > for letting poddlings use blogs.apache.org as a > blogging platform? > > 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: [VOTE] Accept Mysos into the Apache Incubator
alaried Developers > > It is expected that Mysos development will occur on both salaried time > and on volunteer time, after hours. The majority of initial committers > are paid by their employers to contribute to this project. However, > they are all passionate about the project, and we are confident that > the project will continue even if no salaried developers contribute to > the project. We are committed to recruiting additional committers > including non-salaried developers. > > Relationships with Other Apache Products > > Mysos depends on Apache Mesos. The Mysos team will work closely with > the Apache Mesos community to ensure the proper stateless primitives > are in place to enable MySQL to run on Apache Mesos. > > An Excessive Fascination with the Apache Brand > > Mysos is a new open source project and the primary benefits to joining > Apache are those outlined in the Rationale section. > > Documentation > > Documentation is currently located as README markdown files: > > /README.md /docs/user-guide.md > > Additional will continue to be added to the project. > > Source and Intellectual Property Submission Plan > > The Mysos codebase is currently hosted on Github: > https://github.com/twitter/mysos. > > These are the codebases that we would migrate to the Apache > foundation. > > External Dependencies > > All Mysos dependencies have Apache compatible licenses. > > Cryptography > > We do not expect Mysos to be a controlled export item due to the use > of encryption. > > Required Resources > > Mailing lists > > priv...@mysos.incubator.apache.org comm...@mysos.incubator.apache.org > d...@mysos.incubator.apache.org Subversion Directory > > Git is the preferred source control system: > > git://git.apache.org/mysos > > Issue Tracking > > We'd like to use JIRA for issue tracking with project key MYSOS and > Review Board for our code reviews. > > Initial Committers > > Chris Aniszczyk Vinod Kone at apache dot org> Dave Lester Yan Xu at twitter dot com> Tobi Knaup Sunil Shah > Jake Farrell > > Affiliations > > Chris Aniszczyk (Twitter) Vinod Kone (Twitter) Dave Lester (Twitter) > Yan Xu (Twitter) Tobi Knaup (Mesosphere) Sunil Shah (Mesosphere) Jake > Farrell (Acquia) > > Sponsors > > Champion > > Jake Farrell > > Nominated Mentors > > Dave Lester Benjamin Hindman apache dot org> Henry Saputra (hsaputra at apache dot org) > > Sponsoring Entity > > The Apache Incubator
Re: [DRAFT] May 2015 Board Report
Hi Tim, I found Konstantin's comment to be helpful. Could it have provided additional details? Sure. But I don't think there's a need to make this personal. Shepherd comments tend to be quite brief. We should celebrate volunteer efforts instead of calling others "unhelpful and lazy." Dave On Mon, May 11, 2015, at 08:21 PM, Tim Williams wrote: > On Mon, May 11, 2015 at 10:11 PM, Konstantin Boudnik > wrote: > > > - Blur: Human activity on Dev list is almost zero: high 90% of the emails > > are from CI system or JIRA notificaitons. > > Human's drive nearly all of that traffic. What is your point? > Honestly, this shepherd comment seems unhelpful and lazy. I'd suggest > it's better to admit that you've run out of time than offer mediocre > shepherd comments. > > --tim > > - > 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] Mysos Incubation proposal
Thanks all for your feedback thus far. I'm open to name changes, particularly since this is early in the project's life and it would create few issues. The initial list of committers will be touching base tomorrow morning and we'll be sure to bring this up and report back on any potential name changes. In the meantime, are there other questions / comments / concerns regarding the proposal? Thanks, Dave On Mon, May 11, 2015, at 07:19 AM, Bertrand Delacretaz wrote: > On Mon, May 11, 2015 at 2:00 PM, Bertrand Delacretaz > wrote: > > ...having such confusing names for Apache projects is not a good idea > > IMO... > > Just to make sure people realize the amount of possible confusion > between the Mesos and Mysos names: in french, the letter "y" is > pronounced very much like "e" in english. I'm not saying any of our > french colleagues have an accent, but if they did you might get the > exact same sound. > > Much too confusing IMO...fun names might sound appealing initially and > bite you in the back later. > > Or you need to get people used to calling those projects Mike Echo and > Mike Yankee ;-) > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Mysos Incubation proposal
in place to enable MySQL to run on Apache Mesos. === An Excessive Fascination with the Apache Brand === Mysos is a new open source project and the primary benefits to joining Apache are those outlined in the Rationale section. == Documentation == Documentation is currently located as README markdown files: /README.md /docs/user-guide.md Additional will continue to be added to the project. == Source and Intellectual Property Submission Plan == The Mysos codebase is currently hosted on Github: https://github.com/twitter/mysos. These are the codebases that we would migrate to the Apache foundation. == External Dependencies == All Mysos dependencies have Apache compatible licenses. == Cryptography == We do not expect Mysos to be a controlled export item due to the use of encryption. == Required Resources == === Mailing lists === * priv...@mysos.incubator.apache.org * comm...@mysos.incubator.apache.org * d...@mysos.incubator.apache.org == Subversion Directory == Git is the preferred source control system: * git://git.apache.org/mysos == Issue Tracking == We'd like to use JIRA for issue tracking with project key MYSOS and Review Board for our code reviews. == Initial Committers == * Chris Aniszczyk * Vinod Kone * Dave Lester * Yan Xu * Tobi Knaup * Sunil Shah * Jake Farrell == Affiliations == * Chris Aniszczyk (Twitter) * Vinod Kone (Twitter) * Dave Lester (Twitter) * Yan Xu (Twitter) * Tobi Knaup (Mesosphere) * Sunil Shah (Mesosphere) * Jake Farrell (Acquia) == Sponsors == === Champion === * Jake Farrell === Nominated Mentors === * Dave Lester * Benjamin Hindman * Henry Saputra (hsaputra at apache dot org) === Sponsoring Entity === The Apache Incubator - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Parquet from the Incubator
+1 (binding) On Mon, Apr 13, 2015, at 10:46 AM, Julien Le Dem wrote: > +1 (non-binding) > > Julien > > > On Apr 13, 2015, at 08:46, Jake Farrell wrote: > > > > This thread is to start a vote on the graduation resolution Apache Parquet > > has approved on the dev list with 14 positive votes (11 PPMC (4 from IPMC > > members), 3 community) > > > > Status page: http://incubator.apache.org/projects/parquet.html > > Graduation discussion: http://s.apache.org/8qU > > Graduation resolution: http://s.apache.org/w7 > > > > Apache Parquet has been apart of the Incubator since May 2014 and in that > > time has > > > > * Had successful IPMC approved releases > > * Expanded the PPMC with new members > > * Worked and submitted fixes in other Apache projects to improve Parquet > > support > > * A successful community vote to graduate with 14 positive votes > > > > I would like to get the voting started with my own +1 > > > > Please vote > > > > [ ] +1 Graduate Apache Parquet as a TLP > > [ ] +0 > > [ ] -1 Don't graduate Apache Parquet as a TLP because… > > > > Voting will end in 72 hours, i.e. 12:00 UTC on 2015-04-16 > > http://www.timeanddate.com/countdown/to?iso=20150416T12 > > > > -Jake > > > > > > > > === Board Resolution == > > > > Establish the Apache Parquet 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 columnar storage format for Hadoop. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache Parquet Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache Parquet Project be and hereby is > > responsible for the creation and maintenance of software > > related to a columnar storage format for Hadoop; and be it further > > > > RESOLVED, that the office of "Vice President, Apache Parquet" 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 Parquet Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache Parquet 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 Parquet Project: > > > > * Chris Aniszczyk > > * Ryan Blue > > * Jonathan Coveney > > * Tianshuo Deng > > * Jake Farrell > > * Marcel Kornacker > > * Mickael Lacour > > * Julien Le Dem > > * Alex Levenson > > * Nong Li > > * Todd Lipcon > > * Chris Mattmann > > * Aniket Mokashi > > * Lukas Nalezenec > > * Brock Noland > > * Wesley Graham Peck > > * Remy Pecqueur > > * Dmitriy Ryaboy > > * Roman Shaposhnik > > * Daniel Weeks > > * Tom White > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julien Le Dem > > be appointed to the office of Vice President, Apache Parquet, 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 Parquet 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 Parquet Project; and be it further > > > > RESOLVED, that the Apache Parquet Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator Parquet podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator Parquet 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] Accept Groovy into the Apache Incubator
+1 (non-binding) On Thu, Mar 19, 2015, at 09:32 PM, Ted Dunning wrote: > +1 (binding) > > > > On Thu, Mar 19, 2015 at 5:57 PM, Mattmann, Chris A (3980) < > chris.a.mattm...@jpl.nasa.gov> wrote: > > > +1 (binding) from me! :) G’luck! > > > > ++ > > Chris Mattmann, Ph.D. > > Chief Architect > > Instrument Software and Science Data Systems Section (398) > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 168-519, Mailstop: 168-527 > > Email: chris.a.mattm...@nasa.gov > > WWW: http://sunset.usc.edu/~mattmann/ > > ++ > > Adjunct Associate Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++ > > > > > > > > > > > > > > -Original Message- > > From: Roman Shaposhnik > > Reply-To: "general@incubator.apache.org" > > Date: Wednesday, March 18, 2015 at 11:55 PM > > To: "general@incubator.apache.org" > > Subject: [VOTE] Accept Groovy into the Apache Incubator > > > > >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
Re: [VOTE] Accept Myriad into the Apache Incubator
+1! On Sun, Feb 22, 2015, at 04:45 PM, Chris Douglas wrote: > +1 (binding) -C > > On Sat, Feb 21, 2015 at 9:34 PM, Adam Bordelon > wrote: > > Hello friends, > > > > After receiving a positive response on the discussion thread, and even a > > new Mentor (Luciano), I would like to call a VOTE to accept Myriad into the > > Apache Incubator. I will end the vote after 7 days. > > > > https://wiki.apache.org/incubator/MyriadProposal?action=recall&rev=7 > > > > [ ] +1 Accept Myriad into the Incubator > > [ ] +0 Don’t care. > > [ ] -1 Don’t accept Myriad into the Incubator because.. > > > > I am clearly a +1. > > > > Thanks, > > -Adam- > > me@apache > > - > 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
+1 (non-binding) On Tue, Feb 11, 2014 at 8:31 AM, Sean McNamara wrote: > +1 !!! > > On 2/10/14, 9:27 PM, "Chris Mattmann" 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 > >* Jason Dai > >* Tathagata Das > >* Ankur Dave > >* Aaron Davidson > >* Thomas Dudziak > >* Robert Evans > >* Thomas Graves > >* Andy Konwinski > >* Stephen Haberman > >* Mark Hamstra > >* Shane Huang > >* Ryan LeCompte > >* Haoyuan Li > >* Sean McNamara > >* Mridul Muralidharam > >* Kay Ousterhout > >* Nick Pentreath > >* Imran Rashid > >* Charles Reiss > >* Josh Rosen > >* Prashant Sharma > >* Ram Sriharsha > >* Shivaram Venkataraman > >* Patrick Wendell > >* Andrew Xia > >* Reynold Xin > >* Matei Zaharia > > > >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 > >
[RESULT][VOTE] Aurora accepted for Apache incubation
The vote for Aurora to become an incubated project has passed with 8 +1 binding votes, 8 +1 non-binding votes, and no -1 or 0 votes. *Binding +1 Votes:* Jake Farrell Henry Saputra Benjamin Hindman Chris Mattmann Alan D. Cabrera Andrei Savu Olivier Lamy Bertrand Delacretaz *Non-Binding +1 Votes:* Dulitha R. Wijewantha Ashish Paliwal Milinda Pathirage Nirmal Fernando Ross Allen Vinod Kone Andy Konwinski Benjamin Mahler Congrats to all involved! Best, Dave
[VOTE] Accept Aurora for Apache Incubation
tation of the Apache brand and have no doubts that it will attract contributors and users, our interest is primarily to give Aurora a solid home as an open source project following an established development model. We have also given reasons in the Rationale and Alignment sections. = Documentation = This proposal exists online as http://wiki.apache.org/incubator/AuroraProposal. Basic build instructions are included in the existing github repository, and the source code has thorough documentation. User documentation exists internally to Twitter, and as part of incubation will be adapted to share and improve user documentation overall. = Initial Source = JIRA Aurora (AURORA) = Source and Intellectual Property Submission Plan = A snapshot of the Aurora scheduler has been posted on github for review: https://github.com/twitter/aurora = External Dependencies = All Aurora dependencies have Apache compatible licenses. = Cryptography = Not applicable. = Required Resources = == Mailing Lists == * aurora-private for private PMC discussions * aurora-dev * aurora-commits == Subversion Directory == We prefer to use Git as our source control system: git:// git.apache.org/aurora == Issue Tracking == JIRA Aurora (AURORA) = Initial Committers = * Jonathan Boulle (jon at twitter dot com) * William Farner (bill at twitter dot com) * Suman Karumuri (skarumuri at twitter dot com) * Maxim Khutornenko (mkhutornenko at twitter dot com) * Dave Lester (dlester at twitter dot com) * Kevin Sweeney (ksweeney at twitter dot com) * Brian Wickman (wickman at twitter dot com) = Affiliations = Twitter = Sponsors = == Champion == * Benjamin Hindman (benh at apache dot org) == Nominated Mentors == * Jake Farrell (jfarrell at apache dot org) * Benjamin Hindman (benh at apache dot org) * Chris Mattmann (mattmann at apache dot org) * Henry Saputra (hsaputra at apache dot org) == Sponsoring Entity == Incubator PMC
Re: [ANNOUNCE] Ben Hindman as Apache Incubator PMC member!
Congrats, Ben! On Wed, Sep 4, 2013 at 11:52 AM, Chris Mattmann wrote: > Hi Folks, > > The IPMC has VOTEd to add Ben Hindman as an Apache Incubator PMC > member. Welcome Ben! > > Please feel free to say a bit about yourself. > > Cheers, > Chris > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Aurora for Incubation
We can always add new mailing lists based upon need, so I'm fine with dev@, private@, and commits@. The change is reflected in the wiki. Best, Dave On Wed, Aug 28, 2013 at 4:10 PM, Mattmann, Chris A (398J) < chris.a.mattm...@jpl.nasa.gov> wrote: > Sure, makes sense to me. > > 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: Henry Saputra > Reply-To: "general@incubator.apache.org" > Date: Wednesday, August 28, 2013 4:08 PM > To: "general@incubator.apache.org" > Subject: Re: [PROPOSAL] Aurora for Incubation > > >Hi Marvin, Dave, > > > >+1 for dev@, private@ and commits@ lists for start. > > > >If Aurora picks up more clients as "user" which making dev@ list too > noisy > >we could always request for user@ list. > > > >- Henry > > > > > >On Wed, Aug 28, 2013 at 9:37 AM, Marvin Humphrey > >wrote: > > > >> On Tue, Aug 27, 2013 at 4:36 PM, Dave Lester > > >> wrote: > >> > We recommended an aurora-user list because Aurora is currently > >> > production-ready and used by Twitter. We anticipate that once we have > >>an > >> > initial release in the Incubator, it will be straightforward to for > >> current > >> > Mesos users to begin using Aurora. Development discussion would still > >> made > >> > on aurora-dev. How does that sound? > >> > >> See <http://wiki.apache.org/incubator/MailingListOptions>. > >> > >> For small-ish projects, we recommend that user traffic be shunted onto > >>the > >> dev > >> list at first because we have observed that great new contributors tend > >>to > >> emerge from the pool of highly engaged users. You want to foster > >> conversations which flow seemlessly from "how do I do this" to "how do I > >> implement this" to "welcome new committer so-and-so". Breaking out a > >> separate > >> user@ list is not generally desirable until the project has hit > critical > >> mass > >> and dev list traffic is high. > >> > >> Community growth is a difficult problem that is central to the Apache > >> mission, > >> and it will be an important challenge for the proposed Aurora podling > >>since > >> all the initial contributors work for the same company (Twitter). It > >>will > >> be > >> tempting to make architectural decisions in private for the sake of > >> efficiency, but doing so will stunt the project's growth. It's > >>important > >> to > >> hold project discussions out in the open where as many people as > >>possible > >> can > >> witness them and potentially jump in. > >> > >> The issues/notifications/ci list is a different story. Making the dev > >> list a > >> good read with a high signal-to-noise ratio is a good recruitment > >>tactic. > >> There are often people who are interested in high-level development > >> conversations and user discussions but who get annoyed by CI spam and > >>issue > >> tracker trivialities. > >> > >> In my opinion, it would be fruitful to start off with just dev@, > >>private@and > >> commits@ lists; discuss adding a notifications@ list as one of the > first > >> community decisions you make on your dev@ list; and perhaps add a > >>user@list > >> later when the time is ripe. However, all of these decisions are > >> ultimately > >> up to the community; us Incubator denizens are just providing the best > >> guidance we can based on what seems to have worked in the past. > >> > >> Marvin Humphrey > >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Aurora for Incubation
Hi Chris, On Mon, Aug 26, 2013 at 8:01 PM, Chris Mattmann wrote: > Mentors and Champions need to be on the IPMC Thanks for your help, and good catch. We welcome more volunteers as mentors or as a champion. Dave
Re: [PROPOSAL] Aurora for Incubation
Hi Henry, On Mon, Aug 26, 2013 at 4:23 PM, Henry Saputra wrote: > > Another question: looks like from the proposal, it does not rely on Mesos > library as external dependencies at all? > Aurora does rely on Mesos as a dependency, as it is an implementation of a Mesos framework. Like other incubator projects, would you consider not having aurora-user > and aurora-issues lists at the beginning of incubation? > We recommended an aurora-user list because Aurora is currently production-ready and used by Twitter. We anticipate that once we have an initial release in the Incubator, it will be straightforward to for current Mesos users to begin using Aurora. Development discussion would still made on aurora-dev. How does that sound? Dave
Re: [PROPOSAL] Aurora for Incubation
On Tue, Aug 27, 2013 at 3:01 PM, Donald Whytock wrote: > So Aurora already exists as a functioning package? > Yes, Aurora is currently used in production at Twitter. > Is there a public-accessible project page for it somewhere? > Not yet, but should the project be voted as an incubated project we will get one online ASAP. Dave
Re: [PROPOSAL] Aurora for Incubation
Hi Jean-Baptiste, The focus is currently on Mesos. Our intent is to make it a sub-project. Dave On Mon, Aug 26, 2013 at 11:52 PM, Jean-Baptiste Onofré wrote: > Hi guys, > > the proposal is interesting. > Quick question: do you plan to focus only on Mesos, or create a kind of > more global and standalone job scheduler ? > > Regards > JB > > > On 08/27/2013 12:27 AM, Dave Lester wrote: > >> Hi All, >> >> We're pleased to share a draft ASF incubation proposal for Aurora, a >> service scheduler used to schedule jobs onto Apache Mesos that we've >> developed at Twitter. Aurora provides all of the primitives necessary to >> quickly deploy and scale stateless and fault tolerant services in a >> datacenter. The complete proposal can be found: >> https://wiki.apache.org/**incubator/AuroraProposal<https://wiki.apache.org/incubator/AuroraProposal>, >> and also pasted below. >> >> In particular, we'd love to add additional mentors to the project. Your >> feedback is appreciated. >> >> Dave >> >
Re: [PROPOSAL] Aurora for Incubation
Hi Henry, Great question. Multiple schedulers are actively being developed for Mesos, including Aurora by Twitter, Chronos by Airbnb ( http://nerds.airbnb.com/introducing-chronos/), one called Marathon that I understand will be open sourced in the future, and I've spoken with several different folks at meetups who are developing their own. There is some overlap between these schedulers, but they also meet different use-cases so I still think it makes sense to create Aurora as a separate Apache project from the Mesos core. It's also worth noting (and perhaps this is something to highlight in the proposal itself) that a scheduler like Aurora could potentially be used with other systems should the community wish to pursue that development in the future. Dave On Mon, Aug 26, 2013 at 3:55 PM, Henry Saputra wrote: > Hi Dave, > > This looks like interesting project and good contributions from Twitter > engineering. > > But given that close relationship with Apache Mesos, wouldn't it be more > effective to be delivered as extension or feature contribution to Apache > Mesos? > > > - Henry > > > On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester wrote: > >> Hi All, >> >> We're pleased to share a draft ASF incubation proposal for Aurora, a >> service scheduler used to schedule jobs onto Apache Mesos that we've >> developed at Twitter. Aurora provides all of the primitives necessary to >> quickly deploy and scale stateless and fault tolerant services in a >> datacenter. The complete proposal can be found: >> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below. >> >> In particular, we'd love to add additional mentors to the project. Your >> feedback is appreciated. >> >> Dave >> >> = Abstract = >> >> Aurora is a service scheduler used to schedule jobs onto Apache Mesos. >> >> = Proposal = >> >> Aurora is a scheduler that provides all of the primitives necessary to >> quickly deploy and scale stateless and fault tolerant services in a >> datacenter. >> >> Aurora builds on top of Apache Mesos and provides common features that >> allow any site to run large scale production applications. While the >> project is currently used in production at Twitter, we wish to develop a >> community to increase contributions and see it thrive in the future. >> >> = Background = >> >> The initial development of Aurora was done at Twitter, and is planned to >> be >> open sourced. This proposal is for Aurora to join the Apache Incubator. >> >> = Rationale = >> >> While the Apache Mesos core focuses on distributing individual tasks >> across >> nodes in a cluster, typical services consist of dozens or hundreds of >> replicas of tasks. As a service scheduler, Aurora provides the abstraction >> of a "job" to bundle and manage these tasks. Aurora provides many key >> functionalities centered around a job, including: definition, the concept >> of an instance and the serverset, deployment and scheduling, health >> checking, and introspection. It also allows cross-cutting concerns to be >> handled like observability and log collection. >> >> = Current Status = >> >> == Meritocracy == >> >> By submitting this incubator proposal, we’re expressing our intent to >> build >> a diverse developer community around Aurora that will conduct itself >> according to The Apache Way and use meritocratic means of accepting >> contributions. Several members of the Aurora team overlap with Apache >> Mesos, which successfully graduated from the Incubator and has embraced a >> meritocratic model of governance; we plan to follow a similar path forward >> with Aurora and believe that a synergy between both projects will make >> this >> even easier. >> >> == Community == >> >> Aurora is currently being used internally at Twitter. By open sourcing the >> project, we hope to extend our contributor base significantly and create a >> vibrant community around the project. >> >> == Core Developers == >> >> Aurora is currently being developed by a team of seven engineers at >> Twitter. >> >> == Alignment == >> >> The ASF is a natural choice to host the Aurora project, given the goal of >> open sourcing the project and fostering a community to grow and support >> the >> software. Additionally, Aurora integrates with Apache Mesos, and Apache >> ZooKeeper for service discovery. >> >> We believe that inclusion within Apache will build stronger ties between >> these projects, and create
Re: [PROPOSAL] Aurora for Incubation
Excellent, thank you Jake! I will add your name to the proposal. Dave On Mon, Aug 26, 2013 at 3:47 PM, Jake Farrell wrote: > I would like to volunteer to be a mentor for this project. > > I am the Apache Thrift project chair and I am involved in the Apache > infrastructure group. I have handled releases for Apache Thrift since its > incubation and am very familiar with new project bootstrapping and > coordination. I think that my experiences with back end systems and scaling > architectures would be a perfect fit for this project along with my desire > to help new comers learn the Apache way. > > Thank you for your consideration > -Jake > > > > > On Mon, Aug 26, 2013 at 6:27 PM, Dave Lester >wrote: > > > Hi All, > > > > We're pleased to share a draft ASF incubation proposal for Aurora, a > > service scheduler used to schedule jobs onto Apache Mesos that we've > > developed at Twitter. Aurora provides all of the primitives necessary to > > quickly deploy and scale stateless and fault tolerant services in a > > datacenter. The complete proposal can be found: > > https://wiki.apache.org/incubator/AuroraProposal, and also pasted below. > > > > In particular, we'd love to add additional mentors to the project. Your > > feedback is appreciated. > > > > Dave > > > > = Abstract = > > > > Aurora is a service scheduler used to schedule jobs onto Apache Mesos. > > > > = Proposal = > > > > Aurora is a scheduler that provides all of the primitives necessary to > > quickly deploy and scale stateless and fault tolerant services in a > > datacenter. > > > > Aurora builds on top of Apache Mesos and provides common features that > > allow any site to run large scale production applications. While the > > project is currently used in production at Twitter, we wish to develop a > > community to increase contributions and see it thrive in the future. > > > > = Background = > > > > The initial development of Aurora was done at Twitter, and is planned to > be > > open sourced. This proposal is for Aurora to join the Apache Incubator. > > > > = Rationale = > > > > While the Apache Mesos core focuses on distributing individual tasks > across > > nodes in a cluster, typical services consist of dozens or hundreds of > > replicas of tasks. As a service scheduler, Aurora provides the > abstraction > > of a "job" to bundle and manage these tasks. Aurora provides many key > > functionalities centered around a job, including: definition, the concept > > of an instance and the serverset, deployment and scheduling, health > > checking, and introspection. It also allows cross-cutting concerns to be > > handled like observability and log collection. > > > > = Current Status = > > > > == Meritocracy == > > > > By submitting this incubator proposal, we’re expressing our intent to > build > > a diverse developer community around Aurora that will conduct itself > > according to The Apache Way and use meritocratic means of accepting > > contributions. Several members of the Aurora team overlap with Apache > > Mesos, which successfully graduated from the Incubator and has embraced a > > meritocratic model of governance; we plan to follow a similar path > forward > > with Aurora and believe that a synergy between both projects will make > this > > even easier. > > > > == Community == > > > > Aurora is currently being used internally at Twitter. By open sourcing > the > > project, we hope to extend our contributor base significantly and create > a > > vibrant community around the project. > > > > == Core Developers == > > > > Aurora is currently being developed by a team of seven engineers at > > Twitter. > > > > == Alignment == > > > > The ASF is a natural choice to host the Aurora project, given the goal of > > open sourcing the project and fostering a community to grow and support > the > > software. Additionally, Aurora integrates with Apache Mesos, and Apache > > ZooKeeper for service discovery. > > > > We believe that inclusion within Apache will build stronger ties between > > these projects, and create further alignment between their goals and > > communities. > > > > = Known Risks = > > > > == Orphaned Products == > > > > The core developers plan to continue working full time on the project, > and > > there is very little risk of Aurora being abandoned since it is running > > hundreds of services as part of Twitte
[PROPOSAL] Aurora for Incubation
ve no doubts that it will attract contributors and users, our interest is primarily to give Aurora a solid home as an open source project following an established development model. We have also given reasons in the Rationale and Alignment sections. = Documentation = This proposal exists online as http://wiki.apache.org/incubator/AuroraProposal. Project documentation exists and will be released at the same time as an initial code push. = Initial Source = JIRA Aurora (AURORA) Source and Intellectual Property Submission Plan The current codebase is available upon request. = External Dependencies = All Aurora dependencies have Apache compatible licenses, except cron4j (LGPL). An alternative library, most likely Quartz (Apache Public License 2.0) will be used prior to an initial code push. = Cryptography = Not applicable. = Required Resources = == Mailing Lists == * aurora-private for private PMC discussions * aurora-dev * aurora-commits * aurora-user * aurora-issues == Subversion Directory == We prefer to use Git as our source control system: git:// git.apache.org/aurora == Issue Tracking == JIRA Aurora (AURORA) = Initial Committers = * William Farner (bill at twitter dot com) * Brian Wickman (wickman at twitter dot com) * Kevin Sweeney (ksweeney at twitter dot com) * Sathya Hariesh (sathya at twitter dot com) * Jonathan Boulle (jon at twitter dot com) * Maxim Khutornenko (mkhutornenko at twitter dot com) * Suman Karumuri (skarumuri at twitter dot com) * Dave Lester (dlester at twitter dot com) = Affiliations = Twitter = Interested Parties = * Airbnb * Foursquare * Mesosphere = Sponsors = == Champion == Ben Hindman == Nominated Mentors == * Chris Mattmann * Ben Hindman == Sponsoring Entity == Incubator PMC
Requesting permission to edit Incubator wiki
I'd like to be added to the ContributorsGroup on the Incubator wiki so I can submit a proposal. My wiki username is DaveLester, and Apache committer id is dlester. Thanks, Dave
