Re: [VOTE] Retire Gossip

[P. Taylor Goetz]

+1

-Taylor

> On Aug 6, 2018, at 12:48 PM, Josh Elser  wrote:
> 
> Please vote to retire Gossip from the ASF Incubator. My take is that Gossip 
> has failed to get adequate community traction in the ASF Incubator and the 
> administrative work of the ASF is more of a burden than a benefit to the 
> project. Exiting incubation right now seems like the obvious benefit to 
> everyone -- the decision to return can always be made later and should be 
> easier to execute the second time around.
> 
> [ ] +1 to retire
> [ ] -1 Not retiring because..
> 
> Here's my +1
> 
> This will be open for at least 72 hours and is a Majority vote.
> 
> - Josh



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Leave apache and the incubator

[P. Taylor Goetz]

We should start with a retirement vote on dev@. If that passes, we move on to a 
IPMC vote on retirement.

Once that’s done, there are a few administrative steps that need to be done. [1]

-Taylor

[1] https://incubator.apache.org/guides/retirement.html

> On Aug 6, 2018, at 11:20 AM, Edward Capriolo  wrote:
> 
> Yes. Let figure out the steps.
> 
> On Mon, Aug 6, 2018 at 10:35 AM, Josh Elser  wrote:
> 
>> Should I help by looking at what actually needs to be done to retire?
>> Seems like we're back in the same exact state :)
>> 
>> I'd rather us focus efforts on retiring than writing yet another incubator
>> report that says "nothing happened".
>> 
>> On 7/25/18 1:29 PM, Edward Capriolo wrote:
>> 
>>> To follow up on this.
>>> 
>>> +1 from me for "let's get things reviewed & merged before next report in a
>>> month".
>>> 
>>> No activity has happened. The board reports are due soon, I would rather
>>> not write another report to summarize no activity. We should start the
>>> vote
>>> to shut down now.
>>> 
>>> 
>>> 
>>> On Tue, Jul 10, 2018 at 6:01 PM, Sree V 
>>> wrote:
>>> 
>>> Hi Edward,
 I am not aware of the difficulty in setting up the website or continuous
 modifications to it.If you feel so, you may make a motion for an
 alternate
 solutions (eg. git pages, ...) and link to 'gossip.incubator.apache.org
 '.And
 Apache.org is allowing it, now. Similar to, https://apache.github.io/
 incubator-heron/
 It would be a one time task.
 
 
 +1 from me for "let's get things reviewed & merged before next report in
 a
 month".
 
 
 Hi Josh,
 You have been very helpful so far.  And I appreciate that,
 personally.Please suggest a replacement or ad-hoc help that can set us in
 motion for the next few months, until we streamline.
 
 
 Hi Edward/Team,
 I am proposing a meetup event for kick start, again.A hackathon style,
 that would add to our code base.
 Josh came forward honestly. Thank you. Let us go through the rest of the
 names assigned to gossip and find out their level of contributions to
 gossip.And may be find alternatives or announce open positions.That
 should
 attract contributors to gossip.
 
 
 Thank you.Sree
 
 On Monday, July 9, 2018, 11:35:21 AM PDT, Josh Elser <
 els...@apache.org> wrote:
 
  I'd clarify that I don't consider myself to be a part of Gossip. I
 exist
 only to satisfy my obligations of being a mentor (and even that is
 difficult for me, most days).
 
 On 7/8/18 11:21 AM, Sree V wrote:
 
> Hi Edward,
> Allow me to introduce myself, as the creator of the current gossip
> 
 website with the help of Josh.
 
> I prefer to stay in Apache.org.
> 
> Four willing people from this conversation, should be good enough to
> 
 take Gossip forward.(Josh, Chandresh, Ankur & Myself)
 
> 
> You summarized the work involved very nicely.  Thanks.Let's add (i mean
> 
 request) names to each of those tasks. And we are done.
 
> 
> 
> "Delegate"; "Divide & Conquer"; "Epic, Story, Tasks..."  always
> 
 worked historically.
 
> 
> 
> Thank you.Sree Vaddi
> 650.213.2707 M
> 
> 
>  On Friday, July 6, 2018, 8:07:58 AM PDT, Josh Elser <
> 
 els...@apache.org> wrote:
 
> 
>  On 7/5/18 6:59 PM, Edward Capriolo wrote:
> 
>> Of the ones with reports, not much sign off.
>> 
>> 
>> So if your going to make a big deal about reports...time to shut down
>> 
> the
 
> entire incubator.
>> 
> 
> While I know this is tongue-in-cheek, the folks who help out in the
> Incubator are well-stretched already. This isn't a new discussion that
> is coming out of the IPMC -- I'm just actually trying to get Gossip to
> honestly think about this (the comments about how using Github would be
> easier made me think I wasn't off-base).
> 
> 
> 
 
>>> 



signature.asc
Description: Message signed with OpenPGP

Re: Podling Report Reminder - May 2018

[P. Taylor Goetz]

Anyone willing to take this up?

Since Gossip failed to report last cycle, a solid report this month might 
preempt concerns from the IPMC and/or board as to the viability of the project.

Reports may be a nuisance, but not a big ask, especially after you go from 
monthly to quarterly. Not reporting is a bad sign.

-Taylor

> On Apr 30, 2018, at 8:27 PM, johndam...@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, 16 May 2018, 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, May 02).
> 
> 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://wiki.apache.org/incubator/May2018
> 
> 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

Incubator/Board Report Due

[P. Taylor Goetz]

Anyone willing or available to produce a Report?

Failure to report is a sign of trouble. Is it time to think about retirement? I 
don’t see a lot of activity.

That being said, there’s nothing inherently wrong with retiring, it’s just 
another exit point. There’s nothing to stop development progressing elsewhere.

There is, however, a cost associated with podlings in terms of the IPMC. 
Incubating a podling takes volunteer effort on a number of levels.

-Taylor

Re: Vision letter, reqest for discussion

[P. Taylor Goetz]

> On Jul 11, 2017, at 11:15 AM, Русак Максим  wrote:
> 
> "Features for features" is not our goal. "Features for solving users' pain" 
> have sense.

I would propose rephrasing that to “Features that make Gossip useful” is the 
goal. 

> On Jul 11, 2017, at 12:58 PM, Edward Capriolo  wrote:
> 
> There is no simple answer. I think the primary vehicle is blogging and
> community. For example I asked everyone to write up their GSOC work into
> blogs:
> 
> 
>   - Wrote a blog regarding Data Change Event Listeners
>  -  https://medium.com/@mirage20/listening-to-data-change- 
> 
>  events-in-apache-gossip-a0f0a4ea4c21
>  
>   
> >
>   - Wrote a blog regarding Data Replication Control
>  - https://medium.com/@mirage20/data-replication-control-in- 
> 
>  apache-gossip-3571e2bb
> 
> I can tweet out these blogs, some people follow me, they might re-tweet,
> word of mouth we get users who try software or committers interested in
> scratching their own itch.


+1 I think growing the community should be the primary goal at this point. But 
to grow the community people need to know about the project and more 
specifically what Gossip can do for them and their projects.

The blog posts you linked to are great, and I will tweet them out as well. 
However, they are pretty deep in the weeds. That shouldn’t be taken as a 
criticism, I just want to make the point that we should focus more on what 
Gossip can be used for. To that end I’d suggest focusing on higher-level use 
cases. Build some sample applications (anyone remember the J2EE Pet Store?) 
that do something interesting/useful with Gossips features, include it in the 
distribution, write a blog post or documentation about it, and promote it. 
Being able to get a working sample application running in less than 15 minutes 
can be powerful in terms of enticing users to dig deeper.

I also can’t overstate the importance of documentation. When I land on the 
Gossip website, I should quickly learn what it is, its features, and what use 
cases it is applicable too. Then I should be able to clone the repo and get 
some sample apps running with minimal friction. Right now to get to the current 
examples I need to dig into the GitHub repo to find the README for the 
examples. The examples should be (linked) front and center on the website/main 
README. And again, there should be examples that do something useful.

