Re: [VOTE] Accept HTrace into the Apache Incubator

[Naresh Agarwal]

+1 (non-binding)

Thanks
Naresh

On Thu, Nov 6, 2014 at 12:26 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> +1 (non-binding)
>
> On Wed, Nov 5, 2014 at 1:34 PM, Billie Rinaldi  wrote:
>
> > +1
> >
> > On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik 
> wrote:
> >
> > >
> > > Following the discussion earlier in the thread:
> > >http://s.apache.org/Dk7
> > >
> > > I would like to call a VOTE for accepting HTrace
> > > as a new incubator project.
> > >
> > > The proposal is available at:
> > >
> > > https://wiki.apache.org/incubator/HTraceProposal
> > >
> > > Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> > >
> > >  [ ] +1 accept Lens in the Incubator
> > >  [ ] ±0
> > >  [ ] -1 because...
> > >
> > >
> >
>
>
>
> --
> Regards,
> Venkatesh
>
> “Perfection (in design) is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.”
> - Antoine de Saint-Exupéry
>

-- 
_
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: [VOTE] Accept HTrace into the Apache Incubator

[Shwetha GS]

+1 (non-binding)

On Thu, Nov 6, 2014 at 1:36 PM, Naresh Agarwal 
wrote:

> +1 (non-binding)
>
> Thanks
> Naresh
>
> On Thu, Nov 6, 2014 at 12:26 PM, Seetharam Venkatesh <
> venkat...@innerzeal.com> wrote:
>
> > +1 (non-binding)
> >
> > On Wed, Nov 5, 2014 at 1:34 PM, Billie Rinaldi 
> wrote:
> >
> > > +1
> > >
> > > On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik 
> > wrote:
> > >
> > > >
> > > > Following the discussion earlier in the thread:
> > > >http://s.apache.org/Dk7
> > > >
> > > > I would like to call a VOTE for accepting HTrace
> > > > as a new incubator project.
> > > >
> > > > The proposal is available at:
> > > >
> > > > https://wiki.apache.org/incubator/HTraceProposal
> > > >
> > > > Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> > > >
> > > >  [ ] +1 accept Lens in the Incubator
> > > >  [ ] ±0
> > > >  [ ] -1 because...
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Regards,
> > Venkatesh
> >
> > “Perfection (in design) is achieved not when there is nothing more to
> add,
> > but rather when there is nothing more to take away.”
> > - Antoine de Saint-Exupéry
> >
>
> --
> _
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>

-- 
_
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Reza]

Of course, discussion is more than welcomed.
>> Seems a little weird to have such a small team to begin with.  How have you 
>>grown?
This is a concern of the project. The PMC is indeed small. More than half of 
the original group has not participated in the last year and have not voiced 
that they would like to continue on with the project, leaving us with the group 
listed in the resolution. I do not know why these people decided not to 
continue their participation, but I can assure you that the remaining members 
are fully committed to continuing on with the project and we hope to recruit 
future members. Graduating will be a big accomplishment for this project and 
may give this project more visibility and growth.
Also, on another note, I did not give the vote a deadline. If this list wishes 
to continue a vote, it will be open for 72 hours from my original email. I will 
close the vote Nov 8th at noon EST.
thanks,Reza
  From: John D. Ament 
 To: "general@incubator.apache.org" ; Reza 
 
 Sent: Wednesday, November 5, 2014 7:37 PM
 Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator
   
Hi,

Should we perhaps discuss it first?

Seems a little weird to have such a small team to begin with.  How have you
grown?

John



On Wed, Nov 5, 2014 at 10:27 AM, Reza 
wrote:

> So another graduation vote thread..! The Apache DeviceMap project would
> like to graduate from the incubator. The project has made a lot of progress
> in the past 6 months and all project members have voted positively for this
> measure. We got 4 +1 votes from PMC members, 2 +1 votes from IPMC members
> (Bertrand and Kevan), and no 0 or -1 votes [0].
>
>
> This is the incubator vote thread to decide if the Apache DeviceMap
> project graduates from the incubator. The resolution is at the bottom of
> this email and attached.
>
>
> [ ] +1 Graduate Apache DeviceMap from the Incubator.
>
> [ ] +0 Don't care.
>
> [ ] -1 Don't graduate Apache DeviceMap from the Incubator because ...
>
>
> [0]
> http://mail-archives.apache.org/mod_mbox/incubator-devicemap-dev/201411.mbox/%3C394358326.437830.1415058677229.JavaMail.yahoo%40jws106134.mail.bf1.yahoo.com%3E
>
>
> ---
>
>
> Establish the Apache DeviceMap 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 the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache DeviceMap Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache DeviceMap Project be and hereby is responsible
> for the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache DeviceMap" 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 DeviceMap Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache DeviceMap 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 DeviceMapProject:
>
>
>    * Reza Naghibi                    
>
>    * Werner Keil                      
>
>    * Eberhard Speer Jr.              
>
>    * Radu Cotescu                    
>
>    * Bertrand Delacretaz              
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Reza Naghibi be appointed to
> the office of Vice President, Apache DeviceMap, 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 DeviceMap 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 DeviceMap Project; and be it
> further
>
>
> RESOLVED, that the Apache DeviceMap Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator DeviceMap
> podling; and be it further
>
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> DeviceMap podling encumbered upon the Apache Incubator Project are
> hereafter discharged.
>
>
>
> -
> To unsubscribe, e-mail: general-u

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[jan i]

On 6 November 2014 03:31, Reza  wrote:

> Of course, discussion is more than welcomed.
> >> Seems a little weird to have such a small team to begin with.  How have
> you grown?
> This is a concern of the project. The PMC is indeed small. More than half
> of the original group has not participated in the last year and have not
> voiced that they would like to continue on with the project, leaving us
> with the group listed in the resolution. I do not know why these people
> decided not to continue their participation, but I can assure you that the
> remaining members are fully committed to continuing on with the project and
> we hope to recruit future members. Graduating will be a big accomplishment
> for this project and may give this project more visibility and growth.
> Also, on another note, I did not give the vote a deadline. If this list
> wishes to continue a vote, it will be open for 72 hours from my original
> email. I will close the vote Nov 8th at noon EST.
> thanks,Reza
>

I for sure understand and share the concern. One of the reasons for a
project to show it can grow a community.

The project seems to have a fine technical base, but the lack of community
growth is a major concern for me. Would it not be wise to postpone the
graduation, and get the community to grow first ?

Why do you think graduating will give growth or even more visibility ?

rgds
jan i.


>   From: John D. Ament 
>  To: "general@incubator.apache.org" ; Reza <
> reza.nagh...@yahoo.com>
>  Sent: Wednesday, November 5, 2014 7:37 PM
>  Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator
>
> Hi,
>
> Should we perhaps discuss it first?
>
> Seems a little weird to have such a small team to begin with.  How have you
> grown?
>
> John
>
>
>
> On Wed, Nov 5, 2014 at 10:27 AM, Reza 
> wrote:
>
> > So another graduation vote thread..! The Apache DeviceMap project would
> > like to graduate from the incubator. The project has made a lot of
> progress
> > in the past 6 months and all project members have voted positively for
> this
> > measure. We got 4 +1 votes from PMC members, 2 +1 votes from IPMC members
> > (Bertrand and Kevan), and no 0 or -1 votes [0].
> >
> >
> > This is the incubator vote thread to decide if the Apache DeviceMap
> > project graduates from the incubator. The resolution is at the bottom of
> > this email and attached.
> >
> >
> > [ ] +1 Graduate Apache DeviceMap from the Incubator.
> >
> > [ ] +0 Don't care.
> >
> > [ ] -1 Don't graduate Apache DeviceMap from the Incubator because ...
> >
> >
> > [0]
> >
> http://mail-archives.apache.org/mod_mbox/incubator-devicemap-dev/201411.mbox/%3C394358326.437830.1415058677229.JavaMail.yahoo%40jws106134.mail.bf1.yahoo.com%3E
> >
> >
> > ---
> >
> >
> > Establish the Apache DeviceMap 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 the maintenance and expansion of a data repository related to devices,
> > their operating systems and web browsers, and an API for classifying said
> > features.
> >
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC),
> > to be known as the "Apache DeviceMap Project", be and hereby is
> established
> > pursuant to Bylaws of the Foundation; and be it further
> >
> >
> > RESOLVED, that the Apache DeviceMap Project be and hereby is responsible
> > for the maintenance and expansion of a data repository related to
> devices,
> > their operating systems and web browsers, and an API for classifying said
> > features; and be it further
> >
> >
> > RESOLVED, that the office of "Vice President, Apache DeviceMap" 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 DeviceMap Project,
> and
> > to have primary responsibility for management of the projects within the
> > scope of responsibility of the Apache DeviceMap 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 DeviceMapProject:
> >
> >
> >* Reza Naghibi
> >
> >* Werner Keil  
> >
> >* Eberhard Speer Jr.  
> >
> >* Radu Cotescu
> >
> >* Bertrand Delacretaz  
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Reza Naghibi be appointed to
> > the office of Vice President, Apache DeviceMap, 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
> >
> >
> > RESO

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

[jan i]

Hi Seetharam

No need for apologies, we are all humans. Its nice though to see a logical
explanation.

Hope you are well now.

rgds
jan i.


On 6 November 2014 07:54, Seetharam Venkatesh 
wrote:

> Apologies, I don't know how I missed it. I had voted it earlier but
> apparently that vote was canceled and I missed the second call for vote
> since I was out sick for a week.
>
>
> On Wed, Nov 5, 2014 at 8:46 AM, Branko Čibej  wrote:
>
> > On 05.11.2014 16:32, Srikanth Sundarrajan wrote:
> > > Hi Brane,
> > >No, He just didn't get to it before the vote was closed. As I had
> > stated in my earlier response, he has already expressed his views on
> > graduation in the earlier discuss thread that preceded the vote. Adding
> it
> > here for reference.
> >
> > Ah. Thanks for clarifying.
> >
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201410.mbox/%3CCAFfn_Rru5Q%3Dps3EMEneUsqUyuy7p5quyp35YHdkbE4o-p%2BpmJw%40mail.gmail.com%3E
> > >
> > > Regards
> > > Srikanth Sundarrajan
> > >
> > >> Date: Wed, 5 Nov 2014 16:27:53 +0100
> > >> From: br...@apache.org
> > >> To: general@incubator.apache.org
> > >> Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> > >>
> > >> On 05.11.2014 16:05, Srikanth Sundarrajan wrote:
> > >>> Hi Jan,
> > >>> Venkatesh Seetharam is extremely active on the project, but
> > couldn't vote on this thread,
> > >> Why not? Are you guys by any chance treating project committers and
> PPMC
> > >> members differently?
> > >>
> > >> -- Brane
> > >>
> > >> -
> > >> 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
> >
> >
>
>
> --
> Regards,
> Venkatesh
>
> “Perfection (in design) is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.”
> - Antoine de Saint-Exupéry
>

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Bertrand Delacretaz]

Hi,

On Thu, Nov 6, 2014 at 10:12 AM, jan i  wrote:
> ...The project seems to have a fine technical base, but the lack of community
> growth is a major concern for me. Would it not be wise to postpone the
> graduation, and get the community to grow first ?...

As Reza says, only two of the initial committers listed at [1] are
part of the upcoming PMC, so one could argue that the community has
rebuilt itself during incubation, which is a good sign for the future
of the project.

That being said, I agree that a PMC with five members is really small,
but my feeling is that due to the project's scope its community will
remain small, and I don't see how staying in the Incubator would help
it grow more than graduating. That's why, as a DeviceMap mentor, I
have recommended graduation.

-Bertrand

[1] http://wiki.apache.org/incubator/DeviceMapProposal

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

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

[Bertrand Delacretaz]

On Wed, Nov 5, 2014 at 2:48 PM, Jean-Baptiste Onofré  wrote:
> ...This is the Incubator vote to decide if Apache Falcon should graduate from
> the Incubator. Please see the resolution later in this e-mail...

+1 to graduation and to the resolution.

-Bertrand

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

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Sean Owen]

I don't have enough knowledge of DeviceMap to have much opinion. Going
by the book 
(http://incubator.apache.org/incubation/Incubation_Policy.html#Minimum+Graduation+Requirements)
at least 3 committers, presumably active, are as required as anything
can be said to be.

There were 12 committers proposed at the outset, 10 of which dropped
away (?), with 3 others added since. 5 > 3, and glancing at the SVN
log, there are in fact 3 active committers in the last few months. So
I think this minimally passes the incubator guideline.

The trend is worrying though and I share the sentiment that, well, is
there a real hurry if this is just minimally sufficient to graduate?

On Thu, Nov 6, 2014 at 9:37 AM, Bertrand Delacretaz
 wrote:
> Hi,
>
> On Thu, Nov 6, 2014 at 10:12 AM, jan i  wrote:
>> ...The project seems to have a fine technical base, but the lack of community
>> growth is a major concern for me. Would it not be wise to postpone the
>> graduation, and get the community to grow first ?...
>
> As Reza says, only two of the initial committers listed at [1] are
> part of the upcoming PMC, so one could argue that the community has
> rebuilt itself during incubation, which is a good sign for the future
> of the project.
>
> That being said, I agree that a PMC with five members is really small,
> but my feeling is that due to the project's scope its community will
> remain small, and I don't see how staying in the Incubator would help
> it grow more than graduating. That's why, as a DeviceMap mentor, I
> have recommended graduation.
>
> -Bertrand
>
> [1] http://wiki.apache.org/incubator/DeviceMapProposal
>
> -
> 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 DeviceMap from the incubator

[John D. Ament]

Sean,

If you want to discuss graduation guide, here are the steps I'm noticing as
missing.  Lines copied straight from the [guide]:


   - FWD the [VOTE] e-mail to the general list, or
   - Send a different copy to the general list indicating that a graduation
   community [VOTE] is in progress
   - The resolution
    should
   be proposed on the general incubator list
 before
   a VOTE  is started to
   allow feedback. Once a consensus has been reached, a VOTE should be
   started on the same general incubator list by a member of the PPMC
    proposing that the IPMC
   

recommends
   the resolution to theBoard
   

   .

- John

[guide]: http://incubator.apache.org/guides/graduation.html#process

On Thu, Nov 6, 2014 at 6:18 AM, Sean Owen  wrote:

> I don't have enough knowledge of DeviceMap to have much opinion. Going
> by the book (
> http://incubator.apache.org/incubation/Incubation_Policy.html#Minimum+Graduation+Requirements
> )
> at least 3 committers, presumably active, are as required as anything
> can be said to be.
>
> There were 12 committers proposed at the outset, 10 of which dropped
> away (?), with 3 others added since. 5 > 3, and glancing at the SVN
> log, there are in fact 3 active committers in the last few months. So
> I think this minimally passes the incubator guideline.
>
> The trend is worrying though and I share the sentiment that, well, is
> there a real hurry if this is just minimally sufficient to graduate?
>
> On Thu, Nov 6, 2014 at 9:37 AM, Bertrand Delacretaz
>  wrote:
> > Hi,
> >
> > On Thu, Nov 6, 2014 at 10:12 AM, jan i  wrote:
> >> ...The project seems to have a fine technical base, but the lack of
> community
> >> growth is a major concern for me. Would it not be wise to postpone the
> >> graduation, and get the community to grow first ?...
> >
> > As Reza says, only two of the initial committers listed at [1] are
> > part of the upcoming PMC, so one could argue that the community has
> > rebuilt itself during incubation, which is a good sign for the future
> > of the project.
> >
> > That being said, I agree that a PMC with five members is really small,
> > but my feeling is that due to the project's scope its community will
> > remain small, and I don't see how staying in the Incubator would help
> > it grow more than graduating. That's why, as a DeviceMap mentor, I
> > have recommended graduation.
> >
> > -Bertrand
> >
> > [1] http://wiki.apache.org/incubator/DeviceMapProposal
> >
> > -
> > 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 DeviceMap from the incubator

[Bertrand Delacretaz]

Hi,

On Thu, Nov 6, 2014 at 12:18 PM, Sean Owen  wrote:
> ...glancing at the SVN
> log, there are in fact 3 active committers in the last few months. So
> I think this minimally passes the incubator guideline...

Yes, agreed.

>
>... The trend is worrying though and I share the sentiment that, well, is
> there a real hurry if this is just minimally sufficient to graduate?..

DeviceMap has been in the incubator for almost 3 years now, its
community is minimal but functional, it has made several releases and
rebuilt its small community after losing many of the initial
committers.

So the mentors feel that there's no benefit in leaving it in the
Incubator. Best case, the community grows, worst case it becomes too
small and moves to attic.apache.org. The same might happen if it stays
in the Incubator, with no benefit AFAICS.

-Bertrand

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

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Bertrand Delacretaz]

Hi,

On Thu, Nov 6, 2014 at 12:46 PM, John D. Ament  wrote:
> ...   - FWD the [VOTE] e-mail to the general list, or
>- Send a different copy to the general list indicating that a graduation
>community [VOTE] is in progress..

Reza has included the vote link in this thread.

> ...   - The resolution
> should
>be proposed on the general incubator list
>  before
>a VOTE  is started...

We discussed this on the devicemap dev list and as several recent
graduations skipped this step I suggested skipping it as well,
indicating that a discussion that derails the vote is not the end of
the world.

The discussion is happening now and that's fine, let's work on
building consensus for graduating now or later, and if needed the vote
can be restarted.

As I explained in this thread already, I'm in favor of graduating now,
even with this small community, and AFAIK Kevan Miller who's the other
active mentor shares this opinion.

-Bertrand

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

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[jan i]

On 6 November 2014 13:19, Bertrand Delacretaz 
wrote:

