You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@quickstep.apache.org by Julian Hyde <jh...@apache.org> on 2016/06/02 19:55:51 UTC
Re: Podling Report Reminder - May 2016
I saw that the report is filed (thanks for that!) but I'm not ready to sign off.
The report makes the incorrect statement "Last committer joined on May
30, 2016." No committers have been elected since incubation, as far as
I know. Please correct that statement.
Also, please fix the formatting. There is a partial line "aware of?",
and "Quickstep has been incubating since 2016-03-29." should be a
separate paragraph.
I suggest that you email the mentors directly when the report is ready
for sign-off, this month and subsequent months. We're busy people, and
we sometimes need prodding.
Julian
On Wed, May 25, 2016 at 8:09 PM, Julian Hyde <jh...@apache.org> wrote:
> Hi Quickstep committers/PPMC members,
>
> I think this is the first time you’ve filed a report. It’s not absolutely required, but it’s useful if at this point someone volunteers to write the report, and sends a draft to the dev list well in advance of the deadline for comments.
>
> Does that sound like a good idea? If so, any volunteers?
>
> Your affectionate mentor,
>
> Julian
>
>> On May 25, 2016, at 7:33 PM, johndament@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, 15 June 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, June 1st).
>>
>> 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/May2016
>>
>> 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
>
Re: Podling Report Reminder - May 2016
Posted by Julian Hyde <jh...@apache.org>.
s/making a release before/making a release, before/
On Thu, Jun 2, 2016 at 1:50 PM, Julian Hyde <jh...@apache.org> wrote:
> I'd like to see some concrete progress in (a) building a community,
> (b) making a release before the next report. Right now, I can tell
> that you're all about code. Quite frankly, we don't give a hoot about
> code. Build a community, and the code will happen. Quickstep needs to
> start building a community.
>
> Julian
>
>
> On Thu, Jun 2, 2016 at 1:41 PM, Jignesh Patel <ji...@pivotal.io> wrote:
>> Thanks Julian! Adding this to the list to work on.
>>
>> Neat tips!
>>
>> Cheers,
>> Jignesh
>>
>>> On Jun 2, 2016, at 3:40 PM, Julian Hyde <jh...@apache.org> wrote:
>>>
>>> You, as a PMC, should decide what are the criteria & process for
>>> making someone a committer. There are some guidelines[1], but they are
>>> only guidelines.
>>>
>>> In my opinion, you should err on setting the bar too low rather than
>>> too high. Making someone a committer early will tend to draw them into
>>> the community. And, remember that code is not the only kind of
>>> contribution.
>>>
>>> The Quickstep community should also have a broader discussion: how do
>>> you intend to meet your goal of "Acquire early adopters". Electing
>>> committers is a consequence of a successful strategy for growing
>>> community, and helps further that growth.
>>>
>>> Julian
>>>
>>> [1] http://community.apache.org/newcommitter.html
>>>
>>> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel <ji...@pivotal.io> wrote:
>>>> Thanks Julian!
>>>>
>>>> What are the guidelines for election? We would love to welcome new
>>>> committers who are starting to make serious contributions.
>>>>
>>>> Cheers,
>>>> Jignesh
>>>>
>>>> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote:
>>>>
>>>> The key word here is "elected", as opposed to "showed up in his
>>>> congressional office for the first time". :)
>>>>
>>>>
>>
Re: Podling Report Reminder - May 2016
Posted by Julian Hyde <jh...@apache.org>.
I'd like to see some concrete progress in (a) building a community,
(b) making a release before the next report. Right now, I can tell
that you're all about code. Quite frankly, we don't give a hoot about
code. Build a community, and the code will happen. Quickstep needs to
start building a community.
Julian
On Thu, Jun 2, 2016 at 1:41 PM, Jignesh Patel <ji...@pivotal.io> wrote:
> Thanks Julian! Adding this to the list to work on.
>
> Neat tips!
>
> Cheers,
> Jignesh
>
>> On Jun 2, 2016, at 3:40 PM, Julian Hyde <jh...@apache.org> wrote:
>>
>> You, as a PMC, should decide what are the criteria & process for
>> making someone a committer. There are some guidelines[1], but they are
>> only guidelines.
>>
>> In my opinion, you should err on setting the bar too low rather than
>> too high. Making someone a committer early will tend to draw them into
>> the community. And, remember that code is not the only kind of
>> contribution.
>>
>> The Quickstep community should also have a broader discussion: how do
>> you intend to meet your goal of "Acquire early adopters". Electing
>> committers is a consequence of a successful strategy for growing
>> community, and helps further that growth.
>>
>> Julian
>>
>> [1] http://community.apache.org/newcommitter.html
>>
>> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel <ji...@pivotal.io> wrote:
>>> Thanks Julian!
>>>
>>> What are the guidelines for election? We would love to welcome new
>>> committers who are starting to make serious contributions.
>>>
>>> Cheers,
>>> Jignesh
>>>
>>> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote:
>>>
>>> The key word here is "elected", as opposed to "showed up in his
>>> congressional office for the first time". :)
>>>
>>>
>
Re: Podling Report Reminder - May 2016
Posted by Jignesh Patel <ji...@pivotal.io>.
Thanks Julian! Adding this to the list to work on.
Neat tips!
Cheers,
Jignesh
> On Jun 2, 2016, at 3:40 PM, Julian Hyde <jh...@apache.org> wrote:
>
> You, as a PMC, should decide what are the criteria & process for
> making someone a committer. There are some guidelines[1], but they are
> only guidelines.
>
> In my opinion, you should err on setting the bar too low rather than
> too high. Making someone a committer early will tend to draw them into
> the community. And, remember that code is not the only kind of
> contribution.
>
> The Quickstep community should also have a broader discussion: how do
> you intend to meet your goal of "Acquire early adopters". Electing
> committers is a consequence of a successful strategy for growing
> community, and helps further that growth.
>
> Julian
>
> [1] http://community.apache.org/newcommitter.html
>
> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel <ji...@pivotal.io> wrote:
>> Thanks Julian!
>>
>> What are the guidelines for election? We would love to welcome new
>> committers who are starting to make serious contributions.
>>
>> Cheers,
>> Jignesh
>>
>> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote:
>>
>> The key word here is "elected", as opposed to "showed up in his
>> congressional office for the first time". :)
>>
>>
Re: Podling Report Reminder - May 2016
Posted by Julian Hyde <jh...@apache.org>.
You, as a PMC, should decide what are the criteria & process for
making someone a committer. There are some guidelines[1], but they are
only guidelines.
In my opinion, you should err on setting the bar too low rather than
too high. Making someone a committer early will tend to draw them into
the community. And, remember that code is not the only kind of
contribution.
The Quickstep community should also have a broader discussion: how do
you intend to meet your goal of "Acquire early adopters". Electing
committers is a consequence of a successful strategy for growing
community, and helps further that growth.
Julian
[1] http://community.apache.org/newcommitter.html
On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel <ji...@pivotal.io> wrote:
> Thanks Julian!
>
> What are the guidelines for election? We would love to welcome new
> committers who are starting to make serious contributions.
>
> Cheers,
> Jignesh
>
> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote:
>
> The key word here is "elected", as opposed to "showed up in his
> congressional office for the first time". :)
>
>
Re: Podling Report Reminder - May 2016
Posted by Jignesh Patel <ji...@pivotal.io>.
Thanks Julian!
What are the guidelines for election? We would love to welcome new committers who are starting to make serious contributions.
Cheers,
Jignesh
> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote:
>
> The key word here is "elected", as opposed to "showed up in his
> congressional office for the first time". :)
Re: Podling Report Reminder - May 2016
Posted by Julian Hyde <jh...@apache.org>.
The key word here is "elected", as opposed to "showed up in his
congressional office for the first time". :)
This section is important because the IPMC is looking for indications
that the project is able to grow beyond its base of initial
committers.
I signed off.
Julian
On Thu, Jun 2, 2016 at 1:07 PM, Jignesh Patel <ji...@pivotal.io> wrote:
> Answers inlined.
>
>> On Jun 2, 2016, at 2:55 PM, Julian Hyde <jh...@apache.org> wrote:
>
>> The report makes the incorrect statement "Last committer joined on May
>> 30, 2016." No committers have been elected since incubation, as far as
>> I know. Please correct that statement.
>
> I mentioned this last committer date since Navneet joined the committer list on this date. But perhaps, I misunderstood the question. So, I have dropped that line altogether and made this N/A. Please feel free to let me know if there is a better answer there.
>
>> Also, please fix the formatting. There is a partial line "aware of?",
>> and "Quickstep has been incubating since 2016-03-29." should be a
>> separate paragraph.
>
> Done.
>
>>
>> I suggest that you email the mentors directly when the report is ready
>> for sign-off, this month and subsequent months. We're busy people, and
>> we sometimes need prodding.
>
> Will do. The new report is now ready with the changes above.
>
> Jignesh
Re: Podling Report Reminder - May 2016
Posted by Jignesh Patel <ji...@pivotal.io>.
Answers inlined.
> On Jun 2, 2016, at 2:55 PM, Julian Hyde <jh...@apache.org> wrote:
> The report makes the incorrect statement "Last committer joined on May
> 30, 2016." No committers have been elected since incubation, as far as
> I know. Please correct that statement.
I mentioned this last committer date since Navneet joined the committer list on this date. But perhaps, I misunderstood the question. So, I have dropped that line altogether and made this N/A. Please feel free to let me know if there is a better answer there.
> Also, please fix the formatting. There is a partial line "aware of?",
> and "Quickstep has been incubating since 2016-03-29." should be a
> separate paragraph.
Done.
>
> I suggest that you email the mentors directly when the report is ready
> for sign-off, this month and subsequent months. We're busy people, and
> we sometimes need prodding.
Will do. The new report is now ready with the changes above.
Jignesh