From @localheinz to @ergebnis
With 2019 in review and 2020 coming closer, I am sorting out a few things related to open-source projects I am maintaining.
Move
I have decided to move the open-source PHP projects I am currently maintaining on my personal account @localheinz
to the organization @ergebnis
on GitHub.
The following projects have been moved so far:
-
ergebnis/classy
-
ergebnis/clock
-
ergebnis/composer-normalize
-
ergebnis/composer-normalize-action
-
ergebnis/factory-girl-definition
-
ergebnis/factory-muffin-definition
-
ergebnis/faker-provider
-
ergebnis/github-changelog
-
ergebnis/http-method
-
ergebnis/json-normalizer
-
ergebnis/json-printer
-
ergebnis/php-cs-fixer-config
-
ergebnis/php-library-template
-
ergebnis/phpunit-framework-constraint
Why
At the moment, I have ~350 public repositories under my personal account. Most of these repositories are forks of projects I have contributed to in the past, and only a few of them are sources.
By moving the source repositories to a separate organization:
- they become more visible to me and can be more easily be discovered by others
- they become less attached to my person and maintenance can be more easily transferred to collaborators when necessary
- adding and managing maintainers or collaborators becomes a lot easier
If you are using any of the packages provided by these repositories: thank you! I am happy that I - standing on the shoulders of giants - have built something useful for others.
In any case, take a look at CHANGELOG.md
; I have provided instructions for updating. In most cases, the only things that have changed are vendor prefixes (from localheinz
to ergebnis
) and namespaces (from Localheinz
to Ergebnis
).
How
Perhaps you have been considering to do something similar?
Here is an example of how I moved localheinz/test-util
to ergebnis/test-util
:
- transfer ownership
- rename references
localheinz/test-util
toergebnis/test-util
- rename namespace
Localheinz\Test\Util
toErgebnis\Test\Util
- provide details on how to update in
CHANGELOG.md
- submit package
ergebnis/test-util
to Packagist - ensure that integration with Packagist works
- abandon package
localheinz/test-util
on Packagist and suggestergebnis/test-util
as a replacement - tag and push a new major release of
ergebnis/test-util
- update packages previously using
localheinz/test-util
to usingergebnis/test-util
, for example, inergebnis/phpstan-rules
- keep fingers crossed 🤞
Archive
At the same time, I am archiving a few projects that I have never brought to a stage that makes sense keeping them around:
-
localheinz/composer-json-normalizer
-
localheinz/composer-require-checker-action
-
localheinz/data-structure
-
localheinz/github-pulse
-
localheinz/specification
-
localheinz/token
If you find the transition from @localheinz
to @ergebnis
difficult, please accept my apologies.
If you need any help, let me know, and I will see what I can do.
Do you find this article helpful?
Do you have feedback?
Just blogged: "From @localheinz to @ergebnis”https://t.co/xPTKckZsK4
— Andreas Möller (@localheinz) December 10, 2019