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.
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:By adding a
late_submission_tokenfield toSubmission, we can track how often one of these tokens was used.You'll need to add create, update and delete views in the
orgaapp (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.