[NTLUG:Discuss] linux newbie manual

[micky hotmail]

Yeah, I wasn't thinking that much money could be made publishing.  I have
just seen those Linux white papers books around, which contain the same
white papers that are available online.  But just in case this takes off....
:)

I sent an e-mail to linuxnewbies, i'll also check out sourceforge also
(though i thought that was just for program development; i guess i have more
to learn about what's available in the linux community!).

I'm fine with the idea of just putting a link for now.  i put dates on my
site to keep track of progress and any issues that might come up.

I'm going to try to get some people involved from nylug (New york city linux
users group), because their list is one of the more active ones in the US
(though surprisingly, ntlug is the most active list i've seen so far!).  The
way i see it, the more people involved, the better.

I'll contact the people you mentioned, and see what they think.  Thanks for
your input Chris, this has really helped steer me in the right direction.
-Micky
----- Original Message -----
From: "Chris Cox" <cjcox at acm.org>
To: <discuss at ntlug.org>
Sent: Thursday, March 07, 2002 3:35 PM
Subject: Re: [NTLUG:Discuss] linux newbie manual


> micky hotmail wrote:
>
> >Brian and everyone,
> >I will license this under free license.  I want to post this on ntlug's
> >site, and also on www.linuxnewbie.org, if I get their permission.  Can we
> >license it before it's finished?  If so, I'll do that right now.  I do
> >understand the awkwardness of hosting it on a coorporate training site,
so
> >if i get permission, i would really like to put in on ntlug's site as
soon
> >as possible.  But if noone really cares, then we'll just leave it on PD's
> >site.
> >
> I think we can put a link somewhere on ntlug.org.  I think as far as
> hosting the actual
> pages, I'll need board approval since it could bring complications
> depending upon
> the popularity of the pages (of course we have hosted Chris Browne's
> pages for so long...
> I guess it really doesn't matter).  ... so I'm guessing that we can make
> this happen.
> We can certainly link to it first and then get something set up on the
> server later.
>
> >
> >Because this will be a free license documentation, i'm always looking for
> >other places where we may submit this material for internet and
non-internet
> >postings.
> >
> I'd like you also to talk to Dennis Rice who is heading up our new NTLUG
> Training
> arm (drice at dal.devry.edu ... he probably has a home email.. I just
> couldn't locate
> it).  We can look at setting up a mail list or a newsgroup to handle
> stuff.  However,
> if this has broader reach... probably should go to sourceforge or that GNU
> collaboration site (the name elludes me right now).... you'll have more
> visibility
> as well for the project (I think?).
>
> >
> >When, and not if, I start publishing this in book form, I want to donate
the
> >profits to ntlug and their operations.  I have no need for profits gained
> >from publishing this, as I will be using it myself to teach Linux
classes.
> >This project started out as a hobby, as I was tutoring some friends from
> >Rockwall, TX in Linux administration to pass the now-bankrupt (and
possible
> >illegitimate) company called linuxgruven.  I was going to be giving them
the
> >manual to help improve their teaching materials, which were very hard to
> >understand.  But since their business practices were ethically
questionable,
> >and I am affiliated with another company, I have no desire to do so.
> >I updated the website to address all these concerns:
> >http://www.prodirections.com/linux
> >
> I doubt you'll make too much since the publication is available for
> free... hopefully
> "the money" is not a prime motivator.  Some publishing companies may
> give you some
> grief about publising because of this as well... you may want to
> research some
> companies on that... I guess O'Reilley has published some in the past...
> but if you've
> ever dealt with publishers before you'll know that they like to OWN
> every word
> printed.
>
> >