Knowledge Base / Policy / Abandoned and Inactive Projects

Project Definitions

What is an abandoned project?

Really there are two types of abandoned projects. There are ones that we've marked as abandoned, and there are ones that are abandoned in practise, but not in name.

We give projects a long time, a very long time, before we mark them as abandoned. So these types are considered essentially dead. However, if the project's license allows, it can be resurrected.

The second category is for a project which hasn't been updated in a long time; the project leader seems to be MIA and/or the project is slowly fading due to bitrot.

What is an inactive project?

An inactive project is one which has not had any activity for a period of time.

What is a mature project?

Some projects are feature complete and essentially will not break when patches come out. These projects will not get a lot of attention from their authors simply because the attention is not needed.

If you feel that your project will not need updates in the future, please mark it as mature. Do not mark a project as mature simply as a way to circumvent the automatic status changes; they were put into place for a reason.

Reclaiming your abandoned or inactive project

These project statuses are often set automatically by the system. If the status was set and you do not feel that it is correct, please do not submit a ticket or a report: You can manually change the status by going to Project management, Edit project, then changing the Development stage near the bottom of the page.

Taking over an abandoned project

You should attempt to contact the author directly - we will do nothing without the project owner's express permission. If you cannot receive permission to take over the project for whatever reason, and that project's license is permissive of forking, you should fork the project using a different name from the original.

We do not allow fan updates, as most of these are fire-once-and-forget and we also want to avoid a situation of having five different versions of "Awesome AddOn X Continued" which only serves to confuse users of the original project.

Uploading to another authors work to CurseForge

In certain instances, the original author(s) will not want to maintain their project on CurseForge. In these cases when creating a project you must do the following:

  1. Obtain explicit permission to upload to CurseForge. This permission must be included in the project description.
  2. Link back to the original hosting location of the project.
  3. Credit the original authors in your main description.

Required project elements when taking over a project

When taking over a project we require that you observe the following rules:

  1. The original project author(s) are kept on the project as authors (There is now a former author role for the site, please use that if the author is no longer active.).
  2. The main description of the project identifies that you have taken over from another author and lists who previously worked on the project.
  3. Credit the original author(s) in the code (aka X-credits in a .toc)