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

Email after talk proposal submission #27

Open
honzajavorek opened this issue Sep 5, 2018 · 7 comments
Open

Email after talk proposal submission #27

honzajavorek opened this issue Sep 5, 2018 · 7 comments
Assignees
Labels

Comments

@honzajavorek
Copy link
Member

@honzajavorek honzajavorek commented Sep 5, 2018

People do not get any acknowledgement by email when they post a CfP proposal, but according to feedback, that's something they expect. See https://pyvec.slack.com/archives/C4PPZNPDK/p1519223809000450

For 2018 we decided to send a bulk email with the closure of CfP. This is a sprint idea to make PyCon CZ great for future generations.


Supersedes pyvec/cz.pycon.org-2018#23

@frenzymadness
Copy link
Member

@frenzymadness frenzymadness commented Jan 13, 2019

Ping 😉

@torsava
Copy link
Contributor

@torsava torsava commented Jan 21, 2019

In the meantime, there's the note "Please note that you won’t receive any copy of your proposal to your mailbox.", but it's drowned among all the other text on the submission form. We could move/copy it to the "We've received your proposal" page, where there's comparatively little text. Plus that is the point where the message is the most relevant.

CC @benabraham

@frenzymadness
Copy link
Member

@frenzymadness frenzymadness commented Jan 27, 2019

Should we reassign this issue @gjask?

@gjask
Copy link
Collaborator

@gjask gjask commented Jan 27, 2019

I am sorry. I got a little distracted with my own work in last two weeks. Is it still useful to implement email notification, or should I focus on the "after page" as @torsava suggested?

@frenzymadness
Copy link
Member

@frenzymadness frenzymadness commented Jan 27, 2019

@gjask
Copy link
Collaborator

@gjask gjask commented Feb 1, 2019

I am not sure, how to link pull request with issue. I've not use github much before. Here is my work: #54

@benabraham benabraham added this to the Future enhancements milestone Feb 25, 2019
@benabraham benabraham unpinned this issue Mar 3, 2019
@benabraham benabraham added the next year label Feb 8, 2020
@benabraham
Copy link
Member

@benabraham benabraham commented Feb 8, 2020

For 2020 we're using Google Forms so this is not needed.

Keeping this open as I'm not sure about solution for 2021.

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

Successfully merging a pull request may close this issue.

None yet
5 participants