Re: [VOTE] Release Apache Beam, version 0.1.0-incubating

2016-06-11 Thread Jean-Baptiste Onofré 

+1 (binding)

We will address the LICENSE and NOTICE points mentioned by Justin for 
next release.


Thanks

Regards
JB

On 06/12/2016 01:54 AM, Davor Bonaci wrote:

Hi everyone,
Here's the first vote for the first release of Apache Beam -- version
0.1.0-incubating!

The complete staging area is available for your review, which includes:
* the official Apache source release to be deployed to dist.apache.org [1],
and
* all artifacts to be deployed to the Maven Central Repository [2].

This corresponds to the tag "v0.1.0-incubating-RC3" in source control, [3].

The Apache Beam community has unanimously approved this release, [4], [5],
[6].

Please vote as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

As customary, the vote will be open for at least 72 hours. It is adopted by
a majority approval with at least three PMC affirmative votes. If approved,
we will proceed with the release.

Thanks,
Davor

[1]
https://dist.apache.org/repos/dist/dev/incubator/beam/0.1.0-incubating/RC3/
[2] https://repository.apache.org/content/repositories/orgapachebeam-1002/
[3] https://github.com/apache/incubator-beam/tree/v0.1.0-incubating-RC3
[4]
https://lists.apache.org/thread.html/68bf80b386dde080126b51ddf3497c6801015903a705411d435d64a1@%3Cdev.beam.apache.org%3E
[5]
https://lists.apache.org/thread.html/32c991987e0abf2a09cd8afad472cf02e482af02ac35418ee8731940@%3Cdev.beam.apache.org%3E
[6]
https://lists.apache.org/thread.html/e6ffcba94ef4514e8cf5c6fed39100ee359b954c4876d3275b1bc33a@%3Cdev.beam.apache.org%3E



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

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

Re: [DISCUSS] DistributedLog Incubation Proposal

2016-06-11 Thread Henry Saputra 
Sravya,

Thank you for the interest and willingness to help.
We definitely looking for more contributors as the projects coming to ASF.

Being mentor is not necessary requirement to help a podling as you probably
already know.

Looking forward to see you in the community :)

- Henry

On Saturday, June 11, 2016, Sravya Tirukkovalur  wrote:

> @Sijie: As I am not an IPMC member, I am not eligible to be a mentor. I am
> figuring out if I can still contribute in some way informally. Will keep
> you posted. So no, I do not think you should add me to the proposal.
>
> Thanks for your interest though!
>
> On Sat, Jun 11, 2016 at 12:38 PM, Sijie Guo  > wrote:
>
>>
>>
>> Thanks Eitan for adding me.
>>
>> Sravya, cool! I am glad that you are interested in mentoring this
>> project. Shall I add you to the proposal?
>>
>> Sijie
>>
>>
>> On Saturday, June 11, 2016, Eitan Adler > > wrote:
>>
>>> + some people explicitly
>>>
>>> On 10 June 2016 at 12:42, Sravya Tirukkovalur  wrote:
>>> > Excited to see DistributedLog come to ASF!
>>> >
>>> > I see that you already have good list of nominated mentors. As a
>>> member of
>>> > recently graduated project, I can offer mentorship(informal) as well if
>>> > needed. I am not an IPMC member, so I guess I cannot be a formal
>>> mentor.
>>> >
>>> > Regards,
>>> >
>>> > On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo  wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> I would like to propose DistributedLog to be an Apache Incubator
>>> project.
>>> >>
>>> >> DistributedLog is a high performance replicated log service.
>>> >> It offers durability, replication and strong consistency, which
>>> provides
>>> >> a fundamental building block for building reliable distributed
>>> systems,
>>> >> e.g replicated-state-machines, general pub/sub systems, distributed
>>> >> databases, distributed queues and etc.
>>> >>
>>> >> Here's a link to the proposal in the Incubator wiki
>>> >>
>>> >> https://wiki.apache.org/incubator/DistributedLogProposal
>>> >>
>>> >> I've also pasted the initial contents below.
>>> >>
>>> >> Thanks,
>>> >>
>>> >> Sijie
>>> >>
>>> >> = Abstract =
>>> >> DistributedLog is a high-performance replicated log service. It offers
>>> >> durability, replication and strong consistency, which provides a
>>> >> fundamental building block for building reliable distributed systems,
>>> >> e.g replicated-state-machines, general pub/sub systems, distributed
>>> >> databases, distributed queues and etc.
>>> >>
>>> >> See “Building Distributedlog - Twitter’s high performance replicated
>>> >> log service” for details:
>>> >>
>>> >>
>>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>>> >>
>>> >> = Proposal =
>>> >> We propose to contribute DistributedLog codebase and associated
>>> >> artifacts (e.g. documentation, web-site content etc.) to the Apache
>>> >> Software Foundation with the intent of forming a productive,
>>> >> meritocratic and open community around DistributedLog’s continued
>>> >> development, according to the ‘Apache Way’.
>>> >>
>>> >> = Background =
>>> >> Engineers at Twitter began developing DistributedLog in early 2013.
>>> >> DistributedLog is described in a Twitter engineering blog post and
>>> >> presented at the Messaging Meetup in Sep 2015. It has been released as
>>> >> an Apache-licensed open-source project on GitHub in May 2016.
>>> >>
>>> >> DistributedLog is a high-performance replicated log service, which
>>> >> provides simple stream-oriented abstractions over log-segments and
>>> >> offers durability, replication and strong consistency for building
>>> >> reliable distributed systems. The features offered by DistributedLog
>>> >> includes:
>>> >>  * Simple high-level, stream oriented interface
>>> >>  * Naming and metadata scheme for managing streams and other entities
>>> >>  * Log data management policies, include data segmentation and data
>>> >> retention
>>> >>  * Fast write pipeline leveraging batching and compression
>>> >>  * Fast read mechanism leveraging long-poll and read-ahead caching
>>> >>  * Service tiers supporting writer fan-in and reader fan-out
>>> >>  * Geo-replicated logs
>>> >>
>>> >> DistributedLog’s most important benefit is high-performance with a
>>> >> strong durability guarantee, making it extremely appropriate for
>>> >> running different workloads from distributed database journaling to
>>> >> real-time stream computing. Its modern, layered architecture makes it
>>> >> easy to run the service tiers in multi-tenant datacenter environments
>>> >> such as Apache Mesos or cloud environments such as EC2.
>>> >>
>>> >> = Rationale =
>>> >> DistributedLog is designed to provide core fundamental features like
>>> >> high-performance, durability and strong consistency to anyone who is
>>> >>

