Considering to Archive LDT project
As LDT is project is not active/maintain anymore and for now nobody want to take the project over, we should maybe consider to archive it.
The desired way :
Ideally I wanted something which looks like (from most important to less one):
- a static website MUST be kept with clear status of it.
- an easy way to download the last version of the product (and maybe update sites) MUST be kept (as the software is still usable).
- Wiki (documentation) SHOULD be kept. (read-only is OK)
- Source code SHOULD be accessible (at least a readonly git repository)
- Forum MAY be kept. (read-only is OK)
- Mailing lists can be disabled but archives MAY be eventually be preserved.
- Jenkins instance MUST be removed.
The rational behind this: The project is no more maintained but the software is still usable so users should be able to :
- find it (search engine),
- download it
- know how to use it (access to user documentation and question/response about it)
- eventually understand how it works (access to code and eventually dev documentation)
The current Eclipse foundation way :
But current eclipse archive project seems to radical to me :
When we archive a project all of it's resources(source,downloads,archived downloads) are packed into a single tarball on archives.eclipse.org and the web URLs redirect to a list of archived projects which will include LDT(and a link to the tarball).
(source : eclipsefdn/helpdesk#3454 (comment 1351467))
The recommendation
The Eclipse Foundation recommendation :
If you feel that there is value in keeping the resource of the project active, you should consider keeping the project itself active, but shut down those resources (e.g., build instance) that you no longer need.
Wayne
Current state :
Goal | state | status |
---|---|---|
a static website MUST be kept with clear status of it |
Site Web is updated. ldt-website@76130379, ldt-website@dfc18214 |
|
an easy way to download the last version of the product (and maybe update sites) MUST be kept (as the software is still usable) | Already available on ldt website (only artifacts pointed by ldt#installation website was kept in download.eclipse.org, I also deleted some useless artifact on archive.eclipse.org ~10GB free) |
|
Wiki (documentation) SHOULD be kept. (read-only is OK) |
eclipse wiki will be close. documentation was migrate to static one in website ldt-website@27c52ad0 See migration details |
|
Source code SHOULD be accessible (at least a readonly git repository) | git repo was move to gitlab | |
Forum MAY eventually be kept in read-only state |
forum is now read-only/archived. see : eclipsefdn/helpdesk#4034 (comment 1475288) |
|
Mailing lists can be disabled but archives MAY be eventually be preserved | Eclipse foundation want to keep mailing list enable for active project so no way to remove ldt-dev. See : eclipsefdn/helpdesk#4034 (comment 1475241) |
|
Jenkins instance MUST be removed | Jenkins instance is close |