9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Don Bailey <don.bailey@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]
Date: Thu, 25 Jan 2024 12:22:30 -0500	[thread overview]
Message-ID: <CAL_X0tDt9UmTXTNtf+OX0YVnxe7ptJ5F1sdAfwKrDpUuJUMmfQ@mail.gmail.com> (raw)
In-Reply-To: <7e4d32d6-6b75-47d9-9547-e46a0943845e@posixcafe.org>

[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]

Sounds like you're happy keeping 9front separate from "mainline", then.
Works for me :-)



On Thu, Jan 25, 2024 at 12:20 PM Jacob Moody <moody@posixcafe.org> wrote:

> On 1/25/24 09:35, Don Bailey wrote:
> > Direction comes from people writing code... but you write code for
> 9front, yes? What does that have to do with mainline Plan 9? And what does
> that have to do with the direction set forth by the people that actually
> designed it?
> 
> There is no "path for patches" in 9legacy, if I wanted to write code for
> "mainline Plan 9" who do
> I send to code to? Who is going to help review and bug test my code. You
> mentioned earlier that
> you had ported Plan 9 to other systems, is that code available anywhere,
> was that upstreamed into
> "mainline Plan 9". 9front happened, as Ori stated, because there was no
> path forward with "mainline
> Plan 9".
> 
> When I looked in to Plan 9 some 5ish years ago and looking at both camps
> of folks it was clear to me
> that one group was going to look at my patches, work on my hardware, and
> had an active community.
> 
> If y'all wanted to set up a pipeline for patches, encourage folks to send
> in their patches and make
> some repo for folks to work on then yeah sure. But right now there really
> isn't a comparison between
> what "mainline plan 9" is and 9front, one is a museum and the other is a
> living distribution. There is
> of course Miller's branch, which I respect as being active and actually
> usable, but I have a feeling you
> don't consider that "mainline plan 9" either.
> 
> Look man, be the change you want to see in the world, setup the repo,
> review patches, merge new code, et
> all. Getting mad at us for writing the code and keeping stuff working is a
> bit silly, especially if your
> only reason is that we aren't the "blessed few". Those folks as far as I
> can tell are not interested in
> this anymore, we're on our own here. There are clearly some folks
> interested here in continuing "mainline
> plan 9" why not work together and get something that is easier for folks
> to use? 9front will continue to
> be over here with a ten year plus head start.
> 
> - moody
> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42f11e0265bcfa18-M4b5f9413c29bdca94e2f565f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3850 bytes --]

  reply	other threads:[~2024-01-25 17:22 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 15:47 [9fans] Supported Notebooks alex-ml
2024-01-24 16:07 ` David Leimbach via 9fans
2024-01-24 17:11 ` Don Bailey
2024-01-24 18:09 ` Jacob Moody
2024-01-24 20:28   ` Michael Grunditz
2024-01-24 20:48     ` Jacob Moody
2024-01-24 14:27       ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] vic.thacker
2024-01-24 23:42         ` [9fans] Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community noam
2024-01-25  0:01           ` Lucas Francesco
2024-01-25  1:01         ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Don Bailey
2024-01-24 16:32           ` vic.thacker
2024-01-25  1:53             ` Don A. Bailey
2024-01-25  2:09               ` Jacob Moody
2024-01-25  2:23               ` Kurt H Maier via 9fans
2024-01-25  3:49                 ` Don A. Bailey
2024-01-25  6:38                   ` Kurt H Maier via 9fans
2024-01-25  2:42               ` Alex Musolino
2024-01-25  3:13                 ` Noam Preil
2024-01-25 14:10               ` hiro via 9fans
2024-01-25 16:44                 ` Don Bailey
2024-01-25 16:53                   ` Jacob Moody
2024-01-25 18:18                     ` Don Bailey
2024-01-25 17:07                   ` Kurt H Maier via 9fans
2024-01-25 17:10                     ` Don Bailey
2024-01-25 17:24                   ` Bakul Shah
2024-01-25 17:31                     ` Don Bailey
2024-01-25 18:00                       ` thedaemon via 9fans
2024-01-25 18:17                         ` Don Bailey
2024-01-25 19:43                           ` Eli Cohen
2024-01-25 21:17                             ` Don A. Bailey
2024-01-25 18:14                   ` Michael Misch
2024-01-25 18:21                     ` Re[2]: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was: " Alexandr Babic
2024-01-25 21:16                     ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: " Don A. Bailey
2024-01-25 18:42                   ` noam
2024-01-25 20:14                   ` ori
2024-01-26  4:08                   ` hiro
2024-01-25 20:37               ` ori
2024-01-25 21:09                 ` [9fans] P9F meetings (was: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community) David Arnold
2024-01-25 21:23                   ` ori
2024-01-25 22:31                   ` Don A. Bailey
2024-01-25 22:03                 ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Don A. Bailey
2024-01-25 22:19                   ` Jacob Moody
2024-01-25 23:38                     ` Don A. Bailey
2024-01-26  0:00                       ` Jacob Moody
2024-01-26  1:23                         ` Don A. Bailey
2024-01-26  3:50                           ` Lucio De Re
2024-01-26  4:06                             ` Don A. Bailey
2024-01-26  1:01                       ` Michael Misch
2024-01-26  2:31                         ` Don A. Bailey
2024-01-25 18:03                           ` vic.thacker
2024-01-26  3:09                             ` Dan Cross
2024-01-26  3:52                           ` Jeremy Jackins
2024-01-26  5:08                           ` hiro
2024-01-25 22:40                   ` ori
2024-01-26  0:08                     ` Don A. Bailey
2024-01-26  0:51                       ` fig
2024-01-25  2:32             ` Noam Preil
2024-01-25  3:52               ` Don Bailey
2024-01-25  4:26                 ` Noam Preil
2024-01-24 21:17                   ` vic.thacker
2024-01-25  6:58                     ` Kurt H Maier via 9fans
2024-01-25  9:32                       ` Sergey Zhilkin
2024-01-25  6:31                   ` Lucio De Re
2024-01-25 14:14                     ` hiro via 9fans
2024-01-25 11:03         ` ori
2024-01-25 15:35           ` Don Bailey
2024-01-25 16:02             ` Jacob Moody
2024-01-25 17:22               ` Don Bailey [this message]
2024-01-25 17:34                 ` Jacob Moody
2024-01-25 18:54                   ` Don Bailey
2024-01-25 18:47                     ` noam
2024-01-25 20:29                       ` Don Bailey
2024-01-25 20:05             ` ori
2024-01-25 21:29               ` Don A. Bailey
2024-01-25 23:40               ` Charles Forsyth
2024-01-25 21:15         ` ori
2024-01-25 21:15         ` ori
2024-01-25 22:38           ` Don A. Bailey
2024-01-26  6:20             ` Edouard Klein
2024-01-26  6:48               ` noam
2024-01-26 15:44                 ` ibrahim via 9fans
2024-01-26 19:23                   ` g_patrickb via 9fans
2024-01-27  0:09                     ` Vester "Vic" Thacker
2024-01-27  9:44                       ` hiro via 9fans
2024-03-12  0:22                   ` Rui Carmo

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=CAL_X0tDt9UmTXTNtf+OX0YVnxe7ptJ5F1sdAfwKrDpUuJUMmfQ@mail.gmail.com \
    --to=don.bailey@gmail.com \
    --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).