OCDS 1.2 Announcements

[jpmckinney]

Today, we kick off the development of the next minor release of the Open Contracting Data Standard, OCDS 1.2.

In a blog post, we briefly describe:

• What went into versions 1.0 and 1.1
• What we expect to cover in version 1.2
• What the process looks like

English: https://www.open-contracting.org/2020/10/14/ocds-1-2-we-want-to-hear-your-proposals/

Español: https://www.open-contracting.org/es/2020/10/14/ocds-1-2-queremos-escuchar-sus-propuestas/

The first step is to propose any additional issues to address by 28 October. All existing issues that can be resolved in a minor release are already collected into the 1.2.0 milestone. If there is something outside that list that you would like to see changed, please create an issue on GitHub. If you are new to GitHub, you can watch a recording of our introduction to GitHub, review the slides, or use this handout.

To get updates about the process, please subscribe to the standard-discuss mailing list or to this issue.

We look forward to active participation of the OCDS community throughout this process.

[jpmckinney]

Two weeks ago, we kicked off development of the next minor release of the Open Contracting Data Standard, OCDS 1.2.

In a new blog post, we go into more detail on the priorities for OCDS 1.2.

English: https://www.open-contracting.org/2020/10/27/ocds-1-2-what-well-be-working-on/

Spanish: https://www.open-contracting.org/es/2020/10/28/ocds-1-2-en-lo-que-estaremos-trabajando/

This marks the second step of the governance process, initiating a two-week period in which anyone can discuss whether to include issues that were left out, or remove issues that were added in, by 11 November.

The next step will be to solicit input on and propose solutions for the prioritized issues. To contribute to any of the topics in the blog post, please follow the links to comment on the associated GitHub issue.

We need expert input from the community of OCDS publishers and users to ensure that the proposed changes will improve the OCDS for everyone.

[jpmckinney]

Several new issues were created up to November 11. They were all assigned to an appropriate milestone.