-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused proposal requirements #13
Comments
Hi there. Happy to help out. These conf systems tend to have a lot of context knowledge baked into them, so there will be some domain rampup time before I can make sensible fixes. I've worked with pentabarf (XML outputs) but not on penta or OSEM. I'll evaluate how much of a proper fix I can do or outline a temporary workaround by 15 May. Then hopefully get it in the following 10 days. |
I see there's a Vagrantfile. It may be helpful for me to also have an example config that's as close to what's running in production as possible if you can get it (with sensitive info scrubbed out). Feel free to email the address in my github profile. |
@kormoc? Could you oblige? |
Everything that we have setup with the exception of the database passwords should be in the repo. We have the deployment information in wiki and https://github.com/SeaGL/osem/blob/master/config/deploy.rb contains the code |
Quick update, I've gotten it to run although had some problems, the latest being I had to upgrade rails to 4.2.8 locally. 4.2.7 is not compatible with ruby 2.4, I get a nested stack recursion exception on running Just need to figure out how to make a conf and admin user later today. Hopefully that lets me into the part of the UI that this issue is referencing. I don't imagine there's some seed / example data for a conference organising tool :), but if you know of some, let me know. I couldn't find any in the upstream repo this is a fork of. |
OK, I think I've managed to achieve that in PR #14 . You can toggle any of the options at any time by editing the CFP and it just affects what's shown in the speaker todo list. |
|
Every year we field a lot of questions about this stuff:
We don't use most of the things which OSEM sees as "requirements":
Perfect world? Everything on that "Your todo list" is a toggle-able option in CFP setup. But we don't live in a perfect world, so…
Things we absolutely want to remove from the process entirely:
Anything else we get is just a bonus.
The text was updated successfully, but these errors were encountered: