You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by jm...@apache.org on 2020/01/16 00:25:31 UTC
Podling Nuttx Report Reminder - February 2020
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, 19 February 2020, 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, February 05).
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.
Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.
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.
* How does the podling rate their own maturity.
This should be appended to the Incubator Wiki page at:
https://cwiki.apache.org/confluence/display/INCUBATOR/February2020
Note: This is manually populated. You may need to wait a little before
this page is created from a template.
Note: The format of the report has changed to use markdown.
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
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I personally deliberately avoided number of commits/PRs in the report
> as I saw Justin giving the same remark in his review to other reports
> that did that, and I believe he has a good argument.
I’s not just my point, the board frequently gives the same feedback on reports that just contain stats/number with no explanation.
Some examples:
"rb: Please drop the mailing list and Jira stats section of the
report unless those numbers support a specific point you wish to
make."
"idf: When including mailing list and jira stats it would be helpful
if you could include a bit of explanation as to what they mean
for your project.”
“ mt: The mailing list stats and the Jira stats should be not be
included in the report unless there is something noteworthy
about them”
Thanks,
Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
Hi,
I personally deliberately avoided number of commits/PRs in the report
as I saw Justin giving the same remark in his review to other reports
that did that, and I believe he has a good argument.
Probably a better stats would be number of PRs from new contributors,
that will show that the project is attracting new people and growing
its community.
Significant additions could also make it to the report, like new
architectures, new subsystems, etc.
On Fri, Feb 7, 2020 at 12:10 PM Flavio Junqueira <fp...@apache.org> wrote:
>
> +1 to more metrics about community, code changes, etc. I have signed off in any case.
>
> -Flavio
>
> > On 6 Feb 2020, at 03:27, Justin Mclean <ju...@classsoftware.com> wrote:
> >
> > HI,
> >
> >> Instead of giving absolute numbers, why not say there was an increase of x%
> >> in the number of PRs applied, etc
> >
> > Which is slightly better but without context or explanation to why this happened it’s mostly meaningless for people outside the project.
> >
> > Thanks,
> > Justin
> >
> >
> >
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Flavio Junqueira <fp...@apache.org>.
+1 to more metrics about community, code changes, etc. I have signed off in any case.
-Flavio
> On 6 Feb 2020, at 03:27, Justin Mclean <ju...@classsoftware.com> wrote:
>
> HI,
>
>> Instead of giving absolute numbers, why not say there was an increase of x%
>> in the number of PRs applied, etc
>
> Which is slightly better but without context or explanation to why this happened it’s mostly meaningless for people outside the project.
>
> Thanks,
> Justin
>
>
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> Instead of giving absolute numbers, why not say there was an increase of x%
> in the number of PRs applied, etc
Which is slightly better but without context or explanation to why this happened it’s mostly meaningless for people outside the project.
Thanks,
Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Nathan Hartman <ha...@gmail.com>.
On Wed, Feb 5, 2020 at 5:12 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> HI,
>
> > - Is it possible to mention the count of commits, contributors in the
> report.
> > - Also can we mentions who many discussions happened in the mailing list
> and how many people participated in the discussion.
>
> Only if it adds something to the report.
>
> > These are the non-technical details but it will help to keep a track on
> the health of the community.
>
> On their own they are meaningless, you need to explain why they are
> significant if you put them in a report. Remember people who read this
> report are not involved in your project.
Instead of giving absolute numbers, why not say there was an increase of x%
in the number of PRs applied, etc
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> - Is it possible to mention the count of commits, contributors in the report.
> - Also can we mentions who many discussions happened in the mailing list and how many people participated in the discussion.
Only if it adds something to the report.
> These are the non-technical details but it will help to keep a track on the health of the community.
On their own they are meaningless, you need to explain why they are significant if you put them in a report. Remember people who read this report are not involved in your project.
Thanks,
Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Mohammad Asif Siddiqui <as...@apache.org>.
Hi Justin,
I signed off the report, just a trivial suggestion on the report:
- Is it possible to mention the count of commits, contributors in the report.
- Also can we mentions who many discussions happened in the mailing list and how many people participated in the discussion.
These are the non-technical details but it will help to keep a track on the health of the community.
Regards
Asif
On 2020/02/05 01:01:22, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
> Don't forget the report is due today.
>
> Thanks,
> Justin
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
Hi Justin,
Thanks.
Sorry about that, I thought I double checked everything.
We'll be more vigilant next time.
On Wed, Feb 5, 2020, 02:49 Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
> > I just submitted it.
>
> Thanks for that, it looks fine and I’ve signed dit off.
>
> In future please follow the formatting guidelines at the top of the page
> and don’t change the spacing from the template, I’ve fixed it this time.
>
> In particular:
> • Keep all lines under 76 characters long.
> • All content under the ### headings should be indented by two
> spaces. Do not use tabs.
> • Please don't change the text in the headings or add new ones.
> • Include a space after a bullet point or full stop on a numbered
> list.
> • Use [X] (X and no spaces) to sign off reports.
>
> Thanks,
> Justin
>
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I just submitted it.
Thanks for that, it looks fine and I’ve signed dit off.
In future please follow the formatting guidelines at the top of the page and don’t change the spacing from the template, I’ve fixed it this time.
In particular:
• Keep all lines under 76 characters long.
• All content under the ### headings should be indented by two spaces. Do not use tabs.
• Please don't change the text in the headings or add new ones.
• Include a space after a bullet point or full stop on a numbered list.
• Use [X] (X and no spaces) to sign off reports.
Thanks,
Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
Hi Justin,
I just submitted it.
On Wed, Feb 5, 2020 at 1:01 AM Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> Don't forget the report is due today.
>
> Thanks,
> Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Don't forget the report is due today.
Thanks,
Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
> I stand corrected, those must have been the ones from testing. Maybe it
> needs to be redirected to commits@, I don't know.
We would probably want that as well.
testing is expected to see more traffic in the up coming days.
Re: Podling Nuttx Report Reminder - February 2020
Posted by Nathan Hartman <ha...@gmail.com>.
On Sat, Feb 1, 2020 at 10:57 PM Abdelatif Guettouche <
abdelatif.guettouche@gmail.com> wrote:
> They are? I think they got redirected to commit@.
> Only the testing repo still got its discussions forwarded to dev@.
> At least this is how I see them.
I stand corrected, those must have been the ones from testing. Maybe it
needs to be redirected to commits@, I don't know.
Nathan
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
They are? I think they got redirected to commit@.
Only the testing repo still got its discussions forwarded to dev@.
At least this is how I see them.
On Sun, Feb 2, 2020, 03:37 Nathan Hartman <ha...@gmail.com> wrote:
> On Sat, Feb 1, 2020 at 5:24 AM Abdelatif Guettouche <
> abdelatif.guettouche@gmail.com> wrote:
>
> > > I have noticed there seem to be less discussion happening on mailing,
> > and there may be some conversion happening off-list, which may be an
> issue
> > that needs to be looked into. But just about all podlings have that issue
> > at this stage.
> >
> > Correct. Some discussions are also happening on PRs comments.
>
>
> Those are all being forwarded to dev@.
>
> (At least, I am receiving a copy of each, and it appears to be coming from
> (or to?) dev@.)
>
> Thanks,
> Nathan
>
Re: Podling Nuttx Report Reminder - February 2020
Posted by Nathan Hartman <ha...@gmail.com>.
On Sat, Feb 1, 2020 at 5:24 AM Abdelatif Guettouche <
abdelatif.guettouche@gmail.com> wrote:
> > I have noticed there seem to be less discussion happening on mailing,
> and there may be some conversion happening off-list, which may be an issue
> that needs to be looked into. But just about all podlings have that issue
> at this stage.
>
> Correct. Some discussions are also happening on PRs comments.
Those are all being forwarded to dev@.
(At least, I am receiving a copy of each, and it appears to be coming from
(or to?) dev@.)
Thanks,
Nathan
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
Hi,
Yes, it is light. Not a lot of things have changed since the last report.
However, this is not the last version, it will get updated during the
next couple of days.
> I have noticed there seem to be less discussion happening on mailing, and there may be some conversion happening off-list, which may be an issue that needs to be looked into. But just about all podlings have that issue at this stage.
Correct. Some discussions are also happening on PRs comments.
On Sat, Feb 1, 2020 at 12:02 AM Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> > There already is a draft:
> > https://cwiki.apache.org/confluence/display/NUTTX/February+2020
> > We would appreciate your usual feedback.
>
> No major feedback but it seems a little light on for detail. Have a look at some of the previous incubator reports [1], you see some piddling reports are better than others. Your last report was well received by the board (on incubator private list sorry you can’t see that).
>
> I have noticed there seem to be less discussion happening on mailing, and there may be some conversion happening off-list, which may be an issue that needs to be looked into. But just about all podlings have that issue at this stage.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/board/minutes/Incubator.html
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> There already is a draft:
> https://cwiki.apache.org/confluence/display/NUTTX/February+2020
> We would appreciate your usual feedback.
No major feedback but it seems a little light on for detail. Have a look at some of the previous incubator reports [1], you see some piddling reports are better than others. Your last report was well received by the board (on incubator private list sorry you can’t see that).
I have noticed there seem to be less discussion happening on mailing, and there may be some conversion happening off-list, which may be an issue that needs to be looked into. But just about all podlings have that issue at this stage.
Thanks,
Justin
1. https://whimsy.apache.org/board/minutes/Incubator.html
Re: Podling Nuttx Report Reminder - February 2020
Posted by Abdelatif Guettouche <ab...@gmail.com>.
Hi Justin,
There already is a draft:
https://cwiki.apache.org/confluence/display/NUTTX/February+2020
We would appreciate your usual feedback.
On Fri, Jan 31, 2020 at 10:31 PM Justin Mclean <jm...@apache.org> wrote:
>
> Hi,
>
> it a good idea to start working on the report early so people can give feedback on it, a week before it is due is the suggestion. Who on the PPMC would like to try getting a draft together first?
>
> Thanks,
> Justin
Re: Podling Nuttx Report Reminder - February 2020
Posted by Justin Mclean <jm...@apache.org>.
Hi,
it a good idea to start working on the report early so people can give feedback on it, a week before it is due is the suggestion. Who on the PPMC would like to try getting a draft together first?
Thanks,
Justin