Open Database License/Implementation Plan

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. Worked on implementation plan following partial review of plan comments.

6th March

• Working group meeting. Additional work on implementation plan. What If scenario planning.

12th March

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

?? March

• Date unknown, Jordan (the author of the ODbL) has said he will publish a further draft on the comment site based on the comments received, before the end of the comment process. We don't know when that date will be.

20th March

• End of OpenData Commons' ODbL 1.0 comment period. This is the close of the comment period on the ODbL *only* and this is driven by its author and its home at the OKFN. This is not the close of comments on how, when and if OSM adopts that license.

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 first considers endorsing licence and asks OSMF members (as of 23rd January) to vote (2 week, after 1 week we will send out a reminder to people who haven't yet responded) on whether ODbL 1.0 should be put to the community for adoption.
• If the OSMF so decides, it will send an email to OSMF members.

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

+ 2 weeks

• 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. (no decision to actually remove data from the central database yet... ) 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.
• Large data imports where permission has been given previously (AND, GeoBase etc) are asked formally to agree to release their data under the ODbL. (informal communications ongoing lead up to this point led by the working group and the groups/individuals who worked on the imports).

+ 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. Community Question... What do we do with the people who have said no or not responded?
• A final planet.osm export of the database under the CC-BY-SA license will be published and will be made available for an indefinite period.