balug:balug_todo_list
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| balug:balug_todo_list [2010-02-25T07:25:37+0000] – robots.txt files have all been reviewed/updated michael_paoli | balug:balug_todo_list [2022-08-11T02:10:07+0000] (current) – format tweak michael_paoli | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | ==== in approximate priority ranking - notes first ==== | + | |
| - | *Notes: | + | |
| - | *This is not a complete/ | + | |
| - | *higher/ | + | |
| - | *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 %%< | + | |
| - | *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/ | + | |
| - | *line up more speakers/ | + | |
| - | *get more volunteer(s) actively working on this | + | |
| - | ---- | + | ^ [L]UGs/ |
| - | ---- | + | ^[[https:// |
| + | |d | ||
| + | |y | ||
| + | |? | ||
| + | |y | ||
| + | |d | ||
| + | |i | ||
| + | |y | ||
| + | |i | ||
| + | |? | ||
| + | |? | ||
| + | |p | ||
| + | |p | ||
| + | |p | ||
| + | |p | ||
| + | |p | ||
| + | |p | ||
| + | |p | ||
| + | | |p | ||
| + | | |h | ||
| + | | | | | ||
| + | | | | | ||
| + | | | | | ||
| + | | | | | ||
| - | ===== Caution - much of the material on this page below this point is rather out-of-date ===== | + | Note that this is intended to be not //just// for BALUG, but in addition to BALUG, ...\\ |
| + | [Linux] User Groups ([L]UG)s / Special Interest Group(s) (SIG)(s) etc. "to do" list | ||
| + | Notably covering in addition to BALUG, those also sharing or also using BALUG Virtual Machine (VM)\\ | ||
| + | and/or having other common/ | ||
| - | ===== general todo ===== | + | Priority ordering |
| - | * Get (more) detailed information (text blurbs, etc., both short and extended) for upcoming confirmed speaker engagements | + | * higher/highest priorities at/towards top, (possibly) |
| - | * update website with the above | + | * dependencies may be listed before that which depends upon them |
| - | * sf-lug.com (hosts new.balug.com) transitioning to new hardware box! | + | * available resources |
| - | * remote management/setup: KVM over IP? (Michael Paoli attempting to get resources for that; Cced Jim Stockford on communications). | + | * key (multiple may be used): |
| - | * 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 | + | * ~~SP~~ |
| - | * 2007-10-28 - Michael Paoli e-mailed Andrew Fife regarding 501%%(c)%%(3) status (also checked earlier with Jim Stockford regarding | + | * - no |
| - | * need to coordinate sf-lug.com./new.balug.org. hardware migration strategy (Michael Paoli, Jim Stockford, et. al.) | + | * ? maybe |
| - | * most recent indications are build of new box will be started sometime on/after 2007-10-29 | + | * d done |
| - | * get more control into hands of webmaster(s), | + | * f future(?) |
| - | * more automagic updates of [www.]balug.org. from www.new.balug.org. | + | * h hold (on hold ... for reason(s) or lack of resource(s)). |
| - | * various staging/ | + | * i in-progress |
| - | * better ways for webmasters to control when updates occur and have more free reign with website (at least for testing purposes, anyway) | + | * n no |
| - | * continue to tweak and improve our dining experience and coordination (cat herding and menu improvements, | + | * o overlap |
| - | * survey the membership / meeting attendees? | + | * p proposed |
| - | * continue to line up speaker(s)/ | + | * y yes |
| - | * In general, increasing moves to a more "production" | + | |
| - | * 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\\ | + | |
| - | * 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 may have e-mailed and/or called domain registrant 2007-10-14 | + | |
| - | * 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 | + | |
| - | * lots of wiki pages that were functional there | + | |
| - | * presenter information, | + | |
| - | * meeting writeups/ | + | |
| - | * past approximately 3 years of BALUG history | + | |
| - | * (most) all the HTML page stuff | + | |
| - | * information for speakers | + | |
| - | * speaker coordination resources | + | |
| - | * spiffier information on directions to the meeting location | + | |
| - | * other useful resources and pages of information | + | |
| - | * etc.\\ ) | + | |
| - | * get regular off-site automated backups in place (covering absolutely everything BALUG has hosted on DreamHost.com., | + | |
| - | * have some manual backups of some(/ | + | |
| - | * new landing places for stuff moved/ | + | |
| - | * beta.balug.org. - where should that be? | + | |
| - | * sf-lug.com. box (and the major migration/ | + | |
| - | * BALUG has an IP (208.96.15.254) | + | |
| - | * basic new web infrastructure exists http:// | + | |
| - | * As of 2007-09-01 some http:// | + | |
| - | * increase the automated http:// | + | |
| - | * Mailman (list software) is installed on sf-lug.com. box, but isn't configured yet | + | |
| - | * BALUG needs to create its own e-mail infrastructure off of 208.96.15.254 | + | |
| - | * 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 " | + | |
| - | * 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/ | + | |
| - | * List archives and subscribers, | + | |
| - | * automate backups of this data, as complete as feasible | + | |
| - | * it's presently being done approximately monthly manually (last done 2007-10-21); | + | |
| - | * optimal extraction/ | + | |
| - | * Older web content (most notably many wiki pages) | + | |
| - | * "just in case" backup of raw data - may have some(/ | + | |
| - | * optimal extraction/ | + | |
| - | * DNS phased migration off of DreamHost.com | + | |
| - | * have created new.balug.org. and beta.balug.org. (including slave(s)) | + | |
| - | * start phased change of balug.org. (get registrar control, add NS records for balug.org.) | + | |
| - | * add slaves for balug.org. (have queued up good volunteer slave resources once we can allow them to do zone transfers) | + | |
| - | * continue to maintain balug.org. zone in mode compatible with DreamHost.com until fully migrated off of DreamHost.com (work in progress - currently being done with (to be new) primary master on ns1.balug.org.) | + | |
| - | * e-mail (@balug.org, | + | |
| - | * The @balug.org e-mail addresses are mostly fairly managed at this point - have functional forwarding aliases in place, have the information on the expansion of the aliases also on the sf-lug.com. box. Main thing missing from @balug.org is reasonable spam filtering - DreamHost.com doesn' | + | |
| - | This list originally based upon some earlier partial lists / status reports, e.g.:\\ | + | There' |
| - | [[http:// | + | Nevertheless, older listing |
| - | [[http:// | + | or done when there' |
| - | + | So ... [[https://www.wiki.balug.org/wiki/doku.php?id=balug: | |
| - | ===== Steering Committee ===== | + | and of course |
| - | 2007-10-01T12: | + | |
| - | + | ||
| - | ==== Agenda ==== | + | |
| - | -__**The Big Plan**__ | + | |
| - | * BALUG in general | + | |
| - | * sponsorships/ | + | |
| - | * general direction, plans, and vision for BALUG? | + | |
| - | -**__BALUG Web & Email Issues__** | + | |
| - | * beta.balug.org - where, objectives, participants, | + | |
| - | * longer term Internet plans (redundancy, | + | |
| - | * Website | + | |
| - | -Do we have access/own all of the resources that we need? | + | |
| - | * not yet: | + | |
| - | * need to get full control of DNS (Michael Paoli/Mae Ling Mak following up on this) | + | |
| - | * redundancy/ | + | |
| - | *What are BALUG' | + | |
| - | -System & Storage? | + | |
| - | -Physical Access? | + | |
| - | -Bandwidth? | + | |
| - | -Can we move forward without the old broke mysql stuff? | + | |
| - | * yes and no: | + | |
| - | * yes - we've got beta.balug.org. - can put it anywhere we want and use it as long as we want | + | |
| - | * no: | + | |
| - | * unless we want a gaping hole in BALUG' | + | |
| - | * we can't smoothly transition the lists without doing some well timed and coordinated mysql extracts and loads. | + | |
| - | -Anyone opposed to a hosted wysiwyg solution like sitekreator.com? | + | |
| - | * yeah, I'm not keen on the idea: | + | |
| - | * Haven' | + | |
| - | * " | + | |
| - | * do we really want to be subject to terms that aren't under our control and can be changed at any time without notice, and be agreed to the terms in advance? | + | |
| - | * various folks might also object on various " | + | |
| - | -How can we implement an RSVP system for events? | + | |
| - | * for now: simple e-mail alias (That' | + | |
| - | * future: snazzier web form, with reminder option(s), etc. | + | |
| - | * Should reminders be optional? | + | |
| - | * we probably want to avoid some 3rd party system that folks may not particularly trust and/or that may have terms some or many may find objectionable (e.g. many folks don't want their e-mail addresses made available to yet another 3rd party site that may end up leading to spam or unwanted promotional e-mails, etc.) | + | |
| - | * we probably need to consistently " | + | |
| - | -__**[[Event Communications]]**__ | + | |
| - | * Which lists/locations? | + | |
| - | -Internal BALUG mailing lists | + | |
| - | -External UG mailing lists | + | |
| - | -RSS from the website? | + | |
| - | * feasibility & implementation timing? | + | |
| - | * perhaps in the future, but not yet | + | |
| - | -iCal and/or similar notification/ | + | |
| - | -Flyers | + | |
| - | -Member blogs | + | |
| - | -Speaker blogs | + | |
| - | -Event listing websites | + | |
| - | -Social Networking: Facebook, MySpace, others? | + | |
| - | -__**Speaker Coordination**__ | + | |
| - | * 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 | + | |
| - | * also use < | + | |
| - | * Best Practices Guide for Speakers | + | |
| - | * did a quite good page of that before; it's still to be extracted from the old BALUG wiki stuff (and no, I don't feel like writing up all that work again, but if someone else wants to, feel free; we can always reintegrate useful bits from the older materials into a newer writeup once we've retrieved the older materials) | + | |
| - | -__**Event Logistics**__ | + | |
| - | * Update from Mae Ling on the Four Seas | + | |
| - | -Menu Changes | + | |
| - | *Number of dishes won't change | + | |
| - | *Variety will change & rotate monthly between 4 entrees from the beef, pork, chicken & veggie menu items (yum!) | + | |
| - | *Menu will rotate monthly between noodles & rice, both of which will be veggie (yum!) | + | |
| - | -50+ people, we can eat upstairs (how to forecast this?) | + | |
| - | -No more Musical Chairs (yippie!) | + | |
| - | *Portions of food will be determined by the number of blue tickets instead of by number of people sitting at the table | + | |
| - | -Feb. 2008 - 2008-02-19 - any conflicts between date, venue, and Chinese New Year? No, we're all clear on that date (and in 2009). | + | |
| - | * Name tags? - probably, but need to be sure we do it in a time efficient manner (e.g. don't slow up dinner to do name tags!) | + | |
| - | * Address bottlenecks: | + | |
| - | -Sitting down for dinner promptly - at 7:00 P.M.! | + | |
| - | -Selling dinner tickets - in bar, upon arrival - or certainly before leaving bar area | + | |
| - | -Late comers | + | |
| - | -Musical Chairs | + | |
| - | -Dinner to speaker transition - works better if we dine upstairs; short of that, timely start on dinner helps a lot | + | |
| - | -Door Prizes - speed it up - draw at most for 3 items | + | |
| - | * How can we improve the AV equipment? | + | |
| - | -Portable Projector (Can borrow from Untangle, Speaker is bringing his own for October) | + | |
| - | -Portable Screen (About $300) (that might be okay for 25 folks, but when we have 50+ folks would a portable screen even help us at all?) | + | |
| - | * Time for community announcements, | + | |
| - | * Publicizing the next event: __**[[Event Communications]]**__ | + | |
| - | -__**Finances**__ | + | |
| - | * setting up a bank account | + | |
| - | * via USENIX/ | + | |
| - | * via ??? | + | |
| - | * via Jim Stockford? | + | |
| - | * budget | + | |
| - | -__**Mailing Lists**__ | + | |
| - | * Keeping Mailing Lists Useful | + | |
| - | *this has mostly been a non-issue so far: | + | |
| - | *the Mailman list software is pretty good at detecting and snagging spam | + | |
| - | *" | + | |
| - | *" | + | |
balug/balug_todo_list.1267082737.txt.bz2 · Last modified: 2010-02-25T07:25:37+0000 by michael_paoli