Hi all,
Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*).
As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-...
I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts?
Would people mind or even like to move to this functionality?
Regards,
Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure it's possible with gitlab pages. Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-... I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure
it's possible with gitlab pages.
Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the
option to log in on the host through ssh connections to manage their
hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the
majority of the repositories on the site - includes a hosting offer for
static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-
pages-to-community-edition/
I've not studied the functionality in depth, but I'm wondering: would
the time have come to start moving the project pages into GitLab by
using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
If there's no code hosting, then what is the purpose of c-l.net? Without the repositories, that only leaves the mailing lists and a few other random things, I think.
I am grateful for everything that c-l.net provides. Otherwise, I'd have to host them myself or find some other means of hosting everything else except the repos (for which there are many alternatives).
On Sat, May 6, 2017 at 4:56 PM, Anton Vodonosov avodonosov@yandex.ru wrote:
Several more words.
For many projects github pages might be enough. Also, code hosting can be done on github . Maybe we should encourage this to free cl.net supporters from maintenance of code hosting?
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure
it's possible with gitlab pages.
Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the
option to log in on the host through ssh connections to manage their
hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the
majority of the repositories on the site - includes a hosting offer for
static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-
pages-to-community-edition/
I've not studied the functionality in depth, but I'm wondering: would
the time have come to start moving the project pages into GitLab by
using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
I am not that happy about github (or sf.net or whatever).
I don’t like the github “one-size-fits-all” basic setup (sf.net is better in that respect).
My preference would be to keep c-l.net as is; however, I am not doing much work about it :)
Cheers — MA
On May 7, 2017, at 07:32 , Raymond Toy toy.raymond@gmail.com wrote:
If there's no code hosting, then what is the purpose of c-l.net? Without the repositories, that only leaves the mailing lists and a few other random things, I think.
I am grateful for everything that c-l.net provides. Otherwise, I'd have to host them myself or find some other means of hosting everything else except the repos (for which there are many alternatives).
On Sat, May 6, 2017 at 4:56 PM, Anton Vodonosov avodonosov@yandex.ru wrote: Several more words.
For many projects github pages might be enough. Also, code hosting can be done on github . Maybe we should encourage this to free cl.net supporters from maintenance of code hosting?
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote: Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure it's possible with gitlab pages. Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-... I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Ray
-- Marco Antoniotti
SourceForge is a very good example of why common-lisp.net should continue to provide repository hosting and you should host your projects' official repositories on c-l.net and encourage others to do the same.
In 2013 SourceForge was acquired by Dice Holdings, who proceeded to do things like infect downloadable binaries with spyware and adware. Fortunately for SourceForge users it was again sold to another company in 2016 who stopped the adware. For now.
I made the mistake of moving some of my projects' official repositories to github in 2012, and plan to move them back to c-l.net this year. You can always use github as another remote and get the benefits of their pull request interface.
In the long run having a non-profit entity like common-lisp.net provide Free Software hosting is a lot less work than dealing with "free" accounts from for-profit corporations that can modify or take away the service at any time (Google Code is a good example here).
Vladimir
Marco Antoniotti marcoxa@cs.nyu.edu writes:
I am not that happy about github (or sf.net or whatever).
I don’t like the github “one-size-fits-all” basic setup (sf.net is better in that respect).
My preference would be to keep c-l.net as is; however, I am not doing much work about it :)
Cheers — MA
On May 7, 2017, at 07:32 , Raymond Toy toy.raymond@gmail.com wrote:
If there's no code hosting, then what is the purpose of c-l.net? Without the repositories, that only leaves the mailing lists and a few other random things, I think.
I am grateful for everything that c-l.net provides. Otherwise, I'd have to host them myself or find some other means of hosting everything else except the repos (for which there are many alternatives).
On Sat, May 6, 2017 at 4:56 PM, Anton Vodonosov avodonosov@yandex.ru wrote: Several more words.
For many projects github pages might be enough. Also, code hosting can be done on github . Maybe we should encourage this to free cl.net supporters from maintenance of code hosting?
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote: Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure it's possible with gitlab pages. Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-... I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Ray
I agree with Vladimir,
I personally dislike github (although I use it) and had a very old SF account which I use sparingly. Alas, during the c-l.net “loss of usability” period, I moved two repositories to SF and I plan to move them to c-l.net as soon as I find some time to do it (it may be a long time, but that’s just me :) ).
Marco
On May 9, 2017, at 22:16 , Vladimir Sedach vsedach@oneofus.la wrote:
SourceForge is a very good example of why common-lisp.net should continue to provide repository hosting and you should host your projects' official repositories on c-l.net and encourage others to do the same.
In 2013 SourceForge was acquired by Dice Holdings, who proceeded to do things like infect downloadable binaries with spyware and adware. Fortunately for SourceForge users it was again sold to another company in 2016 who stopped the adware. For now.
I made the mistake of moving some of my projects' official repositories to github in 2012, and plan to move them back to c-l.net this year. You can always use github as another remote and get the benefits of their pull request interface.
In the long run having a non-profit entity like common-lisp.net provide Free Software hosting is a lot less work than dealing with "free" accounts from for-profit corporations that can modify or take away the service at any time (Google Code is a good example here).
Vladimir
Marco Antoniotti marcoxa@cs.nyu.edu writes:
I am not that happy about github (or sf.net or whatever).
I don’t like the github “one-size-fits-all” basic setup (sf.net is better in that respect).
My preference would be to keep c-l.net as is; however, I am not doing much work about it :)
Cheers — MA
On May 7, 2017, at 07:32 , Raymond Toy toy.raymond@gmail.com wrote:
If there's no code hosting, then what is the purpose of c-l.net? Without the repositories, that only leaves the mailing lists and a few other random things, I think.
I am grateful for everything that c-l.net provides. Otherwise, I'd have to host them myself or find some other means of hosting everything else except the repos (for which there are many alternatives).
On Sat, May 6, 2017 at 4:56 PM, Anton Vodonosov avodonosov@yandex.ru wrote: Several more words.
For many projects github pages might be enough. Also, code hosting can be done on github . Maybe we should encourage this to free cl.net supporters from maintenance of code hosting?
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote: Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure it's possible with gitlab pages. Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the option to log in on the host through ssh connections to manage their hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the majority of the repositories on the site - includes a hosting offer for static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-... I've not studied the functionality in depth, but I'm wondering: would the time have come to start moving the project pages into GitLab by using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Ray
-- Marco Antoniotti
Hi Anton,
On Sun, May 7, 2017 at 1:56 AM, Anton Vodonosov avodonosov@yandex.ru wrote:
Several more words.
For many projects github pages might be enough. Also, code hosting can be done on github . Maybe we should encourage this to free cl.net supporters from maintenance of code hosting?
I would like to point out that I was writing (not accidentally) Git*Lab* pages not Git*Hub* pages: GitLab has a functionality which looks remarkably similar to GitHub Pages and it's something that needs a bit of configuring to get working. After the GitLab Pages work on c-l.net, the users of that functionality no longer need SSH login accounts.
Just to clear up any potential for misunderstanding: I'm *not* proposing a move to GitHub for any kind of functionality. Code hosting will absolutely remain on c-l.net. Same for the mailing lists and list archives. However, we're trying to advance our services to be as easy to use as those offered by our "competitors", so, every now and then we need to evaluate our offering (both in terms of ease for users as well as for admins).
From other responses in this thread, I understand that there's still a need
for SSH access and "raw" hosting. We'll absolutely respect that.
One question does remain: would anybody be interested in having the "easy" route for deploying static website content through Git*Lab* pages? In other words, would there still be a benefit for us setting it up or is there no demand?
Regards,
Erik.
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure
it's possible with gitlab pages.
Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the
option to log in on the host through ssh connections to manage their
hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the
majority of the repositories on the site - includes a hosting offer for
static pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-
pages-to-community-edition/
I've not studied the functionality in depth, but I'm wondering: would
the time have come to start moving the project pages into GitLab by
using this offering and start moving away from having OS-based accounts? Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
On Wed, May 10, 2017 at 4:09 AM, Erik Huelsmann ehuels@gmail.com wrote:
One question does remain: would anybody be interested in having the "easy" route for deploying static website content through Git*Lab* pages? In other words, would there still be a benefit for us setting it up or is there no demand?
Is it a lot of work or on-going maintenance? Do the static pages also get a git repo so you can do revision control on them?
I'm considering moving the pages from www.cmucl.org to here (and having www.cmucl.org redirect). But we're also considering just moving all the pages there to the wiki, so we then wouldn't need static pages. There aren't a lot of pages and the pages are quite simple so the effort to move to the wiki isn't huge.
Regards,
Erik.
06.05.2017, 13:15, "Erik Huelsmann" ehuels@gmail.com:
Hi Daniel, Anton,
Thanks for your reactions. That's enough to decide not to change our ways.
Regards,
Erik.
On Sat, May 6, 2017 at 11:00 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Same goes for me, I host various static files on both ECL and McCLIM projects (documentation, papers, in case of ECL - releases).
Regards, Daniel
Anton Vodonosov writes:
In cl-test-grid I store reports as static files on cl.net. Not sure
it's possible with gitlab pages.
Best regards,
- Anton
06.05.2017, 01:30, "Erik Huelsmann" ehuels@gmail.com:
Hi all, Since the inception of Common-Lisp.net, we have offered projects the
option to log in on the host through ssh connections to manage their
hosted project pages (https://common-lisp.net/project/*). As off December 2016, GitLab - the software we use to provide the
majority of the repositories on the site - includes a hosting offer for
static pages: https://about.gitlab.com/2016/
12/24/were-bringing-gitlab-pages-to-community-edition/
I've not studied the functionality in depth, but I'm wondering: would
the time have come to start moving the project pages into GitLab by
using this offering and start moving away from having OS-based
accounts?
Would people mind or even like to move to this functionality? Regards,
-- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
On Fri, May 19, 2017 at 4:50 PM, Raymond Toy toy.raymond@gmail.com wrote:
On Wed, May 10, 2017 at 4:09 AM, Erik Huelsmann ehuels@gmail.com wrote:
One question does remain: would anybody be interested in having the "easy" route for deploying static website content through Git*Lab* pages? In other words, would there still be a benefit for us setting it up or is there no demand?
Is it a lot of work or on-going maintenance? Do the static pages also get a git repo so you can do revision control on them?
Yes: every project uses a git repository to develop its pages. you can push to your pages repo, the pages feature builds your static content and pushes it out to update the hosted site. I was studying the exact mechanics last night.
There is mostly the initial effort to get it set up. There doesn't seem to me more effort involved in maintaining this additional bit of GitLab than there already is with the rest of it.
I'm considering moving the pages from www.cmucl.org to here (and having www.cmucl.org redirect). But we're also considering just moving all the pages there to the wiki, so we then wouldn't need static pages. There aren't a lot of pages and the pages are quite simple so the effort to move to the wiki isn't huge.
Do you want to run an experiment with GitLab pages to see if it suits your needs?
-
Anton Vodonosov -
Daniel Kochmański -
Erik Huelsmann -
Marco Antoniotti -
Raymond Toy -
Vladimir Sedach