fairDataSociety / FDS-Github-Guide

Guidelines for FDS projects

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

FDS-Github-Guide

Guidelines for FDS projects, please follow these rules as much as possible.

Projects

Owners

Each active project should have a maintainer assigned. Maintainers responsibilities are the following:

  • Maintain pull requests in a timely manner. Pull requests should be commented on positively and respecfully and merged or closed.
  • Maintain branches. Long list of os stale branches are a cruft.
  • Work with SecOps/DevOps on security issues. Try to patch high vurneable software in a timely manner.
  • Try to have a overlook of the opened issues. Similar to PR but lower priority.

Branches

Master branch: "master"

Master branches are considered "production" branches and are autodeployed to primary websites (without .dev.). For swarm connected projects this means that master branches deploy or are connected to swarm mainnet network. We try to avoid pushing single commits to this branch, but rather "releases" or branch merges.

Development branch: "development"

Development branches are testing/development branches. Any commits to master branch must be pushed here first. Projects are deployed to "dev" domains. (ie. app.fairdrive.dev.fairdatasociety.org). For swarm connected projects this means that development branches are deploying or are connecting to swarm testnet network.

master projects (which are also autodeployed)

Development projects (which are also autodeployed)

About

Guidelines for FDS projects