As I mentioned at yesterday's meeting, we're at the point where we can
really start to use volunteer help. There are many things, both technical
and nontechnical, that we need to do to get to the next level.
One thing I want to make clear up front is that, beyond Doug, there is no
hierarchy. This may be a problem later on, but I think the group is small
enough so that we can work effectively this way. What it means is that
the only requirements to contribute are enthusiasm, a willingness to
collaborate, and a little bit of time.
Here are the tasks that I see an immediate need for:
1. Revamping the OHS web site. We need to come up with a good structure,
reorganize what's currently there, integrate all of the new material we've
created, and decide what other documents we need to add.
2. Writing support documents. This not only includes design and
requirement documents for the OHS, but also things like tutorials on
related technologies. As I mentioned at the meeting, these will not only
be tremendously valuable for us, but they are also an opportunity to get
published. In my former life, I was a high-tech editor, and I will gladly
help people get in touch with the right contacts for publication.
3. Writing code. What was apparent at yesterday's meeting was that we
have not done a good job of translating the design and architecture in our
heads onto paper so that others can benefit from them. I think there are
about four of us who have really discussed this stuff quite a bit over the
last several months and have a good picture of what's going on, but now we
need to make that information available. One of the ways others can help
is by asking questions, forcing us to write down information that
currently resides only in our heads. I know that I personally have made a
lot of assumptions that other people haven't shared, and it has been
helpful for me to get the right feedback from others. Once you feel you
have a good understanding of what we're trying to do, I'd encourage
interested parties to write some code.
I'm going to list some names of people who have volunteered to help with
particular tasks. This is by no means a binding contract; if you want to
do something else or if I made a mistake, point them out. Those of you
who haven't spoken up yet, if there are areas to which you want to
contribute, speak up!
Use cases/Requirements maintenance -- Eugene
General writing -- Eric, Eugene
Coding -- Eric, Eugene, Grant, Lee, Shinya
Web site -- Nicholas
System administration -- Shinya
One final comment/plea. We're all volunteers here, and all feedback is
meaningful. Please don't hesitate to make your thoughts known.
-- +=== Eugene Eric Kim ===== email@example.com ===== http://www.eekim.com/ ===+ | "Writer's block is a fancy term made up by whiners so they | +===== can have an excuse to drink alcohol." --Steve Martin ===========+
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:57:48 PDT