This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6252?nav=1&selectedTab=comments at Sun, 06 Nov 2022 08:46:56 GMT SourceForge : artf6252: 6025: Open Grid Forum Document Process and Requirements

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Tracker
Project: Editor     Trackers > Published > View Artifact
Artifact artf6252 : 6025: Open Grid Forum Document Process and Requirements
Tracker: Published
Title: 6025: Open Grid Forum Document Process and Requirements
Description:
This tracker replaces broken tracker http://forge.gridforum.org/sf/go/artf6025?nav=1

This is an update to GFD-C1.

Submitted By: 	Greg Newby
Submitted By: Greg Newby
Submitted On: 07/28/2008 3:25 AM EDT
Last Modified: 10/12/2009 12:54 AM EDT

Status / Comments Change Log Associations Attachments (6)  
Status  
Group: * GFSG
Status:* Closed
Category: * Community Practice
Customer: *
Priority: * 1
Assigned To: * Greg Newby
Reported in Release: *
Fixed in Release: *
Estimated Hours: * 0
Actual Hours: * 0
resolution: * Accepted
Comments
Greg Newby: 10/12/2009 12:54 AM EDT
  Action: Move
Moved from Submit OGF Draft to Published
resolution set to Accepted
Status changed from Ready to Publish to Closed
Greg Newby: 10/12/2009 12:35 AM EDT
  Action: Update
Assigned To changed from Joel Replogle to Greg Newby
Priority changed from 2 to 1
Greg Newby: 06/09/2009 10:38 AM EDT
  Comment:
The GFSG discussed this June 9.  This document will now be published as GFD-C-P.152.

Document GFD-C-P.1 will be obsoleted.
  Action: Update
Assigned To changed from Chris Smith to Joel Replogle
Status changed from GFSG Review: Last call to Ready to Publish
Greg Newby: 05/26/2009 3:36 PM EDT
  Comment:
Public comment is complete.  There were several comments, but none seem to require changes.  (Comments from a prior round were already attended to.)

This can now go to standards council final call, prior to publication.
  Action: Update
Assigned To changed from Joel Replogle to Chris Smith
Priority changed from 3 to 2
Status changed from Public Comment Period to GFSG Review: Last call
Greg Newby: 04/22/2009 1:31 PM EDT
  Comment:
The public comment tracker is here: http://www.ogf.org/gf/docs/comment.php?id=294
  Action: Update
Joel Replogle: 03/25/2009 3:14 PM EDT
  Comment:
Re-entered public comment 2009-03-25
  Action: Update
Greg Newby: 03/24/2009 3:42 PM EDT
  Comment:
For completeness, this file has Word's "track changes" active.
  Attachment: draft-gwdc-gfsg-c1-v8-trackchanges.doc (158 KB)
  Action: Update
Added an attachment.
Greg Newby: 03/24/2009 3:42 PM EDT
  Comment:
Next draft attached.  This is now ready for 60-day public comment, per the GFSG.
  Attachment: draft-gwdc-gfsg-c1-v8.doc (136.5 KB)
  Action: Update
Added an attachment.
Assigned To changed from Greg Newby to Joel Replogle
Priority changed from 4 to 3
Status changed from Author Action Needed to Public Comment Period
Greg Newby: 02/13/2009 2:19 PM EST
  Attachment: draft-gwdc-gfsg-c1-v7-trackchanges.doc (204.5 KB)
  Action: Update
Added an attachment.
Greg Newby: 02/13/2009 2:18 PM EST
  Comment:
This is now in mailing list last call, to the GFSG.  New versions are uploaded.
  Attachment: draft-gwdc-gfsg-c1-v7.doc (197.5 KB)
  Action: Update
Added an attachment.
Greg Newby: 02/04/2009 8:47 PM EST
  Comment:
The standards council discussed this document on February 3.  A next iteration is forthcoming, for public comment.
  Action: Update
Greg Newby: 09/27/2008 2:45 PM EDT
  Comment:
The document was discussed @ OGF24 in Singapore, and next steps have been specified.  A newly revised document is forthcoming...
  Action: Update
Greg Newby: 08/25/2008 6:31 PM EDT
  Comment:
The standards council will discuss the extent of 
public access to written reviews, as well as the
mechanisms for collecting public comments.  This
discussion will happen at OGF24 in Singapore.  

Hopefully after that the document will be
ready for the next (final?) round of public comment
prior to adoption.
  Action: Update
Greg Newby: 08/07/2008 7:52 PM EDT
  Comment:
Version 5 submitted; sending to standards council for input.  The major changed text is to streamline the process of going to a full recommendation.

4.5.3 Grid Recommendation

Once a document is published as a Proposed Recommendation, a 24-month
timer will begin. During this period it is expected that operational
experience will be gained.  Typically, this will mean that at least
two interoperable implementations (from different code bases and, in
the case of licensed code, from two separate license agreements) must
be demonstrated (if appropriate).  The entire protocol or
specification should be implemented in the interoperable
implementations. If needed, the AD and relevant Council will determine
whether interoperable implementations (or implementations in software
at all) are necessary or whether operational experience can be gained
in a different fashion.

A document must remain at the GFD Proposed Recommendation level for a
minimum of 6 months before it is eligible for advancement to a Grid
Recommendation.

Within the 24-month period that begins with publication as a Proposed
Recommendation, operational experience must be documented in the form
of published documents, preferably one or more Experimental documents.
When sufficient operational experience has been achieved and
documented, an expert review will be solicited.  Expert reviewers
should not be document authors or otherwise have a conflict of
interest.  More than one expert review may be desirable.  The review
may be solicited by any interested party, not only the document
authors and editors.  However, including the athors/editors in the
review process, if possible, is desirable.  Depending on the subject
matter, expert review may be desired from relevant standards bodies
(such as the W3C or IETF).

The review will provide input to the relevant Council in determining
whether the Proposed Recommendation should (a) become a Grid
Recommendation, (b) remain at the same status level, or (c) be moved
to obsolete or historical status.  In any case, the relevant Area
Director(s) will briefly summarize the reasoning of the Council, also
providing this summary to the group chairs and/or authors.  While a
formal solicitation for public comments will not typically be made,
the OGF will advertise the document’s status in moving to
Grid Recommendation, so that interested parties can provide input.

Small changes (as described in the Errata section below) may be
applied from the Proposed Recommendation to the Grid Recommendation,
but these should be used with caution, and changes that would impact
interoperability should be avoided.  If substantive changes are
needed, a new Proposed Recommendation must be developed.

When a Proposed Recommendation document has not reached the Grid
Recommendation level after twenty-four months, and every twelve months
thereafter until the status is changed, the Council will review the
viability of moving to a Grid Recommendation. Following each such
review, the Council will decide whether to maintain the specification
at the same maturity level or to move it to obsolete or historical
status (thereby removing the Proposed Recommendation from further
consideration to advance). This decision will be communicated to the
OGF to allow the OGF community an opportunity to comment. This
provision is not intended to threaten a legitimate and active working
group effort, but rather to provide an administrative mechanism for
terminating a moribund effort.


4.5.4 Summary of Document Processing for Grid Recommendation Documents

A document may be returned to an earlier phase of the document
process, if deemed necessary.

1. Passage of time: At least 6 months since publication as a GFD-R-P
          must pass.

2. Document review: A written expert review, summarizing operational
          experience and documents published that reflect the
          readiness of the document to become a Grid Recommendation.
          Other parties may solicit this on behalf of the document
          authors.  It may be submitted to the document authors, the
          AD, or directly to the OGF Editor.

3. Process check: When document authors or other interested parties
          inform the OGF Editor of the desire to move the document to
          Grid Recommendation status, the Editor will check that
          requirements are met and seek consensus from the AD that the
          document is ready for advancement to Grid Recommendation.

4. Final document preparation: If small changes are sought to the
          final document, the submitters must propose them in the form
          of a replacement document.

5. Public notice: The Editor will inform the OGF community of the
          intention to move the document to Grid Recommendation,
          including a summary of or link to the expert review.

6. Final review: The AD will present the result of the review and all
          other evidence (such as Experimental documents) to the
          appropriate Council, with a recommendation for whether to
          change the status to a Grid Recommendation.  The Council
          will be given 15 days to read and comment on the document.
          At the end of that period, the AD will gain consensus as to
          whether the document is acceptable for advancement.

7. Republication: The OGF Editor will replace GFD-R-P with GFD-R in
          the document, and apply any other needed changes.  The
          Editor will inform the OGF community of the new document.
  Attachment: draft-gwdc-gfsg-c1-v5.doc (203.5 KB)
  Action: Update
Added an attachment.
Greg Newby: 07/28/2008 3:26 AM EDT
  Comment:
This needs a few more changes, then will go for another round of public comments.
  Action: Update
Greg Newby: 07/28/2008 3:25 AM EDT
  Comment:
Prior tracker comments:

 	

cmnt20084       artf6025        Sorry, wait - there is another minor change to make. No public comment yet.     2008-06-22 21:18:30-05          
trxn41B6B5B5011AB32D851AF76C    user3483
cmnt20083       artf6025        At OGF23 in Barcelona, the GFSG accepted the changes to this document. Because they are substantial, we are sending 
this for another 60-day round of public comments.   2008-06-22 21:16:22-05  trxn41B6B5B5011AB32D851ADC8C    user3483
cmnt19989       artf6025        Version 4, submitted for final GFSG review.    2008-05-29 23:24:01-05   trxn41B6B5B5011A37A0F5FCB837    user3483
cmnt19805       artf6025        Update from the author/editor (me): next draft is expected by OGF22.    2008-02-12 20:22:03-06  
trxn41B6B5B50118106B189C2688   user3483
cmnt19755       artf6025        Comments will be addressed in a new document, forthcoming shortly.      2007-12-31 12:01:33-06  
trxn41B6B5B5011731576E412043   user3483
cmnt19723       artf6025        Public comment is complete. Review comments here: https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf
-editor/discussion.cp_ogf_document_process        2007-12-11 14:37:17-06  trxn41B6B5B50116CADDBCD9382B    user3483
cmnt19553       artf6025        Move document into public comment.      2007-10-02 11:24:35-05  trxn41B6B5B50115616AA079542E    user2590
  Action: Update
Greg Newby: 07/28/2008 3:25 AM EDT
  Attachment: draft-gwdc-gfsg-c1-v4.doc (181 KB)
  Action: Create
Added an attachment.


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6252?nav=1&selectedTab=comments at Sun, 06 Nov 2022 08:46:56 GMT