Re: [VOTE] Retire HTrace from Incubation

[Jake Farrell]

+1 to retire the HTrace podling

-Jake


On Thu, Mar 8, 2018 at 9:49 AM, lewis john mcgibbney <lewi...@apache.org>
wrote:

> Hi Folks,
> Below I've populated our report for the month of March 2018.
> https://wiki.apache.org/incubator/March2018 (also below)
> I've basically initiated the Retirement sentiment which has been prevalent
> within the HTrace community for some time. I would therefore like to
> formally open a VOTE to retire HTrace from the Incubator.
> The VOTE will be open for at least 72 hours.
> [ ] +1 retire the HTrace podling
> [ ] -1 NOT NOT retire the HTrace podling (please provide justification)
> Lewis
>
> ===
>
> HTrace
>
> HTrace is a tracing framework intended for use with distributed systems
> written in java.
>
> HTrace has been incubating since 2014-11-11.
>
> Three most important issues to address in the move towards graduation:
>
>   1. -
>   2. -
>   3. -
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> The HTrace podling has seen no code activity in months. Discussion of
> sending it to the Attic have been circulating for some time as well.
> After literally no activity again over the last few months, it looks like
> it is time to progress with sending HTrace to the Attic.
>
> How has the community developed since the last report?
>
> It has not.
>
> How has the project developed since the last report?
>
> It has not.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [X] Initial setup
>   [X] Working towards first release
>   [X] Community building
>   [ ] Nearing graduation
>   [X] Other: No actiity.
>
> Date of last release:
>
>   2016-03-04
>
> When were the last committers or PPMC members elected?
>
>   2016-10-03
>
> Signed-off-by:
>
>   [ ](htrace) Jake Farrell
>  Comments:
>   [ ](htrace) Todd Lipcon
>  Comments:
>   [X](htrace) Lewis John Mcgibbney
>  Comments: In our January 2018 report we mentioned that
>  "HTrace is very quiet. There is opportunity to continue
>  work if we engage with projects already using HTrace. If that does not
>  happen, we should retire the podling." We should therefore retire the
> podling.
>   [ ](htrace) Andrew Purtell
>  Comments:
>   [ ](htrace) Billie Rinaldi
>  Comments:
>   [ ](htrace) Michael Stack
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Re: Current status?

[Jake Farrell]

Hey John
I agree with Lewis's comments. Mike did bring up another thread about user
activity in other projects leveraging HTrace, but unfortunately the
projects dev community has no seen this same activity.

-Jake

On Tue, Dec 12, 2017 at 7:05 AM, lewis john mcgibbney 
wrote:

> Hi John,
> This surfaced again about a month or so ago and although opinions were
> voiced that HTrace should not retire, I have not seen any activity.
> I think the writing is on the wall is it would appear committers do not
> quite have the time to move things forward.
> Lewis
>
> On Sun, Dec 10, 2017 at 6:32 AM, <
> dev-digest-h...@htrace.incubator.apache.org> wrote:
>
> >
> > From: "John D. Ament" 
> > To: 
> > Cc:
> > Bcc:
> > Date: Sun, 10 Dec 2017 14:32:24 -
> > Subject: Current status?
> > Dear HTrace Podling,
> >
> > I was wondering what your current status is.  There is no report filed,
> > and very low on list activity.  Is it time to begin retirement
> discussions?
> >
> > John
> >
> >
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Re: podling report draft

[Jake Farrell]

+1, thanks for putting it together, signed off on the wiki

-Jake

On Wed, Jun 7, 2017 at 3:19 PM, Colin McCabe  wrote:

> Here's a draft of the podling report.  Let me know if I left out
> anything...
>
> -
> HTrace is a tracing framework intended for use with distributed systems
> written in java.
>
> HTrace has been incubating since 2014-11-11.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Continue to grow the Apache HTrace community
>   2. Continue to explore projects integrating Apache HTrace
>   3. Continue to develop and release stable Apache HTrace incubating
> artifacts
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   There are no issues requiring board attention at this time.
>
> How has the community developed since the last report?
>
>   Mailing lists have been quiet.
>
> How has the project developed since the last report?
>
>   We are on track to make an HTrace 4.3 release.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [x] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   2016-10-06
>
> When were the last committers or PPMC members elected?
>
>   2016-10-03
>

Re: report due today

[Jake Farrell]

Thanks Stack, signed off on

-Jake

On Wed, Dec 7, 2016 at 8:15 PM, Stack <st...@duboce.net> wrote:

