search

open-contracting / ocdskit

A suite of command-line tools for working with OCDS data
https://ocdskit.readthedocs.io
BSD 3-Clause "New" or "Revised" License
17 stars 7 forks source link

Migrate scripts from standard and public-private-partnerships #19

Closed jpmckinney closed 6 years ago

jpmckinney commented 6 years ago

For standard, see https://github.com/open-contracting/standard/issues/631

Bjwebb commented 6 years ago

For our OS4D work we discussed moving scripts, particularly translation scripts, into a generic repo. However we only use them for OCDS (standard & PPPs) at the moment, so moving all the scripts into ocdskit probably makes most sense for now.

Bjwebb commented 6 years ago

Moving scripts to ocdskit should mean we no longer need to have the OCDS standard repo as a requirements of the PPPs repo - https://github.com/open-contracting/public-private-partnerships/blob/master/requirements.txt#L35-L36

jpmckinney commented 6 years ago

@Bjwebb @robredpath Where in the timeline is moving scripts from the standard repo to this repo (or whatever consolidated repo)?

robredpath commented 6 years ago

@Bjwebb any sense of scale on this? Not sure how far down the dependency rabbit hole this will take us. Hours/days/weeks/months/years?

Bjwebb commented 6 years ago

This should be a matter of hours.

jpmckinney commented 6 years ago

What does OCDS for PPPs depend on from the standard repo?

Bjwebb commented 6 years ago

I think it's just these two babel extractors https://github.com/open-contracting/standard/blob/1.1-dev/setup.py#L9-L10

jpmckinney commented 6 years ago

ocdskit may not be the best home for those, but perhaps one of the OCP or ODS Sphinx repos?

jpmckinney commented 6 years ago

Opened https://github.com/open-contracting/ocds_sphinx_directives/issues/7