Re: gossip board report

2016-06-03 Thread P. Taylor Goetz
Thanks Sean. I’ve signed off on the report as well. Edward — can you send a request to general@incubator with your Incubator wiki username and request write access? Note that that wiki is separate from the confluence wiki. -Taylor > On Jun 3, 2016, at 2:08 PM, Sean Busbey

Re: gossip board report

2016-06-03 Thread P. Taylor Goetz
I will ad it. -Taylor > On Jun 3, 2016, at 1:59 PM, Edward Capriolo wrote: > > Sorry, > I have mentioned this before but every page is immutable to me. Can someone > with wiki access please add this for me. > >> On Fri, Jun 3, 2016 at 11:46 AM, Josh Elser

Gossip Embedded

2016-06-02 Thread P. Taylor Goetz
One use case that shouldn't be overlooked is the embedded market.Think of low level devices discovering one another in a network of constrained devices. It may be worth considering using byte arrays for gossip payloads, and potentially introducing a plugable parser or handler layer (at least in

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

2016-06-20 Thread P. Taylor Goetz (JIRA)
[ https://issues.apache.org/jira/browse/GOSSIP-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339652#comment-15339652 ] P. Taylor Goetz commented on GOSSIP-6: -- [~sreevaddi] We have gitpubsub setup for the website

Re: 5 mail DLs total, i guess ?

2016-06-20 Thread P. Taylor Goetz
+1 -Taylor > On Jun 20, 2016, at 9:05 AM, Edward Capriolo wrote: > > Incubator projects typically decide not to have a user. Following advice we > did not create one. > > With the traffic levels at this point I suggest we stuck with 2 dev and > private. > On Jun 20,

Re: Gossip Project Bootstrap

2016-05-18 Thread P. Taylor Goetz
: > > +1 for git branch. Does this mean that we don't have to use svnpubsub? > > Gary. > > On Wed, May 18, 2016 at 12:34 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > >> Here’s the JIRA for INFRA: >> https://issues.apache.org/jira/browse/INFRA-11909 >>

Gossip Project Bootstrap

2016-05-18 Thread P. Taylor Goetz
Here’s the JIRA for INFRA: https://issues.apache.org/jira/browse/INFRA-11909 Quick question: For the project website, do we want to use subversion or git? The ASF allows you to create a special branch in git (i.e. “gossip-site”) containing

Re: Post-0.1.1 release actions

2017-02-03 Thread P. Taylor Goetz
Edward, The staging repository in nexus is ready, all you have to do is click on the Release button for 1002, and Drop the earlier rcs. -Taylor > On Feb 3, 2017, at 4:03 PM, Edward Capriolo wrote: > > On Fri, Feb 3, 2017 at 3:36 PM, Josh Elser

Re: [Discuss] rename Apache Gossip to Apache Consensus

2017-02-22 Thread P. Taylor Goetz
Before going though the pain of a rename, I would suggest checking with trademarks@ to make sure the name “Apache Consensus” is suitable (i.e. a PODLINGNAMESEARCH JIRA would be approved). You don’t want to rename, only to have to rename again. -Taylor > On Feb 22, 2017, at 10:31 AM, Edward

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

2017-01-19 Thread P. Taylor Goetz
10, 2017, at 11:56 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > The vote for gossip-0.1.1-incubating (RC2) has passed! > > The votes were: > > Josh Elser +1 > P. Taylor Goetz +1 > Gary Dusbabek +1 > Chandresh Pancholi +1 > Edward Capriolo +1 > > T

Re: [VOTE] Release Apache Gossip

2016-10-07 Thread P. Taylor Goetz
The typical process is to have a DISCUSS thread before and official VOTE thread, but I assume that was the intent here. I’m +1 for moving forward with a release. Here are some links to some light reading about the process [1][2]. A quick check of the gossip repo reveals the following that need

Re: [VOTE] Release Apache Gossip

2016-10-07 Thread P. Taylor Goetz
gt; +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.

Re: [VOTE] Release Apache Gossip

2016-10-27 Thread P. Taylor Goetz
>>>> 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. >>>>>>> >>>>>>> >>>>>>>

Re: [VOTE] Release Apache Gossip

2016-10-27 Thread P. Taylor Goetz
Done. -Taylor > On Oct 27, 2016, at 11:58 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > > I’ll take care of it. > > -Taylor > >> On Oct 27, 2016, at 11:43 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: >> >> The reply in the ticket is:

Re: [VOTE] Release Apache Gossip

2016-11-09 Thread P. Taylor Goetz
AVEN/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) &g

