-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update developer and organization data #363
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, do we actually need that information in the config file? There is also a section for contributors in the documentation, which we are not using so far. The developers section is meant for committers. But that whole distinction of committers and contributors is kind of obsolete with Git. The actual overview of contributors is at https://github.com/metafacture/metafacture-core/graphs/contributors. Maybe we can simply remove the developers
section? And the top-level organization
too, since the idea is that this is a community project. That would leave only the header change and the update of the ciManagement
.
The information is used to build e.g. 'https://repo1.maven.org/maven2/org/metafacture/metamorph/5.2.0/metamorph-5.2.0.pom'. I don't know if it is used by anyone or of it is of any importance. But at least the
and may make sense by taking dedicated responsibility bound to an organization (which may, as you note, handed over to an other organization) building some kind of trust regarding a future development. |
Looking at the way the |
Point organization to github.com/metafacture to emphasize the community character.
Removed developers section and point to github organization. |
Add multiple missing playground examples for fix functions
See #311.