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


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

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

Subject: Re: We will need a volunteer to fix the resolution

Hi Norm,

Well good, we have an ultimate goal in common, that's a good starting point.

Greg and I were talking last week and he brought up the "when worlds
collide" metaphor - that in effect there is a gap here between what
you have/need/want on docbook.org and what OASIS has/needs/wants on
docs.oasis-open.org. I'm paraphrasing a bit but his point was that
docbook.org has a lot of content that is more in the line of living
code than standards and specifications - and the OASIS model doesn't
deal well with that sort of thing right now.

Would you have some time for a discussion next week. You, me, Greg
Carpenter and Robin. Talk about your needs and see if we can't come up
with a game plan for moving things forward. I don't want you to have
to put your hands over your ears every time you see an email come in
from me.

If there is any particularly good or bad time for you, let me know.



On Tue, Jun 26, 2012 at 3:18 PM, Norman Walsh <ndw@nwalsh.com> wrote:
> Chet Ensign <chet.ensign@oasis-open.org> writes:
>> Unfortunately, our policy doesn't allow anyone other than authorized
>> staff to have direct write access to OASIS systems. (I am copying
>> Scott McGrath so that he will be aware of the request.) I'm sure you
>> can understand that this is standard practice in most private
>> businesses.
> This has been such an ongoing source of pain and suffering that I'm
> sorely tempted to stick my fingers in my ears and go "lalalalala" at
> the top of my lungs.
>> However, there is no need for direct write permission. As part of
>> approving any OASIS work product and either publishing it as a
>> Committee Draft, releasing it for public review, or approving it as a
>> final deliverable, TC Administration publishes the work to the
>> appropriate server locations. You submit the appropriate ticket to us
>> (see http://www.oasis-open.org/resources/tc-admin-requests for the
>> complete set) and we work with you to prepare the final work package
>> and load it to the servers - and of course announce the event to TC
>> members and OASIS and the public.
> Ideally, I'd like docs.oasis-open.org/docbook to be as useful a
> resource as docbook.org. In fact, I'd mostly like it to be a mirror of
> docbook.org, perhaps with a little wordsmithing here and there.
> Submitting tc-admin-requests for every update to 17,353 files seems a
> bit...tedious.
>                                         Be seeing you,
>                                           norm
> --
> Norman Walsh <ndw@nwalsh.com> | Men are more like the times they live
> http://nwalsh.com/            | in than they are like their
>                               | fathers.--Ali Ibn-abi-talib


Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

TC Administration information and support is available at

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

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