> Code reviews happens after the fact but sometimes a wild idea needs to be discussed and fleshed out for a while before code can be written. > Could you provide an example of such a discussion? Links to the relevant messages are good enough, just to understand how/where things happen.
Developers typically create a GitHub issue if they have a wild idea. Discussion happens on the issue. If someone decides to do the work, they can mention the issue in their pull request. This can happen using email but I prefer communication on GitHub (or a similar tool like GitLab) due to the seamless linking between issues, pull requests (i.e code reviews), and commits. I find it much easier to view all communication regarding a commit or an issue if everything is done on GitHub rather than a combination of tools (like email, JIRA, review board, etc). Below is a link to our the most commented issues from all Fluo repositories to give you examples of our work flow: https://github.com/search?o=desc&p=1&q=is%3Aissue+repo%3Aapache%2Fincubator-fluo+repo%3Aapache%2Fincubator-fluo-recipes+repo%3Aapache%2Fincubator-fluo-website+&s=comments&type=Issues&utf8=%E2%9C%93 On Tue, Jul 11, 2017 at 3:39 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi, > > On Mon, Jul 10, 2017 at 4:29 PM, Christopher <ctubb...@apache.org> wrote: > > ...As a project which was born and raised on GitHub, Fluo makes very > heavy use > > of the issue tracker for day to day decision making and asyncronous > > discussions, using GitHub issues and pull requests.... > > Ok, thanks for explaining. > > > ...We're a R-t-C > > community, and a lot of that discussion occurs during code reviews on the > > issue tracker.... > > Code reviews happens after the fact but sometimes a wild idea needs to > be discussed and fleshed out for a while before code can be written. > > Could you provide an example of such a discussion? Links to the > relevant messages are good enough, just to understand how/where things > happen. > > I don't think this has impact on the Fluo graduation but I'd like to > understand better as I suppose your communication patterns are common > for projects born on GitHub. It's important IMO that the Incubator > understands them, to be able to evaluate whether our podlings are run > in a way that's compatible with the ASF view on asynchronous open > discussions. > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