Re: DISCUSS: Trafodion for TLP

2016-06-11 Thread Roman Shaposhnik 
On Wed, Jun 8, 2016 at 9:08 PM, Stack  wrote:
> We'd like to solicit feedback on whether the Trafodiion project is ready to
> go TLP. I am the project Champion writing on behalf of the project PMC.
>
> Our clutch report is nice and healthy [2]. Our up-to-date status page can
> be found here [1.]. Development is brisk. We've made two releases out of
> incubator up to this (with another up for vote).

I'm curious to know how many RC were required to produce each of these
releases. Can you please provide those stats?

Thanks,
Roman.

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

Re: Looking for mentors

2016-06-11 Thread Justin Mclean 
Hi,

> If each graduating podling provided 2 or 3 mentors (or one person prepared to 
> mentor 2 or 3 projects) the problem would be solved.

Not all graduating projects have people who can act in an official mentor role 
i.e. you need to be IPMC and that generally means being a member.

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

Re: [VOTE] Release Apache Beam, version 0.1.0-incubating

2016-06-11 Thread Justin Mclean 
Hi,

+1 (binding)  IMO license issue need to be fixed for the next release.

I checked:
- file name of release contains incubating
- while signature checks out, there’s no KEYS file in the list area and there 
seems to be no key on file for the release manager [1] However there is a KEYS 
file in github.
- hashes good
- DISCLAIMER exists
- NOTICE file contain unneeded text (i.e mentions  Apache v2.0 licence). There 
no need to generally mention Apache 2.0 licences in NOTICE [2]
- LICENSE is missing a few items [3][4]
- All files have Apache headers
- No binary files in release
- Can compile from source

I suggest you also check [3][4] with legal discuss as the Project Gutenberg 
license is not listed in any of the Apache license categories [5] as from a 
casual glance [3] adds a non-commercial restriction. i.e. “NO CHARGES MAY BE 
MADE FOR *ANY* ACCESS TO THIS MATERIAL”. Both license are different versions 
and look to have different restrictions which is also different to the latest 
license. [6]

Also it’s best to sign the release with an Apache email address rather than a 
Google one

Thanks,
Justin

1. https://people.apache.org/keys/committer/
2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
3. ./runners/spark/src/test/resources/pg1112.txt
4. ./runners/spark/src/test/resources/pg2264.txt
5. http://www.apache.org/legal/resolved.html
6. https://www.gutenberg.org/wiki/Gutenberg:The_Project_Gutenberg_License
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for mentors

2016-06-11 Thread John D. Ament 
On Jun 11, 2016 21:37, "Justin Mclean"  wrote:
>
> Hi,
>
> > FWIW: I'm still a big fan of having a cap on the # of podlings a single
mentor
> > could have
>
> I have a self imposed cap and I’m currently at capacity so sorry can’t
help out.

Perfect point, everyone has their own internal cap that indicates
capacity.  People need to be realistic about their availability.

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

Re: Looking for mentors

2016-06-11 Thread Roman Shaposhnik 
On Sun, Jun 12, 2016 at 3:46 AM, Julian Hyde  wrote:
> If each graduating podling provided 2 or 3 mentors (or one person prepared to 
> mentor 2 or 3 projects)
> the problem would be solved. It would be a (virtuous) pyramid scheme and the 
> incubator could grow indefinitely.

