[RESULT] [VOTE] Retire Gossip

[Josh Elser]

Re-sending with proper subject...

On 8/9/18 6:45 PM, Josh Elser wrote:

This vote passes with six +1's and one -1.

I plan to start a vote on general@incubator.

On 8/6/18 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

Re: [VOTE] Retire Gossip

[Josh Elser]

This vote passes with six +1's and one -1.

I plan to start a vote on general@incubator.

On 8/6/18 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

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

Thanks, Taylor. Just started a new thread for a dev-list VOTE.

On 8/6/18 12:05 PM, P. Taylor Goetz wrote:

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).

[VOTE] Retire Gossip

[Josh Elser]

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

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

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).

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

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  
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).
   

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

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).

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

I won't rehash the comments on the more frequent reporting and 
shepherding. I think they were appropriately answered already on 
general@incubator (sorry if the CC to this list was dropped).


I want to address the notion that mentors or other ASF members are here 
to build communities. We're not.


We're here to provide guardrails to try to build healthy communities. 
We're here to help with technical challenges in getting your software 
lifecycle up on ASF infrastructure. We're here to help with the legal 
challenges of software licensing and copyright. We're here to be human 
mentors for when there are questions about interpersonal issues or 
attracting new people.


We're not here to build the community for you.

At the end of the day, I haven't seen an email to this list that wasn't 
a podling report request in months. I actually stopped hounding Ed 
personally because it had become a regular thing. There is absolutely no 
shame in saying that Gossip is not ready for the ASF. I'd really 
encourage you all to take a step back and think about that. I honestly 
think moving to Github would make you all much happier, and, an eventual 
move to the Incubator again later, would be that much easier (knowing 
what goes into it).


On 7/5/18 1:00 PM, Edward Capriolo wrote:

The challenge with this process is Apache claims to be about "building
communities", but you do not have great tools to do that. A number of
apache projects are propped up by some for profit company who just pays
people to work on that thing all the time.

I asked for 3 months (normal reporting cycle) to re-evaluate and have a
legit chance at re-bootstrapping. I go to write up the report (which are
now suddenly due every month that no one discussed with me). The report due
July 4th a US holiday. I go to write the report find a convo in the
incubator about how people want to close up the podling because they can
not even wait to see if I actually get the report in or not.

Meanwhile the project had this "shepard" who never signed off a report and
his first interaction with the ML was to vote on shutting down the podling.
Great job "building communities".



On Thu, Jul 5, 2018 at 12:50 PM, Josh Elser  wrote:


Hey Ed,

I think taking Gossip back to Github is the right decision. The Incubator
is designed to support, long-running, low-activity projects like you
outline. The regular reports on progress become a time-sink because there
isn't the expected level of volume or participants.

The incubator works well when there is an established community of folks
who are active. Like you say, this otherwise becomes a burden on you (the
sole contributor, best as I can see), taking your time away from actually
producing software.

+1 from me

On 7/5/18 9:18 AM, Edward Capriolo wrote:


All,

It was a sizable effort moving everything Gossip into the incubator. Thank
you all for your help along the way. Recently activity has slowed down,
much of this falls on me.

My opinion is gossip would be much better off moving back to github and be
independently hosted (by me or someone else) I believe for the following
reasons:

Infrastructure:

AAA
I forgot my password and when I clicked the "FORGOT MY PASSWORD" link I
got
back a PGP email. No instructions in the email, lol city. I had to google
around ASFs site to try to figure out what to do. Try googling 'pgp lost
password' on apache's docs and figuring out what you need to do.

Releases:
The release process for most Java projects using maven 'mvn release:clean
&& mvn release:prepare && mvn release:perform". Hosting is free and sign
up
takes less then a day. Apache incubator wants to see releases as a sign of
health, yet the release process is involved. We have to do the maven
steps,
generate an email with the checksums of all critical files, post a vote on
the incubator list, release the artifacts to central, and copy them to an
svn directory.

That is a vote across 2 mailing lists. and all the maven steps, and other
manual steps, and that does not even count getting the website changed.
For
me what is a 5 minute thing turns into a days long process. The net result
is we have features in trunk not in the release because doing a release is
just a drag. No one is even half interested in taking on this process and
I
only did it because it is the only way.

Community:
Apache incubator is about building communities.
Mailing list
The mailing list is fairly opaque to me. I am sure there is some way to
figure out what the subscriber base is but I don't know it.

Jira
Jira is great tool but the implementation slows people down. New users
have
to sign up, and they are unable to assign themselves tickets until I
navigate into JIRA and add them to a group. With open source and
attracting
contributors it helps to be able to strike while the iron is hot. Having
users confused as to weather they can start on a task does not help with
that.

GIT
Apache has git 

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

I will point out that I've been pointing out the writing on the wall for 
months. This isn't some abrupt action.


On 7/5/18 1:00 PM, chandresh pancholi wrote:

Before moving it to GitHub, I would say let's give a chance.
I am moving out from current job and I have plenty of time to contribute
and promote gossip to forum in india.

Happy to know your thoughts.
-1 from me.

On Thu, Jul 5, 2018, 10:21 PM Josh Elser  wrote:


Hey Ed,

I think taking Gossip back to Github is the right decision. The
Incubator is designed to support, long-running, low-activity projects
like you outline. The regular reports on progress become a time-sink
because there isn't the expected level of volume or participants.

The incubator works well when there is an established community of folks
who are active. Like you say, this otherwise becomes a burden on you
(the sole contributor, best as I can see), taking your time away from
actually producing software.

+1 from me

On 7/5/18 9:18 AM, Edward Capriolo wrote:

All,

It was a sizable effort moving everything Gossip into the incubator.

Thank

you all for your help along the way. Recently activity has slowed down,
much of this falls on me.

My opinion is gossip would be much better off moving back to github and

be

independently hosted (by me or someone else) I believe for the following
reasons:

Infrastructure:

AAA
I forgot my password and when I clicked the "FORGOT MY PASSWORD" link I

got

back a PGP email. No instructions in the email, lol city. I had to google
around ASFs site to try to figure out what to do. Try googling 'pgp lost
password' on apache's docs and figuring out what you need to do.

Releases:
The release process for most Java projects using maven 'mvn release:clean
&& mvn release:prepare && mvn release:perform". Hosting is free and sign

up

takes less then a day. Apache incubator wants to see releases as a sign

of

health, yet the release process is involved. We have to do the maven

steps,

generate an email with the checksums of all critical files, post a vote

on

the incubator list, release the artifacts to central, and copy them to an
svn directory.

That is a vote across 2 mailing lists. and all the maven steps, and other
manual steps, and that does not even count getting the website changed.

For

me what is a 5 minute thing turns into a days long process. The net

result

is we have features in trunk not in the release because doing a release

is

just a drag. No one is even half interested in taking on this process

and I

only did it because it is the only way.

Community:
Apache incubator is about building communities.
Mailing list
The mailing list is fairly opaque to me. I am sure there is some way to
figure out what the subscriber base is but I don't know it.

Jira
Jira is great tool but the implementation slows people down. New users

have

to sign up, and they are unable to assign themselves tickets until I
navigate into JIRA and add them to a group. With open source and

attracting

