I have given it some more thought this morning and the more I think about it the more I like it.
You can even share interim results -- so have multiple stages, taking snapshots as required. If I can't get to a certain point, I can still carry on with the group without holding them up. In additional, after the workshop I can retry as many times as I want with known starting points and try different variations. Given the presenters desires and comfort level, you could cover more than one distro. It would be nice to see everyone be comfortable with the whatever distro then come in with given time and experience. Has anyone thought of an appropriate topic or range of topics that might interest people? jon wrote: > I second the VM thing. Not only does it allow for a quick start at the > workshop, it's entirely possible to use the resulting VM as is at home > or at work once it's built for its intended purpose. > > I suspect it puts a little more work onto the presenter to have a VM > available for distribution at workshop time, but over time an archive of > VMs at various start and end states can accumulate. That would also add > to Kin's idea of archiving the data for repetition - the VMs can be > archived as well. > > J > > Shawn wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I like the VM idea. I think that would go a LONG way to making things >> work within a given standard. This is probably the best solution. >> >> As for distros, if the work shop is for Postfix, the distro is more or >> less irrelevant - except for getting Postfix and/or any support modules >> installed. It *should* be reasonable to expect that someone will be >> familiar with their distro of choice to partake of the workshop. >> >> Yes, there are exceptions to this. But, in my eyes what you are looking >> for is that everyone be driving the same brand and model of car - even >> if the lesson is on how to change a tire. (and yes that IS very very >> much an oversimplification.. :) >> >> but I think the VM idea solves everything nicely. The planner can set >> up the VM as needed, distribute it, and continue with the lesson. >> >> My thoughts. >> >> Shawn >> >> Kin C Wong wrote: >> >>> Really good point regarding VMs, this is something that was not >>> available a year ago (as readily). This actually can lead to two types >>> of workshops, one which is more of an overview and follow along at a >>> faster clip and a hands-on type of workshop where you could bring in >>> your gear. In the first scenario, you wouldn't necessarily even need a >>> Linux box (not recommended, you get a lots of friendly ribbing) and in >>> the second scenario - one or more distro is possible. >>> >>> With regards to more advance topics, the first scenario is likely all >>> that is required. >>> >>> Gustin Johnson wrote: >>> 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 >>>>>> >>>>>> >> _______________________________________________ >> 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.3 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iD8DBQFFuH5NMia5XCIAQC8RAut3AJ9jBBnpEjjPsZsWmXyTAOhypjxWSACfWPEe >> w/c9Ug+hnT+fMogli+2R4NA= >> =/6i3 >> -----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 >> > > _______________________________________________ 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
