OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] DocBook specializations


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[I just realized this thread should go to docbook@, sorry for cross-posting]

I just created such page (to be filled), but I thought anyone registered
could create new pages? Please ask me if needed, I think I can add
people to the authors list (UserGroup).

http://wiki.docbook.org/topic/DocBookSpecializations

Camille.

cstrong@arielpartners.com a écrit :
> I and others on this list have already traded specializations and even
> made an attempt at coming up with packaging guidelines.
> 
> Based on my experiences with other open source products (Ant, Zope, Cocoon,
> Struts, Emacs, etc.) having a library of optional add-ons is an important
> factor in speeding adoption/attracting new users.  For open source, the
> size of the community is perhaps the single most important factor, for
> many obvious reasons.
> 
> The most successful of the projects I mentioned above had one thing in
> common--they had something akin to the "specializations repository"
> mentioned below.  There were many variations in how it was done, however.
> 
> There are many second order benefits to this.  Specializations that
> become very popular often end up migrating (in some form) to the core.
> After all, open source users vote with their feet.
> 
> We could start very simply by having a "specializations" page on the docbook
> wiki that includes a set of links.  Having the ability to upload
> a zip file containing the package would be nice.  Bigger packages
> could live on sourceforge.  The specializations page could be more than
> a list; it could include a couple of guidelines, best practices, etc.
> 
> If someone with privileges would create such a page, I would be willing
> to contribute to it (a) draft1 of some guidelines and (b) a first example
> package.
> 
> Oh-- we might need two wiki areas.  I am only talking about Docbook5.
> Some other motivated person will have to take the lead for Docbook < 5.
> :-)
> 
> Regards,
> 
> --Craeg
> 
> 
> 
>>> Would it makes sense to provide customization developers a best
>>> practices guide, and a "DocBook Specializations Repository" where people
>>> could contribute their customized schemas and stylesheets to handle
>>> specific requirements, by metier for example?
>> This idea is worth, but is there anyone who can devote his/her free time
>> for this project? Or fund development of such guide and repository?
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEBxNrjv9P65BfOUMRAnj6AJ9vmvVHztQEQNAu1l1IAxIMlUjbHwCeN83e
z2kykzw2PhxogGxx7+jZrws=
=CjNt
-----END PGP SIGNATURE-----
begin:vcard
fn;quoted-printable:Camille B=C3=A9gnis
n;quoted-printable:B=C3=A9gnis;Camille
org:NeoDoc
adr:Domaine du petit Arbois BP 88;;CEEI;Aix en Provence Cedex 4;;13545;France
email;internet:camille@neodoc.biz
tel;work:+33.4.42.22.62.35 
tel;cell:+33.6.33.15.10.23
x-mozilla-html:FALSE
url:http://neodoc.biz
version:2.1
end:vcard



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]