Lourens Veen wrote:
Hi all,
I'm ready to take another look at the OGP website design. It's been a
month or os, so here is a summary of the previous discussion (see
http://lists.duskglow.com/open-graphics/2006-March/004815.html).
- 100% of the people (i.e. both of them :-)) who said something about
the looks liked them. I think they can be refined a little, but there
seems to be consensus that it's not horribly ugly at least.
- A number of people raised technical issues with my first attempt,
which were discussed and will be taken into account in the second
iteration.
- We don't have a good idea yet of what should be on the site, who will
be using it and for what purpose, and so on.
I think that that last point is currently the most pressing one. The
organisation of the page depends upon its contents and how they will be
used. So, we need to know what the site will do, and for whom.
To start with the latter, I already posted the previous potential users:
- End users
- Developers
- Corporate customers
and I'd like to add
- Press
- Non-technical contributors
Good things to add, yes. I might mentally group developers and non-tech
contributors a bit, but in some ways they're definitely distinct.
Any other kinds of users for the site?
As for what these users will want to do, here are some points for you
all to add to, in part taken from Dieter's post on the subject:
- End users
- Download drivers for their hardware
- Read installation and troubleshooting instructions
- Request support (a web forum?)
- File bugreports (personally, I find Bugzilla very confusing, and I'd
like to see something that is friendlier to end users and yields better
bug reports)
I wouldn't expect end users to file bugs in hardware, or even in
drivers. Applications is one thing--my program doesn't do what I tell it
to!--but an end user doesn't really have any idea what he's "telling the
graphics card to do". Thus I'd say most outside people filing bugs would
be experienced software or hardware developers, and would be able to
find their way in a developers section.
- Developers
- Per project (Hardware or Software)
- Requirements
- Design
- Documentation
- Theory of operation
- Design documents / schematics
- Gerber
- Timing diagrams / behaviour
- Interfaces (pinouts, voltages, functions and data
types)
- Environmental requirements (power, cooling, OS,
libraries...)
- Installation instructions
- Implementation
- Latest code/HDL
- Somewhere to send contributions
- Testing
- Test cases
- Test results
- Non-technical contributors
- Marketing (probably needs a mailing list and a wiki to exchange
ideas, at least)
- Book keeping (all in the open? Or semi-closed, with regularly
published reports?)
- Legal discussion/information
- Corporate customers
- Should be referred to Traversal Technology
- Press
- General information about the project
- News
- Contact information for a spokesperson
- Official logos, etc.
Please quote and add, and let the brains storm.
There are still other issues, like software and file formats to use, but
they are really part of the next stage I think. If you have any ideas
on those please save them for later, or if you really can't wait, send
them off-list so as to not drag this thread off-topic too much.
Lourens
Other than that, sounds good! :)
(To me at least... there are parts, e.g. content of the developers
section, that I'm clueless on.)
--
dolphinling
<http://dolphinling.net/>
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
