Migrating BerliOS to SourceForge

[Alpha]

I have been starting a few tests with with migration of the BerliOS dump files, and have run into what will likely be a major issue.  Attached files on SourceForge do not appear anywhere in the complete export.  They are only referenced by a url, but give no hint of how a file could be imported to that location.

Code Select Expand


{
  "status": "open",
  "reported_by_id": "5124334124b0d9277e70766c",
  "related_artifacts": [],
  "attachments": [
    {
      "url": "http://sourceforge.net/p/ticketexport/patches/3/attachment/converterTest.py",
      "bytes": 921
    }
  ],
  "reported_by": "alpha0010",
  "description": "Extended description.",
  "labels": [],
  "assigned_to": "alpha0010",
  "assigned_to_id": "5124334124b0d9277e70766c",
  "private": false,
  "summary": "Ticket with patch",
  "discussion_thread": {
    "_id": "bc4d1a58",
    "posts": [],
    "discussion_id": "529d6ac0d46bb4611598533a",
    "subject": ""
  },
  "mod_date": "2014-06-06 01:34:22.120000",
  "votes_down": 0,
  "votes_up": 0,
  "_id": "53911a9df1fd8d55b0aeeeb3",
  "discussion_thread_url": "http://sourceforge.net/rest/p/ticketexport/patches/_discuss/thread/bc4d1a58/",
  "ticket_num": 3,
  "custom_fields": {
    "_milestone": "1.0"
  },
  "created_date": "2014-06-06 01:34:21.961000"
}


[Alpha]

Another issue, is that it appears the BerliOS dump was faulty: inside bs_patches_0.1.xml, all instances of the tags status_id and category_id are empty.

[Alpha]

Attached is a start at creating a conversion script (Python).  (The .patch must be applied first to remove invalid characters from the XML dump.)
Unfortunately SourceForge import does not tell you what the errors are when an import fails, so this will not be easy.

[oBFusCATed]

I don't think we should do any migration at all.
We cannot match the users on the two systems, but most bugs require a dialogue with the user in order to gather more information or to understand what the problem was. Thus will end with a pile of bugs no one would bother to try to fix.

[ollydbg]

@Alpha, maybe, we should ask the questions on SF, I and Morten have asked there, see:
Bug/feature reqeust move to Sourceforge

@OBF, If we don't migrate, we may lose a lot of resources(some patches, feature requests in BerliOS are very useful)

[oBFusCATed]

If something is useful it would be requested again.
The bug tracker on berlios is full of invalid or abandoned (by the reporter) issues.

[BlueHazzard]

I'm with obfuscated, the patch and also the bugtracker on berlios where to old, and to bad maintained to get useful things from them. Also if some patch where useful they are now integrated or they where not necessary... I would count more on seeing it as a restart. The new bug tracker on sourceforge is again full with bugs/patches not maintained from the admins (no offense here!!!)...
They should get closed if there is nothing to say about them (like the first ticket)

greetings

[ollydbg]

If something is useful it would be requested again.
The bug tracker on berlios is full of invalid or abandoned (by the reporter) issues.

Yes, there are many invalid issues. But I once added some issues as my TODO lists, and now they are all buried in the exported xml files  :-\ )
So it is great if the exported xml files can be imported to SF's ticket system.

[Alpha]

I have been thinking about this, and perhaps it is better if we create a read-only page for the history, and allow SF to start fresh.  Here is my beginning:
https://github.com/alpha0010/cb-history
http://alpha0010.github.io/cb-history/patches.html

[ollydbg]

I have been thinking about this, and perhaps it is better if we create a read-only page for the history, and allow SF to start fresh.  Here is my beginning:
https://github.com/alpha0010/cb-history
http://alpha0010.github.io/cb-history/patches.html

Nice work, the html page looks good.

[Alpha]

The bugs listing is populated.
http://alpha0010.github.io/cb-history/bugs.html

Next up, features list.  Then I will see what I can do about filtering and searching.

[ollydbg]

The bugs listing is populated.
http://alpha0010.github.io/cb-history/bugs.html

Next up, features list.  Then I will see what I can do about filtering and searching.

Great.
One suggestion:
Is it possible to translate the link in the comments of Patch to Bug items?
See: http://alpha0010.github.io/cb-history/patches/3502-Allow_C_11_com.html There is a link:

Code Select Expand

https://developer.berlios.de/bugs/?func=detailbug&bug_id=19125&group_id=5358
in the comments.

Thanks.

[Alpha]

Is it possible to translate the link in the comments of Patch to Bug items?

I think so.  I already have some local code starting that; but I think I should finish the features list first so I can cross link between the three.

[ollydbg]

Hi, alpha, I may be aggressive. Here is another idea: once a bug is fixed in our trunk, can the bug web page be marked as closed or fixed. I mean if it can have futures(API) that devs have rights to edit the issue item. Thanks.

[ollydbg]

I have update our wiki home page, so that bugs/features direct to SF and the pages your created.