Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
2018 DAC CRS codelist updates #249
This PR is two months old now, with no response. It looks to me like a relatively trivial update.
Furthermore, the contents of the update is 6 months old. In fact, there’s also a new update from DAC waiting.
Could someone from @IATI review and merge this, please?
Many thanks for your response, @samuele-mattiuzzo!
This can be treated as independent of #172 (see below for details on this).
This PR represents updates to some replicated (third party) codelists maintained by the DAC. It’s equivalent to #231 (a similar update from last year).
There’s a process for management of these codelists:
#172 was used to generate this. It’s a script to fetch these (and other) codelists from managed sources, so that someone (ideally someone who isn’t me) can more easily keep an eye on them and keep them up-to-date.
I’m guessing (but no-one has actually told me this) that #172 is blocked while the secretariat waits to see what’s going on with the DAC publishing IATI XML, perhaps with a view to dropping these codelists from the IATI standard? But I’m guessing – I really don’t know. @PetyaKangalova would know better.
@samuele-mattiuzzo My intention wasn’t to point out how old this PR is! It was more to flag that there’s a process for non-embedded codelist management that doesn’t appear to be being followed here – without any explanation why.
Bill has said the plan is to move towards a new sustainable process for updates, which I support (in fact I’ve done some work to that effect!) But I don’t see why that would be a blocker for these updates.
If it’s possible to shed a bit more light on the blockers here, or give some indication of when this might be merged, that would be great.