Create an Icon and add to

• Doku
• Doku Favicon
• GitHub
• Docker
• ???

Change default role after registration to the actual default role

currently the username is saved initially when registering with thirdparty providers, but we should enable the users to update it either via current third party logins or manually, if they plan to remove the thirdparty login

after #29 the following migration error appears

warn: Microsoft.EntityFrameworkCore.Migrations[30200]
      An operation of type 'InsertDataOperation' will be attempted while a rebuild of table 'OrganizationData' is pending. The database may not be in an expected state. Review the SQL generated by this migration to help diagnose any failures. Consider moving these operations to a subsequent migration.

https://download.tiny.cloud/tinymce/community/languagepacks/6/langs.zip

Wäre es sinnvoll für die Umsetzung graphQL anstatt REST zu verwenden?
https://chillicream.com/docs/hotchocolate

because of i18n support it would be better than doxfx

becuase of github security concept the sonarcloud scanning does not work with external pull requests and thats okay, because the tests are running code which is provided by the pr and could expose secrets.

we have to do one of those 3 things:

• implement https://github.com/imjohnbo/ok-to-test so a comment with /ok-to-test sha= is required to run the testing
• use the pull_request_target with type labled to run the test and lable each external pr with a lable
• skip the sonarcloud test if no login is available which would disable the sonarcloud scan for external PRs, which is not good.

Add usersettings for user specific things like the ui language

currently its easy to overlook the messages

currently the visibillity options (VisibilityStateDto) are:

Everyone,
LoggedIn,
Invited

but we should somehow implement to add visibilityscopes for different groups

implement testing inside the running container before it gets pushed to docker hub

currently it is not possible to resend the confirmation mail

There is some customisation missing in the current NetEventDatagrid

Missing localisation:

• Netevent datagrid pagination Rows per page:
• Netevent datagrid Edit dialog title and buttons
• Netevent datagrid "settings" button Columns text
• Netevent datagrid Add dialog title and buttons

Other stuff:

• The add feature seems to just open the edit dialog

Add caching to API calls

https://medium.com/@anaschahid/how-to-make-your-api-faster-in-asp-net-8-9b7155309132

• discuss what we want to include on the Changelog : Available Options

• implement [action] (https://github.com/marketplace/actions/generate-changelog)

get lang from organisationsettings and add localizer

implement documentation build on feature and dev branch PRs but prevent forcepublish

only if logged in:

• /confirmation/pending
• /confirmation/success
• /register/external/complete

only if not in:

• /login
• /register

implement different eventtypes starting with lan party

• How should code be devided into which parts of NetEvent / folderstructure

• How should new models look like

• How should a new Service look like

• How does the authentication system work

• How does the rights system work

• Development process in github

  • how i announce that i work on a feature (draft pr)
  • branch naming
  • CI/CD documentation
  • Release process

• Requrements for PRs

  • Are all Strings i18n
  • Sonarcloud
  • Tests fully written
  • documentation for the feature written
  • developer documentation for the feature written

• which things you should never do

• Dev env setup

• Versioning concept

• Write PR Template

• Online and presence events
• Signup/Info Pages
• Tickets
  • QR Codes
  • Tickets for the whole event or single days
  • Signups/Gifts/Staff/Refunds
• Seating with multiple zones
• Login Gateways
  • Steam
  • Origin
  • Github
  • Google
  • Discord
• User Management
• Group Management
• staff/Admin Panel -> Single Backend panel with settings depending on group rights
• (File)Gallery
• Helpsystem to publish help/faq articles
• Themes?
• System Api tokens for specific parts of the system
• User Api tokens
• Todo System for staff with different tasks
• Support Ticket System for staff
• Catering system
• Seating Plans
• Shop
• Credit System
• Venue Management
• Multiple timetables per event supported!
• Voting and Poll Management
• News Management
• Comment Management
• Messageboard
• systemwide page modules like gameserver list / Matchmaking feature
• Event Sign in
• Sign in via QR Code
• Event specific page for when at the event
• Imprint / Dataprotection page
• Newsletter / Email Feature
• Multilanguage (currently EN and DE)
• EU cookie consent
• Playerstats for Matchmaking and Tournaments
• Terms & Conditions
• Communication Handler for notifications:
  • Mail
  • Discord
  • Teamspeak
• Webhooks
• Multiple Payment Providers
  • Paypal
  • Onsite
  • Free
  • ?
• Multiple Event Types with predefined event components:
  • Event Type Lan Party:
    • Timetables
    • Tournaments
    • Catering
    • Game Management
    • Gamserver Management
      • RCON Support for remote management and status
      • Support for automated Gameserver assignments and fully automated matchmaking / tournaments
  • Event Type Sports:
    • Timetables
    • Tournaments
    • Catering
  • Event Type hackathon:
    • Timetables
    • repository list
    • Catering
  • Event Type concert:
    • Timetables
    • Catering

Implement modular healthchecks for the system info view (GetSystemInfoHandler.cs)
to perform checks on various services like game servers, the mail server, payment apis ...
and remove dummy entrys

if a users role is changed while the user is logged on, the old claims seem to persist currently.
This should be checked on every site load.

https://github.com/Lan2Play/NetEvent/settings/branch_protection_rules/25502141

Add system info view to backend with version, build information and dependency infos

Add Logos to

• Docs/templates/netevent/favicon.ico
• Docs/templates/netevent/logo.svg
• README.md

find strings in all files (user printed error strings and so on) and localize them

• finish settings
• add main client component
• add to documentation / readme
• add statusbadge to documentation / readme

• a right system so that modules can bring multiple new rights for different purposes
• Group management
• Group rights management
• User->Group management

implement email template management and mass email sending in the admin panel

Add Venue Country