On Wed, Feb 15, 2017 at 11:50 AM, Kiran Mathews <[email protected]> wrote:
> Hai Edward, > > Thanks for your wonderful introduction. > > An official IRC sounds interesting. > > By the way, I also watched your intro video in Youtube. Now I am reading > the article “Network-Friendly Gossiping” to get more clear picture. > Network-Friendly Gossiping disuses more social networks (ER, scale free, > ....) and youtube videos describes more it as a kind "Dynamic Topology > Detection". So, could you describe some use cases (examples) of the project > ? > > Also I am going through the source code. > > I hope that would be the first step, or is there any suggestion from you to > get started (some research papers, articles or anything else)? > > About issues in jira, whether the reporter is deciding the assignee ?? > > About git stars (done) and blogging , i will do it ;-) > > Regards, > Kiran Mathews > > On Wed, Feb 15, 2017 at 4:19 PM, Edward Capriolo <[email protected]> > wrote: > > > On Wed, Feb 15, 2017 at 6:55 AM, Kiran Mathews <[email protected] > > > > wrote: > > > > > (Sorry for the previous incomplete mail) > > > > > > Hallo, > > > > > > I am Kiran Mathews. I wish to contribute to this project during my free > > > time. > > > > > > My skills are: > > > > > > - Distributed wireless protocols > > > - Ad-hoc algorithms > > > - SDL > > > - Research experience in Mac Layer and Network layer protocols > > > - Also, I can Code ;-) > > > > > > I hope, I contribute to this project with my current skills and learn > > > something new. > > > > > > Regards > > > > > > Kiran Mathews > > > > > > On Wed, Feb 15, 2017 at 12:48 PM, Kiran Mathews < > > [email protected]> > > > wrote: > > > > > > > Hallo, > > > > > > > > I am Kiran Mathews. I wish to contribute to this project during my > free > > > > time. > > > > > > > > My skills, > > > > > > > > > > > > > > > > > > > Kiran, > > > > Welcome! > > > > It sounds like we can learn a lot from your participation. > > > > In the spirit of of the http://theapacheway.com/ "They work side by > side > > with contributors who are simply “scratching their own itch”: people who > > simply want to fix their own problems, but who find it's often easier to > do > > that in concert with others as it is to do alone." > > > > To "scratch your own itch" we are open to contributors suggesting and > > adding features that they find are important. The project is new and > fairly > > open in direction, but we want to keep things in scope. (IE a new object > -> > > RDBMS mapper would not fit in Gossip. ) > > > > There are many ways to be involved: > > - participate in conversations on this list. Even a reply with +1 to a > > DISCUSS thread shows that people are out there and listening > > - follow https://github.com/apache/incubator-gossip (stars help) > > - HELP WITH CODE REVIEWS. This is something we can use. Many of the code > > reviews would only take someone who knows how to read/write idiomatic > java > > - pick up an open issue https://issues.apache.org/jira/browse/GOSSIP > > - write blogs and evangelize > > - suggest and implement your own ideas > > > > I have been talking with people directly over gmail chat and IRC. We > should > > probably make an official IRC channel soon. > > > > Myself and some others are here to guide you along if yo have time to be > > involved. Feel free to reach out to me directly > > > > Thanks, > > Edward > > > So, could you describe some use cases (examples) of the project? In general Gossip is used in a few places. NoSQL databases 9Cassandra) and grid computing platforms (hama/spark). We are looking to build a shared component that can be used for a variety of tasks. There are several Apache projects that use a Gossip layer to function. We eventually want to consider integrating there. My main hypothesis is that many applications require some type of coordination/ data sharing. Typically they solve this by introducing another component like RDBMS or Zookeeper, or a NodeManager to handle this task, but in many cases the application itself with the help of Gossip could do this directly. About issues in jira, whether the reporter is deciding the assignee ?? In Jira if there is no 'assignee' that means the issue is free to take up. If the issue has an assignee but has no progress for a while it is good form to ask if you can help/take over the issue. However because of SPAM bots we have to grant your id access to be assigned issues. If you comment on an issue or send me an email with your Jira id I can add you to the contributors group.