contributors it helps to be able to strike while the iron is hot. Having
users confused as to weather they can start on a task does not help with
that.

GIT
Apache has git but not github is only a mirror. When I have to merge
peoples stuff I have to do it by hand with git commands. (No squash and
merge button)

Updating the site:
Another series of obscure svn commands, making simple things hard, (much
like the release process)

Reports
I get an 4-5 emails at different rates titled "Incubator Report Due" at
different rates. Only one of them is for this project. We were never

great

with reports. Almost all the info in the report could be automatically
generated. We missed a report, we got placed onto a report now do every
month category.

The last one was due yesterday, sorry I was enjoying a hotdog at a bbq, I
went to fill it out today and, saw yet another email chain on the

incubator

list about how Gossip should leave apache. The report is just another

huge

time suck, the time I spend doing it I could be doing an hour of code
review.

Even though some things are in the incubator 7 years, and some apache

TLPs

have no activity Gossip out of the incubator seems to be a constant thing
for some

So lets get out of here.

Re: [DISCUSS] Leave apache and the incubator

[Josh Elser]

Hey Ed,

I think taking Gossip back to Github is the right decision. The 
Incubator is designed to support, long-running, low-activity projects 
like you outline. The regular reports on progress become a time-sink 
because there isn't the expected level of volume or participants.


The incubator works well when there is an established community of folks 
who are active. Like you say, this otherwise becomes a burden on you 
(the sole contributor, best as I can see), taking your time away from 
actually producing software.


+1 from me

On 7/5/18 9:18 AM, Edward Capriolo wrote:

All,

It was a sizable effort moving everything Gossip into the incubator. Thank
you all for your help along the way. Recently activity has slowed down,
much of this falls on me.

My opinion is gossip would be much better off moving back to github and be
independently hosted (by me or someone else) I believe for the following
reasons:

Infrastructure:

AAA
I forgot my password and when I clicked the "FORGOT MY PASSWORD" link I got
back a PGP email. No instructions in the email, lol city. I had to google
around ASFs site to try to figure out what to do. Try googling 'pgp lost
password' on apache's docs and figuring out what you need to do.

Releases:
The release process for most Java projects using maven 'mvn release:clean
&& mvn release:prepare && mvn release:perform". Hosting is free and sign up
takes less then a day. Apache incubator wants to see releases as a sign of
health, yet the release process is involved. We have to do the maven steps,
generate an email with the checksums of all critical files, post a vote on
the incubator list, release the artifacts to central, and copy them to an
svn directory.

That is a vote across 2 mailing lists. and all the maven steps, and other
manual steps, and that does not even count getting the website changed. For
me what is a 5 minute thing turns into a days long process. The net result
is we have features in trunk not in the release because doing a release is
just a drag. No one is even half interested in taking on this process and I
only did it because it is the only way.

Community:
Apache incubator is about building communities.
Mailing list
The mailing list is fairly opaque to me. I am sure there is some way to
figure out what the subscriber base is but I don't know it.

Jira
Jira is great tool but the implementation slows people down. New users have
to sign up, and they are unable to assign themselves tickets until I
navigate into JIRA and add them to a group. With open source and attracting
contributors it helps to be able to strike while the iron is hot. Having
users confused as to weather they can start on a task does not help with
that.

GIT
Apache has git but not github is only a mirror. When I have to merge
peoples stuff I have to do it by hand with git commands. (No squash and
merge button)

Updating the site:
Another series of obscure svn commands, making simple things hard, (much
like the release process)

Reports
I get an 4-5 emails at different rates titled "Incubator Report Due" at
different rates. Only one of them is for this project. We were never great
with reports. Almost all the info in the report could be automatically
generated. We missed a report, we got placed onto a report now do every
month category.

The last one was due yesterday, sorry I was enjoying a hotdog at a bbq, I
went to fill it out today and, saw yet another email chain on the incubator
list about how Gossip should leave apache. The report is just another huge
time suck, the time I spend doing it I could be doing an hour of code
review.

Even though some things are in the incubator 7 years, and some apache TLPs
have no activity Gossip out of the incubator seems to be a constant thing
for some

So lets get out of here.

Re: Podling Report Reminder - July 2018

[Josh Elser]

Ah, maybe "moving to the Attic" is the phrase I was trying to avoid then 
:). Thanks, John.


Agreed on the software still being great and going to receive love.

On 6/28/18 1:10 PM, John D. Ament wrote:

That sounds like retirement to me.  The way I've always seen it is that
podlings don't fail, the people behind them simply had a change in
priorities.

Gossip is a great toolkit that I believe people will continue to use.

John


On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:


I've been trying to be patient around this, but I think this month's
incubator report must be "Gossip is going to exit incubation" (I'm not
sure what the proper verb is here; I only know that "retire" is wrong)

We've gone through many months where the only traffic I've seen on the
mailing list are the report reminders.

This doesn't need to be interpreted as "Gossip is a failure at the ASF"
or anything of the such. It just means "It's not the right time for
Gossip at the ASF incubator". By all means, we can bring it back into
incubation if we get some more community traction behind the project.

On 6/27/18 5:41 PM, jmcl...@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, 18 July 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, July 04).

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/July2018

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



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling Report Reminder - July 2018

[Josh Elser]

I've been trying to be patient around this, but I think this month's 
incubator report must be "Gossip is going to exit incubation" (I'm not 
sure what the proper verb is here; I only know that "retire" is wrong)


We've gone through many months where the only traffic I've seen on the 
mailing list are the report reminders.


This doesn't need to be interpreted as "Gossip is a failure at the ASF" 
or anything of the such. It just means "It's not the right time for 
Gossip at the ASF incubator". By all means, we can bring it back into 
incubation if we get some more community traction behind the project.


On 6/27/18 5:41 PM, jmcl...@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, 18 July 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, July 04).

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/July2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Any pulse?

[Josh Elser]

I think the writing has been on the wall for a little bit, John. 
Retirement seems in order to me at this point.


On 4/5/18 9:42 AM, John D. Ament wrote:

Hi Gossip Podling

Just wondering, on list communication seems to have died in January.  Are
you still around?

John

Re: Podling Report Reminder - January 2018

[Josh Elser]

Thanks Ed, but did this fall off your radar? I don't see it updated.

On 1/3/18 12:08 PM, Edward Capriolo wrote:

Yes. I will put this together by 3:00 pm EST.

On Wed, Jan 3, 2018 at 11:47 AM, Josh Elser <els...@apache.org> wrote:


Anyone out there capable of putting this together? It is due today..

On 1/3/18 7:17 AM, 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, 17 January 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, January 03).

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.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/January2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Report Reminder - January 2018

[Josh Elser]

Anyone out there capable of putting this together? It is due today..

On 1/3/18 7:17 AM, 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, 17 January 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, January 03).

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.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/January2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [DRAFT] Incubator PMC Board Report - October 2017

[Josh Elser]

Thanks, John. That helps and I agree with your assessment.

Let me leave comment to that effect.

On 10/11/17 10:50 PM, John D. Ament wrote:

Josh,

On Wed, Oct 11, 2017 at 9:48 PM Josh Elser <els...@apache.org> wrote:


(trimming CC since asking a specific question)

John -- how would you like to handle Gossip's lack of report? It seems
like despite my pestering, no one on the ppmc is creating one.



My personal take - mentor should be adding their comments as to what was
attempted to get a report, response(s) from the community when requested.
Mentors shouldn't try to submit the report unless they can actively speak
of the developer community from a participant standpoint.

When I look at gossip's commit history [1], it seems like it's just a case
of being a low volume core internal library.  Not very visible, would
probably be fine to graduate as a TLP with minimal PMC, but that assumes
they stay active enough to keep 3 binding votes together and get reports
out quarterly.

[1]: https://github.com/apache/incubator-gossip/commits/master




I can try to put one together on their behalf, but I don't want to give
an impression that they're doing more than they are..

On 10/11/17 8:04 PM, John D. Ament wrote:

All,

Below is the revised draft.  Not much has changed.  For mentors receiving
this, we have 5 podlings needing sign off.  If you are not sure about
signing off please let the podling know.  Otherwise please try to sign

off

at your convenience.

Incubator PMC report for October 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are currently 54 podlings incubating.  Podlings executed seven
releases last month.  Two new IPMC members joined our fold and one new
podling joined.  We presently have two or three podlings preparing to
graduate this month.

* Community

New IPMC members:

- Davor Bonaci
- Jacques Le Roux

People who left the IPMC:



* New Podlings

- PageSpeed

* Podlings that failed to report, expected next month

- Gossip
- Myriad

* Podling reports missing sign off, will be removed without mentor sign

off


- BatchEE
- Heron
- Milagro
- NetBeans
- Rya

* Graduations

The board has motions for the following:

- Mnemonic
- PredictionIO
- Juneau (possibly)

* Releases

The following releases entered distribution during the month of
September:

- 2017-09-04 Apache Airflow 1.8.2
- 2017-09-05 Apache MXNet 0.11.0
- 2017-09-13 Apache Impala 2.10.0
- 2017-09-13 Apache Mnemonic 0.9.0
- 2017-09-21 Apache Tephra 0.13.0
- 2017-09-27 Apache PredictionIO 0.12.0
- 2017-09-29 Apache Unomi 1.2.0

* IP Clearance



* Legal / Trademarks



* Infrastructure

- A change to the mlreq process caused delays in creation of mailing
lists for PageSpeed.  Work is on going to migrate to a new process for
these requests that is agreeable for IPMC members to execute on.

* Miscellaneous



* Credits

--
 Table of Contents
Airflow
Amaterasu
Annotator
BatchEE
Daffodil
DataFu
FreeMarker
Gobblin
Gossip
HAWQ
Heron
Juneau
Livy
Milagro
MXNet
Myriad
NetBeans
ODF Toolkit
Rya
SensSoft
Spot
Traffic Control
Weex

--


Airflow

Airflow is a workflow automation and scheduling system that can be used

to

author and manage data pipelines.

Airflow has been incubating since 2016-03-31.

Three most important issues to address in the move towards graduation:

1. We are working on our 4th apache release 1.9.0 and are getting

better

at releases
2.
3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None


How has the community developed since the last report?
1. We had our third official release 1.8.2 on Aug 7th 2017.
2. Since our last podling report 3 months ago (i.e. between July
   5 & Sept 25, inclusive), we grew our contributors from 280 to 315
4. Since our last podling report 3 months ago (i.e. between July
   5 & Sept 25, inclusive), we resolved 167 pull requests (currently

at

1797 closed
   PRs)
5. Since being accepted into the incubator, the number of companies
   officially using Apache Airflow has risen from 30 to 114, 16 new

from

the last podling report.



How has the project developed since the last report?
See above : 167 PR resolved, 35 new contributors, & 16 new companies
officially using it.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[x] Nearing graduation
[ ] Other:

Date of last release:

2017-08-07

When were the last committers or PPMC members elected?

2017-01-01 fokko a.k.a Fokko Driesp

Re: [DRAFT] Incubator PMC Board Report - October 2017

[Josh Elser]

 members elected?

   2017-02-13 Woonsan Ko, committer (non-PMC)

Signed-off-by:

   [X](freemarker) Jacopo Cappellato
  Comments:
   [X](freemarker) Jean-Frederic Clere
  Comments:
   [X](freemarker) David E. Jones
  Comments:
   [X](freemarker) Ralph Goers
  Comments:
   [ ](freemarker) Sergio Fernández
  Comments:

IPMC/Shepherd notes:




Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

Gobblin has been incubating since 2017-02-23.

Three most important issues to address in the move towards graduation:

   1. Cut our first release.
   2. Elect new Committer(s) / PPMC.
   3. Update links on website and documentation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

   None

How has the community developed since the last report?

* 15+ major companies, startups, universites and research institutes are
now using Gobblin (refer to Powered-by section [1] here:
https://gobblin.apache.org/ )
* Email stats for last month:
   u...@gobblin.incubator.apache.org : 25
   d...@gobblin.incubator.apache.org : 163
* There have been 40 Commits in last month:
 git log --format='%ci' | grep -cE '2017-0(9)'
* 29 of those commits were by non-committers:
git log --format='%ae %ci' | grep -E '2017-0(9)' | cut -d ' ' -f 1 |
sort | uniq -c | sort -n
* Another video conference based meetup happened last month with good
attendance and interest.
* We are continuing to work towards our first release.

[1] This data was collected before incubation via a survey. It was expanded
to include more companies as and when requested by respective contributors.

How has the project developed since the last report?

* Continued active development.
* Progress continues to be tracked via JIRA / Sprint dashboard.

How would you assess the podling's maturity?

There is an all around progress, and the podling is working towards its
first release.

   [ ] Initial setup
   [X] Working towards first release
   [X] Community building
   [ ] Nearing graduation
   [ ] Other:

Date of last release:

   N/A

When were the last committers or PPMC members elected?

   N/A

Signed-off-by:

   [ ](gobblin) Jean-Baptiste Onofré
  Comments:
   [ ](gobblin) Olivier Lamy
  Comments:
   [X](gobblin) Jim Jagielski
  Comments:

IPMC/Shepherd notes:

   johndament: The podling has the right notion of next steps, website is
probably the biggest area of work needed.


Gossip

Gossip is an implementation of the Gossip Protocol.

Gossip has been incubating since 2016-04-28.

Three most important issues to address in the move towards graduation:

   1.
   2.
   3.

Any issues that the Incubator PMC (IPMC) or ASF Board 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 would you assess the podling's maturity?
Please feel free to add your own commentary.

   [ ] Initial setup
   [ ] Working towards first release
   [ ] Community building
   [ ] Nearing graduation
   [ ] Other:

Date of last release:

   -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

   [ ](gossip) P. Taylor Goetz
  Comments:
   [ ](gossip) Josh Elser
  Comments:
   [ ](gossip) Drew Farris
  Comments:

IPMC/Shepherd notes:




HAWQ

HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a
robust and high-performance massively-parallel processing (MPP) SQL
framework
evolved from Pivotal Greenplum Database.

HAWQ has been incubating since 2015-09-04.

Three most important issues to address in the move towards
graduation:

   1. Continue to improve the project's release cadence. To this
  end we plan on expanding automation services to support
  increased developer participation.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
to be aware of?

  Nothing urgent at this time.

How has the community developed since the last report?

1. Conference Talks (2):

  * Big Data Technology Trends. China Big Data Industry Ecosystem Conference
(Speaker: Lei Chang, August 2, 2017)

  * Future Data Warehouse. China CIO Conference (Speaker: Lei Chang, Sep 16,
2017)

2. Active contributions from approximately 20 different community
contributors since the last report (July 2017).

3. Yi JIN volunteered as the release manager for 2.3 release.

4. Three committer candidates are under voting process:

1) Amy BAI
2) ChunLing WANG
3) Hongxu MA


