-
Notifications
You must be signed in to change notification settings - Fork 92
Collaboration Call: February 22, 2019
brockfanning edited this page Mar 6, 2019
·
1 revision
UK team
- Lots of inward facing work like feature branches and testing
- Chris is working on test maps
- Changes to the reporting statuses, allowing for custom workflows so that people have more flexibility in their options. Could be a helpful feature for Open SDG.
- Still working on Google Analytics and SDMX
- Backing up their CODE on GitLab. Could be discussed to back up the Open SDG code on their own GitLab platform or find a way to back up the site somewhere else
US team
- Working on disaster recovery plans, like the UK. Kali could call in from NY for the next call to chat about it.
CODE team
- Added some tagging functionality to the site so that people can add tags to the indicators. Brock is working on expanding this to multilingual.
- Added the UN color wheel for the logo. It is on the GitHub and the Open SDG platform. Could also be used for blog posts and other comms.
- Created a demo repository of Open SDG in different languages. The link is at the next steps at the bottom of the page. Could be helpful to see how platforms would look with different languages. US is planning on just using the UN official languages but Kali would like another independent check before launching. Brock will send the links and the files for the translations to Kali. Links:
- Provided more documentation for data providers to describe how to edit data and metadata on GitHub. Also hoping to do a video of the same thing with simple language and some subtitles.
- Kali: it could be helpful to have a video of how to fork as well.
Country/subnational interest in cloning the NRP
- UK been doing remote work with Rwanda. Been doing QA and testing for the launch. Hoping to have some test maps on there for next week.
- UK has python scripts to help and has been sharing with countries but it may be helpful to open more broadly.
- Brock has imported Germany’s translation and they have been imported into the project, along with Armenian.
- Brock worked with Armenia to fix the goals page and some other issues. Almost ready to point the data providers to the site to start loading data. Brock will send the link. Their site will be using Armenian and Russian. They haven’t made any corrections to the Russian translations.
- Kali: make sure that the indicators are consistent across platforms, if any of the indicators, goals, or targets change.
- ONS has a partnership with Kenya. The contact in Kenya, Caroline, is interested and they may contact them in late March.
- Poland is OK to add a note to the community page. They are not technically using Open SDG but a previous version so we need to think about how to talk about it and what text to use.
- There is an opportunity to present something to the SDMX working group. Ann needs a country experience from someone who is using SDMX and could share it. Could help if we presented so we could talk about SDMX and Open SDG.
- Coordinating to set a target date to make public announcements about the platform.
- Ann - depends on how long it takes for us to prepare standard text and case studies. Can’t think of any events that would be helpful to coordinate with right now. But would like to do their assessment of the platform before the release. They are bringing in reviewers in April to ensure the platform follows the “Leave No one Behind” and other UK government standardsso they would prefer they do it after.
- US -
- Phil should flag with his office before putting it out there. But doesn’t think there is a time frame that they would need to follow
- Kali - any SDG related issues, including the reporting platform should got through the US chief statistician
- 3 contacts - generic address, Kali, then Phil
- Organizations and governments reaching out to set up the platform. Who should be the contact person, especially after the CODE grant runs out?
- Ann said she would like input from DFID and ONS. Ann can get some text on how to talk about that and how they could provide support.
- She would also like to focus on the resources so that it is easier for people to fork.
- Kali - they are often approached directly but not needed to market it. If it is mentioned then they can approach the US.
- Brock - documentation and code of conduct. Could add an email address on it. Who should that be?
- General consensu - Not sure who it should be so it will be brought up at the next meeting.
- Ann said she would like input from DFID and ONS. Ann can get some text on how to talk about that and how they could provide support.
- Slide deck would be a good idea to help promote and have people to share it
- The Open SDG use of the logo is not approved but it doesn't break any of the rules for use.
- Country case studies
- Who would write them and how should we do them?
- Ann- need a standard template that we can share with them to do. Could start with Rwanda and Ghana to add the information then send to them to fill out. Would then iterate through the template to make sure that they have enough information.
- CODE can draft the template
- Social media
- Developing GIFs and visuals could be done by ONS who could help with this.
- The examples could be UK based
- Short tutorial videos to explain the platform
- This was discussed earlier on the call and CODE can take the lead on these.
- Expanding the FAQs
- We have some good information there but it may be helpful to expand to have some more examples and links so that people can see examples of what these look like.
- There are also questions about APIs and other things that would be helpful to include
- We have some good information there but it may be helpful to expand to have some more examples and links so that people can see examples of what these look like.
- CODE will review the comments on the comms plan and throw out some target dates for releasing the platform along with the notes.
- To consider: Is there a single email address that we should put on the Code of Conduct page?
- Brock's next steps:
- Look into rubygems.org and the possibility of removing Jekyll plugins from site repositories
- Look into translation of site configuration, and metadata and data
- Investigate SDMX API with Cambodia example
- Follow up about build-time GeoJSON specs
- Look into what open-source projects typically do about disaster recovery
- Work more on video for data providers and forking guidance