One Smart OS City

Overview

Github Repositories

https://gitlab.com/oscity/singletally/blockcerts-implementation-roadmap
https://gitlab.com/oscity/singletally/blockchain-api
https://gitlab.com/oscity/singletally/wordpress
https://gitlab.com/oscity/singletally/cert-viewer-instance
https://gitlab.com/oscity/singletally/blockchain-documentation

Initial Call Notes

Overall I thought this call went well. Seems like we got them to think about open source specifically for their project in a way they weren't thinking about it before.

Current situation

• Open source milestones: Active coding efforts, not focusing on open source yet
• Extending Blockcerts (MIT License) for project
  • Mostly back-end project
  • OS City building an interface and extending back-end
  • Most engagement in upstream community forums; upstream code base is lagging in contributions
  • Some communication to upstream but not much to development team; mostly with business leaders of projects
• Not thinking much about if open source practices are great; thinking to “beautify” it at the end of the funding process
• Two open source repos: one for back-end and one for front-end
  • Later: One repository only with proper documentation
  • No proprietary repositories
• Team experience: Occasional contributions but not leading a project

Project management

• Methodology:
  • One back-end developer, two front-end
  • Weekly sprints
  • Mix of agile methodologies
• Asana (https://asana.com/)
  • Scrum-based with sprints and separated tasks (“sections” in Asana)
  • Assigned to different people

Testing / code health

• Not writing frequent unit tests; not thinking about it yet
• No review process for code; depending on user front-end testing
• No automation tools used to deploy
  • Using Google Cloud Compute Engine
  • Snapshots of GCE images to reshare and redistribute images of software
  • Using Docker / containers where upstream uses it already

Documentation

• READMEs: Three repos, one is an aggregate
  • Master repo with project metadata
  • Front/back-end READMEs probably need work; not thorough
• Yes; devel environment instructions exist but could be improved

Miscellaneous

• Cash flow is biggest focus and also distraction
  • Need to deliver on other deliverables so open source aspects are neglected
  • Need better ways to make FOSS accessible to their workflow