Actions open at 13th September 2016

Technical Committee (TC)

  • Sep ACTION-TC-2016-47: LM/NM/GT/DP/DG - Join the GeoNetworks developer mail-list.
  • Sep ACTION-TC-2016-46: LM - Circulate the url of the portal on Proxmox.

  • Jul ACTION-TC-2016-44: RG - Will send round an email with the team contact email address.

  • Mar ACTION-TC-2016-30: WQ - Trial TC by Webex.
  • Mar ACTION-TC-2016-28: PR - Include tasks on the Kanban board to cover: docs, open source community activities, setting up a web site etc.
  • Mar ACTION-TC-2016-25: WQ - TC to set a task to develop onboarding docs set for developers.
  • Mar ACTION-TC-2016-24: PR - Propose a Kanban workflow for v4 development work.
  • Mar ACTION-TC-2016-23: JT - Include the requirement for the Security Service to control data access in the Data Policy workpackage.
  • Mar ACTION-TC-2016-22: RGr - Create a work package to review Data Policy and Access Control implications in detail.
  • Mar ACTION-TC-2016-21: RGb - Investigate how to link the data policy in the metadata with the assignment of GeoNetwork privileges.
  • Mar ACTION-TC-2016-20: JT - Create a work package for WMO metadata guidance templates.
  • Mar ACTION-TC-2016-19: BB - Ask Simon Pigot for an update.
  • Mar ACTION-TC-2016-18: JT - Create work package on UI improvement for bulk subs.
  • Mar ACTION-TC-2016-17 ALL: make NWS aware of our requirements for Eclipse.
  • Mar ACTION-TC-2016-15: RGb: draft a User Story for the User Portal subscription process.
  • Mar ACTION-TC-2016-14: JT - Revisit the GeoCat code packaging.
  • Mar ACTION-TC-2016-13: WQ - document the design pattern policy; still deploy to wildfly in short/medium term.
  • Mar ACTION-TC-2016-9: LM - update the install guide (#6).
  • Mar ACTION-TC-2016-8: LM - update the install guide (#3).
  • Mar ACTION-TC-2016-7: RGr - Check with Francois that #32 is fixed.

Steering Committee (SC)

  • Mar ACTION-SC-2016-33: JT - Set a date for the next SC in June 2016.
  • Mar ACTION-SC-2016-32: EE - Check with Michael Robbins for fees related to trademarks.
  • Mar ACTION-SC-2016-31: BB - Will help develop a value proposition. But I’m not ideal; people in WMO have that experience, so I will ask around to see if I can identify the right
  • Mar ACTION-SC-2016-30: JT - Let’s put targeted communications on the agenda for the next SC meeting.
  • Mar ACTION-SC-2016-29: OL - Come up with an appropriate name.
  • Mar ACTION-SC-2016-28: JT - To write a strategy paper on: Where we can deliver the most value for the broader community in the near future.
  • Mar ACTION-SC-2016-26: RGib - Provide to the Association the feedback received so far from users to TC and SC.
  • Mar ACTION-SC-2016-25: RGib - Improve the existing web-site (nothing grand).
  • Mar ACTION-SC-2016-24: LLG – Clarify in the communications plan.
  • Mar ACTION-SC-2016-23: RGib - email info about who is using OpenWIS to both TC and SC.
  • Mar ACTION-SC-2016-22: JT - Come up with suitable method for managing CLAs. Bring back to SC to approve by correspondence. Update CLA process and forms if approved.
  • Mar ACTION-SC-2016-21: JT/PR - Work with Michael to determine legal validity in all territories of a click-through online CLA - and validity under Belgian law. Refer to legal contact of IRM?
  • Mar ACTION-SC-2016-20: JT/PR - Talk to Michael Robbins about whether an umbrella agreement would have legal standing.
  • Mar ACTION-SC-2016-19: RGir - Investigate appetite for a project proposal with DWD.
  • Mar ACTION-SC-2016-18: MDA - Find out if NMS Canada is interested in bringing MetPX under the OpenWIS umbrella.
  • Mar ACTION-SC-2016-17: WQ - To do a project proposal relating an investigation work package for the OpenWIS Core.
  • Mar ACTION-SC-2016-16: JT - Clarify articles that may appear to force other people to pay for your project.
  • Mar ACTION-SC-2016-15: WQ(TC) - Define the roles in the development process - see JT doc.
  • Mar ACTION-SC-2016-14: PR - RISK for Board Risk Register - That the articles of the Association are not fit for purpose regarding, particularly: Article 14.1 Architecture role of TC, Article 9.1 No mention of contributors, Article 21.2 Indemnity of partners and contributors.
  • Mar ACTION-SC-2016-13: JT (through Michael Robbins) get legal advice on whether the articles shelter the contributors from litigation.
  • Mar ACTION-SC-2016-12: JT - Make sure the role of User is clear in the internal rules.
  • Mar ACTION-SC-2016-10: JT - As part of going open source we need a Communications Plan.
  • Mar ACTION-SC-2016-08: MDA/JT will award Leon a certificate as formal recognition of his contribution.
  • Mar ACTION-SC-2016-07: WQ - TC to review the use of these servers in Jan 2017 and decide whether to extend.
  • Mar ACTION-SC-2016-05: PR - Do some more detailed tasking around production of docs for open source.
  • Mar ACTION-SC-2016-04: WQ - TC to agree lifecycle patching strategy.
  • Mar ACTION-SC-2016-03: WQ – TC to define ‘patchable’.
  • Mar ACTION-SC-2016-02: WQ – Define ‘good test coverage’ as a percentage (with TC).
  • Mar ACTION-SC-2016-01: PR - make a proposal for Kanban backlog and metrics, agree with TC and then circulate to SC.

Annual Meeting (AM)

  • Mar ACTION-AM-2016-07: MDA – Establish a Risk Register for the OpenWIS Association AISBL.
  • Mar ACTION-AM-2016-06: EE - Remove the 30 day rule about budgets from the Internal Rules annex.
  • Mar ACTION-AM-2016-05: EE – Amend the Internal Rules annex to recommend due diligence when purchasing.
  • Mar ACTION-AM-2016-04: EE – Amend the Internal Rules annex to oblige the seeking of quote(s) or estimate(s) and sending them to the Treasurer prior to entering contractual arrangements.
  • Mar ACTION-AM-2016-03: MDA - Talk to ING contact on return to France.
  • Mar ACTION-AM-2016-02: JT/SC - agree smart metrics for each goal by June SC.
  • Mar ACTION-AM-2016-01: WQ/PR - draft a process for separating PMC/TC tasks into appropriate meetings.

Actions closed by 13th September 2016

  • Jul ACTION-TC-2016-45: SO - Will email round the address of the Developer Workshop venue.
  • Jul ACTION-TC-2016-43: SO/MGo/MGi - will speak on Friday morning (8/7/16).
  • May ACTION-TC-2016-42: MGo/LM Set up OpenWIS v4 on the MF cloud servers, by the next TC if possible.
  • May ACTION-TC-2016-41: RG - Give MGo/LM access to the MF cloud servers.
  • May ACTION-TC-2016-40: MG - Ask the CM Team to open up OpenWIS 4.x so everyone else can take a look.
  • May ACTION-TC-2016-39: MG - Raise a pull request for the script.
  • May ACTION-TC-2016-38: PR - Ask Michael Robbins for legal advice.
  • Apr ACTION-TC-2016-34: LM - Provide some developer docs on how to set up the development environment using a combination of vagrant and puppet.
  • Apr ACTION-TC-2016-33: LM/PR - draft a backlog for the next TC.
  • Apr ACTION-TC-2016-32: RG - Put the configuration script onto GitHub.
  • Apr ACTION-TC-2016-31: PN - ask the UKMO OpenAM team if there are any schema changes to worry about.
  • Mar ACTION-TC-2016-29: PR/LM - pass on lessons from the last Dev Con.
  • Mar ACTION-TC-2016-27: PR - transfer backlog and Github issues for v 4 to a Kanban board.
  • Mar ACTION-TC-2016-26: PR - Investigate/arrange a Markdown to html publication process.
  • Mar ACTION-TC-2016-16: JT: share the GeoCat docs.
  • Mar ACTION-TC-2016-12: MGo - Set up Jenkins emails for the TC mail list only.
  • Mar ACTION-TC-2016-11: ALL - do end-to-end tests in own environments for the 3.14 release.
  • Mar ACTION-TC-2016-10: MGo - send info on how to access the cloud testing to Francois.
  • Mar ACTION-TC-2016-6: MGo - Raise a new issue.
  • Mar ACTION-SC-2016-27: RGir – prepare a presentation.
  • Mar ACTION-SC-2016-11: JT - Publish Articles, Internal Rules and Board etc on our website.
  • Mar ACTION-SC-2016-09: WQ - Confirm that Leon will continue in the role for the next 12 months.
  • Mar ACTION-SC-2016-06: - BR - Put someone at UKMO in touch with ECMWF about using [PALAMIDA][BR1]