Re: [VOTE] Retire Gossip

+1 On Mon, Aug 6, 2018 at 1:20 PM, Gary Dusbabek wrote: > +1 > > On Mon, Aug 6, 2018 at 11:48 AM 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

Re: [DISCUSS] Leave apache and the incubator

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

Re: [DISCUSS] Leave apache and the incubator

;; "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> wr

Re: [DISCUSS] Leave apache and the incubator

> > 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: &g

Re: [DISCUSS] Leave apache and the incubator

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

Re: [DISCUSS] Leave apache and the incubator

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

Re: [DISCUSS] Leave apache and the incubator

er, 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 >> a

Re: [DISCUSS] Leave apache and the incubator

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

Re: [DISCUSS] Leave apache and the incubator

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

[DISCUSS] Leave apache and the incubator

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

Re: Podling Report Reminder - June 2018

I handled the report. I should have confirmed if my report from last month would be sufficient or not to reset the clock. Thanks, Edward I have a few things reviewed and ready to be merged, I had some environmental issues with apache ssh, and have those lined up now. On Sat, Jun 9, 2018 at 9:46

Re: Podling Report Reminder - June 2018

John, I put my report into the May report last month. I realize it was late so I can include that information in this months report again if you wish. There has been some traction. I started reviewing some of the open PRs. I was blocked up for a while because my PGP key was on a laptop I moth

Re: Podling Report Reminder - May 2018

high hopes Thanks, On Tue, May 8, 2018 at 10:44 PM, John D. Ament <johndam...@apache.org> wrote: > Thus far no report has been submitted. As an ASF project, you're expected > to report to the board on a quarterly basis. > > John > > On 2018/05/01 04:11:36, Edward Capriol

Re: Podling Report Reminder - May 2018

Yes. I got it. On Tue, May 1, 2018 at 12:10 AM, P. Taylor Goetz wrote: > 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. > >

Re: Any pulse?

-1 on retirement. On Fri, Apr 6, 2018 at 6:17 PM, Juby Victor <juby.vic...@gmail.com> wrote: > +1 > > Regards, > Juby > > > On Apr 6, 2018, at 11:11 PM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > > > > I am still around. Let me think on th

Re: Podling Report Reminder - January 2018

Yes. I will put this together by 3:00 pm EST. On Wed, Jan 3, 2018 at 11:47 AM, Josh Elser 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

[jira] [Commented] (GOSSIP-69) Implement Crdt mvregister

