Skip to content
This repository has been archived by the owner on Oct 25, 2018. It is now read-only.

Software Development Communications

Mayank Ojha edited this page Feb 14, 2017 · 2 revisions

Review from CogniCity v3.0 Development

Development / Communications what worked, what didn’t work?

  • Communications tools, Gitter, Wiki, GitHub Issues, GitHub Projects
  • Wiki:
    • Needs Organising (folders?)
    • Define what we want it to be (and document on wiki home page)
    • Avoid wikis under individual repos -> create README files or use urbanriskmap-meta
  • GitHub issues great!
    • Use for software issues under specific repositories (use appropriate tags, milestones), refer in commits.
    • Create templates for various members to post issues (eg. front-end issues template for field team), include useragent info from dev website, etc.
    • Use issues in urbanriskmap-meta as discussions -> Helps in archiving different member comments, tag issues from other repos, tag releases & milestones.
  • GitHub projects are out.
  • Gitter for real-time discussion AND meta-discussions
    • More specific room names required?
    • Try to reduce WhatsApp and Email.
  • Make a super short communications guide and share with teams