Skip to content
This repository was archived by the owner on Oct 8, 2025. It is now read-only.
This repository was archived by the owner on Oct 8, 2025. It is now read-only.

[Meta] Archiving of repositories #36

@jupjohn

Description

@jupjohn

It's clear that Lukkit is - and has been for a long time - dead. With the last release being 5 years ago, and no real progress being made on v3 outside of hopes and dreams, I believe it's time to archive repository and all others under the Lukkit organisation.

Thank you to anyone who contributed to this over the years - from it's original developer who was more than happy to hand it over to a 16 year-old me, to those who gave their time up until the last release. On a personal note, this was my first "real" software project and even if I didn't give it as much love as it needed (I certainly gave heaps ideas,) it played a part in getting me into the industry I'm in now. I hope others got something out of it too ❤️

Archive plan

As part of archiving this project, we should do the following:

  • Create an organisation profile README with an archive notice & link to this issue;
  • Announce archiving of repos & link to this issue in the Lukkit Discord server;
  • Make all channels in the Lukkit Discord server read-only;
  • Create a #gh-maintainer-transfer channel in the Lukkit Discord server for possible ownership transfers (see handling further development below);
  • Finally, archive the Lukkit GitHub organisation.

Handling further development

If someone(s) wants to continue Lukkit in the future, then I would expect the following before handing over the organisation/project & resources:

  1. The transferee(s) must be actively developing/maintaining a fork of the Lukkit plugin, with non-trivial changes (i.e. not just a README update);
  2. The transferee(s) must be willing to take full ownership of the project, with no support from current maintainers;
  3. The transferee(s) must take ownership of all non-source resources (lukkit.net domain, GitBooks site, Discord server, Spigot plugin page);
  4. A majority of existing owners must agree to transfer.

If this project is archived and you would like to take ownership, we'll have a #gh-maintainer-transfer channel available in the Lukkit Discord. Tag the maintainers and we'll go from there, or reach out to myself via email if you get nothing.


@AL1L @mathhulk as the other two org owners, I'd like sign-off (and weigh-in if you have anything to add) from the both of you.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions