On Thu, Aug 6, 2009 at 6:46 PM, alan mcclellan<no-reply at opensolaris.org> 
wrote:
> As I've mentioned, I'm in process of reviewing the docs community site and 
> cleaning it up prior to the 9/14 content migration to xwiki. To that end, 
> I've come up with a site architecture document that shows how I would like to 
> re-organize the site. I would greatly appreciate any inputs from folks here 
> who care about such matters. Take a  look at the PDF site architecture 
> document here:
>
> http://opensolaris.org/os/community/documentation/reviews/docs-community-site-architecture-01.pdf
>
> As you'll see in the slides, I'm basing the site layout on the premise that 
> purpose of the site is to support the user community that wants to:
>
> ? Contribute to OpenSolaris documentation
> ? Redistribute OpenSolaris documentation
> ? Contribute code to the OpenSolaris project
> ? Set up OpenSolaris and develop applications on OpenSolaris

I guess I'm slightly confused by the latter two bullets here.

If I wanted to contribute code to X, I would expect to go to X to find
out how to do it. So, why is that covered here as well? Part of that
question is: are you linking back to X, or does X link back to docs?
In other words, are you providing links to help people because
they've come to the wrong place, or is this the right place they should
have come to first?

(So for another project or community, what can they expect to do in
terms of interactions with the docs community when they're writing
docs: do they come to you for tools, standards, a repository for the
finished documentation, or even authorship resources?)

There's a lot of stuff you just link to right now (quite a lot on wikis.sun.com
for example) - is the intention to keep it spread out, or to bring more of that
material onto os.org once we've got the new infrastructure?

I'm also unclear on the Access Info  bit of the tree - some more explanation
of what that is would help me out.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/

Reply via email to