From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 Sources Repository
Date: Sat, 19 Jul 2014 17:49:20 +0200 [thread overview]
Message-ID: <d010c8c196ad53582c7cd36fe3a3aa94@posteo.de> (raw)
In-Reply-To: <CAB8pEY5ef-dYk+YAS_wsCa3P-wsxgEt35JAhUD2zMnqsU-=GcA@mail.gmail.com>
Usable, not bureaucratic.
And you don't need to invest work.
Just use it if you like it.
Take a look at how it works now. Is this OK with you?
1. "/n/sources/contrib/fgb/root/rc/bin/contrib/install fgb/contrib"
Why do I need to know about "fgb", why not
"/n/sources/packages/contrib/rc/bin/contrib/install contrib ?
2. bichued/hg -- 1.0.2
jas/hg-src
mjl/hgfs
stallion/mercurial -- 2.2.3
Which one now?
3. What about
http://www.plan9.bell-labs.com/wiki/plan9/software_for_Plan_9/ ?
What about the broken links there?
Can we still save that software?
Archive.org?
Regards,
Dante
P.S. I knew that I will receive a certain amount of
conservative/negative answers for questioning the Status Quo.
I also got some very helpful ones, see Eric.
Maybe this is the right moment to ask such questions.
For years, Plan9 was hard to install on common hardware, lacking
drivers (I tried more than once and failed).
This all changed with Raspberry Pi.
There is a good, stable (in the medium/long term) platform that
costs next to nothing for people to play with Plan9.
The core system is very elegant and flexible.
Yet, I have the impression that some potential users may be put
off by the lack of polish in some other places (installer, ports etc.).
These potential users are also potential contributors.
More mass could mean:
- having a useable (like useable in 2014) Web browser
- having a useable (or having one at all) video/media player
- having an SSH2 server (there is one in 9atom, but I didn't see
it in the stock Plan9). Are you sure it doesn't have the Heartbleed?
- having a useable driver for touch pads or 2-button-plus-wheel
mice. I couldn't find a 3-button mouse these days, and clicking on the
wheel is awful.
- up-to-date versions of modern programming languages. I miss
Ruby a lot.
Wouldn't that be nice?
8D
On 19.07.2014 17:11, Jacob Todd wrote:
> Are you intentionally trying to make plan bureaucratic?
next prev parent reply other threads:[~2014-07-19 15:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 13:19 dante
2014-07-18 14:14 ` Aram Hăvărneanu
2014-07-18 14:18 ` cam
2014-07-18 14:36 ` erik quanstrom
2014-07-19 9:31 ` dante
2014-07-19 11:20 ` Riddler
2014-07-19 11:50 ` dante
2014-07-19 11:49 ` pmarin
2014-07-19 11:51 ` dante
2014-07-19 12:02 ` dante
2014-07-19 19:06 ` Anthony Sorace
2014-07-20 0:12 ` Brian L. Stuart
2014-07-20 7:33 ` dante
2014-07-19 12:03 ` tlaronde
2014-07-19 12:12 ` dante
2014-07-19 14:41 ` erik quanstrom
2014-07-19 15:06 ` dante
2014-07-19 15:11 ` Jacob Todd
2014-07-19 15:49 ` dante [this message]
2014-07-19 18:00 ` Kurt H Maier
2014-07-19 23:19 ` Brian L. Stuart
2014-07-19 18:17 ` erik quanstrom
2014-07-19 19:20 ` Christopher Nielsen
2014-07-19 20:13 ` Aram Hăvărneanu
2014-07-19 22:10 ` dante
2014-07-19 22:30 ` erik quanstrom
2014-07-20 7:33 ` dante
2014-07-19 22:54 ` Brian L. Stuart
2014-07-19 17:31 ` hiro
2014-07-19 17:48 ` dante
2014-07-19 15:03 ` Aram Hăvărneanu
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=d010c8c196ad53582c7cd36fe3a3aa94@posteo.de \
--to=subscriptions@posteo.eu \
--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).