> Hi,
>
> On Thu, Nov 6, 2014 at 12:46 PM, John D. Ament 
> wrote:
> > ...   - FWD the [VOTE] e-mail to the general list, or
> >- Send a different copy to the general list indicating that a
> graduation
> >community [VOTE] is in progress..
>
> Reza has included the vote link in this thread.
>
> > ...   - The resolution
> >
> should
> >be proposed on the general incubator list
> >  before
> >a VOTE  is started...
>
> We discussed this on the devicemap dev list and as several recent
> graduations skipped this step I suggested skipping it as well,
> indicating that a discussion that derails the vote is not the end of
> the world.
>
> The discussion is happening now and that's fine, let's work on
> building consensus for graduating now or later, and if needed the vote
> can be restarted.
>

> As I explained in this thread already, I'm in favor of graduating now,
> even with this small community, and AFAIK Kevan Miller who's the other
> active mentor shares this opinion.
>
I am still sceptical with regard to the small community, but Bertrand's
words convinced me that there are no further benefits for devicemap to be
in incubator.

so I am also in favour of graduating now.

rgds
jan i.


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

Re: [VOTE] Accept HTrace into the Apache Incubator

[Tim Williams]

+1

--tim

On Wed, Nov 5, 2014 at 2:36 PM, Roman Shaposhnik  wrote:
> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:
>> Following the discussion earlier in the thread:
>>http://s.apache.org/Dk7
>>
>> I would like to call a VOTE for accepting HTrace
>> as a new incubator project.
>>
>> The proposal is available at:
>>
>> https://wiki.apache.org/incubator/HTraceProposal
>>(a full version of the proposal is attached)
>>
>> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
>>
>>  [ ] +1 accept Lens in the Incubator
>>  [ ] ±0
>>  [ ] -1 because...
>
> Thanks,
> Roman.
>
> == Abstract ==
> HTrace is a tracing framework intended for use with distributed
> systems written in java.
>
> == Proposal ==
> HTrace is an aid for understanding system behavior and for reasoning
> about performance
> issues in distributed systems. HTrace is primarily a low impedance
> library that a java
> distributed system can incorporate to generate ‘breadcrumbs’ or
> ‘traces’ along the path
> of execution, even as it crosses processes and machines. HTrace also
> includes various
> tools and glue for collecting, processing and ‘visualizing’ captured
> execution traces
> for analysis ex post facto of where time was spent and what resources
> were consumed.
>
> == Background ==
> Distributed systems are made up of multiple software components
> running on multiple
> computers connected by networks. Debugging or profiling operations run
> over non-trivial
> distributed systems -- figuring execution paths and what services, machines, 
> and
> libraries participated in the processing of a request -- can be involved.
>
> == Rationale ==
> Rather than have each distributed system build its own custom
> ‘tracing’ libraries,
> ideally all would use a single project that provides necessary
> primitives and saves
> each project building its own visualizations and processing tools anew.
>
> Google described “...[a] large-scale distributed systems tracing 
> infrastructure”
> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper
> tells a compelling story of what is possible when disparate systems 
> standardize
> on a single tracing library and cooperate, ‘passing the baton’, filling out
> trace context as executions cross systems.
>
> HTrace aims to provide a rough equivalent in open source of the described core
> Dapper tools and library.  As it is adopted by more projects, there will be a
> ‘network effect’ as HTrace will provide a more comprehensive view of activity
> on the cluster.  For example, as HDFS gets HTrace support, we can connect this
> with the HTrace support in HBase to follow HBase requests as they enter HDFS.
>
> Given the success of HTrace depends on its being integrated by many  projects,
> HTrace should be perceived as unhampered, free of any commercial, political,
> or legal ‘taint’. Being an Apache project would help in this regard.
>
> == Initial Goals ==
> HTrace is a small project of narrow scope but with a grand vision:
>   * Move the HTrace source and repository to Apache, a vendor-neutral
> location. Currently HTrace resides at a Cloudera-hosted repository.
>   * Add past contributors as committers and institute Apache governance.
>   * Evangelize and encourage HTrace diffusion. Initially we will
> continue a focus on the Hadoop space since that is where most of the
> initial contributors work and it is where HTrace has been initially
> deployed.
>   * Building out the standalone visualization tool that ships with HTrace.
>   * Build more community and add more committers
>
> == Current Status ==
> Currently HTrace has a viable Java trace library that can be interpolated
> to create ‘traces’.  The work that needs to be done on this library is mostly
> bug fixes, ease-of-use improvements, and performance tweaks.  In the future,
> we may add libraries for other languages besides Java.
>
> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> (a tracing
> sink and visualization system developed by Twitter
> https://github.com/twitter/zipkin),
> or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
> (https://code.google.com/p/python-graph/).
>
> Since the initial sprint in the summer of 2012 which saw HTrace patches 
> proposed
> for Apache HDFS and committed to Apache HBase, development has been sporadic;
> mostly a single developer or two adding a feature or bug fixing. HTrace is
> currently undergoing a new “spurt” of development with the effort to get 
> HTrace
> added to Apache HDFS revived and a new standalone viewing facility being added
> in to HTrace itself.
>
> HTrace has been integrated by Apache Phoenix.
>
>
> === Meritocracy ===
> HTrace, up to this, has been run by Apache committers and PMC members.
> We want to
> build out a diverse developer and user community and run the HTrace project in
> the Apache way.  Users and new contributors will be treated with respect and
> welcomed; they will earn merit in the 

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Reza]

>> Why do you think graduating will give growth or even more visibility ?

No specific reason other than its just another accomplishment for the project. 
Active projects tend to garner more attention than inactive ones. But im just 
speculating, so that statement is far from fact.

Reza
  From: jan i 
 To: general@incubator.apache.org; Reza  
 Sent: Thursday, November 6, 2014 4:12 AM
 Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator
   


On 6 November 2014 03:31, Reza  wrote:

Of course, discussion is more than welcomed.
>> Seems a little weird to have such a small team to begin with.  How have you 
>>grown?
This is a concern of the project. The PMC is indeed small. More than half of 
the original group has not participated in the last year and have not voiced 
that they would like to continue on with the project, leaving us with the group 
listed in the resolution. I do not know why these people decided not to 
continue their participation, but I can assure you that the remaining members 
are fully committed to continuing on with the project and we hope to recruit 
future members. Graduating will be a big accomplishment for this project and 
may give this project more visibility and growth.
Also, on another note, I did not give the vote a deadline. If this list wishes 
to continue a vote, it will be open for 72 hours from my original email. I will 
close the vote Nov 8th at noon EST.
thanks,Reza


I for sure understand and share the concern. One of the reasons for a project 
to show it can grow a community.

The project seems to have a fine technical base, but the lack of community 
growth is a major concern for me. Would it not be wise to postpone the 
graduation, and get the community to grow first ?

Why do you think graduating will give growth or even more visibility ?

rgds
jan i.


 

      From: John D. Ament 
 To: "general@incubator.apache.org" ; Reza 

 Sent: Wednesday, November 5, 2014 7:37 PM
 Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator

Hi,

Should we perhaps discuss it first?

Seems a little weird to have such a small team to begin with.  How have you
grown?

John



On Wed, Nov 5, 2014 at 10:27 AM, Reza 
wrote:

> So another graduation vote thread..! The Apache DeviceMap project would
> like to graduate from the incubator. The project has made a lot of progress
> in the past 6 months and all project members have voted positively for this
> measure. We got 4 +1 votes from PMC members, 2 +1 votes from IPMC members
> (Bertrand and Kevan), and no 0 or -1 votes [0].
>
>
> This is the incubator vote thread to decide if the Apache DeviceMap
> project graduates from the incubator. The resolution is at the bottom of
> this email and attached.
>
>
> [ ] +1 Graduate Apache DeviceMap from the Incubator.
>
> [ ] +0 Don't care.
>
> [ ] -1 Don't graduate Apache DeviceMap from the Incubator because ...
>
>
> [0]
> http://mail-archives.apache.org/mod_mbox/incubator-devicemap-dev/201411.mbox/%3C394358326.437830.1415058677229.JavaMail.yahoo%40jws106134.mail.bf1.yahoo.com%3E
>
>
> ---
>
>
> Establish the Apache DeviceMap 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 the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache DeviceMap Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache DeviceMap Project be and hereby is responsible
> for the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache DeviceMap" 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 DeviceMap Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache DeviceMap 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 DeviceMapProject:
>
>
>    * Reza Naghibi                    
>
>    * Werner Keil                      
>
>    * Eberhard Speer Jr.              
>
>    * Radu Cotescu                    
>
>    * Bertrand Delacretaz              
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Reza Naghibi be appointed to
> the office of Vice President, Apache DeviceMap, to serve in accordance with
> and 

Re: [VOTE] Graduation of Apache DeviceMap from the incubator

[Reza]

>> Why do you think graduating will give growth or even more visibility ?

No specific reason other than its just another accomplishment for the project. 
Active projects tend to garner more attention than inactive ones. But im just 
speculating, so that statement is far from fact.

Reza
  From: jan i 
 To: general@incubator.apache.org; Reza  
 Sent: Thursday, November 6, 2014 4:12 AM
 Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator
   


On 6 November 2014 03:31, Reza  wrote:

Of course, discussion is more than welcomed.
>> Seems a little weird to have such a small team to begin with.  How have you 
>>grown?
This is a concern of the project. The PMC is indeed small. More than half of 
the original group has not participated in the last year and have not voiced 
that they would like to continue on with the project, leaving us with the group 
listed in the resolution. I do not know why these people decided not to 
continue their participation, but I can assure you that the remaining members 
are fully committed to continuing on with the project and we hope to recruit 
future members. Graduating will be a big accomplishment for this project and 
may give this project more visibility and growth.
Also, on another note, I did not give the vote a deadline. If this list wishes 
to continue a vote, it will be open for 72 hours from my original email. I will 
close the vote Nov 8th at noon EST.
thanks,Reza


I for sure understand and share the concern. One of the reasons for a project 
to show it can grow a community.

The project seems to have a fine technical base, but the lack of community 
growth is a major concern for me. Would it not be wise to postpone the 
graduation, and get the community to grow first ?

Why do you think graduating will give growth or even more visibility ?

rgds
jan i.


 

      From: John D. Ament 
 To: "general@incubator.apache.org" ; Reza 

 Sent: Wednesday, November 5, 2014 7:37 PM
 Subject: Re: [VOTE] Graduation of Apache DeviceMap from the incubator

Hi,

Should we perhaps discuss it first?

Seems a little weird to have such a small team to begin with.  How have you
grown?

John



On Wed, Nov 5, 2014 at 10:27 AM, Reza 
wrote:

> So another graduation vote thread..! The Apache DeviceMap project would
> like to graduate from the incubator. The project has made a lot of progress
> in the past 6 months and all project members have voted positively for this
> measure. We got 4 +1 votes from PMC members, 2 +1 votes from IPMC members
> (Bertrand and Kevan), and no 0 or -1 votes [0].
>
>
> This is the incubator vote thread to decide if the Apache DeviceMap
> project graduates from the incubator. The resolution is at the bottom of
> this email and attached.
>
>
> [ ] +1 Graduate Apache DeviceMap from the Incubator.
>
> [ ] +0 Don't care.
>
> [ ] -1 Don't graduate Apache DeviceMap from the Incubator because ...
>
>
> [0]
> http://mail-archives.apache.org/mod_mbox/incubator-devicemap-dev/201411.mbox/%3C394358326.437830.1415058677229.JavaMail.yahoo%40jws106134.mail.bf1.yahoo.com%3E
>
>
> ---
>
>
> Establish the Apache DeviceMap 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 the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache DeviceMap Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache DeviceMap Project be and hereby is responsible
> for the maintenance and expansion of a data repository related to devices,
> their operating systems and web browsers, and an API for classifying said
> features; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache DeviceMap" 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 DeviceMap Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache DeviceMap 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 DeviceMapProject:
>
>
>    * Reza Naghibi                    
>
>    * Werner Keil                      
>
>    * Eberhard Speer Jr.              
>
>    * Radu Cotescu                    
>
>    * Bertrand Delacretaz              
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Reza Naghibi be appointed to
> the office of Vice President, Apache DeviceMap, to serve in accordance with
> and 

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

[Alan Gates]

+1.

Alan.


Jean-Baptiste Onofré 
November 5, 2014 at 5:48
Hi all,

We wrapped up the vote on the Apache Falcon dev list in which the 
community expressed its desire to graduate to a top-level project.


The vote has passed with:
13 binding +1 votes
8 non-binding +1 votes
no 0 or -1 vote

This is the Incubator vote to decide if Apache Falcon should graduate 
from the Incubator. Please see the resolution later in this e-mail.

This vote is open for at least 72 hours.

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

Thanks,
Regards
JB

 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 Big Data management platform covering data 
pipelines, data motion, data lifecycle management, data discovery & 
governance


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


RESOLVED, that the Apache Falcon Project be and hereby is responsible 
for the creation and maintenance of software related to interactive 
analysis of large-scale datasets; and be it further RESOLVED, that the 
office of "Vice President, Apache Falcon" 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 Falcon Project, and to have 
primary responsibility for management of the projects within the scope 
of responsibility of the Apache Falcon 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 Falcon Project:


* Srikanth Sundarrajan 
* Venkatesh Seetharam 
* Shwetha GS 
* Shaik Idris 
* Sanjay Radia 
* Sharad Agarwal 
* Amareshwari SR 
* Samarth Gupta 
* Rishu Mehrothra 
* Arpit Gupta 
* Suhas Vasu 
* Jean-Baptiste Onofré 
* Ruslan Ostafiychuk 
* Raghav Kumar Gautam 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be 
appointed to the office of Vice President, Apache Falcon, 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 Falcon Project be and hereby is tasked with 
the migration and rationalization of the Apache Incubator Falcon 
podling; and be it further


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





--
Sent with Postbox 

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Accept HTrace into the Apache Incubator

[Colin McCabe]

+1 (non-binding)

Colin

On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik  wrote:
> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:
>> Following the discussion earlier in the thread:
>>http://s.apache.org/Dk7
>>
>> I would like to call a VOTE for accepting HTrace
>> as a new incubator project.
>>
>> The proposal is available at:
>>
>> https://wiki.apache.org/incubator/HTraceProposal
>>(a full version of the proposal is attached)
>>
>> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
>>
>>  [ ] +1 accept Lens in the Incubator
>>  [ ] ±0
>>  [ ] -1 because...
>
> Thanks,
> Roman.
>
> == Abstract ==
> HTrace is a tracing framework intended for use with distributed
> systems written in java.
>
> == Proposal ==
> HTrace is an aid for understanding system behavior and for reasoning
> about performance
> issues in distributed systems. HTrace is primarily a low impedance
> library that a java
> distributed system can incorporate to generate ‘breadcrumbs’ or
> ‘traces’ along the path
> of execution, even as it crosses processes and machines. HTrace also
> includes various
> tools and glue for collecting, processing and ‘visualizing’ captured
> execution traces
> for analysis ex post facto of where time was spent and what resources
> were consumed.
>
> == Background ==
> Distributed systems are made up of multiple software components
> running on multiple
> computers connected by networks. Debugging or profiling operations run
> over non-trivial
> distributed systems -- figuring execution paths and what services, machines, 
> and
> libraries participated in the processing of a request -- can be involved.
>
> == Rationale ==
> Rather than have each distributed system build its own custom
> ‘tracing’ libraries,
> ideally all would use a single project that provides necessary
> primitives and saves
> each project building its own visualizations and processing tools anew.
>
> Google described “...[a] large-scale distributed systems tracing 
> infrastructure”
> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper
> tells a compelling story of what is possible when disparate systems 
> standardize
> on a single tracing library and cooperate, ‘passing the baton’, filling out
> trace context as executions cross systems.
>
> HTrace aims to provide a rough equivalent in open source of the described core
> Dapper tools and library.  As it is adopted by more projects, there will be a
> ‘network effect’ as HTrace will provide a more comprehensive view of activity
> on the cluster.  For example, as HDFS gets HTrace support, we can connect this
> with the HTrace support in HBase to follow HBase requests as they enter HDFS.
>
> Given the success of HTrace depends on its being integrated by many  projects,
> HTrace should be perceived as unhampered, free of any commercial, political,
> or legal ‘taint’. Being an Apache project would help in this regard.
>
> == Initial Goals ==
> HTrace is a small project of narrow scope but with a grand vision:
>   * Move the HTrace source and repository to Apache, a vendor-neutral
> location. Currently HTrace resides at a Cloudera-hosted repository.
>   * Add past contributors as committers and institute Apache governance.
>   * Evangelize and encourage HTrace diffusion. Initially we will
> continue a focus on the Hadoop space since that is where most of the
> initial contributors work and it is where HTrace has been initially
> deployed.
>   * Building out the standalone visualization tool that ships with HTrace.
>   * Build more community and add more committers
>
> == Current Status ==
> Currently HTrace has a viable Java trace library that can be interpolated
> to create ‘traces’.  The work that needs to be done on this library is mostly
> bug fixes, ease-of-use improvements, and performance tweaks.  In the future,
> we may add libraries for other languages besides Java.
>
> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> (a tracing
> sink and visualization system developed by Twitter
> https://github.com/twitter/zipkin),
> or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
> (https://code.google.com/p/python-graph/).
>
> Since the initial sprint in the summer of 2012 which saw HTrace patches 
> proposed
> for Apache HDFS and committed to Apache HBase, development has been sporadic;
> mostly a single developer or two adding a feature or bug fixing. HTrace is
> currently undergoing a new “spurt” of development with the effort to get 
> HTrace
> added to Apache HDFS revived and a new standalone viewing facility being added
> in to HTrace itself.
>
> HTrace has been integrated by Apache Phoenix.
>
>
> === Meritocracy ===
> HTrace, up to this, has been run by Apache committers and PMC members.
> We want to
> build out a diverse developer and user community and run the HTrace project in
> the Apache way.  Users and new contributors will be treated with respect and
> welcomed; they will ear

Re: [VOTE] Accept HTrace into the Apache Incubator

[jan i]

+1 binding.

rgds
jan i

On 6 November 2014 18:49, Colin McCabe  wrote:

> +1 (non-binding)
>
> Colin
>
> On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik  wrote:
> > On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik 
> wrote:
> >> Following the discussion earlier in the thread:
> >>http://s.apache.org/Dk7
> >>
> >> I would like to call a VOTE for accepting HTrace
> >> as a new incubator project.
> >>
> >> The proposal is available at:
> >>
> >> https://wiki.apache.org/incubator/HTraceProposal
> >>(a full version of the proposal is attached)
> >>
> >> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> >>
> >>  [ ] +1 accept Lens in the Incubator
> >>  [ ] ±0
> >>  [ ] -1 because...
> >
> > Thanks,
> > Roman.
> >
> > == Abstract ==
> > HTrace is a tracing framework intended for use with distributed
> > systems written in java.
> >
> > == Proposal ==
> > HTrace is an aid for understanding system behavior and for reasoning
> > about performance
> > issues in distributed systems. HTrace is primarily a low impedance
> > library that a java
> > distributed system can incorporate to generate ‘breadcrumbs’ or
> > ‘traces’ along the path
> > of execution, even as it crosses processes and machines. HTrace also
> > includes various
> > tools and glue for collecting, processing and ‘visualizing’ captured
> > execution traces
> > for analysis ex post facto of where time was spent and what resources
> > were consumed.
> >
> > == Background ==
> > Distributed systems are made up of multiple software components
> > running on multiple
> > computers connected by networks. Debugging or profiling operations run
> > over non-trivial
> > distributed systems -- figuring execution paths and what services,
> machines, and
> > libraries participated in the processing of a request -- can be involved.
> >
> > == Rationale ==
> > Rather than have each distributed system build its own custom
> > ‘tracing’ libraries,
> > ideally all would use a single project that provides necessary
> > primitives and saves
> > each project building its own visualizations and processing tools anew.
> >
> > Google described “...[a] large-scale distributed systems tracing
> infrastructure”
> > in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The
> paper
> > tells a compelling story of what is possible when disparate systems
> standardize
> > on a single tracing library and cooperate, ‘passing the baton’, filling
> out
> > trace context as executions cross systems.
> >
> > HTrace aims to provide a rough equivalent in open source of the
> described core
> > Dapper tools and library.  As it is adopted by more projects, there will
> be a
> > ‘network effect’ as HTrace will provide a more comprehensive view of
> activity
> > on the cluster.  For example, as HDFS gets HTrace support, we can
> connect this
> > with the HTrace support in HBase to follow HBase requests as they enter
> HDFS.
> >
> > Given the success of HTrace depends on its being integrated by many
> projects,
> > HTrace should be perceived as unhampered, free of any commercial,
> political,
> > or legal ‘taint’. Being an Apache project would help in this regard.
> >
> > == Initial Goals ==
> > HTrace is a small project of narrow scope but with a grand vision:
> >   * Move the HTrace source and repository to Apache, a vendor-neutral
> > location. Currently HTrace resides at a Cloudera-hosted repository.
> >   * Add past contributors as committers and institute Apache governance.
> >   * Evangelize and encourage HTrace diffusion. Initially we will
> > continue a focus on the Hadoop space since that is where most of the
> > initial contributors work and it is where HTrace has been initially
> > deployed.
> >   * Building out the standalone visualization tool that ships with
> HTrace.
> >   * Build more community and add more committers
> >
> > == Current Status ==
> > Currently HTrace has a viable Java trace library that can be interpolated
> > to create ‘traces’.  The work that needs to be done on this library is
> mostly
> > bug fixes, ease-of-use improvements, and performance tweaks.  In the
> future,
> > we may add libraries for other languages besides Java.
> >
> > HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> > (a tracing
> > sink and visualization system developed by Twitter
> > https://github.com/twitter/zipkin),
> > or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
> > (https://code.google.com/p/python-graph/).
> >
> > Since the initial sprint in the summer of 2012 which saw HTrace patches
> proposed
> > for Apache HDFS and committed to Apache HBase, development has been
> sporadic;
> > mostly a single developer or two adding a feature or bug fixing. HTrace
> is
> > currently undergoing a new “spurt” of development with the effort to get
> HTrace
> > added to Apache HDFS revived and a new standalone viewing facility being
> added
> > in to HTrace itself.
> >
> > HTrace has been integrated by 

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

[jan i]

+1 (binding)

jan i

On 6 November 2014 17:50, Alan Gates  wrote:

> +1.
>
> Alan.
>
>   Jean-Baptiste Onofré 
>  November 5, 2014 at 5:48
> Hi all,
>
> We wrapped up the vote on the Apache Falcon dev list in which the
> community expressed its desire to graduate to a top-level project.
>
> The vote has passed with:
> 13 binding +1 votes
> 8 non-binding +1 votes
> no 0 or -1 vote
>
> This is the Incubator vote to decide if Apache Falcon should graduate from
> the Incubator. Please see the resolution later in this e-mail.
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache Falcon from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Falcon from the Incubator because ...
>
> Thanks,
> Regards
> JB
>
>  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 Big Data management platform covering data pipelines, data motion, data
> lifecycle management, data discovery & governance
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Falcon Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Falcon Project be and hereby is responsible for
> the creation and maintenance of software related to interactive analysis of
> large-scale datasets; and be it further RESOLVED, that the office of "Vice
> President, Apache Falcon" 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 Falcon Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the Apache
> Falcon 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 Falcon Project:
>
> * Srikanth Sundarrajan 
> * Venkatesh Seetharam 
> * Shwetha GS 
> * Shaik Idris 
> * Sanjay Radia 
> * Sharad Agarwal 
> * Amareshwari SR 
> * Samarth Gupta 
> * Rishu Mehrothra 
> * Arpit Gupta 
> * Suhas Vasu 
> * Jean-Baptiste Onofré 
> * Ruslan Ostafiychuk 
> * Raghav Kumar Gautam 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be
> appointed to the office of Vice President, Apache Falcon, 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 Falcon Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Falcon podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Falcon podling encumbered upon the Apache Incubator Project are hereafter
> discharged.
> 
>
>
> --
> Sent with Postbox 
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

Re: [VOTE] Accept HTrace into the Apache Incubator

[Jonathan Leavitt]

+1 (non-binding)

On Thu, Nov 6, 2014 at 9:56 AM, jan i  wrote:

> +1 binding.
>
> rgds
> jan i
>
> On 6 November 2014 18:49, Colin McCabe  wrote:
>
> > +1 (non-binding)
> >
> > Colin
> >
> > On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik 
> wrote:
> > > On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik 
> > wrote:
> > >> Following the discussion earlier in the thread:
> > >>http://s.apache.org/Dk7
> > >>
> > >> I would like to call a VOTE for accepting HTrace
> > >> as a new incubator project.
> > >>
> > >> The proposal is available at:
> > >>
> > >> https://wiki.apache.org/incubator/HTraceProposal
> > >>(a full version of the proposal is attached)
> > >>
> > >> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> > >>
> > >>  [ ] +1 accept Lens in the Incubator
> > >>  [ ] ±0
> > >>  [ ] -1 because...
> > >
> > > Thanks,
> > > Roman.
> > >
> > > == Abstract ==
> > > HTrace is a tracing framework intended for use with distributed
> > > systems written in java.
> > >
> > > == Proposal ==
> > > HTrace is an aid for understanding system behavior and for reasoning
> > > about performance
> > > issues in distributed systems. HTrace is primarily a low impedance
> > > library that a java
> > > distributed system can incorporate to generate ‘breadcrumbs’ or
> > > ‘traces’ along the path
> > > of execution, even as it crosses processes and machines. HTrace also
> > > includes various
> > > tools and glue for collecting, processing and ‘visualizing’ captured
> > > execution traces
> > > for analysis ex post facto of where time was spent and what resources
> > > were consumed.
> > >
> > > == Background ==
> > > Distributed systems are made up of multiple software components
> > > running on multiple
> > > computers connected by networks. Debugging or profiling operations run
> > > over non-trivial
> > > distributed systems -- figuring execution paths and what services,
> > machines, and
> > > libraries participated in the processing of a request -- can be
> involved.
> > >
> > > == Rationale ==
> > > Rather than have each distributed system build its own custom
> > > ‘tracing’ libraries,
> > > ideally all would use a single project that provides necessary
> > > primitives and saves
> > > each project building its own visualizations and processing tools anew.
> > >
> > > Google described “...[a] large-scale distributed systems tracing
> > infrastructure”
> > > in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure.
> The
> > paper
> > > tells a compelling story of what is possible when disparate systems
> > standardize
> > > on a single tracing library and cooperate, ‘passing the baton’, filling
> > out
> > > trace context as executions cross systems.
> > >
> > > HTrace aims to provide a rough equivalent in open source of the
> > described core
> > > Dapper tools and library.  As it is adopted by more projects, there
> will
> > be a
> > > ‘network effect’ as HTrace will provide a more comprehensive view of
> > activity
> > > on the cluster.  For example, as HDFS gets HTrace support, we can
> > connect this
> > > with the HTrace support in HBase to follow HBase requests as they enter
> > HDFS.
> > >
> > > Given the success of HTrace depends on its being integrated by many
> > projects,
> > > HTrace should be perceived as unhampered, free of any commercial,
> > political,
> > > or legal ‘taint’. Being an Apache project would help in this regard.
> > >
> > > == Initial Goals ==
> > > HTrace is a small project of narrow scope but with a grand vision:
> > >   * Move the HTrace source and repository to Apache, a vendor-neutral
> > > location. Currently HTrace resides at a Cloudera-hosted repository.
> > >   * Add past contributors as committers and institute Apache
> governance.
> > >   * Evangelize and encourage HTrace diffusion. Initially we will
> > > continue a focus on the Hadoop space since that is where most of the
> > > initial contributors work and it is where HTrace has been initially
> > > deployed.
> > >   * Building out the standalone visualization tool that ships with
> > HTrace.
> > >   * Build more community and add more committers
> > >
> > > == Current Status ==
> > > Currently HTrace has a viable Java trace library that can be
> interpolated
> > > to create ‘traces’.  The work that needs to be done on this library is
> > mostly
> > > bug fixes, ease-of-use improvements, and performance tweaks.  In the
> > future,
> > > we may add libraries for other languages besides Java.
> > >
> > > HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> > > (a tracing
> > > sink and visualization system developed by Twitter
> > > https://github.com/twitter/zipkin),
> > > or Apache HBase.  Executions can be viewed either in Zipkin or in
> pygraph
> > > (https://code.google.com/p/python-graph/).
> > >
> > > Since the initial sprint in the summer of 2012 which saw HTrace patches
> > proposed
> > > for Apache HDFS and committed to Apache HBase, development has been

Re: [VOTE] Accept HTrace into the Apache Incubator

[Masatake Iwasaki]

+1 (non-binding)

Masatake Iwasaki

(11/5/14, 11:36), Roman Shaposhnik wrote:

On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:

Following the discussion earlier in the thread:
http://s.apache.org/Dk7

I would like to call a VOTE for accepting HTrace
as a new incubator project.

The proposal is available at:

https://wiki.apache.org/incubator/HTraceProposal
(a full version of the proposal is attached)

Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC

  [ ] +1 accept Lens in the Incubator
  [ ] ±0
  [ ] -1 because...


Thanks,
Roman.

== Abstract ==
HTrace is a tracing framework intended for use with distributed
systems written in java.

== Proposal ==
HTrace is an aid for understanding system behavior and for reasoning
about performance
issues in distributed systems. HTrace is primarily a low impedance
library that a java
distributed system can incorporate to generate ‘breadcrumbs’ or
‘traces’ along the path
of execution, even as it crosses processes and machines. HTrace also
includes various
tools and glue for collecting, processing and ‘visualizing’ captured
execution traces
for analysis ex post facto of where time was spent and what resources
were consumed.

== Background ==
Distributed systems are made up of multiple software components
running on multiple
computers connected by networks. Debugging or profiling operations run
over non-trivial
distributed systems -- figuring execution paths and what services, machines, and
libraries participated in the processing of a request -- can be involved.

== Rationale ==
Rather than have each distributed system build its own custom
‘tracing’ libraries,
ideally all would use a single project that provides necessary
primitives and saves
each project building its own visualizations and processing tools anew.

Google described “...[a] large-scale distributed systems tracing infrastructure”
in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper
tells a compelling story of what is possible when disparate systems standardize
on a single tracing library and cooperate, ‘passing the baton’, filling out
trace context as executions cross systems.

HTrace aims to provide a rough equivalent in open source of the described core
Dapper tools and library.  As it is adopted by more projects, there will be a
‘network effect’ as HTrace will provide a more comprehensive view of activity
on the cluster.  For example, as HDFS gets HTrace support, we can connect this
with the HTrace support in HBase to follow HBase requests as they enter HDFS.

Given the success of HTrace depends on its being integrated by many  projects,
HTrace should be perceived as unhampered, free of any commercial, political,
or legal ‘taint’. Being an Apache project would help in this regard.

== Initial Goals ==
HTrace is a small project of narrow scope but with a grand vision:
   * Move the HTrace source and repository to Apache, a vendor-neutral
location. Currently HTrace resides at a Cloudera-hosted repository.
   * Add past contributors as committers and institute Apache governance.
   * Evangelize and encourage HTrace diffusion. Initially we will
continue a focus on the Hadoop space since that is where most of the
initial contributors work and it is where HTrace has been initially
deployed.
   * Building out the standalone visualization tool that ships with HTrace.
   * Build more community and add more committers

== Current Status ==
Currently HTrace has a viable Java trace library that can be interpolated
to create ‘traces’.  The work that needs to be done on this library is mostly
bug fixes, ease-of-use improvements, and performance tweaks.  In the future,
we may add libraries for other languages besides Java.

HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
(a tracing
sink and visualization system developed by Twitter
https://github.com/twitter/zipkin),
or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
(https://code.google.com/p/python-graph/).

Since the initial sprint in the summer of 2012 which saw HTrace patches proposed
for Apache HDFS and committed to Apache HBase, development has been sporadic;
mostly a single developer or two adding a feature or bug fixing. HTrace is
currently undergoing a new “spurt” of development with the effort to get HTrace
added to Apache HDFS revived and a new standalone viewing facility being added
in to HTrace itself.

HTrace has been integrated by Apache Phoenix.


=== Meritocracy ===
HTrace, up to this, has been run by Apache committers and PMC members.
We want to
build out a diverse developer and user community and run the HTrace project in
the Apache way.  Users and new contributors will be treated with respect and
welcomed; they will earn merit in the project by tendering quality patches
and support that move the project forward.  Those with a proven support and
quality patch track record will be encouraged to become committers.

=== Community ===
There are

Re: [VOTE] Accept HTrace into the Apache Incubator

[Elliott Clark]

+ 1 ( Non-Binding)

On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:

> +1 (non-binding)
>
> Masatake Iwasaki
>
>
> (11/5/14, 11:36), Roman Shaposhnik wrote:
>
>> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:
>>
>>> Following the discussion earlier in the thread:
>>> http://s.apache.org/Dk7
>>>
>>> I would like to call a VOTE for accepting HTrace
>>> as a new incubator project.
>>>
>>> The proposal is available at:
>>>
>>> https://wiki.apache.org/incubator/HTraceProposal
>>> (a full version of the proposal is attached)
>>>
>>> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
>>>
>>>   [ ] +1 accept Lens in the Incubator
>>>   [ ] ±0
>>>   [ ] -1 because...
>>>
>>
>> Thanks,
>> Roman.
>>
>> == Abstract ==
>> HTrace is a tracing framework intended for use with distributed
>> systems written in java.
>>
>> == Proposal ==
>> HTrace is an aid for understanding system behavior and for reasoning
>> about performance
>> issues in distributed systems. HTrace is primarily a low impedance
>> library that a java
>> distributed system can incorporate to generate ‘breadcrumbs’ or
>> ‘traces’ along the path
>> of execution, even as it crosses processes and machines. HTrace also
>> includes various
>> tools and glue for collecting, processing and ‘visualizing’ captured
>> execution traces
>> for analysis ex post facto of where time was spent and what resources
>> were consumed.
>>
>> == Background ==
>> Distributed systems are made up of multiple software components
>> running on multiple
>> computers connected by networks. Debugging or profiling operations run
>> over non-trivial
>> distributed systems -- figuring execution paths and what services,
>> machines, and
>> libraries participated in the processing of a request -- can be involved.
>>
>> == Rationale ==
>> Rather than have each distributed system build its own custom
>> ‘tracing’ libraries,
>> ideally all would use a single project that provides necessary
>> primitives and saves
>> each project building its own visualizations and processing tools anew.
>>
>> Google described “...[a] large-scale distributed systems tracing
>> infrastructure”
>> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The
>> paper
>> tells a compelling story of what is possible when disparate systems
>> standardize
>> on a single tracing library and cooperate, ‘passing the baton’, filling
>> out
>> trace context as executions cross systems.
>>
>> HTrace aims to provide a rough equivalent in open source of the described
>> core
>> Dapper tools and library.  As it is adopted by more projects, there will
>> be a
>> ‘network effect’ as HTrace will provide a more comprehensive view of
>> activity
>> on the cluster.  For example, as HDFS gets HTrace support, we can connect
>> this
>> with the HTrace support in HBase to follow HBase requests as they enter
>> HDFS.
>>
>> Given the success of HTrace depends on its being integrated by many
>> projects,
>> HTrace should be perceived as unhampered, free of any commercial,
>> political,
>> or legal ‘taint’. Being an Apache project would help in this regard.
>>
>> == Initial Goals ==
>> HTrace is a small project of narrow scope but with a grand vision:
>>* Move the HTrace source and repository to Apache, a vendor-neutral
>> location. Currently HTrace resides at a Cloudera-hosted repository.
>>* Add past contributors as committers and institute Apache governance.
>>* Evangelize and encourage HTrace diffusion. Initially we will
>> continue a focus on the Hadoop space since that is where most of the
>> initial contributors work and it is where HTrace has been initially
>> deployed.
>>* Building out the standalone visualization tool that ships with
>> HTrace.
>>* Build more community and add more committers
>>
>> == Current Status ==
>> Currently HTrace has a viable Java trace library that can be interpolated
>> to create ‘traces’.  The work that needs to be done on this library is
>> mostly
>> bug fixes, ease-of-use improvements, and performance tweaks.  In the
>> future,
>> we may add libraries for other languages besides Java.
>>
>> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
>> (a tracing
>> sink and visualization system developed by Twitter
>> https://github.com/twitter/zipkin),
>> or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
>> (https://code.google.com/p/python-graph/).
>>
>> Since the initial sprint in the summer of 2012 which saw HTrace patches
>> proposed
>> for Apache HDFS and committed to Apache HBase, development has been
>> sporadic;
>> mostly a single developer or two adding a feature or bug fixing. HTrace is
>> currently undergoing a new “spurt” of development with the effort to get
>> HTrace
>> added to Apache HDFS revived and a new standalone viewing facility being
>> added
>> in to HTrace itself.
>>
>> HTrace has been integrated by Apache Phoenix.
>>
>>
>> === Meritoc

Re: [VOTE] Accept HTrace into the Apache Incubator

[Dilli Arumugam]

+1 (non-binding)

On Thu, Nov 6, 2014 at 10:23 AM, Elliott Clark  wrote:

> + 1 ( Non-Binding)
>
> On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki <
> iwasak...@oss.nttdata.co.jp> wrote:
>
> > +1 (non-binding)
> >
> > Masatake Iwasaki
> >
> >
> > (11/5/14, 11:36), Roman Shaposhnik wrote:
> >
> >> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik 
> wrote:
> >>
> >>> Following the discussion earlier in the thread:
> >>> http://s.apache.org/Dk7
> >>>
> >>> I would like to call a VOTE for accepting HTrace
> >>> as a new incubator project.
> >>>
> >>> The proposal is available at:
> >>>
> >>> https://wiki.apache.org/incubator/HTraceProposal
> >>> (a full version of the proposal is attached)
> >>>
> >>> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> >>>
> >>>   [ ] +1 accept Lens in the Incubator
> >>>   [ ] ±0
> >>>   [ ] -1 because...
> >>>
> >>
> >> Thanks,
> >> Roman.
> >>
> >> == Abstract ==
> >> HTrace is a tracing framework intended for use with distributed
> >> systems written in java.
> >>
> >> == Proposal ==
> >> HTrace is an aid for understanding system behavior and for reasoning
> >> about performance
> >> issues in distributed systems. HTrace is primarily a low impedance
> >> library that a java
> >> distributed system can incorporate to generate ‘breadcrumbs’ or
> >> ‘traces’ along the path
> >> of execution, even as it crosses processes and machines. HTrace also
> >> includes various
> >> tools and glue for collecting, processing and ‘visualizing’ captured
> >> execution traces
> >> for analysis ex post facto of where time was spent and what resources
> >> were consumed.
> >>
> >> == Background ==
> >> Distributed systems are made up of multiple software components
> >> running on multiple
> >> computers connected by networks. Debugging or profiling operations run
> >> over non-trivial
> >> distributed systems -- figuring execution paths and what services,
> >> machines, and
> >> libraries participated in the processing of a request -- can be
> involved.
> >>
> >> == Rationale ==
> >> Rather than have each distributed system build its own custom
> >> ‘tracing’ libraries,
> >> ideally all would use a single project that provides necessary
> >> primitives and saves
> >> each project building its own visualizations and processing tools anew.
> >>
> >> Google described “...[a] large-scale distributed systems tracing
> >> infrastructure”
> >> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The
> >> paper
> >> tells a compelling story of what is possible when disparate systems
> >> standardize
> >> on a single tracing library and cooperate, ‘passing the baton’, filling
> >> out
> >> trace context as executions cross systems.
> >>
> >> HTrace aims to provide a rough equivalent in open source of the
> described
> >> core
> >> Dapper tools and library.  As it is adopted by more projects, there will
> >> be a
> >> ‘network effect’ as HTrace will provide a more comprehensive view of
> >> activity
> >> on the cluster.  For example, as HDFS gets HTrace support, we can
> connect
> >> this
> >> with the HTrace support in HBase to follow HBase requests as they enter
> >> HDFS.
> >>
> >> Given the success of HTrace depends on its being integrated by many
> >> projects,
> >> HTrace should be perceived as unhampered, free of any commercial,
> >> political,
> >> or legal ‘taint’. Being an Apache project would help in this regard.
> >>
> >> == Initial Goals ==
> >> HTrace is a small project of narrow scope but with a grand vision:
> >>* Move the HTrace source and repository to Apache, a vendor-neutral
> >> location. Currently HTrace resides at a Cloudera-hosted repository.
> >>* Add past contributors as committers and institute Apache
> governance.
> >>* Evangelize and encourage HTrace diffusion. Initially we will
> >> continue a focus on the Hadoop space since that is where most of the
> >> initial contributors work and it is where HTrace has been initially
> >> deployed.
> >>* Building out the standalone visualization tool that ships with
> >> HTrace.
> >>* Build more community and add more committers
> >>
> >> == Current Status ==
> >> Currently HTrace has a viable Java trace library that can be
> interpolated
> >> to create ‘traces’.  The work that needs to be done on this library is
> >> mostly
> >> bug fixes, ease-of-use improvements, and performance tweaks.  In the
> >> future,
> >> we may add libraries for other languages besides Java.
> >>
> >> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> >> (a tracing
> >> sink and visualization system developed by Twitter
> >> https://github.com/twitter/zipkin),
> >> or Apache HBase.  Executions can be viewed either in Zipkin or in
> pygraph
> >> (https://code.google.com/p/python-graph/).
> >>
> >> Since the initial sprint in the summer of 2012 which saw HTrace patches
> >> proposed
> >> for Apache HDFS and committed to Apache HBase, development has been
> >> sporadic;
> >

Re: [VOTE] Accept HTrace into the Apache Incubator

[Aditya]

+1 (non-binding).

On Thu, Nov 6, 2014 at 11:10 AM, Dilli Arumugam 
wrote:

> +1 (non-binding)
>
> On Thu, Nov 6, 2014 at 10:23 AM, Elliott Clark  wrote:
>
> > + 1 ( Non-Binding)
> >
> > On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki <
> > iwasak...@oss.nttdata.co.jp> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Masatake Iwasaki
> > >
> > >
> > > (11/5/14, 11:36), Roman Shaposhnik wrote:
> > >
> > >> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik 
> > wrote:
> > >>
> > >>> Following the discussion earlier in the thread:
> > >>> http://s.apache.org/Dk7
> > >>>
> > >>> I would like to call a VOTE for accepting HTrace
> > >>> as a new incubator project.
> > >>>
> > >>> The proposal is available at:
> > >>>
> > >>> https://wiki.apache.org/incubator/HTraceProposal
> > >>> (a full version of the proposal is attached)
> > >>>
> > >>> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> > >>>
> > >>>   [ ] +1 accept Lens in the Incubator
> > >>>   [ ] ±0
> > >>>   [ ] -1 because...
> > >>>
> > >>
> > >> Thanks,
> > >> Roman.
> > >>
> > >> == Abstract ==
> > >> HTrace is a tracing framework intended for use with distributed
> > >> systems written in java.
> > >>
> > >> == Proposal ==
> > >> HTrace is an aid for understanding system behavior and for reasoning
> > >> about performance
> > >> issues in distributed systems. HTrace is primarily a low impedance
> > >> library that a java
> > >> distributed system can incorporate to generate ‘breadcrumbs’ or
> > >> ‘traces’ along the path
> > >> of execution, even as it crosses processes and machines. HTrace also
> > >> includes various
> > >> tools and glue for collecting, processing and ‘visualizing’ captured
> > >> execution traces
> > >> for analysis ex post facto of where time was spent and what resources
> > >> were consumed.
> > >>
> > >> == Background ==
> > >> Distributed systems are made up of multiple software components
> > >> running on multiple
> > >> computers connected by networks. Debugging or profiling operations run
> > >> over non-trivial
> > >> distributed systems -- figuring execution paths and what services,
> > >> machines, and
> > >> libraries participated in the processing of a request -- can be
> > involved.
> > >>
> > >> == Rationale ==
> > >> Rather than have each distributed system build its own custom
> > >> ‘tracing’ libraries,
> > >> ideally all would use a single project that provides necessary
> > >> primitives and saves
> > >> each project building its own visualizations and processing tools
> anew.
> > >>
> > >> Google described “...[a] large-scale distributed systems tracing
> > >> infrastructure”
> > >> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure.
> The
> > >> paper
> > >> tells a compelling story of what is possible when disparate systems
> > >> standardize
> > >> on a single tracing library and cooperate, ‘passing the baton’,
> filling
> > >> out
> > >> trace context as executions cross systems.
> > >>
> > >> HTrace aims to provide a rough equivalent in open source of the
> > described
> > >> core
> > >> Dapper tools and library.  As it is adopted by more projects, there
> will
> > >> be a
> > >> ‘network effect’ as HTrace will provide a more comprehensive view of
> > >> activity
> > >> on the cluster.  For example, as HDFS gets HTrace support, we can
> > connect
> > >> this
> > >> with the HTrace support in HBase to follow HBase requests as they
> enter
> > >> HDFS.
> > >>
> > >> Given the success of HTrace depends on its being integrated by many
> > >> projects,
> > >> HTrace should be perceived as unhampered, free of any commercial,
> > >> political,
> > >> or legal ‘taint’. Being an Apache project would help in this regard.
> > >>
> > >> == Initial Goals ==
> > >> HTrace is a small project of narrow scope but with a grand vision:
> > >>* Move the HTrace source and repository to Apache, a vendor-neutral
> > >> location. Currently HTrace resides at a Cloudera-hosted repository.
> > >>* Add past contributors as committers and institute Apache
> > governance.
> > >>* Evangelize and encourage HTrace diffusion. Initially we will
> > >> continue a focus on the Hadoop space since that is where most of the
> > >> initial contributors work and it is where HTrace has been initially
> > >> deployed.
> > >>* Building out the standalone visualization tool that ships with
> > >> HTrace.
> > >>* Build more community and add more committers
> > >>
> > >> == Current Status ==
> > >> Currently HTrace has a viable Java trace library that can be
> > interpolated
> > >> to create ‘traces’.  The work that needs to be done on this library is
> > >> mostly
> > >> bug fixes, ease-of-use improvements, and performance tweaks.  In the
> > >> future,
> > >> we may add libraries for other languages besides Java.
> > >>
> > >> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> > >> (a tracing
> > >> sink and visualization system developed by Twitter
> > >> https:

Re: [VOTE] Accept HTrace into the Apache Incubator

[Arvind Prabhakar]

+1 (binding)

Regards,
Arvind Prabhakar

On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik  wrote:

> On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:
> > Following the discussion earlier in the thread:
> >http://s.apache.org/Dk7
> >
> > I would like to call a VOTE for accepting HTrace
> > as a new incubator project.
> >
> > The proposal is available at:
> >
> > https://wiki.apache.org/incubator/HTraceProposal
> >(a full version of the proposal is attached)
> >
> > Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
> >
> >  [ ] +1 accept Lens in the Incubator
> >  [ ] ±0
> >  [ ] -1 because...
>
> Thanks,
> Roman.
>
> == Abstract ==
> HTrace is a tracing framework intended for use with distributed
> systems written in java.
>
> == Proposal ==
> HTrace is an aid for understanding system behavior and for reasoning
> about performance
> issues in distributed systems. HTrace is primarily a low impedance
> library that a java
> distributed system can incorporate to generate ‘breadcrumbs’ or
> ‘traces’ along the path
> of execution, even as it crosses processes and machines. HTrace also
> includes various
> tools and glue for collecting, processing and ‘visualizing’ captured
> execution traces
> for analysis ex post facto of where time was spent and what resources
> were consumed.
>
> == Background ==
> Distributed systems are made up of multiple software components
> running on multiple
> computers connected by networks. Debugging or profiling operations run
> over non-trivial
> distributed systems -- figuring execution paths and what services,
> machines, and
> libraries participated in the processing of a request -- can be involved.
>
> == Rationale ==
> Rather than have each distributed system build its own custom
> ‘tracing’ libraries,
> ideally all would use a single project that provides necessary
> primitives and saves
> each project building its own visualizations and processing tools anew.
>
> Google described “...[a] large-scale distributed systems tracing
> infrastructure”
> in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The
> paper
> tells a compelling story of what is possible when disparate systems
> standardize
> on a single tracing library and cooperate, ‘passing the baton’, filling out
> trace context as executions cross systems.
>
> HTrace aims to provide a rough equivalent in open source of the described
> core
> Dapper tools and library.  As it is adopted by more projects, there will
> be a
> ‘network effect’ as HTrace will provide a more comprehensive view of
> activity
> on the cluster.  For example, as HDFS gets HTrace support, we can connect
> this
> with the HTrace support in HBase to follow HBase requests as they enter
> HDFS.
>
> Given the success of HTrace depends on its being integrated by many
> projects,
> HTrace should be perceived as unhampered, free of any commercial,
> political,
> or legal ‘taint’. Being an Apache project would help in this regard.
>
> == Initial Goals ==
> HTrace is a small project of narrow scope but with a grand vision:
>   * Move the HTrace source and repository to Apache, a vendor-neutral
> location. Currently HTrace resides at a Cloudera-hosted repository.
>   * Add past contributors as committers and institute Apache governance.
>   * Evangelize and encourage HTrace diffusion. Initially we will
> continue a focus on the Hadoop space since that is where most of the
> initial contributors work and it is where HTrace has been initially
> deployed.
>   * Building out the standalone visualization tool that ships with HTrace.
>   * Build more community and add more committers
>
> == Current Status ==
> Currently HTrace has a viable Java trace library that can be interpolated
> to create ‘traces’.  The work that needs to be done on this library is
> mostly
> bug fixes, ease-of-use improvements, and performance tweaks.  In the
> future,
> we may add libraries for other languages besides Java.
>
> HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
> (a tracing
> sink and visualization system developed by Twitter
> https://github.com/twitter/zipkin),
> or Apache HBase.  Executions can be viewed either in Zipkin or in pygraph
> (https://code.google.com/p/python-graph/).
>
> Since the initial sprint in the summer of 2012 which saw HTrace patches
> proposed
> for Apache HDFS and committed to Apache HBase, development has been
> sporadic;
> mostly a single developer or two adding a feature or bug fixing. HTrace is
> currently undergoing a new “spurt” of development with the effort to get
> HTrace
> added to Apache HDFS revived and a new standalone viewing facility being
> added
> in to HTrace itself.
>
> HTrace has been integrated by Apache Phoenix.
>
>
> === Meritocracy ===
> HTrace, up to this, has been run by Apache committers and PMC members.
> We want to
> build out a diverse developer and user community and run the HTrace
> project in
> the Apache way.  Users and new contributors will 

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

[Chris Douglas]

+1 (binding) -C

On Wed, Nov 5, 2014 at 5:48 AM, Jean-Baptiste Onofré  wrote:
> Hi all,
>
> We wrapped up the vote on the Apache Falcon dev list in which the community
> expressed its desire to graduate to a top-level project.
>
> The vote has passed with:
> 13 binding +1 votes
> 8 non-binding +1 votes
> no 0 or -1 vote
>
> This is the Incubator vote to decide if Apache Falcon should graduate from
> the Incubator. Please see the resolution later in this e-mail.
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache Falcon from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Falcon from the Incubator because ...
>
> Thanks,
> Regards
> JB
>
>  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 Big Data management platform covering data pipelines, data motion, data
> lifecycle management, data discovery & governance
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Falcon Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Falcon Project be and hereby is responsible for
> the creation and maintenance of software related to interactive analysis of
> large-scale datasets; and be it further RESOLVED, that the office of "Vice
> President, Apache Falcon" 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 Falcon Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache Falcon
> 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 Falcon Project:
>
> * Srikanth Sundarrajan 
> * Venkatesh Seetharam 
> * Shwetha GS 
> * Shaik Idris 
> * Sanjay Radia 
> * Sharad Agarwal 
> * Amareshwari SR 
> * Samarth Gupta 
> * Rishu Mehrothra 
> * Arpit Gupta 
> * Suhas Vasu 
> * Jean-Baptiste Onofré 
> * Ruslan Ostafiychuk 
> * Raghav Kumar Gautam 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be
> appointed to the office of Vice President, Apache Falcon, 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 Falcon Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Falcon podling; and be
> it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Falcon podling encumbered upon the Apache Incubator Project are hereafter
> discharged.
> 
>
> --
> 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
>

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

Re: [VOTE] Accept HTrace into the Apache Incubator

[Andrew Purtell]

+1 (binding)

On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik  wrote:

> Following the discussion earlier in the thread:
>http://s.apache.org/Dk7
>
> I would like to call a VOTE for accepting HTrace
> as a new incubator project.
>
> The proposal is available at:
>
> https://wiki.apache.org/incubator/HTraceProposal
>
> Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC
>
>  [ ] +1 accept Lens in the Incubator
>  [ ] ±0
>  [ ] -1 because...
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)