9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] RFC: 9zine
Date: Thu, 27 Mar 2008 17:19:07 +0100	[thread overview]
Message-ID: <20080327161907.GB13243@nibiru.local> (raw)
In-Reply-To: <89d4cb5faa89f9211713946601c469cb@csplan9.rit.edu>

* john@csplan9.rit.edu <john@csplan9.rit.edu> wrote:

> My concern with "ezines" is always that they don't have much to offer
> that you can't get through incremental updates to a blog.  I like
> getting real magazines and newsletters because you have the
> anticipation of waiting and end up with a nice stack of the old stuff
> to proudly display in your basement.  It's not a rational thing; I
> just think people prefer to have this kind of thing mailed, rather
> than downloading and printing it themselves.

So you're talking about an paper magazine ?
Interesting idea - already thought of this :)

If articles are written in some suitable format (eg. TeX), we could
at least parts of it automatically :)

Well, I'm actually not an confident layouter/typesetter. I could hire
an old friend (for a good price), but this first needs a budget.
So we first should have to make clear, how "nice" the layout should
be (eg. simplicistic scientific paper vs. typical hi-quality paper
print like Linux-Mag ;-)), how many print exemplars and how much
people are willing to pay.

My idea was to start with an (simple) ezine and let it grow, print
magazine would be the next step.

> If said...  magazine (I hate the word 'zine') is interesting enough,

... well, the word "9zine" would sound nice, IMHO ;-)

> say, with new papers and editorials from people who actually know
> something about Plan 9, I'd print it out and read it.  There are some
> really great things being done with Plan 9 by some really smart
> people; I won't put myself in that class but I could probably put out
> an article or two myself.

If it's just an collection of papers, w/o much layout, it shouldn't
be that hard job (eg. w/ TeX).

> If it turns out to be "Enrico and Pietro propose 10 new synthetic
> filesystems they'll never build", well, I can read that on 9fans and

Hey, hey, I'm really building my suggested FS'es ... I just want to
get more people into an open specification process before actually
coding ;-O


cu
--
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------


  reply	other threads:[~2008-03-27 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  0:04 Enrico Weigelt
2008-03-27  0:58 ` Pietro Gagliardi
2008-03-27  1:14 ` Tom Lieber
2008-03-27  5:24   ` Harri Haataja
2008-03-27 15:46     ` john
2008-03-27 16:19       ` Enrico Weigelt [this message]
2008-03-27 20:07       ` Harri Haataja
2008-03-27 15:53     ` Enrico Weigelt

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=20080327161907.GB13243@nibiru.local \
    --to=weigelt@metux.de \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).