Skip to content

Software quality of the project #98

Description

@nafieshehu

Can someone from the team have a look on these questions? Would really help the community get a better understanding of the way CityZen is structured as a project.

  • is our community highly prioritizing producing secure software?
  • Do we have what is considered a well-documented channel to report security issues, along with a documented response process?
  • do we prioritize backward compatibility, documentation of any incompatible changes, tools and documentation to help users transition to new release features?
  • Is our project striving for timely response to bug reports?
  • does our project include unit and integration test suites of sufficient coverage? Is coverage documented?
  • Do we include enough documentation for anyone to test or deploy any of the software?
  • Do we include documentation for a software developer of moderate skill to set up their development environment to contribute?
  • we document how we integrate with OpenStreetMap and other projects (Mapbox in the future?)
  • is a Continuous Integration pipeline is used for testing and deployment purposes?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions