TODO

[github-actions]

TODO

Active

• .github/workflows/deploy.yml:113 ends with 400
• .github/workflows/deploy.yml:113 ends with 400
• .github/workflows/deploy.yml:115 ends with 400
• .github/workflows/deploy.yml:60 ends with 400
• fiesta/apps/accounts/adapters.py:21 making usernames from first_name is kinda bleeh
• fiesta/apps/accounts/forms/profile.py:112 think about limiting the choices by country of section, in which is current membership
• fiesta/apps/accounts/forms/profile.py:27 what to do, when no specific configuration is found?
• fiesta/apps/accounts/forms/profile.py:57 show only related facultites & universities
• fiesta/apps/accounts/forms/profile_factory.py:54 what to do, when no specific configuration is found?
• fiesta/apps/accounts/forms/profile_factory.py:92 what to do, when no specific configuration is found?
• fiesta/apps/accounts/models/profile.py:139 Notifications: what, how, when? #23
• fiesta/apps/accounts/models/profile.py:141 define formfield/widget to handle flagging
• fiesta/apps/accounts/templatetags/memberships.py:16 the next cannot blindly follow the source /path, because user probably does have
• fiesta/apps/buddy_system/templatetags/buddy_system.py:34 could be more then one?
• fiesta/apps/esnaccounts/provider.py:75 definitely not, user nationality != section assignment
• fiesta/apps/esnaccounts/provider.py:80 check all possible for ESN Accounts roles
• fiesta/apps/esnaccounts/provider.py:84 should be as AccountsConfiguration attribute, so section can select
• fiesta/apps/esncards/views/applications.py:48 do it properly
• fiesta/apps/esncards/views/applications.py:94 limit somehow?
• fiesta/apps/events/models/event.py:10 Maybe pre-registration, registration and paused registration for different field.
• fiesta/apps/events/models/event.py:137 hybrid registration, default user, only online (qr), offline registrations (counter, subtract from capacity)
• fiesta/apps/events/models/participant.py:60 problematika ověřování lidí (QR check-in)
• fiesta/apps/events/models/participant.py:9 do we need a state if we have an expiration date
• fiesta/apps/fiestaforms/widgets/models.py:69 filter state?
• fiesta/apps/fiestaforms/widgets/models.py:91 filter state?
• fiesta/apps/fiestarequests/forms/request.py:19 group field somehow and add group headings
• fiesta/apps/fiestarequests/forms/request.py:45 add save/load of contacts to/from user_profile
• fiesta/apps/fiestarequests/matching_policy.py:101 make it working
• fiesta/apps/fiestarequests/matching_policy.py:28 NotImplemented or base implementation?
• fiesta/apps/fiestarequests/tables/editor.py:86 fix attrs accessor
• fiesta/apps/fiestarequests/tables/editor.py:89 dynamic by section preferences
• fiesta/apps/fiestarequests/views/editor.py:109 django.lifecycle would be probably better
• fiesta/apps/fiestatables/columns.py:15 probably not needed anymore
• fiesta/apps/files/storage.py:88 think about defining public url of bucket directly to nginx proxypass conf
• fiesta/apps/pages/models/page.py:77 probably not needed
• fiesta/apps/pages/urls.py:9 use custom converter https://docs.djangoproject.com/en/4.1/topics/http/urls/#registering-custom-path-converters
• fiesta/apps/pickup_system/urls.py:37 the url name is defined also in issuer/matcher_picture_url, better would be to generalize it
• fiesta/apps/plugins/admin.py:65 relating to django-polymorphic docs, UUID PK should not work
• fiesta/apps/plugins/middleware/plugin.py:60 check, if plugin is enabled, perms and all the stuff
• fiesta/apps/plugins/utils.py:40 resolver.app_name is full-dotted path
• fiesta/apps/sections/admin.py:41 Listing all memberships in section admin
• fiesta/apps/sections/forms/membership.py:15 preselect active?
• fiesta/apps/sections/models/membership.py:36 think about
• fiesta/apps/sections/models/membership.py:53 add flag to signalize, if membership has been added from ESN Accounts
• fiesta/apps/sections/models/membership.py:64 rename BANNED and add "PAUSED"
• fiesta/apps/sections/models/section.py:32 remove blankness after proper migration from ESN accounts
• fiesta/apps/sections/models/section.py:99 refactor to share code from CheckEnabledPluginsViewMixin
• fiesta/apps/sections/services/sections_plugins_validator.py:34 would be better to refactor to some kind of matrix:
• fiesta/apps/sections/tables/faculties.py:14 probably extract to constant in fiestatables
• fiesta/apps/sections/tables/internationals.py:21 do it properly
• fiesta/apps/sections/tables/internationals.py:21 do it properly
• fiesta/apps/sections/tables/members.py:21 do it properly
• fiesta/apps/sections/tables/membership_filter.py:40 needed?
• fiesta/apps/sections/tables/membership_filter.py:51 find out why search vector is not enough to find "Gus Fring" for "Fri"
• fiesta/apps/sections/urls.py:31 homepage for esn section plugin?
• fiesta/apps/sections/views/choose_space.py:22 temporary hack, have to decide if need to have choosespace page
• fiesta/apps/sections/views/choose_space.py:43 limit to current membership
• fiesta/apps/sections/views/mixins/membership.py:11 maybe specific error page? idk
• fiesta/apps/sections/views/mixins/membership.py:24 fallback to superuser (w/message) only if test_membership fails?
• fiesta/apps/sections/views/mixins/membership.py:26 should not happen? is always True?
• fiesta/apps/sections/views/stats.py:35 weird, filtering via self.filters keeps lookup_expr as exact
• fiesta/apps/universities/models/university.py:18 logo? or color?
• fiesta/apps/utils/management/commands/loadlegacydata.py:167 state
• fiesta/apps/utils/templatetags/navigation.py:43 consider better way
• fiesta/apps/wiki/elastic.py:112 really here?
• fiesta/fiesta/settings/auth.py:19 check, which settings are needed
• fiesta/fiesta/settings/db.py:14 access to legacy db by standard user
• fiesta/fiesta/settings/db.py:23 pass from ENV
• fiesta/fiesta/settings/files.py:26 pass from env
• fiesta/fiesta/settings/logging.py:19 [%(request)s] is bullshit here, since it's wsgi request only
• fiesta/fiesta/settings/project.py:28 fill from environ
• fiesta/fiesta/settings/project.py:73 replace by CSP
• get-docker.sh:447 [thaJeztah] remove the $CHANNEL check once 22.06 and docker-buildx-plugin is published to the "stable" channel
• get-docker.sh:447 [thaJeztah] remove the $CHANNEL check once 22.06 and docker-buildx-plugin is published to the "stable" channel
• webpack/src/css/_Forms.css:279 needed after daysiui migration to v4, probably better would be to drop it
• webpack/src/css/_Tables.css:47 refactor pagination to btn-group
• webpack/src/css/main.css:26 make it fine
• webpack/tailwind.config.js:13 till the Tailwind content scanning in Python files #188 is fixed
• webpack/webpack.prod.config.js:11 breaks integrity after deploy
• webpack/webpack.prod.config.js:19 for cache purpose would be better to tweak CORS to allow serving from topdomain on subdomains with SRI
• wiki/fetcher.rb:138 well, GH or self-hosted?

Done

• .github/workflows/deploy.yml:207 ends with 400
• .github/workflows/docker-build.yml:54 tag
• docker-compose.prod.yml:23 figure out before deployment, whereever/where should be certs stored
• fiesta/apps/accounts/forms/profile.py:29 what to do, when no specific configuration is found?
• fiesta/apps/accounts/forms/profile.py:36 check also Membership.state?
• fiesta/apps/accounts/forms/profile.py:50 what to do, when no specific configuration is found?
• fiesta/apps/accounts/forms/profile.py:63 what to do, when no specific configuration is found?
• fiesta/apps/accounts/forms/profile_finish.py:19 find generic way for configuration instance -> form setup
• fiesta/apps/accounts/models/profile.py:132 social network profiles
• fiesta/apps/accounts/models/profile.py:138 weird, basically it's exactly one of these
• fiesta/apps/accounts/models/profile.py:22 required by section configuration...
• fiesta/apps/accounts/models/profile.py:24 define relation to section, membership
• fiesta/apps/accounts/models/profile.py:24 define relation to section, membership, universities
• fiesta/apps/accounts/models/profile.py:57 profile picture
• fiesta/apps/accounts/models/profile.py:71 help, not description
• fiesta/apps/accounts/models/profile.py:99 phone, profiles
• fiesta/apps/accounts/templatetags/memberships.py:19 default homepage for section? since public on / is not available in section space
• fiesta/apps/accounts/templatetags/user_profile.py:26 compute based on accounts conf and profile state
• fiesta/apps/accounts/views/membership.py:11 limit role only to member/international
• fiesta/apps/accounts/views/membership.py:11 clean role only to member/international
• fiesta/apps/accounts/views/profile.py:47 next?
• fiesta/apps/accounts/views/profile.py:48 mixin?
• fiesta/apps/buddy_system/admin.py:10 parent admin doesn't work with inserted middle abstract class BaseRequestSystemConfiguration
• fiesta/apps/buddy_system/forms.py:14 add notes, interests, etc
• fiesta/apps/buddy_system/forms.py:15 and others by preference of responsible_section
• fiesta/apps/buddy_system/forms.py:24 group field somehow and add group headings
• fiesta/apps/buddy_system/forms.py:64 add save/load of contacts to/from user_profile
• fiesta/apps/buddy_system/models/configuration.py:20 pass configuration?
• fiesta/apps/buddy_system/views/editor.py:101 fix attrs accessor
• fiesta/apps/buddy_system/views/editor.py:107 dynamic by section preferences
• fiesta/apps/buddy_system/views/matching.py:69 check matcher relation to responsible section
• fiesta/apps/buddy_system/views/matching.py:70 reset any previous match for this BR
• fiesta/apps/buddy_system/views/matching.py:78 target URL?
• fiesta/apps/buddy_system/views/request.py:33 depends, if member or international is here
• fiesta/apps/buddy_system/views/request.py:34 check existence of in_space_of_section, since without section it doesn't make sense
• fiesta/apps/dashboard/views/index.py:37 only by state? maybe the R/O or editor is needed
• fiesta/apps/esnaccounts/provider.py:63 check all possible for ESN Accounts roles
• fiesta/apps/esncards/templatetags/esncards.py:12 could be more then one?
• fiesta/apps/esncards/views/application.py:84 check perms
• fiesta/apps/fiestarequests/models/configuration.py:17 make it visible and working
• fiesta/apps/fiestarequests/models/configuration.py:25 pass configuration?
• fiesta/apps/fiestarequests/models/managers/request.py:20 check matcher relation to responsible section?
• fiesta/apps/fiestarequests/views/matching.py:31 check matcher relation to responsible section
• fiesta/apps/fiestarequests/views/matching.py:32 reset any previous match for this BR
• fiesta/apps/fiestarequests/views/matching.py:40 target URL?
• fiesta/apps/fiestatables/views/tables.py:20 get QS and rename the output
• fiesta/apps/pickup_system/forms.py:67 add save/load of contacts to/from user_profile
• fiesta/apps/pickup_system/templatetags/pickup_system.py:75 limit by semester / time
• fiesta/apps/plugins/admin.py:41 make configuration form field dependent on selected configuration
• fiesta/apps/plugins/middleware/plugin.py:32 not active membership, redirect or?
• fiesta/apps/plugins/middleware/plugin.py:38 resolver.app_name is full-dotted path
• fiesta/apps/plugins/middleware/plugin.py:44 decide, which section -> which plugin
• fiesta/apps/plugins/models/plugin.py:18 state with visibility only for editors and highers
• fiesta/apps/sections/middleware/section_space.py:30 check for existing section
• fiesta/apps/sections/middleware/section_space.py:31 detect active state of selected section
• fiesta/apps/sections/middleware/section_space.py:32 compare section space with active membership section
• fiesta/apps/sections/middleware/user_membership.py:22 Detect, in which membership is user logged:
• fiesta/apps/sections/middleware/user_membership.py:30 Detect, in which membership is user logged:
• fiesta/apps/sections/middleware/user_membership.py:36 check, if user does have a filled profile
• fiesta/apps/sections/models/section.py:108 what to do if user is logged and dashboard is not available?
• fiesta/apps/sections/views/members.py:20 do it properly
• fiesta/apps/sections/views/mixins/membership.py:11 maybe specific error page? idk
• fiesta/apps/sections/views/mixins/membership.py:12 maybe specific error page? idk
• fiesta/apps/sections/views/permissions.py:0 should not happen? is always True?
• fiesta/apps/sections/views/permissions.py:41 check anything else?
• fiesta/apps/utils/templatetags/breadcrumbs.py:34 eg "Home > Docs" doesn't make sense
• fiesta/apps/utils/templatetags/breadcrumbs.py:36 slash is not always the home page?
• fiesta/apps/utils/templatetags/navigation.py:38 define these urls elsewhere
• fiesta/fiesta/settings.py:0 check, which settings are needed & move to settings subpackage
• fiesta/fiesta/settings.py:117 access to legacy db by standard user
• fiesta/fiesta/settings.py:81 replace by CSP
• fiesta/fiesta/settings/auth.py:82 do redirect to special url with smart router, which redirects to section
• fiesta/fiesta/settings/security.py:10 set before deployment!
• fiesta/fiesta/settings/security.py:10 probably dynamic?
• get-docker.sh:0 [thaJeztah] remove the $CHANNEL check once 22.06 and docker-buildx-plugin is published to the "stable" channel
• get-docker.sh:447 [thaJeztah] remove the $CHANNEL check once 22.06 and docker-buildx-plugin is published to the "stable" channel
• webpack/tailwind.config.js:13 till the Tailwind content scanning in Python files #188 is fixed
• wiki/fetcher.rb:67 does not work with relative paths

---

Generated by Github Action, please do not edit.
If you want to extract TODO into sub-issue, please include file:line somethere in the body text and add label todo.