Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer the trackers from sourceforge #70

Closed
Utumno opened this issue Mar 2, 2014 · 8 comments
Closed

Transfer the trackers from sourceforge #70

Utumno opened this issue Mar 2, 2014 · 8 comments
Labels
R-wont-fix Rejection: Bug will not be fixed (usually due to technical reasons)

Comments

@Utumno
Copy link
Member

Utumno commented Mar 2, 2014

@lojack5 : add what's left to do when you get the chance.

Maybe have a look at https://github.com/ttencate/sf2github ? If you decide doing it this way I would recommend doing it in a throw away repo once first as we can't delete issues - in case anything goes wrong.

Also I have no admin rights so I don't think I can do much - hilfe!

@Utumno Utumno added this to the 304.4 milestone Mar 2, 2014
@Utumno Utumno self-assigned this Mar 2, 2014
@lojack5
Copy link
Member

lojack5 commented Mar 3, 2014

@Utumno: I set you up as admin on the sourceforge page. As mentioned in #58, I think postponing this would be ok. I'd have to check out that tool to see if it could be done faster, I think there will still be lots of manual tweaking however.

@Utumno
Copy link
Member Author

Utumno commented Mar 3, 2014

@lojack5 - thanks ! - if you could check the tool it'd be great - I plan to start this around thursday if the tool proves not an option. Open bugs starting with 131 Possible CBash patcher bugs ?

I'd say transfer only open bugs - no need to clutter this repo with all the closed bugs

On the other hand it would be nice if we could export all the metadata from the svn and leave them here as a blob somewhere for safekeeping. Is this possible ?

@lojack5
Copy link
Member

lojack5 commented Mar 6, 2014

So I tried to go at the script to transfer stuff, however I ran into two issues (one I could get around, the other not):

  1. SourceForge doesn't want to export the Oblivionworks data anymore (which the script parses to generate the Github Issues. Specifically, it says "Preparing your data...bla bla...you'll recieve an email with download instructions", but I never get the email.
  2. The script needs a username/password, but I use 2-factor authentication, and the script doesn't support that. This one I could get around by disabling 2-factor, but problem 1 makes the issue moot.

@Utumno
Copy link
Member Author

Utumno commented Mar 6, 2014

@lojack5 thank you

On 1 - could you bug the SVN admins ? Scripting etc are not my strong points and setting this up will suck a lot of my time. If 1 can't be resolved well then - copyPaste() time

EDIT: I would like to have this in 304.4 after all

@lojack5
Copy link
Member

lojack5 commented Mar 6, 2014

I've contacted support, but no response yet. Might as well start doing it by hand again.

@Utumno Utumno added the git label Mar 14, 2014
@Utumno Utumno modified the milestones: Move to git, 304.4 Mar 14, 2014
@Utumno Utumno modified the milestones: 304.4, Move to git Mar 31, 2014
@Utumno
Copy link
Member Author

Utumno commented Mar 31, 2014

We need some bugs to generate the posts

@lojack5: Managed to export the data (just worked for me)
bugs : https://www.dropbox.com/s/ae7cttxr749814r/oblivionworks-backup-2014-03-31-002841.zip
enhancements: https://www.dropbox.com/s/6e13l55bobs7vsj/oblivionworks-backup-2014-03-31-004657.zip

Have a look if you have time - better on a throwaway repo (we can't delete issues !)

@lojack5
Copy link
Member

lojack5 commented Mar 31, 2014

Looked over the dumps real quick to be sure it was up to date (had that problem before with the second post data), seems to be good.

I think I'll filter through it semi-manually at first to clean out closed stuff and anything already ported over, then test importing eventually in my "test" repo. Not sure when I want to go through and get rid of bugs we don't want ported over, I'll figure something out.

@Utumno
Copy link
Member Author

Utumno commented Apr 8, 2014

Not much time but when I find some I'd like to go on with 304.4 and I need some bugs to feed the scripts at meta - @lojack5 if you could specify some (or a range) I could transfer them manually from the SVN

@Utumno Utumno modified the milestones: 305, 304.4 Jul 5, 2014
@Utumno Utumno modified the milestones: 307, 305 Jul 25, 2014
@Utumno Utumno modified the milestones: 307, Move to git Jan 10, 2015
@Utumno Utumno added the M-backburner Misc: On backburner - not rejected, but won't be tackled for a while label Jan 16, 2015
@Utumno Utumno closed this as completed Jan 16, 2015
@Utumno Utumno added R-wont-fix Rejection: Bug will not be fixed (usually due to technical reasons) and removed M-backburner Misc: On backburner - not rejected, but won't be tackled for a while labels Sep 15, 2019
@Infernio Infernio removed this from the Move to git milestone Jul 1, 2022
@Infernio Infernio closed this as not planned Won't fix, can't repro, duplicate, stale Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R-wont-fix Rejection: Bug will not be fixed (usually due to technical reasons)
Projects
None yet
Development

No branches or pull requests

3 participants