<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Sounds great, though it would be helpful to have specific examples.<br></div><div><br></div><div>It would be nice to expand it even wider (though "all communication" may be <br></div><div>an overkill, someone operating OSMF account on Twitter/FB/Telegram should<br></div><div>not be obligated to replicate every reply also on some open platform)<br></div><div><br></div><div>Aug 16, 2020, 21:37 by osm@tobias-knerr.de:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Hi everyone,<br></div><div><br></div><div>proprietary social media platforms are a highly influential part of life<br></div><div>in 2020, and many people use them daily. It stands to reason that we<br></div><div>want OSM to be visible in those spaces. At the same time, we would like<br></div><div>community members who prefer open communication channels to be confident<br></div><div>that their choice will not exclude them from effective participation in<br></div><div>the OSM community.<br></div><div><br></div><div>To strike this balance, the OSMF board would like make to an explicit<br></div><div>commitment on behalf of the Foundation: Essential communications will<br></div><div>always be accessible through an open, preferably self-hosted platform.<br></div><div>They may be published on proprietary channels as well, but only in<br></div><div>addition to an open channel.<br></div><div><br></div><div>For the purpose of this commitment, essential communications include:<br></div><div>* Publications or consultations by the board, WGs, committees or other<br></div><div>Foundation bodies.<br></div><div>* Communications mandated by OSMF policies/guidelines/frameworks and<br></div><div>similar documents.<br></div><div>* Anything related to how the OSMF is governed, such as AGMs and elections.<br></div><div><br></div><div>By open platforms, we mean those that are accessible through open-source<br></div><div>software and open protocols, and do not require an account at a<br></div><div>third-party service to access. (Read-only public access is sufficient<br></div><div>for one-way publications, but not two-way communications.)<br></div><div><br></div><div>We have already consulted the Foundation's working groups to make sure<br></div><div>this does not get in the way of their work, and we're now hoping for<br></div><div>community feedback. Depending on your responses, we plan to adopt a<br></div><div>commitment along these lines as an OSMF policy at our next board meeting.<br></div><div><br></div><div>Tobias<br></div><div>(for the OSMF board)<br></div><div><br></div><div>_______________________________________________<br></div><div>osmf-talk mailing list<br></div><div>osmf-talk@openstreetmap.org<br></div><div>https://lists.openstreetmap.org/listinfo/osmf-talk<br></div></blockquote><div><br></div> </body>
</html>