<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Good morning all.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/7/23 01:48, Marc_marc wrote:<br>
</div>
<blockquote type="cite"
cite="mid:30e41249-a8f8-9171-41ec-7bec8d249b27@mailo.com">you put
out a call for comments here
<br>
and the next thread says that people on the forum voted,
<br>
without a call for a vote on the mailing list.
<br>
of course ppl from the forum vote for the forum.
<br>
I have run an unanoncement vote with myself and got 100%
<br>
in favor of the mailing :) so what ? april fool ?
<br>
</blockquote>
Well, the whole point of the vote was to gauge community interest in
the change, and it seems to me that support is overwhelming.<br>
<blockquote type="cite"
cite="mid:30e41249-a8f8-9171-41ec-7bec8d249b27@mailo.com">
Unfortunately, experience with talk-fr and tagging has shown
<br>
the damage this kind of choice can do:
<br>
some people don't migrate, so the community becomes poorer
<br>
and more fragmented, and those on one media can't communicate
<br>
with those on the other media.
<br>
</blockquote>
The whole point was to change it in the import guidelines, so the
mailing list is no longer mentioned and the community forum is the
channel for communication going forward. If new importers only see
community forum on the wiki page, I don't know how they'd get
confused.<br>
<blockquote type="cite"
cite="mid:30e41249-a8f8-9171-41ec-7bec8d249b27@mailo.com">Instead
of a proposal "against the list", we need to integrate
<br>
the 2 media into a single discussion forum, which is what
Discourse
<br>
will allow when it matures, we just need to give it time to
overcome
<br>
its teething problems.
<br>
</blockquote>
Discourse already has functionality to have a full email experience.
<a moz-do-not-send="true"
href="https://community.openstreetmap.org/t/imports-community-category/97957/21">It
just needs to be fully implemented</a>, i believe.<br>
<blockquote type="cite"
cite="mid:30e41249-a8f8-9171-41ec-7bec8d249b27@mailo.com">what's
even more worrying is the fact that there's hardly a single person
among those who have taken the time to review import requests over
the last 12 months. you can tell them they have to do it on the
forum from now on, but that's not how it works. if a volunteer
doesn't want to use an interface that they find unsuitable, they
won't do it. and the unreviewed import will be approved, without
the quality improvement that the review provided.
<br>
</blockquote>
<p>It seems there are two problems here,</p>
<ul>
<li>There are too few people reviewing imports</li>
<li>Migrating from the list will cause them to leave</li>
</ul>
<p>I can't say I disagree that there are too few people reviewing
imports, but I don't believe that the loss from migrating to the
community forum would come even close to the gain in eyes on the
import that you would get from the migration.</p>
<p>It's not like new reviewers show up on the list all the time. I
have yet to see a new user start to regularly respond to other
threads on the list. <a moz-do-not-send="true"
href="https://community.openstreetmap.org/t/imports-community-category/97957/6">The
community forum already gets more engagement than the list now</a>,
and it wasn't even mentioned on the import guidelines before.<br>
</p>
<blockquote type="cite"
cite="mid:30e41249-a8f8-9171-41ec-7bec8d249b27@mailo.com">
if a volunteer doesn't want to use an interface that they find
unsuitable, they won't do it. <br>
</blockquote>
<p>I think this speaks much bigger to the mailing list than it does
to the community forum. The forum is objectively more functional,
and much easier to query, etc. There was no requirement to vote on
this issue, It was a matter of courtesy to gauge the opinion of
the community. I could've used the rationale that the first letter
I posted to the list received zero opposition, but I doubt that
would've made you happy.</p>
<p><br>
</p>
<p>--James Crawford<br>
</p>
</body>
</html>