Hey all, BACKGROUND
Currently, the GNHLUG websites and mailing lists (and some of the local LUG stuff) are generously hosted on servers owned and operated by Bruce Dawson's company, Codemeta. These servers also host services for paying customers, so we have to be fairly careful to not screw things up. That means security and configuration management and all that stuff. As Bruce reminded me, I've got a server I'm willing to lend to the cause of GNHLUG (even if that cause isn't that well defined :) ). MV Communications in Manchester has generously agreed to host it for us. WHY There are two major benefits I see to this: One is that we can allow more people more access. Right now, only a few GNHLUG people have shell access to anything. Fewer still (only Bruce, I think) have privileged access. If we have our own server, the requirements for access can be lower, as it isn't somebody's business that's on the line. This is not to say the root password will be published on the TWiki; just that more people will be able to help do stuff. This also means that critical maintenance of GNHLUG's Internet infrastructure stops being *just* Bruce Dawson's problem. I'm sure Bruce will appreciate that more then most. :) The other major benefit, related to the first, is that we can more aggressive in our Internet activities. Doing things like upgrading TWiki, or Apache, or mailing list software, or installing new software to try out idea X, will be much more practical. I think there are a few applications of the technology that could really benefit us, if we only had a sandbox to play in. APPLICATIONS Some things that occur to me: - Everything we have now - Automated meeting announcements (yippie!) - Dedicated calendar software (integrated with the above) - Web-based job database (job seekers and job openings), easily postable and searchable without needing a mailing list. - Poll/survey software - RSVP software for the meetings You get the idea. Suggestions welcome. WHERE TO BEGIN Okay, so assuming everybody likes the idea, the next question is, how do we begin setting this up? I'd like this to be as much of a "group effort" as possible. Partly because I'm not familiar with some of the software we need, partly because I'm only one person, but mostly because it's just the Right Thing to do. Aside from the transparency aspect (I'm sure we're all aware of where I stand on *that*), I think it could be a great learning experience for members of the group, myself included. I'd like to see learning available to others. What I'm not so sure about is how to actually approach the mechanics of that collaboration. Obviously, a mailing list would be used for some of this. Should that list be separate from this -org list? I'm not sure how much traffic it would generate, but given the minutia that computers tend to involve, maybe all the people on this -org list might want it elsewhere. On the other hand, we're all pretty much computer geeks (or we wouldn't be here), so maybe it is topical. For that matter, should it be on -discuss? As far as calling for volunteers to help out, I'm contemplating just posting an announcement to -discuss to see who might be interested. What are people's thoughts on that? MORE Additional discussion will no doubt occur at the summit thing this Sunday. In the meantime, as always, I welcome comments, suggestions, condemnations, flames, thoughts, vague notions, and incoherent ramblings. :-) -- Ben "If we had a server we could host the server mailing list on it" Scott _______________________________________________ gnhlug-org mailing list gnhlug-org@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-org
