[b]Meeting minutes...[/b]
[b]Attendees:[/b]
Diane Plampin, Pattie Levinson, Paul Kasper, Alta Elstad, Jyothi Srinath, Kunal
Deo, Barbara Higgins, Barbara Lundquist, Kelly Nishimura
[b]AI review[/b]
* Developer tasks: Close AI. Alan, Alta, Diane have been gathering inputs
to Kelly regarding OpenSolaris developer tasks.
* Draft "release" wiki architecture. Close AI. Initial review today.
[b]Review doc delivery process[/b]
* Reminder to writers working on docs for 2009.06, when done with content,
send mail to os-final-content at sun.com alias. This notifies me, G11N content
is ready and provides info on where to get files.
[b]"Release" wiki content strategy:[/b]
http://opensolaris.org/os/community/documentation/reviews/2009.06-Wiki-Architecture-Abridged.pdf
* Alan asked for comments/questions on this slide presentation. Please send
email or reply to this thread if you weren't in the meeting and you have
thoughts on this approach.
* This is attempt to articulate strategy for snapshotting the current Info
Resources wiki to provide an "official" wiki with 2009.06 content. Alan went
through slides, with following discussion:
o Emphasis on aggregating content per the user roles: New User,
Application Developer, Server Administrator.
o Alan suggested new content use the how to template here:
http://wikis.sun.com/display/OpenSolarisInfo/OpenSolaris+Administrator%27s+How+Tos
(Log in and click the "how to procedure" link.)
o Kunal asked if the "how to" focus was intended to emulate the linux
doc project (TLDP) how tos (http://tldp.org/HOWTO/HOWTO-INDEX/howtos.html).
From Kunal's description, sounds like the intent is similar, although we hope
to provide a little more organization (by role) than is immediately evident on
the TLDP site.
o Kunal noted that TLDP how tos used to be split between mini-how tos
and more lengthy how tos, but doesn't appear that they currently maintain that
distinction. This did raise the question about how large the how tos
could/should be. Paul suggested they should be single topic focused. Alan noted
we should discuss if they become too lengthy to see if there is more modular
way to handle, but that this should be done on case-by-case basis.
o Paul asked if Marketing has any specific role descriptions we can
reference. Diane said she did not think so, based on previous Q&A with them.
However, we've worked with several folks on server administrator and are in
process of honing in on application developer role description.
o Alan noted use of following labels in wiki content to facilitate
content aggregation:
o Role-based labels:
+ newuser
+ appdeveloper
+ singleadmin
+ smallsiteadmin
+ largesiteadmin
o Information type labels:
+ task
+ concept
+ reference
o Kunal asked if you could apply labels at section level in the wiki.
Paul said no, can't do this. Only apply to page level.
o Paul asked about freezing the wiki and if that is the version G11n
would be working with. Alan (speaking for Dolores) said yes.
o Paul asked if there was an alias to use to discuss issues as they
come up. docs-integration has bunch of non-writers on it, and internal writer
aliases may be too broad. For now, just mail Alan and he'll enlist the small
group of writers supporting the project work.
[b]Community metrics for March:[/b]
http://spreadsheets.google.com/pub?key=pzCosgzxVSeXF2GqxVJmQWw
* Alan noted members list grew by 1, but over last couple of months, looks
like there is a fair amount of coming and going (e.g., people
subscribing/people unsubscribing)
* Alan also noted that, while only few months of data, downloads of docs
source and PDF tarballs and man source tarball look to be fairly consistent
month-to-month.
* Alan said it would be good to accumulate some of the data into a
quarterly trend graph.
* Kunal suggested taking a look at alexa.com for further analysis of
traffic patterns.
--
This message posted from opensolaris.org
