+1 for SCM, I think that following the SCM model that will be used across opensolaris.org is the way to go for the docs too. (I have heard from a few people that they don't have a site of their own and that is part of the motivation to post on opensolaris.org.)
Folks might not be aware of the discussion that is underway related to SCM for the opensolaris.org site, but we're keeping an eye on it and intend to write instructions for checkin/out/merge when they make a final decision on the SCM tool. Meantime, you can upload by following these steps: 1-Log in to opensolaris.org 2-Navigate to opensolaris.org/os/community/documentation/files 3-Click 'Manage files' 4-Click 'Add files' 5-Click 'Browse' and select your file 6-Type description into description field 7-Click 'Save' BTW, you can just upload a doc with the same file name and it will overwrite, so you don't have to delete it first. Hope this helps, Michelle >X-Original-To: docs-discuss at opensolaris.org >Delivered-To: docs-discuss at opensolaris.org >Date: Wed, 18 Jan 2006 02:46:29 -0800 >From: Ben Rockwood <benr at cuddletech.com> >User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050720) >X-Accept-Language: en-us, en >MIME-Version: 1.0 >To: Brendan Gregg <brendan.gregg at tpg.com.au> >Subject: Re: [docs-discuss] Uploading docs suggestion >Content-Transfer-Encoding: 7bit >Cc: docs-discuss at opensolaris.org >X-BeenThere: docs-discuss at opensolaris.org >X-Mailman-Version: 2.1.4 >List-Id: General documentation discussion and requests to contribute documentation <docs-discuss.opensolaris.org> >List-Unsubscribe: <http://mail.opensolaris.org/mailman/listinfo/docs-discuss>, <mailto:docs-discuss-request at opensolaris.org?subject=unsubscribe> >List-Archive: <http://mail.opensolaris.org/pipermail/docs-discuss> >List-Post: <mailto:docs-discuss at opensolaris.org> >List-Help: <mailto:docs-discuss-request at opensolaris.org?subject=help> >List-Subscribe: <http://mail.opensolaris.org/mailman/listinfo/docs-discuss>, <mailto:docs-discuss-request at opensolaris.org?subject=subscribe> > >I vote for an SCM, which means it would be implemented with the code SCM >whenever that happens. I'm not sure what you use to write your docs >Brendan, but mine are done in LaTeX and DocBook making an SCM the prime >way to go about it. I manage all my docs and the docs for Enlightenment >this way. If you then want automation to a public locale, assuming you >don't just link to a web viable SCM interface (CVS-Web or Subversion) >you can dump the doc into the final location. > > >Just out of curiousity, whats wrong with the file upload section of the >web interface we currently have? Your a docs community leader, so you >have upload permissions. If your writting in HTML then perhaps it sucks >to delete and re-up your doc (assuming you don't just edit it online via >the web interface) but if your using PDF its the way to go anyway. > >benr. > > >Brendan Gregg wrote: > >>G'Day Folks, >> >>In the past I've written docs for my site and docs for other sites. I >>have a feeling for what works and what doesn't. To cut a long story short, >> >>Not having write access sux. Sometimes you want to make a series of quick >>updates. Having write access to opensolaris.org may be difficult to setup >>for everyone (eg, sourceforge style), perhaps a little easier if there was >>an writable upload directory and a deamon to farm things out (eg, CPAN >>style). But still not very easy. >> >>There is one easyish solution if you are the sole contributer. It goes >>like this, >> >>1. contributer writes document, obeys OpenSolaris style checklist, uploads >> to THEIR own website (perhaps a non-public URL). >>2. contributer posts URL to docs-discuss, asks if document may be included >> on opensolaris.org. >>3. if so, URL is added to a script that downloads and caches the document >> on opensolaris.org. This script is crontab'd to run every week, and >> performs a few checks on content to avoid caching 404 errors, etc. >>4. contributer freely updates the document on THEIR website, >> opensolaris.org automatically picks up the changes every week. >> >>This means contributers can update opensolaris.org without needing write >>access. They just make changes to their site. >> >>this doesn't help if a few people are working on the same document... >> >>Brendan >> >> >>_______________________________________________ >>docs-discuss mailing list >>docs-discuss at opensolaris.org >> >> > >_______________________________________________ >docs-discuss mailing list >docs-discuss at opensolaris.org
