Bugzilla – Full Text Bug Listing
| Summary: | Move LDT project to github | ||
|---|---|---|---|
| Product: | Community | Reporter: | Simon Bernard <sbernard> |
| Component: | GitHub | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Simon Bernard
ping ? Sorry about the delay in responding, this clearly got lost somewhere. If the project is this inactive maybe we should just archive it, rather than moving things. Wayne, what do you think? -M. The project is almost inactive. Until now I did some very quick bug fixes and tried to follow the release train. With the new release train period, I didn't even succeed to follow the rhythm ... I tried to pass the baton : https://www.eclipse.org/forums/index.php/t/1090745/ But It's hard to find successors. I believed that maybe passing to github could help. But maybe, archiving is a better idea... It's an hard decision :/ What means archiving a project ? LDT is clearly not the future for Lua development, but I think the project is still useful and so it make sense to me to keep the website, the wiki and a way to download it. (In reply to Simon Bernard from comment #3) > What means archiving a project ? > LDT is clearly not the future for Lua development, but I think the project > is still useful and so it make sense to me to keep the website, the wiki and > a way to download it. Our usual process for archiving a project means we collect the source code, website and downloads into a single tarball linked from https://www.eclipse.org/projects/archives.php . The projects website is also updated to redirect to that page. All bugs for a project are moved into the z_archived product, under a project specific component . Mailing lists, and forums are closed to new posts, but the archives remain online. -M. Archiving sounds a bit too strong. If we looked at the statistic, the project is still downloaded : /ldt/products/stable/1.4.1/org.eclipse.ldt.product-win32.win32.x86_64.zip 12752 /ldt/products/stable/1.4.1/org.eclipse.ldt.product-linux.gtk.x86_64.tar.gz 1934 /ldt/products/stable/1.4.1/org.eclipse.ldt.product-macosx.cocoa.x86_64.tar.gz 1434 /stats/releases/oxygen/org.eclipse.ldt_1.4.1.201706020937 1770 /stats/releases/oxygen/org.eclipse.ldt.remote_1.4.1.201706020937 1701 I agree it's not so much but probably enough to justify to keep a website and a way to download it. (In reply to Simon Bernard from comment #5) > I agree it's not so much but probably enough to justify to keep a website > and a way to download it. Well under our archival process those things are still true. It's just that www.eclipse.org/ldt will redirect to the archived projects page, and the downloads for ldt will be included in the available tarball. We don't have the resources to keep orphaned projects in some limbo state between active and archived. > Well under our archival process those things are still true. It's just that www.eclipse.org/ldt will redirect to the archived projects page, and the downloads for ldt will be included in the available tarball.
Not really what I had in mind, I think with this nobody will download anything :/
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Based on our private discussion via the EMO inbox this past summer, we'll keep the project alive for now. However... The likelihood that moving the repository to GitHub will "facilitate contribution and maybe hand over" is very low without some effort from project team to recruit contributors. AFAIK, the project does not have the resources to invest that effort, so there's little point in moving the repository. For completeness, we do not migrate Bugzilla issues to GitHub Issues. I will mark this bug as WONTFIX. |