Skip to content
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

Can't submit a proposal that's not been accepted/rejected yet #22

Closed
andrew opened this issue Mar 23, 2017 · 5 comments
Closed

Can't submit a proposal that's not been accepted/rejected yet #22

andrew opened this issue Mar 23, 2017 · 5 comments

Comments

@andrew
Copy link
Contributor

andrew commented Mar 23, 2017

Not sure if this is by design, but a "submission" requires choosing one of approved/rejected, but I only put the proposal in today so it's neither.

Is it better to:

  • Not add until it's been approved/rejected by the conf
  • Add a third "submitted" or "pending" option
  • something else I didn't think of
@nodunayo
Copy link
Owner

The original design of this was intentional, but I was expecting it to be brought up for discussion.

I think the most value comes from being able to see the outcome of submissions, rather than a list of places that the proposal has been submitted to.

I have a concern that if you allow a pending option then people will input their proposal and add a list of submissions, but then won't come back to update the outcome of submissions.

On the other hand, I don't want to prevent people from inputting proposals that haven't been accepted or rejected yet (which is how it currently works).

Now I'm thinking about it, maybe it is useful to see that a proposal has indeed been submitted to places, rather than just something the speaker wrote up and didn't put out there for somebody to see.

In any case, a list of 'Pending' submissions could be a prompt to somebody to ping the speaker or update the record themselves.

Thoughts?

@jemagee
Copy link
Contributor

jemagee commented Mar 24, 2017 via email

@nodunayo
Copy link
Owner

Hi John,

Sorry it's taken me so long to reply to this.

Generally, I love the idea of having some automatic way of working out when a decision should have been made on a talk or not. At the very latest, decisions about an event will have been made by the day of the event!

Then there can be some form of notification, either to the poster (you'd then need poster information) or on the website about proposals that need updating.

I think that this is rather complicated for this stage of the project though. Let's see how others use the site as it stands and go from there, I reckon.

@nodunayo
Copy link
Owner

nodunayo commented Feb 4, 2018

Dealt with in: #56

@andrew
Copy link
Contributor Author

andrew commented Feb 6, 2018

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants