<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The wiki pages are indeed fine.<div class=""><br class=""><div class=""><div class="">Moving the issues from the export project to the Seaside project proves to be a whole different story. </div><div class="">At the very least, we have to accept that the issue export is just to preserve the issue in *some* state (i.e. not being cleanly mapped to github labels, milestones, users, etc.). I think it’s OK, given that the essential info is preserved and that I do not have time to try implementing a better mapping. </div><div class=""><br class=""></div><div class="">But I want to get rid of the export project and move the issues to SeasideSt/Seaside. </div><div class="">I can move issue by issue using [1], which seems relatively OK except that there is no batch move feature (yet). I moved 1 closed issue to see how the result looks like.</div><div class="">I tried using another script [2], but that moves closed issues back to the open state, which is a no-go for me. It actually did not work either when I tried it.</div><div class="">I also looked at the github API to implement something myself, but that will require more time.</div><div class=""><br class=""></div><div class="">Maybe I will leave the issues in the export project for now and wait for a better solution.</div><div class=""><br class=""></div><div class="">Johan</div><div class=""><br class=""></div><div class="">[1] <a href="https://github.com/google/github-issue-mover" class="">https://github.com/google/github-issue-mover</a></div><div class="">[2] <a href="https://github.com/IQAndreas/github-issues-import" class="">https://github.com/IQAndreas/github-issues-import</a></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 26 Mar 2015, at 18:20, Philippe Marschall <<a href="mailto:philippe.marschall@gmail.com" class="">philippe.marschall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Thu, Mar 26, 2015 at 6:09 PM, Johan Brichau <<a href="mailto:johan@inceptive.be" class="">johan@inceptive.be</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">On 26 Mar 2015, at 11:05, Johan Brichau <<a href="mailto:johan@inceptive.be" class="">johan@inceptive.be</a>> wrote:<br class=""><br class="">- I can't find the wiki<br class=""><br class="">this one is in the wiki branch, I found instructions for moving them to<br class="">github wiki [1]<br class=""><br class=""><br class="">The (bare-bones) export of the wiki got added to the Seaside project:<br class=""><a href="https://github.com/SeasideSt/Seaside/wiki" class="">https://github.com/SeasideSt/Seaside/wiki</a><br class=""></blockquote><br class="">That looks OK. We had no structure on Google Code so we can't really<br class="">expect much. What's not optimal is that the links on the release pages<br class="">go to the google code issue tracker. But since it's all .md files now<br class="">we should be able to fix this with a script.<br class=""><br class="">Cheers<br class="">Philippe<br class="">_______________________________________________<br class="">seaside-dev mailing list<br class=""><a href="mailto:seaside-dev@lists.squeakfoundation.org" class="">seaside-dev@lists.squeakfoundation.org</a><br class="">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>