BALUG-Admin

balug-admin@lists.balug.org

2 participants
548 discussions

BALUG announcment is out (John D. Mitchell), etc.
by Michael Paoli 08 Sep '07

08 Sep '07

The announcment is out: http://lists.balug.org/pipermail/balug-announce-balug.org/2007-September/00… I Bcced: John D. Mitchell when I sent it. I also forwarded a short note to 4 additional UGs - and have thus far seen it show up on 3 of those 4 UG lists (haven't seen it show up on Oakland perl Mongers - at least yet, anyway: http://mail.pm.org/pipermail/oakland/2007-September/date.html ): ----- Forwarded message from Michael Paoli ----- Date: Fri, 7 Sep 2007 23:30:44 -0700 From: Michael Paoli Subject: BALUG 2007-09-18: John D. Mitchell, Krugle Chief Architect - Find and reuse code; etc. To: Bay Area Debian <bad(a)bad.debian.net>, Berkeley Unix User Group <buug(a)weak.org>, SF-LUG <sf-lug(a)linuxmafia.com>, Oakland Perl Mongers <oakland(a)pm.org> Bay Area Linux Users Group (BALUG) BALUG 2007-09-18: John D. Mitchell, Krugle Chief Architect - Find and reuse code; etc. BALUG 2007-10-16: Paddy Sreenivasan of Zmanda The announcement (that and other details): http://lists.balug.org/pipermail/balug-announce-balug.org/2007-September/00… For the latest information, check the BALUG site: http://www.balug.org/ ----- End forwarded message -----

1 0

Fwd: beta.balug.org. (?) and other useful ideas?
by Michael Paoli 05 Sep '07

05 Sep '07

Originally sent to the BALUG contact, webmaster, and sysadmins aliases, presented here slightly redacted: ----- Forwarded message from Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> ----- Date: Fri, 31 Aug 2007 20:10:35 -0700 From: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Reply-To: balug-sysadmins(a)balug.org Subject: beta.balug.org. (?) and other useful ideas? To: balug-contact(a)balug.org, balug-sysadmins(a)balug.org Cc: balug-webmaster(a)balug.org Anyway, a couple of (random?) thoughts/ideas that may be rather to quite useful - or perhaps at least so in part. A) beta.balug.org.? One of the issues that's been going on for a while is the "tension" between: Preserve/restore all the useful old stuff as much as feasible (and move it to new appropriate manageable home) - even if it means lots of newer/spiffier stuff is deferred for quite a while and: The heck with that, let's run from that old unmanageable mess as fast as possible even if we have to give up trying to save any of the old stuff, just start fresh, and kiss the old stuff bye-bye. One possible approach (there may be other approaches that would do similarly) on that that may rather substantially well cover *both* of the "competing"/"/conflicting" objectives might be roughly as follows: a) create beta.balug.org. We can mention/promote it on www.balug.org. (e.g. link to cool stuff on beta.balug.org. that isn't available/feasible to do (yet anyway) on www.balug.org.) - but continue to present core useful information on www.balug.org. (and presumably likewise include that or quite similar content on beta.balug.org.) We can create a separate beta.balug.org (highly analogous to how we've created new.balug.org ... doesn't even have to be on the same system ... could be anywhere). We could go *relatively* hog wild on beta.balug.org., but we'd want to observe a few "restrictions" ... just enough that would 1) allow us to later smoothly integrate www.balug.org. and beta.balug.org into a smooth homogeneous unified www.balug.org. and 2) provide *reasonably* consistent information between www.balug.org. and beta.balug.org. (e.g. we don't want them providing conflicting information) 1) would mostly involve some relatively simple rules on URL construction, such that in the future we could redirect http[s]://beta.balug.org/<whatever> to http[s]://www.balug.org/<whatever> and users(/bookmarks/search engines) would find essentially that same content they were looking for at the beta URL that would be then getting (301 "permanent") redirected (at some future post-unification date and time). Using this type of a beta.balug.org. approach could help us well cover both of the "competing" (save, preserve, and move, vs. drop and run) approaches on dealing with the "old" (DreamHost.com hosted) stuff. The name(s) used needn't be specifically and precisely beta.balug.org., but we would want to pick exactly what name(s) we'd be using quite carefully and with due technical and other considerations. Our DNS limitations with DreamHost.com impose some slight restrictions (we can't pick completely arbitrary names), but as long as we avoid name conflict with DreamHost.com DNS names (that are more-or-less effectively "mandatory" with a domain hosted there), we're relatively free to pick a name, and can delegate it via DNS - quite like the case is presently with new.balug.org. B) Additional colo box(es)? <redacted> may have a bit more to say on this. There was some talk(/offer?) of providing a (possibly virtual) new/additional host for BALUG (presumably in a colo, or other reliably hosted infrastructure/location). While at first reaction I may have stated/thought "Naw, we really don't need that, have the old stuff we're moving off of, and have stuff we can share and do on the SF-LUG.com box", since then my thinking and opinion has shifted, mainly because a) once we're finally and completely moved off of all DreamHost.com hosted, that would leave us with exactly one system ... though we may have backups of stuff elsewhere, it doesn't give us a highly reliable infrastructure (one significant booboo <redacted> or a significant hardware problem, or long maintenance outage, etc.), and that box could be effectively blown out of the water for days or more - and it could be quite a while before BALUG on-line infrastructure was operational again (approximately up to days or more). b) It would be quite nice to have BALUG have a much more robust infrastructure set-up. E.g. two independent systems (either or both of which could be virtual, or shared resources on a common box, so long as the two systems were highly independent (not both on same box or at same location)), so that BALUG infrastructure could continue to function at least reasonably, and perhaps identically or nearly so, if either system were to suddenly become unavailable for a while (even a fairly long while). As a random comment, I'll also note that this is (or will be) much more an issue for BALUG, than SF-LUG, as SF-LUG has two systems (SF-LUG.com and SF-LUG.org - highly independent and separate systems). Anyway, being able to reasonably gain a substantially independent system, that could be used for redundancy, failover, etc. could be a really good thing for BALUG - especially as and when we move fully clear of DreamHost.com ----- End forwarded message -----

2 1

Fwd: new.balug.org vs.(?) beta.balug.org (Re: beta.balug.org. (?) and other useful ideas?)
by Michael Paoli 05 Sep '07

05 Sep '07

And some information/clarification on new vs. beta (somewhat different purposes). Also, since that earlier e-mail (later on 2007-09-01) some infrastructure has been put in place to automagically propagate at least some web content from http://www.new.balug.org/ to http://www.balug.org/ Also, at least some initial bits of the beta.balug.org. infrastructure have been put into place (DNS, a very minimal bit of web stuff - doesn't yet have it's own DocumentRoot separate from new.balug.org, but that will likely happen in the near future). references/excerpts: ----- Forwarded message from Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> ----- Date: Sat, 1 Sep 2007 20:57:48 -0700 From: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Reply-To: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Subject: new.balug.org vs.(?) beta.balug.org (Re: beta.balug.org. (?) and other useful ideas?) To: balug-webmaster(a)balug.org, balug-sysadmins(a)balug.org Cc: balug-contact(a)balug.org This is primarily for our webmaster(s), but also for our BALUG systems administrators and (at least key) contacts, to be sure we're all at least reasonably "on the same page". A) new.balug.org. - please treat it (at least almost) like production - certainly at least in terms of web page content and the like (at least for stuff on/under http://www.new.balug.org/ on (default of) port 80. I will likely quite soon set up mechanism(s) to automagically replicate at least specific web content (page(s)) from http://www.new.balug.org/ (certainly at least including the main page there) to the main BALUG page (http://www.balug.org/) (for lazy (or efficient) typists, the www. can be ommitted in those URLs, and that will likely always be the case). This will also make life a bit easier for our webmasters :-) B) new.balug.org isn't the (proposed) beta.balug.org, nor will it be (though they may share the same IP address). new.balug.org. has mostly been and will become staging for production www.balug.org. Longer term, new.balug.org would likely replace www.balug.org (taking www.balug.org's name). Even longer term (at least as thus far proposed - exactly in what order things change might be subject to change) beta.balug.org would eventually merge its functionality into www.balug.org (and as beta.balug.org went or faded away, it would redirect what's migrated to the location of that material on www.balug.org.) C) beta.balug.org - at least thus far hearing mostly positive feedback on the idea, I'll probably soon start to proceed more in that direction (no "heavy" investments until I'm sure we have something between consensus and at least a quite overwhelming supermajority). ----- End forwarded message -----

1 0

stats: list membership (~457 total uniques)
by Michael Paoli 03 Sep '07

03 Sep '07

list subscribers (does include also those with delivery disabled): $ wc -l */memb*`date -I` 27 balug-admin/membership_2007-09-03 264 balug-announce/membership_2007-09-03 258 balug-talk/membership_2007-09-03 And a rough approximation of unique e-mail addresses (note that some folks use unique per-list addresses): $ sort -u */membership_*`date -I` | wc -l 457 Note also that it appears we have a fairly large number of folks that are subscribed to "talk", but *NOT* subscribed to "announce". Theoretically (at least logically) that shouldn't be the case (in general - typically exceptions being per-list e-mail addresses), but it is totally under "user" control. A quick count of that: $ { sort -u balug-talk/membership_`date -I` > cat balug-announce/membership_`date -I` \ > balug-announce/membership_`date -I`; } | sort | uniq -u | wc -l 185 references: http://lists.balug.org/pipermail/balug-admin-balug.org/2007-July/000391.html http://www.balug.org/#Lists file://new.balug.org/home/balug/e-mail_lists/

3 4

Re: [Balug-Admin] SF-LUG.COM replacement box (& BALUG)
by Michael Paoli 30 Aug '07

30 Aug '07

Well, treat replacing the sf-lug.com box as an "upgrade". ... basically all the data stays the same - or as same as feasible, or at *least* fully back up all the data and metadata, so all the applicable desired functionality and data can be restored and put back in place as soon as feasible. May also be quite desirable to tweak the filesystem configuration and mirroring a bit when doing the "upgrade" ... most notably, I know there's been desire to set up the disk mirroring to be quite symetrical - at present I don't think it's quite as symetrical as desired. Some of the filesystem heirarchy should also be split a bit more into separate filesystems, ... most notably I'd strongly recommend /usr and /var be separate filesystems. I'd also recommend /tmp be tmpfs. Among the metadata, also gather size and sizing information (e.g. du -sx /var; du -sx /usr; sfdisk -uS -l; sfdisk -uS -d). references/excerpts: $ hostname; df -k /var /usr; mount | awk '{if($3=="/tmp")print;}' sf-lug Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 9612516 3323336 5800888 37% / /dev/md0 9612516 3323336 5800888 37% / /dev/hda9 on /tmp type ext3 (rw) $ Quoting jim stockford <jim(a)well.com>: > it looks like we're getting a replacement box, > which means revisiting box issues, notably > hostname and the install-configs of the various > apps on the box (notably postfix and apache). > comments and opinions are welcome.

2 1

stuff for announce - speakers, $13, book(s)/swag, etc.
by Michael Paoli 15 Aug '07

15 Aug '07

