You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juneau.apache.org by James Bognar <ja...@salesforce.com> on 2016/06/28 17:56:00 UTC
Juneau Slack channel to be sunset.
FYI....I posted a message to the Slack channel that it's going to be sunset
and provided instructions for subscribing to the mail list. I plan on
shutting down the channel in 1 week.
--
James Bognar
Re: Juneau Slack channel to be sunset.
Posted by Craig Russell <cr...@oracle.com>.
One of the things that will change as any project moves to Apache is the style of communication. We are a world-wide community and asynchronous communication is a requirement for all projects.
In addition, there may be occasions for real-time communications channels. For example, around a release there might be some issues to resolve that can’t wait for a multi-day chat.
But for the most part, email should be used. This gives all participants a chance to comment on any issues.
Craig
> On Jun 29, 2016, at 2:39 AM, Jochen Wiedmann <jo...@gmail.com> wrote:
>
> On Wed, Jun 29, 2016 at 11:24 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
>
>> It might still be worth having a look at Gitter, or apache.hipchat.com
>> (we can just ask Apache INFRA to make a room there) or
>> irc.freenode.net (!) as a synchronous background channel for the email
>> list - but perhaps get everyone to join this email list first for the
>> main communication?
>
> I strongly discourage using external Chat servers. Experience shows,
> that this leads to closed groups within the community sooner, or
> later.
>
> Right now, I cannot determine any reason for *not* using
> dev@juneau.i.a.o for communication.
>
> Jochen
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Craig L Russell
Architect
craig.russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Juneau Slack channel to be sunset.
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Jun 29, 2016 at 11:24 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
> It might still be worth having a look at Gitter, or apache.hipchat.com
> (we can just ask Apache INFRA to make a room there) or
> irc.freenode.net (!) as a synchronous background channel for the email
> list - but perhaps get everyone to join this email list first for the
> main communication?
I strongly discourage using external Chat servers. Experience shows,
that this leads to closed groups within the community sooner, or
later.
Right now, I cannot determine any reason for *not* using
dev@juneau.i.a.o for communication.
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Re: Juneau Slack channel to be sunset.
Posted by Stian Soiland-Reyes <st...@apache.org>.
As far as I know Slack is always bound to a @emaildomain + invitation.
I had a Slack account from a different project, but it was not
compatible with the Juneau Slack, because this in was a different
"team".
It might still be worth having a look at Gitter, or apache.hipchat.com
(we can just ask Apache INFRA to make a room there) or
irc.freenode.net (!) as a synchronous background channel for the email
list - but perhaps get everyone to join this email list first for the
main communication?
IRC is also a classic, but I've found it only works for large
communities, for both #taverna and #jena the IRC channels are usually
quiet for a week at a time, which don't work well for a synchronous
channel - as often you don't know the name or the email address of the
person who asked a question and has since logged out. Large projects
like #maven and #clojure prosper well on IRC - but mainly for dev-user
and user-user communication.
Gitter/Slack/HipChat all have the strength that they work as
semi-asynchronous - you log in and get access to the backlog, mixed
with some nice bot messages. So I wouldn't dismiss that technology
fully - just be aware that it should be easy to contribute to and be a
part of Apache Juneau (incubating) without having to agree to
third-party Terms&Conditions, etc; and so the main traffic should be
on the list (or issue tracker).
On 28 June 2016 at 19:06, John D. Ament <jo...@apache.org> wrote:
> Do we want to pursue a more open communication channel via slack? I know
> the slack channel was limited to IBM and SF emails.
>
> John
>
> On Tue, Jun 28, 2016 at 1:56 PM James Bognar <ja...@salesforce.com>
> wrote:
>
>> FYI....I posted a message to the Slack channel that it's going to be sunset
>> and provided instructions for subscribing to the mail list. I plan on
>> shutting down the channel in 1 week.
>>
>> --
>> James Bognar
>>
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/0000-0001-9842-9718
Re: Juneau Slack channel to be sunset.
Posted by "John D. Ament" <jo...@apache.org>.
Do we want to pursue a more open communication channel via slack? I know
the slack channel was limited to IBM and SF emails.
John
On Tue, Jun 28, 2016 at 1:56 PM James Bognar <ja...@salesforce.com>
wrote:
> FYI....I posted a message to the Slack channel that it's going to be sunset
> and provided instructions for subscribing to the mail list. I plan on
> shutting down the channel in 1 week.
>
> --
> James Bognar
>