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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-requirements message

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


Subject: Re: [office-requirements] Groups - requirements_draft_03_06_2009.ods uploaded


Hi Bob,

Bob Jolliffe wrote:

[...]

> 
>> The comment of Rick Jelliffe is the older one and has also the higher
>> priority (blocker against major), while RF2000's issue has a concrete
>> proposal attached. FMPOV, it would be best practice to keep the older
>> issue, adding the link to our proposal. Would you agree? Is there
>> anything else to consider?
> 
> I think there are ideally two sources of submitted requirements  (Of
> course there are also others which were not submitted explicitly as
> requirements but which have become designated as such by the TC).  The
> one is from the general public via a mail to the comment list using
> the  Requirements template.  The other, at least at the moment, is the
> list of proposals on the wiki, which are proposals submitted by TC
> members also using a template.
> 
> I think the best thing to do would be to create a proposal on the
> "list of proposals" page of the wiki which refers to your mail.  What
> do others think?  Am I interpreting this list correctly?

The proposal shall of course be added to the wiki. However, the comments
I have been getting so far, raised some concerns about the data model
and it's effects regarding on accessibility. I wanted to work on this,
but couldn't find enough time so far. To move ahead and gain visibility,
I will copy the proposal as it is to the wiki and work on it later.

> 
> And yes, we will have to group them and link or remove duplicates.
> But for the moment my first challenge is to ensure that we have
> captured all of them.

I totally agree.

Best regards,
Peter

>> bobj@dst.gov.za wrote:
>>> Greetings
>>>
>>> I have uploaded a calc spreadsheet which is automatically generated via
>>> xslt from the issues tagged as a fix for ODF-Next on Jira.  Its a first
>>> stab and there's some work to be done with it.
>>>
>>> Unfortunately not all requirements submissions have come through the
>>> prescribed process - in an email with fields marked up as +TITLE, +NAME,
>>> +SCOPE etc.  What I have done in my primitive jira2ods xslt transformation
>>> is to follow the URLs listed in the jira issue and parse this information
>>> out.  Two possible fixes to the process would be:
>>>
>>> 1. for me to re-post the unformatted public comment (perhaps to the
>>> odf-next list) and put in the required fields.  Then edit the jira issue so
>>> that it points at the new mail message.
>>>
>>> 2. create the requirements fields as "first class" jira issue attributes
>>> for a requirement.  I don't know how to do that, but I suspect it is
>>> doable.  Then manually edit them.
>>>
>>> The other alternative is to do nothing so fancy and just manually maintain
>>> the list.
>>>
>>> In addition we have a list of 46 TC proposals
>>> (http://wiki.oasis-open.org/office/List_of_Proposals) which are "in
>>> progress" but have not been approved.  Given that we did a freeze on new
>>> proposals for odf 1.2 I am assuming that each of these will also
>>> potentially be a requirement for odf-next.
>>>
>>> Regards
>>> Bob
>>>
>>>  -- Mr. Bob Jolliffe
>>>
>>> The document named requirements_draft_03_06_2009.ods has been submitted by
>>> Mr. Bob Jolliffe to the OpenDocument - Requirements document repository.
>>>
>>> Document Description:
>>> ODF-Next requirements
>>>
>>> View Document Details:
>>> http://www.oasis-open.org/committees/document.php?document_id=32771
>>>
>>> Download Document:
>>> http://www.oasis-open.org/committees/download.php/32771/requirements_draft_03_06_2009.ods
>>>
>>>
>>> PLEASE NOTE:  If the above links do not work for you, your email application
>>> may be breaking the link into two pieces.  You may be able to copy and paste
>>> the entire link address into the address field of your web browser.
>>>
>>> -OASIS Open Administration
>> --
>> Peter Junge
>> Open Source Strategy Director
>>
>> Beijing Redflag Chinese 2000 Software Co., Ltd.
>> Building No.2, Block A, Huilongsen, 18 Xihuan Nanlu
>> Beijing Economic-Technological Development Area
>> 100176 Beijing - P.R.China
>>
>> 北京红旗中文贰仟软件技术有限公司
>> 地址:北京经济技术开发区(亦庄)西环南路18号汇龙森A座二层
>> 邮编:100176
>>
>> 电话/Tel: +86-10-51570010 ext.6183
>> 邮箱/e-mail: peterjunge@RedOffice.com
>> http://www.RedOffice.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>> --
>> This message has been scanned by DST MailScanner
>>
>>
>>
> 

-- 
Peter Junge
Open Source Strategy Director

Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan Nanlu
Beijing Economic-Technological Development Area
100176 Beijing - P.R.China

北京红旗中文贰仟软件技术有限公司
地址:北京经济技术开发区(亦庄)西环南路18号汇龙森A座二层
邮编:100176

电话/Tel: +86-10-51570010 ext.6183
邮箱/e-mail: peterjunge@RedOffice.com
http://www.RedOffice.com


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