[balug-admin] Fwd: Re: BALUG website [BALUG stuff to do (site, etc.)]

Michael Paoli Michael.Paoli@cal.berkeley.edu
Mon Jul 17 22:47:05 PDT 2006

... and propogate that error by copying it with the error a second time ...

----- Forwarded message from Michael Paoli <Michael.Paoli@cal.berkeley.edu> -----
    Date: Mon, 17 Jul 2006 22:41:13 -0700
    From: Michael Paoli <Michael.Paoli@cal.berkeley.edu>
Reply-To: Michael Paoli <Michael.Paoli@cal.berkeley.edu>
 Subject: Re: BALUG website [BALUG stuff to do (site, etc.)]
      To: mikron <mikron1234@gmail.com>

FYI, I ran checkbot against http://www.balug.org/ (excluding

Most of the stuff isn't too exciting (e.g. minor corrections should
be made, such as:
http://linuxmafia.com/cabal/installfest -->
http://www.linuxmafia.com/cabal/ -->

Some of the stuff, I'm not exactly where checkbot dug it up (it probably
included searching areas that needn't have been searched - at least some
of the URLs and such that checkbot found, I couldn't find on the
http://www.balug.org/ site - at least with some simple quick Google

Anyway, may want to review it and tweak those things that actually ought
to be tweaked (and ignore the what's "noise" and essentially false

                             Checkbot: main report

   Status: Done.

Report summary

    Links checked  59209
   Problems so far 82130
     Links to do   0

Overview per server

   Server Server
   Type Unique
   links Problem
   links Ratio
   [1]www.balug.org Apache/1.3.31 (Unix) DAV/1.0.3 mod_fastcgi/2.4.2
   mod_gzip/ PHP/4.3.10 mod_ssl/2.8.19 OpenSSL/0.9.6c 82871
   82130 99%

Checkbot session parameters

   --url     Start URL(s)               http://www.balug.org/
   --match   Match regular expression   ^(http\:\/\/www\.balug\.org\/)
   --exclude Exclude regular expression http://lists.balug.org/pipermail/

   Page created by [2]Checkbot 1.75 on Sat Jul 15 13:04:57 2006.

   [3]Valid XHTML 1.1!


Checkbot: report for server www.balug.org

   Go To: [1]Main report page, [2]301 Moved Permanently, [3]302 Found,
   [4]404 Not Found, [5]500 Internal Server Error, [6]903 URL contains
   double slash in URL.

    301 Moved Permanently


          + [8]http://linuxmafia.com/cabal/installfest
          + [9]http://mods.postnuke.com/
          + [10]http://www.bxxp.org/bxxp
          + [11]http://www.c2net.com/
          + [12]http://www.gnu-designs.com/palm+linux/
          + [13]http://www.imap-partners.net/
          + [14]http://www.linuxgazette.com/
          + [15]http://www.linuxmafia.com/cabal/
          + [16]http://www.suse.com/
          + [17]http://www.wholewheatradio.org/

    302 Found


          + [19]http://www.objfocus.com/
            Moved Temporarily
          + [20]http://www.qlitech.net/products/laptops/index.html
          + [21]http://www.secondlife.com/
          + [22]http://www.sw-soft.com/
          + [23]http://www.thematrix.com/
            Moved Temporarily
          + [24]http://www.valinux.com/
          + [25]http://www.vonage.com/

    404 Not Found


          + [27]http://balug.org/ml/balug-talk/msg00357.html
          + [28]http://phpwiki.sourceforge.net/phpwiki-wiki(1.3)/images/p
          + [29]http://www.art.unt.edu/ntieva/artcurr/japan/wabisabi.htm
          + [30]http://www.balug.org/index.php?module=Legal%20Documents
          + [31]http://www.balug.org/index.php?module=Legal%20Documents&f
          + [32]http://www.balug.org/meetings/kidslinux.pdf
          + [33]http://www.balug.org/meetings/kidslinux.sxi
          + [34]http://www.balug.org/meetings/mar1998/index.html
          + [35]http://www.balug.org/meetings/mar1998/speak32598.html
          + [36]http://www.balug.org/meetings/may1998/index.html
          + [37]http://www.balug.org/meetings/sep1998/speaker998.html
          + [38]http://www.balug.org/meetings/ssh1.zip
          + [39]http://www.balug.org/scripts/cookie_auth.gz
          + [40]http://www.balug.org/scripts/kernelnew1.sh
          + [41]http://www.balug.org/scripts/kernelnew2.sh
          + [42]http://www.balug.org/scripts/ppp1.gz
          + [43]http://www.balug.org/themes/Tekkno/images/favicon.ico
          + [44]http://www.balug.org/themes/Tekkno/images/icon.png
          + [45]http://www.google.com/company.html

    500 Internal Server Error


          + [47]http://tcl.apache.org'/
            Can't connect to tcl.apache.org':80 (Bad hostname
          + [48]http://www.cdrom.com/
            Server closed connection without sending any data back
          + [49]http://www.linuxcare.com/
            Can't connect to www.linuxcare.com:80 (Bad hostname
          + [50]http://www.usemod.com/cgi-bin/mb.pl?LikePages
          + [51]http://www.yggdrasil.com/
            Can't connect to www.yggdrasil.com:80 (connect: Connection
          + [52]http://www.yourhost.yourdomain/images/picture.png
            Can't connect to www.yourhost.yourdomain:80 (Bad hostname
          + [53]http://www2.parasoft.com/jsp/home.jsp
            Can't connect to www2.parasoft.com:80 (connect: timeout)

    903 URL contains double slash in URL


          + [55]http://www.balug.org//modules/phpWiki/images/rss.png
          + [56]http://www.balug.org//modules/phpWiki/images/wikibase.png
          + [57]http://www.balug.org/themes/Tekkno/images//mn_0.gif
          + [58]http://www.balug.org/themes/Tekkno/images//mn_1.gif
          + [59]http://www.balug.org/themes/Tekkno/images//mn_2.gif
          + [60]http://www.balug.org/themes/Tekkno/images//mn_3.gif
          + [61]http://www.balug.org/themes/Tekkno/images//mn_4.gif
          + [62]http://www.balug.org/themes/Tekkno/images//mn_5.gif
          + [63]http://www.balug.org/themes/Tekkno/images//mn_6.gif
          + [64]http://www.balug.org/themes/Tekkno/images//sidebox_0.gif
          + [65]http://www.balug.org/themes/Tekkno/images//sidebox_1.gif
          + [66]http://www.balug.org/themes/Tekkno/images//sidebox_10.gif
          + [67]http://www.balug.org/themes/Tekkno/images//sidebox_11.gif
          + [68]http://www.balug.org/themes/Tekkno/images//sidebox_12.gif
          + [69]http://www.balug.org/themes/Tekkno/images//sidebox_13.gif
          + [70]http://www.balug.org/themes/Tekkno/images//sidebox_14.gif
          + [71]http://www.balug.org/themes/Tekkno/images//sidebox_2.gif
          + [72]http://www.balug.org/themes/Tekkno/images//sidebox_3.gif
          + [73]http://www.balug.org/themes/Tekkno/images//sidebox_4.gif
          + [74]http://www.balug.org/themes/Tekkno/images//sidebox_5.gif
          + [75]http://www.balug.org/themes/Tekkno/images//sidebox_6.gif
          + [76]http://www.balug.org/themes/Tekkno/images//sidebox_7.gif
          + [77]http://www.balug.org/themes/Tekkno/images//sidebox_8.gif
          + [78]http://www.balug.org/themes/Tekkno/images//sidebox_9.gif
          + [79]http://www.balug.org/themes/Tekkno/images//top_0.gif
          + [80]http://www.balug.org/themes/Tekkno/images//top_1.gif
          + [81]http://www.balug.org/themes/Tekkno/images//top_2.gif
          + [82]http://www.balug.org/themes/Tekkno/images//top_3.gif
          + [83]http://www.balug.org/themes/Tekkno/images//top_4.gif

   Page created by [84]Checkbot 1.75 on Sat Jul 15 13:04:57 2006.

   [85]Valid XHTML 1.1!

Quoting Michael Paoli <Michael.Paoli@cal.berkeley.edu>:

> Thanks for volunteering.
> I'm not aware of much/anything in the way of database stuff to do
> presently, but regarding the site in general, you might start with some
> of these items.
> Get yourself subscribed to the "admin" list <balug-admin@list.balug.org>
> http://lists.balug.org/listinfo.cgi/balug-admin-balug.org
> It's probably a fairly good idea to read/skim a moderate bit of past
> archives (e.g. about the last 1 to 3 years).
> You can also grab those from the archives:
> http://lists.balug.org/pipermail/balug-admin-balug.org/
> if you grab the gzipped stuff, and gunzip those, they're in mbox format,
> so those could be browsed/skimmed with most mail client software, if
> desired ... can probably also just concatenate them all into one long
> mbox format file (something like that may be more convenient than trying
> to browse lots of them via the web interface).
> Anyway, reviewing a fair bit of the "admin" archives will give you a
> fairish overview of various issues which have been discussed and such.
> Probably good to also likewise at least skim the Subject: lines for the
> last year or so of of the "announce" and "talk" lists.
> On the website itself, you probably want to look it over and get
> familiar with the various portions of it.  Some are probably in the dead
> to semi-dead range - e.g. haven't changed in a very very long time, and
> may not have been actively used for similarly long time.  Opinions might
> differ on this, but perhaps some of those could be turned into static
> archives, rather than exist as "dynamic" stuff that nobody updates or
> actively uses (other than looking at older/historic stuff).
> It's probably a *good* idea to preserve backwards compatibility, in
> terms of content.  E.g. folks do find, reference, search out, link to,
> etc., various stuff on our web pages, so, preserving most of that
> functionality - at least in terms of preserving references, can be quite
> useful.  Unfortunately some older stuff has been lost and/or
> significantly munged (e.g. I've been active with BALUG since sometime in
> 2003, and since then the mailing lists have gone through 3 very
> different configurations, and in at least some cases access to the older
> archived stuff has been effectively lost (I think the data still exists,
> but not in a format we've been able to make use of)).
> The most active areas (at least in my opinion and as far as I can tell)
> are the lists, and a few relatively "high level" web pages on the site.
> Most notably (interpreting / tersely paraphrasing) there are the lists:
> "announce" - low volume, moderated, "highly" important/relevant stuff to
>   BALUG (e.g. information about upcoming meetings/speakers, etc.)
> "talk" - open unmoderated (must be subscribed to it) discussion (should
>   be reasonably topical to BALUG, but we haven't carved out a highly
>   specific policy for that list.)  Traffic volume varies from quite
>   quiet, to very active.
> "admin" - administrivia - basically for discussing (it's publicly
>   archived) BALUG administrivia stuff (the "business" of running
>   BALUG).  Stuff that shouldn't be publicly accessible should go in
>   private e-mails (e.g. often communications to/from prospective
>   speakers arranging speaking engagements, passwords (unless very
>   strongly encrypted), etc.)
> I think we've got a fairly reasonable handle on the lists and their
> management presently, so that's probably mostly okay.  What could
> probably use more attention is the website itself.
> It's hosted by Dreamhost, so, as long as that's the case, and the
> interfaces are as they are, we can't go in a freely muck about with and
> change things in any and/or all ways we might want to.  Unfortunately, I
> don't think we have, or know that we have a way to set up a "beta" or
> "test" site, such that it would effectively be a copy, yet would have
> the same interfaces when it comes to changing stuff - so that we could
> safely test out changes without mucking up the main site.  Unfortunately
> some of the interfaces definitely leave things to be desired - not only
> do we not have the lower level control of the site, but it is possible
> (e.g. via a HTML error) to introduce error(s) into the site that cannot
> be corrected via the same interfaces that introduced the error(s) (at
> least from what I've been told and seen thus far anyway).  So, ... one
> does need to be rather to quite careful with at least some types of
> changes on the web pages - at least given our current interfaces to
> manage them.
> If you poke around some of the Dreamhost support and related web pages,
> that'll also give you a rough idea of what we can and can't do, and how,
> and also the types of problems/issues others have run into under our
> present hosting arrangement.
> e.g.: http://www.dreamhost.com/support.html and related pages.
> There's been occasional talk of switching to a rather/quite different
> hosting arrangement.  For that to be feasible, however, various
> conditions would need to be met, e.g.:
> o it would need to be quite affordable
> o it would need to be rather/quite reliable (e.g. probably in a colo)
> o it would need to be "sufficiently easy" to maintain - a web hosting
>   situation (such as dreamhost) may not give us the flexibility and direct
>   access we might like, but it saves someone from having to also do all
>   the OS and hardware maintenance, etc.  Covering the OS and hardware
>   isn't particularly trivial ... unless that's just someone's N+1th
>   similar system (real or virtual) in an existing large managed set of N
>   systems - otherwise it's a fair bit of time and work for some person(s)
>   to cover, and do so reliably and regularly.
> Yes, ... Post Nuke, ... get yourself set up with a login on the web site
> using the New User? Sign Up! link on the main page, continue to get
> yourself familiar with the site, and one of us with admin access to
> the site can then grant that access to you presuming we're then settled
> upon that.
> Again, thanks for your interest in volunteering to assist with this.
> Quoting mikron <mikron1234@gmail.com>:
> > Hi Michael,
> > 
> > It was interesting to hear about the state of the BALUG website last
> Tues,
> > and I look forward to  contributing to a fix up.
> > 
> > I took a quick peak at the site, and discovered what content management
> > system it runs on.  It uses Post Nuke, and I discovered that by looking
> at
> > the HTML source meta tags.  The post nuke site is here: 
> > http://postnuke.com,
> > and a demo site is accessible here:
> >
> http://www.opensourcecms.com/index.php?option=content&task=view&id=130&Itemid=159
> > 
> > Presumably, someone has an admin login so we can manipulate our content.
> > 
> > Not sure what the next step is, but at least we know what we are dealing
> > with.
> > 
> > Mike

----- End forwarded message -----

More information about the BALUG-Admin mailing list