> On Jul 17, 2017, at 5:31 PM, Edward Capriolo  wrote:
> 
> We just do not have the bodies for that.  If you want to make a change (as
> a committer) you do not really have to wait around for consensus. For a
> committer there is an implicit "WILL MERGE IN 2 DAYS IF NO COMMENT". If you
> are not a committer (or want to wait for my blessing) you are probably
> going to have to send me a singing telegram or two. Doing the apache
> releases takes cycles, mentoring the GSOC proposals takes cycles, life,
> jobs, etc.

The Gossip community should figure out whether it is RTC (Review Then Commit) 
or CTR (Commit Then Review) or some hybrid (e.g. RTC for main codebase, CTR for 
documentation, etc.). For the “WILL MERGE IN X DAYS” I would suggest making 
that explicit in the pull request: e.g. “I plan on merging this in X days if 
there are no objections.” That gives other committers/contributors a heads up 
about your intent.


> 
> As for Gossip having a direction, I don't want Gossip to follow the lead of
> other "owned" apache projects. "Hey we are 'EdTech' the commercial
> consulting/solutions arm in the engine room of 'apache gossip' we have all
> the committers and we have a ROAD MAP and our CTO KNOWS WHAT TO DO BASED ON
> WHAT OUR INVESTORS WANT TO HEAR and if your working on something else
> ..tough crap."  :)

+1 Apache projects are owned, led, etc. by their respective communities, not 
any individual or outside organization.


> 
> I am trying to move at a pace that others can follow/play along. I _COULD_
> have implemented all the CRDTs, but I did one and left the rest open. This
> leaves a door open for others to make meaningful contributions. That is
> essentially what I am trying to do, guide.

That’s a good approach. Another one is to mark issues with a “newbie” label.

> If i had more time (job, gossip
> (reviews, releases, gsoc), other apache pmc roles, 2 year old) i would
> probably do more outreach like meetups and blogs. There are less bodies on
> deck then I expected at this phase but such is life. I see some projects
> are in the incubator for 3-4 years, not trying to go that long, but not
> trying to rush either.

Outreach is not the responsibility of a single person, but that of the whole 
community.

Graduation is largely a func

Re: [GSoC 2017] CRDT Umbrella

[P. Taylor Goetz]

Welcome to the Gossip community Mirage!

Looks like you and Edward are working together well on scoping out the work. 
Well done.

-Taylor

> On Mar 10, 2017, at 7:00 PM, Edward Capriolo  wrote:
> 
> On Fri, Mar 10, 2017 at 4:46 PM, Mirage Abeysekara 
> wrote:
> 
>> My apache-jira id is mirage20
>> 
>> 
>> *Mirage Abeysekara*
>> Undergraduate
>> Computer Science and Engineering
>> University of Moratuwa
>> Twitter: https://twitter.com/MiRAGECreator
>> GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
>> 
>>> On 10 March 2017 at 18:23, Edward Capriolo  wrote:
>>> 
>>> Thanks,
>>> 
>>> What is your apache-jira id?
>>> 
>>> On Thu, Mar 9, 2017 at 3:49 AM, Mirage Abeysekara <
>> mirage...@cse.mrt.ac.lk
 
>>> wrote:
>>> 
 Hi Edward,
 
 I created a new PR with proper formatting
 https://github.com/apache/incubator-gossip/pull/42
 
 "pub sub on data objects" looks great. Can you please provide mode
>>> details
 (or example) on that issue?
 Is it like adding CRDT data change events for a same node? or between
 nodes?
 
 Thanks.
 
 *Mirage Abeysekara*
 Undergraduate
 Computer Science and Engineering
 University of Moratuwa
 Twitter: https://twitter.com/MiRAGECreator
 GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
 
 On 9 March 2017 at 12:11, Edward Capriolo 
>> wrote:
 
> On Thu, Mar 9, 2017 at 12:43 AM, Mirage Abeysekara <
> mirage...@cse.mrt.ac.lk>
> wrote:
> 
>> Hello Edward,
>> 
>> I updated the PR based on your review.
>> 
>> I didn’t understand what you meant. You mean all the CRDT tickets
>>> under
>> GSoC are assigned for someone or ticket that I tried to fix?
>> 
>> Thanks.
>> 
>> *Mirage Abeysekara*
>> Undergraduate
>> Computer Science and Engineering
>> University of Moratuwa
>> Twitter: https://twitter.com/MiRAGECreator
>> GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
>> 
>> On 8 March 2017 at 21:30, Edward Capriolo 
 wrote:
>> 
>>> Mirage,
>>> 
>>> Also something important to note: Please try to not to work on
>> any
 more
>>> tickets labeled GSOC yet. We already have someone interested in
>>> doing
>> GSOC
>>> (with gossip) and we sized that work so there would be
>> substantial
 work
>> for
>>> that one person to do during the GSOC period. We need to slice
>> off
 more
>>> work likely if we end up with two GSOC applicants.
>>> 
>>> Thanks
>>> 
>>> On Wed, Mar 8, 2017 at 8:29 AM, Edward Capriolo <
 edlinuxg...@gmail.com
>> 
>>> wrote:
>>> 
 
 
 On Wed, Mar 8, 2017 at 12:01 AM, Mirage Abeysekara <
 mirage...@cse.mrt.ac.lk> wrote:
 
> Hi all,
> 
> I'm Mirage Abeysekara, a final year Computer Science and
 Engineering
> undergraduate from University of Moratuwa, Sri Lanka. I am
> interested
>> in
> contributing to the Apache Gossip by adding CRDT
>>> implementations.
> As a
> start, I implemented the sample grow-only counter
>> (GOSSIP-63)[1]
 by
> refering the Wikipedia[2]. I created a PR for git mirror[3].
>> It
> would
>> be
> great if you can give me some feedback regarding the G-Counter
> implementation.
> 
> [1] https://issues.apache.org/jira/browse/GOSSIP-63
> [2]
> https://en.wikipedia.org/wiki/Conflict-free_replicated_data_
> type#State-based_increment-only_counter
> [3] https://github.com/apache/incubator-gossip/pull/41
> 
> 
> Thanks.
> 
> *Mirage Abeysekara*
> Undergraduate
> Computer Science and Engineering
> University of Moratuwa
> Twitter: https://twitter.com/MiRAGECreator
> GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
> 
 
 Hello Mirage,
 
 Thank you for the addition. Welcome! I have already done a
>> first
 pass
 review for you on the g-counter work.
 
 We have set aside some of these tickets for Maxim (another GSOC
 contributor). Make sure you have done what you need to do on
>> your
 end
>> for
 GSOC. I also filled out a mentor request yesterday and we have
>> to
> find
>> a
 mentor for you.
 
 Thanks again,
 Edward
 
>>> 
>> 
> 
> 
> I didn’t understand what you meant. You mean all the CRDT tickets
>> under
> GSoC are assigned for someone or ticket that I tried to fix?
> 
> (You already started on the gcounter ticket and are doing great work
 there
> so we should finish that.)
> 
> Yes, the tickets under the CRDT umbrella are part of someone
> else's proposal for GSOC. It would be bes

Re: [Discuss] rename Apache Gossip to Apache Consensus

[P. Taylor Goetz]

Before going though the pain of a rename, I would suggest checking with 
trademarks@ to make sure the name “Apache Consensus” is suitable (i.e. a 
PODLINGNAMESEARCH JIRA would be approved).

You don’t want to rename, only to have to rename again.

-Taylor

> On Feb 22, 2017, at 10:31 AM, Edward Capriolo  wrote:
> 
> I am sure the infra team with love this idea :):
> 
> Thinking about the direction of Gossip. This is currently the message on
> our front page:
> 
> Apache Gossip
> 
> Apache Gossip™ is a system to form peer-to-peer networks using the gossip
> protocol.
> 
> 
> Thinking about the bigger picture... We are looking to add SWIM, we are
> looking to add CRDT. In the future we might have some type of leader
> election, or multicast based cluster membership.
> 
> I am borrowing a notion that Gary brought up in the early days of the
> proposal with the term "toolkit". Here is my new idea:
> 
> Apache Consensus
> 
> Apache Consensus is a distributed services toolkit that includes clustering
> technology like peer-to-peer membership services like gossip and data
> primitives like distributed CRDT data types bla bla.
> 
> What does everyone think? This is no immediate need here, but I think the
> re-brand is more inline with there we are headed and more interesting to
> attract development. Comments and other suggestions are welcome.

Re: Post-0.1.1 release actions

[P. Taylor Goetz]

Edward,

The staging repository in nexus is ready, all you have to do is click on the 
Release button for 1002, and Drop the earlier rcs.

-Taylor


> On Feb 3, 2017, at 4:03 PM, Edward Capriolo  wrote:
> 
> On Fri, Feb 3, 2017 at 3:36 PM, Josh Elser  wrote:
> 
>> Hi again,
>> 
>> Just your friendly mentor pestering to get the announcement for 0.1.1 done
>> :)
>> 
>> I've taken the liberty of updating the website:
>> https://github.com/apache/incubator-gossip/pull/30
>> 
>> I noticed that the artifacts were not promoted via Nexus to be mirror to
>> Maven Central. This needs to be done before we merge in these site changes.
>> I *think* I have the ability to do this if it comes to it. Normally the
>> release manager would do it (Edward).
>> 
>> Anyone have a moment to take a glance before I push?
>> 
>> -  Josh
>> 
> 
> 
> Josh,
> 
> The page looks good. Thank you for taking the time to update it. You can
> feel free to merge and push.
> 
> The documents in apache land which suggested doing this in our pom.
> 
> 
> 
> org.apache.maven.plugins
> 
> maven-release-plugin
>2.5.1
>
> 
> false
> 
> true
> 
> true
> 
> 
> distribution
> 
> clean install
>
>
> 
> Outside of apache I simply run' mvn release:clean release:prepare
> release:perform' and the mvn command does this. I am unsure as to what I
> need to do in this case. Is there a guide/do you know?

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

[P. Taylor Goetz]

Edward,

The IPMC vote period for this release has expired and there enough positive 
votes for it to pass. Can you close out the IPMC vote thread (i.e. "[RESULT] 
[VOTE]”) and proceed with releasing the associated artifacts, making downloads 
available, etc.?


-Taylor



> *On Jan 10, 2017, at 11:56 AM, Edward Capriolo  wrote:
> 
> The vote for gossip-0.1.1-incubating (RC2) has passed!
> 
> The votes were:
> 
> Josh Elser +1
> P. Taylor Goetz +1
> Gary Dusbabek +1
> Chandresh Pancholi +1
> Edward Capriolo +1
> 
> The vote thread is here:
> https://lists.apache.org/thread.html/86bf41b491a575c4751c1191f8f9d8ee2d17bedeac4bdef582ba5f03@%3Cdev.gossip.apache.org%3E
> 
> I will forward forward onto the incubator PMC for a vote shortly.

Re: Board report

[P. Taylor Goetz]

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  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  wrote:
> 
>> 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

[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: [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...

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

[P. Taylor Goetz]

Josh is correct that there is some wiggle room on this specific issue (json.org 
license). The wiggle room is that existing projects have a grace period for 
removing the json.org dependency, with the deadline I think being June 2017.

Since Gossip has yet to make a release, I would lean toward removing it. It 
would be a good demonstration to the IPMC of the podling taking efforts to 
comply with license policy.

> On Jan 3, 2017, at 4:54 PM, Gary Dusbabek  wrote:
> 
> On Tue, Jan 3, 2017 at 10:45 AM, Josh Elser  wrote:
> 
>> -1 due to a dependency on a project with a category-X license [1].
>> 
> 
> Wait. So you're saying that a transitive category-X licensed dependency is
> verboten even when we do not include the binary or the source?
> 

The litmus test I use is “Can the software be used without the category-X 
licensed dependency?”

If the answer is “no” then it is verboten. 

-Taylor

Re: https://issues.apache.org/jira/browse/GOSSIP-22 and failure detector

[P. Taylor Goetz]

There's not a lot of code there. Could it be reimplemented in gossip without 
infringing on any copyrights?

-Taylor

> On Dec 1, 2016, at 6:21 PM, Edward Capriolo  wrote:
> 
> I reached out to the initial author of the failure library to see if they
> would consider contributing it and I. I have not heard back.
> 
> The library itself is comprised of two functions, with no unit testing, and
> those functions lean heavily on commons-math. I think the signatures and
> the return types are not setup in a way that is natural for us to leverage.
> I think it is best we simply write the code to execute the failure detector
> logic ourselves.  We can make with a method signature we want and provide
> our own direct testing.
> 
> If anyone sees an alternative library let me know. Remember the algorithm
> itself is essentially a one-liner on top of common-math parts.
> 
> Thanks,
> Edward
> 
> On Thu, Nov 17, 2016 at 1:49 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
> 
>> https://github.com/apache/incubator-gossip/compare/
>> master...edwardcapriolo:GOSSIP-22?expand=1
>> Try the whole URL.
>> 
>> Thanks
>> 
>> On Thu, Nov 17, 2016 at 11:15 PM, Sandeep More 
>> wrote:
>> 
>>> Hello Edward,
>>> 
>>> Sorry for jumping in late, I tried to look at the URL you gave, it says
>>> "There isn’t anything to compare."
>>> 
>>> BTW https://github.com/arosien/failure looks great !
>>> 
>>> Best,
>>> Sandeep
>>> 
>>> 
>>> On Thu, Nov 17, 2016 at 11:52 AM, Edward Capriolo >> 
>>> wrote:
>>> 
 If someone gets a chance please review. It turned out to be a little
>>> easier
 then i thought:
 
 https://github.com/apache/incubator-gossip/compare/
>>> master...edwardcapriolo
 :
 GOSSIP-22?expand=1
 
 Leveraging the code here:
 
 https://github.com/arosien/failure
 
 I attempted to contact the author of failure (ASF V2) to see if he
>> wants
>>> to
 contribute the code. (not in maven) We have other options like fork and
 package etc.
 
 Lets hold off the merge of this until after the release.
 
 Thanks,
 Edward
 
 On Tue, Nov 15, 2016 at 10:42 PM, chandresh pancholi <
 chandreshpancholi...@gmail.com> wrote:
 
> I will also look into it.
> 
> On Wed, Nov 16, 2016 at 5:53 AM, Edward Capriolo <
>>> edlinuxg...@gmail.com>
> wrote:
> 
>> This seems interesting and low bar to entry:
>> 
>> https://github.com/arosien/failure
>> 
>> On Tue, Nov 15, 2016 at 4:01 PM, Edward Capriolo <
 edlinuxg...@gmail.com>
>> wrote:
>> 
>>> I was doing some load testing and I found the the current gating
 factor
>>> for max instances running in the same JVM is limited by the JMX
>>> based
>>> notification system the failure detector uses.
>>> 
>>> Currently a cluster of N requires N * (N-1) JMX notification
 threads. I
>>> started attempting to remove this limit without going into
>> building
 the
>>> accrual failure detector (22) but there were some nuanced bugs
>> and
>>> I
>> backed
>>> off because it did not seem worth the change.
>>> 
>>> If anyone has an literature to contribute about building a
>>> consensus
>> based
>>> failure detector please discuss. Once we cut this release that is
> likely
>>> were I will spent my attention.
>>> 
>>> Thanks,
>>> Edward
>>> 
>> 
> 
> 
> 
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660
> 
 
>>> 
>> 
>> 
>> 
>> --
>> Chandresh Pancholi
>> Senior Software Engineer
>> Flipkart.com
>> Email-id:chandresh.panch...@flipkart.com
>> Contact:08951803660
>> 

Re: One session on Gossip codebase

[P. Taylor Goetz]

When scheduling any “live” meeting, it would be good to poll the dev@ mailing 
list for timezones and schedule accordingly to maximize potential 
participation. I would also suggest announcing any meeting at least 72 hours 
before it takes place.

And when holding any off-list meetings, its important to bring any discussion 
items back to the dev@ list. Since this is just a code walkthrough I’m not 
concerned, but something to keep in mind.

-Taylor

> On Nov 17, 2016, at 1:50 PM, chandresh pancholi 
>  wrote:
> 
> Once we have the session i will create on boarding document for new
> contributors.
> 
> On Fri, Nov 18, 2016 at 12:15 AM, Edward Capriolo 
> wrote:
> 
>> That sounds like a good idea. Since we launched I have touched enough parts
>> of the code-base that I have a solid understanding of the majority of
>> things.  At minimum I can put together a power point. Or a screen share
>> walk through.
>> 
>> Ill start on that soon.
>> 
>> 
>> On Thu, Nov 17, 2016 at 12:42 PM, chandresh pancholi <
>> chandreshpancholi...@gmail.com> wrote:
>> 
>>> Hi,
>>> 
>>> We are looking forward to our first release. It would be great if we have
>>> one codebase session where Ed can walk us through.
>>> 
>>> We can record the session which would help new contributors in ramping
>> up.
>>> 
>>> 
>>> --
>>> Chandresh Pancholi
>>> Senior Software Engineer
>>> Flipkart.com
>>> Email-id:chandresh.panch...@flipkart.com
>>> Contact:08951803660
>>> 
>> 
> 
> 
> 
> -- 
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

> 
> 2) It looks like you have no signatures on your GPG key. This essentially 
> means that there is no weight on the validity of your key actually being 
> yours'. I'm fuzzy as to whether or not this is a blocker, but it would 
> definitely be a good thing to make happen. I've participated in a "virtual 
> key-signing party" with Calcite which worked out pretty well. Not in the 
> traditional spirit for sure, but it was better than nothing.

Having the release manager’s key signed into the web of trust is not strictly 
necessary for a release, though I strongly recommend it.

> 
> 
> 3) Need to add your pubkey to 
> https://dist.apache.org/repos/dist/release/incubator/gossip/KEYS (presently 
> doesn't exist). Feel free to look at another project/podling for an example. 
> This lets people easily `curl https://dist.a.o./.../KEYS | gpg --import` or 
> similar from the trusted ASF location.

