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

Provide a secret CfP url #324

Closed
rixx opened this issue Jan 21, 2018 · 3 comments
Closed

Provide a secret CfP url #324

rixx opened this issue Jan 21, 2018 · 3 comments

Comments

@rixx
Copy link
Member

@rixx rixx commented Jan 21, 2018

This is an issue that is well-suited for external contributors – let me know if I can be of any help, either via this issue or via support@pretalx.com.

What this is about

pretalx manages the CfP of an event via a set of deadlines (an event-global deadline plus optionally different ones on submission types). Sometimes organisers want to permit specific persons to submit a proposal after the last deadline is over, though.

How to get started

First of all, leave a comment on this issue to make sure nobody else starts working on this issue at the same time!

Next, you need pretalx running locally on your machine. First, fork the repository to your own GitHub account. Then clone it locally (or set it as your remote if you already cloned it earlier)

Follow the developer setup guide, and then play around with pretalx a bit.
Have a look at the places impacting this issue. Look at the code responsible for the issues (searching for relevant words or files should help you find your way around). We have an explanation of our code structure and the actual data models.

How to do this

We'll need a new model in pretalx/submission/models/token.py, looking roughly like this:

class LateSubmissionToken(…):
    event = ForeignKey('event.Event')
    uses = PositiveIntegerField(null=True)
    token = CharField()
    valid_until = DateTimeField()

By adding a late_submission_token field to Submission, we can track how often one of these tokens was used.

You'll need to add create, update and delete views in the orga app (you can look at tracks, which have very simple views and forms and should be a good starting point), and then make sure that users can submit if they have a valid token, e.g. by providing it via the URL (…?token=abcd…).

Submit the PR

There are a number of tutorials on the Pull Request workflow online, for example this short version by GitHub itself and this more in-depth tutorial.

Remember to provide documentation and tests, if applicable. Run the tests before opening your PR, including style checks. We have a contribution guide, which ought to prove helpful at this stage.

@MacLemon

This comment has been minimized.

Copy link
Contributor

@MacLemon MacLemon commented Mar 28, 2018

Maybe that doesn't require a special secret URL? Makes sense to have one though.

Could be tied to a speaker profile as well.

Speaker get's a notification that “late-checkin” is now enabled for them to submit a number of n events. That property could be directly attached to a speaker invitation as well.

Example:
Prospective speaker and orga person talk on $medium and the orga person decides to invite that person to enter CfP, even when late. The person hands over an email address and agrees it be used for sending the invitation. To prevent the necessity for further back-and-forth for that person, the late-entry would ideally be attached to the invitation and inherited by the resulting speaker profile for submission.

@rixx

This comment has been minimized.

Copy link
Member Author

@rixx rixx commented Jan 31, 2019

I think I'd rather work with special links, as the people targeted may not have a profile yet. The current planning involves codes that are valid for 1..n submissions in a set timeframe, so that the organizers can either choose to distribute personalized links, or to just hand out the same link to everybody.

@rixx rixx added the help wanted label May 1, 2019
@rixx

This comment has been minimized.

Copy link
Member Author

@rixx rixx commented Nov 6, 2019

Closed by way of access codes.

@rixx rixx closed this Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.