> 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
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.
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.
Hi,
On request of the mailing list owner, the following lists (but not their
archives) have been removed:
cl-interpol-devel
rdnzl-announce
rdnzl-devel
regex-coach
fm-lisp
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
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
Hi,
Sorry, yes, wrong list!
Thanks for the pointers! Ik use them while mailing the right list.
Regards,
Erik
On Mar 5, 2018 22:22, "Daniel Herring" <dherring(a)tentpost.com> wrote:
Hi Erik,
Did this get sent to the wrong list?
Anyway, I would recommend mimicking Qt's approach to translation. If
possible, re-use their file formats. Then you can use their toolchain for
maintaining translations.
http://doc.qt.io/qt-5/linguist-overview.html
- Daniel
On Mon, 5 Mar 2018, Erik Huelsmann wrote:
Hi,
>
> In our translation catelog, we have the word "To". There are multiple uses
> for this word, which is marked for translation for all uses.
>
> One use is the case of a date range ("From ... To ...."). Another use is
> the case of an address ("To: <address on the next line(s)>".
>
> When translating these to Dutch, these use cases have very different
> translations (Date range: "Tot"; address: "Aan").
>
> It seems we need some context specific translations. However, our
> translation library (which isn't gettext), doesn't cater for them.
>
> Any ideas as to how to approach this problem?
>
> How will we know which domains we need to distinguish?
>
>
>
> --
> Bye,
> Erik.
>
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
>
>
Hi,
In our translation catelog, we have the word "To". There are multiple uses
for this word, which is marked for translation for all uses.
One use is the case of a date range ("From ... To ...."). Another use is
the case of an address ("To: <address on the next line(s)>".
When translating these to Dutch, these use cases have very different
translations (Date range: "Tot"; address: "Aan").
It seems we need some context specific translations. However, our
translation library (which isn't gettext), doesn't cater for them.
Any ideas as to how to approach this problem?
How will we know which domains we need to distinguish?
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Hi,
There are 107 darcs repositories remaining on common-lisp.net which have
not been converted to Git yet.
I'm looking at what to do with those. These 107 seem to fall into the
following categories:
1. darcs-managed web pages (i.e.: /srv/project/*/public_html/_darcs)
2. project-published repositories (i.e.:
/srv/project/*/public_html/<repository-name>/_darcs) which were not
registered with darcsweb.
The first category I'm thinking of converting to Git, importing in Gitlab
as a 'public_html' project in the associated project group. Then, convert
the project's public_html folder from Darcs repository to Git repository by
replacing the _darcs directory with a .git directory.
The second category I'm thinking of converting to git using the same
procedure as the ones that just moved to GitLab (the published Darcsweb
list).
Comments?
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Hi,
As announced before, the darcs repositories listed at
https://common-lisp.net/cgi-bin/darcsweb.cgi will be migrated to
Git+GitLab. At the same time, darcs "support" will be deprecated on
Common-Lisp.net and the darcsweb URL above will be replaced by a rewrite
rule redirecting to GitLab.
Preparations have progressed well enough to be able to announce migration
to take place coming Saturday (Feb 17). common-lisp.net operations will be
available during migration.
Kind regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