How has the project developed since the last report?

1. Apache HAWQ 2.2.0.0 was released. HAWQ 2.2 is the first binary release.

Release information:

1) Release page:

https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release

2) Is

Re: Vision letter, reqest for discussion

[Josh Elser]

On 7/18/17 10:30 PM, Edward Capriolo wrote:

On Tue, Jul 18, 2017 at 3:25 PM, P. Taylor Goetz  wrote:


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

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

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 

Re: Podling Report Reminder - July 2017

[Josh Elser]

Thanks!

On 7/5/17 4:10 PM, Edward Capriolo wrote:

Josh,

I just filled it out.

Thanks,
Edward

On Wed, Jul 5, 2017 at 1:23 PM, Josh Elser <els...@apache.org> wrote:


Reminder -- this is due today...

On 7/5/17 10:00 AM, 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, 19 July 2017, 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, July 05).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

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/July2017

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

Fwd: Gossip (apache incubator)

[Josh Elser]

Hi Terry,

Not sure where you pulled my information from, but all Apache projects 
have mailing list where community discussions happen.


I've forwarded your original message to that list. Please take a moment 
to subscribe (send a message to 
dev-subscr...@gossip.incubator.apache.org and follow the instructions in 
the automated reply you receive).


The other folks on the list will be able to help you get involved! 
Please also take some time to read the information on the website.


- Josh


 Forwarded Message 
Subject: Gossip (apache incubator)
Date: Wed, 24 May 2017 22:59:25 -0400
From: Terry Weymouth 
To: josh.el...@gmail.com

Josh, 	apologies for the intrusion, but among all the contributors to 
Gossip, yours is the only profile with an e-mail.

A couple of questions:
Is there a message board; IRC; comment board; or e-mail archive for the 
project?
I’m running into typical start up problems; how to set things, 
constructing the first working example: that sort of thing.

Just wanted to have some resource for the new-be questions.

Thanks.
Terry.

Re: Podling report for April

[Josh Elser]

Left my sign-off. Looks good!

Thanks for taking care of this.

Edward Capriolo wrote:

Hey all,

This month wrote our podling report right to the wiki.

https://wiki.apache.org/incubator/April2017

There are still a few days left before the due date (5th) so if anyone
would like me to add/change anything please suggest it.

Thanks,
Edward

Re: [RESULT] [VOTE] Release Gossip (Incubating) version gossip-0.1.2-incubating (RC1)

[Josh Elser]

I haven't missed you sending the VOTE up to the general@incubator list, 
have I?


Edward Capriolo wrote:

The vote passes.

Vote thread:
https://lists.apache.org/thread.html/d56cfc6bb3b7d3bdb94058605e3b77c4da93df6fc875280df73f4c1d@%3Cdev.gossip.apache.org%3E

+1
Gary Dusbabek
Edward Capriolo
Chandresh Pancholi
Josh Elser

-1
Nil

0
Nil

Forwarding onto IPMC for next round.

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

[Josh Elser]

+1 (binding)

Looks good to me.

* sigs/xsums OK
* mvn apache-rat:check passes
* DISCLAIMER present
* L look OK
* Dependencies look OK
* Could run tests (yay)
* Generated jar contains L

A couple of minor things to fix (nit-picky things -- not release issues)

* Move keys/ to src/test/resources. They appear to be test-related. 
Maybe I'll just put a PR in for this one :)
* Maybe slap a header on the eclipse-template.xml. Would be nice, but 
not super critical.


Great work, Edward.

Edward Capriolo wrote:

I am pleased to be calling this vote for the source release of Apache
Gossip 0.1.2.

A detailed description of the release is here:
https://lists.apache.org/thread.html/d244f03eba775c0de96bf527c67dce80e393c7ed614d43650cb23793@%3Cdev.gossip.apache.org%3E

Ancillary artifacts such as poms, jars, ect. can be found here:
https://repository.apache.org/content/repositories/orgapachegossip-1003/

The Git commit ID is:
d5fe9f96c8edae620f7b7568c7498486df216806
https://github.com/apache/incubator-gossip/commit/d5fe9f96c8edae620f7b7568c7498486df216806

The tag is:
https://github.com/apache/incubator-gossip/tree/gossip-0.1.2-incubating-b-rc1

Checksums of:

https://repository.apache.org/content/repositories/orgapachegossip-1003/org/apache/gossip/gossip/0.1.2-incubating/gossip-0.1.2-incubating-source-release.zip
SHA1: 5bbb5f097b9f8d0e6812a8d5c875d2fa190c40ff
MD5: 7d6d886bfcdf741530ecc29a0cbfb434

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

The artifacts are also staged in
https://dist.apache.org/repos/dist/dev/incubator/gossip/gossip-0.1.2-incubating-rc1/

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.

Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Re: Post-0.1.1 release actions

[Josh Elser]

Website is updated.

All that remains is to send a note out to announceme...@apache.org to 
brag about, I mean announce, the release ;)


Make sure to send from your apache.org addr, include a brief explanation 
about what Gossip is, and include the stock "incubation disclaimer".


P. Taylor Goetz wrote:

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<edlinuxg...@gmail.com>  wrote:

On Fri, Feb 3, 2017 at 3:36 PM, Josh Elser<els...@apache.org>  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: Post-0.1.1 release actions

[Josh Elser]

Sweet! Thanks, Edward. Will do shortly.

(Literally) just saw it propagate to central :)

http://central.maven.org/maven2/org/apache/gossip/gossip/0.1.1-incubating/

Edward Capriolo wrote:

Josh,

Sorry about that. For most of my maven release I have that step
automated. 1002 is released. You can merge/push the site and I will make
the announcement.

Thanks,
Edward

On Fri, Feb 3, 2017 at 3:36 PM, Josh Elser <els...@apache.org
<mailto:els...@apache.org>> 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
<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

Post-0.1.1 release actions

[Josh Elser]

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

Re: Gossip learning videos

[Josh Elser]

Nice!

Have you added a link to it from the gossip.i.a.o site?

Edward Capriolo wrote:

Hey all,

Based on a conversation we had on list about knowledge transfer I created a
video, that explains gossip protocol and how to get started on it.

https://twitter.com/edwardcapriolo/status/819580942343868416

I hope this helps.

Thanks,
Edward

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:

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

[Josh Elser]

Edward Capriolo wrote:

On Tue, Jan 3, 2017 at 11:45 AM, Josh Elser<els...@apache.org>  wrote:


-1 due to a dependency on a project with a category-X license [1].

Gossip is transitively depending on org.json:json via
jackson-datatype-json-org.

