Furrest City's modified version of OSEM
http://osem.io
Introduce an association between User and Event for the user schedule. As there was already a relation call users in Event the new relation is called public_users. And for the same reason the relation in Event is called public_events. |
||
|---|---|---|
| app | ||
| bin | ||
| config | ||
| db | ||
| doc | ||
| lib | ||
| public | ||
| spec | ||
| vendor | ||
| .gitignore | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .travis.yml | ||
| app.json | ||
| bootstrap.sh | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| dotenv.example | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| INSTALL.md | ||
| LICENSE | ||
| PAYMENTS.md | ||
| Rakefile | ||
| README.md | ||
| TRANSLATION.md | ||
| Vagrantfile | ||
Open Source Event Manager
An event management tool tailored to Free and Open Source Software conferences.
OSEM actively participates in GSoC and RGSoC.
Installation
Please refer to INSTALL documentation file
How to contribute to OSEM
Please refer to our CONTRIBUTING guide
How to translate OSEM into your language
Please refer to our TRANSLATION 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.

