Transition plan for Laminas-Commons

[visto9259]

Please review and comment the following transition plan:

1. Create the LM-Commons GitHub organization with the same teams and access rights as Laminas-Commons. (@visto9259 or @matwright). Report on Gitter once that's done.
2. I guess we should create a Gitter for LM-Commons or change the name of the existing Gitter?
3. Import the Laminas-Commons repos into LM-Commons. This will bring over the history of each repo but will not bring over the open issues and open Pull Request. We can copy the issues in the LM-Commons repos with a link to the orignal issue in the Laminas-Commons repo. That's what the folks at Laminas seem to have done with the already existing ZF issues. Not sure what to do with the Pull Request. We can always ask the author to re-submit the PR on the new repo.
4. For each imported repo:
   • Update the name in Composer to LM-Commons/LmcUser and so on.
   • Update any references to Laminas-Commons to LM-Commons in documentation like the README.MD
   • Update any badges in the README like Buid, Scrutinizer, etc.
   • Make sure that CI testing succeeds and then release the code. Unless there is change in the code, I think we should keep the same release version number as the original repo.
   • Submit the new repos to Packagist (I think it has to be either @visto9259 or @matwright that can do this step and make sure that maintainers are added as well)
   • Test that you can install it in your application to make sure that dependencies work in Composer
5. Once a repo is released, let us know and we will archive/abandon the old repo and state the name of the new repo as a replacement.
6. Once all repos are migrated, we will delete Laminas-Commons after about 3-6 months. We can monitor downloads on Packagist to see if people are still using the old repos. Hopefully, everybody will have transitioned to Lm-Commons by then.

I can take care of LmcCors and LmcRbacMVC.
@matwright, are you doing LmcUser?
Who wants to do LmcRbac? If no takers, I'll do it.
Eric

[svycka]

Also, maybe would be a good idea to add https://getcomposer.org/doc/04-schema.md#replace

[visto9259]

Agreed.

[matwright]

@visto9259 yes, I can do LmcUser
I'm happy to set up new organisation and take care of the various third party integrations, too. (Gitter/Packagist/Travis)

I don't mind taking LmcRbac if there are no other takers.