I wish to resign from my activities as the main maintainer of the Common Lisp Document Repository (CDR - http://cdr.europlisp.org). Although Arthur Lemmens, Edi Weitz, and Marc Battyani have supported the effort throughout CDR's existence, for which I'm very grateful, the main work rested on my shoulders. CDR had some noticeable impact in the seven years of its existence, but it may benefit from some new ideas and a fresh perspective. Since Arthur, Edi, and/or Marc do not want to take over the day-to-day activities for maintaining CDR, this effectively means that we are looking for volunteers to take over its maintenance. I would like to ensure that CDR doesn't become unmaintained, so I will keep on running things for as long as necessary. Feel free to ask any questions, either publicly, or privately to me directly, or via editors@cdr.eurolisp.org. Thanks, Pascal -- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
Pascal, could you quickly describe: - What is typically involved doing this work? - How much time does it typically take? It might be helpful for people considering taking over from you to know how much work is involved. Thank you for all of your hard work doing this! --Scott On Mon, Nov 4, 2013 at 6:28 AM, Pascal Costanza <pc@p-cos.net> wrote:
I wish to resign from my activities as the main maintainer of the Common Lisp Document Repository (CDR - http://cdr.europlisp.org). Although Arthur Lemmens, Edi Weitz, and Marc Battyani have supported the effort throughout CDR's existence, for which I'm very grateful, the main work rested on my shoulders.
CDR had some noticeable impact in the seven years of its existence, but it may benefit from some new ideas and a fresh perspective. Since Arthur, Edi, and/or Marc do not want to take over the day-to-day activities for maintaining CDR, this effectively means that we are looking for volunteers to take over its maintenance.
I would like to ensure that CDR doesn't become unmaintained, so I will keep on running things for as long as necessary.
Feel free to ask any questions, either publicly, or privately to me directly, or via editors@cdr.eurolisp.org.
Thanks, Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
Scott, The minimum amount of work that needs to be done should be clear from the description of the CDR process that can be found at http://cdr.eurolisp.org/manual.html As a CDR maintainer, you have to be at the receiving end of that process. As you can see, it involves checking the submissions that you receive for the very basic requirements (widely used document format, proper publication rights). You then determine the initial period for the document (usually 6 weeks), publish the document in the repository as an initial document with a fresh CDR number, and inform the author, the announcement mailing list, and the CDR blog about the new document. Under normal circumstances, if all goes smooth, you then move the document to its final state after 6 weeks. This may be different if the author retracts the document, or resubmits changed versions. When a document is in its final stage, it cannot be changed anymore. None of these steps is particularly heavy-weight, and I don’t have any problems with continuing this job a little longer, if necessary. I currently maintain the CDR website manually, by editing HTML pages with emacs and pushing changes to the website through darcs. I typically spend at most an hour (typically less) in total per CDR on these jobs. CDR was designed to be light-weight in this respect. Of course, a new maintainer is free to choose his/her own preferred tools for any of these steps. There have recently been some discussions and suggestions for improving CDR, for example at this year’s ELS in Madrid. For example, it was suggested to better track which CL implementations implement which CDR; to try to define a way how to check *features* for the presence of specific CDRs; to try to promote the implementation of CDRs with both commercial and open-source CL ‘vendors’; and so on. There seems to be a feeling that the CDR idea needs some form of push to have a greater impact. This will require more work and effort on the side of a new maintainer, but it’s also up to him/her to be creative and come up with new ideas. This is exactly the part where I feel I cannot contribute a lot more, and where I think it’s better to make room for somebody else. Does this answer your question? Pascal On 4 Nov 2013, at 14:35, Scott McKay <swmckay@gmail.com> wrote:
Pascal, could you quickly describe: - What is typically involved doing this work? - How much time does it typically take?
It might be helpful for people considering taking over from you to know how much work is involved.
Thank you for all of your hard work doing this!
--Scott
On Mon, Nov 4, 2013 at 6:28 AM, Pascal Costanza <pc@p-cos.net> wrote: I wish to resign from my activities as the main maintainer of the Common Lisp Document Repository (CDR - http://cdr.europlisp.org). Although Arthur Lemmens, Edi Weitz, and Marc Battyani have supported the effort throughout CDR's existence, for which I'm very grateful, the main work rested on my shoulders.
CDR had some noticeable impact in the seven years of its existence, but it may benefit from some new ideas and a fresh perspective. Since Arthur, Edi, and/or Marc do not want to take over the day-to-day activities for maintaining CDR, this effectively means that we are looking for volunteers to take over its maintenance.
I would like to ensure that CDR doesn't become unmaintained, so I will keep on running things for as long as necessary.
Feel free to ask any questions, either publicly, or privately to me directly, or via editors@cdr.eurolisp.org.
Thanks, Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
-- Pascal Costanza
Hi I think I can volunteer for the job (alongside whomever else wants to pitch in). My only reservation is that in the past I have been involved with the CLURFI failure and I would like to be sure that there weren’t any bad feelings about that before taking up this task. Let me just say that all in all it was, in retrospect, a good experience with lot of things learnt in the process. Cheers — Marco On Nov 4, 2013, at 14:56 , Pascal Costanza <pc@p-cos.net> wrote:
Scott,
The minimum amount of work that needs to be done should be clear from the description of the CDR process that can be found at http://cdr.eurolisp.org/manual.html
As a CDR maintainer, you have to be at the receiving end of that process. As you can see, it involves checking the submissions that you receive for the very basic requirements (widely used document format, proper publication rights). You then determine the initial period for the document (usually 6 weeks), publish the document in the repository as an initial document with a fresh CDR number, and inform the author, the announcement mailing list, and the CDR blog about the new document. Under normal circumstances, if all goes smooth, you then move the document to its final state after 6 weeks. This may be different if the author retracts the document, or resubmits changed versions. When a document is in its final stage, it cannot be changed anymore.
None of these steps is particularly heavy-weight, and I don’t have any problems with continuing this job a little longer, if necessary. I currently maintain the CDR website manually, by editing HTML pages with emacs and pushing changes to the website through darcs. I typically spend at most an hour (typically less) in total per CDR on these jobs. CDR was designed to be light-weight in this respect. Of course, a new maintainer is free to choose his/her own preferred tools for any of these steps.
There have recently been some discussions and suggestions for improving CDR, for example at this year’s ELS in Madrid. For example, it was suggested to better track which CL implementations implement which CDR; to try to define a way how to check *features* for the presence of specific CDRs; to try to promote the implementation of CDRs with both commercial and open-source CL ‘vendors’; and so on. There seems to be a feeling that the CDR idea needs some form of push to have a greater impact. This will require more work and effort on the side of a new maintainer, but it’s also up to him/her to be creative and come up with new ideas. This is exactly the part where I feel I cannot contribute a lot more, and where I think it’s better to make room for somebody else.
Does this answer your question?
Pascal
On 4 Nov 2013, at 14:35, Scott McKay <swmckay@gmail.com> wrote:
Pascal, could you quickly describe: - What is typically involved doing this work? - How much time does it typically take?
It might be helpful for people considering taking over from you to know how much work is involved.
Thank you for all of your hard work doing this!
--Scott
On Mon, Nov 4, 2013 at 6:28 AM, Pascal Costanza <pc@p-cos.net> wrote: I wish to resign from my activities as the main maintainer of the Common Lisp Document Repository (CDR - http://cdr.europlisp.org). Although Arthur Lemmens, Edi Weitz, and Marc Battyani have supported the effort throughout CDR's existence, for which I'm very grateful, the main work rested on my shoulders.
CDR had some noticeable impact in the seven years of its existence, but it may benefit from some new ideas and a fresh perspective. Since Arthur, Edi, and/or Marc do not want to take over the day-to-day activities for maintaining CDR, this effectively means that we are looking for volunteers to take over its maintenance.
I would like to ensure that CDR doesn't become unmaintained, so I will keep on running things for as long as necessary.
Feel free to ask any questions, either publicly, or privately to me directly, or via editors@cdr.eurolisp.org.
Thanks, Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
-- Pascal Costanza
-- Marco Antoniotti, Associate Professor tel. +39 - 02 64 48 79 01 DISCo, Università Milano Bicocca U14 2043 http://bimib.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY Please note that I am not checking my Spam-box anymore. Please do not forward this email without asking me first.
From: Antoniotti Marco <antoniotti.marco@disco.unimib.it> Date: Wed, 6 Nov 2013 09:02:11 +0000
Hi
I think I can volunteer for the job (alongside whomever else wants to pitch in).
My only reservation is that in the past I have been involved with the CLURFI failure and I would like to be sure that there weren’t any bad feelings about that before taking up this task. Let me just say that all in all it was, in retrospect, a good experience with lot of things learnt in the process.
Looking back on it, CLRFI was much too heavy handed. CDR went the other way and has been very lightweight, which I think explains why it's been so much more successful. The important thing about mistakes is to learn from them, and I'm sure we did. Good luck with this! - nick
There was a typo in the URL. It’s actually this: http://cdr.eurolisp.org Pascal On 4 Nov 2013, at 12:28, Pascal Costanza <pc@p-cos.net> wrote:
I wish to resign from my activities as the main maintainer of the Common Lisp Document Repository (CDR - http://cdr.europlisp.org). Although Arthur Lemmens, Edi Weitz, and Marc Battyani have supported the effort throughout CDR's existence, for which I'm very grateful, the main work rested on my shoulders.
CDR had some noticeable impact in the seven years of its existence, but it may benefit from some new ideas and a fresh perspective. Since Arthur, Edi, and/or Marc do not want to take over the day-to-day activities for maintaining CDR, this effectively means that we are looking for volunteers to take over its maintenance.
I would like to ensure that CDR doesn't become unmaintained, so I will keep on running things for as long as necessary.
Feel free to ask any questions, either publicly, or privately to me directly, or via editors@cdr.eurolisp.org.
Thanks, Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
-- Pascal Costanza
participants (4)
-
Antoniotti Marco -
Nick Levine -
Pascal Costanza -
Scott McKay