Brickimedia has about 460+ (463 to be exact at the time this was posted), and 398 are closed while 65 are open. Is it possible for all of them to be migrated (old for historical reference/archive), while the current because they haven't be fixed yet, just current issues, or no migration at all?
Issues are located at https://github.com/brickimedia/brickimedia/issues
I don't think importing all of them is the right way to go, some of them apply to Brickipedia exclusively and not the code in the projects. I'd just recreate relevant ones, the person who authored the tickets at GitHub can re-author them here if they're active and willing or you can just copy and paste them.
Hey @Aklapper, since you're the bug manager, are we allowed to migrate our relevant issues over to this platform from GitHub?
Hi! Of course. You can do whatever helps you to effectively manage your work. :)
Technically, I am just not aware of an import script from GitHub so I cannot offer help when it comes to fiddling with APIs. (I wonder which projects we have imported into Phab before and if that was from SourceForge or GitHub. Maybe maybe @valhallasw remembers something.)
Socially, it's up to the Brickimedia team to define criteria and decide whether to import all issues from GitHub or just some (also because I do not have enough knowledge to judge what is "irrelevant" and why).
For Pywikibot, @Legoktm did the initial SourceForce -> Bugzilla migration; those tickets were then migrated here. I think Toolserver's JIRA was also first migrated to Bugzilla....
so as far as import is concerned, I think the best idea is to take a look at the code behind @rtimport. If you only care about open bugs, I would suggest doing it by hand -- that will take a few hours, but is probably faster than integrating the APIs (and getting all edge cases right).
The importbots we have had are all members of the project, I could see a GitHub bot being usable in the future or other extension devs if they want to move over.
If we set it to use conduit to import them so they can claim the imported tasks would be handy, Github has a standard format for email address and can also be pulled from the api (the former can be added as a secondary email in phab)
Thanks guys, I think I shall import them by hand later this weekend once I talk with the others and look through the tickets. :)
I agree with @valhallasw, being completely honest I'd probably mess up trying to use the API haha
Not resolved - there's still 37 tickets open as of now, I'll create them and spread out over the week ( A. because there's a lot and B. don't want to create too much noise in notifications)