Differences

This shows you the differences between two versions of the page.

--- balug_todo_list [2007-10-15T11:33:34+0000] – miscellaneous updates michael_paoli
+++ balug:balug_todo_list [2010-02-25T07:25:37+0000] – robots.txt files have all been reviewed/updated michael_paoli
@@ Line 1: / Line 1: @@
 ====== BALUG todo list ======
+==== in approximate priority ranking - notes first ====
+  *Notes:
+    *This is not a complete/current list
+    *higher/highest priority towards the top
+    *lower priority items may proceed before higher items depending on resources and if not dependent upon higher priority items
+  *system(s):
+    *restore (most) all functionality BALUG had on the %%<=%%2009-11-11 VIP on shared tower box to the balug Xen domU, still to do:
+      *finish rounding out appropriate redirects (critical ones done, but many others remain to be done)
+      *disable temporary testing stuff(?) (e.g. /env)
+    *send out relevant communication(s) once the above is sufficiently complete (most notably need to update webmaster how-to stuff, as it's changed a fair bit).
+  *more wiki page updates:
+    *webmaster "how to" and such (work-in-progress)
+    *sysadmin "how to" and such (mostly pending)
+  *speakers/presentations
+    *line up more speakers/presentations
+    *get more volunteer(s) actively working on this
+----
+----
+===== Caution - much of the material on this page below this point is rather out-of-date =====
 ===== general todo =====
@@ Line 6: / Line 27: @@
   * sf-lug.com (hosts new.balug.com) transitioning to new hardware box!
     * remote management/setup: KVM over IP?  (Michael Paoli attempting to get resources for that; Cced Jim Stockford on communications).
+      * obtained one remote KVM device 2007-11-01, have another remote KVM devices pledged to us/SF-LUG - need 501%%(c)%%(3) EIN for the second of those donations
+        * 2007-10-28 - Michael Paoli e-mailed Andrew Fife regarding 501%%(c)%%(3) status (also checked earlier with Jim Stockford regarding possibly handling that via sfccp)
     * need to coordinate sf-lug.com./new.balug.org. hardware migration strategy (Michael Paoli, Jim Stockford, et. al.)
+      * most recent indications are build of new box will be started sometime on/after 2007-10-29
   * get more control into hands of webmaster(s), PHP assistant(s)/consultant(s)/fixer(s), etc., (Michael Paoli working to set these up) e.g.:
     * more automagic updates of [www.]balug.org. from www.new.balug.org.
-    * various staging/test/PHP areas
+    * various staging/test/PHP areas (mostly done weekend of 2007-11-03, there are now separate [[http://www.new.balug.org/|new]], [[http://www.beta.balug.org/|beta]], and [[http://www.test.balug.org/|test]] areas)
     * better ways for webmasters to control when updates occur and have more free reign with website (at least for testing purposes, anyway)
   * continue to tweak and improve our dining experience and coordination (cat herding and menu improvements, avoiding musical chair syndrome, etc.)
@@ Line 15: / Line 39: @@
   * continue to line up speaker(s)/presentation(s) more future meetings
   * In general, increasing moves to a more "production" infrastructure (reliable and redundant web, lists and e-mail) (probably don't need super-high availability, but being able to fail over or recover to alternate system in relatively quick order (minutes to hours, rather than days to weeks) would be a very good thing)
-    * untangle.com. to provide virtual host - that should cover us pretty well in that regard (Michael Paoli to follow up).
+    * untangle.com. to provide virtual host - that should cover us pretty well in regards to redundancy/failovver
+      * 2007-10-01 virtual host contact information passed along to Michael Paoli
+      * 2007-10-21 Michael Paoli followed up with contact on initial questions (e.g. setup, options, etc.) & again on 2007-11-06
+      * 2007-11-06 heard back from untangle.com contact
   * Migration off of DreamHost.com - including salvaging all that's feasible and of significant interest to BALUG, and smooth migration\\ (including:
     * control of and (eventual) migration of DNS (
       * Michael Paoli: e-mailed domain registrant on 2007-09-08 & 2007-09-30
       * Michael Paoli: left phone message(s) and e-mailed again on 2007-10-10
-      * Mae Ling Mak: e-mailed domain registrant 2007-10-14
+      * Mae Ling Mak may have e-mailed and/or called domain registrant 2007-10-14
-      * need to follow-up as necessary to gain control of registrant and DNS delegation information ... without being excessively pesky about it\\ )
+      * received an e-mail from domain registrant & replied on 2007-10-15
+      * Michael Paoli: e-mailed domain registrant again on 2007-11-06
+      * e-mail received 2007-11-06 from domain registrant
+      * Michael Paoli e-mailed domain registrant again on 2007-11-08 (with a bit of luck, we may have the registrant control stuff all wrapped up within about 5 to 10 days or so)
+      * need to follow-through as necessary to gain control of registrant and DNS delegation information ... without being excessively pesky about it\\ )
     * lists and list archives (including passwords, names, preferences, etc.)
     * lots of wiki pages that were functional there
@@ Line 46: / Line 77: @@
         * wiki - sf-lug.com. has a wiki configured for it (and BALUG is using some of that) ... but don't yet have such configured separately for BALUG (under it's own IP address and DNS names and such) - so, the BALUG stuff that's there so far may not be at all in it's "permanent" location.
     * DreamHost.com content extraction
-      * Any PHP and MySQL volunteers? (As of 2007-09-24 we've started to get at least some volunteer(s) to step forward on that.) BALUG could use assistance/consulting advice with PHP and MySQL; that could aid transition from the old DreamHost.com hosted site of www.balug.org. and lists.balug.org.  Maybe we can leverage some "talk" list(s) or similar resources for answer to specific questions?  Nothing all that major to do, but those aren't at least presently expert fields of the current BALUG sysadmins, and they'll likely  otherwise manage to muddle through them anyway.  Mostly just need to dump some MySQL data - and preferably in most useful/portable format(s) feasible - e.g. we may not be reloading that data into MySQL, but may want to process and pull out relevant bits via perl or other means ... though reloading into MySQL might also be a possibility.  There's also some (slightly) broken PHP stuff to fix (or diagnose and make a "fix" recommendation).  Presumably (my best guess) the PHP stuff was all working with the same, or a slightly older version of PHP, and changes in PHP version and/or some minor goofs in some PostNuke PHP web data have gotten the "old" stuff to the point where it's effectively quite non-functional ... but it's probably not all that horribly difficult to fix ... at least enough to usefully extract information - which is key objective.  Anyway, if some person(s) want to volunteer a bit of assistance/consulting on MySQL and/or PHP, that may be of significant benefit to BALUG.
+      * Any PHP and MySQL volunteers? (As of 2007-09-24 we've started to get at least some volunteer(s) to step forward on that.) BALUG could use assistance/consulting advice with PHP and MySQL; that could aid transition from the old DreamHost.com hosted site of www.balug.org. and lists.balug.org.  Maybe we can leverage some "talk" list(s) or similar resources for answer to specific questions?  Nothing all that major to do, but those aren't at least presently expert fields of the current BALUG sysadmins, and they'll likely  otherwise manage to muddle through them anyway.  Mostly just need to dump/migrate some MySQL data - and preferably in most useful/portable format(s) feasible - e.g. we may want to reload all the Mailman related data into a different MySQL database, but for some of the other data, we may want to process and pull out relevant bits via perl or other means.  There's also some (slightly) broken PHP stuff to fix (or diagnose and make a "fix" recommendation).  Presumably (my best guess) the PHP stuff was all working with the same, or a slightly older version of PHP, and changes in PHP version and/or some minor goofs in some PostNuke PHP web data have gotten the "old" stuff to the point where it's effectively quite non-functional ... but it's probably not all that horribly difficult to fix ... at least enough to usefully extract information - which is key objective.  Anyway, if some person(s) want to volunteer a bit of assistance/consulting on MySQL and/or PHP, that may be of significant benefit to BALUG.
       * List archives and subscribers, etc.
         * automate backups of this data, as complete as feasible
-          * it's presently being done approximately monthly manually (last done 2007-09-03); covers a rather imperfect and limited view of archives (munged @ --> " at " and most headers stripped, and no backup of any attachments), and list subscriber e-mail addresses (but not names, passwords, or preferences)
+          * it's presently being done approximately monthly manually (last done 2007-10-21); covers a rather imperfect and limited view of archives (munged @ --> " at " and most headers stripped, and no backup of any attachments), and list subscriber e-mail addresses (but not names, passwords, or preferences)
         * optimal extraction/migration may require fair bit of use of MySQL
       * Older web content (most notably many wiki pages)
@@ Line 118: / Line 149: @@
       -Social Networking: Facebook, MySpace, others?
   -__**Speaker Coordination**__
-    * What is our goal... driving meeting attendance or supporting local causes?
+    * What is our goal... driving meeting attendance or supporting local causes? (JS: entertain and/or enlighten members attending the meeting, not either driving meeting attendance, which should result from entertain/enlighten, nor support any particular cause other than general free and open source -ness.)
     * How to ensure that we don't double book speaking slots?
       * Update [[BALUG Speaker Coordination]] (note that that page may eventually move - but for the time being, that's where it is) - that's what it's there for.  If one doesn't put information there that a speaker is booked/confirmed (or even tentative) for a date, then folks will presume the date is open.  Folks aren't going to remember that e-mail from N days/weeks/months ago - especially if they weren't on <balug-speaker-coordinators@balug.org> at the time (and having a bunch 'o individuals trying independently to track the status would be rather redundant with what the wiki page is intended to do; also if folks separately maintain their own copies of such status, when they have conflicting information, how would one determine which information is correct? ... with the wiki page it's out there for all to see (and even the revision history of who made what changes and when)).