stuff for BALUG announcment ... anything to add to this? I'll probably send it out late today or tomorrow A.M. items to cover: talk/presentation (community colo) $13.00 for dinner ($12.00 to restaurant) (modest price increase, first time the restaurant part of the price has gone up in many years - perhaps in the whole history of BALUG). LWCE "swag" - we have a bunch of books (and some other items too) ... will probably give at least some of that away as "door prizes" at the next BALUG meeting - I was thinking we'd "meter" them out - not try to give them all out at one meeting ... have a fair number of books. Might also give away more swag at meetings where we don't have speaker/presentation, and somewhat less where we do have speaker/presentation. BALUG fortune cookie - probably at least a bit of a mention about that. Anything else to cover? references/excerpts: ----- Forwarded message from Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> ----- Date: Wed, 15 Aug 2007 07:55:40 -0700 From: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Reply-To: balug-speaker-coordinators(a)balug.org Subject: Re: speaking at BALUG 2007-08-21 To: ryan Excellent. Thanks. If you also want to also specify a very short descriptor, (for subject line, title links to more details on the event/presentation, etc.) I could use that too. I'd presume something like: BALUG 2007-08-21: Ryan Bagueros & Isabela Fernandes Bagueros on Community Colo and for URL and (short) URL title on the project: http://www.sfccp.net/ San Francisco Community Colocation Project If you'd like those to appear differently, let me/us know. I hope to have the "announcement" item out sometime between late today and sometime tomorrow morning. If you want to peek at earlier example, you can look at some items in the "announce" list, e.g.: http://lists.balug.org/pipermail/balug-announce-balug.org/2007-July/000088.… Thanks again for agreeing to do the talk/presentation, and for the more detailed descriptive text too (we'll certainly also be able to use that). Feel free to also let us know if you have any questions or concerns. Quoting ryan: > Hello, we passed this description on to Jim and I'll put it here also: > > San Francisco Community Colo is a node in a larger network of > non-profit colocation facilities springing up around the country. > CCP's leverage community participation to drive down the costs of > server colocation by evenly distributing costs within a transparent, > open organization. > > This enables non-profits and community groups to rack their servers in > high-availability, high-speed facilities at an affordable cost. > We will discuss organizational logistics that we've learned and we'll > also talk about the practical and philosophical reasons for building > and supporting non-commercial internet infrastructure. > > Ryan Bagueros has worked in the internet industry for over 10 years in > the San Francisco Bay Area. He was head of engineering at Tagged.com, > one of the fastest growing social networking websites today, and went > on to found his own company, northxsouth.com, an open source business > with offices in North & South America. > > Isabela Fernandes Bagueros helped build one of Latin America's largest > independent media networks in Brazil. She's also worked with the > federal government of Brazil, migrating their systems to open source, > free software. She now lives in the SF Bay Area, working on a number > of digital media and open source projects, including the San Francisco > Community Colo. > > Ryan & Isabela Fernandes Bagueros > > Is that good? > > > Toya/Ryan, > > > > Please let us know, as soon as you can, some "short blurb" I can use > > for our web page (and brief synopsis) - who will be giving the talk > > (name(s) as you want them to appear), on what topic (as you want it > > listed), and also applicable URL(s). We usually use "short" description > > in Subject: on announcement(s), and also on at least some places on > > some of our web pages. > > > > We can also uses a somewhat longer (paragraph or so) description, > > mini-bios, background, etc., to include in the full text of "announcment" > > that we send out and similar locations/materials. > > > > We look forward to having you at the BALUG meeting 2007-08-21. > > Please let us know also if you have any questions or concerns. > > > > Quoting jim stockford: > > > > > You're on. The meeting is on Tuesday, August 21, > > > at the Four Seas restaurant in Chinatown, on Grant > > > Avenue near Sacramento. > > > jim > > > > > > On Aug 8, 2007, at 8:59 AM, toya wrote: > > > > > > > Hi Jim, > > > > Thanks for inviting us, we will do it for sure. > > > > Just let us know when so we can plan it and also invite the > > > > community to join :) > > > > > > > > jim stockford said: > > > >> > > > >> Hi, Toya, > > > >> Michael Paoli had the idea that the BALUG group > > > >> would be interested in hearing about community > > > >> colos in general and sfccp in particular. Can you > > > >> speak at the BALUG meeting? It's held at the Four > > > >> Seas restaurant on Grant Street in Chinatown. > -- > w . http://www.sfccp.net/ > . san francisco community colo project ----- End forwarded message ----- ----- Forwarded message from Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> ----- Date: Sat, 11 Aug 2007 11:15:01 -0700 From: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Subject: Re: dividing the spoils, LW E To: jim stockford I "inventoried" at least a fair chunk of what I hauled away from LinuxWorld intended mostly or entirely for user groups. This is most or all of the items more likely of interest to user groups. I've got a bunch of "smaller" stuff (stuffed critters, pen(s) and/or blinky things, etc. at home that I've not particularly inventoried yet. I've also some CDs/DVDs and other misc. stuff yet to inventory. At work (in San Francisco - I don't generally want to haul stuff home (Berkeley) just to haul it back to San Francisco (BALUG, etc.) again), I inventoried the following: _LINUX Format_ September 2007 with DVD www.linuxformat.co.uk Draft Manuscript of _Damn Small Linux_ ISBN-13: 978-0-13-233869-1 ISBN-10: 0-13-233869-6 _Knoppix Hacks_ with CD-ROM ISBN: 0-596-00787-6 _Professional LINUX Programming_ ISBN: 978-0-471-77613-0 _Hacking Ubuntu_ ISBN: 978-0-470-10827-7 _The Official ubuntu Book_ with DVD ISBN-13: 978-0-13235413-4 ISBN-10: 0-13-235413-6 _Rail Space_ ISBN-13: 978-0-321-48079-8 ISBN-10: 0-321-48079-1 _Solaris Performance and Tools_ ISBN: 0-13-156819-1 _Pro Oracle Database 10g RAC on LINUX_ ISBN: 1-59059-524-6 _LINUX Systems Administration_ ISBN-10: 0-596-00952-6 ISBN-13: 978-0-596-00952-6 _Practices of an Agile Developer_ ISBN: 0-9745140-8-X _;login_ August 2007 (USENIX) qty. 2 _Computing in Science & Engineering_ July/August 2007 (IEEE) _Security & Privacy_ July/August 2007 (IEEE) _LINUX Journal_ www.linuxjournal.com September 2007 t-shirt, green, LINUX SUPERSTAR, XL 100% COTTON PRESHRUNK (Novell/SUSE?) I figured I'd take the Solaris book to BUUG (likely to be of more interest there than at most LUGs), and one of the two _;login_ copies. Can potentially redistributed/rebalance/trade some or much of the rest, but I was thinking of taking most or all of it to BALUG (probably give away somewhat slowly as door prizes over the course of several meetings, perhaps with more/bigger/better door prizes for any meetings where we didn't have a speaker/presentation lined up). Most or all of what I dragged home that I'd intend for UGs is more magazines (not yet inventoried) and other flashy/fuzzy stuff (stuffed critters, pen(s) and/or blinky things, etc.), and some CDs/DVDs. references/excerpts: ~/tmp/linuxworld/2007/swag_for_UGs Quoting jim stockford: > I've got a box of books from various publishers along > with maybe 50 copies of Linux Magazine (featuring > Python as the cover story) and one or two dozen copies > of the current Ubuntu (7.04) live CD. > Lemme know what you want. Scott, Jason, and Toya > get priority for one title each, then Michael (BALUG), > Paul (SV-LUG), and I (SF-LUG) get to choose some > for give-aways -- maybe we'll arm wrestle in the case > of contention. > > O'Reilly: > 2 - Linux Kernel in a Nutshell, Kroah-Hartman > 2 - Programming Firefox, Feldt > 2 - Linux System Administration, Adelstein & Lubanovic > 2 - SUSE Linux, Brown > 1 - Knoppix Hacks, Rankin > > No Starch: > 1 - Linux Cookbook, Stutz > > Addison - Wesley: > 1 - RailsSpace, Hartl & Prochazka > 1 - Moving to Ubuntu Linux, Gagne > > Prentice Hall: > 2 - The Official Ubuntu Book (2nd ed), Mako Hill et al > 1 - JBoss Seam (Simplicity and Power beyond Java EE), Yuan and Heute > > Apress: > 1 - Beginning Ubuntu Linux (2nd ed), Thomas > 1 - Beginning Fedora (From Novice to Professional), Sharma and Thomas > > Novell: > 1 - Novell Cluster Services for Linux and Netware, Bastiaansen and van > Vugt > > Sams: > 1 - Linux Starter Kit (SUSE and video lessons on DVD with booklet), > <no_author_credit> ----- End forwarded message -----

