Open Database License/Implementation Plan

From OpenStreetMap Wiki
< Open Database License
Revision as of 00:29, 4 March 2009 by Firefishy (talk | contribs) (→‎2nd March: Fix date - Meeting hasn't happened yet)
Jump to navigation Jump to search

All dates approximate for review.

License Plan

27th February

  • This draft adoption plan made public to legal and talk list with the draft license text made available by the Open Data Commons (with facility for comments back) . Local contacts asked to assist in passing on the message, and subsequent announcements.

5th? March

  • Working group meeting. Finalise implementation plan following review of plan comments; What If scenario planning.

12th March

  • Working group meeting. Review of community feedback received to date.

20th March

  • End of ODbL comment period.

28 March

  • ODbL 1.0 is expected to be released by Open Data Commons at The Open Knowledge Conference (OKCon) London event.

31st March

  • OSMF Board endorses licence and asks OSMF members (as of 23rd January) to vote (1 week) on whether ODbL 1.0 should be put to the community for adoption.

What follows is based on a positive response from the OSMF members...

+ 1 week

  • Website only allows you to log in and use API when you have set yes/no on new license. New signups agree to both licenses. Sign up page still says dual licensing so that we can release planet etc. People who have made zero edits are automatically moved over to new license and are emailed a notice.
  • Website to allow users to voluntarily agree to new license. Design allows you to click yes, or if you disagree a further page explaining the position and asking to reconsider as there may be a requirement to ultimately remove the users data. This will help stop people accidentally clicking 'no'. Sign up page now states you agree to license your changes under both CCBYSA and also ODbL.

+ 2 weeks?

  • Require people to respond to the licensing question. How? Should we deny API access otherwise?

+1 month

  • Working group meeting. Assessment of number of no responses and number of people who haven't said either way. Emails ready to send to contact those who have not clicked yes or no. Personal outreach to those who have said no.

+ 2 months

  • Final cut-off. What do we do with the people who have said no or not responded?