<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Denis and friends<div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please lets park this until the hackfest discussion. The issue already consumed so much community energy and I think these discussions get very circular. I’d prefer we broadcast outcomes of the vote / PSC and community discussion in Madeira after we have got a concrete plan of action. There are so many different view points that there is no way to resolve this without taking a position contrary to *someone’s* view. Along the way lets improve some of our statutes and community guidelines in particular I think addressing some of these issues in our charter may help to give a clearer path for future situations such as this:</div><div class=""><br class=""></div><div class="">1) clearly define who may call for a vote, when and how a community vote may be called. </div><div class="">2) clearly define what the criteria are for a vote being accepted (minimum number of votes, % majority, what to do if there are lots of abstentions)</div><div class="">3) define in which situations the PSC may override a vote, in which situations a vote may override the PSC</div><div class="">4) define our policy on using open source - do we mandate it, prefer it, or use the best / most pragmatic tool for the job</div><div class=""><br class=""></div><div class="">Thanks for your understanding and patience, lets resolve this with oil and grease not hammers and tongs!</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 15 Feb 2018, at 19:33, Denis Rouzaud <<a href="mailto:denis.rouzaud@gmail.com" class="">denis.rouzaud@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">Le jeu. 15 févr. 2018 à 13:03, Jürgen E. Fischer <<a href="mailto:jef@norbit.de" class="">jef@norbit.de</a>> a écrit :<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Denis,<br class="">
<br class="">
On Thu, 15. Feb 2018 at 15:05:14 +0000, Denis Rouzaud wrote:<br class="">
> On practical points, proof of concept was achieved by Matthias (and some<br class="">
> others) and showed all of this is possible except attributing comments to<br class="">
> the original author...bummer ;).<br class="">
<br class="">
News to me. The migration didn't go though - I thought Matthias had given up<br class="">
on the migration, because he was uncertain that we'd go through with it and it<br class="">
might end up as a waste of energy. And his target was not to do a full<br class="">
migration - IIRC.<br class=""></blockquote><div class=""><br class=""></div><div class="">Well, it depends on what we mean by migration of course (moving all tickets? all tags? etc). <br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
I tried a full migration - and ran into obstacles from github (eg. throtteling)<br class=""></blockquote><div class=""><br class=""></div><div class="">proposition was to contact Github, correct?</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and had doubts about mapping all what we have in redmine to tags in github </blockquote><div class=""><br class=""></div><div class="">well, again depends on what we're migrating. History or tags. My proposition is to start with a new empty list for QGIS 3 and migrate issues on demand (with an assitant tool, triggered from Redmine or semi-manually).</div><div class="">And for the history, to keep Redmine as read-only.</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-<br class="">
and how useable it would be which such a large number of issues and/or tags as<br class="">
ours.<br class="">
<br class="">
Richard tried again later and also gave up.<br class="">
<br class="">
Attributing comments to the original author was just one thing that couldn't be<br class="">
done at all.<br class="">
<br class="">
We finally settled to upgrade and move redmine to a faster machine - and that<br class="">
was that.<br class=""></blockquote><div class=""><br class=""></div><div class="">Upgrading Redmine should certainely help the migration as the original migration tool was for more recent version, correct? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
And when this was brought up again, we didn't talk about the implementation<br class="">
(ie. how we map the trac/redmine ticket numbers to github issues - our commit<br class="">
messages reference the tickets).<br class="">
<br class="">
And then there was this sudden vote...<br class=""></blockquote><div class=""><br class=""></div><div class="">I understand that. Let's wait for Madeira then. </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
> (because, damn, it's not integrated with the source code!).<br class="">
<br class="">
Of course it is linked to the source code. It's just not linked to github,<br class="">
because github doesn't allow us to - otherwise we'd just address PRs and issues<br class="">
differently and let one point to github and the other to redmine.<br class=""></blockquote><div class=""><br class=""></div><div class="">Of course, I meant source code repo! </div><div class=""><br class=""></div><div class="">I think we can discuss for ever on what has been done and what is possible. Then, we can adapt the decision tree and add the question:</div><div class=""><br class=""></div><div class="">If we can't keep the whole history, shall we stick to Redmine?</div><div class="">And what do we mean with whole history (added files, comments, tags, etc).</div><div class=""><br class=""></div><div class="">Denis</div><div class=""><br class=""></div></div></div>
_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-psc</div></blockquote></div><br class=""><div class="">
<span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"> </span><span><img apple-inline="yes" id="B6663751-6623-474B-98A2-18CD008197F4" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;">
</div>
<br class=""></div></body></html>