24bf5f0fea
Apparently, there was a practice to archive branches by tagging them "archive/branch-name" and then deleting them. We don't practice that anymore and I would suggest to not start doing it again. Our setup is a bit different now. We now use our own forks for feature branches and can have our own, individual archiving practices in our forks. There is no need to have a central graveyard of people's "work after progress". The old feature branches we used to have in the central repository got archived in another fork: https://github.com/openfoodfoundation/openfoodnetwork-archive/ Branches associated to pull requests should be deleted after the pull request has been closed. Github keeps a reference to those branches in the pull request which is like an archive. Special branches we still have and delete from time to time: - transifex: Created for new translations, deleted afterwards. - dependabot/*: Dependabot always creates pull requests. See above. - 1-31-1-stable etc: They only live as long as they are supported. I would also like to delete the old `archive/*` tags. They are in the openfoodnetwork-archive repository and could confuse developers in the main repository. Let's keep it clean.
Open Food Network
The Open Food Network is an online marketplace for local food. It enables a network of independent online food stores that connect farmers and food hubs (including coops, online farmers' markets, independent food businesses etc); with individuals and local businesses. It gives farmers and food hubs an easier and fairer way to distribute their food.
Supported by the Open Food Foundation and a network of global affiliates, we are proudly open source and not-for-profit - we're trying to seriously disrupt the concentration of power in global agri-food systems, and we need as many smart people working together on this as possible.
We're part of global movement - get involved!
- Join the conversation on Slack. Make sure you introduce yourself in the #general channel
- Head to https://openfoodnetwork.org for more information about the global OFN project.
- Check out the User Guide for a list of features and tutorials.
- Join our discussion forum.
Contributing
If you are interested in contributing to the OFN in any capacity, please introducing yourself on Slack, and have a look through our Contributor Guide
Our GETTING_STARTED and CONTRIBUTING guides are the best place to start for developers looking to set up a development environment and make contributions to the codebase.
Provisioning
If you're interested in provisioning a server, see ofn-install for the project's Ansible playbooks.
We also have a Super Admin Guide to help with configuration of new servers.
Testing
We use BrowserStack as a manual testing tool. BrowserStack provides open source projects with unlimited and free of charge accounts. A big thanks to them!
Licence
Copyright (c) 2012 - 2019 Open Food Foundation, released under the AGPL licence.