-
Notifications
You must be signed in to change notification settings - Fork 92
Collaboration Call: June 14, 2019
brockfanning edited this page Jun 27, 2019
·
3 revisions
UK team
- Chris and Lucy have been in Kyrgyzstan. Working with Abdulla. Setting up their Open SDG site and developing SDMX functionality. Lucy is going to send a progress report around for more information.
- Working on accessibility updates. Booked the retest for 3 July. Preparing for that date. Many of these updates will feed into Open SDG once they’re approved.
- Beginning user testing on 5 July. Hoping that there will be outcomes and new features that we can feed into Open SDG as well. Currently determining our user base. Going to start with 5 external users. Working on this for the next six months.
US team
- Making sure that everything is good for deployment on Monday. Doing a sweep of the latest submissions.
- Noticed a glitch in the reporting status. Is that something particular to the US version? Or part of Open SDG?
- Brock: When we upgraded the US platform to Open SDG, we pushed data through before it was time. After Monday, it should be resolved.
- Also planning to move Open SDG to the Federalist platform. When ready, we’ll switch the DNS.
CODE team
- Working a lot with Kazakhstan on their Open SDG platform. Finding a few bugs. Putting issues up on GitHub.
- Just released version 0.6.0 of Open SDG. Put in a new feature on indicator names that is creating issues for the UK.
- Chris: Is this problem is specific to the UK or are others experiencing it?
- Brock: It’s an unintended change of behavior. Previous version of Open SDG had global indicators. Now it’s whatever is in the metadata field. Causing an issue on the UK platform because those things are different. Need to look at all the different ways the indicator names are displayed. Most likely going to reverse this change and think of another solution.
- When should we release version 1 of Open SDG? There’s a standard of open-source projects called semantic versioning (e.g. number.number.number). The first number is very important. This is what tells a user what changes will “break” their site. We have to think about when to release version 1. Probably want to start by bringing sub-projects (e.g. SDG Build, SDG Translations) to version 1. Then do Open SDG. Also need to do an audit of Open SDG to add more documentation.
- Chris: There may be outcomes from user testing that are useful for Open SDG before we move to version 1.
- Brock: Yes. The main obstacle for version 1 is stable requirements and stable documentation.
- Chris: Are there plans for version 2?
- Brock: When we want to make a big change that would break the sites, we would need to create version 2. We could start the new version but maintain the old version.
- Phil: Is there a script or upgrade path that handles the migration?
- Brock: For minor upgrades, we could provide an upgrade path.
Country/subnational interest in cloning the NRP
- Kyrgyzstan
- Cambodia - considering using .Stat and Open SDG together
- Ghana - considering using .Stat and Open SDG together as well
- Namibia - working with Veijo (developer)
- Reports of initial interest from Madagascar and South Africa
N/A
- CODE is ready to go with Open SDG blog post. Send any additional comments by email.
- Brock will start working on bringing SDG Build and SDG Translations to version 1.
- Lucy will send progress report around about Kyrgyzstan.
- Chris will reach out to Phil and Kali by email with more details about the UK’s plans for user testing - including question on whether the US has user pools that the UK could draw from.