You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2009/01/15 23:46:24 UTC
Projects not in Incubator project menu.
The following two new projects exist on the ReportingSchedule, but
doesn't appear on the right-hand menu on Incubator site. This is just
a reminder that it should happen sooner rather than later...
- Kato
- Stonehenge
Cheers
Niclas
--
http://www.qi4j.org - New Energy for Java
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
Upayavira wrote:
>
> Clearly my chance never came, so let's make it happen now.
>
> The task itself is trivial - send an email to each email address listed
> in a file once a month, using a different file for each of a three month
> rotation cycle.
>
> Now, the questions are:
>
> 1. What date do we send the email out on?
Make it as easy as possible for everyone.
I suggest just send on the first day of the month.
Going by the list at http://wiki.apache.org/incubator/
Section 4, that would amount to between 9-14 days to get
their report in.
The tricky part is that someone needs to populate
each monthly wiki page with the current list, to be ready
for the podling reports.
I have been doing it each month, early in the month.
This time Niclas already has it done, ready for next month.
> 2. Do we, and if so when do we, send reminder emails?
I say no. These podlings need to be independent and interested.
> 3. What do the emails say?
> 4. What date do we state in the below email?
Keep it simple, don't provide a date.
They can look at that month's report template, e.g.
http://wiki.apache.org/incubator/August2009
The date and other instructions are stated load and clear.
Also stated at http://wiki.apache.org/incubator/
> Attempt to answer 3 is:
>
> -------------------------------------------------------------------------
> Dear <PODLING>-dev,
>
> Your latest report to the Apache Board is required by XX/XX/XXXX. Please
> ensure it is posted to http://incubator.apache.org/MonthYYYY, by the end
> of that day.
>
> Please ensure you provide a summary of your project at the beginning of
> the report and provide an answer to the question "What are the next
> steps your project needs to take to move towards graduation". You should
> also provide details of any new committers, PPMC members, product
> releases and so on, as well as anything else that might seem significant
> to you.
>
> Mentors - once the report has been posted to the Incubator Wiki, please
> 'sign' it to show that you have read the report.
>
> Incubator PMC
> ------------------------------------------------------------------------
Seems okay. It could be simpler, as everything is aleady stated
at the top of each wiki report page, e.g.
http://wiki.apache.org/incubator/August2009
One thing that i would like to have clearly stated, is that this
report is up to each project's group of committers, and should not
be left to the mentors.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by Upayavira <uv...@odoko.co.uk>.
Clearly my chance never came, so let's make it happen now.
The task itself is trivial - send an email to each email address listed
in a file once a month, using a different file for each of a three month
rotation cycle.
Now, the questions are:
1. What date do we send the email out on?
2. Do we, and if so when do we, send reminder emails?
3. What do the emails say?
4. What date do we state in the below email?
Attempt to answer 3 is:
-------------------------------------------------------------------------
Dear <PODLING>-dev,
Your latest report to the Apache Board is required by XX/XX/XXXX. Please
ensure it is posted to http://incubator.apache.org/MonthYYYY, by the end
of that day.
Please ensure you provide a summary of your project at the beginning of
the report and provide an answer to the question "What are the next
steps your project needs to take to move towards graduation". You should
also provide details of any new committers, PPMC members, product
releases and so on, as well as anything else that might seem significant
to you.
Mentors - once the report has been posted to the Incubator Wiki, please
'sign' it to show that you have read the report.
Incubator PMC
------------------------------------------------------------------------
On Wed, 2009-04-08 at 03:28 +0100, Upayavira wrote:
> On Sat, 2009-04-04 at 13:46 흝㐍ꯢ琪쥞쬊븧䊮謬闬낮譞:
> > > Upayavira wrote:
> > > >
> > > > Thinking more about this, there are three components I could really do
> > > > with:
> > > >
> > > > * dev list address
> > > > * project name
> > > > * board meeting dates
> > > >
> > > > I can scrape the code to identify the board meeting date from Marvin
> > > > (assuming I can find him). You've given me the dev list addresses, which
> > > > is great. It would be nice (but not necessary though) to have the
> > > > project names in the same report_due_*.txt file, e.g.
> > > > shindig-dev@incubator.apache.org|Shindig. How achievable is that?
> > > >
> > > > Then I'll script the rest.
> > >
> > > Perhaps you missed the earlier discussion with Craig.
> > > The files currently have the project name and dev address,
> > > http://incubator.apache.org/report_due_3.txt
> > > e.g.
> > > "Shindig Developers" <sh...@incubator.apache.org>
> > >
> > > This caters for later having a comma-separated list of
> > > addressees, if we are happy with publishing mentor addresses.
> > >
> > > That should be readily parseable to extract the names.
> > >
> > > Is that okay?
> >
> > Ping ... just keeping this thread alive, not pushing.
>
> Now on a trip to the US. Should get a chance to sort this over next few
> days.
>
> Upayavira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by Upayavira <uv...@odoko.co.uk>.
On Sat, 2009-04-04 at 13:46 +1100, David Crossley wrote:
> David Crossley wrote:
> > Upayavira wrote:
> > >
> > > Thinking more about this, there are three components I could really do
> > > with:
> > >
> > > * dev list address
> > > * project name
> > > * board meeting dates
> > >
> > > I can scrape the code to identify the board meeting date from Marvin
> > > (assuming I can find him). You've given me the dev list addresses, which
> > > is great. It would be nice (but not necessary though) to have the
> > > project names in the same report_due_*.txt file, e.g.
> > > shindig-dev@incubator.apache.org|Shindig. How achievable is that?
> > >
> > > Then I'll script the rest.
> >
> > Perhaps you missed the earlier discussion with Craig.
> > The files currently have the project name and dev address,
> > http://incubator.apache.org/report_due_3.txt
> > e.g.
> > "Shindig Developers" <sh...@incubator.apache.org>
> >
> > This caters for later having a comma-separated list of
> > addressees, if we are happy with publishing mentor addresses.
> >
> > That should be readily parseable to extract the names.
> >
> > Is that okay?
>
> Ping ... just keeping this thread alive, not pushing.
Now on a trip to the US. Should get a chance to sort this over next few
days.
Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Upayavira wrote:
> >
> > Thinking more about this, there are three components I could really do
> > with:
> >
> > * dev list address
> > * project name
> > * board meeting dates
> >
> > I can scrape the code to identify the board meeting date from Marvin
> > (assuming I can find him). You've given me the dev list addresses, which
> > is great. It would be nice (but not necessary though) to have the
> > project names in the same report_due_*.txt file, e.g.
> > shindig-dev@incubator.apache.org|Shindig. How achievable is that?
> >
> > Then I'll script the rest.
>
> Perhaps you missed the earlier discussion with Craig.
> The files currently have the project name and dev address,
> http://incubator.apache.org/report_due_3.txt
> e.g.
> "Shindig Developers" <sh...@incubator.apache.org>
>
> This caters for later having a comma-separated list of
> addressees, if we are happy with publishing mentor addresses.
>
> That should be readily parseable to extract the names.
>
> Is that okay?
Ping ... just keeping this thread alive, not pushing.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
Upayavira wrote:
>
> Thinking more about this, there are three components I could really do
> with:
>
> * dev list address
> * project name
> * board meeting dates
>
> I can scrape the code to identify the board meeting date from Marvin
> (assuming I can find him). You've given me the dev list addresses, which
> is great. It would be nice (but not necessary though) to have the
> project names in the same report_due_*.txt file, e.g.
> shindig-dev@incubator.apache.org|Shindig. How achievable is that?
>
> Then I'll script the rest.
Perhaps you missed the earlier discussion with Craig.
The files currently have the project name and dev address,
http://incubator.apache.org/report_due_3.txt
e.g.
"Shindig Developers" <sh...@incubator.apache.org>
This caters for later having a comma-separated list of
addressees, if we are happy with publishing mentor addresses.
That should be readily parseable to extract the names.
Is that okay?
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by Upayavira <uv...@odoko.co.uk>.
On Sat, 2009-02-21 at 18:01 +1100, David Crossley wrote:
> David Crossley wrote:
> > Craig L Russell wrote:
> > >
> > > What I was thinking is to have email lists generated for each podling,
> > > so email could be sent out to the people who care.
> > >
> > > For example, in http://incubator.apache.org/report_due_1.txt I'd like
> > > to see
> > >
> > > <Imperius dev list>imperius-dev@incubator.apache.org, <Imperius Mentor
> > > Craig Russell>clr@apache.org, <Imperius Mentor Bill
> > > Stoddard>stoddard@apache.org , <Imperius Mentor Filip
> > > Hanik>filip@apache.org, ...
>
> I get concerned about publishing lists of email addresses
> in an easy-to-use form.
>
> Should i be, or are committer details already out there
> so much that it does not matter?
> e.g. http://people.apache.org/~jim/committers.html
>
> > Some data is already available. See the generated
> > Python pickle file:
> > http://incubator.apache.org/clutch.html#data
> >
> > We have dev list addresses and mentor names, but not
> > mentor email addresses.
> >
> > I see one solution. The main "Incubation Table" at
> > http://incubator.apache.org/projects/
> > could have ASF committer IDs in brackets after
> > their names. Then clutch could gather that data.
> >
> > We also need an automated notice to general@ which
> > lists all projects that are due each month.
> >
> > I am wary about extending Clutch's operations too far.
> > It is already a clumsy oaf, thanks to my non-modular
> > programming.
> >
> > I will generate the report_due_*.txt to have each dev
> > list address.
>
> That part is done now.
>
> > ... Later we can add the mentor addresses.
> > So whoever develops the application to send the mail
> > can either parse that, or use the "Python pickle file"
> > directly.
Thinking more about this, there are three components I could really do
with:
* dev list address
* project name
* board meeting dates
I can scrape the code to identify the board meeting date from Marvin
(assuming I can find him). You've given me the dev list addresses, which
is great. It would be nice (but not necessary though) to have the
project names in the same report_due_*.txt file, e.g.
shindig-dev@incubator.apache.org|Shindig. How achievable is that?
Then I'll script the rest.
Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Craig L Russell wrote:
> >
> > What I was thinking is to have email lists generated for each podling,
> > so email could be sent out to the people who care.
> >
> > For example, in http://incubator.apache.org/report_due_1.txt I'd like
> > to see
> >
> > <Imperius dev list>imperius-dev@incubator.apache.org, <Imperius Mentor
> > Craig Russell>clr@apache.org, <Imperius Mentor Bill
> > Stoddard>stoddard@apache.org , <Imperius Mentor Filip
> > Hanik>filip@apache.org, ...
I get concerned about publishing lists of email addresses
in an easy-to-use form.
Should i be, or are committer details already out there
so much that it does not matter?
e.g. http://people.apache.org/~jim/committers.html
> Some data is already available. See the generated
> Python pickle file:
> http://incubator.apache.org/clutch.html#data
>
> We have dev list addresses and mentor names, but not
> mentor email addresses.
>
> I see one solution. The main "Incubation Table" at
> http://incubator.apache.org/projects/
> could have ASF committer IDs in brackets after
> their names. Then clutch could gather that data.
>
> We also need an automated notice to general@ which
> lists all projects that are due each month.
>
> I am wary about extending Clutch's operations too far.
> It is already a clumsy oaf, thanks to my non-modular
> programming.
>
> I will generate the report_due_*.txt to have each dev
> list address.
That part is done now.
> ... Later we can add the mentor addresses.
> So whoever develops the application to send the mail
> can either parse that, or use the "Python pickle file"
> directly.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
Craig L Russell wrote:
>
> Thanks for making Clutch and extending it to make it even better.
[ snip ]
Thanks for your feedback. Keep it coming.
> What I was thinking is to have email lists generated for each podling,
> so email could be sent out to the people who care.
>
> For example, in http://incubator.apache.org/report_due_1.txt I'd like
> to see
>
> <Imperius dev list>imperius-dev@incubator.apache.org, <Imperius Mentor
> Craig Russell>clr@apache.org, <Imperius Mentor Bill
> Stoddard>stoddard@apache.org , <Imperius Mentor Filip
> Hanik>filip@apache.org, ...
Some data is already available. See the generated
Python pickle file:
http://incubator.apache.org/clutch.html#data
We have dev list addresses and mentor names, but not
mentor email addresses.
I see one solution. The main "Incubation Table" at
http://incubator.apache.org/projects/
could have ASF committer IDs in brackets after
their names. Then clutch could gather that data.
We also need an automated notice to general@ which
lists all projects that are due each month.
I am wary about extending Clutch's operations too far.
It is already a clumsy oaf, thanks to my non-modular
programming.
I will generate the report_due_*.txt to have each dev
list address. Later we can add the mentor addresses.
So whoever develops the application to send the mail
can either parse that, or use the "Python pickle file"
directly.
> Interim to someone with their own itch to automate email, it would be
> easy (for someone) to copy/paste the list of email addresses into a
> Marvin-style email subject: Podling reports are due by March 10...
>
> If the information to generate the email addresses is not available in
> the form needed, let's see how to make it available, for example
> update the STATUS file to include the reminder email addresses.
However, as Clutch shows, many projects just don't attend
to their status files. So that is not reliable. Clutch
tries to find other ways to supplement that data.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi David,
Thanks for making Clutch and extending it to make it even better.
On Feb 17, 2009, at 10:41 PM, David Crossley wrote:
> Okay, Clutch now re-generates those files every time
> it runs.
>
> report_due_1.txt is for group-1 (Jan,Apr,Jul,Oct)
> report_due_2.txt is for group-2 (Feb,May,Aug,Nov)
> report_due_3.txt is for group-3 (Mar,Jun,Sep,Dec)
>
> e.g. cat report_due_2.txt
> BlueSky Cassandra Droids ESME Kato Lokahi PDFBox PhotArk Pivot Sling
> Stonehenge VCL WSRP4J XAP
>
> Please say if you want a different format or
> additional text in the files.
What I was thinking is to have email lists generated for each podling,
so email could be sent out to the people who care.
For example, in http://incubator.apache.org/report_due_1.txt I'd like
to see
<Imperius dev list>imperius-dev@incubator.apache.org, <Imperius Mentor
Craig Russell>clr@apache.org, <Imperius Mentor Bill Stoddard>stoddard@apache.org
, <Imperius Mentor Filip Hanik>filip@apache.org, ...
Interim to someone with their own itch to automate email, it would be
easy (for someone) to copy/paste the list of email addresses into a
Marvin-style email subject: Podling reports are due by March 10...
If the information to generate the email addresses is not available in
the form needed, let's see how to make it available, for example
update the STATUS file to include the reminder email addresses.
Craig
>
>
> Would you or someone else please handle the cron job
> to send the email.
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
sebb wrote:
> David Crossley wrote:
> >
> > e.g. cat report_due_2.txt
> > BlueSky Cassandra Droids ESME Kato Lokahi PDFBox PhotArk Pivot Sling Stonehenge VCL WSRP4J XAP
>
> [from the peanut gallery:]
>
> AFAICS that format will be problematical should a podling have one or
> more spaces in its name. Also, it would be easier to interpret
> differences if there is one line per podling.
Yes, i wondered about all that. Will do it.
Thanks.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by sebb <se...@gmail.com>.
On 18/02/2009, David Crossley <cr...@apache.org> wrote:
> Upayavira wrote:
> > David Crossley wrote:
> > > Upayavira wrote:
> > > > David Crossley wrote:
> > > > >
> > > > > http://incubator.apache.org/clutch.html
> > > >
> > > > Could clutch in some way be used to mimic Marvin for the Incubator?
> > > >
> > > > I for one would really appreciate an email each month saying what
> > > > projects need to report.
> > > >
> > > > Could simply be group1.html, group2.html and group3.html mailed to
> > > > general@ rotating every month.
> > >
> > > The goal of Clutch is to gather data. It is run
> > > on an ad hoc basis.
> >
> > Yes. All I had in mind is that clutch generate three files, month1.txt,
> > month2.txt and month3.txt. Then, a separate process could mail
> > month($month % 3 +1).txt to general@ every month. Simple, crude, but it
> > would work.
>
>
> That is nice.
>
> Okay, Clutch now re-generates those files every time
> it runs.
>
> report_due_1.txt is for group-1 (Jan,Apr,Jul,Oct)
> report_due_2.txt is for group-2 (Feb,May,Aug,Nov)
> report_due_3.txt is for group-3 (Mar,Jun,Sep,Dec)
>
> e.g. cat report_due_2.txt
> BlueSky Cassandra Droids ESME Kato Lokahi PDFBox PhotArk Pivot Sling Stonehenge VCL WSRP4J XAP
[from the peanut gallery:]
AFAICS that format will be problematical should a podling have one or
more spaces in its name. Also, it would be easier to interpret
differences if there is one line per podling.
> Please say if you want a different format or
> additional text in the files.
>
> Would you or someone else please handle the cron job
> to send the email.
>
> So projects will then have many ways to know when their
> reports are due:
> * http://wiki.apache.org/incubator/ReportingSchedule
>
> * http://wiki.apache.org/incubator/
>
> * http://incubator.apache.org/clutch.html
> * the commit diffs for the report_due_*.txt
> * http://incubator.apache.org/report_due_2.txt etc.
> * the automated email each month.
>
> The remaining problem will be that someone needs to
> create the Wiki page at the beginning of each month,
> e.g. http://wiki.apache.org/incubator/February2009
> and add the banner, due date, and list of projects.
>
> For the last few months that has been me. Please don't
> rely on that. Anyone can do it. Ditto with running Clutch.
>
> If someone wants to create a more sophisticated
> Marvin-like reminder system, or extend Marvin, then
> the main data file generated by Clutch has the
> name of the podling's dev list, which reporting group,
> and whether they are on monthly reporting.
> http://incubator.apache.org/clutch.html#data
> Do 'python clutch2data.py' in the top-level of
> incubator svn.
>
>
> -David
>
>
> > I guess, by a similar approach, it would be possible to template out the
> > wiki page such that a simple cut and paste would get the report page up
> > in no time.
> >
> > Just thoughts about how we could get a quick hit out of the valuable
> > data Clutch collects.
> >
> > Upayavira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
Upayavira wrote:
> David Crossley wrote:
> > Upayavira wrote:
> > > David Crossley wrote:
> > > >
> > > > http://incubator.apache.org/clutch.html
> > >
> > > Could clutch in some way be used to mimic Marvin for the Incubator?
> > >
> > > I for one would really appreciate an email each month saying what
> > > projects need to report.
> > >
> > > Could simply be group1.html, group2.html and group3.html mailed to
> > > general@ rotating every month.
> >
> > The goal of Clutch is to gather data. It is run
> > on an ad hoc basis.
>
> Yes. All I had in mind is that clutch generate three files, month1.txt,
> month2.txt and month3.txt. Then, a separate process could mail
> month($month % 3 +1).txt to general@ every month. Simple, crude, but it
> would work.
That is nice.
Okay, Clutch now re-generates those files every time
it runs.
report_due_1.txt is for group-1 (Jan,Apr,Jul,Oct)
report_due_2.txt is for group-2 (Feb,May,Aug,Nov)
report_due_3.txt is for group-3 (Mar,Jun,Sep,Dec)
e.g. cat report_due_2.txt
BlueSky Cassandra Droids ESME Kato Lokahi PDFBox PhotArk Pivot Sling Stonehenge VCL WSRP4J XAP
Please say if you want a different format or
additional text in the files.
Would you or someone else please handle the cron job
to send the email.
So projects will then have many ways to know when their
reports are due:
* http://wiki.apache.org/incubator/ReportingSchedule
* http://wiki.apache.org/incubator/
* http://incubator.apache.org/clutch.html
* the commit diffs for the report_due_*.txt
* http://incubator.apache.org/report_due_2.txt etc.
* the automated email each month.
The remaining problem will be that someone needs to
create the Wiki page at the beginning of each month,
e.g. http://wiki.apache.org/incubator/February2009
and add the banner, due date, and list of projects.
For the last few months that has been me. Please don't
rely on that. Anyone can do it. Ditto with running Clutch.
If someone wants to create a more sophisticated
Marvin-like reminder system, or extend Marvin, then
the main data file generated by Clutch has the
name of the podling's dev list, which reporting group,
and whether they are on monthly reporting.
http://incubator.apache.org/clutch.html#data
Do 'python clutch2data.py' in the top-level of
incubator svn.
-David
> I guess, by a similar approach, it would be possible to template out the
> wiki page such that a simple cut and paste would get the report page up
> in no time.
>
> Just thoughts about how we could get a quick hit out of the valuable
> data Clutch collects.
>
> Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: remember when each project report is due
Posted by Upayavira <uv...@odoko.co.uk>.
On Tue, 2009-01-20 at 21:12 +1100, David Crossley wrote:
> Upayavira wrote:
> > David Crossley wrote:
> > >
> > > http://incubator.apache.org/clutch.html
> >
> > Could clutch in some way be used to mimic Marvin for the Incubator?
> >
> > I for one would really appreciate an email each month saying what
> > projects need to report.
> >
> > Could simply be group1.html, group2.html and group3.html mailed to
> > general@ rotating every month.
>
> The goal of Clutch is to gather data. It is run
> on an ad hoc basis.
Yes. All I had in mind is that clutch generate three files, month1.txt,
month2.txt and month3.txt. Then, a separate process could mail
month($month % 3 +1).txt to general@ every month. Simple, crude, but it
would work.
I guess, by a similar approach, it would be possible to template out the
wiki page such that a simple cut and paste would get the report page up
in no time.
Just thoughts about how we could get a quick hit out of the valuable
data Clutch collects.
Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
remember when each project report is due
Posted by David Crossley <cr...@apache.org>.
Upayavira wrote:
> David Crossley wrote:
> >
> > http://incubator.apache.org/clutch.html
>
> Could clutch in some way be used to mimic Marvin for the Incubator?
>
> I for one would really appreciate an email each month saying what
> projects need to report.
>
> Could simply be group1.html, group2.html and group3.html mailed to
> general@ rotating every month.
The goal of Clutch is to gather data. It is run
on an ad hoc basis.
Other separate jobs can use that data. Perhaps a simple
cron job to read the data and send the email.
http://incubator.apache.org/clutch.html#data
To view the data, do:
]$ cd /asf/svn/incubator (i.e. your local SVN working copy)
]$ python clutch2data.py
Also one of the Incubator PMC members will manually initialise
each month's reporting page early in the month.
e.g. http://wiki.apache.org/incubator/January2009
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Projects not in Incubator project menu.
Posted by Upayavira <uv...@odoko.co.uk>.
On Fri, 2009-01-16 at 14:53 +1100, David Crossley wrote:
> Niclas Hedhman wrote:
> > The following two new projects exist on the ReportingSchedule, but
> > doesn't appear on the right-hand menu on Incubator site. This is just
> > a reminder that it should happen sooner rather than later...
> >
> > - Kato
> > - Stonehenge
>
> Yep. Just a reminder that "Clutch" alerts us all to such,
> and tries to provide some starter links to documentation
> about how to proceed with each step.
>
> http://incubator.apache.org/clutch.html
> http://incubator.apache.org/clutch.html#steps
Could clutch in some way be used to mimic Marvin for the Incubator?
I for one would really appreciate an email each month saying what
projects need to report.
Could simply be group1.html, group2.html and group3.html mailed to
general@ rotating every month.
Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Projects not in Incubator project menu.
Posted by Robert Burrell Donkin <ro...@gmail.com>.
a basic status file and link committed. need to start filling in the
content but that can wait till it's sync'd
- robert
On Thu, Jan 22, 2009 at 4:36 AM, Sonal Goyal <so...@gmail.com> wrote:
> Just in case this got missed..
> Thanks and Regards,
> Sonal
>
>
> ---------- Forwarded message ----------
> From: David Crossley <cr...@apache.org>
> Date: Fri, Jan 16, 2009 at 9:23 AM
> Subject: Re: Projects not in Incubator project menu.
> To: general@incubator.apache.org
>
>
> Niclas Hedhman wrote:
>> The following two new projects exist on the ReportingSchedule, but
>> doesn't appear on the right-hand menu on Incubator site. This is just
>> a reminder that it should happen sooner rather than later...
>>
>> - Kato
>> - Stonehenge
>
> Yep. Just a reminder that "Clutch" alerts us all to such,
> and tries to provide some starter links to documentation
> about how to proceed with each step.
>
> http://incubator.apache.org/clutch.html
> http://incubator.apache.org/clutch.html#steps
>
> -David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Fwd: Projects not in Incubator project menu.
Posted by Sonal Goyal <so...@gmail.com>.
Just in case this got missed..
Thanks and Regards,
Sonal
---------- Forwarded message ----------
From: David Crossley <cr...@apache.org>
Date: Fri, Jan 16, 2009 at 9:23 AM
Subject: Re: Projects not in Incubator project menu.
To: general@incubator.apache.org
Niclas Hedhman wrote:
> The following two new projects exist on the ReportingSchedule, but
> doesn't appear on the right-hand menu on Incubator site. This is just
> a reminder that it should happen sooner rather than later...
>
> - Kato
> - Stonehenge
Yep. Just a reminder that "Clutch" alerts us all to such,
and tries to provide some starter links to documentation
about how to proceed with each step.
http://incubator.apache.org/clutch.html
http://incubator.apache.org/clutch.html#steps
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Projects not in Incubator project menu.
Posted by David Crossley <cr...@apache.org>.
Niclas Hedhman wrote:
> The following two new projects exist on the ReportingSchedule, but
> doesn't appear on the right-hand menu on Incubator site. This is just
> a reminder that it should happen sooner rather than later...
>
> - Kato
> - Stonehenge
Yep. Just a reminder that "Clutch" alerts us all to such,
and tries to provide some starter links to documentation
about how to proceed with each step.
http://incubator.apache.org/clutch.html
http://incubator.apache.org/clutch.html#steps
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org