9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: ori@eigenstate.org, 9front@9front.org
Subject: Re: [9front] IWP92020 Announcement
Date: Mon, 13 Jan 2020 18:34:41 -0800	[thread overview]
Message-ID: <5F2130438F420C5CA4EBC7D5F77F98FD@eigenstate.org> (raw)
In-Reply-To: <11E2C3DD794FB352D3B99436E0558105@eigenstate.org>

> IWP92020 is happening. Submit papers and sign up here:
> 
> 	http://iwp9.org
> 
> Hope to see you there!

And, since I have heard concerns from some: This will be a
9front-friendly space.

As far as the hackathon, it's going to be openbsd-style, where
we're just collaborating on projects that interest us, and
taking the opportunity to bounce ideas off of each other, get
help from people who are more familiar with certain parts of the
system, and drink beer together.

To give you the flavor of what I'm hoping for, I want to work
(and collaborate) on things like:

	- Experiements that may lead towards 9p2020
		- Measurements around coherent caching
		- Measurements around pipelining
		- Arguments about how to avoid complexity
	- Bugfixing and filling in our C99 support, especially
	  around designated initializers and bitfields.
	- Better (faster, more crash-safe) on disk file systems.
	- Small bugfixes and improvements to scripts and system
	  utilities.
	- Implementing git/serve, if it's not done by then.
	- Implementing the http transport for git, if it's not
	  done by then.
	- Improving VMX performance so that I can get rid of the
	  machine I VNC into for a browser.
	- Figure out a better way of maintaining alien software.

The list of ideas will almost certainly change by the time the
hackathon happens, and  I don't expect to get close to finishing
the listed items. But it gives you an idea of the kind of things
I want to do.



      reply	other threads:[~2020-01-14  2:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  2:16 ori
2020-01-14  2:34 ` ori [this message]

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=5F2130438F420C5CA4EBC7D5F77F98FD@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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).