```
[INFO] org.apache.gossip:gossip:jar:0.1.1-incubating
[INFO] +- com.fasterxml.jackson:jackson-datatype-json-org:jar:1.8.0:co
mpile
[INFO] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.8.6:compile
[INFO] |  |  \- org.codehaus.jackson:jackson-core-asl:jar:1.8.6:compile
[INFO] |  \- org.json:json:jar:20090211:compile
```

org.json:json is licensed with the JSON license which the ASF has recently
moved to category-X [2]. Debian has a list of some alternatives[3] which
can be used instead. This would need to be resolved before your release.

I know in Calcite we use jackson-databind for JSON serialization of POJOs
and that doesn't have the dependency on org.json:json. Perhaps this can be
easily resolved switching the jackson dependencies and maybe some API calls.

Good:

* xsums/sigs match (for source-release.zip)
* KEYS looks good
* Can build from source
* DISCLAIMER is present

I see that the rc1 tag was pushed, and will assume that the next VOTE
message will get that right too. Re-stating this one as I can't verify that
presently.

Nit:

* Wrong header in the src/**/log4j.properties files. Update it to match
the header in the rest of the java files. Fix for next release.
* Year in NOTICE is now out of date. Fix for next release.
* Use "Apache Gossip" for the first mention of "Gossip" in the README.md.
Fix for next release.
* Add the license text to the README and eclipse template as it's trivial
to do so for both (xml and md both support "comments"). Fix for next
release.
* Tests failed for me (on a `mvn package`). Not a release issue, just a
quality issue. I would expect that all of the tests would pass, and just
wanted to mention it.

```
Failed tests:
   ShutdownDeadtimeTest.DeadNodesDoNotComeAliveAgain:103 ComparisonFailure
expected:<[16]>  but was:<[8]>
   StartupSettingsTest.testUsingSettingsFile:69 » Runtime
java.net.BindException:...
   TenNodeThreeSeedTest.test:44->abc:78 » Runtime java.net.BindException:
Address...
   TenNodeThreeSeedTest.testAgain:49->abc:78 » Runtime
java.net.BindException: Ad...
```

- Josh

[1] https://www.apache.org/legal/resolved#category-x
[2] https://www.apache.org/legal/resolved#json
[3] https://wiki.debian.org/qa.debian.org/jsonevil

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-1001

The Git commit ID is:
https://github.com/edwardcapriolo/incubator-gossip/commit/74
133870410fec45bd6cac39351fcbbe0950de18

Which will be tagged as gossip-0.1.1-incubating

https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
a=commit;h=66d8b7f060bddeeb7c50cb0918f98ce3b265c564


Checksums of
https://repository.apache.org/content/repositories/orgapache
gossip-1001/org/apache/gossip/gossip/0.1.1-incubating/
gossip-0.1.1-incubating-source-release.zip.asc
:
SHA1: 53ca6498d0f704fe7931ec23ca81a638a1fd666c
MD5: c27067c47bdeb6133660beda908f679c

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/rya/KEYS

The vote will be open for 72 hours. Please download the release candidate
and evaluate the necessary items including checking hashes, signatures,
build from source, and test.


Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...



I have changed the dependency to this:
https://mvnrepository.com/artifact/com.fasterxml.jackson.datatype/jackson-datatype-json-org/2.8.5



 com.fasterxml.jackson.datatype
 jackson-datatype-json-org
 2.8.5


Which produces this:

mvn dependency:tree
[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ gossip ---
[INFO] org.apache.gossip:gossip:jar:0.1.2-incubating-SNAPSHOT
[INFO] +-
com.fasterxml.jackson.datatype:jackson-datatype-json-org:jar:2.8.5:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-core:jar:2.8.5:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-databind:jar:2.8.5:compile
[INFO] |  |  \-
com.fasterxml.jackson.core:jackson-annotations:jar:2.8.0:compile
[INFO] |  \- org.apache.geronimo.bundles:json:jar:20090211_1:compile
[INFO] +- org.junit.jupiter:junit-jupiter-api:jar:5.0.0-M2:test
[INFO] |  +- org.opentest4j:opentest4j:jar:1.0.0-M1:test
[INFO] |  \- org.junit.platform:junit-platform-commons:jar:1.0.0-M2:test
[INFO] +- org.junit.jupiter:junit-jupiter-engine:jar:5.0.0-M2:test
[INFO] |  \- org.junit.platform:junit-platform-engine:jar:1.0.0-M2:test
[INFO] +- org.junit.vintage:junit-vintage-engine:jar

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

[Josh Elser]

I'm just getting back from a little vacation. If you can hold off on 
calling the vote strictly after 72hrs, I'll do my best to look at this 
tmrw before it makes its way to the IPMC for a vote.


A couple of remarks on the VOTE email's content:
  * The git commit ID is good to see (not just the tag), but linking to 
your personal github acct is a little out-of-the-normal to me.

  * The URL to the KEYS file and the git-wip-us URL are both wrong.
  * For the checksums, I'm guessing you copied the wrong filename. I 
assume you meant those are the checksums for 
gossip-0.1.1-incubating-source-release.zip as a gpg signature doesn't 
require a checksum to ensure it was not tampered with.


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-1001

The Git commit ID is:
https://github.com/edwardcapriolo/incubator-gossip/commit/74133870410fec45bd6cac39351fcbbe0950de18

Which will be tagged as gossip-0.1.1-incubating

https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=66d8b7f060bddeeb7c50cb0918f98ce3b265c564


Checksums of
https://repository.apache.org/content/repositories/orgapachegossip-1001/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip.asc
:
SHA1: 53ca6498d0f704fe7931ec23ca81a638a1fd666c
MD5: c27067c47bdeb6133660beda908f679c

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/rya/KEYS

The vote will be open for 72 hours. Please download the release candidate
and evaluate the necessary items including checking hashes, signatures,
build from source, and test.


Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

[jira] [Commented] (GOSSIP-12) add 'gossip' in search-hadoop.com or similar

[Josh Elser (JIRA)]

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

Josh Elser commented on GOSSIP-12:
--

Are you aware of https://lists.apache.org/list.html?gossip.apache.org? This is 
the primary ASF-controlled mail-archives

The sites you list aren't owned/controlled by the PMC, and I'm not sure who we 
would go about adding Gossip to them.

> add 'gossip' in search-hadoop.com or similar
> 
>
> Key: GOSSIP-12
> URL: https://issues.apache.org/jira/browse/GOSSIP-12
> Project: Gossip
>  Issue Type: Wish
>Reporter: Sree Vaddi
>  Labels: archives, mail, search
> Fix For: 0.1.2
>
>
> add 'gossip' to the list of projects that can be searchable at:
> http://search-hadoop.com/ or similar.
> for this contact:
> https://sematext.com/contact/



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

Re: [VOTE] Release Apache Gossip

[Josh Elser]

I've added you as an administrator of the GOSSIP project.

chandresh pancholi wrote:

Awesome.
Kudos to Ed.

Now let's move rest of the open issues to next version in JIRA. I don't
have permission. Please provide Edit permission in JIRA, I will move them.

Thanks

On Sun, Dec 11, 2016 at 11:11 PM, Edward Capriolo<edlinuxg...@gmail.com>
wrote:


Update: Thanks to Taylor who helped me sign my key.

Here is the released artifact for gossip-0.1.1-incubating:
https://repository.apache.org/content/repositories/orgapachegossip-1001

Here is the content to be pushed as a tag.
https://github.com/apache/incubator-gossip/compare/
master...edwardcapriolo:master

Thanks all.



On Mon, Nov 21, 2016 at 10:41 AM, Edward Capriolo<edlinuxg...@gmail.com>
wrote:


I will add the licence headers to the affected java files and make the

RAT

changes today.

As for the web of trust. Since I am the release manager for this release
it seems like I can have a "key-signing party" with Taylor and/or Josh

via

google hangouts. I can also contact some of my other ASF buddies and
attempt to do the same.

Is any committer on incubator-gossip outside of myself interested in
attending an incubator-gossip signing party?

Thanks,
Edward

On Fri, Nov 18, 2016 at 3:06 PM, Josh Elser<josh.el...@gmail.com>

wrote:


P. Taylor Goetz wrote:


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.


Cool thanks for confirming. I couldn't recall for certain if it was a
"should" or "must" :)



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.


Good enough for me!

-Taylor
- Josh

Re: [VOTE] Release Apache Gossip

[Josh Elser]

Are you asking for this to be voted on?

If so... it would be good to start a new thread and clearly state the 
information about what's being voted on. You're missing some things that 
are required. Here's an example from another podling that contains all 
of the necessary info: 
https://lists.apache.org/thread.html/01d692717b2ee088253fa96c42759309a2a4d2aaf9867905bc473fa7@%3Cdev.rya.apache.org%3E


Thanks.

Edward Capriolo wrote:

Update: Thanks to Taylor who helped me sign my key.

Here is the released artifact for gossip-0.1.1-incubating:
https://repository.apache.org/content/repositories/orgapachegossip-1001

Here is the content to be pushed as a tag.
https://github.com/apache/incubator-gossip/compare/master...edwardcapriolo:master

Thanks all.



On Mon, Nov 21, 2016 at 10:41 AM, Edward Capriolo<edlinuxg...@gmail.com>
wrote:


I will add the licence headers to the affected java files and make the RAT
changes today.

As for the web of trust. Since I am the release manager for this release
it seems like I can have a "key-signing party" with Taylor and/or Josh via
google hangouts. I can also contact some of my other ASF buddies and
attempt to do the same.

Is any committer on incubator-gossip outside of myself interested in
attending an incubator-gossip signing party?

Thanks,
Edward

On Fri, Nov 18, 2016 at 3:06 PM, Josh Elser<josh.el...@gmail.com>  wrote:



P. Taylor Goetz wrote:


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.


Cool thanks for confirming. I couldn't recall for certain if it was a
"should" or "must" :)



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.


Good enough for me!

-Taylor
- Josh

Re: [VOTE] Release Apache Gossip

[Josh Elser]

P. Taylor Goetz wrote:

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.


Cool thanks for confirming. I couldn't recall for certain if it was a 
"should" or "must" :)




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.


Good enough for me!


-Taylor


- Josh

Re: [VOTE] Release Apache Gossip

[Josh Elser]

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<josh.el...@gmail.com>  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<edlinuxg...@gmail.com>
wrote:

I created https://issues.apache.org/jira/browse/INFRA-12911

On Wed, Nov 9, 2016 at 5:14 PM, P. Taylor Goetz<ptgo...@gmail.com>
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 of it?

-Taylor

On Nov 9, 2016, at 4:01 PM, Edward Capriolo<edlinuxg...@gmail.com>
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<josh.el...@gmail.com>


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<edlinuxg...@gmail.com>


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
ating.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 exis

Re: [VOTE] Release Apache Gossip

[Josh Elser]

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/maven2/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/maven2/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/maven2/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<edlinuxg...@gmail.com>
wrote:


I created https://issues.apache.org/jira/browse/INFRA-12911

On Wed, Nov 9, 2016 at 5:14 PM, P. Taylor Goetz<ptgo...@gmail.com>  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 of it?

-Taylor


On Nov 9, 2016, at 4:01 PM, Edward Capriolo<edlinuxg...@gmail.com>

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<josh.el...@gmail.com>

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<edlinuxg...@gmail.com>

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
ating.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-in

Re: [VOTE] Release Apache Gossip

[Josh Elser]

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<edlinuxg...@gmail.com>  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<ptgo...@gmail.com<mailto:ptgo...@gmail.com>>  wrote:
Done.

-Taylor


On Oct 27, 2016, at 11:58 AM, P. Taylor 
Goetz<ptgo...@gmail.com<mailto:ptgo...@gmail.com>>  wrote:

I’ll take care of it.

-Taylor


On Oct 27, 2016, at 11:43 AM, Edward 
Capriolo<edlinuxg...@gmail.com<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<edlinuxg...@gmail.com<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<els...@apache.org<mailto:els...@apache.org>>  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/release/incubator/gossip>
https://dist.apache.org/repos/dist/dev/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 Capri

Re: [VOTE] Release Apache Gossip

[Josh Elser]

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=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
 apache
 RELEASE
 

 org.apache.gossip
 gossip
 gossip

A few people seem to be confused because the pre-fork code is also

in

my

github.

On Fri, Oct 7, 2016 at 2:55 PM, P. Taylor Goetz

wrote:

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<

chandreshpancholi...@gmail.com>  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<

ptgo...@gmail.com>

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<

edlinuxg...@gmail.com>

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





--
Chandresh Pancholi
Senior Software Engineer
Flipkart.com

[jira] [Commented] (GOSSIP-23) Description of apache gossip is showing on every page of website

[Josh Elser (JIRA)]

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

Josh Elser commented on GOSSIP-23:
--

Also, the website source is available in the same repository as the codebase: 
https://github.com/apache/incubator-gossip/tree/site-src

> Description of apache gossip is showing on every page of website
> 
>
> Key: GOSSIP-23
> URL: https://issues.apache.org/jira/browse/GOSSIP-23
> Project: Gossip
>  Issue Type: Improvement
>Reporter: Chandresh Pancholi
>
> If possible please share web ui code base so that i can make necessary 
> changes in code and push.



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

[jira] [Commented] (GOSSIP-17) Add metrics to key codepaths

[Josh Elser (JIRA)]

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

Josh Elser commented on GOSSIP-17:
--

Done, [~chinnasamyad].

> Add metrics to key codepaths
> 
>
> Key: GOSSIP-17
> URL: https://issues.apache.org/jira/browse/GOSSIP-17
> Project: Gossip
>  Issue Type: New Feature
>Reporter: Edward Capriolo
>Assignee: Chinnasamy
>
> yammer/dropwizzard/codahale metrics would be a good thing to add.
> We should use histograms to track how long inter-node operations take.
> We should use meters or counters with successful/failed requests. 
> It would be interesting to keep per host stats but possibly it makes sense to 
> turn that off for larger deployments.



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

[jira] [Resolved] (GOSSIP-9) Change the mailing list URI

[Josh Elser (JIRA)]

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

Josh Elser resolved GOSSIP-9.
-
Resolution: Won't Fix

Agreed, [~ashishpaliwal]. The ML's are correct, the subscribe address is just 
different.

