[fluid-dev] Re: Migration of services

[jimmy]

If there are only a dozen or two, I can help extracting them and a few of us 
here can probably manually cut and paste a few tickets each and be done with 
them.  If there are 50, 100, or more tickets, then scripting it would be 
worth-while.

Ticket migration can probably be automated.  The following assume SourceForge, 
but it should work with most other web sites via HTTP, too.

wget can do HTTP post, and support userid/password (with web cookies saved to a 
file).  So you can use wget to login, save the SourceForge cookie to a file, 
then use that cookie for every ticket you want to create, or submit to 
SourceForge.

More specifically, use a shell script (or perl script) login, saving the 
session cookie to a cookie file), loop and extract each ticket to a temporary 
text file, then send (http post) each ticket to SourceForge using that session 
cookie info.  Perl may have plenty of HTTP libraries to deal with it, I haven't 
used those much.

I assume that you can delete invalid, or unwanted tickets, right?  Which is 
inevitable with the first few "testing" tickets.

Well, in theory that's all doable.  One has to try it and see if it works.  Of 
course, userid/password is needed, using temporary password and reset it 
afterward is an option, too.  This is script programming (Bash, Perl, or your 
choice of scripting language).

Firefox javascript (XUL) maybe another option, too.  But I'm not familiar with 
it and have never tried it.

If you want, I can try creating a couple of tickets and see if I can create a 
dozen new test tickets this way.  I don't know if anyone can just create a 
ticket.  Chances are I'll have to get a SF account to get permission to create 
new ticket(s).  Of course, the original submitter info (if we still have those) 
will have to be part of the textual description anyway (accounts from different 
systems).

Let me know if you want me to try it, give me the new web site and URL for 
creating new ticket(s).

Jimmy