+1! I have ideas regarding the meeting structure and observations of things I've seen work well, but I think it's best to evaluate what is necessary based upon who comes forward and the content of the meetings. On a basic level, I think this will improve transparency of what's actively being developed in the community, and pull some new folks into the mix.
Dave On Wed, Apr 16, 2014 at 3:12 PM, Henry Saputra <henry.sapu...@gmail.com>wrote: > +1 > > The Apache Helix does the similar thing and seems like it helps flush > clearing up out questions and validate new ideas/proposals. > > Just a reminder the chat transcript need to be recorded and > rebroadcasted to dev@ list. > > Not sure how diverse Aurora dev community is but Apache Helix > alternates each week between mornings (10am) and evenings (10pm) > > > - Henry > > On Wed, Apr 16, 2014 at 2:51 PM, Bill Farner <wfar...@apache.org> wrote: > > We've had a request for a periodic meeting on #aurora as an opportunity > for > > users and developers to engage. I think this is a great idea, and i > would > > love to make it happen. > > > > I'd appreciate feedback on: > > > > *Date/time* - Mondays 11 AM - 12 PM Pacific time. Please speak up if > this > > is a bad time for you. > > > > *Format* - my initial (perhaps lazy) thought is to begin without a > > pre-defined format, and shape the meeting over time. We could open with > a > > discussion of tickets we expect to close in the coming week, hopefully > not > > overlapping with JIRA too much. > > > > Interested in what you all think! > > > > > > -=Bill >