> Change the mailing list URI
> ---
>
> Key: GOSSIP-9
> URL: https://issues.apache.org/jira/browse/GOSSIP-9
> Project: Gossip
>  Issue Type: Task
> Environment: Apache incubator URI
>Reporter: Mahesh Dharmasena
>  Labels: mailing-list
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Please change mailing list URIs of the Apache Incubator page 
> (http://incubator.apache.org/projects/gossip.html). The mailing list 
> displayed are not working.
> Change the URI to:
> commits-subscr...@gossip.incubator.apache.org
> dev-subscr...@gossip.incubator.apache.org



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

[jira] [Commented] (GOSSIP-19) Download page must not link to unreleased software

[Josh Elser (JIRA)]

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

Josh Elser commented on GOSSIP-19:
--

bq. I keep ducking doing the first release. Maybe this is a good time.

+1

The website should be fixed before the first release goes out though. Anyone 
able to take this up?

> Download page must not link to unreleased software
> --
>
> Key: GOSSIP-19
> URL: https://issues.apache.org/jira/browse/GOSSIP-19
> Project: Gossip
>  Issue Type: Bug
>Reporter: Sean Busbey
>Priority: Blocker
>
> Currently the Gossip download page provides a link for using unreleased 
> software (specifically pointing out the github repository). It also links to 
> that repository in the main nav bar at the top of the page.
> ASF policy prohibits the former and "best practices" strongly discourages the 
> latter.



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

Re: [jira] [Commented] (GOSSIP-15) GossipManager: TimeUnit.MILLISECONDS.sleep(1) is consuming resources.

[Josh Elser]

Filing a JIRA issue for the test failure would definitely be great.

Thanks Chia-Hung!

Chia-Hung Lin wrote:

I am interested in this issue. But searching the website[1] doesn't
find instruction on how to contribute so simply place my change at
[2].

In addition to the change, I notice that `mvn clean package` sometimes
fails due to ShutdownDeadtimeTest test case. This happens even with a
clean checkout from incubator repos (git clone ...) so it looks not
related to my change. Perhaps I should open another ticket for this?

org.junit.ComparisonFailure: ComparisonFailure expected:<[16]>  but was:<[2]>
at 
org.apache.gossip.ShutdownDeadtimeTest.DeadNodesDoNotComeAliveAgain(ShutdownDeadtimeTest.java:100)

Results :

Failed tests:
   ShutdownDeadtimeTest.DeadNodesDoNotComeAliveAgain:100
ComparisonFailure expected:<[16]>  but was:<[2]>
   TenNodeThreeSeedTest.testAgain:52->abc:90 ComparisonFailure
expected:<[2]0>  but was:<[]0>

[1]. http://gossip.incubator.apache.org/
[2]. 
https://github.com/chlin501/incubator-gossip/commit/0a7d2ee12e54cdd4ccc171ea89ddb41af8b380e4

On 16/07/2016, Edward Capriolo (JIRA)  wrote:

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

Edward Capriolo commented on GOSSIP-15:
---

ScheduledExecutor seems like a good fit.


GossipManager: TimeUnit.MILLISECONDS.sleep(1) is consuming resources.
-

 Key: GOSSIP-15
 URL: https://issues.apache.org/jira/browse/GOSSIP-15
 Project: Gossip
  Issue Type: Bug
Reporter: Gary Dusbabek

We need to find a better solution to what is essentially a busy wait.



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

Re: created infra for svn branch for website

[Josh Elser]

I left some comments for Sree on the pull request that need to be added for
Apache incubator projects.

I think this is the blocker.
On Jun 29, 2016 2:47 PM, "Edward Capriolo" <edlinuxg...@gmail.com> wrote:

> Hello,
>
> The site is still coming soon. I did not follow deeply the entire convo put
> I would like to push this through and promote the project to internet. Is
> there any specific this my I can do to unblock this.
>
> On Thursday, June 23, 2016, Edward Capriolo <edlinuxg...@gmail.com> wrote:
>
> > No that name is fune
> > On Jun 22, 2016 11:38 PM, "Josh Elser" <josh.el...@gmail.com
> > <javascript:_e(%7B%7D,'cvml','josh.el...@gmail.com');>> wrote:
> >
> >> Edward, et al,
> >>
> >> Anyone have a preference on the name of the branch for the Jekyll
> project
> >> that Sree has put together?
> >>
> >> Josh Elser wrote:
> >>
> >>> Sorry, Sree, I thought you were a committer already :). Too many names
> >>> to keep track of.
> >>>
> >>> You can either just do one pull-request for the jekyll project (like
> you
> >>> did already), or you can also do a pull-request for the generated-HTML
> >>> to the asf-site branch.
> >>>
> >>> Accumulo called their jekyll-source branch "gh-pages" so that Github
> >>> would auto-render it and be all pretty. Gossip can call it whatever it
> >>> wants. I only mentioned what Accumulo does as a concrete example with
> >>> documentation+workflow.
> >>>
> >>> Will comment on your pull-request directly.
> >>>
> >>> Sree V wrote:
> >>>
> >>>> Still figuring out the 'git hook', Josh.
> >>>>
> >>>> I created the initial base and this is the pull request for
> >>>> it.https://github.com/apache/incubator-gossip/pull/5
> >>>>
> >>>> Would someone with commit privileges create 'site-src' branch and push
> >>>> to github, please ?So, I can create a pull request for it. Let me
> >>>> know, otherwise.
> >>>>
> >>>> 'site-src' more descriptive than 'gh-pages' ?
> >>>>
> >>>>
> >>>> Thanking you.
> >>>> With Regards
> >>>> Sree
> >>>>
> >>>> On Tuesday, June 21, 2016 8:06 PM, Josh Elser<josh.el...@gmail.com
> >>>> <javascript:_e(%7B%7D,'cvml','josh.el...@gmail.com');>>
> >>>> wrote:
> >>>>
> >>>>
> >>>> I like Jekyll a lot. I just didn't want to sway you into thinking you
> >>>> had to use it or that it was the only option.
> >>>>
> >>>> Also: I already sent you the link to the commit hook, Sree.
> >>>>
> >>>>
> >>>>
> https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=_devtools/git-hooks/post-commit;hb=gh-pages
> >>>>
> >>>>
> >>>> Sree V wrote:
> >>>>
> >>>>> Thank you for the details, Josh.
> >>>>> I will take the same approach.I will use the jekyll for now, unless
> >>>>> you recommend another.
> >>>>> Please send the 'git commit hook', to install on my local.
> >>>>>
> >>>>>
> >>>>> Thanking you.
> >>>>> With Regards
> >>>>> Sree
> >>>>>
> >>>>> On Monday, June 20, 2016 3:57 PM, Josh Elser<josh.el...@gmail.com
> >>>>> <javascript:_e(%7B%7D,'cvml','josh.el...@gmail.com');>>
> >>>>> wrote:
> >>>>>
> >>>>>
> >>>>> I thought Taylor mentioned this on the INFRA JIRA issue, but there
> is a
> >>>>> branch named "asf-site" in the incubator-gossip repository. This is
> >>>>> what
> >>>>> git-pubsub is configured to pull HTML content from and publish it to
> >>>>> your website on git-push:
> >>>>>
> >>>>>
> >>>>>
> https://git1-us-west.apache.org/repos/asf?p=incubator-gossip.git;a=shortlog;h=refs/heads/asf-site
> >>>>>
> >>>>>
> >>>>> A "common" approach would be have another branch which hosts some
> >>>>> project which can generate your website (a Jekyll project is common,
> >>>>> but
> >>

Re: created infra for svn branch for website

[Josh Elser]

Sorry, Sree, I thought you were a committer already :). Too many names 
to keep track of.


