You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by Edward Capriolo <ed...@gmail.com> on 2017/01/04 20:24:21 UTC
Board report
I completed the board report, I wanted to get the RC voting going before
doing the report. If anyone has any comments/ suggestions let me know.
The report is due today (sorry if that puts a rush on anyone)
Thanks,
Edward
--------------------
Gossip
Gossip is a system to form peer-to-peer networks using the gossip
protocol.
Gossip has been incubating since 2016-05.
Three most important issues to address in the move towards graduation:
1. Establish an Apache website for Gossip that makes it easy for new
users and contributors to get started.
2. Focus on large scale multi-node testing.
3. Accrual Failure detection via (
https://issues.apache.org/jira/browse/GOSSIP-22)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
One contributer has been voted as a committer.
There are 13 watches 24 stars on github
How has the project developed since the last report?
Issues:
Period Created Resolved
July 2016 6 3
August 2016 3 3
September 2016 2 5
October 2016 7 5
November 2016 2 4
December 2016 0 0
January 2017 1 1
*Note: We completed several Tasks related to our first release that are not
accounted for in this report.
We also have several features/issues that have been frozen waiting for
release
Date of last release:
Currently in voting
When were the last committers or PMC members elected?
We added a committer during the last report cycle
Signed-off-by:
[X](Gossip) Edward Capriolo
[ ](Gossip) Josh Elser
[ ](Gossp) P. Taylor
Shepherd/Mentor notes:
Re: Board report
Posted by Edward Capriolo <ed...@gmail.com>.
On Wed, Jan 4, 2017 at 3:39 PM, Josh Elser <el...@apache.org> wrote:
>
>
> Edward Capriolo wrote:
>
>> I completed the board report, I wanted to get the RC voting going before
>> doing the report. If anyone has any comments/ suggestions let me know.
>>
>> The report is due today (sorry if that puts a rush on anyone)
>>
>>
>> Thanks,
>> Edward
>>
>> --------------------
>> Gossip
>>
>> Gossip is a system to form peer-to-peer networks using the gossip
>> protocol.
>>
>> Gossip has been incubating since 2016-05.
>>
>> Three most important issues to address in the move towards graduation:
>>
>> 1. Establish an Apache website for Gossip that makes it easy for new
>> users and contributors to get started.
>> 2. Focus on large scale multi-node testing.
>> 3. Accrual Failure detection via (
>> https://issues.apache.org/jira/browse/GOSSIP-22)
>>
>
> Personally, I view "ready for graduation" in terms of the community side
> much more than the technical side. Yes, you do typically attract new devs
> via technical merit/worth, but the graduation requirements really have
> nothing to do with the technical details.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>> No
>>
>>
>> How has the community developed since the last report?
>>
>> One contributer has been voted as a committer.
>> There are 13 watches 24 stars on github
>>
>
> We haven't seen any new contributors, have we?
>
> I would also mention Sean stepping down as a mentor and adopting Drew as a
> replacement.
>
> How has the project developed since the last report?
>>
>> Issues:
>> Period Created Resolved
>> July 2016 6 3
>> August 2016 3 3
>> September 2016 2 5
>> October 2016 7 5
>> November 2016 2 4
>> December 2016 0 0
>> January 2017 1 1
>>
>> *Note: We completed several Tasks related to our first release that are
>> not
>> accounted for in this report.
>> We also have several features/issues that have been frozen waiting for
>> release
>>
>
> I'm really not a fan of this chart as a measure of how the project has
> developed. Would strongly recommend putting this into words: mention
> Chandresh moving from a contributor to a committer, acknowledge the periods
> of little/no activity, acknowledge the few assorted contributions from new
> people.
>
> Date of last release:
>>
>> Currently in voting
>>
>> When were the last committers or PMC members elected?
>>
>> We added a committer during the last report cycle
>>
>> Signed-off-by:
>>
>> [X](Gossip) Edward Capriolo
>>
>
> You don't sign off -- mentors do.
>
> [ ](Gossip) Josh Elser
>> [ ](Gossp) P. Taylor
>> Shepherd/Mentor notes:
>>
>>
Personally, I view "ready for graduation" in terms of the community side
much more than the technical side. Yes, you do typically attract new devs
via technical merit/worth, but the graduation requirements really have
nothing to do with the technical details.
Ok people have asked for more material from me like a code walk through. I
will address those.
We haven't seen any new contributors, have we?
This information is a bit difficult to query from Jira but I think we have
had a small contribution that I can remember:
https://issues.apache.org/jira/browse/GOSSIP-31
I believe there was on other.
I plan on committing this once we lock in the release.
Here is my update
--------------------
Gossip
Gossip is a system to form peer-to-peer networks using the gossip
protocol.
Gossip has been incubating since 2016-05.
Three most important issues to address in the move towards graduation:
1. Create some tutorial videos and blog posts to educate people on Gossip
Project
2. Focus on some critical technnical improvements multi-node testing and
accrual
failure detection that will be critical for adoption into other projects
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
One contributer has been voted as a committer. There are 13 watches 24
stars on github. Sean Busbey has stepped down as a mentor. Sean's early
help was critical to this hatchling. Thank you Sean.
Drew Farris has taken a role as a mentor.
Some technical features were frozen out until we completed our first
release. Effort was spent on doing the first
release (getting access, key signing, correctly enabling RAT maven plugin
etc). This was mostly one-time effort.
Date of last release:
Our first release is currently in voting.
When were the last committers or PMC members elected?
Chandresh Panchol as added as a committer.
Signed-off-by:
[ ](Gossip) Josh Elser
[ ](Gossp) P. Taylor Goetz
Shepherd/Mentor notes:
Re: Board report
Posted by Josh Elser <el...@apache.org>.
Edward Capriolo wrote:
> I completed the board report, I wanted to get the RC voting going before
> doing the report. If anyone has any comments/ suggestions let me know.
>
> The report is due today (sorry if that puts a rush on anyone)
>
>
> Thanks,
> Edward
>
> --------------------
> Gossip
>
> Gossip is a system to form peer-to-peer networks using the gossip
> protocol.
>
> Gossip has been incubating since 2016-05.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Establish an Apache website for Gossip that makes it easy for new
> users and contributors to get started.
> 2. Focus on large scale multi-node testing.
> 3. Accrual Failure detection via (
> https://issues.apache.org/jira/browse/GOSSIP-22)
Personally, I view "ready for graduation" in terms of the community side
much more than the technical side. Yes, you do typically attract new
devs via technical merit/worth, but the graduation requirements really
have nothing to do with the technical details.
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> No
>
>
> How has the community developed since the last report?
>
> One contributer has been voted as a committer.
> There are 13 watches 24 stars on github
We haven't seen any new contributors, have we?
I would also mention Sean stepping down as a mentor and adopting Drew as
a replacement.
> How has the project developed since the last report?
>
> Issues:
> Period Created Resolved
> July 2016 6 3
> August 2016 3 3
> September 2016 2 5
> October 2016 7 5
> November 2016 2 4
> December 2016 0 0
> January 2017 1 1
>
> *Note: We completed several Tasks related to our first release that are not
> accounted for in this report.
> We also have several features/issues that have been frozen waiting for
> release
I'm really not a fan of this chart as a measure of how the project has
developed. Would strongly recommend putting this into words: mention
Chandresh moving from a contributor to a committer, acknowledge the
periods of little/no activity, acknowledge the few assorted
contributions from new people.
> Date of last release:
>
> Currently in voting
>
> When were the last committers or PMC members elected?
>
> We added a committer during the last report cycle
>
> Signed-off-by:
>
> [X](Gossip) Edward Capriolo
You don't sign off -- mentors do.
> [ ](Gossip) Josh Elser
> [ ](Gossp) P. Taylor
> Shepherd/Mentor notes:
>
Re: Board report
Posted by Josh Elser <el...@apache.org>.
Good enough for me. Looks much better, thank again for your
responsiveness, Edward!
Edward Capriolo wrote:
> I uploaded the report to
> https://wiki.apache.org/incubator/January2017#preview
>
> @Taylor
> Thank you. I put an X next to your name because you said: "The updated
> report looks better."
>
> @Josh @Drew
> There is space for you to X if you wish.
>
> If I got ahead of the game by posting to the wiki let me know and I will
> withdraw it.
>
> Thank you,
> Edward
>
>
>
>
> On Wed, Jan 4, 2017 at 4:32 PM, P. Taylor Goetz<pt...@gmail.com> wrote:
>
>> Parallelism and eventual consistency at work. ;) (See my previous response)
>>
>> I agree with Josh\u2019s comments, especially wrt mentioning mentor changes.
>>
>> In general, I\u2019d say try to be as detailed as possible, avoid statements
>> that will raise questions, and focus on what\u2019s important to the IPMC (i.e.
>> community growth, making releases, etc.).
>>
>> The updated report looks better.
>>
>> -Taylor
>>
>>
>>> On Jan 4, 2017, at 4:27 PM, Edward Capriolo<ed...@gmail.com>
>> wrote:
>>> "What are the tasks that aren\u2019t accounted for? And what tasks are pending
>>> release? The above statements raise questions."
>>>
>>> That breakdown was from Jira, I realize that the report only counts
>>> "Issues" not "tasks" and some other types. So the 0 was very misleading
>>> because things i did like fix javadoc and add rat plugin were not
>> counted.
>>> Please see the updated report in my last email.
>>>
>>> On Wed, Jan 4, 2017 at 4:21 PM, P. Taylor Goetz<pt...@gmail.com>
>> wrote:
>>>> Comments in-line below.
>>>>
>>>> -Taylor
>>>>
>>>>> On Jan 4, 2017, at 3:24 PM, Edward Capriolo<ed...@gmail.com>
>>>> wrote:
>>>>> I completed the board report, I wanted to get the RC voting going
>> before
>>>>> doing the report. If anyone has any comments/ suggestions let me know.
>>>>>
>>>>> The report is due today (sorry if that puts a rush on anyone)
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Edward
>>>>>
>>>>> --------------------
>>>>> Gossip
>>>>>
>>>>> Gossip is a system to form peer-to-peer networks using the gossip
>>>>> protocol.
>>>>>
>>>>> Gossip has been incubating since 2016-05.
>>>>>
>>>>> Three most important issues to address in the move towards graduation:
>>>>>
>>>>> 1. Establish an Apache website for Gossip that makes it easy for new
>>>>> users and contributors to get started.
>>>> Minor nit: Gossip already has a website, do you mean expanding? I do
>> like
>>>> the community-building aspect here though.
>>>>
>>>>> 2. Focus on large scale multi-node testing.
>>>>> 3. Accrual Failure detection via (
>>>>> https://issues.apache.org/jira/browse/GOSSIP-22)
>>>> These are technical aspects that the IPMC likely doesn\u2019t care too much
>>>> about. The IPMC cares more about what the projects needs to do in order
>> to
>>>> graduate. As a mentor, I\u2019d say the top two right now are:
>>>>
>>>> 1. Grow the community.
>>>> 2. Make more frequents releases.
>>>>
>>>>
>>>>
>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>>>> aware of?
>>>>>
>>>>> No
>>>>>
>>>>>
>>>>> How has the community developed since the last report?
>>>>>
>>>>> One contributer has been voted as a committer.
>>>> Who is the committer and when were they added (I know, but it is helpful
>>>> to include this information in the report)?
>>>>
>>>>> There are 13 watches 24 stars on github
>>>>>
>>>>>
>>>>> How has the project developed since the last report?
>>>>>
>>>>> Issues:
>>>>> Period Created Resolved
>>>>> July 2016 6 3
>>>>> August 2016 3 3
>>>>> September 2016 2 5
>>>>> October 2016 7 5
>>>>> November 2016 2 4
>>>>> December 2016 0 0
>>>>> January 2017 1 1
>>>> I would just summarize for the current reporting period. E.g. "X/Y
>> issues
>>>> created/resolved in the current reporting period. X/Y in the previous
>>>> period."
>>>>
>>>>> *Note: We completed several Tasks related to our first release that are
>>>> not
>>>>> accounted for in this report.
>>>>> We also have several features/issues that have been frozen waiting for
>>>>> release
>>>> What are the tasks that aren\u2019t accounted for? And what tasks are pending
>>>> release? The above statements raise questions.
>>>>
>>>>> Date of last release:
>>>>>
>>>>> Currently in voting
>>>>>
>>>>> When were the last committers or PMC members elected?
>>>>>
>>>>> We added a committer during the last report cycle
>>>>>
>>>>> Signed-off-by:
>>>>>
>>>>> [X](Gossip) Edward Capriolo
>>>>> [ ](Gossip) Josh Elser
>>>>> [ ](Gossp) P. Taylor
>>>>> Shepherd/Mentor notes:
>>>>
>>
>
Re: Board report
Posted by Edward Capriolo <ed...@gmail.com>.
I uploaded the report to
https://wiki.apache.org/incubator/January2017#preview
@Taylor
Thank you. I put an X next to your name because you said: "The updated
report looks better."
@Josh @Drew
There is space for you to X if you wish.
If I got ahead of the game by posting to the wiki let me know and I will
withdraw it.
Thank you,
Edward
On Wed, Jan 4, 2017 at 4:32 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
> Parallelism and eventual consistency at work. ;) (See my previous response)
>
> I agree with Josh’s comments, especially wrt mentioning mentor changes.
>
> In general, I’d say try to be as detailed as possible, avoid statements
> that will raise questions, and focus on what’s important to the IPMC (i.e.
> community growth, making releases, etc.).
>
> The updated report looks better.
>
> -Taylor
>
>
> > On Jan 4, 2017, at 4:27 PM, Edward Capriolo <ed...@gmail.com>
> wrote:
> >
> > "What are the tasks that aren’t accounted for? And what tasks are pending
> > release? The above statements raise questions."
> >
> > That breakdown was from Jira, I realize that the report only counts
> > "Issues" not "tasks" and some other types. So the 0 was very misleading
> > because things i did like fix javadoc and add rat plugin were not
> counted.
> >
> > Please see the updated report in my last email.
> >
> > On Wed, Jan 4, 2017 at 4:21 PM, P. Taylor Goetz <pt...@gmail.com>
> wrote:
> >
> >> Comments in-line below.
> >>
> >> -Taylor
> >>
> >>> On Jan 4, 2017, at 3:24 PM, Edward Capriolo <ed...@gmail.com>
> >> wrote:
> >>>
> >>> I completed the board report, I wanted to get the RC voting going
> before
> >>> doing the report. If anyone has any comments/ suggestions let me know.
> >>>
> >>> The report is due today (sorry if that puts a rush on anyone)
> >>>
> >>>
> >>> Thanks,
> >>> Edward
> >>>
> >>> --------------------
> >>> Gossip
> >>>
> >>> Gossip is a system to form peer-to-peer networks using the gossip
> >>> protocol.
> >>>
> >>> Gossip has been incubating since 2016-05.
> >>>
> >>> Three most important issues to address in the move towards graduation:
> >>>
> >>> 1. Establish an Apache website for Gossip that makes it easy for new
> >>> users and contributors to get started.
> >>
> >> Minor nit: Gossip already has a website, do you mean expanding? I do
> like
> >> the community-building aspect here though.
> >>
> >>> 2. Focus on large scale multi-node testing.
> >>> 3. Accrual Failure detection via (
> >>> https://issues.apache.org/jira/browse/GOSSIP-22)
> >>
> >> These are technical aspects that the IPMC likely doesn’t care too much
> >> about. The IPMC cares more about what the projects needs to do in order
> to
> >> graduate. As a mentor, I’d say the top two right now are:
> >>
> >> 1. Grow the community.
> >> 2. Make more frequents releases.
> >>
> >>
> >>
> >>>
> >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >>> aware of?
> >>>
> >>> No
> >>>
> >>>
> >>> How has the community developed since the last report?
> >>>
> >>> One contributer has been voted as a committer.
> >>
> >> Who is the committer and when were they added (I know, but it is helpful
> >> to include this information in the report)?
> >>
> >>> There are 13 watches 24 stars on github
> >>>
> >>>
> >>> How has the project developed since the last report?
> >>>
> >>> Issues:
> >>> Period Created Resolved
> >>> July 2016 6 3
> >>> August 2016 3 3
> >>> September 2016 2 5
> >>> October 2016 7 5
> >>> November 2016 2 4
> >>> December 2016 0 0
> >>> January 2017 1 1
> >>
> >> I would just summarize for the current reporting period. E.g. "X/Y
> issues
> >> created/resolved in the current reporting period. X/Y in the previous
> >> period."
> >>
> >>>
> >>> *Note: We completed several Tasks related to our first release that are
> >> not
> >>> accounted for in this report.
> >>> We also have several features/issues that have been frozen waiting for
> >>> release
> >>
> >> What are the tasks that aren’t accounted for? And what tasks are pending
> >> release? The above statements raise questions.
> >>
> >>>
> >>> Date of last release:
> >>>
> >>> Currently in voting
> >>>
> >>> When were the last committers or PMC members elected?
> >>>
> >>> We added a committer during the last report cycle
> >>>
> >>> Signed-off-by:
> >>>
> >>> [X](Gossip) Edward Capriolo
> >>> [ ](Gossip) Josh Elser
> >>> [ ](Gossp) P. Taylor
> >>> Shepherd/Mentor notes:
> >>
> >>
>
>
Re: Board report
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Parallelism and eventual consistency at work. ;) (See my previous response)
I agree with Josh’s comments, especially wrt mentioning mentor changes.
In general, I’d say try to be as detailed as possible, avoid statements that will raise questions, and focus on what’s important to the IPMC (i.e. community growth, making releases, etc.).
The updated report looks better.
-Taylor
> On Jan 4, 2017, at 4:27 PM, Edward Capriolo <ed...@gmail.com> wrote:
>
> "What are the tasks that aren’t accounted for? And what tasks are pending
> release? The above statements raise questions."
>
> That breakdown was from Jira, I realize that the report only counts
> "Issues" not "tasks" and some other types. So the 0 was very misleading
> because things i did like fix javadoc and add rat plugin were not counted.
>
> Please see the updated report in my last email.
>
> On Wed, Jan 4, 2017 at 4:21 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
>
>> Comments in-line below.
>>
>> -Taylor
>>
>>> On Jan 4, 2017, at 3:24 PM, Edward Capriolo <ed...@gmail.com>
>> wrote:
>>>
>>> I completed the board report, I wanted to get the RC voting going before
>>> doing the report. If anyone has any comments/ suggestions let me know.
>>>
>>> The report is due today (sorry if that puts a rush on anyone)
>>>
>>>
>>> Thanks,
>>> Edward
>>>
>>> --------------------
>>> Gossip
>>>
>>> Gossip is a system to form peer-to-peer networks using the gossip
>>> protocol.
>>>
>>> Gossip has been incubating since 2016-05.
>>>
>>> Three most important issues to address in the move towards graduation:
>>>
>>> 1. Establish an Apache website for Gossip that makes it easy for new
>>> users and contributors to get started.
>>
>> Minor nit: Gossip already has a website, do you mean expanding? I do like
>> the community-building aspect here though.
>>
>>> 2. Focus on large scale multi-node testing.
>>> 3. Accrual Failure detection via (
>>> https://issues.apache.org/jira/browse/GOSSIP-22)
>>
>> These are technical aspects that the IPMC likely doesn’t care too much
>> about. The IPMC cares more about what the projects needs to do in order to
>> graduate. As a mentor, I’d say the top two right now are:
>>
>> 1. Grow the community.
>> 2. Make more frequents releases.
>>
>>
>>
>>>
>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> aware of?
>>>
>>> No
>>>
>>>
>>> How has the community developed since the last report?
>>>
>>> One contributer has been voted as a committer.
>>
>> Who is the committer and when were they added (I know, but it is helpful
>> to include this information in the report)?
>>
>>> There are 13 watches 24 stars on github
>>>
>>>
>>> How has the project developed since the last report?
>>>
>>> Issues:
>>> Period Created Resolved
>>> July 2016 6 3
>>> August 2016 3 3
>>> September 2016 2 5
>>> October 2016 7 5
>>> November 2016 2 4
>>> December 2016 0 0
>>> January 2017 1 1
>>
>> I would just summarize for the current reporting period. E.g. "X/Y issues
>> created/resolved in the current reporting period. X/Y in the previous
>> period."
>>
>>>
>>> *Note: We completed several Tasks related to our first release that are
>> not
>>> accounted for in this report.
>>> We also have several features/issues that have been frozen waiting for
>>> release
>>
>> What are the tasks that aren’t accounted for? And what tasks are pending
>> release? The above statements raise questions.
>>
>>>
>>> Date of last release:
>>>
>>> Currently in voting
>>>
>>> When were the last committers or PMC members elected?
>>>
>>> We added a committer during the last report cycle
>>>
>>> Signed-off-by:
>>>
>>> [X](Gossip) Edward Capriolo
>>> [ ](Gossip) Josh Elser
>>> [ ](Gossp) P. Taylor
>>> Shepherd/Mentor notes:
>>
>>
Re: Board report
Posted by Edward Capriolo <ed...@gmail.com>.
"What are the tasks that aren’t accounted for? And what tasks are pending
release? The above statements raise questions."
That breakdown was from Jira, I realize that the report only counts
"Issues" not "tasks" and some other types. So the 0 was very misleading
because things i did like fix javadoc and add rat plugin were not counted.
Please see the updated report in my last email.
On Wed, Jan 4, 2017 at 4:21 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
> Comments in-line below.
>
> -Taylor
>
> > On Jan 4, 2017, at 3:24 PM, Edward Capriolo <ed...@gmail.com>
> wrote:
> >
> > I completed the board report, I wanted to get the RC voting going before
> > doing the report. If anyone has any comments/ suggestions let me know.
> >
> > The report is due today (sorry if that puts a rush on anyone)
> >
> >
> > Thanks,
> > Edward
> >
> > --------------------
> > Gossip
> >
> > Gossip is a system to form peer-to-peer networks using the gossip
> > protocol.
> >
> > Gossip has been incubating since 2016-05.
> >
> > Three most important issues to address in the move towards graduation:
> >
> > 1. Establish an Apache website for Gossip that makes it easy for new
> > users and contributors to get started.
>
> Minor nit: Gossip already has a website, do you mean expanding? I do like
> the community-building aspect here though.
>
> > 2. Focus on large scale multi-node testing.
> > 3. Accrual Failure detection via (
> > https://issues.apache.org/jira/browse/GOSSIP-22)
>
> These are technical aspects that the IPMC likely doesn’t care too much
> about. The IPMC cares more about what the projects needs to do in order to
> graduate. As a mentor, I’d say the top two right now are:
>
> 1. Grow the community.
> 2. Make more frequents releases.
>
>
>
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No
> >
> >
> > How has the community developed since the last report?
> >
> > One contributer has been voted as a committer.
>
> Who is the committer and when were they added (I know, but it is helpful
> to include this information in the report)?
>
> > There are 13 watches 24 stars on github
> >
> >
> > How has the project developed since the last report?
> >
> > Issues:
> > Period Created Resolved
> > July 2016 6 3
> > August 2016 3 3
> > September 2016 2 5
> > October 2016 7 5
> > November 2016 2 4
> > December 2016 0 0
> > January 2017 1 1
>
> I would just summarize for the current reporting period. E.g. "X/Y issues
> created/resolved in the current reporting period. X/Y in the previous
> period."
>
> >
> > *Note: We completed several Tasks related to our first release that are
> not
> > accounted for in this report.
> > We also have several features/issues that have been frozen waiting for
> > release
>
> What are the tasks that aren’t accounted for? And what tasks are pending
> release? The above statements raise questions.
>
> >
> > Date of last release:
> >
> > Currently in voting
> >
> > When were the last committers or PMC members elected?
> >
> > We added a committer during the last report cycle
> >
> > Signed-off-by:
> >
> > [X](Gossip) Edward Capriolo
> > [ ](Gossip) Josh Elser
> > [ ](Gossp) P. Taylor
> > Shepherd/Mentor notes:
>
>
Re: Board report
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Comments in-line below.
-Taylor
> On Jan 4, 2017, at 3:24 PM, Edward Capriolo <ed...@gmail.com> wrote:
>
> I completed the board report, I wanted to get the RC voting going before
> doing the report. If anyone has any comments/ suggestions let me know.
>
> The report is due today (sorry if that puts a rush on anyone)
>
>
> Thanks,
> Edward
>
> --------------------
> Gossip
>
> Gossip is a system to form peer-to-peer networks using the gossip
> protocol.
>
> Gossip has been incubating since 2016-05.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Establish an Apache website for Gossip that makes it easy for new
> users and contributors to get started.
Minor nit: Gossip already has a website, do you mean expanding? I do like the community-building aspect here though.
> 2. Focus on large scale multi-node testing.
> 3. Accrual Failure detection via (
> https://issues.apache.org/jira/browse/GOSSIP-22)
These are technical aspects that the IPMC likely doesn’t care too much about. The IPMC cares more about what the projects needs to do in order to graduate. As a mentor, I’d say the top two right now are:
1. Grow the community.
2. Make more frequents releases.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> No
>
>
> How has the community developed since the last report?
>
> One contributer has been voted as a committer.
Who is the committer and when were they added (I know, but it is helpful to include this information in the report)?
> There are 13 watches 24 stars on github
>
>
> How has the project developed since the last report?
>
> Issues:
> Period Created Resolved
> July 2016 6 3
> August 2016 3 3
> September 2016 2 5
> October 2016 7 5
> November 2016 2 4
> December 2016 0 0
> January 2017 1 1
I would just summarize for the current reporting period. E.g. "X/Y issues created/resolved in the current reporting period. X/Y in the previous period."
>
> *Note: We completed several Tasks related to our first release that are not
> accounted for in this report.
> We also have several features/issues that have been frozen waiting for
> release
What are the tasks that aren’t accounted for? And what tasks are pending release? The above statements raise questions.
>
> Date of last release:
>
> Currently in voting
>
> When were the last committers or PMC members elected?
>
> We added a committer during the last report cycle
>
> Signed-off-by:
>
> [X](Gossip) Edward Capriolo
> [ ](Gossip) Josh Elser
> [ ](Gossp) P. Taylor
> Shepherd/Mentor notes: