Why not use to IRC instead? Airflow_users for user user related questions and airflow_dev for developing related questions. Both obviously open to anyone but with a different topic. With a good channel bot archives will be available automatically and public. If really needed a log can even be sent to the mailing list.
Or whatever else that allows a faster stream and topic based discussion publicly. B. Sent from my iPhone > On 22 aug. 2016, at 20:42, Chris Nauroth <cnaur...@hortonworks.com> wrote: > > I agree with Jakob. Please make these changes. Additionally, I ask that if > any prior discussion on the private Gitter channel culminated in a > significant project decision (design choice, whether or not to commit a pull > request, etc.), then please recap that publicly on ASF infrastructure > (mailing list, JIRA, etc.). If any of the discussion was a PMC decision that > legitimately needed a restricted audience, then please use the private > mailing list. > > --Chris Nauroth > > On 8/22/16, 11:29 AM, "Jakob Homan" <jgho...@gmail.com> wrote: > > Hey all- > Apparently there is a private channel being used for project > discussion on gitter (the archive would be here: > https://gitter.im/apache/incubator-airflow/Airflow_committers/archives/all, > similar to the public archive of the regular gitter channel: > https://gitter.im/apache/incubator-airflow/archives/all), titled > "Airflow_committers." > > As has been discussed before, all non-PMC level ASF communication > *has* to be in a public accessible forum (preferably that is archived > to an ASF list). Even if well intentioned, these channels are > exclusionary and absolutely verboten per ASF. > > We need to open or shut that channel down and make sure we note this > on the next IPMC report... > > -Jakob > > >
