| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
As we look at the work ahead in developing the
Resilient Packet Ring standard, good web page design and maintenance can play a
significant and positive roll. With that in mind, I would like to share
some of the ideas I have as to what will make our web presence more
useful. Please come forward with your own suggestions for making our web
presence easy to use, and easy to maintain, and an overall asset to the
technology we are developing.
Please also consider this note to be a general
request for those with the skills to consider becoming webmaster for the
working group. I believe the webmaster should be one of
the working groups officers.
Web Considerations:
The home page should be laid out so that
experienced participants and people who are just joining the group can
easily find all the links they are likely to need. In addition, we all
ought to be able to see what is new, and what the dates of the last few postings
are.
Some of the information that should be directly
accessible from the home page, or from a place clearly pointed to on the front
page include the following:
The Working Group's Home Page should
state in a single sentence what our focus is. 802.1 does this with a
mission statement. 802.3 states that it develops standards for CMSA/CD
LANs, 802.15 says "The IEEE 802.15 Working Group develops Personal Area Network
consensus standards for short distance wireless networks; a.k.a.
WPANsTM". We can design our own to fit our
needs.
Administrative information that people should be
able to get their hands on quickly (both newcomers and veterans)
including:
Working Group Rules and Procedures
A list containing the wording and votes for all motions that have been passed by the working group (extracted from the minutes) The current list of action items (primarily
extracted from minutes, although some may result from e-mail discussions and
votes)
Working Group Officers with contact information (at
least their e-mail addresses)
A list of all active projects (The entry for this
list would be a hyper-link to the web section that has the detailed information
on that project.
Notification of any open ballots with their open
and close dates (including e-mail ballots)
Upcoming meetings info Notification of any issues or documents requiring working group action, i.e. meeting minutes that need to be approved, drafts out for review, even though they are not out for ballot. A What's new section that will allow the "regulars"
to see what information has been posted recently.
Overall guidelines for presenters including a very
strong statement accenting the requirement to stay focused on the task of
developing a standard and to eliminate ALL language that smacks of
commercialism, or of bolstering a single companies capabilities to offer
products into a market.
Pointers to where all Working group contributions
are posted (the contributions may be associated with meetings, but need not
be.
A pointer to a master list of all docuemnts posted on the web site.
A pointer to the reflector archives.
A pointer to a secure area with a list of all participants and their
contact information
For each active project (initially, our first PAR) there is a separate set
of pointers 1 level deeper than the web site home page.
The PAR
The Response to the 5 Criteria
Any more complete statement of project scope and objectives
Technical Reuirements (both those agreed to, and those under
discussion)
The project schedule.
The master issues list
All project documents including:
* by meeting, all contributions made at meetings, along with meeting
minutes
* All drafts (although they may require a secure area)
Project leaders contact information (as appropriate for the project.
The list may inculde Ad Hoc chairs, editors, task force leaders, etc.)
Notification of any open action items with their
open and close dates (including e-mail ballots)
Upcoming meetings info (this may be a task force only, and not a working group meeting. Links to Other sites that are relavent such
as:
Robert's Rules of Order
IEEE 802 Home Page with a description of the types of documents available there (i.e. links to operating rules and procedural documents, plenary meeting information IEEE Stds Boards rules IEEE Stds Board calendar. IEEE Patent Policy Other Standards bodies working
on related issues
Industry Groups focused on the same issues and
technology
(Note to Howard Frazier: Howard, you may want to
consider putting a "Useful Links" page up on the IEEE 802 site, that each
of the working groups could reference, rather than replicating. Links to
the IEEE Standards Board calendar and operating rules, IEEE Patent Policy,
and to Robert's Rules of Order would be useful to every working
group.) This is my first cut
at what I believe will facilitate our standards development. Let me hear
your ideas as a reflector response to this note.
Best regards,
Robert D. Love
President, LAN Connect Consultants 7105 Leveret Circle Raleigh, NC 27615 Phone: 919 848-6773 |