Migration to another issue tracker
If Forge is to be kept for other projects (apart from the Core), then actually a new tag is needed for the new platform.
#1 Updated by Chris topher almost 2 years ago
E.g. for GitHub: Since, unlike on Forge, issue numbers are not unique on GitHub, but are repeated for each project, owner and project name have to be part of the tag as well, e.g.
<github>TYPO3-Documentation/TYPO3CMS-Guide-Installation/1</github>. Another option would be to allow providing a full GitHub URL inside the tag. This would be way more user-friendly.
- The real name of the user closing the issue obviously is not part of that response. It can be obtained using the user name (e.g. from
['closed_by']['url']) in a new request to for example https://api.github.com/users/fsuter =>
['name']. See https://developer.github.com/v3/users/#get-a-single-user.
- The first e.g. 100 signs of
['body']might be a nice idea for a tooltip of the link we create.
Another idea would be to additionally add another tag: E.g.
<t3github> or something like that, which links to the issue in the GitHub TYPO3 CMS project. That way, actually only the issue number needs to be provided in order to use the tag.
(Only) for those issues, which are actually moved to GitHub, the old tag can be replaced by the new one. A mapping of old to new issue number would be good to have for this case. Should e.g. be possible by using wget to map the Forge issue number to the issue number of the redirect target. And the server team should have such a mapping then already. Text replacement can be done in the text and revision/logging tables directly via MySQL queries.
#2 Updated by Sybille Peters 6 months ago
There is now a wiki.typo3.org project on Gitlab. I suggest to migrate the remaining issues there: https://gitlab.typo3.org/services/wiki.typo3.org
I don't propose maintaining Wiki issues on GitHub https://github.com/TYPO3-Documentation because the Wiki and the Docs Team are 2 separate things. There is some overlap, when it comes to documentation, but the Wiki contains a number of other content (events, exceptions etc.) and the teams working on this are mutually exclusive.
In 2018, the docs team decided it is no longer responsible of the Wiki (among other things), see https://github.com/TYPO3-Documentation/T3DocTeam/issues/26#issuecomment-408606287
This was a decision due to very little peoplepower and the overwhelming number of task.
So, in addition to migrating the issues here, I think it would be good to form a Wiki team or at least separate the Wiki issues, Wiki slack channel (already the case with #typo3-wiki) and handling of the Wiki in general for documentation on docs.typo3.org.