From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Ori Bernstein <ori@eigenstate.org>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Request for (constructive?) comments: Plan 9 : 2020
Date: Wed, 23 Oct 2019 00:32:28 -0700 [thread overview]
Message-ID: <CAJSxfmJOoER=GHcak58x=T6gGFBaRf8R9a0OmPW9nt+XAP5jdg@mail.gmail.com> (raw)
In-Reply-To: <305DB5416B0218BFD8D80F5FF104032A@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
The general idea of teaming up to address issues/bugs or add features is
some sort of hackathon.
On Tue, Oct 22, 2019 at 9:49 PM <ori@eigenstate.org> wrote:
> > Jeff (jas) and I have been chatting about organizing a "Plan 9 : 2020"
> > workshop. We're trying to gauge everyone's interest, and to solicit
> agenda
> > items, venue suggestions, and hopefully volunteers to help organize it.
>
> I'd be interested in attending, and I don't mind taking some time to
> help organize.
>
> > If you have a different suggestion, or are willing to offer a venue,
> please
> > comment.
>
> Some of us have also been talking about planning an OpenBSD-style
> hackathon. (OpenBSD hackathons: Get developers in a room, and write
> code for a week, exchanging ideas, trying to get commits into base and
> ports. Beer is usually involved.)
>
> We'd discussed putting together something like that for Plan 9 in the
> first half of 2020. Anyone hacking on Plan 9 related code would be
> welcome.
>
> I don't know if this is a different suggestion so much as a different
> event. Experience implies that merging the two together may be a bit
> too much in one shot.
>
> Expect a post about that when we start sorting out the details.
>
>
[-- Attachment #2: Type: text/html, Size: 1644 bytes --]
next prev parent reply other threads:[~2019-10-23 7:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 4:49 ori
2019-10-23 6:58 ` Steve Simon
2019-10-23 8:40 ` Iruatã Souza
2019-10-23 7:32 ` Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-30 1:02 ori
2019-10-31 18:58 ` Lyndon Nerenberg
2019-10-31 21:03 ` Iruatã Souza
2019-10-29 18:40 umbraticus
2019-10-29 19:00 ` Rodrigo G. López
2019-10-29 19:16 ` Marshall Conover
2019-10-26 20:44 ori
2019-10-26 23:58 ` Rodrigo G. López
2019-10-27 16:22 ` tlaronde
2019-10-24 9:45 Jonas Amoson
2019-10-24 20:47 ` erik quanstrom
2019-10-25 4:21 ` Skip Tavakkolian
2019-10-25 4:28 ` Kurt H Maier
2019-10-25 5:17 ` Skip Tavakkolian
2019-10-26 0:27 ` Skip Tavakkolian
2019-10-26 14:10 ` Marshall Conover
2019-10-26 19:26 ` Lyndon Nerenberg
2019-10-26 20:32 ` Marshall Conover
2019-10-29 15:16 ` Marshall Conover
2019-10-29 16:24 ` Nicolas S. Montanaro
2019-10-29 16:31 ` Chris McGee
2019-10-29 17:56 ` Lyndon Nerenberg
2019-10-29 19:43 ` Lyndon Nerenberg
2019-10-29 20:02 ` Dave MacFarlane
2019-10-30 19:28 ` Chris McGee
2019-10-29 16:33 ` David Bulkow
2019-10-29 17:50 ` Marshall Conover
2019-10-22 20:33 Skip Tavakkolian
2019-10-23 0:22 ` [9fans] " Sean Hinchee
2019-10-23 1:14 ` Marshall Conover
2019-10-23 11:09 ` tlaronde
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='CAJSxfmJOoER=GHcak58x=T6gGFBaRf8R9a0OmPW9nt+XAP5jdg@mail.gmail.com' \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
--cc=ori@eigenstate.org \
/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).