You can either just do one pull-request for the jekyll project (like you 
did already), or you can also do a pull-request for the generated-HTML 
to the asf-site branch.


Accumulo called their jekyll-source branch "gh-pages" so that Github 
would auto-render it and be all pretty. Gossip can call it whatever it 
wants. I only mentioned what Accumulo does as a concrete example with 
documentation+workflow.


Will comment on your pull-request directly.

Sree V wrote:

Still figuring out the 'git hook', Josh.

I created the initial base and this is the pull request for 
it.https://github.com/apache/incubator-gossip/pull/5

Would someone with commit privileges create 'site-src' branch and push to 
github, please ?So, I can create a pull request for it.  Let me know, otherwise.

'site-src' more descriptive than 'gh-pages' ?


Thanking you.
With Regards
Sree

 On Tuesday, June 21, 2016 8:06 PM, Josh Elser<josh.el...@gmail.com>  wrote:


  I like Jekyll a lot. I just didn't want to sway you into thinking you
had to use it or that it was the only option.

Also: I already sent you the link to the commit hook, Sree.

https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=_devtools/git-hooks/post-commit;hb=gh-pages

Sree V wrote:

Thank you for the details, Josh.
I will take the same approach.I will use the jekyll for now, unless you 
recommend another.
Please send the 'git commit hook', to install on my local.


Thanking you.
With Regards
Sree

   On Monday, June 20, 2016 3:57 PM, Josh Elser<josh.el...@gmail.com>   
wrote:


   I thought Taylor mentioned this on the INFRA JIRA issue, but there is a
branch named "asf-site" in the incubator-gossip repository. This is what
git-pubsub is configured to pull HTML content from and publish it to
your website on git-push:

https://git1-us-west.apache.org/repos/asf?p=incubator-gossip.git;a=shortlog;h=refs/heads/asf-site

A "common" approach would be have another branch which hosts some
project which can generate your website (a Jekyll project is common, but
not the only option). From this Jekyll project, you can generate HTML,
and then commit it to the asf-site branch and push that branch.

Concretely, here's an example of how we make this work in Apache
Accumulo[1]. There is a branch named "gh-pages" which contains our
Jekyll project. We provide a Git commit-hook[2] which you can install
locally which will automatically build and commit your latest commit on
gh-pages to the asf-site branch. Then, you can just push both the
gh-pages and asf-site branch. I'm not sure what other kind of automation
people have here, but the possibilities are endless.

[1] http://accumulo.apache.org/source#website
[2]
https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=_devtools/git-hooks/post-commit;hb=gh-pages

Sree V wrote:

got it.closed the jira.
what is `git pubsub setup for the gossip website` ?how do i use it to develop 
gossip website ?

Thanking you.
With Regards
Sree

     On Monday, June 20, 2016 10:00 AM, Josh Elser<josh.el...@gmail.com>   
wrote:


 Ditto to what Taylor already said on that issue. Please close that issue
as invalid. Thanks!

Sree V wrote:

Hi Edward/Team,
I created jira, https://issues.apache.org/jira/browse/INFRA-12139
requesting apache infrastructure to create svn branch and enable pubsub,for our 
gossip website.


Thanking you.
With Regards
Sree

Re: created infra for svn branch for website

[Josh Elser]

I thought Taylor mentioned this on the INFRA JIRA issue, but there is a 
branch named "asf-site" in the incubator-gossip repository. This is what 
git-pubsub is configured to pull HTML content from and publish it to 
your website on git-push:


https://git1-us-west.apache.org/repos/asf?p=incubator-gossip.git;a=shortlog;h=refs/heads/asf-site

A "common" approach would be have another branch which hosts some 
project which can generate your website (a Jekyll project is common, but 
not the only option). From this Jekyll project, you can generate HTML, 
and then commit it to the asf-site branch and push that branch.


Concretely, here's an example of how we make this work in Apache 
Accumulo[1]. There is a branch named "gh-pages" which contains our 
Jekyll project. We provide a Git commit-hook[2] which you can install 
locally which will automatically build and commit your latest commit on 
gh-pages to the asf-site branch. Then, you can just push both the 
gh-pages and asf-site branch. I'm not sure what other kind of automation 
people have here, but the possibilities are endless.


[1] http://accumulo.apache.org/source#website
[2] 
https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=_devtools/git-hooks/post-commit;hb=gh-pages


Sree V wrote:

got it.closed the jira.
what is `git pubsub setup for the gossip website` ?how do i use it to develop 
gossip website ?

Thanking you.
With Regards
Sree

 On Monday, June 20, 2016 10:00 AM, Josh Elser<josh.el...@gmail.com>  wrote:


  Ditto to what Taylor already said on that issue. Please close that issue
as invalid. Thanks!

Sree V wrote:

Hi Edward/Team,
I created jira, https://issues.apache.org/jira/browse/INFRA-12139
requesting apache infrastructure to create svn branch and enable pubsub,for our 
gossip website.


Thanking you.
With Regards
Sree

Fwd: [FINAL DRAFT] Incubator PMC Board Report - June 2016 -- feedback

[Josh Elser]

Some positive feedback from Marvin on the recent report :)

Thanks again, Edward, for coming through at the very end with some quality!

 Original Message 
Subject: [FINAL DRAFT] Incubator PMC Board Report - June 2016 -- feedback
Date: Mon, 6 Jun 2016 18:40:21 -0700
From: Marvin Humphrey <mar...@rectangular.com>
Reply-To: gene...@incubator.apache.org
To: gene...@incubator.apache.org <gene...@incubator.apache.org>





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 our first report. We have imported 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) P. Taylor Goetz
  [x](gossip) Josh Elser
  [X](gossip) Sean Busbey

Shepherd/Mentor notes:

  Sean Busbey:
Community def still bootstrapping, but has done a good job of making
progress once infra was in place.


Very nice first report from Gossip -- especially the roadmap!



Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: New PR for a builder for GossipManager

[Josh Elser]

Sounds like a good idea to me :)

Do you have the ability to great an issue on JIRA yourself?

jaideep.d...@gmail.com wrote:

PR - https://github.com/apache/incubator-gossip/pull/2

On Fri, Jun 3, 2016 at 11:25 PM, jaideep.d...@gmail.com<
jaideep.d...@gmail.com>  wrote:


Hi all,
I have created a pull-req to create a builder for the RandomGossipManager
class. Please review.

I didn't see any JIRA for this, should I create one?

Thanks,
--
Jaideep Dhok

Re: gossip board report

[Josh Elser]

Thanks for posting it, Sean. Didn't realize you didn't have the karma, 
Edward.


Team work :)

P. Taylor Goetz wrote:

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<bus...@apache.org>  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<edlinuxg...@gmail.com>  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<josh.el...@gmail.com>  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:

Re: gossip board report

[Josh Elser]

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: