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

Rebasing against v2024.3.1 #66

Open
17 of 25 tasks
johanvdw opened this issue Nov 19, 2024 · 1 comment
Open
17 of 25 tasks

Rebasing against v2024.3.1 #66

johanvdw opened this issue Nov 19, 2024 · 1 comment

Comments

@johanvdw
Copy link
Member

johanvdw commented Nov 19, 2024

As we found out, forking is harder than merging, but let's try to track either pretalx v2024.3.1 or main and rebase our changes. I'm creating this issue to follow up and creating new branches in pretalx-integration and pretalx.

model changes required :

  • add matrix_id (plugin?)
  • add cc: field to mail/mailtemplate (upstream?)
  • on website field

strictly required changes before we move:

  • signals for track expansion (upstream)
  • track_mail logic (track mail as signal)
  • add cc field to mail (upstream?)
  • show other proposals in review (check if not added upstream, it was discussed)
  • show resources in review
  • file upload limit (check we can do this on deploy in ansible instead)
  • state change only by devroom managers
  • vue app changes required to show all rooms/tracks
  • show matrix_id in relevant places
  • nanoc and devroom manager plugin work (probably need bootstrap changes)
  • auditlog
  • add big orga button (propose upstream)

other changes that should happen, but are not yet needed at this point

  • near overlaps warnings (upstream)
  • release logic - on website field / hide release button
    minor changes:
  • session image comment
  • datetime picker/times in steps of 5 minutes (propose upstream)
  • use our feedback system
  • fellow role instead of fellow speaker (propose upstream): ie for call for devrooms/stands
  • powered by pretalx should mention we have a fork + where to submit issues
  • duration can not be updated by submitter (check how this is best handled)

nice to have, but may have better solutions:

  • check errors
  • keep track who sent mail + limit that (not yet implemented)

this overview was created by running
git diff fosdem_2024_extra..fosdem_2024_rebase which should help find the changes mentioned above

@johanvdw
Copy link
Member Author

johanvdw commented Nov 19, 2024

steps to migrate the db:

# mail saw no changes, so not needed to fake
python -m pretalx migrate person 0027 --fake
python -m pretalx migrate devroom_settings 0007 --fake
after updating the branch:
python -m pretalx migrate person 0030 --fake
python -m pretalx migrate devroom_settings 0011 --fake
python -m pretalx migrate submission 0078 --fake

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

No branches or pull requests

1 participant