Good point. At least making sure that we do a bit of nagging during
the graduation could
go a long way. That said, we still have IPMC-mostly-only-for-members
issue and by definition
podlings are typically new folks.

Thanks,
Roman.

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

Re: Looking for mentors

2016-06-11 Thread John D. Ament 
The Incubator PMC has 242 members.  Assuming 3 mentors per project that
means we would need 80 projects before duplicating a member, given that
each PMC member acted as a mentor.
On Jun 11, 2016 21:46, "Julian Hyde"  wrote:

> If each graduating podling provided 2 or 3 mentors (or one person prepared
> to mentor 2 or 3 projects) the problem would be solved. It would be a
> (virtuous) pyramid scheme and the incubator could grow indefinitely.
>
> Julian
>
> > On Jun 11, 2016, at 18:40, Roman Shaposhnik 
> wrote:
> >
> >> On Sun, Jun 12, 2016 at 3:37 AM, Justin Mclean <
> jus...@classsoftware.com> wrote:
> >> Hi,
> >>
> >>> FWIW: I'm still a big fan of having a cap on the # of podlings a
> single mentor
> >>> could have
> >>
> >> I have a self imposed cap and I’m currently at capacity so sorry can’t
> help out.
> >
> > Yup. Make two of us!
> >
> > 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: Looking for mentors

2016-06-11 Thread Julian Hyde 
If each graduating podling provided 2 or 3 mentors (or one person prepared to 
mentor 2 or 3 projects) the problem would be solved. It would be a (virtuous) 
pyramid scheme and the incubator could grow indefinitely. 

Julian

> On Jun 11, 2016, at 18:40, Roman Shaposhnik  wrote:
> 
>> On Sun, Jun 12, 2016 at 3:37 AM, Justin Mclean  
>> wrote:
>> Hi,
>> 
>>> FWIW: I'm still a big fan of having a cap on the # of podlings a single 
>>> mentor
>>> could have
>> 
>> I have a self imposed cap and I’m currently at capacity so sorry can’t help 
>> out.
> 
> Yup. Make two of us!
> 
> 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: Looking for mentors

2016-06-11 Thread Roman Shaposhnik 
On Sun, Jun 12, 2016 at 3:37 AM, Justin Mclean  wrote:
> Hi,
>
>> FWIW: I'm still a big fan of having a cap on the # of podlings a single 
>> mentor
>> could have
>
> I have a self imposed cap and I’m currently at capacity so sorry can’t help 
> out.

Yup. Make two of us!

Thanks,
Roman.

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

Re: Looking for mentors

2016-06-11 Thread Justin Mclean 
Hi,

> FWIW: I'm still a big fan of having a cap on the # of podlings a single mentor
> could have 

I have a self imposed cap and I’m currently at capacity so sorry can’t help out.

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

Re: [ALL] Volunteers for a Math IPMC?

2016-06-11 Thread Niclas Hedhman 
If you have a functioning community around Commons Math already, why do you
feel you need Incubation?

People on a Math TLP would come out of the Commons PMC and simply submit a
Board Resolution, and I doubt that there would be any objects. There are no
legal concerns, no community training, no need for release management
training, and so on...

Or are you looking at a situation where the Commons community has no
interest in Math subproject, and need new blood?


Cheers
Niclas

On Sat, Jun 11, 2016 at 6:25 PM, James Carman 
wrote:

> We (the Commons PMC) have not decided yet what to do, but I just wanted to
> gauge the interest in joining the math IPMC if we choose to go TLP by way
> of the incubator. The idea would be that math (whatever its name may be),
> would go through the incubator in order to enrich its community prior to
> becoming a TLP. Do we have any folks willing to throw their hat in the
> ring?
>
> p.s. I've cross-posted to the incubator list as there are folks there who
> are very good at this stuff and could perhaps lend us some advice.
>



-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Re: Looking for mentors

2016-06-11 Thread Roman Shaposhnik 
On Thu, Jun 9, 2016 at 9:01 AM, Sergio Fernández  wrote:
> (Off-topic) At some point we may need to discuss our incubation capacity...
> People present cool proposal and they get vote just because that, without
> checking our available resources.

FWIW: I'm still a big fan of having a cap on the # of podlings a single mentor
could have (at which point Incubator capacity becomes a self-throttling one).
But given discussions as of 9 month I don't think this idea enjoys much of IPMC
support.

Thanks,
Roman.

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

[VOTE] Release Apache Beam, version 0.1.0-incubating

2016-06-11 Thread Davor Bonaci 
Hi everyone,
Here's the first vote for the first release of Apache Beam -- version
0.1.0-incubating!

The complete staging area is available for your review, which includes:
* the official Apache source release to be deployed to dist.apache.org [1],
and
* all artifacts to be deployed to the Maven Central Repository [2].

This corresponds to the tag "v0.1.0-incubating-RC3" in source control, [3].

