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

Fancier delegate reports #483

Open
6 of 17 tasks
jfly opened this issue Apr 7, 2016 · 0 comments
Open
6 of 17 tasks

Fancier delegate reports #483

jfly opened this issue Apr 7, 2016 · 0 comments
Labels
AREA: UI/UX design META: good second issue More involved than first issue, these help get a deeper understanding of the codebase PRIORITY: low-priority A step above backlog - nice to have, but not essential to work on. project: improve delegate reports TEAM: delegates TEAM: wdc Issues related to WDC TEAM: wqac Issues related to WQAC TEAM: wrc issues related to WRC

Comments

@jfly
Copy link
Contributor

jfly commented Apr 7, 2016

I'm picturing a text box that lets you type in markdown, and when you're done, you click confirm to make it uneditable and send out an email to the delegates list.

Mandatory:

  • Automatically send emails with fancy title (automatically include region?!)
  • WYSIWG text editors here (ideally one with support for image uploads)
  • Link to the corresponding discussion over on Google groups. However, I have no idea how to do this... Jfly decided to farm this work out on the Board =)

Nice to have:

  • Link to delegate report on the competition nav
  • Automatically send nag emails for delegates who have not submitted their reports (cc the board after a while) (see how we did this for submitting results in Nag delegates about results after a week #682) Delegate report submission nag email #696
  • Compute the number of newcomers
  • If WCA registration was used, show the number of registrants
  • "As an afterthought, it would be nice having a counter of competitions delegated/attended for each delegate. Not necessarily on the report, but maybe on the profile." -Natan
  • Do we need to support image uploads? What about arbitrary file uploads? Even if we do decide we want this, it's not the sort of thing we'd have to support at first.
  • Daniel Sheppard: A checkbox and a notification sent to WDC would be fantastic.
  • "A +/- data entry feature for incidents with auto-numbering, instead of rich text, might make it easier to track and comment on particular issues. They could then be escalated to the WRC/WDC for review individually." -@TimMcMahon (here)
  • "Numbers are lost when copy/pasting stuff into the rich text fields. You can't just select 10 lines and hit the "ordered list" button to prefix each line with a number that increments to 10, it makes all of them 1's. You need to type, hit enter to go to the next line for "2." to appear etc." -@TimMcMahon (here)
  • If you are not familiar with Markdown you probably do not understand how the image tag works. If that is possible, it would be nice to have a default text here, like "add your description here". -@Laura-O (here)
  • In the preview the headings and the input text have the same font size. So you cannot distinguish between them if your text starts with bold letters (and I am sure people will do that). -@Laura-O (here)
  • Another possible fancy improvement: if the organizers have WCA IDs, make their name link to their WCA profile. -@viroulep
  • "I really like the layout, but maybe some window like ‚Course of the competition‘ or ‚Competitionflow‘ would be good? Right now you only can write this in the last window under Remarks, but in most of the competition reports it’s directly under the organizational stuff." -Linus
  • "Also I noticed that there is not really an appropriate window for stuff like ‚registered persons‘ compared to competitors who actually came to the competition, this may be at a good place right under the 'Competitors‘, if even necessary :-)" -Linus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AREA: UI/UX design META: good second issue More involved than first issue, these help get a deeper understanding of the codebase PRIORITY: low-priority A step above backlog - nice to have, but not essential to work on. project: improve delegate reports TEAM: delegates TEAM: wdc Issues related to WDC TEAM: wqac Issues related to WQAC TEAM: wrc issues related to WRC
Projects
Status: No status
Development

No branches or pull requests

6 participants