Who' going to pick this up?  :)
Regards,
Alan

On Apr 1, 2013, at 8:27 AM, Marvin <[EMAIL PROTECTED]> 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, 17 April 2013, 10:30:00:00 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, Apr 3rd).
>
> 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/April2013
>
> Note: This 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
>

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, 16 January 2013, 10:30:00:00 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, Jan 2nd).

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/January2013

Note: This 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

Any volunteers?  :)

I think that it would be good if the new mentors also put their opinions on what they would like to see happen in the near future.
Regards,
Alan

On Jan 8, 2013, at 10:09 AM, Marvin 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, 16 January 2013, 10:30:00:00 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, Jan 2nd).
>
> 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/January2013
>
> Note: This 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
>

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, 16 January 2013, 10:00:00 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, Jan 2nd).

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/January2013

Note: This 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

While the discussion has settled for Chukwa to continue, we should discuss
among the community on our plan for 2013 to move toward graduation.  Here
is a list of items that have been identified to be considered to include in
the report:

- Add a new policy page for how to contribute to Chukwa.  I drafted a copy
base on Hadoop contribution guide line at:
http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute

On the development side:
- Primary focus is to collect Hadoop and related technology log files and
metrics
- Add web UI for showing a list of running adaptors
- Add web UI for showing status of data streams written to destination
- Consolidate Agent and Collector features to use Chukwa Agent as the
primary process for data collection
- Replace SequenceFileWriter with WebHDFS support, discuss if changing
sequence file format to avro make sense

Any other points that would be interesting to include in the report?  I am
not sure what else that we should do before graduation.  In Chukwa status
page, we seem to have accomplished all check points.  Alan and I also
discussed about organizing meet up group, but I currently don't have
resource to organize.  Hence, it may be best to skip the meet up group
discussion for now.

regards,
Eric

On Wed, Jan 2, 2013 at 8:20 AM, Marvin <[EMAIL PROTECTED]> 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, 16 January 2013, 10:00:00 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, Jan 2nd).
>
> 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/January2013
>
> Note: This 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
>
>

Hi,

On Thu, Jan 3, 2013 at 6:56 AM, Eric Yang <[EMAIL PROTECTED]> wrote:
>
> - Add a new policy page for how to contribute to Chukwa.  I drafted a copy
> base on Hadoop contribution guide line at:
> http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
Great stuff! It would be good if this was more prominently visible on
http://incubator.apache.org/chukwa/.

Currently the getting involved guide on the website just points to the
issue tracker and the mailing lists, which is nice but not nearly as useful
as that wiki page. Additionally, the source repository page on the web site
is somewhat confusing, suggesting broken things like "svn checkout http://
svn.apache.org/repos/asf/incubator/chukwa site"...

Another area that could be improved on the web site are the getting started
instructions. Now it just points to the releases and documentation in
general (the doc link still points to 0.4.0). The information in the README
file could be there directly or at least behind a direct link. Also the
architecture/design page from the documentation, the quick start wiki page
and some past presentations might be good resources to link to directly.

Thinking a bit further, something like a simple example with real world
data and some interesting analysis questions would be a great way to get
people up and running. Can we do something like a "Chukwa in 5 minutes"
example?

Any other points that would be interesting to include in the report?  I am
> not sure what else that we should do before graduation.  In Chukwa status
> page, we seem to have accomplished all check points.
My general feeling is that Chukwa might be ready to start preparing for
graduation.

As discussed in the retirement threads, there are graduated podlings and
other Apache projects with similar levels of activity and diversity. The
underlying reason for the activity and diversity criteria for graduation is
the desire to ensure longevity of the project. Someone who starts using an
Apache product should have a reasonable expectation of help from the
community and people willing to review and apply their potential patches
also a few years down the line. This is often ensured by a large and
vibrant community (typically hundreds of messages per month, plenty of
active committers and contributors), but smaller projects with committed
community members and significant real-world users and deployments can be
just as resilient. It seems like Chukwa fits the latter category and has a
reasonable chance to also grow larger over time.

PS. Unless it already came up, the general Apache guidance for IRC channels
and other real-time communications is that they're fine as long as all
significant decisions and discussions are brought back to the mailing list
(or issue tracker) where also other members of the community (who may be in
different time zones, etc.) can participate.

BR,

Jukka Zitting

On Thu, Jan 10, 2013 at 10:14 AM, Jukka Zitting <[EMAIL PROTECTED]>wrote:
> Any other points that would be interesting to include in the report?  I am
> > not sure what else that we should do before graduation.  In Chukwa status
> > page, we seem to have accomplished all check points.
>
>
> My general feeling is that Chukwa might be ready to start preparing for
> graduation.
>
> As discussed in the retirement threads, there are graduated podlings and
> other Apache projects with similar levels of activity and diversity. The
> underlying reason for the activity and diversity criteria for graduation is
> the desire to ensure longevity of the project. Someone who starts using an
> Apache product should have a reasonable expectation of help from the
> community and people willing to review and apply their potential patches
> also a few years down the line. This is often ensured by a large and
> vibrant community (typically hundreds of messages per month, plenty of
> active committers and contributors), but smaller projects with committed
> community members and significant real-world users and deployments can be
> just as resilient. It seems like Chukwa fits the latter category and has a
> reasonable chance to also grow larger over time.
>
>
Hi everyone. I'm inclined to agree with that.

The main suggestion I have from what i've seen of the project so far is
that there are a lot of patch commits and at least some of those are from
people who've contributed multiple patches. So i wonder if some of those
people couldn't be made committers. Having a low bar to commitership,
especially in low activity projects, can help with keeping the project
active and alive.

   ..ant

Hi Ant,

Agree with your recommendation.  There were some people that have
contributed multiple patches in the past.  Some of them date back to 2010.
 I wonder if it would be a good idea to invite them to contribute, or we
should focus on people that have multiple patches in 2012?

regards,
Eric

On Fri, Jan 11, 2013 at 5:09 AM, ant elder <[EMAIL PROTECTED]> wrote:

> On Thu, Jan 10, 2013 at 10:14 AM, Jukka Zitting <[EMAIL PROTECTED]
> >wrote:
>
>
> > Any other points that would be interesting to include in the report?  I
> am
> > > not sure what else that we should do before graduation.  In Chukwa
> status
> > > page, we seem to have accomplished all check points.
> >
> >
> > My general feeling is that Chukwa might be ready to start preparing for
> > graduation.
> >
> > As discussed in the retirement threads, there are graduated podlings and
> > other Apache projects with similar levels of activity and diversity. The
> > underlying reason for the activity and diversity criteria for graduation
> is
> > the desire to ensure longevity of the project. Someone who starts using
> an
> > Apache product should have a reasonable expectation of help from the
> > community and people willing to review and apply their potential patches
> > also a few years down the line. This is often ensured by a large and
> > vibrant community (typically hundreds of messages per month, plenty of
> > active committers and contributors), but smaller projects with committed
> > community members and significant real-world users and deployments can be
> > just as resilient. It seems like Chukwa fits the latter category and has
> a
> > reasonable chance to also grow larger over time.
> >
> >
> Hi everyone. I'm inclined to agree with that.
>
> The main suggestion I have from what i've seen of the project so far is
> that there are a lot of patch commits and at least some of those are from
> people who've contributed multiple patches. So i wonder if some of those
> people couldn't be made committers. Having a low bar to commitership,
> especially in low activity projects, can help with keeping the project
> active and alive.
>
>    ..ant
>

Hi Jukka,

Thank you for review the web site.  I updated the site deployment
instruction to reflect our changes of using maven apt format for generating
site documents.  We will visit each of the recommend changes to our site
layout to improve usability.  I think we can make our setup installation
easier.  For deploying Hadoop + ZooKeeper + HBase + Pig + Chukwa is not a
trivial task.  We can do some of the simplification for Chukwa in the
coming release of Chukwa 0.6.0.  I hope this will improve our user
experience as well.

regards,
Eric

On Thu, Jan 10, 2013 at 2:14 AM, Jukka Zitting <[EMAIL PROTECTED]>wrote:

