OSS Best Practices
The following is best practices for Open Source Software Development for Potlock protocol in adhereance to https://publiccode.net/standard-for-public-code/#standard-compliance-and-certification
- develop high quality software and policy for better public service delivery
- develop codebases that can be reused across contexts and collaboratively maintained
- reduce technical debt and project failure rate
- have more granular control over, and ability to make decisions about, their IT systems
- improve vendor relationships with a better economic model
- setting out a common terminology for public code development
- establishing measures to help develop high quality public code
- providing guidance on how to fulfill its criteria and operationalize compliance
Checklist
- Yes, the codebase is developed in the open.
- Yes, the codebase implements a public policy.
- Yes, the codebase is meant to be used for multiple contexts.
- Yes, we welcome contributions. (check all repos for "good-first-issues" backlog at https://potlock.org/backlog
- Yes, anyone can contribute.
- Yes, the source code is in a publicly accessible version control system.
- Yes, review of contributions is required.
- Yes, codebase and community objectives are documented. Forum at (https://potlock.org/forum), Community governance at (https://potlock.org/gov), Telegram Support https://potlock.org/community, Announcements at https://potlock.org/blog, Documentation at https://potlock.org/docs, and roadmap at https://potlock.org/roadmap,
- Yes, we strive to use English as the primary language.
- Yes, the codebase has an open license. (potlock.org/license) MIT Open Source license