I just initialized that file with my public key. All project members should add 
theirs as well.

> 
> 4) LICENSE/NOTICE both look standard. I forget the origins of Gossip, if 
> anything _should_ be included in the NOTICE file. Are there relevant 
> copyright notices which should be preserved from the pre-Apache days?

LICENSE/NOTICE look good. I did a fairly thorough vetting of the code prior to 
incubation, and didn’t find anything that would affect L/N.

-Taylor

> 
> Overall, looks pretty good though!
> 
> Josh Elser wrote:
>> For the promotion to Central, this can happen after the Gossip PPMC and
>> IPMC votes both pass. When you "promote" the repository, it will be
>> automatically mirrored to Central for you.
>> 
>> The only manual steps will be updating the SVN dist.a.o repo.
>> 
>> P. Taylor Goetz wrote:
>>> The official release needs to be a source code archive. Binaries are
>>> optional.
>>> 
>>> The Apache parent Pom should take care of everything if you are only
>>> packaging as a library.
>>> 
>>> -Taylor
>>> 
>>>> On Nov 17, 2016, at 5:32 PM, Edward Capriolo
>>>> wrote:
>>>> 
>>>>> On Thu, Nov 17, 2016 at 4:27 PM, Josh Elser
>>>>> wrote:
>>>>> 
>>>>> Fantastic!
>>>>> 
>>>>> To be clear, I'll take a look tonight at https://repository.apache.org/
>>>>> content/repositories/orgapachegossip-1000/org/apache/gossip/
>>>>> gossip/0.1.0-incubating/gossip-0.1.0-incubating-source-release.zip
>>>>> (assuming that is the official release artifact).
>>>>> 
>>>>> I assume that you also intend to publish the binary jar to Maven
>>>>> Central
>>>>> as well?
>>>>> 
>>>>> Edward Capriolo wrote:
>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> I have closed the repository.
>>>>>> 
>>>>>> https://repository.apache.org/content/repositories/orgapachegossip-1000/
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Thu, Nov 17, 2016 at 12:30 PM, Josh Elser
>>>>>> wrote:
>>>>>> 
>>>>>> Sure, happy to do that before an official VOTE thread!
>>>>>>> Looks like you haven't closed the staging repository yet. This is
>>>>>>> important for a few reasons.
>>>>>>> 
>>>>>>> * Closing the repository will trigger a number of automated release
>>>>>>> checks
>>>>>>> (notably around checksums and crypto signatures)
>>>>>>> * Makes the staging repository immutable (you can presently
>>>>>>> add/remove
>>>>>>> files)
>>>>>>> * Provides a nice URL to pass around :)
>>>>>>> 
>>>>>>> Can you log into https://repository.apache.org with your ASF creds,
>>>>>>> click
>>>>>>> on "Staging Repositories", find the "orgapachegossip-1000"
>>>>>>> repository,
>>>>>>> click the checkbox and then the "Close" button. This will trigger the
>>>>>>> aforementioned checks and, upon successful close, will give you a URL
>>>>>>> under
>>>>>>> the Summary tab.
>>>>>>> 
>>>>>>> LMK if you get stuck
>>>>>>> 
>>>>>>> Edward Capriolo wrote:
>>>>>>> 
>>>>&

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

The official release needs to be a source code archive. Binaries are optional.

The Apache parent Pom should take care of everything if you are only packaging 
as a library.

-Taylor

> On Nov 17, 2016, at 5:32 PM, Edward Capriolo  wrote:
> 
>> On Thu, Nov 17, 2016 at 4:27 PM, Josh Elser  wrote:
>> 
>> Fantastic!
>> 
>> To be clear, I'll take a look tonight at https://repository.apache.org/
>> content/repositories/orgapachegossip-1000/org/apache/gossip/
>> gossip/0.1.0-incubating/gossip-0.1.0-incubating-source-release.zip
>> (assuming that is the official release artifact).
>> 
>> I assume that you also intend to publish the binary jar to Maven Central
>> as well?
>> 
>> Edward Capriolo wrote:
>> 
>>> Thanks,
>>> 
>>> I have closed the repository.
>>> 
>>> https://repository.apache.org/content/repositories/orgapachegossip-1000/
>>> 
>>> 
>>> On Thu, Nov 17, 2016 at 12:30 PM, Josh Elser
>>> wrote:
>>> 
>>> Sure, happy to do that before an official VOTE thread!
>>>> 
>>>> Looks like you haven't closed the staging repository yet. This is
>>>> important for a few reasons.
>>>> 
>>>> * Closing the repository will trigger a number of automated release
>>>> checks
>>>> (notably around checksums and crypto signatures)
>>>> * Makes the staging repository immutable (you can presently add/remove
>>>> files)
>>>> * Provides a nice URL to pass around :)
>>>> 
>>>> Can you log into https://repository.apache.org with your ASF creds,
>>>> click
>>>> on "Staging Repositories", find the "orgapachegossip-1000" repository,
>>>> click the checkbox and then the "Close" button. This will trigger the
>>>> aforementioned checks and, upon successful close, will give you a URL
>>>> under
>>>> the Summary tab.
>>>> 
>>>> LMK if you get stuck
>>>> 
>>>> Edward Capriolo wrote:
>>>> 
>>>> Great infra solved that issue!
>>>>> 
>>>>> [INFO] Uploaded:
>>>>> https://repository.apache.org/service/local/staging/deploy/m
>>>>> aven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.
>>>>> 0-incubating-sources.jar.asc
>>>>> (836 B at 2.7 KB/sec)
>>>>> [INFO] Uploading:
>>>>> https://repository.apache.org/service/local/staging/deploy/m
>>>>> aven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.
>>>>> 0-incubating-javadoc.jar.asc
>>>>> [INFO] 836/836 B
>>>>> [INFO]
>>>>> [INFO] Uploaded:
>>>>> https://repository.apache.org/service/local/staging/deploy/m
>>>>> aven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.
>>>>> 0-incubating-javadoc.jar.asc
>>>>> (836 B at 2.6 KB/sec)
>>>>> [INFO] [INFO]
>>>>> 
>>>>> 
>>>>> [INFO] [INFO] BUILD SUCCESS
>>>>> [INFO] [INFO]
>>>>> 
>>>>> 
>>>>> 
>>>>> We have the artifacts deployed to staging now.
>>>>> 
>>>>> So the "tag" will not be pushed by the release
>>>>> https://github.com/apache/incubator-gossip/compare/master...
>>>>> edwardcapriolo:master.
>>>>> And I will have to push it manually.
>>>>> 
>>>>> Does anyone want to review the artifacts produced?
>>>>> 
>>>>> Thanks,
>>>>> Edward
>>>>> 
>>>>> On Mon, Nov 14, 2016 at 10:04 AM, Edward Capriolo>>>>> 
>>>>> wrote:
>>>>> 
>>>>> I created https://issues.apache.org/jira/browse/INFRA-12911
>>>>> 
>>>>>> On Wed, Nov 9, 2016 at 5:14 PM, P. Taylor Goetz
>>>>>> wrote:
>>>>>> 
>>>>>> I just tried and got the same error. Then I looked in the INFRA JIRA
>>>>>> and
>>>>>> 
>>>>>>> saw that we never requested Nexus access for the project.
>>>>>>> 
>>>>>>> Edward, are you comfortable doing that, or would you rather a mentor
>>>>>>> take
>>>>>>> care o

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