> Hi,
>
> On Thu, Jan 3, 2013 at 6:56 AM, Eric Yang <[EMAIL PROTECTED]> wrote:
> >
> > - Add a new policy page for how to contribute to Chukwa.  I drafted a
> copy
> > base on Hadoop contribution guide line at:
> > http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
>
>
> Great stuff! It would be good if this was more prominently visible on
> http://incubator.apache.org/chukwa/.
>
> Currently the getting involved guide on the website just points to the
> issue tracker and the mailing lists, which is nice but not nearly as useful
> as that wiki page. Additionally, the source repository page on the web site
> is somewhat confusing, suggesting broken things like "svn checkout http://
> svn.apache.org/repos/asf/incubator/chukwa site"...
>
> Another area that could be improved on the web site are the getting started
> instructions. Now it just points to the releases and documentation in
> general (the doc link still points to 0.4.0). The information in the README
> file could be there directly or at least behind a direct link. Also the
> architecture/design page from the documentation, the quick start wiki page
> and some past presentations might be good resources to link to directly.
>
> Thinking a bit further, something like a simple example with real world
> data and some interesting analysis questions would be a great way to get
> people up and running. Can we do something like a "Chukwa in 5 minutes"
> example?
>
> Any other points that would be interesting to include in the report?  I am
> > not sure what else that we should do before graduation.  In Chukwa status
> > page, we seem to have accomplished all check points.
>
>
> My general feeling is that Chukwa might be ready to start preparing for
> graduation.
>
> As discussed in the retirement threads, there are graduated podlings and
> other Apache projects with similar levels of activity and diversity. The
> underlying reason for the activity and diversity criteria for graduation is
> the desire to ensure longevity of the project. Someone who starts using an
> Apache product should have a reasonable expectation of help from the
> community and people willing to review and apply their potential patches
> also a few years down the line. This is often ensured by a large and
> vibrant community (typically hundreds of messages per month, plenty of
> active committers and contributors), but smaller projects with committed
> community members and significant real-world users and deployments can be
> just as resilient. It seems like Chukwa fits the latter category and has a
> reasonable chance to also grow larger over time.
>
> PS. Unless it already came up, the general Apache guidance for IRC channels
> and other real-time communications is that they're fine as long as all
> significant decisions and discussions are brought back to the mailing list
> (or issue tracker) where also other members of the community (who may be in
> different time zones, etc.) can participate.
>
> BR,
>
> Jukka Zitting
>

How about having a chukwa irc channel?

On Wednesday, January 2, 2013, Eric Yang wrote:

> While the discussion has settled for Chukwa to continue, we should discuss
> among the community on our plan for 2013 to move toward graduation.  Here
> is a list of items that have been identified to be considered to include in
> the report:
>
> - Add a new policy page for how to contribute to Chukwa.  I drafted a copy
> base on Hadoop contribution guide line at:
> http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
>
> On the development side:
> - Primary focus is to collect Hadoop and related technology log files and
> metrics
> - Add web UI for showing a list of running adaptors
> - Add web UI for showing status of data streams written to destination
> - Consolidate Agent and Collector features to use Chukwa Agent as the
> primary process for data collection
> - Replace SequenceFileWriter with WebHDFS support, discuss if changing
> sequence file format to avro make sense
>
> Any other points that would be interesting to include in the report?  I am
> not sure what else that we should do before graduation.  In Chukwa status
> page, we seem to have accomplished all check points.  Alan and I also
> discussed about organizing meet up group, but I currently don't have
> resource to organize.  Hence, it may be best to skip the meet up group
> discussion for now.
>
> regards,
> Eric
>
> On Wed, Jan 2, 2013 at 8:20 AM, Marvin <[EMAIL PROTECTED] <javascript:;>>
> 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, 16 January 2013, 10:00:00 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, Jan 2nd).
> >
> > 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/January2013
> >
> > Note: This 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
> >
> >
>

Good idea.  I will put the irc channel idea in the report.  irc channel has
been mentioned in the how to contribute page.  Developers can access it
with a web client as well at: http://webchat.freenode.net and join #chukwa
channel.

regards,
Eric

On Wed, Jan 2, 2013 at 9:24 PM, shreyas subramanya <[EMAIL PROTECTED]>wrote:

> How about having a chukwa irc channel?
>
> On Wednesday, January 2, 2013, Eric Yang wrote:
>
> > While the discussion has settled for Chukwa to continue, we should
> discuss
> > among the community on our plan for 2013 to move toward graduation.  Here
> > is a list of items that have been identified to be considered to include
> in
> > the report:
> >
> > - Add a new policy page for how to contribute to Chukwa.  I drafted a
> copy
> > base on Hadoop contribution guide line at:
> > http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
> >
> > On the development side:
> > - Primary focus is to collect Hadoop and related technology log files and
> > metrics
> > - Add web UI for showing a list of running adaptors
> > - Add web UI for showing status of data streams written to destination
> > - Consolidate Agent and Collector features to use Chukwa Agent as the
> > primary process for data collection
> > - Replace SequenceFileWriter with WebHDFS support, discuss if changing
> > sequence file format to avro make sense
> >
> > Any other points that would be interesting to include in the report?  I
> am
> > not sure what else that we should do before graduation.  In Chukwa status
> > page, we seem to have accomplished all check points.  Alan and I also
> > discussed about organizing meet up group, but I currently don't have
> > resource to organize.  Hence, it may be best to skip the meet up group
> > discussion for now.
> >
> > regards,
> > Eric
> >
> > On Wed, Jan 2, 2013 at 8:20 AM, Marvin <[EMAIL PROTECTED]<javascript:;>>
> > 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, 16 January 2013, 10:00:00 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, Jan 2nd).
> > >
> > > 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/January2013
> > >
> > > Note: This 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

Hi mentors and ppmc,

I have written the report for Jan 2013 for Chukwa.  It briefly describes
the retirement voting thread, departure of Chris and Bill.  I also added
irc channel and how to contribute information to Chukwa.  Outlined
development features that can be worked on in 2013 to improve Chukwa.  The
problem solving aspect of the project can help to increase community
awareness.

Your review of the report is appreciated.  Thanks

P.S. We probably need to run a irc bot to prevent people from hijack our
channel.  Anyone know how to run a irc bot to moderate the channel?

regards,
Eric

On Wed, Jan 2, 2013 at 10:33 PM, Eric Yang <[EMAIL PROTECTED]> wrote:

> Good idea.  I will put the irc channel idea in the report.  irc channel
> has been mentioned in the how to contribute page.  Developers can access it
> with a web client as well at: http://webchat.freenode.net and join
> #chukwa channel.
>
> regards,
> Eric
>
>
> On Wed, Jan 2, 2013 at 9:24 PM, shreyas subramanya <[EMAIL PROTECTED]>wrote:
>
>> How about having a chukwa irc channel?
>>
>> On Wednesday, January 2, 2013, Eric Yang wrote:
>>
>> > While the discussion has settled for Chukwa to continue, we should
>> discuss
>> > among the community on our plan for 2013 to move toward graduation.
>>  Here
>> > is a list of items that have been identified to be considered to
>> include in
>> > the report:
>> >
>> > - Add a new policy page for how to contribute to Chukwa.  I drafted a
>> copy
>> > base on Hadoop contribution guide line at:
>> > http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
>> >
>> > On the development side:
>> > - Primary focus is to collect Hadoop and related technology log files
>> and
>> > metrics
>> > - Add web UI for showing a list of running adaptors
>> > - Add web UI for showing status of data streams written to destination
>> > - Consolidate Agent and Collector features to use Chukwa Agent as the
>> > primary process for data collection
>> > - Replace SequenceFileWriter with WebHDFS support, discuss if changing
>> > sequence file format to avro make sense
>> >
>> > Any other points that would be interesting to include in the report?  I
>> am
>> > not sure what else that we should do before graduation.  In Chukwa
>> status
>> > page, we seem to have accomplished all check points.  Alan and I also
>> > discussed about organizing meet up group, but I currently don't have
>> > resource to organize.  Hence, it may be best to skip the meet up group
>> > discussion for now.
>> >
>> > regards,
>> > Eric
>> >
>> > On Wed, Jan 2, 2013 at 8:20 AM, Marvin <[EMAIL PROTECTED]<javascript:;>>
>> > 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, 16 January 2013, 10:00:00 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, Jan 2nd).
>> > >
>> > > 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

