Hi Stephen,

OK, thanks for the clarification. I still don't get it, but I'm sure 
it will all come together as they get rolling. I'm just happy that 
someone is answering the call of 'the article writers' because I made 
an effort to ask for some site functionality and templates for 
articles when I came on board, but didn't make much headway...as Ben 
put it, rubber never hit the road. Probably because I was assuming a 
need for templates and tools when there is none! :) 

At any rate, the docs community is striving to provide tools 
instruction and templates that folks can use to publish on 
opensolaris.org or anywhere else in HTML (we generally just use 
single-chapter book for something the size of an article). So, if 
there becomes a need, we can hopefully help out.

cheers,
Michelle


>Date: Tue, 24 Jan 2006 09:16:26 -0800
>From: Stephen Hahn <sch at eng.sun.com>
>To: Michelle Olson <mo137222 at jurassic.sfbay.sun.com>
>Cc: benr at cuddletech.com, docs-discuss at opensolaris.org
>Subject: Re: [docs-discuss] Cross Post: OpenSolaris Articles Project
>Mime-Version: 1.0
>Content-Disposition: inline
>User-Agent: Mutt/1.5.7i
>
>* Michelle Olson <mo137222 at jurassic.sfbay.sun.com> [2006-01-23 
16:44]:
>> Articles have the same technical needs as all the other documents 
we 
>> want to produce for opensolaris, so maybe it is better to say not 
that 
>> we have conflicting projects, but that we'll grapple with common 
>> hurdles: license, authoring tools, review cycles, style guidelines. 
If 
>> the articles project manages some of these hurdles more quickly, 
then 
>> we can leverage that speed here too. I certainly would endorse such 
a 
>> project and hope to learn something from it and add something to 
it. 
>
>  Unless I'm misreading the proposal, Jim is actually discussing
>  assisting article authors who might be publishing other than on
>  opensolaris.org, so I think the { license, tools, review
>  process, style } aspects are controlled by the venue (except for 
use
>  of trademarks...).
>
>  - Stephen
>


Reply via email to