On Mon, May 29, 2017 at 9:49 PM, Terry Weymouth <weymo...@umich.edu> 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
> about a quarter of the way through. See:
> https://github.com/Terry-Weymouth/incubator-gossip/tree/example-setup <
> https://github.com/Terry-Weymouth/incubator-gossip/tree/example-setup>
>
> While browsing around in the GitHub site, I ran across a branch in which
> gossip-examples is in a module on its own: https://github.com/gdusbabek/
> incubator-gossip/tree/gossip_manager_coupling <
> https://github.com/gdusbabek/incubator-gossip/tree/gossip_manager_coupling>
> .
>
> Based on my experience over the last couple of weeks, in the process of
> (still) coming up to speed on Gossip, this separation seems an excellent
> idea. What are the plans for merging a separate gossip-examples module into
> the master branch, if any?
>
> If there is something that makes sense for me to use, I’d love to
> pull/merge that effort so that my work could build on top of the examples
> in a separate module. It make so much sense; clarifies usage.
>
> Terry.
>
>
>
> Terry,

The normal use/user of Gossip would be embedding it in something else a
nosql database or a web server, some other piece of software where they
wish to share information or member state.

The stand alone examples are essentially are a way for the end-user(like
you) to interact with the project without me saying "run the unit tests".

I would love to get your markdown into the project and coupling that with a
new module seems liek a good idea to me.

Please read our guide on contributing code.
https://cwiki.apache.org/confluence/display/GOSSIP/Apache+Gossip+contribute+code

We have already talked about this enough so you can start from the part
"Create a JIRA ticket" and submit a patch with the examples moved out into
a module and your markdown.

I will help usher the process.

Thanks
Edward

Reply via email to