New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TC Minutes - DRAFT to prep Markup TEMPORARY #474
Comments
Technical Committee – annual meeting May 2018 – DRAFT minutes 1 Opening and introductions Delegates: 3 Technical infrastructure: status and plan for future management and operation SO - We have a CLA is place that has been legally vetted. The next step is to get internal sign-up. JT and RGr, what level does sign-up need to be, individual or organisation? JT - We have had voice that it should be at organisation level. RGr - OK too. SO - what level of authority does it need to be? JT - Someone with authority to Intellectual property (IP) away. SO - What is the time-scale in which sign-up be achieved? JT - last year. SO – So how about we do this is 2 months, by end of July 2018? RESOLUTION – Outstanding Contributor Licence Agreements (CLA) to be signed by end July 2018 RESOLUTION – The TC agreed that the secure DropBox service for storing completed CLAs would b. Is the code of conduct being applied? SO - We have our scope, enforcement and attribution. Is there is anything that needs to change or be added? JT - noted that when people are signing the code of conduct they are also committing to the technical rules. No responses from attendees. Therefore, the review of the code of conduct is complete.
JT - part of the Code of Conduct is to challenge anyone that is not following it by raising it with the TC Chair.
A new action to align web site page information on technical rules, code of conduct and development process was agreed
JT – It would be good to ask ED to deploy the PoC onto AWS servers that UK Met Office manages to enable an engineer to understand how to deploy OpenWIS. |
Closed by #477 |
Jude to insert text
The text was updated successfully, but these errors were encountered: