-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My take on this is that we are talking about a pre-defined default for a presentation. So, something like "Apache Performance Tuning with Debian stable". Other distros are welcome but the examples, documentation and "expertise" will be Debian centric.
I also expect this to be driven by the lead team for this particular workshop, especially if there is prepared material (prebuilt VMs, handouts, etc.). Kevin Anderson wrote: > Standard distro is hard to define. That would be my only comment. > > IS RH a standard? I think we'd all say yes, but that that include > Fedora and/or CentOS? > Standard or not, will anyone support Novell? :) > Is Debian the standard or is *buntu? That's becoming a difficult > question. > > And the real kicker, is even if we say RH is the standard, does that > mean with Gnome? That's the default. Is vi the standard, or vim, or > nano, or emacs, or Microsoft word? If I do Scalix, do I do it with > postfix or sendmail? Sendmail is the standard for Scalix, but not for > almost any distro anymore. (Both work fine). > > "Standard Distro" is just going to be VERY difficult to define. > > Kev. > > -----Original Message----- > From: Kin C Wong [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 25, 2007 12:01 AM > To: CLUG General > Subject: [clug-talk] Workshop plans > > I had a chat with Dave on Monday as I reminisce over the workshops that > we had in the good old days (only about a year ago) -- I would like to > resurrect that but am incapable of doing it alone as many of you might > also feel. I think it might be worthwhile as a team project - to be > able to learn in a small team and to deliver in a bigger environment. > > In my mind the following components will be required: > > time > knowledge and the willingness to share that knowledge ability to > transfer knowledge an interesting topic > > I know many of you have many aspects required but very few have them all > -- however as a group, I am sure that we could pull something like this > off. > > Purpose of the whole exercise, build a legacy -- something that could be > run by someone who is willing without all the skills that is willing to > share and move Clug forward. > > Stage 1 -- anyone else thinks this might be a good idea and have a bit > of time and effort to donate > > Stage 2 -- identification of a topic that might be of interest to a > group > > Stage 3 -- get together to design a mini-workshop > > Stage 4 -- document and delivery of that knowledge to a small group > > Stage 5 -- file away so that someone can repeat the exercise in a years > time for the next wave of Linux adopters > > I know this will be a sore point with some -- I insist on the use of a > standard distro. I know we all have our favourites but too have a high > level of success and good participation, I think this is something that > we need to adopt in the beginning. The time for experimentation is > after we got it working and we get more experts involved. The past of > workshop would also be that much quicker. > > Just my 2 pesos. > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > > > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuGyKwRXgH3rKGfMRAvbbAJ9jCciTqqtSGGA/XdxaikB0ivDF+ACfeQBf kVln6QD7HIjTbrEbcGeuExI= =gj1p -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
