Welcome Aaron! I think we need to update our release process docs. They may be out of date. We've tried to simplify and automate things a bit further, so anybody can do a release.
On Wed, Nov 2, 2016 at 5:36 PM Aaron D. Mihalik <[email protected]> wrote: > I took you all up on your offer and joined the fluo dev list :) > > And may I say: Excellent documentation and processes! Spent a lot of time > referring to your release process documentation and inspecting your git > repo while I was cutting the first Rya release. Thanks for the excellent > and clean examples. > > --Aaron > > On Wed, Nov 2, 2016 at 5:30 PM Josh Elser <[email protected]> wrote: > > > Keith Turner wrote: > > > On Tue, Nov 1, 2016 at 10:57 PM, Christopher<[email protected]> > > wrote: > > >> > I think growing our community is really the only outstanding area > of > > >> > concern (with respect to graduation) that we need to work on. > > However, I'm > > >> > not sure how we can do that. One thing is that we could reach out > to > > Rya, > > >> > and any other developers who are using Fluo that we know about, to > > >> > explicitly invite them (rather than wait for them to come to us). > > >> > > > >> > Aside from that, I'm not sure what else we can do. Maybe we could > > spend > > > > > > I think we can also give talks to help raise awareness. > > > We can create integration with other communities (like Kafka and Nifi) > > > and then blog within those communities. > > > We can also blog about possible integration with other communites... > > > like maybe Fluo could be used with Presto to keep a secondary index up > > > to date.. we could blog about how we would think that would work. > > > > > > > Everybody loves secondary indexing ;). In general, this kind of > > cross-pollination is a great way to get people interested. > > > > Blogs, tutorials, presentations are a great way to help find these kinds > > of people that you can get involved in Fluo. > > >
