You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Eric Barboni <sk...@apache.org> on 2019/04/03 09:39:54 UTC
netbeans slack on theasf
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
RE: netbeans slack on theasf
Posted by Eric Barboni <sk...@apache.org>.
Hi
As the only available solution for Jenkins to slack was to use asfslack I created a netbeans-builds channel. It's intended more for Apache NetBeans Infra than for mainstream users like the netbeanslack.
As we got a push issue with the website I append the website jenkins build with such notification.
Regards
Eric
-----Message d'origine-----
De : Christian Lenz <ch...@gmx.net>
Envoyé : mercredi 3 avril 2019 16:12
À : dev@netbeans.incubator.apache.org
Objet : AW: netbeans slack on theasf
We have another ticket: https://issues.apache.org/jira/browse/INFRA-18149 sometimes the bridge between Jira and Slack is broken for NetBeans Slack. After restarting Jira, everything is fine again. Problem is they seem to not want to help here anymore, instead of saying please migrate to oour slack. Nothing to say here that I don’t like the „solution“ but yeah.
Cheers
Chris
Von: Eric Barboni
Gesendet: Mittwoch, 3. April 2019 15:51
An: dev@netbeans.incubator.apache.org; wadechandler@apache.org
Betreff: RE: netbeans slack on theasf
It's more for jenkins to message to slack, we got a token (chris do that configuration) but AFAIK and by infra (https://issues.apache.org/jira/browse/INFRA-18116) we cannot expose it in the Jenkins.
It's not urgent at all it's just oportunity
Regards
Eric
-----Message d'origine-----
De : Wade Chandler <wa...@apache.org> Envoyé : mercredi 3 avril 2019 13:55 À : dev@netbeans.incubator.apache.org Objet : Re: netbeans slack on theasf
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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: netbeans slack on theasf
Posted by Christian Lenz <ch...@gmx.net>.
We have another ticket: https://issues.apache.org/jira/browse/INFRA-18149 sometimes the bridge between Jira and Slack is broken for NetBeans Slack. After restarting Jira, everything is fine again. Problem is they seem to not want to help here anymore, instead of saying please migrate to oour slack. Nothing to say here that I don’t like the „solution“ but yeah.
Cheers
Chris
Von: Eric Barboni
Gesendet: Mittwoch, 3. April 2019 15:51
An: dev@netbeans.incubator.apache.org; wadechandler@apache.org
Betreff: RE: netbeans slack on theasf
It's more for jenkins to message to slack, we got a token (chris do that configuration) but AFAIK and by infra (https://issues.apache.org/jira/browse/INFRA-18116) we cannot expose it in the Jenkins.
It's not urgent at all it's just oportunity
Regards
Eric
-----Message d'origine-----
De : Wade Chandler <wa...@apache.org>
Envoyé : mercredi 3 avril 2019 13:55
À : dev@netbeans.incubator.apache.org
Objet : Re: netbeans slack on theasf
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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: netbeans slack on theasf
Posted by Eric Barboni <sk...@apache.org>.
It's more for jenkins to message to slack, we got a token (chris do that configuration) but AFAIK and by infra (https://issues.apache.org/jira/browse/INFRA-18116) we cannot expose it in the Jenkins.
It's not urgent at all it's just oportunity
Regards
Eric
-----Message d'origine-----
De : Wade Chandler <wa...@apache.org>
Envoyé : mercredi 3 avril 2019 13:55
À : dev@netbeans.incubator.apache.org
Objet : Re: netbeans slack on theasf
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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: netbeans slack on theasf
Posted by Wade Chandler <wa...@apache.org>.
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
>
>