The Apache Beam community has unanimously approved this release, [4], [5],
[6].

Please vote as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

As customary, the vote will be open for at least 72 hours. It is adopted by
a majority approval with at least three PMC affirmative votes. If approved,
we will proceed with the release.

Thanks,
Davor

[1]
https://dist.apache.org/repos/dist/dev/incubator/beam/0.1.0-incubating/RC3/
[2] https://repository.apache.org/content/repositories/orgapachebeam-1002/
[3] https://github.com/apache/incubator-beam/tree/v0.1.0-incubating-RC3
[4]
https://lists.apache.org/thread.html/68bf80b386dde080126b51ddf3497c6801015903a705411d435d64a1@%3Cdev.beam.apache.org%3E
[5]
https://lists.apache.org/thread.html/32c991987e0abf2a09cd8afad472cf02e482af02ac35418ee8731940@%3Cdev.beam.apache.org%3E
[6]
https://lists.apache.org/thread.html/e6ffcba94ef4514e8cf5c6fed39100ee359b954c4876d3275b1bc33a@%3Cdev.beam.apache.org%3E

Re: [DISCUSS] DistributedLog Incubation Proposal

2016-06-11 Thread Sravya Tirukkovalur 
@Sijie: As I am not an IPMC member, I am not eligible to be a mentor. I am
figuring out if I can still contribute in some way informally. Will keep
you posted. So no, I do not think you should add me to the proposal.

Thanks for your interest though!

On Sat, Jun 11, 2016 at 12:38 PM, Sijie Guo  wrote:

>
>
> Thanks Eitan for adding me.
>
> Sravya, cool! I am glad that you are interested in mentoring this project.
> Shall I add you to the proposal?
>
> Sijie
>
>
> On Saturday, June 11, 2016, Eitan Adler  wrote:
>
>> + some people explicitly
>>
>> On 10 June 2016 at 12:42, Sravya Tirukkovalur  wrote:
>> > Excited to see DistributedLog come to ASF!
>> >
>> > I see that you already have good list of nominated mentors. As a member
>> of
>> > recently graduated project, I can offer mentorship(informal) as well if
>> > needed. I am not an IPMC member, so I guess I cannot be a formal mentor.
>> >
>> > Regards,
>> >
>> > On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo  wrote:
>> >
>> >> Hi,
>> >>
>> >> I would like to propose DistributedLog to be an Apache Incubator
>> project.
>> >>
>> >> DistributedLog is a high performance replicated log service.
>> >> It offers durability, replication and strong consistency, which
>> provides
>> >> a fundamental building block for building reliable distributed systems,
>> >> e.g replicated-state-machines, general pub/sub systems, distributed
>> >> databases, distributed queues and etc.
>> >>
>> >> Here's a link to the proposal in the Incubator wiki
>> >>
>> >> https://wiki.apache.org/incubator/DistributedLogProposal
>> >>
>> >> I've also pasted the initial contents below.
>> >>
>> >> Thanks,
>> >>
>> >> Sijie
>> >>
>> >> = Abstract =
>> >> DistributedLog is a high-performance replicated log service. It offers
>> >> durability, replication and strong consistency, which provides a
>> >> fundamental building block for building reliable distributed systems,
>> >> e.g replicated-state-machines, general pub/sub systems, distributed
>> >> databases, distributed queues and etc.
>> >>
>> >> See “Building Distributedlog - Twitter’s high performance replicated
>> >> log service” for details:
>> >>
>> >>
>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>> >>
>> >> = Proposal =
>> >> We propose to contribute DistributedLog codebase and associated
>> >> artifacts (e.g. documentation, web-site content etc.) to the Apache
>> >> Software Foundation with the intent of forming a productive,
>> >> meritocratic and open community around DistributedLog’s continued
>> >> development, according to the ‘Apache Way’.
>> >>
>> >> = Background =
>> >> Engineers at Twitter began developing DistributedLog in early 2013.
>> >> DistributedLog is described in a Twitter engineering blog post and
>> >> presented at the Messaging Meetup in Sep 2015. It has been released as
>> >> an Apache-licensed open-source project on GitHub in May 2016.
>> >>
>> >> DistributedLog is a high-performance replicated log service, which
>> >> provides simple stream-oriented abstractions over log-segments and
>> >> offers durability, replication and strong consistency for building
>> >> reliable distributed systems. The features offered by DistributedLog
>> >> includes:
>> >>  * Simple high-level, stream oriented interface
>> >>  * Naming and metadata scheme for managing streams and other entities
>> >>  * Log data management policies, include data segmentation and data
>> >> retention
>> >>  * Fast write pipeline leveraging batching and compression
>> >>  * Fast read mechanism leveraging long-poll and read-ahead caching
>> >>  * Service tiers supporting writer fan-in and reader fan-out
>> >>  * Geo-replicated logs
>> >>
>> >> DistributedLog’s most important benefit is high-performance with a
>> >> strong durability guarantee, making it extremely appropriate for
>> >> running different workloads from distributed database journaling to
>> >> real-time stream computing. Its modern, layered architecture makes it
>> >> easy to run the service tiers in multi-tenant datacenter environments
>> >> such as Apache Mesos or cloud environments such as EC2.
>> >>
>> >> = Rationale =
>> >> DistributedLog is designed to provide core fundamental features like
>> >> high-performance, durability and strong consistency to anyone who is
>> >> building reliable distributed systems, in a simple and efficient way.
>> >>
>> >> We believe that the ASF is the right venue to foster an open-source
>> >> community around DistributedLog’s development. We expect that
>> >> DistributedLog will benefit from collaboration with related Apache
>> >> projects, and under the auspices of the ASF will attract talented
>> >> contributors who will push DistributedLog’s development forward at a
>> >> faster pace.
>> >>
>> >> We believe that the timing is right for DistributedLog’s development
>> >> to move to the ASF: DistributedLog has already