I just tried and got the same error. Then I looked in the INFRA JIRA and saw 
that we never requested Nexus access for the project.

Edward, are you comfortable doing that, or would you rather a mentor take care 
of it?

-Taylor

> On Nov 9, 2016, at 4:01 PM, Edward Capriolo  wrote:
> 
> Thanks.
> 
> I have been running with:
> 
> mvn  release:perform -Darguments='-Dmaven.test.skip=true'
> 
> The tests are a bit flaky as something is not shutting down consistently. I
> will look into that tonight.
> 
> On Wed, Nov 9, 2016 at 3:33 PM, Josh Elser  wrote:
> 
>> Let me know if you need help. I can try to find some time in the evenings
>> to poke around, too.
>> 
>> Short answer to your question, Edward: `mvn release:prepare
>> release:perform` should stage a Maven repository on repository.a.o for you.
>> Shouldn't have to upload anything there by hand.
>> 
>> P. Taylor Goetz wrote:
>> 
>>> I’ll see if I can run the release procedure. I’ve been able to release
>>> other ASF projects.
>>> 
>>> -Taylor
>>> 
>>> On Nov 9, 2016, at 2:46 PM, Edward Capriolo
>>>> wrote:
>>>> 
>>>> Update;
>>>> 
>>>> I have ran mvn:release prepare which has produced this "unmerged tag"
>>>> 
>>>> https://github.com/apache/incubator-gossip/compare/master...
>>>> edwardcapriolo:master<https://github.com/apache/incubator-
>>>> gossip/compare/master...edwardcapriolo:master>
>>>> 
>>>> I have verified that signed artifacts are being released.
>>>> My keys are uploaded here:
>>>> 
>>>> http://people.apache.org/~ecapriolo/<http://people.apache.
>>>> org/~ecapriolo/>
>>>> 
>>>> mvn release:perform is not working
>>>> 
>>>> [INFO] Uploading: https://repository.apache.org/
>>>> service/local/staging/deploy/maven2/org/apache/gossip/gossip
>>>> /0.1.0-incubating/gossip-0.1.0-incubating.pom>>> repository.apache.org/service/local/staging/deploy/maven2/
>>>> org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.0-incubating.pom>
>>>> [INFO] 4/10 KB
>>>> [INFO] 8/10 KB
>>>> [INFO] 10/10 KB
>>>> [INFO]
>>>> [INFO] [INFO] --
>>>> --
>>>> [INFO] [INFO] BUILD FAILURE
>>>> [INFO] [INFO] --
>>>> --
>>>> [INFO] [INFO] Total time: 19.973s
>>>> [INFO] [INFO] Finished at: Wed Nov 09 14:31:25 EST 2016
>>>> [INFO] [INFO] Final Memory: 27M/397M
>>>> [INFO] [INFO] --
>>>> --
>>>> [INFO] [WARNING] The requested profile "distribution" could not be
>>>> activated because it does not exist.
>>>> [INFO] [ERROR] Failed to execute goal 
>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>>> (default-deploy) on project gossip: Failed to deploy artifacts: Could not
>>>> transfer artifact org.apache.gossip:gossip:jar:0.1.0-incubating from/to
>>>> apache.releases.https (https://repository.apache.org
>>>> /service/local/staging/deploy/maven2<https://repository.
>>>> apache.org/service/local/staging/deploy/maven2>): Failed to transfer
>>>> file: https://repository.apache.org/service/local/staging/deploy/m
>>>> aven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.
>>>> 0-incubating.jar<https://repository.apache.org/service/
>>>> local/staging/deploy/maven2/org/apache/gossip/gossip/0.1.
>>>> 0-incubating/gossip-0.1.0-incubating.jar>. Return code is: 400 ->
>>>> [Help 1]
>>>> [INFO] [ERROR]
>>>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
>>>> with the -e switch.
>>>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
>>>> logging.
>>>> [INFO] [ERROR]
>>>> [INFO] [ERROR] For more information about the errors and possible
>>>> solutions, please read the following articles:
>>>> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/conflu
>>>> ence/display/MAVEN/MojoExecutionException<http://cwiki.
>>>> apache.org/confluence/display/MAVEN/MojoExecutionException>
>>>> 
>>>> I am poking around on http://repository.apache.org>>> ttp://reposit

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

I’ll see if I can run the release procedure. I’ve been able to release other 
ASF projects.

-Taylor

