<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Common Lisp.net : Beta</title>
  <link href="http://beta.common-lisp.netindex.xml" rel="self" />
  <link href="http://beta.common-lisp.net"/>
  <updated>2013-02-02T02:02:02Z</updated>
  <id>http://beta.common-lisp.netindex.xml</id>
  <entry><title type="html">Projects site</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2013/04/22_projects-site.html"/><updated>2013-04-22T13:53:00Z</updated><published>2013-04-22T13:53:00Z</published><id>news/2013/04/22_projects-site.html</id><category scheme="/tags/shell-script.html" term="shell script" label="shell script"/><content type="html">&lt;p&gt;
It is a simple script, of course.
&lt;/p&gt;



&lt;pre class="src src-sh"&gt;&lt;span style="color: #cdcd00;"&gt;_DIR&lt;/span&gt;=&lt;span style="color: #00cd00;"&gt;"$( cd "$( dirname "$0" )" &amp;amp;&amp;amp; pwd )"&lt;/span&gt;
&lt;span style="color: #cdcd00;"&gt;_projects_file&lt;/span&gt;=${&lt;span style="color: #cdcd00;"&gt;_DIR&lt;/span&gt;}/../projects.org

&lt;span style="color: #0000ee; font-weight: bold;"&gt;echo&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;"* common-lisp.net projects"&lt;/span&gt; &amp;gt; $&lt;span style="color: #cdcd00;"&gt;_projects_file&lt;/span&gt;
&lt;span style="color: #0000ee; font-weight: bold;"&gt;echo&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;" Common-lisp.net is the home to many projects. Here is the links to the websites that they all have locally."&lt;/span&gt;  &amp;gt;&amp;gt; $&lt;span style="color: #cdcd00;"&gt;_projects_file&lt;/span&gt;
&lt;span style="color: #00cdcd; font-weight: bold;"&gt;for&lt;/span&gt; project&lt;span style="color: #00cdcd; font-weight: bold;"&gt; in&lt;/span&gt; &lt;span style="color: #cdcd00;"&gt;`ls -d /project/*`&lt;/span&gt;; 
&lt;span style="color: #00cdcd; font-weight: bold;"&gt;do&lt;/span&gt; &lt;span style="color: #cdcd00;"&gt;bn&lt;/span&gt;=&lt;span style="color: #cdcd00;"&gt;`basename $project`&lt;/span&gt; 
   &lt;span style="color: #0000ee; font-weight: bold;"&gt;echo&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;'- '&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;"[[http://common-lisp.net/project/$bn][$bn]]"&lt;/span&gt; &amp;gt;&amp;gt; $&lt;span style="color: #cdcd00;"&gt;_projects_file&lt;/span&gt;
&lt;span style="color: #00cdcd; font-weight: bold;"&gt;done&lt;/span&gt;

&lt;/pre&gt;

</content></entry><entry><title type="html">The email agent for Common Lisp.net</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2013/04/07_the-email-agent-for-common-lispnet.html"/><updated>2013-04-07T15:40:00Z</updated><published>2013-04-07T15:40:00Z</published><id>news/2013/04/07_the-email-agent-for-common-lispnet.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">&lt;p&gt;
In the past (just before now) &lt;code&gt;cl-net&lt;/code&gt; has run with exim4 and mailman,
as that is what was setup previously. I do not like them either, so
from this point on &lt;code&gt;cl-net&lt;/code&gt;'s email MX will be setup how I think it
should be.
&lt;/p&gt;
&lt;p&gt;
This will likely have some issues with the mailing lists themselves,
as mailman to &lt;a href="http://mlmmj.org/"&gt;mlmmj&lt;/a&gt; is likely not as easy as I hope it is. Regardless,
that is what I am doing.
&lt;/p&gt;
&lt;p&gt;
Currently the setup in progress can be seen here :
&lt;a href="http://alpha.common-lisp.net/email-details.html"&gt;http://alpha.common-lisp.net/email-details.html&lt;/a&gt;
&lt;/p&gt;



&lt;pre class="src src-text"&gt;13:39 &amp;lt;user&amp;gt; I looked at this page, and see description of
               postgresql setup and some tables
