
Wednesday May 04, 2005
notes about content
some notes about this blog content [also answering some questions
that came up recently]
copyright: all text in my blog entries are covered under
a creative commons
attribution-noncommercial-noderivs
license. [i do not care for the poorly designed by-nc-nd logo, so it is not
displayed
here.]
photography: unless i note otherwise, all photographs on my blog entries are
my work, either scanned from my slide images, or recently made with a nikon
d100 or d70. if asked, i would consider providing high-resolution versions
of these images for not-for-profit uses. i do sell art prints from
time to time.
books: i talk a lot about books in this blog, but only about books i have in
my
library and have read, have been reading, or have skimmed
[sometimes called pre-reading] in some detail.
[alas, too many good books, not enough
time.]
links: all my book links go to barnes & noble in the US. this is not because
i care
more about b&n (i do not), but because everyone seems to link to amazon out of inertia,
which annoys me. i am not convinced amazon deserves the strange free ride
it has been getting through reviews, lists and links as if it was a national
public library.
music: all recommended music is from my admittedly limited cd library;
jazz and classical tends to be dominant. [as i am writing this, i am
listening to a track from nicholas payton's gumbo nouveau]
name: the blog username is plan9 which probably looks odd. i wish it was
oz
but that was taken. yes i do run plan9 at my home lab. [badly needs an
upgrade] alas, i do not do much development with plan9. [i once wrote a haiku
about plan9 on my vaio.]
poetry: i am quite serious about haiku [eg.
basho entry] but (with few exceptions) much less serious about western
poetry. poets are always tempted to say too much -- lee gurga
[many programmers are like poets]
case: as may be obvious, i intensely dislike uppercase. i will use them where
i have to,
eg. in formal
writing, but in my blog space, anything i have to type is lowercase only.
misc: this blog content is revision controlled.
i use bitkeeper
and i have a real license. i believe
in using the best tools i can efford for the job, not the second or third
best tool. [cvs is to source code control as horse and buggy are to
transportation -- anon]
(2005-05-04 12:14:29.0)
Permalink
must read: innovation happens elsewhere
goldman and gabriel's new book
innovation happens elsewhere: open source as business strategy is now available.
i hope it will be widely read in the industry. [i do not have a copy yet, but soon]
here is the table of
contents (excluding appendices):
Introduction
Open Source: A Different Way Of Doing Business /
Innovation Happens Elsewhere /
Jumping In /
Understanding Open Source /
Communities /
Who This Book Is Intended For /
Who Else This Book Is Intended For
Innovation Happens Elsewhere
Open Source Is A Commons /
Can The Commons Make A Difference? /
The Commons And Software /
Open Versus Closed /
Use Of The Commons: Creativity & Conversations /
Innovation Happens Elsewhere
What Is Open Source?
Open Source In Brief /
Philosophical Tenets Of Open Source /
Open Source And Agile Methodologies /
Common Open Source Myths, Misconceptions & Questions /
Open Source And Community /
The Secret Of Why Open Source Works /
Variations On Open Source: Gated Communities And Internal Open Source /
Open Source: Why Do They Do It?
Why Consider Open Source?
Business Reasons For Choosing To Open Source Your Code /
Creating Your Business Model And Following Through With It /
Measuring Success /
An Example: The Innovation Happens Elsewhere Strategy /
Business Reasons For Using Open Source Products
Licenses
What The License Does /
What The License Does Not Do /
More On Copyright /
And A Quick Word On Patents /
The Licenses /
Dual Licensing /
Supplementing The License?Contributor Agreements /
Licenses For Documentation
How To Do Open Source Development
The Infrastructure Needed For An Open Source Project /
Software Lifecycle /
Building A Community /
Ending An Open Source Project /
Joining An Existing Open Source Project /
Open Source Within A Company
Going With Open Source
Deciding To Do Open Source /
How To Prepare To Do Open Source At Your Company /
Getting Approval From Your Company /
Problems You Can Expect To Encounter
How To Build Momentum
Marketing Your Project /
Focus On Your Users And Contributors /
Community Outreach /
Harvesting Innovation /
Welcome The Unexpected
What To Avoid Known Problems And Failures
Not Understanding Open Source /
Don't Needlessly Duplicate An Existing Effort /
Licensing Issues /
Design Issues /
Code Issues /
Trying To Control Too Much /
Marketing Issues /
Tension Between An Open Source Project And The Rest Of Your Company /
Community Issues /
Lack Of Resources /
Recovering From Mistakes
Closing Thoughts
[musical recommendation: tbd]
(2005-05-03 21:29:16.0)
Permalink