You are viewing Camdram release v2.59.
Camdram is an open-source project developed by a team of volunteers for the benefit of the Cambridge student theatre community. We use our project page on GitHub to co-ordinate our work and host a copy of the code that runs this site, as well details about bugs that have been submitted and our future roadmap for the site.
If you don't have programming skills but think you've found a bug, or you just have a cool idea for a new feature on Camdram, you can still create a new issue on GitHub, and one of our developers will get back to you.
If you're a programmer and would like to contribute to Camdram, we invite you to fork our repository. You can then fix any open issue or create a new one. Once you've fixed a bug or created some new functionality, you can then submit a pull request to be reviewed by the development team.
In order to avoid wasting effort, we recommend you discuss your ideas before carrying out any significant development work. If there's a relevant issue then you can use that, otherwise we have a Gitter chatroom for developer discussions and questions - feel free to send a message there. You can also use this group if you're having problems getting your development environment set up, or if you're not sure whether something is a bug or a problem with your set-up. We run Camdram as a meritocracy: anyone who has a reasonable number of pull requests accepted will be given access rights to commit straight to the Camdram repository.
Below is a summary of recent development activity on Camdram.
The following people have made contributions to Camdram:
- Peter Hoyes
- Andrew Featherstone
- George Bateman
- David Stansby
- Stuart Cuthbertson
- Charlie Jonas
- Ian Leith
Issues currently being worked on:
Issues recently fixed:
- Bump jms/serializer-bundle from 2.4.2 to 2.4.3
- Bump twig/extensions from 1.5.3 to 1.5.4
- Bump excelwebzone/recaptcha-bundle from 1.5.11 to 1.5.12
- Date format
- Fix CSRF vulnerabilities
- Fix application vacancies API
- [Security] Bump symfony/symfony from 3.4.19 to 3.4.20
- Better roles API endpoint
- 500 error on viewing unauthorised show as non-admin
- Diary refactor
Issues recently created:
- Disallow anonymous API access
- Remove legacy API
- Better notification processing
- Don't send "access granted" email after creating a show
- Don't send venue/society/show admins an email when changes are made by a site admin
- Standardised diary API query params
- Create DB entries for all society and venue strings
- Implement constraints on the JSON data in socs_list
- Reimplement access control for changing which societies own a show
- Rethink role editing UI