1 0

Re: [Balug-Admin] where are the fortune cookies
by Michael Paoli 11 Aug '07

11 Aug '07

Quoting jim stockford <jim(a)well.com>: > I took the remaining fortune cookies to Andrew > at Untangle (about 400). Hopefully he'll be at the next BALUG meeting and can bring some reasonable bunch of them (someting in the 25 to 200 max range ... I was thinking maybe roughly 80)? They should get used fairly soon (like within a month) for best quality. I didn't remember to grab any of the remaining ones at the end of LinuxWorld - would be nice to have at least enough to give everyone who comes to the next BALUG meeting one (in case they'd not seen them), ... and give the restaurant at least a few too. Some of us could also manage to redistribute some modest quantity of them (I could take some to our tech. folks at work, and I could take some to BUUG to give to folks there (and for them to also hand out). I also have a few zillion (okay, well under 1,400) of the BALUG 1/4 sheet flyers we were trying to mostly also give away with the fortune cookies (has lots of LUG/UG/LINUX/etc. resources on the back too, in addition to BALUG stuff). Also, anyone have a digital camera they can snap a few good shots of these with (before they're all gone?). ... perhaps cookie in sealed bag, whole cookie out of bag, cookie split and pulled and with fortune at least about half visible, and good readable shots of front and back of fortune. I've got scanner and two of the fortunes, so I could cover those if someone else doesn't get them ... but that wouldn't work so well for the rest of the images. Oh well, ... we should've pushed them a bit more agressively at the start of LinuxWorld ... we fell a bit behind target giveaway rate, ... got back on track fairly quick, ... but never quite fully caught up.

