Projects without project page
Hi, Working on cleanup this weekend, I found that roughly one quarter of all projects never replaced their auto-generated project page. These projects will likely (I have yet to find out) come in two groups: those which never got off the ground (no commits in source control) and those which simply didn't bother setting up a project page. I'm thinking to point the project page to the source repository (e.g. GitLab) when the project has sources, but doesn't have a project page. As for the projects which never spawned code, I'm wondering: should we simply remove those off the system (after contacting the project members, of course)? I mean, there's little Common Lisp value in them... Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
I'm thinking to point the project page to the source repository (e.g. GitLab) when the project has sources, but doesn't have a project page.
That is a really good idea.
As for the projects which never spawned code, I'm wondering: should we simply remove those off the system (after contacting the project members, of course)? I mean, there's little Common Lisp value in them...
Definitely. They make the projects hub list frustrating to browse. Vladimir
Hi Mariano, others, On Mon, Oct 8, 2018, 05:36 Vladimir Sedach <vsedach@gmail.com> wrote:
I'm thinking to point the project page to the source repository (e.g. GitLab) when the project has sources, but doesn't have a project page.
That is a really good idea.
Ok, I know which projects don't have their project page replaced. I can publish that list here tomorrow. Some years ago, I wrote cl-gitlab ( https://gitlab.common-lisp.net/cl-gitlab/cl-gitlab). Maybe that can be leveraged to detect which groups don't have any repositories so that we can combine those lists to remove the projects which never spawned anything? I'm happy to add anybody who wants to develop cl-gitlab to that project.
As for the projects which never spawned code, I'm wondering: should we simply remove those off the system (after contacting the project members, of course)? I mean, there's little Common Lisp value in them...
Definitely. They make the projects hub list frustrating to browse.
Vladimir
Erik
Hi all,
I'm thinking to point the project page to the source repository (e.g.
GitLab) when the project has sources, but doesn't have a project page.
That is a really good idea.
Ok, I know which projects don't have their project page replaced. I can publish that list here tomorrow.
Of all the projects which don't have a front page (list at the end of this mail), these don't have a git repository in GitLab: arxana asdf-install asdf-packaging boston-lisp chemboy cl-amqp cl-buchberger cl-cactus-kev cl-captcha cl-clickatell cl-gdbm cl-gtk2 clint cl-lazy-list cl-lexer cl-match cl-ode clotnet cl-peg cl-player cl-rundown cltl3 cl-yacc-ebnf common-math decl defmud docutrack fset graphic-forms innen israel-lisp jess-parse lisp-interface-library mit-cadr mk-defsystem movies objective-cl phorplay same sqlisp tioga trivial-features trivial-shell ucs-sort umpa-lumpa xml-psychiatrist Of these, these 4 seem to have a subversion repository though: common-math fset graphic-forms mit-cadr So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members): arxana asdf-install asdf-packaging boston-lisp chemboy cl-amqp cl-buchberger cl-cactus-kev cl-captcha cl-clickatell cl-gdbm cl-gtk2 clint cl-lazy-list cl-lexer cl-match cl-ode clotnet cl-peg cl-player cl-rundown cltl3 cl-yacc-ebnf decl defmud docutrack innen israel-lisp jess-parse lisp-interface-library mk-defsystem movies objective-cl phorplay same sqlisp tioga trivial-features trivial-shell ucs-sort umpa-lumpa xml-psychiatrist The remaining 69 projects will have their project page redirected to the GitLab group page (or in case there's only a Subversion repository, to Trac).
As for the projects which never spawned code, I'm wondering: should we
simply remove those off the system (after contacting the project members, of course)? I mean, there's little Common Lisp value in them...
Definitely. They make the projects hub list frustrating to browse.
Ok. I hope that the above proposal addresses that. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi all,
I'm thinking to point the project page to the source repository (e.g.
GitLab) when the project has sources, but doesn't have a project page.
That is a really good idea.
Ok, I know which projects don't have their project page replaced. I can publish that list here tomorrow.
Of all the projects which don't have a front page (list at the end of this mail), these don't have a git repository in GitLab:
Earlier today, I mailed the members of the projects below. Due to that, there's good and bad news. The bad news is that the site apparently had various configuration preferences as to serving "index.html" vs "index.shtml" and that the current setup preferred "index.shtml" while apparently a number of projects depended on the earlier preference of serving "index.html", causing these "index.html" files to be hidden for a few years. The good news is that we now corrected this setup issue and that it turns out that many more projects now actually serve a project page. While there are still a few projects which didn't set up a project page, their number is now much lower! Possibly this applies to the 69 projects which I was about to redirect to GitLab too. I'm still investigating. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system: cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Fair enough. If we wanted to re-open one of them, should we make a whole new project? Cheers Marco
On Oct 26, 2018, at 11:42 , Erik Huelsmann <ehuels@gmail.com> wrote:
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:
cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Marco Antoniotti
On Fri, Oct 26, 2018 at 1:35 PM Marco Antoniotti <marcoxa@cs.nyu.edu> wrote:
Fair enough.
If we wanted to re-open one of them, should we make a whole new project?
The net effect would be the same as restoring, since the projects didn't contain more than the initial/initialization content. So, yes, you'd request a new one. By the way, let me be clear that you should feel completely free to request projects at any time! It's just that in the past projects have been requested which haven't materialized and we're now cleaning those up. It's probably good to note that during the cleanup process I've been going through over the past weeks/months, I've noticed that I have no means to know when a project was requested. Same for users. And thus, I have no means to establish if a project was established maybe only a few months back (and that it should be given more time to mature) or that it is a very old project which should have matured. I'll be working to store metadata like it about our projects to help the system admins make informed decisions with more data available. Regards, Erik.
Hi Erik, Trivial-features is still needed and it has no other home site. Until we decide what to do with it, can you please resurrect the project ?
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):>>
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:> cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com[1] -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. Links: 1. http://efficito.com/
Hi Stelian, Sure, I can. Actually, before I worked on this removal, I specifically looked at trivial-features. As I remember, it was migrated into GitLab with the original Git repository migration. Then, someone (presumably Fare) moved the repository to https://gitlab.common-lisp.net/xcvb/trivial-features which means the repository is still on common-lisp.net, but the project web page is empty and the gitlab group (our definition of a project) doesn't hold any content. So, I didn't actually delete the trivial-features repository. We can do two things: 1. Recreate the trivial-features project (and gitlab group) and ask Fare to move trival-features back into that 2. Work with the repository as located in the xcvb group (Also note that I think the xcvb group (and Fare?) acted like a big vacuumcleaner at the time: there are many repositories under the xcvb group, which - now that xcvb is probably a dead project - might need to be split out?) Regards, Erik. On Fri, Oct 26, 2018 at 2:23 PM Stelian Ionescu <sionescu@cddr.org> wrote:
Hi Erik,
Trivial-features is still needed and it has no other home site. Until we decide what to do with it, can you please resurrect the project ?
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:
cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
I don't know why Stelian says the common-lisp.net project is needed. trivial-features lives at https://github.com/trivial-features/trivial-features and https://cliki.net/trivial-features. Perhaps there were tarballs hosted in the common-lisp.net project at some point? In any case, Quicklisp grabs the sources from github.com and there's no link to common-lisp.net anywhere in the documentation. HTH, Luís On Fri, Oct 26, 2018 at 1:29 PM Erik Huelsmann <ehuels@gmail.com> wrote:
Hi Stelian,
Sure, I can. Actually, before I worked on this removal, I specifically looked at trivial-features. As I remember, it was migrated into GitLab with the original Git repository migration. Then, someone (presumably Fare) moved the repository to https://gitlab.common-lisp.net/xcvb/trivial-features which means the repository is still on common-lisp.net, but the project web page is empty and the gitlab group (our definition of a project) doesn't hold any content.
So, I didn't actually delete the trivial-features repository.
We can do two things:
1. Recreate the trivial-features project (and gitlab group) and ask Fare to move trival-features back into that 2. Work with the repository as located in the xcvb group
(Also note that I think the xcvb group (and Fare?) acted like a big vacuumcleaner at the time: there are many repositories under the xcvb group, which - now that xcvb is probably a dead project - might need to be split out?)
Regards,
Erik.
On Fri, Oct 26, 2018 at 2:23 PM Stelian Ionescu <sionescu@cddr.org> wrote:
Hi Erik,
Trivial-features is still needed and it has no other home site. Until we decide what to do with it, can you please resurrect the project ?
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:
cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
You're right Luis, I couldn't find it on Github :(
I don't know why Stelian says the common-lisp.net project is needed. trivial-features lives at https://github.com/trivial-features/trivial-features and https://cliki.net/trivial-features. Perhaps there were tarballs hosted in the common-lisp.net project at some point? In any case, Quicklisp grabs the sources from github.com and there's no link to common- lisp.net anywhere in the documentation.> HTH, Luís
On Fri, Oct 26, 2018 at 1:29 PM Erik Huelsmann <ehuels@gmail.com> wrote:>> Hi Stelian,
Sure, I can. Actually, before I worked on this removal, I specifically looked at trivial-features. As I remember, it was migrated into GitLab with the original Git repository migration. Then, someone (presumably Fare) moved the repository to https://gitlab.common-lisp.net/xcvb/trivial-features which means the repository is still on common-lisp.net, but the project web page is empty and the gitlab group (our definition of a project) doesn't hold any content.>> So, I didn't actually delete the trivial-features repository.
We can do two things:
1. Recreate the trivial-features project (and gitlab group) and ask Fare to move trival-features back into that>> 2. Work with the repository as located in the xcvb group
(Also note that I think the xcvb group (and Fare?) acted like a big vacuumcleaner at the time: there are many repositories under the xcvb group, which - now that xcvb is probably a dead project - might need to be split out?)>> Regards,
Erik.
On Fri, Oct 26, 2018 at 2:23 PM Stelian Ionescu <sionescu@cddr.org> wrote:>>> __
Hi Erik,
Trivial-features is still needed and it has no other home site. Until we decide what to do with it, can you please resurrect the project ?>>>
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):>>>>>
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:>>>> cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com[1] -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-- Bye,
Erik.
http://efficito.com[2] -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. Links: 1. http://efficito.com/ 2. http://efficito.com/
OK, cool. Mystery solved! :-) On Fri, Oct 26, 2018 at 4:47 PM Stelian Ionescu <sionescu@cddr.org> wrote:
You're right Luis, I couldn't find it on Github :(
I don't know why Stelian says the common-lisp.net project is needed. trivial-features lives at https://github.com/trivial-features/trivial-features and https://cliki.net/trivial-features. Perhaps there were tarballs hosted in the common-lisp.net project at some point? In any case, Quicklisp grabs the sources from github.com and there's no link to common-lisp.net anywhere in the documentation.
HTH, Luís
On Fri, Oct 26, 2018 at 1:29 PM Erik Huelsmann <ehuels@gmail.com> wrote:
Hi Stelian,
Sure, I can. Actually, before I worked on this removal, I specifically looked at trivial-features. As I remember, it was migrated into GitLab with the original Git repository migration. Then, someone (presumably Fare) moved the repository to https://gitlab.common-lisp.net/xcvb/trivial-features which means the repository is still on common-lisp.net, but the project web page is empty and the gitlab group (our definition of a project) doesn't hold any content.
So, I didn't actually delete the trivial-features repository.
We can do two things:
1. Recreate the trivial-features project (and gitlab group) and ask Fare to move trival-features back into that 2. Work with the repository as located in the xcvb group
(Also note that I think the xcvb group (and Fare?) acted like a big vacuumcleaner at the time: there are many repositories under the xcvb group, which - now that xcvb is probably a dead project - might need to be split out?)
Regards,
Erik.
On Fri, Oct 26, 2018 at 2:23 PM Stelian Ionescu <sionescu@cddr.org> wrote:
Hi Erik,
Trivial-features is still needed and it has no other home site. Until we decide what to do with it, can you please resurrect the project ?
Hi All,
So I propose to remove from the site common-lisp.net, the following 42 projects (after contacting their respective project members):
After further cleaning up the list (taking into account the Apache configuration error we encountered before), I've now removed/archived the following empty projects from our system:
cl-amqp cl-cactus-kev cl-captcha cl-gdbm clint cl-lazy-list cl-lexer clotnet cl-player cl-rundown cltl3 decl defmud docutrack israel-lisp lisp-interface-library mk-defsystem movies objective-cl phorplay same trivial-features umpa-lumpa
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
On Mon, Oct 8, 2018 at 5:36 AM Vladimir Sedach <vsedach@gmail.com> wrote:
I'm thinking to point the project page to the source repository (e.g. GitLab) when the project has sources, but doesn't have a project page.
That is a really good idea.
This is now implemented for all projects, except for "mit-cadr". The problem with mit-cadr is that they use the "public_html" dir to host downloads, but did not bother changing the project's default page. The technical implementation I used to support the redirect doesn't allow hosting the downloads *and* redirect the projects page. I'm thinking how I can resolve this last project's redirect. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
downloads, but did not bother changing the project's default page. The technical implementation I used to support the redirect doesn't allow hosting the downloads *and* redirect the projects page. I'm thinking how I can resolve this last project's redirect.
A meta refresh in index.html should work.
participants (6)
-
Erik Huelsmann -
Luís Oliveira -
Marco Antoniotti -
Stelian Ionescu -
vas＠oneofus.la -
Vladimir Sedach