Re: Looking for mentors

2016-06-11 Thread Sravya Tirukkovalur 
Agree that podlings which have recently graduated might be able to provide
good advice having just been through the experience.

Although, how common is it to have IPMCs in the newly graduated podlings?
Is there a way for folks who are not IPMCs yet to give back in terms of
informally mentoring specific projects?

I get a sense that there is also a notion of informal mentors from this
section[1]

"There is no restriction on the number of informal mentors (note the small m)
that a Podling may have. These can be very useful but have no formal role
in the process."

But, not sure who is eligible to be an informal mentor and how does this
mentoring relation work?

Thanks in advance!

[1] http://incubator.apache.org/guides/proposal.html#template-mentors

On Fri, Jun 10, 2016 at 3:05 AM, Julian Hyde  wrote:

> I strongly believe that one or two people from each graduating podling
> should serve as mentors soon after graduation. It's totally up to them, of
> course. But it is appropriate to give back, having received help from so
> many volunteers during incubation. And, having just been through the
> experience, they are in a good position to give advice.
>
> Julian
>
> > On Jun 9, 2016, at 19:44, Marvin Humphrey 
> wrote:
> >
> >> On Thu, Jun 9, 2016 at 12:01 AM, Sergio Fernández 
> wrote:
> >> (Off-topic) At some point we may need to discuss our incubation
> capacity...
> >> People present cool proposal and they get vote just because that,
> without
> >> checking our available resources.
> >
> > Incubation capacity is limited by total Mentoring capacity across all
> > podlings, and by our ability to cover central administration.
> >
> > With regards to central administration, even at ~55 podlings, we are
> still
> > mostly managing to cover what's needed:
> >
> > * Spare release voting capacity (Justin Mclean, John Ament)
> > * Report preparation (John, Marvin)
> > * Followup after troubled podlings (John)
> > * Administrivia (John, Marvin, Ted, Nick Burch)
> > * Mediation (Ted, Marvin, others)
> > * Relief Mentors (...)
> >
> > Happily, responsibility is more spread out than it used to be -- Jukka
> was the
> > first line of defense for nearly all of those when he was Chair.  We are
> > heavily dependent on both John and Justin and would struggle to replace
> their
> > contributions, but for the moment we are holding -- with the one weakness
> > being that when a podling needs relief Mentors there are few to be had.
> >
> > Total Mentoring capacity is hard to assess.  We keep adding awesome new
> IPMC
> > members, and sometimes new podlings will persuade high-quality inactive
> IPMC
> > Members to return to active duty.  But we do appear to be getting more
> > stretched as strong proposals keep pouring in.
> >
> > In recent times, the Incubator has not been voting to accept podlings
> that
> > have an inadequate *number* of Mentors.  However, we have for many years
> had
> > podlings where several of the Mentors do not do much beyond lend their
> name to
> > the proposal.
> >
> > Overstretched mentoring has always been a concern, but I think it is
> becoming
> > a bit more of a concern now as podlings struggle more to recruit Mentors
> --
> > perhaps tempting already overcommitted Mentors to strech even further, or
> > necessitating the recruitment of rookies from the ASF Membership with no
> > Incubator experience.
> >
> > As a mitigation, I think we should be paying a little more attention to
> the
> > Mentor roster in new proposals.  One simple report would tell us a lot
> -- just
> > list all the podlings that each proposed Mentor is already signed up for.
> >
> > If there are concerns that any of the proposed Mentors are
> overcommitted, it
> > would be appropriate to raise them on private@incubator.
> >
> > 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
>
>


-- 
Sravya Tirukkovalur

Re: [DISCUSS] DistributedLog Incubation Proposal

2016-06-11 Thread Sijie Guo 
Thanks Eitan for adding me.

Sravya, cool! I am glad that you are interested in mentoring this project.
Shall I add you to the proposal?

Sijie

On Saturday, June 11, 2016, Eitan Adler  wrote:

