Furrest City's modified version of OSEM
http://osem.io
072307a7b9
* CactusPuppy-master: (99 commits) Fix Rubocop linting issue Allow ES6 JS syntax Revert "Avoid using ES6 syntax to prevent Heroku asset compilation from failing" Avoid using ES6 syntax to prevent Heroku asset compilation from failing Ensure sqlite isn't trying to be loaded on Heroku Only upload coverage reports from Travis if based in master Unpend test because I guess it works on Travis Pend test so that error is exposed instead of skipping Actually run rest tests instead of features twice Update annotate_models comments Temp pend failing test, as it does not reflect local verification Ensure coverage.xml is generated on Travis Prevent overwriting of jobs by matrix Actually properly report parallel stages Fix minor typo in .travis.yml Specify where the coverage report is Switch to using Codacy for code coverage (following OSEM example) Switch CodeCov badge to Code Climate badge Avoid installing Ruby in finalize stage Ensure finalize stage does not have unecessary installation to do ... |
||
|---|---|---|
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| dist | ||
| doc | ||
| lib | ||
| public | ||
| spec | ||
| vendor | ||
| .codecov.yml | ||
| .dockerignore | ||
| .flayignore | ||
| .gitignore | ||
| .haml-lint.yml | ||
| .haml-lint_todo.yml | ||
| .overcommit.yml | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-gemset | ||
| .ruby-version | ||
| .travis.yml | ||
| app.json | ||
| CHANGES.md | ||
| CODE_OF_CONDUCT.md | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| docker-compose.override.yml.example | ||
| docker-compose.yml | ||
| docker-compose.yml.production-example | ||
| Dockerfile | ||
| Dockerfile.production | ||
| dotenv.example | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| info.yml | ||
| INSTALL.md | ||
| LICENSE | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
Spring 2021 Student Project
Snap!Con
forked from:
Open Source Event Manager - osem.io
An event management tool tailored to Free and Open Source Software conferences.
Installation
Please refer to our installation guide.
How to contribute to OSEM
Please refer to our contributing guide.
Contact
GitHub issues are the primary way for communicating about specific proposed changes to this project. If you have other questions feel free to subscribe to the opensuse-web@opensuse.org mailinglist, all OSEM contributors are on that list! Additionally you can use #osem channel on freenode IRC.