Move repos to other organisations or archive them

[bertfrees]

• forked repos to be removed (if needed, merge with upstream, and in the future, when others want to contribute, they should make their own fork)
  • [ ] pipeline-mod-braille
  • [ ] move branches to daisy/pipeline-mod-braille
  • [ ] original repo can possibly be split up into several sub-repos, each of which can possibly be moved later on to the organisation of its main maintainer
  • [ ] issues in fork should be moved/copied to original repo
  • [ ] dotify
  • [x] dotify.formatter.impl
  • [ ] brailleutils
  • [ ] brailleutils.api
  • [x] pipeline-assembly
  • others should make forks in their own organisations in order to be able to make releases whenever they want. PRs should be made to upstream from time to time
  • [ ] obfl
  • [ ] liblouis
  • issues should either be fixed or moved/copied to original repo
  • [ ] braille-specs
  • [ ] hyphen
  • [x] jhyphen
• repos to be moved to organisation of the new maintainer:
  • [x] pipeline-mod-sbs (moved to sbsdev)
  • [x] pipeline-mod-nlb (moved to nlbdev)
  • [x] pipeline-mod-mtm (moved to mtmse)
  • [x] pipeline-mod-celia (moved to celiafi)
  • [ ] pipeline-mod-nota -> Notalib
  • [ ] pipeline-mod-dedicon (copied to BitBucket but issues are not moved)
• forked repos we should try to merge with upstream (as much as possible)
  • [ ] respec
  • [ ] jStyleParser
  • [ ] hyphen
  • [ ] jsass
• repos to be moved to ... (daisy, braillespecs, brailleapps, liblouis, ... ?)
  • [x] braille-css-spec (moved to braillespecs)
  • [x] libhyphen-nar (moved to daisy)
  • [x] braille-css (moved to daisy)
  • [x] jStyleParser (moved to daisy)
  • [x] jsass (moved to daisy)
  • [ ] liblouis-table-spec -> Liblouis
  • [ ] respec?
  • [ ] hyphen?
• move issues in snaekobbi/issues to other repos (or close)
  • [ ] https://github.com/snaekobbi/issues/issues/3
  • [x] https://github.com/snaekobbi/issues/issues/8
  • [x] https://github.com/snaekobbi/issues/issues/18
  • [x] https://github.com/snaekobbi/issues/issues/21
  • [ ] https://github.com/snaekobbi/issues/issues/23
  • [x] https://github.com/snaekobbi/issues/issues/24
  • [x] https://github.com/snaekobbi/issues/issues/25
  • [x] https://github.com/snaekobbi/issues/issues/28
  • [x] https://github.com/snaekobbi/issues/issues/29
  • [ ] https://github.com/snaekobbi/issues/issues/30
• all other repos should be "archived", if that is possible

Github does not support moving issues to another repo. (It was a mistake of me to activate the issues on the pipeline-mod-braille and liblouis forks.) We'll have to copy them with some tool, deactivate the original issues and update all references to them. Or, if it is possible to deactivate issues while still be able to access them using their URL, we don't have to bother about updating references, we can instead just reference the original issues from the copies and visa-versa.

[josteinaj]

Issues can be moved with a tool like this: https://github-issue-mover.appspot.com/

I've used it before to move issues between different DP2 repos and it works well. I think it's the tool in the above link I used, but there's probably others available.

[jukkae]

pipeline-mod-celia can be moved to celiafi organization (https://github.com/celiafi)

[bertfrees]

CC @EdmarS

[josteinaj]

Not sure if I have admin rights or not yet, but should I move it asap or should I wait a bit? (mod-nlb that is)

[bertfrees]

I've just made you admin. I would say just move.

[bertfrees]

if it is possible to deactivate issues while still be able to access them using their URL

It is possible to lock a conversation, and a note can be made in the project description/readme that new issues should be created in liblouis/liblouis and daisy/pipeline-mod-braille.

[bertfrees]

It is now possible to transfer issues to other repositories! https://help.github.com/articles/transferring-an-issue-to-another-repository

[bertfrees]

Unfortunately you can't move to other organisations yet :(