13:39 &amp;lt;user&amp;gt; how it is going to be used?
13:39 &amp;lt;drewc&amp;gt; I have used postgresql as the database behind email
              for like 15 years at this point :)
13:40 &amp;lt;drewc&amp;gt; So, basically, here is how it works :
13:41 &amp;lt;drewc&amp;gt; There are "virtual_user"s that are associated with
              POSIX users with a UID and GID.
13:42 &amp;lt;drewc&amp;gt; Each of the "virtual_user"s also has a
              /home/&amp;lt;username&amp;gt; directory, as they usually do
13:43 &amp;lt;drewc&amp;gt; now, for a lot of things including email, the users
              are associated with a domain, in this sense,
              "email_domain"
13:43 &amp;lt;drewc&amp;gt; it has  PRIMARY KEY (domain_name, username)  , so one
              domain per user as domain_name is UNIQUE
13:45 &amp;lt;drewc&amp;gt; Then there is "email_address", which really has
              nothing to do with the other two, it is just a place
              to store email addresses.
13:46 &amp;lt;user&amp;gt; as far as I understand, (domain_name, username) may
               have several such pairs for a single user, right?
13:46 &amp;lt;drewc&amp;gt; Finally, what is probably the most important and ties
              it all together is "VIEW maildir"
13:46 &amp;lt;drewc&amp;gt; yup, exactly
13:46 &amp;lt;user&amp;gt; what I asked actually, is what service will be build
               on top of it? mailing lists? or new email accounts
13:47 &amp;lt;drewc&amp;gt; both, it is postfix and dovecot ...  :)
13:47 &amp;lt;drewc&amp;gt; so, for mailing lists, it will be
              http://mlmmj.org/ related
13:48 &amp;lt;drewc&amp;gt; I do not like / have never used mailman, and besides,
              the entire exim4/mailman setup is not something I
              liked, as a part time unix admin.
&lt;/pre&gt;


</content></entry><entry><title type="html">beta.common-lisp.net is up</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/beta/2013/03/08_betacommon-lispnet-is-up.html"/><updated>2013-03-08T18:34:00Z</updated><published>2013-03-08T18:34:00Z</published><id>beta/2013/03/08_betacommon-lispnet-is-up.html</id><category scheme="/tags/betacommon-lispnet.html" term="beta.common-lisp.net" label="beta.common-lisp.net"/><content type="html">&lt;p&gt;
 Because &lt;a href="./news/2013/03/05_the-server-must-move.html"&gt;the server must move&lt;/a&gt;, well, the alpha site has been live for
 a while. I have finally produced a &lt;a href="http://beta.common-lisp.net/index.html"&gt;Beta Version.&lt;/a&gt; We did need to &lt;a href="http://alpha.common-lisp.net/beta/2013/03/08_o-blog-patch-for-how-to-use-tags.html"&gt;patch the o-blog&lt;/a&gt;. And because it is somewhat odd, or i do not know how to do it, &lt;a href="http://alpha.common-lisp.net/alpha/2013/03/08_o-blog-alpha-to-beta.html"&gt;we needed this&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Now, we took out the Alpha category, but left the Beta in. This is a
Beta after all. And moreso, This will now be a blog about the
development of the common-lisp.net related things as well.
&lt;/p&gt;
&lt;p&gt;
So, &lt;a href="http://alpha.common-lisp.net/index.html"&gt;Alpha&lt;/a&gt; is likely not predicable, can change, etc. &lt;a href="http://beta.common-lisp.net/index.html"&gt;Beta&lt;/a&gt;, on the
other hand, is supposed to be reliable, predicable, and very close to
Gamma (the live version), save for the Beta blog.
&lt;/p&gt;
&lt;p&gt;
Hopefully it all works out. Regardless, comments left here are a good
way to contact me if needed.
&lt;/p&gt;</content></entry><entry><title type="html">o-blog patch for How to use tags</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/beta/2013/03/08_o-blog-patch-for-how-to-use-tags.html"/><updated>2013-03-08T18:34:00Z</updated><published>2013-03-08T18:34:00Z</published><id>beta/2013/03/08_o-blog-patch-for-how-to-use-tags.html</id><category scheme="/tags/o-blog.html" term="o-blog" label="o-blog"/><content type="html">&lt;p&gt;
So, I wanted the tag to have dots (&lt;code&gt;.&lt;/code&gt;) in it, but it seems the &lt;a href="http://orgmode.org/manual/Tags.html"&gt;org mode tags&lt;/a&gt; do not support it.
&lt;/p&gt;
&lt;p&gt;
O-blog has &lt;a href="http://renard.github.com/o-blog/tips/2012/01/07_how-to-use-tags.html"&gt;How to use tags&lt;/a&gt;, and says:
&lt;/p&gt;
&lt;blockquote&gt;

