You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 :
strictly required changes before we move:
other changes that should happen, but are not yet needed at this point
minor changes:
nice to have, but may have better solutions:
this overview was created by running
git diff fosdem_2024_extra..fosdem_2024_rebase
which should help find the changes mentioned aboveThe text was updated successfully, but these errors were encountered: