There is now actually an OSGeo "team" on Slack (https://osgeo.slack.com/signup), which is great, but we need to figure out a way to allow anyone to register. (and there is also a #MapServer channel)
Credit to Stephan Meissl for setting this up during the code sprint at FOSS4G-Como.
I am a team "Owner" so I can help configure.
Does anyone have an idea for how to allow people to join with their own e-mail addresses, so we can share this?
Any thoughts on using Gitter [1]? One can create rooms based on
GitHub repositories/organizations and more. Plus the benefit of
reusing GitHub's authentication.
On Sat, Aug 22, 2015 at 11:27 AM, Jeff McKenna
<jmckenna@gatewaygeomatics.com> wrote:
There is now actually an OSGeo "team" on Slack
(https://osgeo.slack.com/signup), which is great, but we need to figure out
a way to allow anyone to register. (and there is also a #MapServer channel)
Credit to Stephan Meissl for setting this up during the code sprint at
FOSS4G-Como.
I am a team "Owner" so I can help configure.
Does anyone have an idea for how to allow people to join with their own
e-mail addresses, so we can share this?
On Sat, Aug 22, 2015 at 01:12:11PM -0400, Tom Kralidis wrote:
Any thoughts on using Gitter
When I entered OSGeo, a lot of tech talk was carried out on the #telascience IRC channel. That's perfect and I can use IRC from a
remote SSH session in a terminal window. Apparently a lot of it has
moved elsewhere, maybe to a different IRC channel - I don't know.
Now people are talking about Slack or Gitter - and I wonder wether I'm
just being too old-style. To be honest, I really don't understand the
net benefit, can someone please explain to me .... or do people use
these new communication channels just because they can ?
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
I have enabled the IRC and XMPP gateways (per steps provided by Jurgen, thanks!). If you are already a member of the OSGeo "team", your steps to enable are at: https://osgeo.slack.com/account/gateways
-jeff
On 2015-08-22 12:27 PM, Jeff McKenna wrote:
There is now actually an OSGeo "team" on Slack
(https://osgeo.slack.com/signup), which is great, but we need to figure
out a way to allow anyone to register. (and there is also a #MapServer
channel)
Credit to Stephan Meissl for setting this up during the code sprint at
FOSS4G-Como.
I am a team "Owner" so I can help configure.
Does anyone have an idea for how to allow people to join with their own
e-mail addresses, so we can share this?
I have enabled the IRC and XMPP gateways (per steps provided by Jurgen, thanks!). If you are already a member of the OSGeo “team”, your steps to enable are at: https://osgeo.slack.com/account/gateways
Well, I also don’t understand yet what this slack is about… Why do we want it and why change the current way of operations?
Well, I also don't understand yet what this slack is about... Why do we
want it and why change the current way of operations?
Was this anyhow discussed in this list?
Thanks
Markus
IRC on Freenode is still the main place Open Source
projects/developers/etc talk.
Slack, Gitter, Hipchat are essentially glorified IRC clients running on
their own servers and are more common among commercial developers and
specific communities (Gitter to Github and Hipchat to Atlassian
(Bitbucket, Jira etc). They are also more user friendly for
non-developers. Sidenote, many of the services can be hit via and IRC,
or XMPP client also.
#telascience will still remain the main SAC place to chat, partly
because it is not logged.
The rest of the the osgeo IRC channels will also continue, #osgeo, QGIS, #gdal, etc (at least the ones that are currently in use).
I think having the options is fine for each project to decide which
places they'd like to push their community to communicate under. IRC
never really took off for some and probably never will.
IRC on Freenode is still the main place Open Source
projects/developers/etc talk.
Slack, Gitter, Hipchat are essentially glorified IRC clients running on
their own servers and are more common among commercial developers and
specific communities (Gitter to Github and Hipchat to Atlassian
(Bitbucket, Jira etc). They are also more user friendly for
non-developers. Sidenote, many of the services can be hit via and IRC,
or XMPP client also.
#telascience will still remain the main SAC place to chat, partly
because it is not logged.
The rest of the the osgeo IRC channels will also continue, #osgeo, QGIS, #gdal, etc (at least the ones that are currently in use).
I think having the options is fine for each project to decide which
places they'd like to push their community to communicate under. IRC
never really took off for some and probably never will.
Thanks,
Alex
Thanks Alex, this is what I was thinking as well, exactly.
Could an OSGeo project or incubating project choose to use the OSGeo Slack to hold its meetings? Of course.
Could the next OSGeo Board discuss the possibility of holding their monthly meeting through the OSGeo Slack? It could.
We can't predict the future, but, we can allow communication to happen and allow community members some choice.
To those sending me direct messages worried about what this new "OSGeo Slack team" means and how it affects our IRC use - I don't even know the answers. Right now IRC is there, we use it, and now Slack is there, it might be used or it might fade away.
Well, I also don't understand yet what this slack is about... Why do we
want it and why change the current way of operations?
Was this anyhow discussed in this list?
Thanks
Markus
IRC on Freenode is still the main place Open Source
projects/developers/etc talk.
Slack, Gitter, Hipchat are essentially glorified IRC clients running on
their own servers and are more common among commercial developers and
specific communities (Gitter to Github and Hipchat to Atlassian
(Bitbucket, Jira etc). They are also more user friendly for
non-developers. Sidenote, many of the services can be hit via and IRC,
or XMPP client also.
#telascience will still remain the main SAC place to chat, partly
because it is not logged.
The rest of the the osgeo IRC channels will also continue, #osgeo, QGIS, #gdal, etc (at least the ones that are currently in use).
I think having the options is fine for each project to decide which
places they'd like to push their community to communicate under. IRC
never really took off for some and probably never will.
All that being said, one of the open source clones of slack would also
work well.
Mike
I agree with Mike.
I use Slack at work all the time, it saves a lot of email, mobile app
is good enough (way better than IRC clients), the search and
"starring" works fine, etc.
Yes it's closed source, like github, the text editor I normally use to
code or the Operating System of many people working on Open Source.
But on the other hand if it improves collaboration and discussion to
people that now is hesitant to use IRC, well I can live with that
closeness.
It's exactly the same discussion than using mailing lists instead of
allowing us to use Meetup or Facebook as new channels for new times
and new audiences.
IRC has worked always well, nobody is telling here to stop using it,
but why not allowing us to experiment with new ways of communicating
and interact?