All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: Tejun Heo <htejun@gmail.com>, Alan <alan@lxorguk.ukuu.org.uk>,
	Albert Lee <albertcc@tw.ibm.com>
Subject: linux-ata.org contributions
Date: Sat, 10 Nov 2007 17:10:43 -0500	[thread overview]
Message-ID: <47362C63.7080108@garzik.org> (raw)

(cc'd to main potential content contributors)

What do you guys think about a git tree for linux-ata.org web pages, 
rather than a wiki?  A git tree would be my preference.

Whenever you want to update or add a page, just send a 'git pull' 
request to me...

As I noted to Tejun in IRC, the main caveat towards contributing to 
linux-ata.org -- in any fashion, git or wiki or whatever -- is that I 
would like to continue to have google adsense ads there.  They help pay 
for the non-Red Hat dedicated server that handles these web pages.

Additional disclosures follow, so that you may align or avoid as your 
ethics dictates...

Disclosure #1:  income from linux-ata.org: Aug US$31, Sep US$38, Oct US$37

Disclosure #2:  the dedicated server in question also handles my email 
(which is intentionally not on Red Hat machines) and other sites like 
linux.yyz.us.

Disclosure #3:  All this is done under the copyright and onus of 
"Dunvegan Media, Inc." which is really me and nobody else.  The company 
was started to put a corporate face on the lulu.com and AdSense stuff, 
and to give myself practice at running a business.  It also does a bit 
of email and DNS hosting for some friends, but the vast majority of 
usage is my linux stuff.  The company has always been [if only slightly] 
cash flow negative, so its not like I'm getting rich off this.  :)

	Jeff



             reply	other threads:[~2007-11-10 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10 22:10 Jeff Garzik [this message]
2007-11-10 22:11 ` linux-ata.org contributions Jeff Garzik
2007-11-10 23:03   ` Alan Cox
2007-11-10 23:06     ` Jeff Garzik
2007-11-10 23:10       ` Alan Cox
2007-11-11 15:41       ` James Andrewartha
2007-11-12  1:18       ` Tejun Heo
2007-11-12  1:57         ` Jeff Garzik
2007-11-12  2:01           ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47362C63.7080108@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertcc@tw.ibm.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.