Differences between revisions 68 and 69
Revision 68 as of 2012-07-17 15:35:25
Size: 4681
Editor: ElenaBlanco
Comment:
Revision 69 as of 2013-04-15 13:56:22
Size: 4683
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Although we do our best to ensure that our wiki content is valuable, the documents within it have not undergone our rigorous [http://www.oss-watch.ac.uk/resources/lifeofadoc.xml Quality Assurance] process. Although we do our best to ensure that our wiki content is valuable, the documents within it have not undergone our rigorous [[http://www.oss-watch.ac.uk/resources/lifeofadoc.xml|Quality Assurance]] process.

Although we do our best to ensure that our wiki content is valuable, the documents within it have not undergone our rigorous Quality Assurance process.

Often, documents that are intended to become briefing notes on our website start life in the wiki. This page records which briefing notes are currently in production. It also records the briefing document that each OSS Watch team member is likely to write next. Finally, it records proposed briefing notes so that there is a pot of suggestions ready to be allocated once a document has been finished.

Assigned Documents

This section records all the document that have been assigned regardless of whether they are being developed in the wiki or using other workflows. The allocated date allows us to keep track of how long it is since the document was assigned to the author. The deadline is the latest agreed date for circulation of a polished draft for team review. The "To Elizabeth" deadline is the date that the doc needs to be with Elizabeth for editing in order to make the deadline for team review.

Author

Document

Description

Allocated

To Elizabeth

Deadline

Comments

Rowan

Total Cost of Ownership

Gabriel

Video doc

Doc pulling together video material to illustrate key points of our advice

Jan 2012

Sander

Sustainability advice

Extracting generic text and advice from the 7 sustainability case studies

April 2011

1 June

15 June

Team to help by each reading one case study and identifying one or two salient points

Pending Documents

These docs have been agreed as the next document for each author. Work will only start on the next doc once the assigned doc has been finished. From August 2010 all documents will need to relate to the support plan (authors will need to demonstrate relevance, GH to decide priorities in relation to the support plan).

Author

Document

Description

Rowan

Gabriel

Sander

Proposed Documents

At each month's review day any author can request that their current pending doc be replaced with a proposed doc. This is a way for us to respond to new demand or changing priorities for a specific doc. Team members can suggest proposed documents at each review day but GH will determine whether they are necessary for the support plan. Only documents that relate to the support plan will make it onto this list.

Potential author

Document

Description

Comments

ET?

Open source in your IT strategy

Extracting key points from mindmap

What is a Fork?

http://osswatch.jiscinvolve.org/wp/2007/10/05/use-the-fork-luke/

Ross

Additional consultancy services OSS Watch can provide

Should go into 'about us' page

GH

Eclipse foundation doc

SL

A week in the life of an OS project

GH

Do I need a foundation?

Short doc simply outlining pros and cons of using a foundation for your project

Workflow

We have simplified the workflow so that the two content editors can work in a more coordinated way. These are the rules:

  • Each team member has one and only one document allocated
  • Each team member has an allocated 'next document' - known as a pending document

Note: where we say 'each team member' we means those team members who are charges with producing briefing notes

At each review day (ie monthly) we discuss:

  • Progress of each allocated doc
  • For anyone who has published a doc since the last review meeting we move the pending doc to the allocated doc and agree a due date. We also allocate a new pending doc from the proposed docs list
  • Anyone can make a case for swapping their current pending doc with a doc from the proposed list - will be agreed or not by content editors
  • Anyone can make a case for swapping another team member's pending doc with a doc from the proposed list (this may be due to feedback/request from a third party or dependency on something they are doing) - will be agreed or not by content editors with reference to support plan priorities

Ideally, a document should be developed in the wiki. Deal directly with Elizabeth, who will help you get it to a stage where it is ready to be considered as a briefing note. Since all documents should be seen by a content editor before being considered ready to become a briefing note we no longer need to worry about whether a document is nominated, a candidate etc.

OSSWatchWiki: BriefingNoteSchedule (last edited 2013-04-15 13:56:22 by localhost)

Creative Commons License
The content of this wiki is licensed under the Creative Commons Attribution-ShareAlike 2.0 England & Wales Licence.

OSS Watch is funded by the Joint Information Systems Committee (JISC) and is situated within the Research Technologies Service (RTS) of the University of Oxford.