1 0

$13.00 USD per person (includes dinner ...
by Michael Paoli 07 Aug '07

07 Aug '07

I've adjusted the BALUG web sites to show: "$13.00 USD per person (includes dinner" ... references: BALUG dinner prices going up!(?) to $13.00!(?) http://lists.balug.org/pipermail/balug-admin-balug.org/2007-July/000394.html

1 0

Re: [Balug-Admin] how to get BALUG promo material to LW E?
by Michael Paoli 07 Aug '07

07 Aug '07

Oooh, 644! Looks like a quite nice score! At least from what I can tell from the various maps, looks like if we in fact have 644 and it's as depicted in the maps I see, looks like it's a 10'x20' ... that's twice the size of the typical small booth and .org booths, if I'm not mistaken. If in fact we've got that much space, I sure hope we can make quite good use of it! references/excerpts: http://www.linuxworldexpo.com/dev/images/other/Website_NGDC_&_LWSFO7.pdf Quoting Bill Kendrick <nbs(a)sonic.net>: > > On Mon, Aug 06, 2007 at 08:11:26AM -0700, jim stockford wrote: > > Bill Kendrick has a web page for scheduling, he's > > maintaining it as people send him info. > > the web page is > > http://www.lugod.org/projects/lwe/ > > Uhyup. I will be offline for huge chunks on Tues and Thurs as I take > the train to/from work in the Bay Area (I'm living in Davis again). > > > > I think the common LUG booth number is 644, not 640. > > Correct. Confirmed by looking for the "LUGS" booth on the Exhibit Hall map > up on the LWCE website. > > -- > -bill! > bill(a)newbreedsoftware.com > http://www.newbreedsoftware.com/ >

2 1

Re: [Balug-Admin] how to get BALUG promo material to LW E?
by Michael Paoli 06 Aug '07

06 Aug '07

I'm finishing up a bit of Bay Area Debian (BAD) materials, but after that I'll probably do something at least somewhat similar for BALUG. If someone wants to jump in on doing materials (or volunteering to print, photocopy, and cut) feel free to let me/us know (can also give me a ring at 1-510-883-0772 (home/msg.). I've got some graphics that'll get used to tie in with the fortune cookie thingy (some of which will go up on the BALUG web site soon, ... before the Expo opens on Tuesday, anyway). Anyway, basic plan for BALUG (and similar for the BAD stuff I'm doing), finish up preparation of the materials (short of photocopying, cutting, and perhaps printing) before tomorrow morning, then print them out (if not already printed), and use those as "masters", photocopy them, and then slice 'em up into 1/4 sheets. For LinuxWorld Expo, I may not make it there quite as soon as the Expo opens on Tuesday, but I expect to make my first visit to the Expo on Tuesday not long after it opens. I'd drop them off then (and likewise the BAD stuff). For the BALUG stuff, I'd probably also write up an "instruction" sheet for the booth attendee(s) (might not always have a BALUG person there, but hopefully have someone from some LUG(s) there at any given time). Instruction sheet might be most handy in handling of fortune cookies - we probably want to avoid someone just dumping 'em all at the front of the table and having 'em all gone within the first hour or two. Probably best to hold them back a bit, and "ration them" per day/hour, ... so they can be slowly given out throughout the show (and so folks don't horde 'em or grab big bunches of 'em). Between BALUG and GroundWork OpenSource, not sure precisely what the plan is as far as what percentage of cookies get distributed from what booth, ... that might also depend on the shared LUG booth staffing (and timing). Did we or anyone ever put up a wiki page to coordinate the shared LUG booth "staffing" ... or (Jim? or someone else?) is that being coordinated via e-mail or other means? Quoting jim stockford <jim(a)well.com>: > The common LUG booth is #640 > I believe you're bringing some hardcopy promo > for BALUG, yes? If so, what arrangements do you > want to make to get it there? > * bring it whenever you come to see the show > * meet somebody pre-show > * other

2 1

← Newer
1
...
36
37
38
39
40
41
42
...
55
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

BALUG-Admin