> Thanks CPmcC. I'll push it.
> St.Ack
>
> On Wed, Dec 7, 2016 at 5:11 PM, Colin McCabe <cmcc...@apache.org> wrote:
>
> > Thanks, Stack!  Agree that it has been a little quiet in the last month.
> >
> > I'm working on a patch to port the native stuff to Mac OS X, but there
> > are a few annoying details that prevent me from posting just yet.
> >
> > I like the writeup below.
> >
> > best,
> > Colin
> >
> > On Wed, Dec 7, 2016, at 13:47, Stack wrote:
> > > Its been quiet of late. How about this:
> > >
> > > HTraceHTrace is a tracing framework intended for use with distributed
> > > systemswritten in java.HTrace has been incubating since
> > > 2014-11-11.Three most important issues to address in the move towards
> > > graduation:
> > >
> > >   1. Continue to grow the Apache HTrace community  2. Continue to
> > > explore projects integrating Apache HTrace  3. Continue to develop and
> > > release stable Apache HTrace incubating artifacts
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > aware
> > > of?
> > >
> > >   There are no issues requiring board attention at this time.
> > >
> > > How has the community developed since the last report? Mailing lists
> have
> > > been quiet. How has the project developed since the last report?
> > >
> > >   Release htrace-4.2.0
> > >
> > >
> > > Date of last release:  htrace-4.2.0 October 6th, 2016When were the
> > > last committers or PMC members elected?
> > >
> > >  +Mike Drob (mdrob) October 3rd, 2016Signed-off-by:  [ ](htrace) Jake
> > > Farrell  [ ](htrace) Todd Lipcon  [ ](htrace) Lewis John Mcgibbney  [
> > > ](htrace) Andrew Purtell  [ ](htrace) Billie Rinaldi  [ ](htrace)
> > > Michael StackShepherd/Mentor notes:
> > >
> > >
> > >
> > > On Wed, Dec 7, 2016 at 1:22 PM, Billie Rinaldi <bil...@apache.org>
> > wrote:
> > >
> > > > Anyone want to put together a podling report for HTrace at
> > > > https://wiki.apache.org/incubator/December2016?
> > > >
> > > > Billie
> > > >
> >
>

Re: Podling Report Reminder - September 2016

[Jake Farrell]

Looks good with a couple slight modifications made, updated and signed off
on

-Jake

On Wed, Sep 7, 2016 at 2:22 PM, lewis john mcgibbney <lewi...@apache.org>
wrote:

> Done, Please scope out and sign off or add.
> Thanks Jake and others.
> Lewis
>
> On Wed, Sep 7, 2016 at 10:28 AM, <
> dev-digest-h...@htrace.incubator.apache.org> wrote:
>
> >
> > dev Digest 7 Sep 2016 17:28:19 - Issue 180
> >
> > Topics (messages 831 through 831)
> >
> > Re: Podling Report Reminder - September 2016
> > 831 by: Jake Farrell
> >
> > Administrivia:
> >
> > -
> > To post to the list, e-mail: dev@htrace.incubator.apache.org
> > To unsubscribe, e-mail: dev-digest-unsubscribe@htrace.
> incubator.apache.org
> > For additional commands, e-mail: dev-digest-help@htrace.
> > incubator.apache.org
> >
> > ----------
> >
> >
> >
> > -- Forwarded message --
> > From: Jake Farrell <jfarr...@apache.org>
> > To: "dev@htrace.incubator.apache.org" <dev@htrace.incubator.apache.org>
> > Cc:
> > Date: Wed, 7 Sep 2016 13:28:14 -0400
> > Subject: Re: Podling Report Reminder - September 2016
> > Our podling report is due today, anyone that has not put it together yet
> > want to give it a shot?
> >
> > -Jake
> >
> >
> >
> > On Sun, Sep 4, 2016 at 5:46 PM, <johndam...@apache.org> wrote:
> >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 21 September 2016, 10:30 am
> PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, September 07).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no knowledge of
> > > the project or necessarily of its field
> > > *   A list of the three most important issues to address in the move
> > > towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > > aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > http://wiki.apache.org/incubator/September2016
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> >
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Re: Podling Report Reminder - September 2016

[Jake Farrell]

Our podling report is due today, anyone that has not put it together yet
want to give it a shot?

-Jake



On Sun, Sep 4, 2016 at 5:46 PM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 21 September 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, September 07).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/September2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Status page updated

[Jake Farrell]

I ran through all of our previous votes and releases and updated the status
page [1] so that it would reflect the current state of the project. Please
let me know if I missed anything

-Jake


[1]: http://incubator.apache.org/projects/htrace.html

Re: Board Report

[Jake Farrell]

+1, looks good, signed off

-Jake

On Thu, Apr 7, 2016 at 7:18 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:

> Thanks for the feedback. I put it up to the wiki.
>
> https://wiki.apache.org/incubator/April2016
>
> Masatake
>
> On 4/7/16 04:45, Colin McCabe wrote:
>
>> Thanks, Masatake.  It looks good!
>>
>> C.
>>
>> On Wed, Apr 6, 2016, at 12:03, Masatake Iwasaki wrote:
>>
>>> Thanks for pinging, John.
>>>
>>> I wrote a draft of board report.
>>> Let me have feedback from HTrace PMC members.
>>>
>>> Masatake
>>>
>>> -
>>> HTrace
>>>
>>> HTrace is a tracing framework intended for use with distributed systems
>>> written in java.
>>>
>>> HTrace has been incubating since 2014-11-11.
>>>
>>> Three most important issues to address in the move towards graduation:
>>>
>>> 1. Continue to grow the HTrace community
>>> 2. Continue to explore projects integratiing HTrace
>>> 3. Continue to develop and release stable HTrace incubating artifacts
>>>
>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> aware of?
>>>
>>> None
>>>
>>> How has the community developed since the last report?
>>>
>>> * YCSB community are working on integrating HTrace.
>>> * Google Summer of Code 2016 projects for Apache HTrace are being
>>> planned.  There are proposals such as
>>> * distributed tracing for s3 and other alternative Hadoop FS
>>> * Kudu span receiver
>>> * integrating HTrace into Hadoop YARN
>>>
>>> How has the project developed since the last report?
>>>
>>> +70 issues were fixed and released as part of 4.1.0-incubating.
>>> * Improved htraced a lot in Web-UI, robustness, metrics and logging
>>> * Added Docker support for development
>>> * Added Documentation for developers
>>>
>>> Date of last release:
>>>
>>> * htrace-4.1.0-incubating on March 5th, 2016
>>>
>>> When were the last committers or PMC members elected?
>>>
>>> * None this period. Last added committer: Abraham Elmahrek - 2.11.15
>>>
>>> Signed-off-by:
>>>
>>> [ ](htrace) Jake Farrell
>>> [ ](htrace) Todd Lipcon
>>> [ ](htrace) Lewis John Mcgibbney
>>> [ ](htrace) Andrew Purtell
>>> [ ](htrace) Billie Rinaldi
>>> [ ](htrace) Michael Stack
>>>
>>> Shepherd/Mentor notes:
>>>
>>> -
>>>
>>> On 4/6/16 08:42, John D. Ament wrote:
>>>
>>>> Dear HTrace Podling,
>>>>
>>>> Just a reminder about your board report, its due tomorrow.
>>>>
>>>> John
>>>>
>>>>
>

Re: [DISCUSS] Release for HTrace/Drive Towards Graduation

[Jake Farrell]

I think that we have the releases and overall release process down and have
been able to demonstrate fixing issues that arise during the rc process in
a clear manner, all of which has been handled on the mailing lists. only
item I see as the final step before graduations is continuing to grow the
community

-Jake

On Mon, Oct 26, 2015 at 10:34 AM, Billie Rinaldi  wrote:

> On Fri, Oct 23, 2015 at 5:55 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Hi Team,
> > Quick thread from me here.
> > What is required to get another release of HTrace?
> > I see two issues are unresolved for 4.1 release
> >
> >
> https://issues.apache.org/jira/browse/HTRACE/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
> > I also see the rest of the issues assigned against no fix version.
> >
> > One we sort this out then we could maybe think about touching the topic
> of
> > HTrace and graduation.
> >
>
> +1
>
> Thanks
> > Lewis
> >
> > --
> > *Lewis*
> >
>

Re: Build instructions for Htrace

[Jake Farrell]

mvnw looks to be gradle training wheels, not sure that its needed. perhaps
a dockerfile would help here and also give us a build env we could run
tests within jenkins/travis with, just a thought

-Jake


On Wed, Sep 2, 2015 at 12:20 PM, Adrian Cole 
wrote:

> What do you think about moving to maven wrapper (ex ./mvnw install as
> opposed to maven install). This sorts out the maven version issues by
> baking them into the wrapper.
>
> I can raise a patch if you think this would help.
>
> -A
>

Re: Build instructions for Htrace

[Jake Farrell]

The ASF jenkins instances are not running docker compose or dotci that i'm
aware of. Just a simple dockerfile and then we either need to script the
docker build/run calls or add them to a jenkins job

-Jake

On Wed, Sep 2, 2015 at 2:43 PM, Adrian Cole  wrote:

> > +1.  Creating a docker build environment for Jenkins has been on our
> to-do
> > list for a while.  It would be a great contribution for someone.  It
> seems
> > like it would also help anyone who wanted to build the project as well.
> Not used it yet, but dotci seems to be available for jenkins folks
> http://groupon.github.io/DotCi/
>
> I suspect a good first step is getting docker-compose working in
> general? That would be independent of what sort of CI slave would
> invoke it.
>

Re: Board Report?

[Jake Farrell]

- In addition to the number of subscribers should include the number of
posts to the mailing lists
- last committer/pmc members elected needs to be the names and date for
last added

Looks good otherwise

-Jake

On Thu, Jun 4, 2015 at 1:49 PM, Stack st...@duboce.net wrote:

 Whoops. Sorry about that John.

 How is the below all? Anything to add? I'd like to put this up in next hour
 or so.

 St.Ack

 ___

 HTrace

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

 HTrace has been incubating since 2014-11.

 Three most important issues to address in the move towards graduation:

 1. Continue to grow the HTrace community
 2. Continue to develop and release stable HTrace incubating artifacts
 3. Continue to explore the integration of the HTrace framework into other
 Apache products

 Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
 aware of?

 None

 How has the community developed since the last report?

 A few new folks have showed up on the dev and user lists of late.

 Lively dev discussion on lists about:

 + The 3.2.0 release.
 + HTrace and CI
 + HTrace and JDK7 minimum
 + A meeting and discussion of GUI going forward
 + How to accommodate github pull requests

 Apache HTrace (Incubating) was presented at HBaseCon May 7th in San
 Francisco by
 Colin McCabe and Abraham Elmahrek

 32 subscribers on dev@


 How has the project developed since the last report?

 About 36 JIRAs resolved since our last report.


 Date of last release:

   htrace-3.2.0 Jun 2, 2015 The release was release managed by Abraham
 Elmahrek

 When were the last committers or PMC members elected?

  None were added during this period.



 On Thu, Jun 4, 2015 at 9:31 AM, John D. Ament johndam...@apache.org
 wrote:

  Hi Htrace Podling!
 
  Just wondering where your board report was this month.
 
  John
 

Re: HTrace development environment CI

[Jake Farrell]

+1 to using docker for this. For Thrift I added a thin vagrant file that
acts as a docker host for anyone that does not want to setup docker in
their own. Also the ASF jenkins servers have docker available so we can
standardize our test environment and have full control over it this way

-Jake

On Wed, May 13, 2015 at 10:00 PM, Colin P. McCabe cmcc...@apache.org
wrote:

 Hi Vladimir,

 Welcome.  Great to see you're interested, and HTRACE-170 is a nice
 improvement!

 I agree that it is a little tough to kick the tires on the project
 right now, just because you have to build all the various downstream
 projects against HTrace.  And you have the usual build project X
 against project Y problems.  The situation is improving over time as
 we get more downstream projects (such as Hadoop) now supporting the
 Apache version of HTrace.  You should be able to build Hadoop 2.7 or
 HBase 1.0.0 against your version of htrace just by doing a mvn
 install of your htrace, and then modifying the Hadoop pom.xml
 slightly to build against your new version.

 We've been talking about setting up Docker images for a while.  Maybe
 I'm getting this wrong, but Vagrant seems kind of similar... except
 that it uses VM images instead of Linux containers.  Vagrant also
 seems to be focused on setting up installation scripts, similar to how
 people use Chef or Puppet, whereas I believe Docker mostly leaves that
 up to you.  Does that make any sense, or did I misunderstand?

 I'm curious if these tools could make it easier for people to test out
 a Hadoop+HTrace setup, or create a development environment.  That
 would be really cool.  We also need some kind of environment to run
 Jenkins jobs in, and all the people who know about such things tell me
 it ought to be a Docker image or VM, for better control over our
 environment.

 cheers,
 Colin

 On Wed, May 13, 2015 at 1:25 PM, Vladimir Sitnikov
 sitnikov.vladi...@gmail.com wrote:
  Hi,
 
  I somehow noticed HTrace, and I might start using it in the near future.
  My main areas of interest are performance  concurrency.
 
  While I lurk around the code I am a bit puzzled on how you create
  development environment.
 
  I saw this thread:
 
 http://mail-archives.apache.org/mod_mbox/htrace-dev/201503.mbox/%3CCA+qbEUOMgw1OZP=achvf5y8ha1wy75kz_isprsvmdfhudve...@mail.gmail.com%3E
 
  It looks like there is quite a few steps to complete in order to
  launch HTrace+HDFS (or whatever else is in trend).
 
 
  For Apache Calcite (a framework to translate SQL queries to different
  storage engines) I created a Vagrant virtual machine that provisions
  third party tools: https://github.com/vlsi/calcite-test-dataset
 
  Although it looks like a maven project, it allows you to provision a
  test machine with all the stuff installed.
  From user perspective, you run mvn install and it provisions a VM for
 you.
 
 
  Do you think it makes sense implementing similar test VM for HTrace
  integration testing?
  While I can help with Vagrant stuff, I am not sure where to start from
  HTrace point of view. I have very brief understanding of
  connectors/etc.
 
  For Calcite we host test VM in another repository to avoid main
  repository bloat.
 
  --
  Regards,
  Vladimir Sitnikov

Re: Moving to JDK7?

[Jake Farrell]

+1, would be nice to jump to 8 since 7 is now eol, but deprecating 6
support is a good start

-Jake

On Tue, May 12, 2015 at 3:11 PM, Colin P. McCabe cmcc...@apache.org wrote:

 Hi all,

 What do y'all think about moving our minJdk version to JDK7?

 It is set at JDK6 right now mostly because that was where Hadoop was
 stuck for a long time.  But now Hadoop is on JDK7, and so is HBase.
 Is there any reason to keep supporting JDK6 in our next release? There
 are some nice things in JDK7 like ThreadLocalRandom,
 try-with-resources, etc. and I would hate to ugly up the code for no
 reason.

 best,
 Colin

Re: [VOTE] HTrace 3.2.0 - Release Candidate 2

[Jake Farrell]

agree, there are no binary files, so the extra artifacts are not a release
blocker, would remove for the next release.

+1 for this rc from me

-Jake

On Thu, May 7, 2015 at 1:33 AM, Lewis John Mcgibbney 
lewis.mcgibb...@gmail.com wrote:

 I would say no, don't roll a new RC.
 If there is a way to ensure that generated files have ALv2.0 headers moving
 forward and committed to trunk then that would be my advice.
 Good job with RC.
 +1 from me

 On Wednesday, May 6, 2015, Abraham Elmahrek a...@cloudera.com wrote:

  Lewis,
 
  These are third party packages and a generated file. The JS dependencies
  are listed in LICENSE.txt. I don't see licenses for
  dependency-reduced-pom.xml in general... but I think it might be
 generated
  by the maven shading plugin. It looks like some of these generated files
  made it into the source tarball. Do you guys think it's worth spinning a
  new RC for this?
 
  -Abe
 
  On Wed, May 6, 2015 at 6:05 PM, Lewis John Mcgibbney 
  lewis.mcgibb...@gmail.com javascript:; wrote:
 
   Hi Folks,
   I ran DRAT over the codebase
  
 Notes Binaries Archives Standards Apache Generated Unknown  0 0 0 120
  83
   0
   28
  
   28 unknown licenses flagged up
  
   Upon further investigation these were
  
   Unapproved licenses:
  
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone-1.1.2.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.marionette-2.4.1.min.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.paginator-2.0.2.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-0.3.5.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-paginator-0.3.5.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.js
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.min.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3-3.5.5.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3.min.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/jquery-2.1.3.min.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/moment-2.9.0.min.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/npm.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.js
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.min.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.min.js
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/underscore-1.7.0.js
  
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-0.3.5.min.css
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-paginator-0.3.5.min.css
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.css
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.min.css
  
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.css
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.min.css
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.css
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.min.css
  
  
   /usr/local/drat/deploy/data/jobs/rat/1430960456828/input/SpanProtos.java
  
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml
  
  
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml_05062015_1800
  
   If we can clarify the above then I am +1 to the release.
  
   There's nothing more I can add over and above what has been stated by
   others.
   SIGS check
   Builds and Tests in native check
   Nice release candidate.
   Thanks
   Lewis
  
  
   On Thu, Apr 30, 2015 at 9:16 PM, Abraham Elmahrek a...@apache.org
  javascript:; wrote:
  
I've the second release candidate here:
   
  *http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/
http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/*
   
The jars have been staged here:
   
  *
  
 https://repository.apache.org/content/repositories/orgapachehtrace-1016

  https://repository.apache.org/content/repositories/orgapachehtrace-1016
   *
   
This release improves the Java client with better error checking and
setting parents in a span after the span is created. Also, some
 issues
  in
the local file span receiver are fixed and work has started on a new
   C/C++
native client.
   
Please vote +1/0/-1 by Friday, May 7th, 2015.
   
Thanks,
Abe
   
1.
   
   
  
 
 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.2.0%20AND%20project%20%3D%20HTRACE%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
   
   
Release Notes - HTrace - Version 3.2.0
   
** Sub-task
* [HTRACE-44] - Add htraced web 

Re: [DISCUSS] Github integration

[Jake Farrell]

Hey Colin
I don't think there was any intention of switching away from jira, just
enabling the github integrations for the project to accept patches from
github. For Thrift we require that all github pull requests have a jira
associated with them, for exactly as you point out, its hard to track
everything in split systems

-Jake

On Tue, Apr 21, 2015 at 1:53 PM, Colin P. McCabe cmcc...@apache.org wrote:

 Hi guys,

 I have an objection.  In the past, I've found it frustrating to search
 through github pull requests.  There is no interface (like there is on
 JIRA) to search using any kind of structured query language, and we
 don't have the tools to track things by release, contributor, etc.

 If we start having some of our patch discussions on github, JIRA will
 become a lot less useful.  We might run into a situation like on Spark
 where people open multiple pull requests for the same thing, not
 knowing about each other.  Or people have a discussion on JIRA, not
 aware that a parallel discussion is going on on github.

 I think we should take more time to think this through.  1 hour is not
 enough time to decide to switch away from JIRA :)

 best,
 Colin

 On Tue, Apr 21, 2015 at 10:21 AM, Jake Farrell jfarr...@apache.org
 wrote:
  Once Github picks up the mirror i'll enable the remaining integrations
  steps so we will start getting notices on our dev@ list and can close
 our
  pull requests through commits. Here are some docs I did for Thrift that
  would be good to adopt or change for how people contribute or commit to
  HTrace.
 
  http://thrift.apache.org/docs/HowToContribute
  http://thrift.apache.org/docs/committers/HowToCommit
 
  If you have any other questions let me know
 
  -Jake
 
 
 
 
 
  On Tue, Apr 21, 2015 at 12:57 PM, Nick Dimiduk ndimi...@apache.org
 wrote:
 
  That was fast, thanks Jake :)
 
  What else do we need to to to get the fancy PR integration i've seen in
  other projects? I see there's a specific task type for that on INFRA
 Jira.
  Is there a doc for Apacheer-but-not-githubbers on what the workflow
 looks
  like? Or is it just read the Github docs on PR's?
 
  Thanks,
  Nick
 
  On Tue, Apr 21, 2015 at 9:54 AM, Jake Farrell jfarr...@apache.org
 wrote:
 
  Hey Eliott
  Great idea, I have setup the git.a.o mirror for us and will enable the
  Github integrations as soon as Github picks up the repo from git.a.o
  (usually within 24 hours)
 
  -Jake
 
  On Tue, Apr 21, 2015 at 12:46 PM, Elliott Clark ecl...@apache.org
  wrote:
 
   That would be great.
  
   On Tue, Apr 21, 2015 at 9:34 AM, Nick Dimiduk ndimi...@apache.org
  wrote:
  
Do we have any kind of github integration setup? I can't even find
 a
   mirror
of HTrace on the apache account. I think we'll make it easier for
  folks
   to
contribute if they can send PR's.
   
I'd like to open an INFRA ticket to get us setup with this
  integration.
   Are
there any objections?
   
Thanks,
Nick
   
  
 
 
 

Re: [DISCUSS] Github integration

[Jake Farrell]

We have that available also, when a pr is created we can launch a jenkins
run for a given project and jenkins will comment back on that pr when its
done with the status. Also for Phoenix I enabled it in the filter for the
pre-commit last night

-Jake



On Tue, Apr 21, 2015 at 2:41 PM, Nick Dimiduk ndimi...@apache.org wrote:

 Jake --

 While I'm making requests of Infra, it would be super-cool if the
 Pre-Commit bot could detect a PR the same way it detects a patch. Then we
 could have our pre-commit scrips pull down the change, and run it like a
 patch through the project's usual process. Better still would be if Apache
 could provide a template for projects to follow. In another thread, I'm
 adding pre commit for Phoenix, which is going to end up using a fork of
 HBase's.. which is itself a fork of Hadoop's. One base script that does
 most of the heavy lifting that we all can inherit from and extend with
 project-specific additions would be really helpful, especially for when I
 get around to adding pre-commit for HTrace too ;)

 -n

 On Tue, Apr 21, 2015 at 11:36 AM, Nick Dimiduk ndimi...@apache.org
 wrote:

 Hi Colin, thanks for making this a DISCUSS thread ;)

 I'm not suggesting switching away from JIRA. What I want is to make it as
 easy as possible for non-Apache folks to find and contribute to HTrace,
 through the following:
  (0) mirror our repo to the github.com/apache account
  (1) allow folks to submit a PR against that account and have it arrive
 meaningfully to the community. On other projects, I've seen this result in
 a mail to dev@

 After that it's up for discussion. I think PR's and RB are a better place
 for deconstructing a large patch than comments on a JIRA. Github has the
 advantage over apache RB of being the most visible code review tool out
 there, so it benefits our project by participating. I also don't think it's
 a big deal to review patches on PR. Just like with RB, it's external to
 JIRA and that's okay, so long as it's clear that there's a non-JIRA
 resource associated with the ticket. For initial contributions that
 originate on a PR, it's obvious where to look for additional discussion.
 It's the exact same as looking to RB or Fabricator for patch comments. It's
 up to the contributor and the sponsor committed to be aware of these
 threads.

 I am absolutely NOT suggesting we replace JIRA with github issue tracker
 or pushing commits that lack and associated JIRA.

 Thanks Jake for the docs on how Thrift integrates with GH, that's what I
 was looking for.

 On Tue, Apr 21, 2015 at 11:23 AM, Jake Farrell jfarr...@apache.org
 wrote:

 Hey Colin
 I don't think there was any intention of switching away from jira, just
 enabling the github integrations for the project to accept patches from
 github. For Thrift we require that all github pull requests have a jira
 associated with them, for exactly as you point out, its hard to track
 everything in split systems

 -Jake

 On Tue, Apr 21, 2015 at 1:53 PM, Colin P. McCabe cmcc...@apache.org
 wrote:

 Hi guys,

 I have an objection.  In the past, I've found it frustrating to search
 through github pull requests.  There is no interface (like there is on
 JIRA) to search using any kind of structured query language, and we
 don't have the tools to track things by release, contributor, etc.

 If we start having some of our patch discussions on github, JIRA will
 become a lot less useful.  We might run into a situation like on Spark
 where people open multiple pull requests for the same thing, not
 knowing about each other.  Or people have a discussion on JIRA, not
 aware that a parallel discussion is going on on github.

 I think we should take more time to think this through.  1 hour is not
 enough time to decide to switch away from JIRA :)

 best,
 Colin

 On Tue, Apr 21, 2015 at 10:21 AM, Jake Farrell jfarr...@apache.org
 wrote:
  Once Github picks up the mirror i'll enable the remaining integrations
  steps so we will start getting notices on our dev@ list and can
 close our
  pull requests through commits. Here are some docs I did for Thrift
 that
  would be good to adopt or change for how people contribute or commit
 to
  HTrace.
 
  http://thrift.apache.org/docs/HowToContribute
  http://thrift.apache.org/docs/committers/HowToCommit
 
  If you have any other questions let me know
 
  -Jake
 
 
 
 
 
  On Tue, Apr 21, 2015 at 12:57 PM, Nick Dimiduk ndimi...@apache.org
 wrote:
 
  That was fast, thanks Jake :)
 
  What else do we need to to to get the fancy PR integration i've seen
 in
  other projects? I see there's a specific task type for that on INFRA
 Jira.
  Is there a doc for Apacheer-but-not-githubbers on what the workflow
 looks
  like? Or is it just read the Github docs on PR's?
 
  Thanks,
  Nick
 
  On Tue, Apr 21, 2015 at 9:54 AM, Jake Farrell jfarr...@apache.org
 wrote:
 
  Hey Eliott
  Great idea, I have setup the git.a.o mirror for us and will enable
 the
  Github integrations as soon as Github picks up the repo

Re: Time for a release?

[Jake Farrell]

+1, think this would also be a good time to add a doc around the release
process so anyone else on the team can pick up and act as the RM

-Jake

On Tue, Apr 14, 2015 at 4:28 PM, Nick Dimiduk ndimi...@gmail.com wrote:

 Looks like there's about 60 commits since 3.1.0-incubating went out, and
 it's been a couple months. Think is time for a release? Any RM volunteers?

 -n

Re: February 2015 Report

[Jake Farrell]

Looks good, thanks Lewis for putting it together

-Jake


On Thu, Jan 29, 2015 at 9:51 PM, Lewis John Mcgibbney 
lewis.mcgibb...@gmail.com wrote:

 Hi Folks,
 Please see our entry in the Incubator reporting page.
 I flushed out some of my observations and options. Please change at will if
 you do not agree.
 Thanks
 Lewis


 On Thu, Jan 29, 2015 at 5:01 PM, Marvin Humphrey mar...@apache.org
 wrote:

  Greetings, {podling} developers,
 
  The marvin automated report reminder script didn't fire for whatever
  reason this week, so I'm sending out a bulk reminder manually for the 19
  podlings who are expected to submit a February 2015 report.  Boilerplate
  repinder text below.
 
  Best,
 
  Marvin Humphrey
 
  ---
 
  Dear podling,
 
  This email was sent by an automated system on behalf of the Apache
  Incubator PMC. It is an initial reminder to give you plenty of time to
  prepare your quarterly board report.
 
  The board meeting is scheduled for Wed, 18 February 2015, 10:30 am PST.
  The report for your podling will form a part of the Incubator PMC
  report. The Incubator PMC requires your report to be submitted 2 weeks
  before the board meeting, to allow sufficient time for review and
  submission (Wed, February 4th).
 
  Please submit your report with sufficient time to allow the incubator
  PMC, and subsequently board members to review and digest. Again, the
  very latest you should submit your report is 2 weeks prior to the board
  meeting.
 
  Thanks,
 
  The Apache Incubator PMC
 
  Submitting your Report
 
  --
 
  Your report should contain the following:
 
  *   Your project name
  *   A brief description of your project, which assumes no knowledge of
  the project or necessarily of its field
  *   A list of the three most important issues to address in the move
  towards graduation.
  *   Any issues that the Incubator PMC or ASF Board might wish/need to be
  aware of
  *   How has the community developed since the last report
  *   How has the project developed since the last report.
 
  This should be appended to the Incubator Wiki page at:
 
  http://wiki.apache.org/incubator/February2015
 
  Note: This is manually populated. You may need to wait a little before
  this page is created from a template.
 
  Mentors
  ---
 
  Mentors should review reports for their project(s) and sign them off on
  the Incubator wiki page. Signing off reports shows that you are
  following the project - projects that are not signed may raise alarms
  for the Incubator PMC.
 
  Incubator PMC
 
 


 --
 *Lewis*

Re: [VOTE] htrace-3.1.0, the sixth release candidate

[Jake Farrell]

I do not see these issues as blocking, but we probably should add a
CHANGELOG and update it each release along with adding javadocs. We can
create tickets and address these issues for the next release

-Jake

On Fri, Jan 9, 2015 at 12:44 PM, Lewis John Mcgibbney 
lewis.mcgibb...@gmail.com wrote:

 If we can clarify if the issues are NOT blocking this RC progressing then I
 am more than happy to vreview folks.
 Please let me know, I was in the process of reviewing until this email came
 in... and quite right too! Good catches and excellent points.
 Thanks
 lewis

 On Thu, Jan 8, 2015 at 6:29 PM, Nick Dimiduk ndimi...@gmail.com wrote:

  I'm trying out this RC over in HBase code. We've broken API compatibility
  in at least two commits:
 
  HTRACE-1 changes the SpanReceiver interface. HBase was instantiating
  SpanReceivers itself and calling .configure(HTraceConfiguration) on each
  one. Looks like now the expectation is that SpanReceiver implementations
  provide a constructor that takes a single parameter of
 HTraceConfiguration.
 
  HTRACE-16 refactors the TraceTree interface a good bit. The handy
  getRoots() method has been replaced with the less obvious
  getSpansByParent().find(Span.ROOT_SPAN_ID) and .getSpansByParentIdMap()
 is
  also an invocation of getSpansByParent().find().
 
  Neither of these changes are a big deal, but none of this code has
  javadocs, so it's not obvious how the contract changed. I had to look at
  diffs and tests to decipher the new usage. This means that a simple
  search/replace is not sufficient for existing users to upgrade.
 
  For reference, my patch is over on HBASE-12810.
 
  I don't think this is enough to sink the RC, but my understanding of the
  earlier discussion was that this release would be a simple search/replace
  kind of upgrade. We need to document these idiom changes for folks.
 
  -n
 
  On Thu, Jan 8, 2015 at 5:06 PM, Stack st...@duboce.net wrote:
 
   I've posted our sixth htrace-3.1.0 RC here:
  
 http://people.apache.org/~stack/htrace-3.1.0-incubatingRC5/
  
   Maven artifacts are here:
  
  
  https://repository.apache.org/content/repositories/orgapachehtrace-1007
  
   The main changes from RC5 are packaging fixups and licensing
 attribution.
  
   The release is a src-only tarball for now. Later we can add binary
  bundles
   to our release after we have better sense of what we as a project would
   like to deliver.
  
   This release is mainly a change of packaging from org.htrace to
   org.apache.htrace to suit our new home here in Apache Incubator but it
  does
   also includes 34 resolved issues [1] including the beginnings of an
  htrace
   daemon whose intent is to make it so there is a low barrier collecting
   cluster traces as well as a new flume receiver.
  
   Beware that Apache Incubator, org.apache.htrace is not compatible with
  its
   former self, org.htrace: the package name has changed but so has the
 JSON
   serialization format.
  
   Shall we make this release candidate our first incubator release?
  
   Lets keep the vote period short (We'll have to run another vote over in
   incubator general after this one if I understand the process properly).
  
   Please vote +1/0/-1 by Monday, January 9th, 2015.
  
   Thanks,
   St.Ack
  
   1.
  
  
 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.1.0%20ORDER%20BY%20issuetype%20DESC
  
 



 --
 *Lewis*

Re: Website: mvn generated or apache cms or....

[Jake Farrell]

cms has its advantages and drawbacks. I've used middleman, jekyll, maven,
and the cms to generate different ASF sites and so far the one that I
prefer for use is middleman. Having the ability to use markdown and live
local dev vs having to push to buildbot (which if down then no site updates
can occur). Example of middleman in use that I did is for mesos or thrift
(thrift also has a cms version since we tested them all out). we can switch
to whichever variant people are most comfortable with, just need to make
sure that its documented so any committer can update the site easily

-Jake

On Thu, Dec 11, 2014 at 2:26 PM, Lewis John Mcgibbney 
lewis.mcgibb...@gmail.com wrote:

 CMS ROCKS

 On Thu, Dec 11, 2014 at 8:43 AM, Stack st...@duboce.net wrote:

  How should we do the website?  Jake set up the svnpubsub for us so we'd
  generate the static site and then publish it only, we have no 'website'
  currently.
 
  I could do a little fixup and then generate the site with 'mvn site'.
  That'd be easy (if ugly). Going forward, changing the website, you'd
 edit,
  stage, and the svn commit to deploy (a minor burden).
 
  We have a bit of markdown carried over the github deploy.  If our site
 used
  'apache cms' [1][2], we could just put up our little bit of *.md.  Devs
  could just login and edit the site; there would be no build, publish
 step.
 
  Jake, is it even possible to move to 'apache cms' post setup?
 
  Any other opinions out there on how to proceed?
  Thanks,
  St.Ack
 
  1. http://incubator.apache.org/guides/sites.html
  2. http://www.apache.org/dev/cms.html
 



 --
 *Lewis*