|
Grex > Coop12 > #152: Topics of discussion related to the Next Grex | |
|
| Author |
Message |
aruba
|
|
Topics of discussion related to the Next Grex
| 
Dec 2 16:38 UTC 2002 |
The board plans to discuss plans for the next Grex machine at the next board
meeting, which is scheduled for December 11th. Hopefully as many staff
members as possible will be there (as well, of course, as anyone else who
would like to attend), so we can get a broad sense of where everyone's at
and what needs to happen next.
This item is for brainstorming topics to discuss at the meeting.
|
| 21 responses total. |
gelinas
|
|
response 1 of 21:
|
Dec 3 03:45 UTC 2002 |
Shoot. The school board is also meeting that night. Ah well.
|
richard
|
|
response 2 of 21:
|
Dec 3 08:05 UTC 2002 |
wow! is the world ready for the NEXT Grex?!?!?!?!?! :)
|
gull
|
|
response 3 of 21:
|
Dec 3 14:07 UTC 2002 |
It waited around for a while, a few years ago, then moved on. ;)
|
cmcgee
|
|
response 4 of 21:
|
Dec 3 14:23 UTC 2002 |
Oh so true!.
|
cross
|
|
response 5 of 21:
|
Dec 3 18:06 UTC 2002 |
The authentication issue, please.
|
cross
|
|
response 6 of 21:
|
Dec 3 18:08 UTC 2002 |
Also, if OpenBSD isn't ready to go on UltraSPARC by this time, I highly
recommend going with x86 instead.
|
aruba
|
|
response 7 of 21:
|
Dec 3 20:20 UTC 2002 |
Re #6: Well, as you, know, that's an issue with many different aspects. So
we need more specifics to discuss.
It looks like the board and staff might not get it together to have a
combined meeting this month, because of other commitments. So the dig
discussion will probably be put off until Jan/Feb. That leaves lots of time
for this brainstorming item.
For myself, I'd like us to come up with at least a broad outline of how the
developement of the system will proceed, so it's on the table and everyone
knows where we stand. After that we can talk timetables, but first we need
a general plan.
I'd also like some agreement on how progress will be tracked and reported to
the users at large. Doesn't have to be anything too formal, but it should
be possible for people to deduce from what's online where the process is at
and what the stumbling blocks are. Hopefully this will also allow the staff
to split up the work more efficiently, too.
|
other
|
|
response 8 of 21:
|
Dec 5 18:16 UTC 2002 |
Slashdot | Sun vs. OpenBSD?
http://slashdot.org/articles/02/12/05/044234.shtml?tid=122
|
gull
|
|
response 9 of 21:
|
Dec 5 21:49 UTC 2002 |
Without looking at the article, but knowing what the Slashdot crowd is
like, I expect the answer to be 'Linux'. ;)
|
mdw
|
|
response 10 of 21:
|
Dec 5 22:23 UTC 2002 |
Well, it was only a matter of time until it hit slashdot.
|
cross
|
|
response 11 of 21:
|
Dec 6 19:03 UTC 2002 |
Regarding #7; Well, the question really is: Is OpenBSD on UltraSPARC
the appropriate direction to go for the next grex? Marcus has been
working on it for a good six months or so now; what's the status? If
it's not rock solid, production ready, then I really, *really*, *REALLY*
recommend just saying, ``okay, bag it; we're going with x86 instead.''
btw- http://www.micropro.com/ sells some pretty killer, customizable,
AMD-athlon based x86 servers. I put together one for $3,020 that
would really, really smoke; more basic machines are much cheaper.
|
remmers
|
|
response 12 of 21:
|
Dec 8 20:49 UTC 2002 |
I guess we've agreed to postpone this topic to a future board meeting,
due to the difficulty of getting both board and staff together on
December 11.
In the meantime, I'll remind folks that I volunteered (I forget in just
which item) to come up with a list of the software decisions to made and
tasks to be done in getting the next Grex up and running. I'm partway
through this process and will post the list publicly when it's done.
The Garage cf. is probably the appropriate place.
|
remmers
|
|
response 13 of 21:
|
Dec 8 20:51 UTC 2002 |
(Re my #12: Just software, not hardware. The choice of hardware platform
is a separate issue.)
|
aruba
|
|
response 14 of 21:
|
Dec 8 23:46 UTC 2002 |
Could you link that to coop, John?
|
janc
|
|
response 15 of 21:
|
Dec 16 20:14 UTC 2002 |
I entered garage:142 which gives my summary of what needs to be done to
build the next grex.
|
janc
|
|
response 16 of 21:
|
Dec 16 20:15 UTC 2002 |
I should have typed that as item:garage:142
|
remmers
|
|
response 17 of 21:
|
Dec 16 21:10 UTC 2002 |
No -- item:garage,142 . Sheesh, don't you know the syntax of your own
user interface?
I've also been thinking about the breakdown of tasks in building the next
Grex as well, and about some of the decisions to be made. I'll add my
thoughts as comments to your summary.
|
janc
|
|
response 18 of 21:
|
Dec 17 15:18 UTC 2002 |
Actually, many different things can be used as a punctuation mark
between the conference name and the item number. I think
item:garage.142 and item:garage;142 also work.
|
janc
|
|
response 19 of 21:
|
Dec 17 15:19 UTC 2002 |
Well, I was wrong about the semicolon.
|
remmers
|
|
response 20 of 21:
|
Dec 17 23:48 UTC 2002 |
Hm, I seem to remember that only the comma used to work, or at least
that the colon didn't. Did you liberalize the syntax?
|
janc
|
|
response 21 of 21:
|
Dec 18 15:53 UTC 2002 |
Think so. A lot of other conferencing systems use dot. To maximize
compatibility, I added that. Don't know which others I added when.
|