I can see the value of the IRC, but not to discuss plans and that stuff. As Ross pointed out, in the ASF, everything must be done in the mailing list, otherwise it never happened. This is one of the gold rules of the ASF, and we need to be careful about respecting the established procedures.
That said, the IRC is a very good place to have discussions about code reviews, design, implementation and that kind of things. Also to start some PoCs with new stuff, experiments, etc. We also have the channel logs [1], so people in different timezones can read the discussions later, if interested. That shouldn't make the IRC the place to make decisions, though. IMO it would be good to define the plans, roadmap, etc, in the mailing list, and the IRC can be used as a discussion room, when needed, about the implementation details, as it is more agile to share code, links, etc. I. [1] https://botbot.me/freenode/jclouds/ On 20 January 2015 at 20:34, Andrew Phillips <aphill...@qrmedia.com> wrote: >> There is a reason ASF projects don't encourage synchronous meetings. It's >> OK to have them, but be aware that they are exclusionary and typically bad >> practice. >> >> If the team go ahead then remember no decisions can be made in these >> meetings, only proposals can be drawn up to be brought to this list. > > > Thanks for the insight, Ross! > > ap
