Then maybe we should go in that direction. Give a five minute explanation about what linux is and where it came from and then talk about what a distribution is and the companies that make them. Then go on to talk about why you'd want to use linux (stability, resilience to viruses, breathing life into old hardware, etc.) Then take the remaining 15 minutes to show off the interface, mozilla, evolution, xmms and gnumoney. Then finish up with a blurb about WLUG (who, what, where and when). Does that sound sensible? Tim. -----Original Message----- From: Stephen C. Daukas [mailto:stephen@daukas.com] Sent: Monday, November 10, 2003 5:40 PM To: Worcester Linux Users Group Subject: Re: [Wlug] W.L.U.G. TV show... I have a few thoughts to offer... Given the format of Community Access Programming on local cable, you have 30 minutes. Period. (At least in Shrewsbury.) If my experience in the past with these productions holds true, you don't have a lot of time to work with and it is very rare to see a multi part show, even from long established programming. (Never mind the editing and work that goes on behind the scences - 30 minutes translates into weeks of work.) 30 minutes isn't a lot of time. Even a high school class is 47 minutes these days, and that gets you one topic, say for example, work = force x distance. There will not be time enough to adress more than once audience, or more than one simple topic for that matter! If you are about to say "but wait, we don't have to limit ourselves to 30 minutes, we can produce what we want" then I would answer, that's true! But, just as true is my next question - who you gonna show it to and how? So, now that we have established the cart and the horse, we need to make a few decisions... I'm thinking that 30 minutes is just enough time (barely) to show a "teaser" piece that talks about Linux "the product" and what it can do. No techno-geek talk (because you will invariable try to cover too much in too little time), just something that will interest the audience enough to want more. 30 minutes is just enough time to show everyone how they can configure a Linux server to support their own real estate business or construction business or oil business or... as well as interest the experienced novice who might want to try getting out from under their ISP. When they want more, then you can talk about follow-up episodes, or direct them to WLUG at the end of the episode (or both). The WLUG site could have video available, metting topics, and so forth... Steve _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Yes, but I think we might be able to get a bit more in... What you describe could be scripted to take less time, depending on the goals... We could do the overview in tandem with configuration work taking place and "check in" with that progress during the show. After 20 minutes or so, show a completely configured running system/server and then hit them with "if you want to know more..." Good? Bad? Keller, Tim wrote:
Then maybe we should go in that direction. Give a five minute explanation about what linux is and where it came from and then talk about what a distribution is and the companies that make them.
Then go on to talk about why you'd want to use linux (stability, resilience to viruses, breathing life into old hardware, etc.)
Then take the remaining 15 minutes to show off the interface, mozilla, evolution, xmms and gnumoney.
Then finish up with a blurb about WLUG (who, what, where and when).
Does that sound sensible?
Tim.
-----Original Message----- From: Stephen C. Daukas [mailto:stephen@daukas.com] Sent: Monday, November 10, 2003 5:40 PM To: Worcester Linux Users Group Subject: Re: [Wlug] W.L.U.G. TV show...
I have a few thoughts to offer...
Given the format of Community Access Programming on local cable, you have 30 minutes. Period. (At least in Shrewsbury.) If my experience in the past with these productions holds true, you don't have a lot of time to work with and it is very rare to see a multi part show, even from long established programming. (Never mind the editing and work that goes on behind the scences - 30 minutes translates into weeks of work.)
30 minutes isn't a lot of time. Even a high school class is 47 minutes these days, and that gets you one topic, say for example, work = force x distance. There will not be time enough to adress more than once audience, or more than one simple topic for that matter!
If you are about to say "but wait, we don't have to limit ourselves to 30 minutes, we can produce what we want" then I would answer, that's true! But, just as true is my next question - who you gonna show it to and how?
So, now that we have established the cart and the horse, we need to make a few decisions...
I'm thinking that 30 minutes is just enough time (barely) to show a "teaser" piece that talks about Linux "the product" and what it can do. No techno-geek talk (because you will invariable try to cover too much in too little time), just something that will interest the audience enough to want more. 30 minutes is just enough time to show everyone how they can configure a Linux server to support their own real estate business or construction business or oil business or... as well as interest the experienced novice who might want to try getting out from under their ISP.
When they want more, then you can talk about follow-up episodes, or direct them to WLUG at the end of the episode (or both). The WLUG site could have video available, metting topics, and so forth...
Steve
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Stephen C. Daukas - stephen@daukas.com - http://daukas.com/
At 11/13/2003 04:51 PM (Thursday), Stephen C. Daukas wrote:
Yes, but I think we might be able to get a bit more in... What you describe could be scripted to take less time, depending on the goals... We could do the overview in tandem with configuration work taking place and "check in" with that progress during the show. After 20 minutes or so, show a completely configured running system/server and then hit them with "if you want to know more..."
Good? Bad?
Generally not a good idea. One basic mistake often made when designing a new production like this is to try to pack too much into one session. Similar to a teacher trying to cover too much material in one class. You generally end up losing everyone - just in different ways and a different times. Better to have one intro show as already described and then a second show which walks through a complete sample install process. This show would display the machine's screen as someone talks the viewer through what he is seeing.
I agree. In fact, I made the same point in my first post. What I was trying to suggest was that while the intro stuff was taking place as usual, reference could be made periodically to a configuration taking place in the background. Not syaing how to do it, but that it is being done during the show. The point here is subtle, but powerful... in the time it takes someone to watch the intro show, someone who gets with WLUG/watches other WLUG shows would be able to configure a complete system in a short period of time... Doug Chamberlin wrote:
At 11/13/2003 04:51 PM (Thursday), Stephen C. Daukas wrote:
Yes, but I think we might be able to get a bit more in... What you describe could be scripted to take less time, depending on the goals... We could do the overview in tandem with configuration work taking place and "check in" with that progress during the show. After 20 minutes or so, show a completely configured running system/server and then hit them with "if you want to know more..."
Good? Bad?
Generally not a good idea. One basic mistake often made when designing a new production like this is to try to pack too much into one session. Similar to a teacher trying to cover too much material in one class. You generally end up losing everyone - just in different ways and a different times.
Better to have one intro show as already described and then a second show which walks through a complete sample install process. This show would display the machine's screen as someone talks the viewer through what he is seeing.
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Stephen C. Daukas - stephen@daukas.com - http://daukas.com/
Hi all, I have configured my INternet Gateway using ipchains by implementing the MASQ connection on some defined port in order to enable the internet connection for my client. Finally, I got this bellow message: ftp> ls -l 502 Illegal PORT Command 150 Opening ASCII mode data connection for directory listing. How can it be like that ? Login was successfull, but I permitted nothing to run the command. Can you help me ? Browsing, receiving and sending mail, etc are working fine. Except this one, using ftp. For FTP Setting , this is my ipchains settings : # FTP ipchains -I forward -s 192.168.21.0/24 -d 0/0 20 -j MASQ -p tcp ipchains -I forward -s 192.168.21.0/24 -d 0/0 20 -j MASQ -p udp ipchains -I forward -s 192.168.21.0/24 -d 0/0 21 -j MASQ -p tcp ipchains -I forward -s 192.168.21.0/24 -d 0/0 21 -j MASQ -p udp ipchains -I forward -s 192.168.21.0/24 -d 0/0 69 -j MASQ -p tcp ipchains -I forward -s 192.168.21.0/24 -d 0/0 69 -j MASQ -p udp ipchains -I forward -s 192.168.21.0/24 -d 0/0 115 -j MASQ -p tcp ipchains -I forward -s 192.168.21.0/24 -d 0/0 115 -j MASQ -p udp ipchains -I forward -s 192.168.21.0/24 -d 0/0 2431 -j MASQ -p tcp ipchains -I forward -s 192.168.21.0/24 -d 0/0 2431 -j MASQ -p udp Thanks. Aramico
participants (4)
-
Aramico -
Doug Chamberlin -
Keller, Tim -
Stephen C. Daukas