[Seaside-dev] Migration to github

[Johan Brichau]

In finally did it the other way around: I renamed the existing Seaside project on github to Seaside-old and renamed the google-code-export project to become the Seaside project.
In that way, the issues list remains as it was exported from Google code.
I also made a Grease project on github. 

All is on
https://github.com/SeasideSt <https://github.com/SeasideSt>

I also edited those parts of the website necessary to redirect people to the github issue tracker.

What remains to be done:
- adapt the ‘make a release’ instructions
- cleanup the wiki

Mind that the github projects are mirroring the code from the smalltalkhub repositories only (for now). 

> On 28 Mar 2015, at 11:09, Johan Brichau <johan at inceptive.be> wrote:
> 
> The wiki pages are indeed fine.
> 
> Moving the issues from the export project to the Seaside project proves to be a whole different story. 
> 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. 
> 
> But I want to get rid of the export project and move the issues to SeasideSt/Seaside. 
> 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.
> 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.
> I also looked at the github API to implement something myself, but that will require more time.
> 
> Maybe I will leave the issues in the export project for now and wait for a better solution.
> 
> Johan
> 
> [1] https://github.com/google/github-issue-mover <https://github.com/google/github-issue-mover>
> [2] https://github.com/IQAndreas/github-issues-import <https://github.com/IQAndreas/github-issues-import>
> 
>> On 26 Mar 2015, at 18:20, Philippe Marschall <philippe.marschall at gmail.com <mailto:philippe.marschall at gmail.com>> wrote:
>> 
>> On Thu, Mar 26, 2015 at 6:09 PM, Johan Brichau <johan at inceptive.be <mailto:johan at inceptive.be>> wrote:
>>> 
>>> On 26 Mar 2015, at 11:05, Johan Brichau <johan at inceptive.be <mailto:johan at inceptive.be>> wrote:
>>> 
>>> - I can't find the wiki
>>> 
>>> this one is in the wiki branch, I found instructions for moving them to
>>> github wiki [1]
>>> 
>>> 
>>> The (bare-bones) export of the wiki got added to the Seaside project:
>>> https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki>
>> 
>> That looks OK. We had no structure on Google Code so we can't really
>> expect much. What's not optimal is that the links on the release pages
>> go to the google code issue tracker. But since it's all .md files now
>> we should be able to fix this with a script.
>> 
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org <mailto:seaside-dev at lists.squeakfoundation.org>
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20150525/582a187e/attachment-0001.htm