Charlotte Wolter writes:
> Really nice discussion of the issues around using for-profit tools
> in an open-source organization.
The for-profit point isn't really the core issue.
IMHO the big issues are
the use of non-Free software on servers
the use of
Martijn,
I think your approach on this issue is spot on.
I personally think that when a project like OSM supports non-Free software,
especially ones run by external entities, it sends absolutely the wrong
message. Worse still is if we force users to use these gatekeepers to
interface with our
On 2016.03.30. 10:40, Shawn K. Quinn wrote:
On Wed, 2016-03-30 at 10:36 +0300, Rihards wrote:
this might be a bit of a clash of "why are we mapping" reasons.
for some people means are not important.
for others, osm is one bit in a more open, collaborating world.
osm using slack is like
On Wed, 2016-03-30 at 10:36 +0300, Rihards wrote:
> this might be a bit of a clash of "why are we mapping" reasons.
> for some people means are not important.
> for others, osm is one bit in a more open, collaborating world.
>
> osm using slack is like wikipedia using google maps. because they
On 2016.03.30. 10:31, Shawn K. Quinn wrote:
On Sun, 2016-03-27 at 00:07 -0700, Steve Coast wrote:
https://en.wikipedia.org/wiki/Slack_(software)
And on this page:
License Proprietary
Until and unless there is an alternative client that is free software
(ideally GPL licensed, but BSD/MIT
On Sun, 2016-03-27 at 00:07 -0700, Steve Coast wrote:
> https://en.wikipedia.org/wiki/Slack_(software)
And on this page:
> License Proprietary
Until and unless there is an alternative client that is free software
(ideally GPL licensed, but BSD/MIT licensed would also be okay), I would
prefer
Martijn van Exel wrote:
> The web site has always been about the map primarily,
> not the people. I am curious if there are any ideas out
> there to change that.
Groups!
cheers
Richard
--
View this message in context:
http://gis.19327.n5.nabble.com/Slack-tp5870718p5870933.html
Sent from
7 matches
Mail list logo