-
Notifications
You must be signed in to change notification settings - Fork 155
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
Feedback Request Checkbox - Feature Request #114
Comments
Hi Sean, I like your suggestion and the direction of this. We've been thinking of enhancing the custom question functionality to support more answer types beyond free text and it would be perfect to allow organizers to make this possible. If you'd like to take a stab at this, I'd be happy to hop in a call sometime and walk you through what we have and the direction I was thinking for this feature. I will point out that we've got a significant fork on this project that is 1-2 weeks from being brought back into this repo as version 2.0. So if you do want to take this on, I'd either wait for the fork to be merged or work off the fork directly. Thanks! |
Hey Marty, I'll probably wait for the merge since I won't have time until the week after after Thanksgiving (family visiting!) Thanks for the info! |
…ed-data rubycentral#114 - Increase seed data
…mits-forms rubycentral#161-enter-submits-form
There could be a checkbox and a text input field. Checking the box could populate a generic "I would like some feedback please" (or whatever), and the author could fill in more if they like. It would be awesome to have visibility in the app to see what feedback requests there are and whether they've been fulfilled. We already have a public comment area, and that has been used for the feedback. We'd need some smarts to decipher that feedback has been given after the request was made. |
Hey awesome open source developers, I wanted to put a feature request idea up for discussion/consideration.
For background, I was a guide in the scholar and guide program at Rubyconf again this year and it was a huge success. The two scholars I was a guide to (one official, one unofficial) both gave a lightning talk and are motivated to submit to future conferences like Railsconf. (Woo hoo!)
What I would like to propose is adding a checkbox to the proposal form so these first time submitters don't get discouraged if their talks are not accepted and they don't receive feedback. Something like:
or maybe:
I realize this could potentially add a lot of work to the review team especially since people have a tendency to submit last minute so we could add some helper text like "We will provide feedback to CFPs received up until 3 weeks before the CFP period ends." Or something similar so the feedback doesn't coincide with the CFP rush.
I'm obviously happy to do the work and submit a PR.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: