[GitHub] incubator-gossip pull request #7: Gossip 13

[edwardcapriolo]

Github user edwardcapriolo closed the pull request at:

https://github.com/apache/incubator-gossip/pull/7


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Board report

[P. Taylor Goetz]

Comments in-line below.

-Taylor

> On Jan 4, 2017, at 3:24 PM, 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.

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

[Josh Elser]

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:

[jira] [Resolved] (GOSSIP-34) Remove org.gson for release

[Edward Capriolo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GOSSIP-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Capriolo resolved GOSSIP-34.
---
Resolution: Fixed

> Remove org.gson for release
> ---
>
> Key: GOSSIP-34
> URL: https://issues.apache.org/jira/browse/GOSSIP-34
> Project: Gossip
>  Issue Type: Improvement
>Reporter: Edward Capriolo
>Assignee: Edward Capriolo
>
> org.json:json:jar:20090211:compile is not compatible with ASF licensing we 
> use it only to read startup settings in a file we need to remove this to go 
> +1 on our release



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Gossip (Incubating) version gossip-0.1.1-incubating (RC2)

[P . Taylor Goetz]

+1

I checked:

- DISCLAIMER exists
- NOTICE looks good.
- LICENSE looks good
- License headers present
- Can build from source (though I had to skip tests. I got the same failures as 
Josh).
- Signatures/hashes check out.

Nice work on the quick turnaround.

-Taylor

> On Jan 3, 2017, at 3:47 PM, Edward Capriolo  wrote:
> 
> I am pleased to be calling this vote for the source release of Apache Gossip
> 
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
> https://repository.apache.org/content/repositories/orgapachegossip-1002/
> 
> The Git commit ID is:
> 6720f35beb8718ae39018211f33bbff2ac782fb6
> https://github.com/apache/incubator-gossip/commit/6720f35beb8718ae39018211f33bbff2ac782fb6
> 
> The tag is:
> https://github.com/apache/incubator-gossip/tree/gossip-0.1.1-incubating-rc2
> 
> Checksums of:
> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip
> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip.md5
> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip.sha1
> SHA1: 66dfe09a925fe2650fd3d85c97fdc10b049a9776
> MD5: 2695f11e714edb1364a4105b970039b8
> 
> Are confirmed:
> [edward@jackintosh tmp]$ wget
> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip
> [edward@jackintosh tmp]$ md5sum gossip-0.1.1-incubating-source-release.zip
> 2695f11e714edb1364a4105b970039b8  gossip-0.1.1-incubating-source-release.zip
> [edward@jackintosh tmp]$ sha1sum gossip-0.1.1-incubating-source-release.zip
> 66dfe09a925fe2650fd3d85c97fdc10b049a9776
> gossip-0.1.1-incubating-source-release.zip
> 
> Release artifacts are signed with the following key:
> http://people.apache.org/~ecapriolo/
> http://people.apache.org/~ecapriolo/ecapriolo_asf.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/gossip/KEYS
> 
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> 
> Note: The end-to-end tests (ShutdownDeadtimeTest) tend to be flakey.
> https://issues.apache.org/jira/browse/GOSSIP-22 will address this feature
> in next release.
> 
> Release this package?
> [ ] +1 yes
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...