To clarify just in case it's not clear (I had to read it twice to get
it): notifications@f.a.o[1] is what Christopher meant by "the
notifications list" and is probably the discussion you're looking for,
Bertrand :)
[1] https://lists.apache.org/list.html?notificati...@fluo.apache.org
On 7/10/17 10:29 AM, Christopher 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. We're a R-t-C
community, and a lot of that discussion occurs during code reviews on the
issue tracker. We've found that works very well. For ASF tracking purposes,
it relies on infra services to CC the notifications list. New users can get
up to speed by looking at the history there, but it's probably much easier
to dive in to the documentation on the website and browse the discussions
on the issue tracker threads.
On Mon, Jul 10, 2017, 07:34 Bertrand Delacretaz <bdelacre...@codeconsult.ch>
wrote:
Hi,
It looks like Fluo is indeed ready to graduate but I have a question
about its dev list usage.
I had a look at the Fluo dev list archive,
https://lists.apache.org/list.html?d...@fluo.apache.org
There's very little going on there in terms of technical discussions
and decisions, most of the traffic (and that's not much) seems to be
about project governance topics.
Can someone from Fluo comment on that vs. "if it didn't happen on the
dev list it didn't happen" ?
Are open asynchronous discussions happening elsewhere, and how do you
see newcomers getting up to speed?
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
