charms.reactive bi-weekly sync recap

[Antonio Rosales]

On Tue, Feb 14, 2017 at 7:21 AM, Cory Johns <cory.johns at canonical.com> wrote:
> Merlijn, Stuart, Alex, Tim, and I had our bi-weekly charms.reactive sync
> today.
>
> We have had some good exploration of ideas for the future of reactive over
> the last two weeks in the form of Issues on the repo.  This seems to be
> working well for us so far, and allows for anyone to join in the discussion
> (go to https://github.com/juju-solutions/charms.reactive/issues to join in),
> so we will continue with discussions there and in PRs on that repo.  One
> change that we will make is to create a PR with a consolidated "2.0 use
> cases" documentation.  This will serve as both a more consolidated and
> concrete set of examples of the ideas discussed in the "[discussion]"
> issues, as well as becoming the documentation for reactive once those
> features are implemented.
>
> The sync also allowed us to clean up some outstanding PRs and, thanks to
> Stuart and Tim, we resolved an upstream issue that was causing our Travis
> builds to fail.  We now have passing CI on our PRs again.  :)
>
> Our next sync will be two weeks hence, but collaboration will continue on
> the repo, IRC, and here on this mailing list.

Cory,

Thanks for the update, and the pointers to where folks can go to
continue the discussion.

-Antonio