Next in thread → Next in month →

Re: [office-requirements] Groups - requirements_draft_03_06_2009.odsuploaded

From
robert_weirAus.ibm.com
Date
2009-06-04T20:29:01+00:00
ID
Thread
Re: [office-requirements] Groups - requirements_draft_03_06_2009.odsuploaded
I'll close the duplicate version of this, keeping your version, since it 
has a proposed resolution.

And Bob should note that I'm still going through the legacy comments, 
categorizing them.  Although I've already indicated the ODF-Next comments 
that came during the formal call for comments, I am finding more among the 
older comments, ones where the TC had agreed to defer to "ODF 1.3".  So 
I'm assigning these to ODF-Next as I find them.  It will probably be 
another 2 weeks before I've processed all of these.

-Rob


Peter Junge <> wrote on 06/04/2009 06:54:43 AM:
> 
> Re: [office-requirements] Groups - requirements_draft_03_06_2009.ods 
uploaded
> 
> Bob, Rob,
> 
> the issues:
> http://tools.oasis-open.org/issues/browse/OFFICE-1278
> and
> http://tools.oasis-open.org/issues/browse/OFFICE-1503
> are certainly duplicates.
> 
> 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?
> 
> Best regards,
> Peter
> 
>  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 copyand 
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£º 
> 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 
>
Next in thread → Next in month →