> + some people explicitly
>
> On 10 June 2016 at 12:42, Sravya Tirukkovalur  > wrote:
> > Excited to see DistributedLog come to ASF!
> >
> > I see that you already have good list of nominated mentors. As a member
> of
> > recently graduated project, I can offer mentorship(informal) as well if
> > needed. I am not an IPMC member, so I guess I cannot be a formal mentor.
> >
> > Regards,
> >
> > On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo  > wrote:
> >
> >> Hi,
> >>
> >> I would like to propose DistributedLog to be an Apache Incubator
> project.
> >>
> >> DistributedLog is a high performance replicated log service.
> >> It offers durability, replication and strong consistency, which provides
> >> a fundamental building block for building reliable distributed systems,
> >> e.g replicated-state-machines, general pub/sub systems, distributed
> >> databases, distributed queues and etc.
> >>
> >> Here's a link to the proposal in the Incubator wiki
> >>
> >> https://wiki.apache.org/incubator/DistributedLogProposal
> >>
> >> I've also pasted the initial contents below.
> >>
> >> Thanks,
> >>
> >> Sijie
> >>
> >> = Abstract =
> >> DistributedLog is a high-performance replicated log service. It offers
> >> durability, replication and strong consistency, which provides a
> >> fundamental building block for building reliable distributed systems,
> >> e.g replicated-state-machines, general pub/sub systems, distributed
> >> databases, distributed queues and etc.
> >>
> >> See “Building Distributedlog - Twitter’s high performance replicated
> >> log service” for details:
> >>
> >>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
> >>
> >> = Proposal =
> >> We propose to contribute DistributedLog codebase and associated
> >> artifacts (e.g. documentation, web-site content etc.) to the Apache
> >> Software Foundation with the intent of forming a productive,
> >> meritocratic and open community around DistributedLog’s continued
> >> development, according to the ‘Apache Way’.
> >>
> >> = Background =
> >> Engineers at Twitter began developing DistributedLog in early 2013.
> >> DistributedLog is described in a Twitter engineering blog post and
> >> presented at the Messaging Meetup in Sep 2015. It has been released as
> >> an Apache-licensed open-source project on GitHub in May 2016.
> >>
> >> DistributedLog is a high-performance replicated log service, which
> >> provides simple stream-oriented abstractions over log-segments and
> >> offers durability, replication and strong consistency for building
> >> reliable distributed systems. The features offered by DistributedLog
> >> includes:
> >>  * Simple high-level, stream oriented interface
> >>  * Naming and metadata scheme for managing streams and other entities
> >>  * Log data management policies, include data segmentation and data
> >> retention
> >>  * Fast write pipeline leveraging batching and compression
> >>  * Fast read mechanism leveraging long-poll and read-ahead caching
> >>  * Service tiers supporting writer fan-in and reader fan-out
> >>  * Geo-replicated logs
> >>
> >> DistributedLog’s most important benefit is high-performance with a
> >> strong durability guarantee, making it extremely appropriate for
> >> running different workloads from distributed database journaling to
> >> real-time stream computing. Its modern, layered architecture makes it
> >> easy to run the service tiers in multi-tenant datacenter environments
> >> such as Apache Mesos or cloud environments such as EC2.
> >>
> >> = Rationale =
> >> DistributedLog is designed to provide core fundamental features like
> >> high-performance, durability and strong consistency to anyone who is
> >> building reliable distributed systems, in a simple and efficient way.
> >>
> >> We believe that the ASF is the right venue to foster an open-source
> >> community around DistributedLog’s development. We expect that
> >> DistributedLog will benefit from collaboration with related Apache
> >> projects, and under the auspices of the ASF will attract talented
> >> contributors who will push DistributedLog’s development forward at a
> >> faster pace.
> >>
> >> We believe that the timing is right for DistributedLog’s development
> >> to move to the ASF: DistributedLog has already run in production at
> >> Twitter for 3 years and served various workloads including a
> >> distributed database journal, reliable cross datacenter replication,
> >> search ingestion, andgeneral pub/sub messaging. The project is stable.
> >> We are excited to see where an ASF-based community can take
> >> DistributedLog.
> >>
> >> = Current Status =
> >> DistributedLog is a stable project that has been used

RE: [ALL] Volunteers for a Math IPMC?

2016-06-11 Thread Martin Gainty 
Afternoon James
I would ping Bill Barker, Mikkel Andersen, Sebastian Brissard or any math 
committer from the base project
http://commons.apache.org/proper/commons-math/team-list.html
HTH
Martin 
__ 

   


