From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] sources/contrib
Date: Tue, 26 Jan 2021 22:23:44 +0000 (UTC) [thread overview]
Message-ID: <23c1037e-634f-468c-afcf-891808795938@sirjofri.de> (raw)
In-Reply-To: <20210126220132.GA2232@rosemary.nohup.io>
Hello and welcome back,
26.01.2021 23:01:35 Pouya Tafti <pouya+lists.9fans@nohup.io>:
> I'm coming back to Plan 9 after something of a 15 year break.
Wow, that's a very long time. Indeed, welcome back. I hope you feel well
in the new community. I'm sure it changes quite a bit.
> It looks
> like 9p.io has replaced plan9.bell-labs.com. Is it still possible to
> have a contrib directory (and should I have one / do I deserve one)?
As far as I know there is a mirror or remake of the original contrib at
9p.io, but I'm not sure.
Since you were away for 15 years you might want to check out other Plan 9
forks. The most active one is probably 9front[1], which contains lots of
new software as well as hardware support. It also has its own
infrastructure (source repo, contrib).
I know there's (or was?) 9atom, but I don't know the details. Also
there's lots of new software for 9 in general made by other developers
outside the contribs. It's worth mentioning that many new software is in
git repos since we now have a native git software[2]. Lots of older
software is archived on github[3].
There's also a 9fans discord server that's bridged to ##9fans on
freenode, if you want some more synchronous communication.
Don't hesitate to ask questions. Welcome back 🙂
sirjofri
[1] http://9front.org
[2] https://github.com/oridb/git9
[3] https://github.com/Plan9-Archive
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5b1530f46b5c653d-Md2a9b34fd0f7c2a1b8c9c884
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-26 22:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 22:01 Pouya Tafti
2021-01-26 22:23 ` sirjofri [this message]
2021-01-26 23:10 ` Pouya Tafti
2021-01-26 23:28 ` Pouya Tafti
2021-01-26 22:33 ` David du Colombier
-- strict thread matches above, loose matches on Subject: below --
2007-11-20 19:29 Erik Quanstrom
2007-11-20 15:46 Federico Benavento
2007-11-20 15:53 ` erik quanstrom
2007-11-20 15:57 ` Federico Benavento
2007-11-20 18:31 ` Uriel
2007-11-20 18:58 ` erik quanstrom
2007-11-21 3:08 ` lucio
2007-11-20 19:30 ` Gabriel Diaz
2007-11-20 20:21 ` David Leimbach
2007-11-20 21:09 ` erik quanstrom
2007-11-20 21:36 ` Uriel
2007-11-20 21:46 ` erik quanstrom
2007-11-20 22:04 ` anyrhine
2007-11-20 23:57 ` Federico Benavento
2007-11-21 0:01 ` erik quanstrom
2007-11-20 22:42 ` David Leimbach
2007-11-20 23:09 ` dave.l
2007-11-20 23:59 ` David Leimbach
2007-11-21 8:23 ` Uriel
2007-11-21 10:06 ` Robert Raschke
2007-11-21 14:30 ` David Leimbach
2007-11-21 15:33 ` Uriel
2007-11-21 21:08 ` Navin Johnson
2007-11-21 22:59 ` Uriel
2007-11-21 20:55 ` Navin Johnson
2007-11-22 15:44 ` Russ Cox
2007-11-22 19:48 ` Uriel
2007-11-21 0:04 ` Steve Simon
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=23c1037e-634f-468c-afcf-891808795938@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).