BALUG-Admin

balug-admin@lists.balug.org

1 participants
539 discussions

BALUG history/archives
by Michael Paoli 15 Nov '07

15 Nov '07

I did manage to retrieve a fair chunk of older BALUG history/archives. Thanks to The Internet Archive, I got what would seem to be much of the older mail list materials. Covering from approximately 1997-01-27 through approximately 2001-02-11. We have the list materials from 2001-06-15 going forward. The gap from 2001-02-11 through 2001-06-15 might be "lost" or very hard to obtain ... unless we find someone who saved an e-mail archive that includes that. That gap is likely from when the Internet Archive made its last pass over the older mail list locations, and when those locations were last used. On 2001-06-15 the lists picked up starting at a new location. There's still a fair bit of other material to retrieve. Some of the quite old web stuff (which can still probably be pulled from The Internet Archive - I've gotten much of that already, but have some other pieces to retrieve) ... and there's much of the more mid-timeframe range web content (e.g. meeting minutes and materials and lots of other useful/interesting stuff) ... from roughly 2003-09 through 2007-05 ... most of that is "trapped" behind some broken PHP/MySQL on our "legacy" site, ... there may also be some stuff that may be difficult to infeasible to find towards the early end of that range - most notably from the prior site from last pass of The Internet Archive through to the last changes on that older site before it went away and was replaced with the newer site. Anyway, I/we will likely make these older materials available (at least what we've got or been able to retrieve thus far) in the not-too-horribly-distant future. Would be nice to also close in the gaps of thus far missing or not presently accessible materials ... at least as much as feasible, anyway.

2 2

BALUG November Announcements
by Andrew Fife 13 Nov '07

13 Nov '07

BALUG Volunteers: Michael Paoli & I mailed the November announcement to the following LUG mailing lists (see below) and we have planed to send reminders on Sunday or Monday. Quick Question: Does anybody know if BayLISA, East Bay LUG or Stanford LUG have mailing lists? If so, links to their registration pages would be much appreciated, as I have not been able to find them. Lastly, I have to say that I thought Bill Kendrick's post to balug-talk on November 10th regarding LUGOD was the best LUG announcement message I have seen yet. Imitation is the most sincere form of flattery so I borrowed a lot of his style in sending out the message. LUGs mailed for Nov Meeting: SVLUG SFLUG PenLUG Bay Area Debian BayPIGgies SMAUG SoCoSA CABAL BUUG SFO BUG SF Perl Mongers NB LUG BaySec BAFUG Oakland Perl Mongers ---------------------------------------- Andrew Fife Untangle - Open Source Security Gateway download.untangle.com 650.425.3327 (O) 415.806.6028 (C) afife(a)untangle.com -----Original Message----- From: Michael Paoli [mailto:Michael.Paoli@cal.berkeley.edu] Sent: Thursday, November 08, 2007 4:30 AM To: balug-sc(a)balug.org Subject: RE: BALUG Nov. (etc.) annoncement Anyway, ... hopefully you all got/saw it, but in any case the announcement is out: http://lists.balug.org/pipermail/balug-announce-balug.org/2007-November/00 0095.html Quoting Michael Paoli <Michael.Paoli(a)cal.berkeley.edu>: > Well, I don't see the announcement out there yet, ... so, ... I'll > be sending it out very shortly unless I see any indication not to do > so. Hopefully I've incorporated "enough" of folks suggestions that > it will reasonably please most ... but seems infeasible to please > everyone 100% - so it's a bit of a compromise from various bits of > input and suggestions. > > Quoting Michael Paoli: > > > Anyway, to make getting the announcement out a bit easier, I also > > added these two folks: > > Andrew Fife <afife(a)untangle.com> > > Jesse Zbikowski <embeddedlinuxguy(a)gmail.com> > > as being able to post to the "announce" list unmoderated - i.e. > > you can now post it there directly yourself. I picked and added > > the two noted above, as, in addition to myself, they're doing most > > of the on-line posting/e-mailing/event listing publicity anyway. > > > > Also, I did slightly update the "announce" list policy and stuff, to > > clarify and improve it a bit based on various uses and intended uses, > > and feedback and suggestions from "announce" list subscribers (including > > also many of Rick Moen's excellent suggestions). > > The (slightly updated) policy can be seen here: > > http://lists.balug.org/listinfo.cgi/balug-announce-balug.org > > ... most notably, keep the "volume" down - probably aim for only 2 > > postings to the "announce" list per month, with a max of 3 (sort of > > hold the 3rd in reserve, in case the meeting venue burns down > > or Linus decides to pay visit to our meeting on short notice).

3 3

(forw) 66 Balug-Talk moderator request(s) waiting
by Rick Moen 12 Nov '07

12 Nov '07

So, this illustrates why I had the retention period for pending moderator requests dialed down to 3 days (the length of a holiday weekend), and why the recent increase to 21 days strikes me as a bad idea: Dreamhost's spam-blocking is really terrible, so the held-postings count was at 66 today and was obviously heading upwards. So, I've reduced the retention period for all three mailing lists, once again, this time to 5 days. I do read my mail, and so will not fail to see notices of held legitimate postings, except perhaps once in a blue moon when I'm actually able to get away on holiday. ;-> ----- Forwarded message from balug-talk-bounces(a)lists.balug.org ----- From: balug-talk-bounces(a)lists.balug.org To: balug-talk-owner(a)lists.balug.org Date: Mon, 12 Nov 2007 06:02:37 -0800 Subject: 66 Balug-Talk moderator request(s) waiting The Balug-Talk(a)lists.balug.org mailing list has 66 request(s) waiting for your consideration at: http://lists.balug.org/admindb.cgi/balug-talk-balug.org Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Pending posts: From: tiaoewaomfd(a)tom.com on Sun Nov 4 09:33:32 2007 Subject: ??!!??????????!!????????? Cause: Post by non-member to a members-only list From: mihomiho333(a)so-net.ne.jp on Sun Nov 4 16:23:22 2007 Subject: ??????? Cause: Post by non-member to a members-only list From: mihomiho333(a)so-net.ne.jp on Sun Nov 4 16:23:23 2007 Subject: ??????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Sun Nov 4 18:05:26 2007 Subject: ??????100?OFF?? Cause: Post by non-member to a members-only list From: baomi204(a)163.com on Sun Nov 4 21:33:00 2007 Subject: ??????????????? Cause: Post by non-member to a members-only list From: kkkkkkthkghfyhkk441(a)yahoo.de on Sun Nov 4 22:48:48 2007 Subject: ?????????????? Cause: Post by non-member to a members-only list From: kkkkkkthkghfyhkk441(a)yahoo.de on Sun Nov 4 22:49:30 2007 Subject: ?????????????? Cause: Post by non-member to a members-only list From: kasami21(a)so-net.ne.jp on Sun Nov 4 23:27:35 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: kasami21(a)so-net.ne.jp on Sun Nov 4 23:27:41 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Mon Nov 5 01:49:48 2007 Subject: ?GS????????????? Cause: Post by non-member to a members-only list From: sakurasaku_0325_hy(a)yahoo.de on Mon Nov 5 01:59:23 2007 Subject: ???????? Cause: Post by non-member to a members-only list From: mayumi00(a)ocn.ne.jp on Mon Nov 5 02:00:26 2007 Subject: ???????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Mon Nov 5 02:45:13 2007 Subject: ???????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Mon Nov 5 03:46:30 2007 Subject: ???????????????? Cause: Post by non-member to a members-only list From: mit_soco(a)sohu.com on Mon Nov 5 06:13:01 2007 Subject: ?GS????????????? Cause: Post by non-member to a members-only list From: gaojie0323(a)sohu.com on Mon Nov 5 06:34:58 2007 Subject: ?????????1????????????????????????? Cause: Post by non-member to a members-only list From: neteast_mit(a)yahoo.com.cn on Mon Nov 5 11:50:55 2007 Subject: ????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Mon Nov 5 11:51:00 2007 Subject: ????????????? Cause: Post by non-member to a members-only list From: leigywox4(a)a-net.ne.jp on Mon Nov 5 21:53:29 2007 Subject: ??????100?OFF?? Cause: Post by non-member to a members-only list From: mlkjppxzra4(a)a-net.ne.jp on Tue Nov 6 01:33:11 2007 Subject: ??????100?OFF?? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Tue Nov 6 01:36:25 2007 Subject: ?24?? ?????? Cause: Post by non-member to a members-only list From: balug-talk(a)infoseek.jp on Tue Nov 6 02:14:04 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: balug-talk-balug.org(a)msn.co.jp on Tue Nov 6 02:14:08 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: mafan57(a)yeah.net on Tue Nov 6 02:47:05 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Tue Nov 6 03:14:21 2007 Subject: ?24?? ?????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Tue Nov 6 07:51:35 2007 Subject: ???????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Tue Nov 6 09:31:46 2007 Subject: ???????????????? Cause: Post by non-member to a members-only list From: guojie230(a)163.com on Tue Nov 6 15:08:34 2007 Subject: ??????????????? Cause: Post by non-member to a members-only list From: service(a)paypal.com on Tue Nov 6 16:41:36 2007 Subject: Your account has been flagged! Cause: Post by non-member to a members-only list From: nana77nana(a)so-net.ne.jp on Tue Nov 6 17:21:57 2007 Subject: ????????? Cause: Post by non-member to a members-only list From: nana77nana(a)so-net.ne.jp on Tue Nov 6 17:22:33 2007 Subject: ????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 00:38:27 2007 Subject: ????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 00:38:46 2007 Subject: ????? Cause: Post by non-member to a members-only list From: taibian07(a)126.com on Wed Nov 7 06:08:30 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: sanlao202(a)sina.com on Wed Nov 7 09:56:53 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 10:24:06 2007 Subject: ?GS????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 11:09:14 2007 Subject: ?GS????????????? Cause: Post by non-member to a members-only list From: sfh793(a)163.com on Wed Nov 7 15:29:07 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 23:11:39 2007 Subject: ????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Wed Nov 7 23:11:41 2007 Subject: ????????????? Cause: Post by non-member to a members-only list From: o05689ok99(a)tom.com on Thu Nov 8 03:48:14 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: baomi201(a)163.com on Thu Nov 8 09:15:38 2007 Subject: ????????????????????????????? Cause: Post by non-member to a members-only list From: o05689ok(a)tom.com on Thu Nov 8 15:13:11 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Thu Nov 8 18:18:26 2007 Subject: ?24?? ?????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Thu Nov 8 20:09:53 2007 Subject: ?24?? ?????? Cause: Post by non-member to a members-only list From: bailao10(a)yahoo.com on Thu Nov 8 23:14:11 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Fri Nov 9 02:36:53 2007 Subject: ?????????? Cause: Post by non-member to a members-only list From: jywvt300gatz(a)yahoo.co.jp on Fri Nov 9 05:26:38 2007 Subject: ????????????? Cause: Post by non-member to a members-only list From: neowycom6(a)a-net.ne.jp on Fri Nov 9 06:15:46 2007 Subject: ?????????????????? Cause: Post by non-member to a members-only list From: jwcmwtaxzm5(a)a-net.ne.jp on Fri Nov 9 06:16:43 2007 Subject: ?????????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Fri Nov 9 07:27:51 2007 Subject: ?????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Fri Nov 9 17:14:56 2007 Subject: ?????????????? Cause: Post by non-member to a members-only list From: cjyoujsd(a)yahoo.com.cn on Fri Nov 9 18:10:49 2007 Subject: ?????????????? Cause: Post by non-member to a members-only list From: taibian03(a)yahoo.com on Fri Nov 9 22:17:50 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: mit_soco(a)so-net.ne.jp on Sat Nov 10 02:20:16 2007 Subject: ??????????????? Cause: Post by non-member to a members-only list From: mit_soco(a)so-net.ne.jp on Sat Nov 10 02:20:21 2007 Subject: ??????????????? Cause: Post by non-member to a members-only list From: nanako456(a)sina.com on Sat Nov 10 09:00:45 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: gaojie0327(a)sohu.com on Sat Nov 10 09:16:45 2007 Subject: ???0???????????!!??????????????? Cause: Post by non-member to a members-only list From: bizawards(a)usamsgserv.com on Sat Nov 10 16:53:06 2007 Subject: Annual Conference Information Cause: Post by non-member to a members-only list From: sfh702(a)163.com on Sun Nov 11 03:07:05 2007 Subject: ?????????????????????????????????!! Cause: Post by non-member to a members-only list From: balug-talk(a)msn.co.jp on Sun Nov 11 04:21:44 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: balug-talk-balug.org(a)hotmail.co.jp on Sun Nov 11 04:22:23 2007 Subject: ??????????? Cause: Post by non-member to a members-only list From: baomi202(a)163.com on Sun Nov 11 13:20:22 2007 Subject: ??????????????????? Cause: Post by non-member to a members-only list From: manhattan(a)chs.bank.com on Sun Nov 11 17:06:12 2007 Subject: Chase: Update Your Information Cause: Post by non-member to a members-only list From: gzuqhgn1(a)so-net.ne.jp on Sun Nov 11 19:45:05 2007 Subject: ?????(>_<) Cause: Post by non-member to a members-only list From: mymozlr6(a)so-net.ne.jp on Sun Nov 11 19:45:44 2007 Subject: ?????(>_<) Cause: Post by non-member to a members-only list ----- End forwarded message -----

1 0

BALUG web site update (infrastructure, etc.)
by Michael Paoli 12 Nov '07

12 Nov '07

I think it's been a while since I put a bit of information on the list about some of the infrastructure updates. Anyway, though perhaps a bit slow, some of the plans are continuing to well progress. Most notably, as of quite recently (this weekend), at least a fair number of the earlier plans have now been implemented (though I should still round out and catch up on some documenting of it, but hopefully it's mostly relatively self documenting (e.g. those that have the access to change the relevant stuff generally also have the access to at least read the configurations to see how most, or nearly all of the pieces are tied together)). Anyway, webmaster (I'll use webmaster to refer to webmaster(s)) should have significantly improved access to be able to change stuff - including the production [www.]balug.org - at least indirectly, anyway. Starting from production [www.]balug.org and working backwards ... There's now in place a crontab driven rsync script, which propagates appropriate changes from [www.]new.balug.org to [www.]balug.org. [www.]new.balug.org is essentially pre-production staging area - stuff dropped there gets propagated to production ([www.]balug.org.) within approximately 15 minutes or less. webmaster has rather free reign over the contents of [www.]new.balug.org. Also, to avoid unintentionally clobbering legacy stuff in production (from which we still wish to extract some important content), various filters are in place on the rsync to prevent accidental clobbering, and also, in the DocumentRoot for [www.]new.balug.org, various ownerships/permissions are set such that webmaster can't place something where it couldn't be (safely) propagated to production. So, ... effectively, webmaster has relatively free reign in [www.]new.balug.org and that automagically propagates to production. This also affords a fair amount of safety and security, as the present production environment is rather fragile (there's no easy way to separate out webmaster and sysadmin roles in the present production, and the effective sysadmin access could easily by accident or intention destroy lots of stuff there that would be infeasible to impossible to restore/correct - we hope to more fully correct that situation in the future, but that's at least where we still stand presently - at least in part). Then there's also [www.]beta.balug.org. There are actually multiple levels of webmaster - one level that has access to do stuff that propagates to production, and one that doesn't. Only the lower level of access is required (at least presently) to change stuff in [www.]beta.balug.org. At least presently, similar to [www.]new.balug.org. it has various ownerships/permissions in place such that webmaster can't place something where it couldn't be replicated to [www.]new.balug.org and propagated to production. [www.]beta.balug.org may also be highly suitable for placing stuff we don't presently want propagated to production - e.g. for larger archival materials (such as audio recordings of past meetings) where due to space it may not be advisable presently to copy those to production - but we can well accommodate those larger items in [www].beta.balug.org. There's also [www.]test.balug.org - a scratch/test area. webmaster has even fewer limitations there - e.g. permissions/ownership allow webmaster almost completely free reign in the DocumentRoot of [www.]test.balug.org. Anyway, much of this is done via the following various mechanisms: * Apache NameVirtualHost configurations * appropriate separation of roles/users/groups, use of sudo, etc., e.g. the DocumentRoot for one of the webmaster IDs/roles: $ id; ls -ld . uid=10742(balugwm2) gid=10742(balugwm2) groups=10742(balugwm2) drwxrwsr-t 4 root balugwm2 4096 Nov 11 20:39 . $ * along with carefully crafted IDs, access, and ssh configurations, some carefully crafted crontab driven rsync scripting, e.g.: http://www.balug.org/.www.balug.org_rsync.txt (it's not actually run from that location, but the script is readable from there to aid webmaster in understanding exactly what's happening in production and how things propagate from [www.]new.balug.org to [www.]balug.org) A fair bit of the communication has also taken place off-list, but here's some more bits of earlier on-list communication references: http://lists.balug.org/pipermail/balug-admin-balug.org/2007-September/00040… http://lists.balug.org/pipermail/balug-admin-balug.org/2007-September/00041…

1 0

[DRAFT] BALUG 2007-11-20: James Burgett, "ACCRC+Linux: Keeping computers out of Landfills"; etc.
by Michael Paoli 09 Nov '07

09 Nov '07

[ Note this is DRAFT for announcement. Flyer isn't present at the URL shown ... yet. If I don't get an updated flyer, I may make some edits on the older version and then use that. I did include mention of the door prizes - but kept it very brief. Anyway, I hope to have the "final" version out this evening / tonight, or 2007-11-07 A.M. I also tried to better approximate RFC 1153 message digest format, as that may make reading in many mail clients a bit more convenient and user-friendly. ] Contents: Bay Area Linux Users Group (BALUG)[1] 2007-11-20: James Burgett, Alameda County Computer Resource Center (ACCRC)[2]: "Free Software, The Environment, Social Welfare, and the Digital Divide" RSVP door prizes Other upcoming BALUG meetings references (about BALUG, time, location, etc.) ---------------------------------------------------------------------- For our 2007-11-20 BALUG meeting we are pleased to present: James Burgett, Alameda County Computer Resource Center (ACCRC)[2]: "Free Software, The Environment, Social Welfare, and the Digital Divide" flyer[3] (PDF) to help promote the event James will recount the path ACCRC has taken as it's grown in the last five years to reclaim and reuse computers, peripherals, and other electronic devices people donate. In general, ACCRC gives computers to individuals and worthy organizations without charge or strings. ACCRC uses Linux on the systems it gives away and has developed quite a bit of expertise in installing various Linux distros on various (old) hardware. ------------------------------ Planning to come to BALUG meeting? Please e-mail us a note at: rsvp(a)balug.org indicating meeting date and if more than just yourself the number of folks you're RSVPing for, etc. See also: http://www.balug.org/#RSVP[4] Thank you for RSVPing if you're planning to attend. ------------------------------ Door prizes[6]! Yes, we have at least the following for door prizes: _Pro Oracle Database 10g RAC on LINUX_ ISBN: 1-59059-524-6 _Practices of an Agile Developer_ ISBN: 0-9745140-8-X ------------------------------ Other upcoming BALUG meetings We also have quite a lineup of speakers/presentations for BALUG meetings. Not only do we have James Burgett, ACCRC[2] as noted above, but we also have the following lined up for the months ahead - be sure to check out our website http://www.balug.org/[1] for more details and the latest updates. If you're not already subscribed to the BALUG "announce" list[5], be sure to subscribe to be notified of these and future announcements. 2007-12 (no meeting in December this year) 2008-01-15 Eric S. Raymond 2008-02-19 Bruce Perens 2008-03-18 (TBD) 2008-04-15 Eric Allman ------------------------------ references: 1. http://www.balug.org/ 2. http://www.accrc.org/ 3. http://www.balug.org/flyers/2007-11-12.pdf 4. http://www.balug.org/#RSVP 5. http://www.new.balug.org/#Lists door prizes (past and coming up): 6. http://lists.balug.org/pipermail/balug-admin-balug.org/2007-August/000401.h… meeting time, location, and lots of other great BALUG information: Bay Area Linux Users Group (BALUG) http://www.balug.org/

4 5

BayAreaLinuxUsersGroup Domains ---> BALUG.org
by Andrew Fife 04 Nov '07

04 Nov '07

I believe that all 6 of the domains that were purchased now point to new.balug.org Bayarealinuxusersgroup.com/.net/.org Bayarealinuxusergroup.com/.net/.org -Andrew ---------------------------------------- Andrew Fife Untangle - Open Source Security Gateway download.untangle.com 650.425.3327 (O) 415.806.6028 (C) afife(a)untangle.com

2 1

List "policy"/description tweaks
by Michael Paoli 03 Nov '07

03 Nov '07

List "policy"/description tweaks. These are changes I have in mind for the lists. This isn't for the (shorter) text that appears on our main http://[www.]balug.org/ web pages, but rather on the more detailed Mailman list pages, e.g.: http://lists.balug.org/listinfo.cgi/balug-talk-balug.org What I show below is draft of text changes (I'd also do similar on Balug-Admin regarding automagic subscrition to Balug-Announce). The text below doesn't include the relevant URLs (those would be linked appropriately from the text), and there may also be some slight tweaking of e-mail address configurations (most notably admins and moderators for the lists, and any related @balug.org aliases - I'll coordinate with Rick Moen to be sure anything we do there is and works reasonably). ------------------------------------------------------------------------ Balug-Announce This is a low-volume* announce-only (non-discussion) mailing list to cover items of key interest to Bay Area Linux Users Group (BALUG) and its members (e.g. meeting announcements/programs, important announcements, BALUG "news" items of note, and items highly likely to be of interest to many/most BALUG folks and related Linux community). If you subscribe to any of BALUG's lists, you should subscribe at least to Balug-Announce. For more general BALUG and related discussion, see the Balug-Talk list. If you think you have something highly worthy of being sent to the Balug-Announce list, send it to the Balug-Announce list moderators, and we'll consider sending it along, including it, or providing a short reference to it. Note, however, in most cases it is typically more appropriate to post an item to Balug-Talk, and if we deem it appropriate to do so, we may then cross-reference the item posted on Balug-Talk and/or include some of its relevant content on item(s) we send to Balug-Announce. Balug-Announce does not have the "digest" option enabled, as its mailings should be important, and might sometimes be time critical. Note however that the mailings may, however, be in a digest-like form (e.g. a single mailing may include several items of note, and may also have a very brief summary or subject of each noted near the top of the e-mail's body). Balug-Announce is publicly archived. *approximately 1 to 3 e-mails per month - we aim to keep the average at or below 3 per month ------------------------------------------------------------------------ Balug-Talk This is a public discussion mailing list for Bay Area Linux Users Group (BALUG). Items should generally be reasonably appropriate/relevant to the group (e.g. Linux and Open Source, in, around, or including the greater San Francisco Bay Area, etc.). Please try to use/update Subject: on mailings to reasonably summarize what the posting is about. If you feel compelled to post on something rather to quite off-topic, kindly try to indicate so in the Subject: (e.g. start it with "[O.T.]" or something like that). And of course, don't spam the list. We intend to interpret the above, notwithstanding the below, rather liberally. Job postings - job postings/listings are disallowed*, with one exception**. Note however that there isn't a prohibition against noting one's availability for job/contract work, posting a "position wanted" item, or discussion about employment and employers, job markets, recruiting/hiring/firing, whether or not not the list should allow job posting and under what circumstances, how to and not to do a job posting and where, etc. The prohibition is to be interpreted rather narrowly - just don't post a job listing or collection of job listings, or something with the rather exclusive intent to refer to your, your company, or your agency's job listing(s) or job site. If you're looking for places where job postings are permitted/welcomed, you may want to check some other resources (e.g. SVLUG Jobs or BayLISA Jobs, or consult the policy regarding such for SF-LUG). Balug-Talk is publicly archived NOTE: Subscribers to Balug-Talk should also be subscribed to Balug-Announce. If you're subscribed to Balug-Talk, but not subscribed to Balug-Announce, you may find yourself automagicly also added as subscribed to Balug-Announce. If for some reason you don't want that to happen (e.g. you use distinct e-mail addresses for each to route/filter/sort more to your preferences), send an e-mail note to Balug-Announce list admin indicating what e-mail address you don't want automagicly added to Balug-Announce, and why, and we'll add it to our exceptions list. * Job posting policy (general prohibition) may be subject to change/adjustment over time, mostly based upon majority (or at least plurality) of wishes of users subscribed to Balug-Talk (e.g. policy might be adjusted slightly or significantly, or BALUG might decide to create a separate "jobs" list). ** If you have been scheduled and confirmed to give a talk/presentation at BALUG, or have rather to quite recently given such a talk, you are permitted to make a job posting/announcement to BALUG-Talk. It may be advisable to include short mention towards the top of the e-mail that reminds folks how this specificly fits within list policy (e.g. "Thanks for having me for the ... BALUG talk. Per the list policy, here are the currently open positions I'd like to mention:"). Please, only one job posting e-mail per talk/presentation. It may be highly advisable to include relevant links and/or contact information in the posting where folks will be able to obtain updates on the position(s) (e.g. description changes, position closed, additional positions opened, etc.) so one doesn't feel tempted to "need" to make a follow-up posting to the list about the position(s). ------------------------------------------------------------------------ See also, e.g.: http://lists.balug.org/pipermail/balug-admin-balug.org/2007-October/000419.… (starting about halfway down that item) for a bit of earlier discussion on some of these items.

2 4

Lists: stats, etc.
by Michael Paoli 22 Oct '07

22 Oct '07

stats: list membership (~482 total uniques) total uniques up slightly (by about 5%) from not too long ago. list subscribers (does include also those with delivery disabled): $ wc -l */memb*`date -I` 27 balug-admin/membership_2007-10-21 304 balug-announce/membership_2007-10-21 251 balug-talk/membership_2007-10-21 $ sort -u */membership_*`date -I` | wc -l 482 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 172 ... nevertheless *that* number is down moderately from not too long ago. After considering various options, what I'm inclined to do to "rectify" that, is after announcing it and noting it on the lists appropriately, for e-mail addresses that are on the "talk" and/or "admin" list lists, they'll get periodically added to the "announce" list - unless they specifically notify "us" (list admin(s)) that they want to be on an "exception" list (e.g. if they have and want to use separate per-list subscription addresses). The process would be semi-manual at least initially, but would, longer term, be fully automated (well, except for the being added to the "exception" list - that might require manually adding the e-mail address to a file). The above noted approach has the advantages of: * it avoids the potential complications of lists subscribed to lists and differing options/configurations (e.g. we want "announce" to be non-digested, but we want folks to have digested form be option for "talk"; if we subscribed "talk" to "announce", then those getting "talk" digested, and not subscribed to "announce" would only see "announce" within digested "talk" e-mails) * it allows users to have separate per-list e-mail subscription addresses if they desire such, and provides means for them to request not being automatically added to "announce" based on subscription to "talk" and/or "admin". I'm also inclined to set up an alias for the balug list admin(s) - that way folks have a consistent e-mail address that can be used for that. (Mailman lists and displays the list admin e-mail address(es) - it looks a lot more clean if there's a "generic" address for that function, rather than listing all the individual folks that are in the set of list admins for any given list). references/excerpts: http://lists.balug.org/pipermail/balug-admin-balug.org/2007-September/00040…

