And, as it seems comments in confluence are not enabled:
* At apache we encourace asynchronous communication over synchronous communication (We’re all spead out around the world. A project focusing on synchronous communication excludes folks living on the other side of the earth. Therefore it is beneficial to keep as much as possible on asynchronous media, such as email, jira, github) * Even if video-chats are cool, it excludes others even more. Some times community members ar not native speakers and they feel intimidated by the idea of having to speak … here too email and alike have the benefit of allowing the others to write their responses with the time they need. * Regarding tools: Next to Confluence, Github also has some nice Wiki Functions … definitely worth looking into. So … enough un-asked-for mumbling of an interested participant :-) Have a nice weekend. Chris Von: Christofer Dutz <[email protected]> Datum: Freitag, 21. Juli 2023 um 21:53 An: [email protected] <[email protected]> Betreff: AW: [DISCUSS] Communication within Apache One form of communication I haven’t seen in the proposals: GitHub GitHub allows discussions via Issues, Pull Requests and Discussions. If enabled, they can be automatically forwarded to the mailing-lists. And here I’d be happy to help setup things to be a bit more manageable, as the default settings suck (please excuse my French ;-) ) Also, would I like to distinguish between a project-dependent slack instance and the Apache slack instance where we could have KIE channels. I would propose to use the ASF Slack instance, as only this is backed-up and archived for later searches. Last bit of advice from an apache mentor: I would strongly not encourage to adopt the rules of a “famous project” … every project is different, and every community is different. So please, instead of inheriting the rules of a huge and mature project, start with as little as possible rules and make up the rules as you encounter problems, that make rules necessary. Unfortunately I know way to many initiatives, where the initial buzz has been killed by too many rules. Chris Von: Matteo Mortari <[email protected]> Datum: Freitag, 21. Juli 2023 um 20:29 An: [email protected] <[email protected]> Betreff: Re: [DISCUSS] Communication within Apache Would it make sense for the "Proposals" chapter to start with something along the lines of "*KIE project will follow a similar proposal filing as to the Kafka project. ...*"? At first reading the chapter I thought it was some copy-paste which was not being s/Kafka/KIE/ only on reaching the final phrase I understood what was the goal. In any case, thanks! -- Matteo Mortari youtube.com/@MatteoMortari linkedin.com/in/matteomortari On Fri, 21 Jul 2023, 19:44 Jason Porter, <[email protected]> wrote: > I have created the first page of our new wiki space. It details > communication within the ASF and discusses how we will use various tools. > You can find the page at [0]. > > Discussion should happen here on the list, and once consensus has been > reached, we can state on the page's comments when it was adopted. > > [0] - > https://cwiki.apache.org/confluence/display/KIE/Communication+within+Apache > > -- > Jason Porter > Software Engineer > He/Him/His > > IBM > >
