Skip to content
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

Merged
merged 2 commits into from
May 4, 2021
Merged

Conversation

dr0i
Copy link
Member

@dr0i dr0i commented Apr 29, 2021

See #311.

@dr0i dr0i requested a review from fsteeg April 29, 2021 14:02
@acka47 acka47 linked an issue Apr 30, 2021 that may be closed by this pull request
4 tasks
Copy link
Member

@fsteeg fsteeg left a 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.

@fsteeg fsteeg assigned dr0i and unassigned fsteeg May 3, 2021
@dr0i
Copy link
Member Author

dr0i commented May 3, 2021

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 organization may make sense - it is defined as

Configures the organization for the publication represented by this POM.

(https://docs.gradle.org/current/dsl/org.gradle.api.publish.maven.MavenPom.html#org.gradle.api.publish.maven.MavenPom:organization(org.gradle.api.Action)

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.
What do you think?

@dr0i dr0i assigned fsteeg and unassigned dr0i May 3, 2021
@fsteeg
Copy link
Member

fsteeg commented May 3, 2021

Looking at the way the organization is used e.g. here, I think it would make sense to point to the GitHub organization with something like name Metafacture & url https://github.com/metafacture

@fsteeg fsteeg assigned dr0i and unassigned fsteeg May 3, 2021
Point organization to github.com/metafacture to emphasize the community
character.
@dr0i
Copy link
Member Author

dr0i commented May 3, 2021

Removed developers section and point to github organization.

@dr0i dr0i assigned fsteeg and unassigned dr0i May 3, 2021
@fsteeg fsteeg assigned dr0i and unassigned fsteeg May 4, 2021
@dr0i dr0i merged commit 6f3a197 into master May 4, 2021
@dr0i dr0i deleted the 311-updateDevelopersData branch May 4, 2021 13:26
blackwinter pushed a commit that referenced this pull request Dec 13, 2024
Add multiple missing playground examples for fix functions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update release and publish process
2 participants