> From: ja...@carmanconsulting.com
> Date: Sat, 11 Jun 2016 16:12:48 +
> Subject: Re: [ALL] Volunteers for a Math IPMC?
> To: dennis.hamil...@acm.org; general@incubator.apache.org
> 
> I meant PPMC, yeah.
> 
> On Sat, Jun 11, 2016 at 12:11 PM Dennis E. Hamilton 
> wrote:
> 
> > Interesting.  Does this mean migrating Commons Math to a math PPMC (not
> > IPMC)?
> >
> > Would the scope be the same?
> >
> > Would Commons Math go to the Attic?
> >
> > Is there some problem that this is meant to solve?  How is it a solution?
> >
> >  - Dennis
> >
> > PS: I have labored through the dev-commons thread on [Math] Commons Math
> > (r)evolution, and a few other of the June math-related posts.  I think
> > going through the effort to create an Incubation proposal would be useful.
> > You will have to come to grips, and clarity, on whether and to what extent
> > this is effectively an ASF-internal fork.  Not that there is anything wrong
> > with that.  It is leaving it unresolved that strikes me as solving nothing.
> >
> > PPS: Not cross-posting.  The interested parties may need to come to
> > general-incubator to begin appreciating for themselves what is involved.
> >
> > > -Original Message-
> > > From: James Carman [mailto:ja...@carmanconsulting.com]
> > > Sent: Saturday, June 11, 2016 03:26
> > > To: Commons Developers List ;
> > > general@incubator.apache.org
> > > Subject: [ALL] Volunteers for a Math IPMC?
> > >
> > > We (the Commons PMC) have not decided yet what to do, but I just wanted
> > > to
> > > gauge the interest in joining the math IPMC if we choose to go TLP by
> > > way
> > > of the incubator. The idea would be that math (whatever its name may
> > > be),
> > > would go through the incubator in order to enrich its community prior to
> > > becoming a TLP. Do we have any folks willing to throw their hat in the
> > > ring?
> > >
> > > p.s. I've cross-posted to the incubator list as there are folks there
> > > who
> > > are very good at this stuff and could perhaps lend us some advice.
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

Re: [DISCUSS] DistributedLog Incubation Proposal

2016-06-11 Thread Eitan Adler 
+ some people explicitly

On 10 June 2016 at 12:42, Sravya Tirukkovalur  wrote:
> Excited to see DistributedLog come to ASF!
>
> I see that you already have good list of nominated mentors. As a member of
> recently graduated project, I can offer mentorship(informal) as well if
> needed. I am not an IPMC member, so I guess I cannot be a formal mentor.
>
> Regards,
>
> On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo  wrote:
>
>> Hi,
>>
>> I would like to propose DistributedLog to be an Apache Incubator project.
>>
>> DistributedLog is a high performance replicated log service.
>> It offers durability, replication and strong consistency, which provides
>> a fundamental building block for building reliable distributed systems,
>> e.g replicated-state-machines, general pub/sub systems, distributed
>> databases, distributed queues and etc.
>>
>> Here's a link to the proposal in the Incubator wiki
>>
>> https://wiki.apache.org/incubator/DistributedLogProposal
>>
>> I've also pasted the initial contents below.
>>
>> Thanks,
>>
>> Sijie
>>
>> = Abstract =
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental building block for building reliable distributed systems,
>> e.g replicated-state-machines, general pub/sub systems, distributed
>> databases, distributed queues and etc.
>>
>> See “Building Distributedlog - Twitter’s high performance replicated
>> log service” for details:
>>
>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>>
>> = Proposal =
>> We propose to contribute DistributedLog codebase and associated
>> artifacts (e.g. documentation, web-site content etc.) to the Apache
>> Software Foundation with the intent of forming a productive,
>> meritocratic and open community around DistributedLog’s continued
>> development, according to the ‘Apache Way’.
>>
>> = Background =
>> Engineers at Twitter began developing DistributedLog in early 2013.
>> DistributedLog is described in a Twitter engineering blog post and
>> presented at the Messaging Meetup in Sep 2015. It has been released as
>> an Apache-licensed open-source project on GitHub in May 2016.
>>
>> DistributedLog is a high-performance replicated log service, which
>> provides simple stream-oriented abstractions over log-segments and
>> offers durability, replication and strong consistency for building
>> reliable distributed systems. The features offered by DistributedLog
>> includes:
>>  * Simple high-level, stream oriented interface
>>  * Naming and metadata scheme for managing streams and other entities
>>  * Log data management policies, include data segmentation and data
>> retention
>>  * Fast write pipeline leveraging batching and compression
>>  * Fast read mechanism leveraging long-poll and read-ahead caching
>>  * Service tiers supporting writer fan-in and reader fan-out
>>  * Geo-replicated logs
>>
>> DistributedLog’s most important benefit is high-performance with a
>> strong durability guarantee, making it extremely appropriate for
>> running different workloads from distributed database journaling to
>> real-time stream computing. Its modern, layered architecture makes it
>> easy to run the service tiers in multi-tenant datacenter environments
>> such as Apache Mesos or cloud environments such as EC2.
>>
>> = Rationale =
>> DistributedLog is designed to provide core fundamental features like
>> high-performance, durability and strong consistency to anyone who is
>> building reliable distributed systems, in a simple and efficient way.
>>
>> We believe that the ASF is the right venue to foster an open-source
>> community around DistributedLog’s development. We expect that
>> DistributedLog will benefit from collaboration with related Apache
>> projects, and under the auspices of the ASF will attract talented
>> contributors who will push DistributedLog’s development forward at a
>> faster pace.
>>
>> We believe that the timing is right for DistributedLog’s development
>> to move to the ASF: DistributedLog has already run in production at
>> Twitter for 3 years and served various workloads including a
>> distributed database journal, reliable cross datacenter replication,
>> search ingestion, andgeneral pub/sub messaging. The project is stable.
>> We are excited to see where an ASF-based community can take
>> DistributedLog.
>>
>> = Current Status =
>> DistributedLog is a stable project that has been used in production at
>> Twitter for 3 years. The source code is public at github.com/twitter,
>> which will seed the Apache git repository.
>>
>> = Meritocracy =
>> We understand the central importance of meritocracy to the Apache Way.
>> We will work to establish a welcoming, fair and meritocratic
>> community. Several companies have already expressed interest in this
>> project, and we intend to invite additional developers to participate.
>> We look

