<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi,</p>
<p id="reply-intro">On 2019-06-05 11:59, Jürgen E. Fischer wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Hi Andreas,<br /><br />On Wed, 05. Jun 2019 at 09:48:59 +0200, Andreas Neumann wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Is there a way to manually re-assign the author of the migrated ticket<br />from qgib back to myself?</blockquote>
<br />No, I don't you can claim other people's (or bot's ;)) work either.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">But hey - that stupid qgib bot claimed my work to be his work during the migration! And now he can't give it back to me?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Not a big issue. I can live with it. As long as the core developers have some benefit from the issue migration, then I'm fine.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Personally I just have to get used to the new issue system on github. Of<br />course, it takes some time to learn a new system. And no - not<br />everything is easy and self-explaining on github. I would say, because<br />it is a really open system, that it might even be harder to use than<br />Redmine for new users who never used github before (except for the<br />Mantra of course ;-) ).</blockquote>
<br />Once again: the mantra was not necessary for redmine - shortly after getting<br />osgeo ids was requiring the mantra, we enabled direct registration in redmine<br />available (and openid was available too).</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">you are right of course. And the Mantra is still required for plugin-authors. So nothing really improved by the move to Github regarding the Mantra.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><br />And for the open nature of github: you cannot assign owners (see above) - and<br />you cannot integrate an external ticket system.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Sorry - I wasn't very clear what I meant with "open nature" of GitHub: i mean the "open" (unstructured) way of categorizing issues in Github. Labels being the only way of structuring anything in the issues, whereas we had versions, code areas, state, feature vs bug and more in Redmine. If people don't use the label system consciously we quickly end up with a big mess. That is my concern.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br />But you can use tons of other services, that make you more dependent on github<br />(like travis) ;)<br /><br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">And I hope that the open nature of GitHub doesn't lead to a big mess. For<br />developers, the github integration is definitely very nice though.<br /><br />But everything will be easier when we move from Github to Gitlab ;-)</blockquote>
<br />As if that ever would happen - but I was hoping the same for the redmine<br />migration - so you never know ;)</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Who knows ...</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Andreas</div>
</body></html>