Re: [VOTE] Release Apache Gossip

2016-11-09 Thread P. Taylor Goetz
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

Re: [VOTE] Release Apache Gossip

2016-11-18 Thread P. Taylor Goetz
gt; Josh Elser wrote: >> For the promotion to Central, this can happen after the Gossip PPMC and >> IPMC votes both pass. When you "promote" the repository, it will be >> automatically mirrored to Central for you. >> >> The only manual steps will be updating the S

Re: One session on Gossip codebase

2016-11-18 Thread P. Taylor Goetz
When scheduling any “live” meeting, it would be good to poll the dev@ mailing list for timezones and schedule accordingly to maximize potential participation. I would also suggest announcing any meeting at least 72 hours before it takes place. And when holding any off-list meetings, its

Re: [VOTE] Release Apache Gossip

2016-11-17 Thread P. Taylor Goetz
>>>>> (836 B at 2.6 KB/sec) >>>>> [INFO] [INFO] >>>>> ---- >>>>> >>>>> [INFO] [INFO] BUILD SUCCESS >>>>> [INFO] [INFO] >>>&

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

2017-01-03 Thread P. Taylor Goetz
Josh is correct that there is some wiggle room on this specific issue (json.org license). The wiggle room is that existing projects have a grace period for removing the json.org dependency, with the deadline I think being June 2017. Since Gossip has yet to make a release, I would lean toward

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

2017-01-04 Thread P . Taylor Goetz
+1 I checked: - DISCLAIMER exists - NOTICE looks good. - LICENSE looks good - License headers present - Can build from source (though I had to skip tests. I got the same failures as Josh). - Signatures/hashes check out. Nice work on the quick turnaround. -Taylor > On Jan 3, 2017, at 3:47 PM,

Re: Board report

2017-01-04 Thread P. Taylor Goetz
Comments in-line below. -Taylor > On Jan 4, 2017, at 3:24 PM, Edward Capriolo wrote: > > I completed the board report, I wanted to get the RC voting going before > doing the report. If anyone has any comments/ suggestions let me know. > > The report is due today (sorry

Re: Board report

2017-01-04 Thread P. Taylor Goetz
see the updated report in my last email. > > On Wed, Jan 4, 2017 at 4:21 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > >> Comments in-line below. >> >> -Taylor >> >>> On Jan 4, 2017, at 3:24 PM, Edward Capriolo <edlinuxg...@gmail.com> >>

Re: [GSoC 2017] CRDT Umbrella

2017-03-10 Thread P. Taylor Goetz
Welcome to the Gossip community Mirage! Looks like you and Edward are working together well on scoping out the work. Well done. -Taylor > On Mar 10, 2017, at 7:00 PM, Edward Capriolo wrote: > > On Fri, Mar 10, 2017 at 4:46 PM, Mirage Abeysekara

Re: Vision letter, reqest for discussion

2017-07-18 Thread P. Taylor Goetz
> On Jul 11, 2017, at 11:15 AM, Русак Максим wrote: > > "Features for features" is not our goal. "Features for solving users' pain" > have sense. I would propose rephrasing that to “Features that make Gossip useful” is the goal. > On Jul 11, 2017, at 12:58 PM, Edward

Incubator/Board Report Due

2018-04-06 Thread P. Taylor Goetz
Anyone willing or available to produce a Report? Failure to report is a sign of trouble. Is it time to think about retirement? I don’t see a lot of activity. That being said, there’s nothing inherently wrong with retiring, it’s just another exit point. There’s nothing to stop development

Re: Podling Report Reminder - May 2018

2018-04-30 Thread P. Taylor Goetz
Anyone willing to take this up? Since Gossip failed to report last cycle, a solid report this month might preempt concerns from the IPMC and/or board as to the viability of the project. Reports may be a nuisance, but not a big ask, especially after you go from monthly to quarterly. Not