clo-devel

clo-devel@common-lisp.net

3 participants
610 discussions

[missing implementations]
by Daniel Kochmański 14 Oct '18

14 Oct '18

Hey, new website is great. There are though a few suprises: - clisp and lispworks are not listed in Resources -> Common Lisp Implementations - lispworks is not listed on getting started download page, but allegro is (since two free implementations are listed, it would be justified to mention two most popular commercial ones) Best regards, Daniel

8 16

GitLab now has 'reply by e-mail' enabled
by Erik Huelsmann 14 Oct '18

14 Oct '18

Hi, Today I found some time to enable GitLab's 'reply by e-mail' functionality. When you receive a notification e-mail from our GitLab instance, you can now send a reply to that notification. If the notification was from an issue being updated, then your reply will update the issue with a follow-up commont. Regards, Erik -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 2

Your opinion on my version of Common-Lisp.net website
by Mariano Montone 10 Oct '18

10 Oct '18

Hello everybody! I've been working on a new version of Common-Lisp.net website. Let me explain: I had an idea for a Common Lisp website. I was not happy with lisp-lang.org. So I started designing/developing. But then I came across Common-Lisp.net, and thought I could build on top of that instead. The result may be that my personal ideas and preferences may not be good for Common-Lisp.net mission in particular, or the maintainers taste. That's why I want your opinion on it. I'll be glad if some of it gets to replace some of the Common-Lisp.net site, but if not, I have not problem at all. My version of the site is hosted here: https://gitlab.common-lisp.net/mmontone/cl-site I started developing on top of this branch: https://gitlab.common-lisp.net/clo/cl-site/tree/more-scaffolding, that I found better than other branches. Can you guys try it and give me your opinion? To install: git clone https://gitlab.common-lisp.net/mmontone/cl-site make make serve This is what I've done: * Added Bootstrap themes from https://bootswatch.com/, which you can choose from (current one is Simplex) * Redesigned home page to include Planet Lisp and Reddit news in news sidebar. * Added Fontawesome icons * Redesigned Download, Community, and Documentation pages. * Added CL Implementations and Features pages. * Imported lisp libraries page from cl-awesome github project, and lisp-companies page from awesome-lisp-companies github project. Ok. Looking forward to hear your thoughts. Thanks! Mariano

3 5

Cleaning up common-lisp.net user database (not GitLab)?
by Erik Huelsmann 07 Oct '18

07 Oct '18

Hi all, common-lisp.net has 429 OS-level non-system users. Of these users, 347 didn't log in since 2013 (inception of the current instance). Just for the fun of it: cohorts since 2013: 1 2013 7 2014 18 2015 9 2016 10 2017 21 2018 Since these 347 users seem to get by without logging in (or have lost interest), I'm planning to remove these users and their home directories from the system as a system clean-up action. The GitLab accounts associated with these users won't be affected. Neither will project's public_html hosting associated with these users. Before removal of these accounts, all users will be notified through their @ common-lisp.net accounts which is expected to forward to a valid mail address. If a valid forward address isn't available, I'll be assuming we lost contact and there's no other option than to assume lost interest, followed by clean-up. This mail is both to notify as well as to solicit feedback. Any comments? Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

Moving project site deployment to GitLab CI (from upload through SSH)?
by Erik Huelsmann 06 Oct '18

06 Oct '18

Hi all, Today I've worked on figuring out how to (ab)use GitLab CI and GitLab Pages to set up the deployments for the content of https://common-lisp.net/project/* And I've found how to do that! Which means that we can start using GitLab and GitLab CI / GitLab Pages to allow people to deploy content to their hosting directories. As a site maintainer, I'd love to make this change. However, the site is here for its users. What do you think? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Cmucl trac down
by Raymond Toy 16 Sep '18

16 Sep '18

Someone pointed out to me that trac.common-lisp.net/cmucl is not working. That returns an internal error: TracError: IOError: [Errno 13] Permission denied: u'/srv/project/cmucl/trac/log/trac.log' I have no need for trac to be running, except for being able to see old tickets. No new tickets, updates to tickets, wiki changes or anything else is needed since everything has mostly been migrated to gitlab. Well except tickets. trac seems to be available for other projects. -- Ray

2 1

GitLab runner on c-l.net: who uses it?
by Erik Huelsmann 16 Aug '18

16 Aug '18

Hi, Apparently someone (I?) installed a gitlab runner on common-lisp.net. However, it doesn't seem to be registered with our GitLab installation. Who did we install it for? Regards, Erik. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 5

Using your Common Lisp website
by Mark Evenson 07 Jun '18

07 Jun '18

> On May 22, 2018, at 16:44, Mariano Montone <marianomontone(a)gmail.com> wrote: > > El 16/05/18 a las 04:12, Mark Evenson escribió: > >> I’ll try to get back to you in the next couple days about next intermediate steps. Please ping me next week if you haven’t heard from me. Mariano, Yesterday, I presented your work on redesigning the common-lisp.net to the Common Lisp Foundation board. As I expected, everyone was very enthusiatic about moving forward with deploying this work as the new basis for the site. We drafted the following plan: 1. Merge your work back to the clo/cl-site as the master branch 2. Set up a testing instance of our web site that watches a given branch in the clo/cl-site for changes, and then automatically publishes these changes as web pages 3. Spend a couple weeks iteratively working on that branch to edit content and fix the minor technical details 4. When we are satisfied with the results, we will then move the testing instance over to the main site. The question from our side: how involved would you like to be in this process? Even if you do nothing further, we will certainly publically credit you as the person who re-designed the common-lisp.net website. But we would love to have your continued input and help, as quite frankly, your HTML/CSS/JS skills are quite a bit better than anything we can muster! If you wish to help further, what I would suggest would be to just hang tight until we get the test site up (within the next week), and are able to publish automatically when one pushed to a designated branch within GitLab. At that point, I can assemble a list of outstanding issues that would need to be addressed before launch. Again, these “issues” are mostly changes the CLF wishes to make to the text describing common-lisp.net so we can handle most of this. Almost all of your contributions to listing cool Common Lisp resource, linking YouTube videos, linking IRC chat transcripts are all already light years ahead of what we currently have, so if you wanted to refine them, fine. But even as is, they are a fantastic improvement over what we currently have. One cross-cutting technical change that we may need involves our compliance with the EU GDPR. We don’t currently use cookies to track anything, nor do we intentionally analyze any logs, but I don’t know if we are required to state this. We certainly can’t do a popup, because we can’t track whether we have previously served a popup to a given user. So, I think that GDPR compilance can be satisfied by a statement somewhere that we don’t collect or use data, but again, I have to check the legal status. In any case, thank you very much for your excellent contribution to the common-lisp.net cause, and we would very much like to work with you in the future. Sincerely, Mark Evenson Secretary of the Common Lisp Foundation

1 0

/projects alias
by Stelian Ionescu 30 Apr '18

30 Apr '18

Hello, Can you add back to common-lisp.net, the namespace /projects as alias of /project ? That used to be the case previously and I think there might still be references around. Thank you. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

1 0

Re: 2018 Site Redesign Proposal
by Cheryl Yang 08 Apr '18

08 Apr '18

Hi Sammie, Current work on the CLnet site is taking place at this repository: https://gitlab.common-lisp.net/clo/cl-site The page on cl-foundation.org that you found is a very old draft that was left online for some reason. Our priority right now is to finish coding the static site generator in Lisp. Please see my WIP merge request for the status of this and to learn how you can help if you'd like :) Once the static site generator is completed in Lisp, we should be able to remove the Ruby dependency. The current CLnet is generated with Ruby. Hope this clears it up. - Cheryl ---- On Wed, 04 Apr 2018 02:35:21 -0400 Sammie Rawlison Jr <S.Rawlison.Jr(a)outlook.com> wrote ---- This may not be the way comments should be made, but I did not want cause any issues by doing stuff on the "https://mailman.common-lisp.net/listinfo/clo-devel " page that would cause me to be yanked from this thread in case I were an actual member. I tried to flow through the github to follow the messages thread-paths to see where things were going with regards to " https://common-lisp.net/ " and the email I received "Re: 2018 Site Redesign Proposal". I saw a site "http://www.cl-foundation.org/clnet/index.html " which had a look alike the email attachment. Common Lisp - The #1 Programmable Programming Language www.cl-foundation.org welcome Donate. Dear Fellow Lispers, We want to bring common-lisp.net back to its old (modest) glory. We will not stop there, though --- our aim is to work to make it a great set of resources and services for seasoned as well as "newbie" Common Lispers alike. Welcome to Common-Lisp.net! common-lisp.net Introduction. Welcome to the amazing world of Common Lisp, the programmable programming language. This site is one among many gateways to Common Lisp. clo-devel Info Page - Common Lisp mailman.common-lisp.net To see the collection of prior postings to the list, visit the clo-devel Archives.. Using clo-devel: To post a message to all the list members, send email to clo-devel(a)common-lisp.net. The comment of removing Ruby dependencies caught my attention, and also generating the site from Lisp was an eye opener. So Cheryl, when you move over the front-end, the maintainers will continue? Sammie From: clo-devel <clo-devel-bounces(a)common-lisp.net> on behalf of Cheryl Yang <lisp(a)cheryllium.com> Sent: Sunday, April 1, 2018 7:36 AM To: clo-devel Subject: Re: 2018 Site Redesign Proposal Yes, that's right, I recall it now. I'll move the front-end work over and pick up where we left off there. Sorry for my confusion. ---- On Sun, 01 Apr 2018 03:55:21 -0400 Erik Huelsmann <ehuels(a)gmail.com> wrote ---- Hi Cheryl, Mark, On Sun, Apr 1, 2018 at 9:38 AM, Mark Evenson <evenson(a)panix.com> wrote: Indeed for me it is a higher priority to remove the Ruby dependency and be able to generate the site from Lisp than it is to have a new site. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. > On Apr 1, 2018, at 01:08, Cheryl Yang <lisp(a)cheryllium.com> wrote: > > Hello everyone, long time no talk! > > I hope everyone has been well. I've had... a hectic time of it but I'm settling down finally. > > I should apologize for how MIA and hard-to-reach I have been. > Hopefully now that things are more stable in my personal life, I can give more time to CL and other projects. > > As a start, I've written a basic design update for Common-Lisp.net. You can view and comment on the code for it here: https://gitlab.common-lisp.net/clo/site/merge_requests/1 > > This features actual mobile responsiveness (yes, the last design had an embarrassing mistake, I know!) and removes the mtime dependency that was preventing us from upgrading Ruby on CLnet's servers. I think we're still on a very old Ruby version, hopefully this will allow us to upgrade it, or at least remove one more barrier. > > Please take your time to review it at your leisure; I know I'm sort of surprising everyone with this. > I've attached a few screenshots so you can see what it looks like at a glance. > > Thank you, > - C. Yang I thought the plan was to port the current site over to a non-Ruby version in https://gitlab.common-lisp.net/clo/cl-site and then change that one? It would be considerably easier for the operators to get rid of the Ruby dependency.

1 0

← Newer
1
...
12
13
14
15
16
17
18
...
61
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel