I'm involved with Transposit (transposit.com), where they're creating a DevOps orchestration hub, including very strong Slack integration since more and more orgs are using Slack as their primary communication mechanism over e-mail and anything else.
With my Apache NetBeans hat on, if we in the Apache NetBeans community were to be working in Slack, we'd be able to use Transposit to send incoming issues to Slack, prioritize and assign them there, while also automating our release processes from Slack, e.g., call a Slack command to initiate a release with buttons for the release manager to click to initiate the actions that require human intervention. Transposit is interested in making itself available for free to Apache projects, which will make sense once I've explored the potential completely and set up a few stable runbooks for the Apache NetBeans community. However, all this is predicated on scope for Apache communities to work with their Apache projects in the same way as they work with their projects at the places where they work -- via Slack. Gj On Wed, Feb 16, 2022 at 2:17 PM Gary Gregory <garydgreg...@gmail.com> wrote: > My assumption using Slack is that it is a convenience but that decisions > MUST be reflected on a mailing list. > > Gary > > On Wed, Feb 16, 2022, 08:13 Trevor Grant <trevor.d.gr...@gmail.com> wrote: > > > I shared in Comdev channel on ASF Slack that on the mahout slack we have > a > > convention that when we get to something that should be memorialized > > someone says, "This should really be reflected back to the list". And > > whoever says that has implicitly called "not it" for having to reflect it > > back- This motivates everyone to be the first to say "This should go back > > to the list". In the rare cases where no one says it- the original author > > reflects back to the list- as is the case with this email and the comdev > > list. > > > > > > > > On Wed, Feb 16, 2022 at 7:08 AM Gary Gregory <garydgreg...@gmail.com> > > wrote: > > > > > Slack chat and video helped us tremendously on the Log4j team > especially > > > since Log4Shell. > > > > > > Gary > > > > > > On Wed, Feb 16, 2022, 07:50 Roman Shaposhnik <r...@apache.org> wrote: > > > > > > > Hi! > > > > > > > > while the classical ASF communication culture is pretty squarely > > > > centered around mailing lists it has become apparent in recent > > > > years that some of our communities (especially younger ones) > > > > prefer using alternative channels of communication. The range > > > > is pretty wide from Slack to Telegram and WeChat (and I have > > > > even heard of an occasional TikTok use ;-)). > > > > > > > > The question that originated from one of the board meetings and > > > > the one that I'd like to pose for this forum is basically: what's our > > > > collective advice to these communities on these alternative (and > > > > when I say alternative I really mean anything but a mailing list) > > > > communication channels? > > > > > > > > Personally I don't think denying them is a viable strategy, but I'd > > > > like to open up this discussion and see what others think. > > > > > > > > So... let's at least start with folks sharing their experience with > > > > these alternative communication channels: the good, the bad > > > > and the ugly. > > > > > > > > Personally, I don't think I have much to share -- I'm still very > > > > much a mailing list guy when it comes to ASF. > > > > > > > > Thanks, > > > > Roman. > > > > > > > > > >