> On Nov 9, 2016, at 2:46 PM, Edward Capriolo  wrote:
> 
> Update;
> 
> I have ran mvn:release prepare which has produced this "unmerged tag"
> 
> https://github.com/apache/incubator-gossip/compare/master...edwardcapriolo:master
>  
> <https://github.com/apache/incubator-gossip/compare/master...edwardcapriolo:master>
> 
> I have verified that signed artifacts are being released.
> My keys are uploaded here:
> 
> http://people.apache.org/~ecapriolo/ <http://people.apache.org/~ecapriolo/>
> 
> mvn release:perform is not working
> 
> [INFO] Uploading: 
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.0-incubating.pom
>  
> <https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.0-incubating.pom>
> [INFO] 4/10 KB
> [INFO] 8/10 KB   
> [INFO] 10/10 KB   
> [INFO]
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 19.973s
> [INFO] [INFO] Finished at: Wed Nov 09 14:31:25 EST 2016
> [INFO] [INFO] Final Memory: 27M/397M
> [INFO] [INFO] 
> 
> [INFO] [WARNING] The requested profile "distribution" could not be activated 
> because it does not exist.
> [INFO] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
> project gossip: Failed to deploy artifacts: Could not transfer artifact 
> org.apache.gossip:gossip:jar:0.1.0-incubating from/to apache.releases.https 
> (https://repository.apache.org/service/local/staging/deploy/maven2 
> <https://repository.apache.org/service/local/staging/deploy/maven2>): Failed 
> to transfer file: 
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.0-incubating.jar
>  
> <https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/gossip/gossip/0.1.0-incubating/gossip-0.1.0-incubating.jar>.
>  Return code is: 400 -> [Help 1]
> [INFO] [ERROR] 
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with 
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR] 
> [INFO] [ERROR] For more information about the errors and possible solutions, 
> please read the following articles:
> [INFO] [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 
> <http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>
> 
> I am poking around on http://repository.apache.org 
> <http://repository.apache.org/> attempting to upload the artifacts directly 
> (see attached picture)
> 
> I am not sure what the next step here is. is mvn release supposed to work out 
> of the box (I have my password in the settings.xml file)
> 
> Or are the next steps manual?
> 
> Thanks,
> Edward
> 
> On Thu, Oct 27, 2016 at 2:07 PM, P. Taylor Goetz  <mailto:ptgo...@gmail.com>> wrote:
> Done.
> 
> -Taylor
> 
> > On Oct 27, 2016, at 11:58 AM, P. Taylor Goetz  > <mailto:ptgo...@gmail.com>> wrote:
> >
> > I’ll take care of it.
> >
> > -Taylor
> >
> >> On Oct 27, 2016, at 11:43 AM, Edward Capriolo  >> <mailto:edlinuxg...@gmail.com>> wrote:
> >>
> >> The reply in the ticket is:
> >>
> >> As you are a podling, please have someone from the IPMC create the dist
> >> directories you need.
> >>
> >>
> >>
> >> On Thu, Oct 27, 2016 at 10:32 AM, Edward Capriolo  >> <mailto:edlinuxg...@gmail.com>>
> >> wrote:
> >>
> >>> I filed a ticket to cover both:
> >>>
> >>> https://issues.apache.org/jira/browse/INFRA-12833 
> >>> <https://issues.apache.org/jira/browse/INFRA-12833>
> >>>
> >>> I think this is the last thing we need.
> >>>
> >>> Thanks,
> >>> Edward
> >>>
> >>> On Sun, Oct 9, 2016 at 11:50 PM, Josh Elser  >>> <mailto:els...@apache.org>> wrote:
> >>>
> >>>> Create a JIRA issue asking INFRA to create the SVN directories:
> >>>>
> >>>> https://dist.apache.org/repos/dist/release/in

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

Done.

-Taylor

> On Oct 27, 2016, at 11:58 AM, P. Taylor Goetz  wrote:
> 
> I’ll take care of it.
> 
> -Taylor
> 
>> On Oct 27, 2016, at 11:43 AM, Edward Capriolo  wrote:
>> 
>> The reply in the ticket is:
>> 
>> As you are a podling, please have someone from the IPMC create the dist
>> directories you need.
>> 
>> 
>> 
>> On Thu, Oct 27, 2016 at 10:32 AM, Edward Capriolo 
>> wrote:
>> 
>>> I filed a ticket to cover both:
>>> 
>>> https://issues.apache.org/jira/browse/INFRA-12833
>>> 
>>> I think this is the last thing we need.
>>> 
>>> Thanks,
>>> Edward
>>> 
>>> On Sun, Oct 9, 2016 at 11:50 PM, Josh Elser  wrote:
>>> 
>>>> Create a JIRA issue asking INFRA to create the SVN directories:
>>>> 
>>>> https://dist.apache.org/repos/dist/release/incubator/gossip
>>>> https://dist.apache.org/repos/dist/dev/incubator/gossip
>>>> 
>>>> dist/dev is a good location to stage RCs. Beware that items placed in
>>>> dist/release are automatically mirror'ed out. This should only contain
>>>> artifacts that have been approved via vote.
>>>> 
>>>> Check the permissions on your tilde-space. Not sure why this wouldn't
>>>> automatically happen.
>>>> 
>>>> Edward Capriolo wrote:
>>>> 
>>>>> I have generated a key for signing following the instructions here:
>>>>> http://www.apache.org/dev/release-signing.html
>>>>> 
>>>>> I have created a pgp key with the requested strength.
>>>>> http://keys.gnupg.net/pks/lookup?op=get&search=0x843E5702C878C988
>>>>> 
>>>>> I have created a public_html folder on people.apache.org, but I am not
>>>>> seeing the content. http://people.apache.org/~ecapriolo.
>>>>> 
>>>>> There are some steps that suggest I should put keys here:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/release/incubator-gossip
>>>>> 
>>>>> I am not quite sure how to arrange that access.
>>>>> 
>>>>> P.Taylor any hints?
>>>>> 
>>>>> On Fri, Oct 7, 2016 at 3:47 PM, Edward Capriolo
>>>>> wrote:
>>>>> 
>>>>> I created:
>>>>>> https://issues.apache.org/jira/browse/GOSSIP-27
>>>>>> 
>>>>>> Some of the items I have to handle but others are free to take on /send
>>>>>> PR
>>>>>> for the remaining.
>>>>>> 
>>>>>> On Fri, Oct 7, 2016 at 3:43 PM, chandresh pancholi<
>>>>>> chandreshpancholi...@gmail.com>  wrote:
>>>>>> 
>>>>>> Sure Ed.
>>>>>>> Can you create the ticket?
>>>>>>> 
>>>>>>> On Sat, Oct 8, 2016 at 1:07 AM, Edward Capriolo
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Good catch.
>>>>>>>> There are a few issues I see.
>>>>>>>> 
>>>>>>>> The first is the maven instructions at the bottom,
>>>>>>>> 
>>>>>>>> The second is that the build link is wrong. it should be
>>>>>>>> # Apache Gossip ![Build status](
>>>>>>>> https://api.travis-ci.org/edwardcapriolo/incubator-gossip.svg)
>>>>>>>> 
>>>>>>>> The third is that some of the code examples are slightly dated.
>>>>>>>> 
>>>>>>>> Lets open up a ticket to track this and the things p.taylor mentions.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Fri, Oct 7, 2016 at 3:25 PM, chandresh pancholi<
>>>>>>>> chandreshpancholi...@gmail.com>  wrote:
>>>>>>>> 
>>>>>>>> We need to change same in project's readme.md.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Sat, Oct 8, 2016 at 12:40 AM, Edward Capriolo<
>>>>>>>>> 
>>>>>>>> edlinuxg...@gmail.com>
>>>>>>> 
>>>>>>>> wrote:
>>>>>>>>&

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

I’ll take care of it.

-Taylor

> On Oct 27, 2016, at 11:43 AM, Edward Capriolo  wrote:
> 
> The reply in the ticket is:
> 
> As you are a podling, please have someone from the IPMC create the dist
> directories you need.
> 
> 
> 
> On Thu, Oct 27, 2016 at 10:32 AM, Edward Capriolo 
> wrote:
> 
>> I filed a ticket to cover both:
>> 
>> https://issues.apache.org/jira/browse/INFRA-12833
>> 
>> I think this is the last thing we need.
>> 
>> Thanks,
>> Edward
>> 
>> On Sun, Oct 9, 2016 at 11:50 PM, Josh Elser  wrote:
>> 
>>> Create a JIRA issue asking INFRA to create the SVN directories:
>>> 
>>> https://dist.apache.org/repos/dist/release/incubator/gossip
>>> https://dist.apache.org/repos/dist/dev/incubator/gossip
>>> 
>>> dist/dev is a good location to stage RCs. Beware that items placed in
>>> dist/release are automatically mirror'ed out. This should only contain
>>> artifacts that have been approved via vote.
>>> 
>>> Check the permissions on your tilde-space. Not sure why this wouldn't
>>> automatically happen.
>>> 
>>> Edward Capriolo wrote:
>>> 
>>>> I have generated a key for signing following the instructions here:
>>>> http://www.apache.org/dev/release-signing.html
>>>> 
>>>> I have created a pgp key with the requested strength.
>>>> http://keys.gnupg.net/pks/lookup?op=get&search=0x843E5702C878C988
>>>> 
>>>> I have created a public_html folder on people.apache.org, but I am not
>>>> seeing the content. http://people.apache.org/~ecapriolo.
>>>> 
>>>> There are some steps that suggest I should put keys here:
>>>> 
>>>> https://dist.apache.org/repos/dist/release/incubator-gossip
>>>> 
>>>> I am not quite sure how to arrange that access.
>>>> 
>>>> P.Taylor any hints?
>>>> 
>>>> On Fri, Oct 7, 2016 at 3:47 PM, Edward Capriolo
>>>> wrote:
>>>> 
>>>> I created:
>>>>> https://issues.apache.org/jira/browse/GOSSIP-27
>>>>> 
>>>>> Some of the items I have to handle but others are free to take on /send
>>>>> PR
>>>>> for the remaining.
>>>>> 
>>>>> On Fri, Oct 7, 2016 at 3:43 PM, chandresh pancholi<
>>>>> chandreshpancholi...@gmail.com>  wrote:
>>>>> 
>>>>> Sure Ed.
>>>>>> Can you create the ticket?
>>>>>> 
>>>>>> On Sat, Oct 8, 2016 at 1:07 AM, Edward Capriolo
>>>>>> wrote:
>>>>>> 
>>>>>> Good catch.
>>>>>>> There are a few issues I see.
>>>>>>> 
>>>>>>> The first is the maven instructions at the bottom,
>>>>>>> 
>>>>>>> The second is that the build link is wrong. it should be
>>>>>>> # Apache Gossip ![Build status](
>>>>>>> https://api.travis-ci.org/edwardcapriolo/incubator-gossip.svg)
>>>>>>> 
>>>>>>> The third is that some of the code examples are slightly dated.
>>>>>>> 
>>>>>>> Lets open up a ticket to track this and the things p.taylor mentions.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Fri, Oct 7, 2016 at 3:25 PM, chandresh pancholi<
>>>>>>> chandreshpancholi...@gmail.com>  wrote:
>>>>>>> 
>>>>>>> We need to change same in project's readme.md.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Sat, Oct 8, 2016 at 12:40 AM, Edward Capriolo<
>>>>>>>> 
>>>>>>> edlinuxg...@gmail.com>
>>>>>> 
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> You might be looking at the wrong project:
>>>>>>>>> 
>>>>>>>>> https://github.com/edwardcapriolo/incubator-gossip/blob/
>>>>>>>>> 
>>>>>>>> master/pom.xml
>>>>>> 
>>>>>>> 
>>>>>>>>>
>>>>>>>>> org.apache
>>>>>>>>> ap

Re: Quick review - Lots o threads

[P. Taylor Goetz]

Quick ASF github integration tip:

If you create the JIRA issue fist, then prefix the pull request title with the 
JIRA ID (e.g "GOSSIP-28: blah, blah" comments on that pull request will be 
synced to JIRA.

-Taylor
> On Oct 7, 2016, at 6:30 PM, Edward Capriolo  wrote:
> 
> I am playing with Apache Gossip to kick the tires before the release.
> 
> https://issues.apache.org/jira/browse/GOSSIP-28
> 
> I think it would make sense to get this in so we can play nice with peoples
> VMs. If someone has the time to +1 I can handle the merge. Would like to
> get in in place in the next day or two.
> 
> Thanks,
> Edward

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

I would change the groupId to org.apache.gossip. I’d have to check, but I think 
Nexus has rules in place that enforce that, so it’s probably best to just go 
ahead.

-Taylor

> On Oct 7, 2016, at 2:52 PM, chandresh pancholi 
>  wrote:
> 
> +1 for release.
> 
> Concern
> Right now groupId on github says io.teknek. Will it change to
> org.apache.gossip in first release?
> If it changes then we have to remove io.teknek from readme.md
> 
> Thanks
> 
> On Fri, Oct 7, 2016 at 11:55 PM, P. Taylor Goetz  wrote:
> 
>> The typical process is to have a DISCUSS thread before and official VOTE
>> thread, but I assume that was the intent here.
>> 
>> I’m +1 for moving forward with a release. Here are some links to some
>> light reading about the process [1][2].
>> 
>> A quick check of the gossip repo reveals the following that need to be
>> addressed before release:
>> 
>> - DISCLAIMER file needs to be added.
>> - NOTICE file needs to added (see [3] for the procedure)
>> - KEYS file needs to be created (see [4] for more light reading on signing
>> releases)
>> 
>> The release manager will also need an account on repository.apache.org (ASF’s
>> Nexus instance).
>> 
>> It would also be good, but not required, for the signing key to be linked
>> to the Apache web of trust.
>> 
>> Edward, can I assume you are going to be the release manager for the first
>> release?  If you need any help, feel free to ask.
>> 
>> -Taylor
>> 
>> [1] http://incubator.apache.org/guides/releasemanagement.html
>> [2] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>> [3] http://www.apache.org/legal/src-headers.html#notice
>> [4] http://www.apache.org/dev/release-signing.html
>> 
>> 
>> On Oct 7, 2016, at 3:26 AM, Edward Capriolo  wrote:
>> 
>> With the additions of:
>> https://issues.apache.org/jira/browse/GOSSIP-21
>> https://issues.apache.org/jira/browse/GOSSIP-26
>> 
>> Apache Gossip has the the ability to create peer to peer systems and share
>> user defined data between them. Those capabilities prompts me to call a
>> vote for the first release of Apache Gossip.
>> 
>> The current pom tag is 0.1.0-incubating so I think we should call the
>> release version 0.2.0-incubating.
>> 
>> My vote  +1 (binding).
>> 
>> Thank you,
>> Edward
>> 
>> (Thank you mentors for good nudging :)
>> 
>> 
>> 
> 
> 
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release Apache Gossip

[P. Taylor Goetz]

The typical process is to have a DISCUSS thread before and official VOTE 
thread, but I assume that was the intent here.

I’m +1 for moving forward with a release. Here are some links to some light 
reading about the process [1][2].

A quick check of the gossip repo reveals the following that need to be 
addressed before release:

- DISCLAIMER file needs to be added.
- NOTICE file needs to added (see [3] for the procedure)
- KEYS file needs to be created (see [4] for more light reading on signing 
releases)

The release manager will also need an account on repository.apache.org 
 (ASF’s Nexus instance).

It would also be good, but not required, for the signing key to be linked to 
the Apache web of trust.

Edward, can I assume you are going to be the release manager for the first 
release?  If you need any help, feel free to ask.

-Taylor

[1] http://incubator.apache.org/guides/releasemanagement.html 

[2] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases 

[3] http://www.apache.org/legal/src-headers.html#notice
[4] http://www.apache.org/dev/release-signing.html


> On Oct 7, 2016, at 3:26 AM, Edward Capriolo  wrote:
> 
> With the additions of:
> https://issues.apache.org/jira/browse/GOSSIP-21
> https://issues.apache.org/jira/browse/GOSSIP-26
> 
> Apache Gossip has the the ability to create peer to peer systems and share
> user defined data between them. Those capabilities prompts me to call a
> vote for the first release of Apache Gossip.
> 
> The current pom tag is 0.1.0-incubating so I think we should call the
> release version 0.2.0-incubating.
> 
> My vote  +1 (binding).
> 
> Thank you,
> Edward
> 
> (Thank you mentors for good nudging :)



signature.asc
Description: Message signed with OpenPGP using GPGMail

Is it time for a Gossip release?

[P. Taylor Goetz]

One of the more important tasks during incubation is making approved releases.

Any thoughts on working toward a first release?

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

[jira] [Commented] (GOSSIP-6) create initial website

[P. Taylor Goetz (JIRA)]

[ 
https://issues.apache.org/jira/browse/GOSSIP-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339652#comment-15339652
 ] 

P. Taylor Goetz commented on GOSSIP-6:
--

[~sreevaddi] We have gitpubsub setup for the website. There is an 'asf-site' 
branch that contains the content. We don't need to setup svn pubs for website 
content since we can do it all through git.

> create initial website
> --
>
> Key: GOSSIP-6
> URL: https://issues.apache.org/jira/browse/GOSSIP-6
> Project: Gossip
>  Issue Type: Task
>Reporter: Sree Vaddi
>  Labels: svn, website
>
> http://gossip.incubator.apache.org/



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

Re: 5 mail DLs total, i guess ?

[P. Taylor Goetz]

+1

-Taylor

> On Jun 20, 2016, at 9:05 AM, Edward Capriolo  wrote:
> 
> Incubator projects typically decide not to have a user. Following advice we
> did not create one.
> 
> With the traffic levels at this point I suggest we stuck with 2 dev and
> private.
> On Jun 20, 2016 3:08 AM, "Sree V"  wrote:
> 
> Hi Edward/Team,
> PMC member may take care of this, please.
> 
> Please create:
> us...@gossip.incubator.apache.org
> users-subscr...@gossip.incubator.apache.org
> users-unsubscr...@gossip.incubator.apache.org
> 
> iss...@gossip.incubator.apache.org
> issues-subscr...@gossip.incubator.apache.org
> issues-unsubscr...@gossip.incubator.apache.org
> 
> priv...@gossip.incubator.apache.org
> private-subscr...@gossip.incubator.apache.org
> private-unsubscr...@gossip.incubator.apache.org
> 
> Already exists:
> dev@gossip.incubator.apache.org
> comm...@gossip.incubator.apache.org
> 
> Please verify, if these exists and works:
> dev-unsubscr...@gossip.incubator.apache.org
> commits-unsubscr...@gossip.incubator.apache.org
> 
> Please create, mailing archives for all the five above, too.
> 
> 
> refer to:
> https://issues.apache.org/jira/browse/INFRA-12141
> 
> form:https://infra.apache.org/officers/mlreq
> 
> Thanking you.
> With Regards
> Sree

Re: gossip board report

[P. Taylor Goetz]

Thanks Sean.

I’ve signed off on the report as well.

Edward — can you send a request to general@incubator with your Incubator wiki 
username and request write access? Note that that wiki is separate from the 
confluence wiki.

-Taylor

> On Jun 3, 2016, at 2:08 PM, Sean Busbey  wrote:
> 
> Sorry, thought we got you the needed karma earlier this week.
> 
> I've added it now.
> 
> On Fri, Jun 3, 2016 at 12:59 PM, Edward Capriolo  
> wrote:
>> Sorry,
>> I have mentioned this before but every page is immutable to me. Can someone
>> with wiki access please add this for me.
>> 
>> On Fri, Jun 3, 2016 at 11:46 AM, Josh Elser  wrote:
>> 
>>> This really needs to be added to http://wiki.apache.org/incubator/June2016
>>> as soon as possible. The deadline for podlings has already passed.
>>> 
>>> Josh Elser wrote:
>>> 
 nit: s/this is out/this is our/
 
 otherwise, looks great. You have the karma to add it to the appropriate
 incubator wiki page (I'm guessing from the original proposal)?
 
 Edward Capriolo wrote:
 
> 
> 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. Facilitate discussions and build the protocol specification and
> implementation
> 3. Produce a usable release
> 
> 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?
> 
> The community is the same as when it started incubation a few weeks ago.
> 
> How has the project developed since the last report?
> 
> This is out first report. We have important the code from github. We
> are online. We have had good discussions on the dev list that have
> spawned a couple of tickets. One is in the review stage now. Taylor has
> been an enormous help.
> 
> Date of last release:
> 
> Never
> 
> When were the last committers or PMC members elected?
> 
> Never
> 
> Signed-off-by:
> 
> [X](Gossip) Edward Capriolo
> [ ](Gossip) Josh Elser
> [ ](Gossp)
> Shepherd/Mentor notes:
> 
 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: gossip board report

[P. Taylor Goetz]

I will ad it.

-Taylor

> On Jun 3, 2016, at 1:59 PM, Edward Capriolo  wrote:
> 
> Sorry,
> I have mentioned this before but every page is immutable to me. Can someone
> with wiki access please add this for me.
> 
>> On Fri, Jun 3, 2016 at 11:46 AM, Josh Elser  wrote:
>> 
>> This really needs to be added to http://wiki.apache.org/incubator/June2016
>> as soon as possible. The deadline for podlings has already passed.
>> 
>> Josh Elser wrote:
>> 
>>> nit: s/this is out/this is our/
>>> 
>>> otherwise, looks great. You have the karma to add it to the appropriate
>>> incubator wiki page (I'm guessing from the original proposal)?
>>> 
>>> Edward Capriolo wrote:
>>> 
 
 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. Facilitate discussions and build the protocol specification and
 implementation
 3. Produce a usable release
 
 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?
 
 The community is the same as when it started incubation a few weeks ago.
 
 How has the project developed since the last report?
 
 This is out first report. We have important the code from github. We
 are online. We have had good discussions on the dev list that have
 spawned a couple of tickets. One is in the review stage now. Taylor has
 been an enormous help.
 
 Date of last release:
 
 Never
 
 When were the last committers or PMC members elected?
 
 Never
 
 Signed-off-by:
 
 [X](Gossip) Edward Capriolo
 [ ](Gossip) Josh Elser
 [ ](Gossp)
 Shepherd/Mentor notes:
 
>>> 

Gossip Embedded

[P. Taylor Goetz]

One use case that shouldn't be overlooked is the embedded market.Think of low 
level devices discovering one another in a network of constrained devices.

It may be worth considering using byte arrays for gossip payloads, and 
potentially introducing a plugable parser or handler layer (at least in the 
current implementation).

I know for now our implementation is Java. But to support multiple languages we 
should be payload agnostic.

-Taylor

Re: Gossip Wiki + Git + Website

[P. Taylor Goetz]

Hi Edward, I wasn’t able to find your name in cwiki, can you double check?

We now have JIRA:

https://issues.apache.org/jira/browse/GOSSIP 
<https://issues.apache.org/jira/browse/GOSSIP>

I’ve made Edward and all mentors administrators.

I submitted a request for website creation with gitpubsub. The branch for the 
website is ‘asf-site’, and I put a placeholder html page in that branch.

I also submitted a request for GitHub mirroring and integration with JIRA. If a 
pull request is made with a JIRA ticket # in the title (e.g. “GOSSIP-XXX: “) 
github activity will be mirrored to the JIRA. I request TravisCI integration as 
well.

-Taylor


> On May 25, 2016, at 11:21 AM, Edward Capriolo  wrote:
> 
> My wiki username is edwardcapriolo.
> 
> git looks good.
> 
> Thank you for tracking all the status.
> 
> On Tue, May 24, 2016 at 2:33 PM, P. Taylor Goetz  wrote:
> 
>> We now have a confluence wiki:
>> 
>> https://cwiki.apache.org/confluence/display/GOSSIP
>> 
>> If you let me know what your wiki username is, I will give you permissions.
>> 
>> 
>> Git is also setup:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-gossip.git
>> 
>> It’s currently locked, pending verification, which I just did. Edward —
>> can you verify as well? It’s also not yet mirrored to github.
>> 
>> Once the lock is removed, we can create the ‘asf-site’ branch that will
>> host the website. and ask INFRA to start publishing.
>> 
>> JIRA setup is still pending.
>> 
>> Thanks everyone for your patience. I think INFRA is under heavy load right
>> now.
>> 
>> -Taylor
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Podling Report Reminder - June 2016

[P. Taylor Goetz]

Anyone want to take a crack at this?

I'm happy to help.

-Taylor

> On May 25, 2016, at 10:34 PM, johndam...@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

Gossip Wiki + Git + Website

[P. Taylor Goetz]

We now have a confluence wiki:

https://cwiki.apache.org/confluence/display/GOSSIP 


If you let me know what your wiki username is, I will give you permissions.


Git is also setup:

https://git-wip-us.apache.org/repos/asf?p=incubator-gossip.git 


It’s currently locked, pending verification, which I just did. Edward — can you 
verify as well? It’s also not yet mirrored to github.

Once the lock is removed, we can create the ‘asf-site’ branch that will host 
the website. and ask INFRA to start publishing.

JIRA setup is still pending.

Thanks everyone for your patience. I think INFRA is under heavy load right now.

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Gossip Project Bootstrap

[P. Taylor Goetz]

Music to my ears. :)

If there are no objections, tomorrow I'll ask infra to set this up.

-Taylor

> On May 18, 2016, at 5:32 PM, Edward Capriolo  wrote:
> 
> If I could pick I would say go with Git for everything possible, by SVN
> skills have sharply declined after years of not using it.
> 
>> On Wed, May 18, 2016 at 1:34 PM, P. Taylor Goetz  wrote:
>> 
>> Here’s the JIRA for INFRA:
>> https://issues.apache.org/jira/browse/INFRA-11909
>> 
>> Quick question:
>> 
>> For the project website, do we want to use subversion or git? The ASF
>> allows you to create a special branch in git (i.e. “gossip-site”)
>> containing the website content, similar to github pages. Do we want to go
>> with that?
>> 
>> Once we figure that out I’ll go ahead and request the website creation.
>> 
>> -Taylor
>> 

Re: Gossip Project Bootstrap

[P. Taylor Goetz]

Yes, it would mean we wouldn’t have to use svnpubsub (I’m not a fan). Just 
pushing changes to branch would publish the changes. It would also allow people 
to submit pull requests for website changes.

-Taylor

> On May 18, 2016, at 2:09 PM, Gary Dusbabek  wrote:
> 
> +1 for git branch. Does this mean that we don't have to use svnpubsub?
> 
> Gary.
> 
> On Wed, May 18, 2016 at 12:34 PM, P. Taylor Goetz  wrote:
> 
>> Here’s the JIRA for INFRA:
>> https://issues.apache.org/jira/browse/INFRA-11909
>> 
>> Quick question:
>> 
>> For the project website, do we want to use subversion or git? The ASF
>> allows you to create a special branch in git (i.e. “gossip-site”)
>> containing the website content, similar to github pages. Do we want to go
>> with that?
>> 
>> Once we figure that out I’ll go ahead and request the website creation.
>> 
>> -Taylor
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Gossip Project Bootstrap

[P. Taylor Goetz]

Here’s the JIRA for INFRA: https://issues.apache.org/jira/browse/INFRA-11909 


Quick question:

For the project website, do we want to use subversion or git? The ASF allows 
you to create a special branch in git (i.e. “gossip-site”) containing the 
website content, similar to github pages. Do we want to go with that?

Once we figure that out I’ll go ahead and request the website creation.

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail