The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Diomidis Spinellis <dds@aueb.gr>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Usenix: no official Unix 50th celebration, apparently
Date: Wed, 5 Sep 2018 20:23:27 -0400	[thread overview]
Message-ID: <778C65CA-0447-41F0-8F6F-3E3277CFA847@ccc.com> (raw)
In-Reply-To: <53afe3bc-b775-154b-b764-7bc6ac4769ec@aueb.gr>

I’ll ok into it. 

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On Sep 5, 2018, at 5:31 PM, Diomidis Spinellis <dds@aueb.gr> wrote:
> 
>> On 26/08/2018 07:10, Theodore Y. Ts'o wrote:
>> [...]
>> The question I would raise is whether some kind of 50th celebration
>> has to be colocated with Usenix ATC, especially if the Usenix BoD is
>> not innterested in lending much in the way of financial or staff
>> support.  For example, maybe something combined with some kind of
>> fund-raising event held at the Compute History Museum in the Bay Area?
>> Or perhaps the Linux Foundation might be willing to do a Unix 50th
>> celebration at their 2019 Open Source Summit event?
>> It does seem to me that Usenix ought to have the right of first
>> refusal to host such a celebration, but if the Board isn't willing to
>> step it up, there are other possibilities that could be explored.
> 
> One possibility might be to propose a "50th Unix Anniversary" Developer Room at FOSDEM 2019 [1].  FOSDEM is a free event for software developers to meet, share ideas and collaborate.  It takes place every year with thousands of developers of free and open source software from all over the world gathering in Brussels.
> 
> Our room can be used to host presentations related to topics such as the Unix history, the 50th anniversary, and the reconstruction efforts of historic editions.  The many *BSD and Linux folks that attend FOSDEM together with thousands of other open source aficionados provide an excellent audience for our event.  We can also combine the presentations with a TUHS stand where we can display running historic software.
> 
> The deadline for room proposals is September 20th and for stands November 2nd [2].  FOSDEM is entirely organized by volunteers and attendance is free without registration.  We don't have to pay anything for the room and the stand, but we also can't expect any funding from the organizers for flying people in.
> 
> [1] https://fosdem.org/2019/
> [2] https://fosdem.org/2019/news/2018-08-10-call-for-participation/
> 
> Diomidis

  reply	other threads:[~2018-09-06  0:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26  0:31 Warren Toomey
2018-08-26  1:04 ` Lyndon Nerenberg
2018-08-26  1:31   ` Larry McVoy
2018-08-26  2:03   ` Clem Cole
2018-08-26  2:34     ` Larry McVoy
2018-08-26  2:47 ` Dave Horsfall
2018-08-26  4:10   ` Theodore Y. Ts'o
2018-09-05 21:31     ` Diomidis Spinellis
2018-09-06  0:23       ` Clem cole [this message]
2018-08-26  5:29 ` Kurt H Maier
2018-08-28 11:54   ` Kevin Bowling
2018-08-28 23:30     ` Dave Horsfall
2018-08-28 23:37       ` George Michaelson
2018-08-31 21:47 ` [TUHS] Usenix: no official Unix 50th celebration, (yet) Clem Cole
2018-12-26 21:49   ` reed

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=778C65CA-0447-41F0-8F6F-3E3277CFA847@ccc.com \
    --to=clemc@ccc.com \
    --cc=dds@aueb.gr \
    --cc=tuhs@tuhs.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).