1 0

Probably should not have been approved for "announce": Maemo (N800 Linux tablet) course at Stanford on November 6
by Michael Paoli 16 Oct '07

16 Oct '07

This message probably should not have been approved for the BALUG "announce" list: http://lists.balug.org/pipermail/balug-announce-balug.org/2007-October/0000… The evidence would seem to indicate it got "approved" (perhaps someone accidentally clicked the wrong item or thought it was for a different list), though it's not impossible that it may have been passed/approved through some header forging or the like. The message would have been okay for "talk" (that's a relatively open forum, though it could still do without all the attachments). "announce", however should be quite low volume (like 1 to 3 messages per month) and quite topical to BALUG (not a catch-all for any and/or everything LINUX, OpenSource, etc., that anyone and/or everyone may care to announce). If there are non-BALUG events of note that we want to mention on "announce", it's probably most suitable to include a short mention and reference to such along with one of our regular mailings to "announce" ... if at all.

2 2

Re: [Balug-Admin] consider changing the format ... brief time that lets people make announcements
by Michael Paoli 21 Sep '07

21 Sep '07

I think we more-or-less already do that, ... just not all that formally. Typically, frequently, commonly just before the talk/presentation starts, and/or around when the more formal part of talk/presentation ends, we tend to make, and allow for brief announcements (e.g. plug our upcoming meetings events, other events of note, and if someone wants to make a quite brief announcement that's relevant, they can). Quoting jim stockford: > we might consider changing the meeting format > to allow what bayPIGgies call "mapping", a brief > time that lets people make announcements > (including a plea for a ride after the meeting) > such as hiring and other things. > seems to me possible good times for such an > interlude would be at the start of dinner or just > before the speaker begins. probably limit total > time to five or seven minutes, each speaker > getting maybe 60 seconds.

2 1

← Newer
1
...
34
35
36
37
38
39
40
...
54
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