Re: [ALL] Volunteers for a Math IPMC?

2016-06-11 Thread James Carman 
I meant PPMC, yeah.

On Sat, Jun 11, 2016 at 12:11 PM Dennis E. Hamilton 
wrote:

> Interesting.  Does this mean migrating Commons Math to a math PPMC (not
> IPMC)?
>
> Would the scope be the same?
>
> Would Commons Math go to the Attic?
>
> Is there some problem that this is meant to solve?  How is it a solution?
>
>  - Dennis
>
> PS: I have labored through the dev-commons thread on [Math] Commons Math
> (r)evolution, and a few other of the June math-related posts.  I think
> going through the effort to create an Incubation proposal would be useful.
> You will have to come to grips, and clarity, on whether and to what extent
> this is effectively an ASF-internal fork.  Not that there is anything wrong
> with that.  It is leaving it unresolved that strikes me as solving nothing.
>
> PPS: Not cross-posting.  The interested parties may need to come to
> general-incubator to begin appreciating for themselves what is involved.
>
> > -Original Message-
> > From: James Carman [mailto:ja...@carmanconsulting.com]
> > Sent: Saturday, June 11, 2016 03:26
> > To: Commons Developers List ;
> > general@incubator.apache.org
> > Subject: [ALL] Volunteers for a Math IPMC?
> >
> > We (the Commons PMC) have not decided yet what to do, but I just wanted
> > to
> > gauge the interest in joining the math IPMC if we choose to go TLP by
> > way
> > of the incubator. The idea would be that math (whatever its name may
> > be),
> > would go through the incubator in order to enrich its community prior to
> > becoming a TLP. Do we have any folks willing to throw their hat in the
> > ring?
> >
> > p.s. I've cross-posted to the incubator list as there are folks there
> > who
> > are very good at this stuff and could perhaps lend us some advice.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

RE: [ALL] Volunteers for a Math IPMC?

2016-06-11 Thread Dennis E. Hamilton 
Interesting.  Does this mean migrating Commons Math to a math PPMC (not IPMC)? 

Would the scope be the same?

Would Commons Math go to the Attic?  

Is there some problem that this is meant to solve?  How is it a solution?

 - Dennis 

PS: I have labored through the dev-commons thread on [Math] Commons Math 
(r)evolution, and a few other of the June math-related posts.  I think going 
through the effort to create an Incubation proposal would be useful.  You will 
have to come to grips, and clarity, on whether and to what extent this is 
effectively an ASF-internal fork.  Not that there is anything wrong with that.  
It is leaving it unresolved that strikes me as solving nothing.

PPS: Not cross-posting.  The interested parties may need to come to 
general-incubator to begin appreciating for themselves what is involved.

> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Saturday, June 11, 2016 03:26
> To: Commons Developers List ;
> general@incubator.apache.org
> Subject: [ALL] Volunteers for a Math IPMC?
> 
> We (the Commons PMC) have not decided yet what to do, but I just wanted
> to
> gauge the interest in joining the math IPMC if we choose to go TLP by
> way
> of the incubator. The idea would be that math (whatever its name may
> be),
> would go through the incubator in order to enrich its community prior to
> becoming a TLP. Do we have any folks willing to throw their hat in the
> ring?
> 
> p.s. I've cross-posted to the incubator list as there are folks there
> who
> are very good at this stuff and could perhaps lend us some advice.


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

[ALL] Volunteers for a Math IPMC?

2016-06-11 Thread James Carman 
We (the Commons PMC) have not decided yet what to do, but I just wanted to
gauge the interest in joining the math IPMC if we choose to go TLP by way
of the incubator. The idea would be that math (whatever its name may be),
would go through the incubator in order to enrich its community prior to
becoming a TLP. Do we have any folks willing to throw their hat in the ring?

p.s. I've cross-posted to the incubator list as there are folks there who
are very good at this stuff and could perhaps lend us some advice.