Skip to content

Proposal with changes to the organization Manifest. #53

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Proposal with changes to the organization Manifest. #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 35 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,28 +35,37 @@ not present any other legal issues.
* OSI approved license are strongly preferred.
* Mods do not need to be minetest-licensing compatible (meaning, (A)GPL3.0+ is fine).
* Non-OSI licenses may be acceptable, but this is determined on a one-by-one case.
* Pure Public Domain is not acceptable, however WTFPL, MIT or similar usually is acceptable.
* Pure Public Domain is not acceptable, however ISC, MIT or similar usually is acceptable.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about CC0, does that count as "pure public domain"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I consider it not the same. For now, CC0 is, in my opinion, OK for the time being.

* WTFPL is expressly discouraged and we ask that you relicense to another license
before submitting. There are several appropriate alternatives, such as MIT, ISC etc..

The project admins reserve the right to discontinue, remove or refuse any project based
on legality, content or other, at their discretion.
on legality, content or other, at their discretion. However, removal requests for other
than reasons other than non-acceptable content or licensing are unlikely to be granted.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate other than.
Also, a different wording that I think works a bit better:

The project admins reserve the right to discontinue, remove or refuse any project based
on content, licensing, or other reasons, at their discretion. However, removal requests
for reasons other than unacceptable content or licensing are unlikely to be granted.


The original author of the mod should be the one submitting it to the minetest-mods
project. Only in exigent circumstances will a mod fork be allowed, and admins reserve
the right to refuse mod forks at their discretion. In general, forks are only allowed
if the original author clearly no longer maintains the project, and if the project has
been properly licensed by the original author, and last, that the project license has
remained unchanged in the fork.
remained unchanged in the fork. For the purpose of determining whether a mod is a fork
or an original work, we note that forks that were created from non-public sources where
the original work is not publicly available are not considered forks, but are considered
the original public works and acceptable.

Modpacks (groups of mods bundled together) are not permitted in minetest-mods, as they
make management more difficult and prevent users from installing only parts of of a
modpack. For cooperative maintenance of modpacks, see the minetest-modpacks team instead,
or look at the minetest-games project. (At the time of writing of this document, those
two teams/projects do not exist).
two teams/projects do not exist). A few modpacks exist in minetest-mods, but they are
the only ones and new modpacks will not be allowed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while those are technically modpacks, they are so for organisational reasons (mesecons comes to mind)
they aren't modpacks in the traditional sense: collections of unrelated mods to provide a complete experience for users

maybe clarify that or something

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer not to, because providing a technical exception case as to why modpacks are allowed will not be helpful in the long term I think, as people tend to look for excuses.

Having a historical cut-off (no more from now on) is a good way of saying "these mods were used on dozens of servers for years and we don't want them to become stale" while still being able to say "new modpacks should preferably be split up or made into a single mod" to new mods and bring the argument that those new mods aren't widely used yet so it's a better time..

All of this is also "at our discretion" as well. We can still make exceptions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really like to idea of outright dismissing modpacks. We can reject modpacks that have a bunch of unrelated stuff, but splitting mods up into modpacks can be useful for organization (eg, Technic and Mesecons and previously mentioned).

It seems like this would only encourage modders to combine a modpack into one huge mod, which isn't really any better.


Mods should ensure that they have all the needed files present to assure dependencies
and mod metadata is present. description.txt is required to be present, and we strongly
urge mods to have mod.conf present, as well as a screenshot.png file, a LICENSE file
and a README.md file as well.
and mod metadata is present. description.txt and mod.conf files are required to be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Joining the partly late. While going towards 5.0.0, description.txt is no longer required since it can be included in mod.conf.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, we might want to keep it until 0.4.16/17 servers are mostly gone, though....

present, and we strongly request that mods have a screenshot.png file, a LICENSE file
and a README.md file as well. Having a clear license statement is obviously a hard
requirement, and you must be able to provide evidence that this license is proper if
requested.

## Member organization

Expand Down Expand Up @@ -92,6 +101,25 @@ mods.
* committer shall due their due dilligence cooperating with other committer, author and
admin in maintaining the mod as a team.

## Governance

The organization shall regularly assess and verify that enough administrators are active
and acting in the duty of administrator.

The organization and it's administrators shall periodically report on and consult with
authors and committers to determine if the amount of administrators is sufficient
for the proper functioning of the organization. If the current amount of administrators
is found to be insufficient by either the admins or the authors, then the organization
including admins, authors and committers shall appoint the appropriate amount of
new admins to the organization, and the existing admins shall grant the adminstrator
access to the new admin on the organization's github organization.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like the emphasis on "number". You can't just count people to determine how capable they are of handling a workload. I think this should focus more on whether the current administrators are able to handle the workload.


The appointment of new administrators can be vetoed by any active administrator, except
no veto can be issued by any administrator that has announced their departure from the
organization. The collective of all active admins, authors and committers can also veto
new administrators if the number of people supporting that veto is larger than the number
of people opposing that veto.

## Namespace Organization

Many different versions of mods exists, and many mods have similar names but sometimes
Expand Down