Is there a limitation on the Jira tooling preventing using the current Slack? Seems easier to keep it in one place at the moment, then have a bigger discussion about moving it all to Apache Slack otherwise. I don't know about others, but I am a member of multiple Slack groups, per different OSS groups even, so don't see adding a group as a limitation. That part is super easy.
For instance, there are multiple channels on the current Slack group, and NetBeans covers many technologies. The channel names in Slack have fairly short char limits, so preceding them all with netbeans- would not work well. This seems way more difficult that explaining where Slack is and how to access it for everything NetBeans, but we can see. I guess I'm just thinking priorities. I'd rather spend time getting more of the project itself in working order right now unless there is a real limitation. Initially we had to debate the use of Slack at all as an example, so some time under the bridge there. But certainly interested in everyone's opinions. Thanks Wade On Wed, Apr 3, 2019, 05:39 Eric Barboni <sk...@apache.org> wrote: > Hi folks, > > > > As part of a request to connect Jenkins build (for maven and apidoc) to our > netbeans.slack, I was told that we could move/migrate to the slack atasf > to > use their . > > Maybe the more technical channels, like jira,github-repo can be recreated > at asfslack. > > > > It may be easier for people having multiple apache project to be there. > > > > > > Regards > > Eric > >