&lt;p&gt;Special characters used in tags:
&lt;/p&gt;
&lt;p&gt;
At sign (@) is converted to a dash (-).
Underscore (_) is converted to a blank ( ).
&lt;/p&gt;
&lt;/blockquote&gt;


&lt;p&gt;
 &amp;hellip; and it seems that those are the only non letters/numbers
 available. However, in experimenting, it seems that the pound sign
 (&lt;code&gt;#&lt;/code&gt;) can be used, so we simply have to add the transformation for that.
&lt;/p&gt;



&lt;pre class="src src-emacs-lisp"&gt;(&lt;span style="color: #00cdcd; font-weight: bold;"&gt;defun&lt;/span&gt; &lt;span style="color: #0000ee; font-weight: bold;"&gt;ob-parse-entry&lt;/span&gt;()
  &lt;span style="color: #00cd00;"&gt;"Parse blog entry from current position"&lt;/span&gt;
  (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;when&lt;/span&gt; (search-forward-regexp org-complex-heading-regexp
                               (point-at-eol)
                               t)
    (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;let*&lt;/span&gt; ((title (match-string-no-properties 4))
           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;tags is a list of `&lt;/span&gt;&lt;span style="color: #cd00cd;"&gt;ob:tags&lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;'&lt;/span&gt;
           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;to be compliant with org tag syntax (no "-" org space)&lt;/span&gt;
           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;"_" would be replaced with " " and "@" by "-"&lt;/span&gt;
           (tags (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;loop&lt;/span&gt; for tn in (org-get-local-tags)
                       with td
                       do (setf td
                                (replace-regexp-in-string
                                 &lt;span style="color: #00cd00;"&gt;"_"&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;" "&lt;/span&gt;
                                 (replace-regexp-in-string 
                                  &lt;span style="color: #00cd00;"&gt;"@"&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;"-"&lt;/span&gt; 
                                  (replace-regexp-in-string 
                                   &lt;span style="color: #00cd00;"&gt;"#"&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;"."&lt;/span&gt; tn))))
                       and collect (make-ob:tags
                                    &lt;span style="color: #0000ee; font-weight: bold;"&gt;:name&lt;/span&gt; td
                                    &lt;span style="color: #0000ee; font-weight: bold;"&gt;:safe&lt;/span&gt; (ob:sanitize-string td))))

           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;Timestamp is taken from either the CLOSED property or the&lt;/span&gt;
           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;current timestamp.&lt;/span&gt;
           (timestamp (apply 'encode-time
                             (org-parse-time-string
                              (or (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"CLOSED"&lt;/span&gt;)
                      (time-stamp-string &lt;span style="color: #00cd00;"&gt;"%:y-%02m-%02d %02H:%02M:%02S %u"&lt;/span&gt;)))))
           &lt;span style="color: #cdcd00;"&gt;;; &lt;/span&gt;&lt;span style="color: #cdcd00;"&gt;Some other time variables&lt;/span&gt;
           (year (string-to-number (format-time-string &lt;span style="color: #00cd00;"&gt;"%Y"&lt;/span&gt; timestamp)))
           (month (string-to-number (format-time-string &lt;span style="color: #00cd00;"&gt;"%m"&lt;/span&gt; timestamp)))
           (day (string-to-number (format-time-string &lt;span style="color: #00cd00;"&gt;"%d"&lt;/span&gt; timestamp)))

           (category (or (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"category"&lt;/span&gt;)
                         (car (last (org-get-outline-path)))
                         (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"ARCHIVE_OLPATH"&lt;/span&gt;)
                         (ob:blog-default-category BLOG)))
           (category-safe (ob:sanitize-string category))
           (page (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"PAGE"&lt;/span&gt;))

           (filename (or (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"CUSTOM_ID"&lt;/span&gt;)
                         (ob:sanitize-string title)))
           (filepath (funcall (ob:blog-posts-filepath BLOG) category-safe year month))
           (htmlfile (funcall (ob:blog-posts-htmlfile BLOG) filepath day filename)))

      (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;when&lt;/span&gt; page
        (setq htmlfile page
              filename (file-name-sans-extension (file-name-nondirectory htmlfile))
              filepath (file-name-directory htmlfile)))

      (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;let&lt;/span&gt; ((content (ob-get-entry-text)))
        (make-ob:post &lt;span style="color: #0000ee; font-weight: bold;"&gt;:title&lt;/span&gt; title
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:tags&lt;/span&gt; tags
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:timestamp&lt;/span&gt; timestamp
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:year&lt;/span&gt; year
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:month&lt;/span&gt; month
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:day&lt;/span&gt; day
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:filename&lt;/span&gt; filename
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:filepath&lt;/span&gt; filepath
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:path-to-root&lt;/span&gt; (file-relative-name &lt;span style="color: #00cd00;"&gt;"."&lt;/span&gt; filepath)
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:htmlfile&lt;/span&gt; htmlfile
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:template&lt;/span&gt; (or (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"TEMPLATE"&lt;/span&gt;)
                                    (&lt;span style="color: #00cdcd; font-weight: bold;"&gt;if&lt;/span&gt; page &lt;span style="color: #00cd00;"&gt;"blog_static.html"&lt;/span&gt; &lt;span style="color: #00cd00;"&gt;"blog_post.html"&lt;/span&gt;))
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:content&lt;/span&gt; content
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:content-html&lt;/span&gt; (ob-export-string-to-html content)
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:category&lt;/span&gt; (make-ob:category
                                 &lt;span style="color: #0000ee; font-weight: bold;"&gt;:name&lt;/span&gt; category
                                 &lt;span style="color: #0000ee; font-weight: bold;"&gt;:safe&lt;/span&gt; category-safe)
                      &lt;span style="color: #0000ee; font-weight: bold;"&gt;:sitemap&lt;/span&gt; (or (org-entry-get (point) &lt;span style="color: #00cd00;"&gt;"SITEMAP"&lt;/span&gt;))
                      )))))
&lt;/pre&gt;




</content></entry><entry><title type="html">The Server must move</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2013/03/05_the-server-must-move.html"/><updated>2013-03-05T22:03:00Z</updated><published>2013-03-05T22:03:00Z</published><id>news/2013/03/05_the-server-must-move.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">&lt;p&gt;
 The company which hosts the dedicated server on which common-lisp.net
 is run is not offering such a service anymore, and the server itself
 is old and out of date. Because of this, we must migrate a lot to a
 new service.
&lt;/p&gt;
&lt;p&gt;
 This machine, &lt;a href="http://alpha.common-lisp.net/"&gt;http://alpha.common-lisp.net/&lt;/a&gt;, is running on the new
 server, so it is simply moving things over. Still, there is a lot, so
 &lt;code&gt;if you can help, please leave a comment below&lt;/code&gt; or &lt;a href="mailto:drewc@drewc.org"&gt;email me&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
 There is also the matter of the future itself, what we offer and what
 we can do to help the lisp community. I was planning on having a bit
 more thought on this matter before asking others, but since this has
 come up, I figure that now is a good time to ask for input as well.
&lt;/p&gt;
&lt;p&gt;
 If you happen to be able to &lt;a href="https://www.paypal.com/xclick/business=treasurer%40cl-foundation.org&amp;amp;currency_code=EUR&amp;amp;item_name=Donation%20common-lisp%2Enet&amp;amp;lc=GB"&gt;Donate&lt;/a&gt; some time, skills or funds, it
 would really help move things along. If you happen to
 IRC, #common-lisp.net on freenode is the place. Otherwise, comments
 and email will be read and dealt with promptly.
&lt;/p&gt;
</content></entry><entry><title type="html">Migration Finished</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2011/06/05_migration-finished.html"/><updated>2011-06-05T21:50:00Z</updated><published>2011-06-05T21:50:00Z</published><id>news/2011/06/05_migration-finished.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">      Migration has come to a close. Nearly all services are up and running
      again, with the exception of Arch and ArchZoom, for which support
      has been dropped. Here's a list of other changes:&lt;/p&gt;

      &lt;ul&gt;
      &lt;li&gt;WebSVN repository browsing has been replaced:
        Subversion repository browsing is now handled by ViewVC.
        &lt;li&gt;The mailing list web interface is now hosted
          on &lt;a href="http://lists.common-lisp.net/"&gt;lists.common-lisp.net&lt;/a&gt;
          &lt;li&gt;Subversion anonymous checkout is now also supported over HTTP
            through http://svn.common-lisp.net/&amp;lt;project&amp;gt;
            &lt;li&gt;Trac has been upgraded to 0.11.7
            &lt;li&gt;The standard Subversion post-commit hook integrates
              with Trac tickets, if a project also has Trac set up. To
                learn more about this integration, read
                  &lt;a href="http://trac.edgewall.org/browser/tags/trac-0.11.7/contrib/trac-post-commit-hook"
                       &gt;the within-script documentation from the Trac repository&lt;/a&gt;
                       &lt;/ul&gt;
</content></entry><entry><title type="html">A new server move</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2011/04/02_a-new-server-move.html"/><updated>2011-04-02T21:47:00Z</updated><published>2011-04-02T21:47:00Z</published><id>news/2011/04/02_a-new-server-move.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">      We're moving common-lisp.net to a new server.  In the process, all
      services will be completely reconfigured from scratch, with each service
      moving to its own subdomain.  This work is likely to cause service
      interruptions over the coming weeks.  If you want to offer a helping
      hand, please join &lt;b&gt;clo-devel at common-lisp.net&lt;/b&gt;, where the
      process is being discussed and coordinated.&lt;/p&gt;
</content></entry><entry><title type="html">Darcs Web</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2008/06/08_darcs-web.html"/><updated>2008-06-08T21:45:00Z</updated><published>2008-06-08T21:45:00Z</published><id>news/2008/06/08_darcs-web.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">      I've updated the scripts that generate the 
      &lt;a href="http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi" 
      title="Darcs Web"&gt;DarcsWeb&lt;/a&gt; repository listing. If something
      seems awry, please send me an &lt;a href="mailto:gwking@metabang.com"&gt;e-mail&lt;/a&gt;.

</content></entry><entry><title type="html">New Admins Found!</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2008/01/08_new-admins-found.html"/><updated>2008-01-08T21:40:00Z</updated><published>2008-01-08T21:40:00Z</published><id>news/2008/01/08_new-admins-found.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">      &lt;a href="mailto:drew.crampsie@gmail.com"&gt;Drew Crampsie&lt;/a&gt; and 
      &lt;a href="mailto:gwking@metabang.com"&gt;Gary King&lt;/a&gt;, both members of 
      the &lt;a href="http://tech.coop/index"&gt;Tech Co-op&lt;/a&gt;, have volunteered to take care of 
      the duties required to administer cl.net. We
      would both like to extend a hearty thanks to Erik Enge for all the
      hard work over the years.
</content></entry><entry><title type="html">New Administrator wanted</title><author><name>nil</name></author><link href="http://beta.common-lisp.net/news/2007/09/10_new-administrator-wanted.html"/><updated>2007-09-10T21:38:00Z</updated><published>2007-09-10T21:38:00Z</published><id>news/2007/09/10_new-administrator-wanted.html</id><category scheme="/tags/common-lispnet.html" term="common-lisp.net" label="common-lisp.net"/><content type="html">&lt;p&gt;
     Due to commitments at work I'm unable to provide adequate support
     to common-lisp.net.  The result of which is that there are several
     outstanding project applications (sorry guys, hope to get to them
     this week) and other misc tasks.  I'm looking for someone to take
     over the day-to-day administration of common-lisp.net - I'll be
     happy to keep paying for the site and manage the donations (though
     equally happy to give that up as well).  Email admin (at) common-lisp.net
     if you are interested.  The chores involves mostly a couple of shell
     scripts that take care of adding users and projects.
&lt;/p&gt;</content></entry>
</feed>
