From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: AW: [9fans] p9f mention of 9front
Date: Thu, 24 Jun 2021 15:01:06 +0000 (UTC) [thread overview]
Message-ID: <6a6c938d-226d-4286-a68c-346718aa70cc@sirjofri.de> (raw)
In-Reply-To: <CAFSF3XPzKMikiYeNe3r+YUUFE+rjXb3iqUN0V2XjVTsnSbb0dQ@mail.gmail.com>
Hello all,
Klong mail incoming. I hope my English is ok and I don't tread on other's
toes.)
from my perspective it looks like this:
There are multiple Plan 9 forks kor distributions). They all are
philosophically and technically different, but they still share patches
(even if many people don't know). This is fine.
It would be great to have some kind of compatibility. i'm not necessarily
talking about binary/ABI compatibility, but network compatibility, shell
scripting and usability. People are actively working on it. I personally
have no reason to run 9legacy in my network since 9front has everything I
need, but other people do.
The community is split into multiple different areas. Some areas are open
to communicate with others, some actively work together and some are very
"unique": you don't really hear from them in most channels, besides some
email here and there, but that's it.
I can name #cat-v, #plan9, ##9fans (bridged to discord) and the 9fans and
9front mailing lists.
P9f is some very special case: They have the rights to the original
codebase, they stare noble goals, but they seem to actively hide the fact
that 9front exists. Hardcore 9front people don't really care about that,
but the community (and I) do. I consider it really sad that 9front seems
so cut away from the Plan 9 history just because some people try to hide
it. Many people asked about mentioning 9front on the p9f page.
When p9f started they told us that they focus on more important stuff
first (which I can totally understand). Some activities (also mentioned
at 9front.org/who/p9f) make me think that they just don't want 9front to
exist.
They state they want to push all stuff in the plan 9 family (9p, plan9
with forks, inferno), but they seem to actively promote 9legacy (which is
fine, it's the most original continuation of plan9) and hide 9front
(which is just sad). This is especially sad since 9front is probably the
most modern and most active Plan 9 system currently existing.
I just hope we all find a way to still respect each other and to grow as
a community. Misunderstandings happen as well as lots of other human
factors.
My long 2 cents
sirjofri
Disclaimer: I actively used the original Plan 9 4e, Plan 9 on rpi,
inferno, and I am an active 9front user.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T523d6e906a17a7cc-M0a6e0197e217adff3f184fd7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-24 15:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 19:11 hiro
2021-06-23 23:05 ` unobe
2021-06-23 23:35 ` Sigrid Solveig Haflínudóttir
2021-06-23 23:58 ` Romano
2021-06-24 4:06 ` Lucio De Re
2021-06-24 4:56 ` unobe
2021-06-24 5:52 ` Lucio De Re
2021-06-24 21:25 ` Wes Kussmaul
2021-06-24 23:29 ` silas poulson
2021-06-25 13:06 ` Wes Kussmaul
2021-06-24 8:24 ` Frank D. Engel, Jr.
2021-06-24 9:25 ` [9fans] plan9 and touch screens Richard Miller
2021-06-24 9:59 ` Lucio De Re
2021-06-24 10:12 ` [9fans] p9f mention of 9front Philip Silva via 9fans
2021-06-24 16:05 ` unobe
2021-06-24 16:16 ` Ethan Gardener
2021-06-24 11:19 ` hiro
2021-06-24 15:01 ` sirjofri [this message]
2021-06-24 20:51 ` unobe
2021-06-25 8:28 ` Steve Simon
2021-06-25 9:31 ` Richard Miller
2021-06-25 12:41 ` [9fans] full fossil follies Richard Miller
2021-06-25 14:12 ` adr via 9fans
2021-06-25 15:17 ` tlaronde
2021-06-25 16:06 ` adr via 9fans
2021-06-25 16:45 ` adr via 9fans
2021-06-26 9:01 ` Ethan Gardener
2021-06-25 17:23 ` Iruatã Souza
2021-06-26 8:56 ` Richard Miller
2021-06-26 8:34 ` [9fans] p9f mention of 9front Ethan Gardener
2021-06-26 12:55 ` noam
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=6a6c938d-226d-4286-a68c-346718aa70cc@sirjofri.de \
--to=sirjofri+ml-9fans@sirjofri.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).