[Osmf-talk] Commitment to open communication channels
Mateusz Konieczny
matkoniecz at tutanota.com
Mon Aug 17 09:25:36 UTC 2020
There is nothing here that forbids usage of
Facebook, Twitter other proprietary services,
in addition to open services.
17 Aug 2020, 08:35 by heatherleson at gmail.com:
> Hi I appreciate this effort. However, this has a risk of also becoming a niche and exclusive club. Many parts of OSM use facebook, twitter and viber for their communications.
>
> I think we also need to also be open to the communications channels that OSM audiences and contributors use.
>
> Thank you
>
> Heather
>
>
> On Mon, 17 Aug 2020, 01:05 Tobias Knerr, <> osm at tobias-knerr.de> > wrote:
>
>> On 16.08.20 22:58, Frederik Ramm wrote:
>> > To me this seems to reaffirm something we're already doing at present,
>> > rather than change anything. Am I correct or would such a commitment
>> > mean that something would change as a result?
>>
>> According to working groups' responses and in my own experience, we are
>> by and large already practising this. WGs have mentioned some peripheral
>> room for improvement (CWG is working on mirroring some content onto open
>> microblogging platforms, for example), but this certainly isn't intended
>> to bring about any kind of major shift in how we do things.
>>
>> Personally, I hope this commitment can offer reassurance that our use of
>> open platforms is not an accident, and will continue to be something we
>> care about. With a few proprietary OSM channels gaining prominence over
>> the past years, this has been a concern for some people, e.g. during
>> last year's community survey and in conversations at OSM events. I don't
>> want OSM contributors who forgo proprietary platforms to feel like they
>> are missing out.
>>
>> As an additional benefit, this step makes some of the reasons behind our
>> current practices explicit (to help people understand why we're doing
>> things the way we do), and perhaps it can inspire other groups inside
>> and outside the OSM ecosystem to follow along.
>>
>> _______________________________________________
>> osmf-talk mailing list
>> >> osmf-talk at openstreetmap.org
>> >> https://lists.openstreetmap.org/listinfo/osmf-talk
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmf-talk/attachments/20200817/e9da49b0/attachment.htm>
More information about the osmf-talk
mailing list