From wplug at borkware.com Mon Jul 24 21:44:50 2006 From: wplug at borkware.com (Mark Dalrymple) Date: Mon, 24 Jul 2006 21:44:50 -0400 Subject: [wplug-web] Re: WPLUG Website In-Reply-To: <44C3B617.7020200@nedyah.org> References: <44C3B617.7020200@nedyah.org> Message-ID: <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> Hey Mike! On Jul 23, 2006, at 1:47 PM, Michael Semcheski wrote: > Recently, the topic of changing the wplug membership structure has > come > up on mailing lists. > > I went to the website to look for old board minutes, or news, etc. to > see how this issue has progressed, and I couldn't find it. Yep. it's a problem. In the short-short term, we can give Dave Ostroske a login and he can create files locally for minutes and whatnot. > Not too long before that, there was a short discussion about changing > the website's underlying cms. The need for a wiki (or other similar CMSy thing) is the main thing - stuff can be put there and edited by folks without access to the machine. I know Patrick was talking about mediawiki and that it's easy to install. I have no time (Google demands a lot of my time now, plus less involvement due to gas prices and having one vehicle in the family) to take something like that on (plus I get soooo frustrated installing opensource software packages and the associated configuversionitis. it drives me nuts) The current website is an apache process that serves as a reverse proxy for the mailing list stuff (which also runs in apache), and OpenACS running in AOLServer. I think jo2y had RT running as well. The openacs version is a bit old, and is need of an upgrade (Which is why I haven't installed a wiki package for it yet). I haven't made the time to do the upgrade, which will be a PITA because of local customizations. One of the nice thing about OpenACS is that it has an integrated access control mechanism, making it easy to dub people as editors of particular parts of the site. I'm not adverse to adding something adjacent to OpenACS (like http://wplug.org/lists/) for a wiki or some similar thing - so long as there is some kind of access control. It's entirely too easy for a small organization's wiki to become completely covered in spam. This I think is the ideal short-to- medium term solution. Keeps me out of the loop since I know I'll be the bottleneck. If you'd (or anyone else) like to totally replace the system, that's fine. It currently runs out of Postgresql with a pretty rich data model, and I can dump things like the membership database and meeting schedule (which are the two primary uses of the database outside of the general site architecture). I'm a bit leery of grand plans, having survived two previous WPLUG efforts of building a grand system (first Lain, and then the zmanevand php monstrosity) - it was in the middle of the second one where I finally got tired and built the openacs based WPLUG website over a weekend, and the meetings module in another - it's been going now for about 4 years). But if you have the will to lead things, you've got my support (just not necessarily time :-) One thing I don't want to happen is to jettison a working system in favor of a new regime that never gets finished. Once there's a working development site somewhere, I'd be happy to throw the switch and hand the reins over. Cheers, ++Mark Dalrymple, markd at borkware.com "As I *am* getting older, here is my advice for the young ones on the list: Show up. Enjoy. Reflect. Love. Share. Forgive. Believe in the abundance. Do good work. Laugh. Learn." -- Aaron Hillegass From jo2y at midnightlinux.com Mon Jul 24 22:42:56 2006 From: jo2y at midnightlinux.com (James O'Kane) Date: Mon, 24 Jul 2006 19:42:56 -0700 (PDT) Subject: [wplug-web] Re: WPLUG Website In-Reply-To: <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> References: <44C3B617.7020200@nedyah.org> <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> Message-ID: [ keeping cc list intact ] On Mon, 24 Jul 2006, Mark Dalrymple wrote: > the mailing list stuff (which also runs in apache), and OpenACS running in > AOLServer. I think jo2y had RT running as well. >From memory, I setup mod_rewrite to do most of the work. If a request matched a small set of urls, /mailman, /~, etc, apache handled it as normal. If not, apache proxies everything else to port 8080(?) where OpenACS did its thing. Adding /wiki to that list should be straight forward for anyone familiar with apache config files. http://wiki.wplug.org/ could also be done without needing to interact with OpenACS. -james From eksortso at gmail.com Mon Jul 24 23:22:37 2006 From: eksortso at gmail.com (David Ostroske) Date: Mon, 24 Jul 2006 23:22:37 -0400 Subject: [wplug-web] Re: WPLUG Website In-Reply-To: References: <44C3B617.7020200@nedyah.org> <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> Message-ID: As far as minutes and whatnot goes, I could go with Mark's short-short-term suggestion, i.e. a shell login to the server. Someone would need to show me where and how to post files, though, so that I wouldn't break anything. I'm more keen on the idea of posting minutes to a wiki, but I would need to be able to lock the minutes pages, which by necessity must not be changed. Also, it would be good form to link the meeting page to the minutes, though we'd need to figure out how that would be done. Perhaps make a place for it in the meetings template? If we can start a wiki in parallel with the current working system (which you say would be feasible, James), if that's a viable option, then I'd cast my vote for that approach. But that's just my naive opinion at this point. There may be integration issues that I'm not seeing yet. Would we eventually want to make the wiki our new home, ultimately making it www.wplug.org? On 7/24/06, James O'Kane wrote: > [ keeping cc list intact ] > > On Mon, 24 Jul 2006, Mark Dalrymple wrote: > > > the mailing list stuff (which also runs in apache), and OpenACS running in > > AOLServer. I think jo2y had RT running as well. > > > >From memory, I setup mod_rewrite to do most of the work. If a request > matched a small set of urls, /mailman, /~, etc, apache handled > it as normal. If not, apache proxies everything else to port 8080(?) where > OpenACS did its thing. > > Adding /wiki to that list should be straight forward for anyone familiar > with apache config files. > > http://wiki.wplug.org/ could also be done without needing to > interact with OpenACS. > > -james > > _______________________________________________ > wplug-web mailing list > wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > -- David Ostroske From vkochend at nyx.net Tue Jul 25 00:18:42 2006 From: vkochend at nyx.net (Vance Kochenderfer) Date: Mon, 24 Jul 2006 22:18:42 -0600 (MDT) Subject: [wplug-web] Re: WPLUG Website In-Reply-To: <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> Message-ID: <200607250418.k6P4IgWf013212@nyx1.nyx.net> Mark Dalrymple wrote: > not necessarily time :-) One thing I don't want to happen is to > jettison a working system in favor of a new regime that never gets > finished. Once there's a working development site somewhere, I'd be It's absolutely right to be wary of switching over to something that may be half-baked. But I'm equally concerned that you and jo2y are (AFAIK) the only WPLUGers who know OpenACS, and your time is spoken for by The Collective. If we can get people up to speed on OpenACS to add the functionality we're looking for, great. I tried reading the documentation and was utterly baffled (which admittedly isn't too difficult to do). As I said on -plan, the server is going to be run by whatever volunteer labor we can scrounge up, so IMO the best CMS is "whatever everyone else is using." I'm also not too sure about bolting on MediaWiki and other services to the existing site, since that adds yet another access control system to keep current and more packages to maintain. That's one man's semi-informed opinion, anyway. Vance Kochenderfer | "Get me out of these ropes and into a vkochend at nyx.net | good belt of Scotch" -Nick Danger From vendicate at gmail.com Tue Jul 25 00:23:10 2006 From: vendicate at gmail.com (Bruno Pierri Galvao) Date: Tue, 25 Jul 2006 00:23:10 -0400 Subject: [wplug-web] Re: WPLUG Website In-Reply-To: <200607250418.k6P4IgWf013212@nyx1.nyx.net> References: <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> <200607250418.k6P4IgWf013212@nyx1.nyx.net> Message-ID: Alright, why no Tikiwiki? You can get it installed in 5 minutes, customized in 30 minutes, and has one central login system integrated with all the modules (forums, chat, blog, etcetera) User friendly, much involvment in development, great support, and most of all, "everyone uses it" --bruno On 7/25/06, Vance Kochenderfer wrote: > Mark Dalrymple wrote: > > not necessarily time :-) One thing I don't want to happen is to > > jettison a working system in favor of a new regime that never gets > > finished. Once there's a working development site somewhere, I'd be > > It's absolutely right to be wary of switching over to something > that may be half-baked. But I'm equally concerned that you and > jo2y are (AFAIK) the only WPLUGers who know OpenACS, and your time > is spoken for by The Collective. > > If we can get people up to speed on OpenACS to add the > functionality we're looking for, great. I tried reading the > documentation and was utterly baffled (which admittedly isn't too > difficult to do). > > As I said on -plan, the server is going to be run by whatever > volunteer labor we can scrounge up, so IMO the best CMS is > "whatever everyone else is using." > > I'm also not too sure about bolting on MediaWiki and other > services to the existing site, since that adds yet another access > control system to keep current and more packages to maintain. > > That's one man's semi-informed opinion, anyway. > > Vance Kochenderfer | "Get me out of these ropes and into a > vkochend at nyx.net | good belt of Scotch" -Nick Danger > _______________________________________________ > wplug-web mailing list > wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web > -- Bruno Pierri Galvao From wmoran at potentialtech.com Wed Jul 26 11:27:33 2006 From: wmoran at potentialtech.com (Bill Moran) Date: Wed, 26 Jul 2006 11:27:33 -0400 Subject: [wplug-web] Re: WPLUG Website In-Reply-To: References: <44C3B617.7020200@nedyah.org> <3B1314F5-9DB7-4A85-B23C-DF7326585D08@borkware.com> Message-ID: <20060726112733.03bbe149.wmoran@potentialtech.com> In response to "David Ostroske" : > As far as minutes and whatnot goes, I could go with Mark's > short-short-term suggestion, i.e. a shell login to the server. Someone > would need to show me where and how to post files, though, so that I > wouldn't break anything. > > I'm more keen on the idea of posting minutes to a wiki, but I would > need to be able to lock the minutes pages, which by necessity must not > be changed. Also, it would be good form to link the meeting page to > the minutes, though we'd need to figure out how that would be done. > Perhaps make a place for it in the meetings template? > > If we can start a wiki in parallel with the current working system > (which you say would be feasible, James), if that's a viable option, > then I'd cast my vote for that approach. Duncan and I had discussed this a bit. My idea was to put the wiki on the server in the ece machine room, and it can be wiki.wplug.org. Then we can migrate the rest of the system's functionality over at our leisure. Although our leisure seems to be entirely too leisurely. I've been kind of out of it on this for a bit. Last week I had a class. Two weeks ago was Toronto. This week is Confluence. Hopefully I'll end up with some free cycles starting next week. -- Bill Moran Collaborative Fusion Inc.