[ https://issues.apache.org/jira/browse/GOSSIP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287673#comment-16287673 ] Edward Capriolo commented on GOSSIP-69: --- You are free to work on it. > Implement Crdt mvregis

[jira] [Commented] (GOSSIP-51) Consider alternative consensus based protocols

[ https://issues.apache.org/jira/browse/GOSSIP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16227407#comment-16227407 ] Edward Capriolo commented on GOSSIP-51: --- You can fell free to take this over. > Consider alternat

Re: Podling Report Reminder - October 2017

I would like to prepare for next month if possible. I can get the write up together today but I would rather not rush it. Edward On Wed, Oct 4, 2017 at 7:01 AM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC.

[jira] [Commented] (GOSSIP-99) Cast Error while using equals and RemoteGossipMember

[ https://issues.apache.org/jira/browse/GOSSIP-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177797#comment-16177797 ] Edward Capriolo commented on GOSSIP-99: --- is this comparison ever done in the current codebase

[jira] [Updated] (GOSSIP-41) Transfer gossip data in bulk

[ https://issues.apache.org/jira/browse/GOSSIP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-41: -- Fix Version/s: 0.1.3 > Transfer gossip data in b

[jira] [Assigned] (GOSSIP-75) Voting interface

[ https://issues.apache.org/jira/browse/GOSSIP-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo reassigned GOSSIP-75: - Assignee: Mirage Abeysekara > Voting interface > > >

[jira] [Resolved] (GOSSIP-75) Voting interface

[ https://issues.apache.org/jira/browse/GOSSIP-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-75. --- Resolution: Fixed Merged to master. Great job I can not wait to start playing with the feature

Re: Documentation for GOSSIP-55, GOSSIP-88 and GOSSIP-75

I would say the best way now is to get yourself confluence wiki access and add the documentation there. On Wed, Aug 23, 2017 at 1:16 PM, Mirage Abeysekara wrote: > Hi all, > > I wrote draft documentations for the following new features, > > GOSSIP-55:

Re: Contribution to apache gossip

e as far as functionality is >> concerned. I need to take a stab at understanding the code flow again, and >> think through the entire flow, which might take a day or two. After that I >> will come up with a more detailed design, and maybe more questions :) >> >> Thanks &

[jira] [Created] (GOSSIP-96) Create a multi node per request coordinator.

Edward Capriolo created GOSSIP-96: - Summary: Create a multi node per request coordinator. Key: GOSSIP-96 URL: https://issues.apache.org/jira/browse/GOSSIP-96 Project: Gossip Issue Type: Sub

[jira] [Updated] (GOSSIP-93) Create Operation Target interface and Linear implementation

[ https://issues.apache.org/jira/browse/GOSSIP-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-93: -- Description: Create an interface to organize select which nodes should be the target

[jira] [Created] (GOSSIP-94) Create latitude/longitude based targeting

Edward Capriolo created GOSSIP-94: - Summary: Create latitude/longitude based targeting Key: GOSSIP-94 URL: https://issues.apache.org/jira/browse/GOSSIP-94 Project: Gossip Issue Type: Sub

[jira] [Created] (GOSSIP-93) Create Operation Target interface and Linear implementation

Edward Capriolo created GOSSIP-93: - Summary: Create Operation Target interface and Linear implementation Key: GOSSIP-93 URL: https://issues.apache.org/jira/browse/GOSSIP-93 Project: Gossip

[jira] [Assigned] (GOSSIP-70) Build a GeoMetric/GridQuorum model

[ https://issues.apache.org/jira/browse/GOSSIP-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo reassigned GOSSIP-70: - Assignee: Ankur Agrawal (was: Maxim Rusak) > Build a GeoMetric/GridQuorum mo

[jira] [Updated] (GOSSIP-87) Unused workQueue in gossipCore

[ https://issues.apache.org/jira/browse/GOSSIP-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-87: -- Fix Version/s: 0.1.3 > Unused workQueue in gossipC

[jira] [Resolved] (GOSSIP-87) Unused workQueue in gossipCore

[ https://issues.apache.org/jira/browse/GOSSIP-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-87. --- Resolution: Fixed Merged. Thank you so much. If you find any other issues (cleanup

[jira] [Assigned] (GOSSIP-87) Unused workQueue in gossipCore

[ https://issues.apache.org/jira/browse/GOSSIP-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo reassigned GOSSIP-87: - Assignee: Pooya Salehi > Unused workQueue in gossipC

[jira] [Commented] (GOSSIP-35) Different payloads can be transmitted at different rates

[ https://issues.apache.org/jira/browse/GOSSIP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110800#comment-16110800 ] Edward Capriolo commented on GOSSIP-35: --- Good analysis. {quote} Should we support overriding

[jira] [Commented] (GOSSIP-70) Build a GeoMetric/GridQuorum model

[ https://issues.apache.org/jira/browse/GOSSIP-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110167#comment-16110167 ] Edward Capriolo commented on GOSSIP-70: --- Some things we need: # a function that given a Member

[jira] [Resolved] (GOSSIP-88) Data Replication Control

[ https://issues.apache.org/jira/browse/GOSSIP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-88. --- Resolution: Fixed Committed thanks! Great work! > Data Replication Cont

Re: Contribution(s) Agreement , IRC

On Monday, July 31, 2017, wrote: > Hi Folks > > Wanted to check if we we need to get any contributions agreement signed > off by the current employer for working on the project. > > Also do we plan to have an IRC channel setup > > Apologies if these has been answered

[jira] [Commented] (GOSSIP-35) Different payloads can be transmitted at different rates

[ https://issues.apache.org/jira/browse/GOSSIP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107435#comment-16107435 ] Edward Capriolo commented on GOSSIP-35: --- I assigned this issue to you [~jubyvictor]. Let me know how

Re: Contribution to apache gossip

On Sun, Jul 30, 2017 at 10:59 PM, Ankur Agrawal wrote: > Hi > > Not sure if my previous email one week ago did actually get delivered. So I > apologize for resenting in advance. > > My name is Ankur. I am a student, and I am keenly interested in, and want > to

Re: Vision letter, reqest for discussion

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 <edlinuxg...@gmail.com> > wrote: > > > > There is no simple answer. I think the primary vehicle is bloggin

[jira] [Resolved] (GOSSIP-66) Implement Crdt 2P-Set

[ https://issues.apache.org/jira/browse/GOSSIP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-66. --- Resolution: Fixed Fix Version/s: 0.1.3 > Implement Crdt 2P-

[jira] [Commented] (GOSSIP-66) Implement Crdt 2P-Set

[ https://issues.apache.org/jira/browse/GOSSIP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090754#comment-16090754 ] Edward Capriolo commented on GOSSIP-66: --- Looks good. Thanks much. Merged. > Implement Crdt 2P-

Re: Vision letter, reqest for discussion

think there is any need for them right now, > personally. They are a scratch with no itch. :) > > Gary. > > > On Tue, Jul 11, 2017 at 11:58 AM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > > > On Tue, Jul 11, 2017 at 11:15 AM, Русак Максим <mak-ru...@yandex.ru&g

[DISCUSS] next release

It has been a while since our last release. Would anyone be interested in learning the release process? Edward -- Sorry this was sent from mobile. Will do less grammar and spell check than usual.

[jira] [Resolved] (GOSSIP-92) crdt/CrdtAddRemoveSet.java missing license header

[ https://issues.apache.org/jira/browse/GOSSIP-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-92. --- Resolution: Fixed > crdt/CrdtAddRemoveSet.java missing license hea

[jira] [Updated] (GOSSIP-92) crdt/CrdtAddRemoveSet.java missing license header

[ https://issues.apache.org/jira/browse/GOSSIP-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-92: -- Affects Version/s: (was: 0.1.3) > crdt/CrdtAddRemoveSet.java missing license hea

Re: Podling Report Reminder - July 2017

Josh, I just filled it out. Thanks, Edward On Wed, Jul 5, 2017 at 1:23 PM, Josh Elser 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

[jira] [Commented] (GOSSIP-92) crdt/CrdtAddRemoveSet.java missing license header

[ https://issues.apache.org/jira/browse/GOSSIP-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074911#comment-16074911 ] Edward Capriolo commented on GOSSIP-92: --- If you name your branch GOSSIP-92 they pull information

[jira] [Resolved] (GOSSIP-91) Random test failure in SharedDataEventTest

[ https://issues.apache.org/jira/browse/GOSSIP-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-91. --- Resolution: Fixed Changes are done. Thanks [~mirage20] and Terry for fixing and running

[jira] [Updated] (GOSSIP-91) Random test failure in SharedDataEventTest

[ https://issues.apache.org/jira/browse/GOSSIP-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-91: -- Fix Version/s: 0.1.3 > Random test failure in SharedDataEventT

Re: Spuratic test failure:

umber? > On Jun 25, 2017, at 3:38 PM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.194 sec > <<< FAILURE! - in org.apache.gossip.SharedDataEventTest > CrdtDataChangeE

[jira] [Resolved] (GOSSIP-64) Implement Max-Change-Sets

[ https://issues.apache.org/jira/browse/GOSSIP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-64. --- Resolution: Fixed Looks good. Thank you > Implement Max-Change-S

[jira] [Commented] (GOSSIP-64) Implement Max-Change-Sets

[ https://issues.apache.org/jira/browse/GOSSIP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064082#comment-16064082 ] Edward Capriolo commented on GOSSIP-64: --- Resolved with minor fixes. Class names are Lww not LWW

[jira] [Updated] (GOSSIP-64) Implement Max-Change-Sets

[ https://issues.apache.org/jira/browse/GOSSIP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-64: -- Fix Version/s: 0.1.3 > Implement Max-Change-S

Re: GOSSIP-90 Why call clock.nanotime() once?

The tests are flakey on my machine thry fail every other time in current state. On Sunday, June 25, 2017, Русак Максим wrote: > Why call clock.nanotime() once? > If you want to make tests more deterministic and don't rely on assumption > that between two commands there will

[jira] [Updated] (GOSSIP-62) Implement Crdt PN-Counter

[ https://issues.apache.org/jira/browse/GOSSIP-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-62: -- Fix Version/s: 0.1.3 > Implement Crdt PN-Coun

[jira] [Resolved] (GOSSIP-62) Implement Crdt PN-Counter

[ https://issues.apache.org/jira/browse/GOSSIP-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-62. --- Resolution: Fixed Nice job. Thanks much. > Implement Crdt PN-Coun

[jira] [Commented] (GOSSIP-62) Implement Crdt PN-Counter

[ https://issues.apache.org/jira/browse/GOSSIP-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062018#comment-16062018 ] Edward Capriolo commented on GOSSIP-62: --- Your merge() has to be immutable that is a critical piece

Re: GOSSIP-64 review

Maxim, To solicit reviews and interaction from the community you may want to provide more detail on the mailing list or in the ticket of what you worked on. Many people are not familiar with max-change-sets. inside the patch there is only a single link to an external resource. Consider sending

[jira] [Updated] (GOSSIP-55) Pub sub on data objects

[ https://issues.apache.org/jira/browse/GOSSIP-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-55: -- Fix Version/s: 0.1.3 > Pub sub on data objects > --- > >

[jira] [Resolved] (GOSSIP-55) Pub sub on data objects

[ https://issues.apache.org/jira/browse/GOSSIP-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-55. --- Resolution: Fixed This issue is merged. Great work. > Pub sub on data obje

[jira] [Commented] (GOSSIP-65) Implement crdt LWW-Element-Set

[ https://issues.apache.org/jira/browse/GOSSIP-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055060#comment-16055060 ] Edward Capriolo commented on GOSSIP-65: --- Great feature. Thanks much > Implement crdt LWW-Element-

[jira] [Updated] (GOSSIP-65) Implement crdt LWW-Element-Set

[ https://issues.apache.org/jira/browse/GOSSIP-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-65: -- Fix Version/s: 0.1.3 > Implement crdt LWW-Element-

[jira] [Resolved] (GOSSIP-65) Implement crdt LWW-Element-Set

[ https://issues.apache.org/jira/browse/GOSSIP-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-65. --- Resolution: Fixed > Implement crdt LWW-Element-

Re: CRDT data types

Maxim, Lets leave the pncounter to Terry now. You can tackle the other crdt tickets. On Tuesday, June 13, 2017, Terry Weymouth wrote: > Maxim, Pleasure to meet you. Delighted to be working on the CRDT data > types. As you may have noticed, Edward identified a list of small

Re: Mockito in gossip??

I am not a strong believer in mockito. Generally i believe that if you design things well you need less / no mockink. That said. Moving the end to end test to thier own module lowered code coverage. running mvn cobertura:cobertura and adding unit/mock tests to increase coverage is a good idea.

[jira] [Commented] (GOSSIP-86) Examples in separate module - Update Readme.

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16044735#comment-16044735 ] Edward Capriolo commented on GOSSIP-86: --- I tested this out today. It is much easier to study

[jira] [Created] (GOSSIP-87) Unused workQueue in gossipCore

Edward Capriolo created GOSSIP-87: - Summary: Unused workQueue in gossipCore Key: GOSSIP-87 URL: https://issues.apache.org/jira/browse/GOSSIP-87 Project: Gossip Issue Type: Bug

[jira] [Resolved] (GOSSIP-86) Examples in separate module - Update Readme.

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-86. --- Resolution: Fixed Thanks Terry. Good stuff. Hopefully you can do more of this. Very high

[jira] [Commented] (GOSSIP-86) Examples in separate module - Update Readme.

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037023#comment-16037023 ] Edward Capriolo commented on GOSSIP-86: --- My mistake. I assumed that out lira was setup

[jira] [Commented] (GOSSIP-86) Examples in separate module - Update Readme.

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036929#comment-16036929 ] Edward Capriolo commented on GOSSIP-86: --- [~weymouth] Terry. This looks good. patch_availabe

[jira] [Commented] (GOSSIP-86) Readme file for examples; examples in separate module

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035981#comment-16035981 ] Edward Capriolo commented on GOSSIP-86: --- This is a good idea. I would suggesting referencing

[jira] [Assigned] (GOSSIP-86) Readme file for examples; examples in separate module

[ https://issues.apache.org/jira/browse/GOSSIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo reassigned GOSSIP-86: - Assignee: Terry Weymouth > Readme file for examples; examples in separate mod

Re: Running the example: StandAloneNode

Terry, We are all volunteers and understand that things happen when they happen. Feel free to drop any emails to the list or catch up on IRC. Let us know what you learn as you go. Edward On Wed, May 31, 2017 at 3:57 PM, Terry Weymouth wrote: > Thanks. Will do. Holiday,

Re: Running the example: StandAloneNode

On Mon, May 29, 2017 at 9:49 PM, Terry Weymouth wrote: > Folks, > as a learning exercise, I started working on a README for the > examples package in gossip-base, org.apache.gossip.examples. > It is meant to be a “how to run the examples" for a new person, and I’m >

Re: Running the example: StandAloneNode

I think that since the video gossip-itest would be the module you can run it from. I thing soon we will do a moduke with something like gossip-uber that does the amagamation. On Saturday, May 27, 2017, Terry Weymouth wrote: > I thought it would be worthwhile to capture my

Re: Gossip (apache incubator)

On Fri, May 26, 2017 at 9:51 AM, Terry Weymouth wrote: > Edward, thanks! The second half of this video was very helpful! (I just > ignored the audio :-} ) > > https://www.youtube.com/watch?v=bZXZrp7yBkw=39s < > https://www.youtube.com/watch?v=bZXZrp7yBkw=39s> > It looks like

Re: [GSoC 2017] [Progress] Add Event Listeners to Data Objects and Implement Vote Based Locking

ps://twitter.com/MiRAGECreator > GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara > > On 24 May 2017 at 20:39, Edward Capriolo <edlinuxg...@gmail.com> wrote: > >> >> >> On Wed, May 24, 2017 at 10:24 AM, Mirage Abeysekara < >> mirage...@cse.mrt.ac

Re: Gossip (apache incubator)

Terry, "I’m running into typical start up problems; how to set things, constructing the first working example: that sort of thing." Understandable. There are two ways you can get apache Gossip from maven: https://mvnrepository.com/artifact/org.apache.gossip/gossip Or install a snapshot for

Re: [GSoC 2017] [Progress] Add Event Listeners to Data Objects and Implement Vote Based Locking

nI1zKIP > QTDN6RkDL_jEZc/edit?usp=sharing > > Thanks, > > *Mirage Abeysekara* > Undergraduate > Computer Science and Engineering > University of Moratuwa > Twitter: https://twitter.com/MiRAGECreator > GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara > > On 22 May

Re: [GSoC 2017] [Progress] Add Event Listeners to Data Objects and Implement Vote Based Locking

Mirage, We can keep a majority of communication on list but our mentor-mentee specific communications like updates can probably be personal to you and me. During reading your paper we discussed a need for a feature that would be tangential but important for your work. Currently all the shared

[jira] [Commented] (GOSSIP-84) Consistently use Clock or System for time.

[ https://issues.apache.org/jira/browse/GOSSIP-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999475#comment-15999475 ] Edward Capriolo commented on GOSSIP-84: --- [~RajkumarNatarajan] [~rajlcpsg] It looks like you have two

[jira] [Resolved] (GOSSIP-85) Move UDP server into transport from passive gossip thread

[ https://issues.apache.org/jira/browse/GOSSIP-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-85. --- Resolution: Fixed Assignee: Edward Capriolo Fix Version/s: 0.1.3 Thanks

[jira] [Updated] (GOSSIP-85) Move UDP server into transport from passive gossip thread

[ https://issues.apache.org/jira/browse/GOSSIP-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-85: -- Summary: Move UDP server into transport from passive gossip thread (was: UDP Server moved

[jira] [Commented] (GOSSIP-85) UDP Server moved to sub module

[ https://issues.apache.org/jira/browse/GOSSIP-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993178#comment-15993178 ] Edward Capriolo commented on GOSSIP-85: --- I think we are getting out of scope a bit. Lets just

Re: [jira] [Created] (GOSSIP-84) Consistently use Clock or System for time.

this JIRA to my id looks like I don't have permission. > > I have start watching this Issue. Could you please assign thi JIRA to me. > > Regards, > Rajkumar > > On Sat, Apr 29, 2017 at 10:14 AM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > > > Feel fr

[jira] [Created] (GOSSIP-85) UDP Server moved to sub module

Edward Capriolo created GOSSIP-85: - Summary: UDP Server moved to sub module Key: GOSSIP-85 URL: https://issues.apache.org/jira/browse/GOSSIP-85 Project: Gossip Issue Type: Improvement

[jira] [Commented] (GOSSIP-84) Consistently use Clock or System for time.

[ https://issues.apache.org/jira/browse/GOSSIP-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989891#comment-15989891 ] Edward Capriolo commented on GOSSIP-84: --- Rajkumar Natarajan wishes to work on this. > Consisten

[jira] [Resolved] (GOSSIP-81) Move code into separate packages for Jackson and UDP

[ https://issues.apache.org/jira/browse/GOSSIP-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-81. --- Resolution: Fixed Merged. Thank you. > Move code into separate packages for Jackson and

[jira] [Resolved] (GOSSIP-79) create gossip-transport-udp module

[ https://issues.apache.org/jira/browse/GOSSIP-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-79. --- Resolution: Fixed Merged... good stuff > create gossip-transport-udp mod

[jira] [Resolved] (GOSSIP-80) Sundry cleanups

[ https://issues.apache.org/jira/browse/GOSSIP-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo resolved GOSSIP-80. --- Resolution: Fixed Fix Version/s: 0.1.3 Merged in. Thank you. > Sundry clean

[jira] [Updated] (GOSSIP-78) Convert to multi-module maven project

[ https://issues.apache.org/jira/browse/GOSSIP-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-78: -- Description: Without modifying any code, convert the project to a multi-module maven project

[jira] [Updated] (GOSSIP-79) create gossip-transport-udp module

[ https://issues.apache.org/jira/browse/GOSSIP-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-79: -- Description: Create a transport module that houses the UDP transport. This will probably

[jira] [Updated] (GOSSIP-79) create gossip-transport-udp module

[ https://issues.apache.org/jira/browse/GOSSIP-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated GOSSIP-79: -- Description: Create a transport module that houses the UDP transport. This will probably

Re: service layers

ringboot, etc. It > would probably make sense to do this earlier, rather than wait. A nice > side-effect is that it will force us to thinking about getting > component/layer encapsulation right. > > Gary. > > On Wed, Apr 12, 2017 at 1:25 PM, Edward Capriolo <edlinuxg...@gm

Re: service layers

On Wed, Apr 12, 2017 at 2:06 PM, Gary Dusbabek wrote: > I have a few questions: > > 1. Interchangeable Transports: Is there support for adding transports > beyond UDP? I can see some utility for TCP-based transports. > > 2. Interchangeable Protocols: JSON is great for some

Three cheers for our two GSOC applicants Mirage Abeysekara and Maxim Rusak

All, I wanted to take a moment to thank Mirage and Maxim for getting in Google Summer Of Code applications in. Besides having interesting proposals the both of you contributed to the Gossip before the GSOC period, which I do personally appreciate as well. Let me also say: You are great coders!

Re: Vote Based Locking - Design

pdated the Vote Based > Locking design document. > > Thanks > > *Mirage Abeysekara* > Undergraduate > Computer Science and Engineering > University of Moratuwa > Twitter: https://twitter.com/MiRAGECreator > GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara &

Slicer: autosharding

https://www.usenix.org/system/files/conference/osdi16/osdi16-adya.pdf Several things that might be of interesting to us

Re: Vote Based Locking - Design

On Wed, Mar 29, 2017 at 3:45 AM, Mirage Abeysekara wrote: > Hi all, > > The following document contains the draft design of locking protocol for > Apache Gossip which is based on voting. Any suggestions or feedback is > highly appreciated. > >

  1   2   3   >