On Jan 2, 2013, at 8:56 PM, Eric Yang wrote:

> While the discussion has settled for Chukwa to continue, we should discuss
> among the community on our plan for 2013 to move toward graduation.  Here
> is a list of items that have been identified to be considered to include in
> the report:
>
> - Add a new policy page for how to contribute to Chukwa.  I drafted a copy
> base on Hadoop contribution guide line at:
> http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
>
> On the development side:
> - Primary focus is to collect Hadoop and related technology log files and
> metrics
> - Add web UI for showing a list of running adaptors
> - Add web UI for showing status of data streams written to destination
> - Consolidate Agent and Collector features to use Chukwa Agent as the
> primary process for data collection
> - Replace SequenceFileWriter with WebHDFS support, discuss if changing
> sequence file format to avro make sense
>
> Any other points that would be interesting to include in the report?  I am
> not sure what else that we should do before graduation.  In Chukwa status
> page, we seem to have accomplished all check points.  Alan and I also
> discussed about organizing meet up group, but I currently don't have
> resource to organize.  Hence, it may be best to skip the meet up group
> discussion for now.

Anyone going to ApacheCon?

Also, I would like to hear comments from the new mentor as to what they would like to see in the near term.  What was it that they thought could be done differently than what was done in the past?
Regards,
Alan

We have not vote in any new mentor after Chris and Bill left.  Did we?

regards,
Eric

On Wed, Jan 9, 2013 at 8:12 AM, Alan Cabrera <[EMAIL PROTECTED]> wrote:

>
> On Jan 2, 2013, at 8:56 PM, Eric Yang wrote:
>
> > While the discussion has settled for Chukwa to continue, we should
> discuss
> > among the community on our plan for 2013 to move toward graduation.  Here
> > is a list of items that have been identified to be considered to include
> in
> > the report:
> >
> > - Add a new policy page for how to contribute to Chukwa.  I drafted a
> copy
> > base on Hadoop contribution guide line at:
> > http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
> >
> > On the development side:
> > - Primary focus is to collect Hadoop and related technology log files and
> > metrics
> > - Add web UI for showing a list of running adaptors
> > - Add web UI for showing status of data streams written to destination
> > - Consolidate Agent and Collector features to use Chukwa Agent as the
> > primary process for data collection
> > - Replace SequenceFileWriter with WebHDFS support, discuss if changing
> > sequence file format to avro make sense
> >
> > Any other points that would be interesting to include in the report?  I
> am
> > not sure what else that we should do before graduation.  In Chukwa status
> > page, we seem to have accomplished all check points.  Alan and I also
> > discussed about organizing meet up group, but I currently don't have
> > resource to organize.  Hence, it may be best to skip the meet up group
> > discussion for now.
>
> Anyone going to ApacheCon?
>
> Also, I would like to hear comments from the new mentor as to what they
> would like to see in the near term.  What was it that they thought could be
> done differently than what was done in the past?
>
>
> Regards,
> Alan
>
>

Ant and Jukka volunteered.  Do mentors get voted in?  Usually podlings go around "begging".  ;)

My questions were actually directed to them since they're bringing in the "fresh blood".  :)
Regards,
Alan

On Jan 9, 2013, at 10:24 PM, Eric Yang wrote:

> We have not vote in any new mentor after Chris and Bill left.  Did we?
>
> regards,
> Eric
>
> On Wed, Jan 9, 2013 at 8:12 AM, Alan Cabrera <[EMAIL PROTECTED]> wrote:
>
>>
>> On Jan 2, 2013, at 8:56 PM, Eric Yang wrote:
>>
>>> While the discussion has settled for Chukwa to continue, we should
>> discuss
>>> among the community on our plan for 2013 to move toward graduation.  Here
>>> is a list of items that have been identified to be considered to include
>> in
>>> the report:
>>>
>>> - Add a new policy page for how to contribute to Chukwa.  I drafted a
>> copy
>>> base on Hadoop contribution guide line at:
>>> http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
>>>
>>> On the development side:
>>> - Primary focus is to collect Hadoop and related technology log files and
>>> metrics
>>> - Add web UI for showing a list of running adaptors
>>> - Add web UI for showing status of data streams written to destination
>>> - Consolidate Agent and Collector features to use Chukwa Agent as the
>>> primary process for data collection
>>> - Replace SequenceFileWriter with WebHDFS support, discuss if changing
>>> sequence file format to avro make sense
>>>
>>> Any other points that would be interesting to include in the report?  I
>> am
>>> not sure what else that we should do before graduation.  In Chukwa status
>>> page, we seem to have accomplished all check points.  Alan and I also
>>> discussed about organizing meet up group, but I currently don't have
>>> resource to organize.  Hence, it may be best to skip the meet up group
>>> discussion for now.
>>
>> Anyone going to ApacheCon?
>>
>> Also, I would like to hear comments from the new mentor as to what they
>> would like to see in the near term.  What was it that they thought could be
>> done differently than what was done in the past?
>>
>>
>> Regards,
>> Alan
>>
>>

Welcome Ant and Jukka.  Thank you for volunteer to mentor Chukwa community.
 Good to know that we didn't need to beg for mentors for Chukwa.  :)

regards,
Eric

On Wed, Jan 9, 2013 at 10:53 PM, Alan Cabrera <[EMAIL PROTECTED]> wrote:

> Ant and Jukka volunteered.  Do mentors get voted in?  Usually podlings go
> around "begging".  ;)
>
> My questions were actually directed to them since they're bringing in the
> "fresh blood".  :)
>
>
> Regards,
> Alan
>
> On Jan 9, 2013, at 10:24 PM, Eric Yang wrote:
>
> > We have not vote in any new mentor after Chris and Bill left.  Did we?
> >
> > regards,
> > Eric
> >
> > On Wed, Jan 9, 2013 at 8:12 AM, Alan Cabrera <[EMAIL PROTECTED]>
> wrote:
> >
> >>
> >> On Jan 2, 2013, at 8:56 PM, Eric Yang wrote:
> >>
> >>> While the discussion has settled for Chukwa to continue, we should
> >> discuss
> >>> among the community on our plan for 2013 to move toward graduation.
>  Here
> >>> is a list of items that have been identified to be considered to
> include
> >> in
> >>> the report:
> >>>
> >>> - Add a new policy page for how to contribute to Chukwa.  I drafted a
> >> copy
> >>> base on Hadoop contribution guide line at:
> >>> http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute
> >>>
> >>> On the development side:
> >>> - Primary focus is to collect Hadoop and related technology log files
> and
> >>> metrics
> >>> - Add web UI for showing a list of running adaptors
> >>> - Add web UI for showing status of data streams written to destination
> >>> - Consolidate Agent and Collector features to use Chukwa Agent as the
> >>> primary process for data collection
> >>> - Replace SequenceFileWriter with WebHDFS support, discuss if changing
> >>> sequence file format to avro make sense
> >>>
> >>> Any other points that would be interesting to include in the report?  I
> >> am
> >>> not sure what else that we should do before graduation.  In Chukwa
> status
> >>> page, we seem to have accomplished all check points.  Alan and I also
> >>> discussed about organizing meet up group, but I currently don't have
> >>> resource to organize.  Hence, it may be best to skip the meet up group
> >>> discussion for now.
> >>
> >> Anyone going to ApacheCon?
> >>
> >> Also, I would like to hear comments from the new mentor as to what they
> >> would like to see in the near term.  What was it that they thought
> could be
> >> done differently than what was done in the past?
> >>
> >>
> >> Regards,
> >> Alan
> >>
> >>
>
>