User Tools

Site Tools


act-requirements-collection

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
act-requirements-collection [2019/03/20 14:12]
haj Conversion of a first batch if GitHub issues
act-requirements-collection [2019/03/20 18:14]
haj Added another bunch of GitHub stuff
Line 21: Line 21:
     * Who has this problem: Everyone who tries to run an Act instance, and everyone who wants to test improvements to the production code.     * Who has this problem: Everyone who tries to run an Act instance, and everyone who wants to test improvements to the production code.
     * Why this is important: Being able to get the stuff up and running is a prerequisite for developing.     * Why this is important: Being able to get the stuff up and running is a prerequisite for developing.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​21|GitHub issue 21: Error checking and messages are needed]], [[https://​github.com/​book/​Act/​issues/​1|GitHub issue 1: Port to PSGI/​Plack]],​ [[https://​github.com/​book/​Act/​issues/​49|GitHub issue 49: Merge PSGI]]
   * I'd like to have control over how my personal data is published and shared   * I'd like to have control over how my personal data is published and shared
     * Who has this problem: Registered users of Act     * Who has this problem: Registered users of Act
     * Why this is important: [[wp>​GDPR]] is an EU regulation which "aims primarily to give control to individuals over their personal data".     * Why this is important: [[wp>​GDPR]] is an EU regulation which "aims primarily to give control to individuals over their personal data".
     * Related: [[https://​github.com/​book/​Act/​issues/​68|GitHub Issue 68: Non consent of attendee'​s data sharing between services and publicly available]]     * Related: [[https://​github.com/​book/​Act/​issues/​68|GitHub Issue 68: Non consent of attendee'​s data sharing between services and publicly available]]
 +  * I can't enter a secure GPG Id
 +    * Who has this problem: Users editing their user profile with a 64-bit GPG key
 +    * Why this is important: There are many 23 bit public key IDs that have collisions already, see http://​evil32.com
 +    * Related: [[https://​github.com/​book/​Act/​issues/​67|GitHub issue 65: "GPG public key ID field only permits weak 32 bit IDs]]
 +  * I want to log in with my Google account
 +    * Who has this problem: Users who want to identify themselves
 +    * Why this is important: Having Yet Another password to remember is annoying
 +    * Related: [[https://​github.com/​book/​Act/​issues/​56|GitHub issue 56: Allow to log in with a Google Account]]
 +  * I can't remove an unapproved talk from my schedule
 +    * Who has this problem: Members with talks_admin privilege
 +    * Why this is important: You can, by mistake, click on the star multiple times, messing up the favourite talks counter.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​43|GitHub issue 43: talks_admin members can add unapproved talks to the personal schedule multiple times]]
 +  * Annoying: When I attend to several conferences,​ I need to sign out and sign in each time
 +    * Who has this problem: Users having registered to more than one conference
 +    * Why this is important: Not a big issue according to the reporter (maddingue)
 +    * Related: [[https://​github.com/​book/​Act/​issues/​41|GitHub issue 41: allow to be connected to more than one conference]]
 +  * I can't submit a talk with more than one speaker
 +    * Who has this problem: Users who want to be speakers
 +    * Why this is important: Suggested by Rolf Langsdorf (YAPC::EU 2012)
 +    * Related: [[https://​github.com/​book/​Act/​issues/​37|GitHub issue 37: allow more than one speaker per talk]]
 +  * I can't pay for another person
 +    * Who has this problem: Act users who want to pay for another attendee
 +    * Why this is important: According to szabgab, There are many cases when the person who attends the event and the person who actually makes the payment are different.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​34|GitHub issue 34: separate person to arrange payment]]
 +  * I want to contact other Act users
 +    * Who has this problem: Act users
 +    * Why this is important: According to Dolmen, Act should help the participants to communicate between themselves.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​31|GitHub issue 31: List messaging accounts for all registered users]]
 +  * I want to contact other Act users over Twitter
 +    * Who has this problem: Act users
 +    * Why this is important: I have no idea.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​30|GitHub issue 30: Show Twitter account on profile]]
 +  * I want to add my Twitter username to my profile
 +    * Who has this problem: Act users
 +    * Why this is important: ...so that others can contact me.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​29|GitHub issue 29: Twitter username field in profile]]
 +  * I don't understand the changepwd form
 +    * Who has this problem: Users who forgot their password
 +    * Why this is important: Being asked for the current password after you have confessed that you've forgotten it is embarassing.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​25|GitHub issue 25: The changepwd form can be confusing]]
 +  * The Act user interface is too difficult to customize
 +    * Who has this problem: Organizers who want to define the UI for their conferences
 +    * Why this is important: Organizers lack the time, maybe also CSS or TT skills, to adapt the website to the expectations of their attendees and sponsors.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​52|GitHub issue 52: Replace ancient Jquery]], [[https://​github.com/​book/​Act/​issues/​19|GitHub issue 19: Modernize HTML]]
 +  * Registration workflow and terminology is confusing
 +    * Who has this problem: Act users, especially first-time visitors
 +    * Why this is important: The unclear workflow leads to wrong invoices which can't be corrected within the system.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​18|GitHub issue 18: Registration workflow and terminology is confusing]]
 +  * Lightning talk speakers must not get free registration
 +    * Who has this problem: Conference organizers
 +    * Why this is important: We are on a budget, aren't we?  Submitting a measly Lightning Talk should not be worth so much money.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​17|GitHub issue 17: Create new class of speaker - '​lightning talk speaker'​]]
 +  * I don't want to manually nudge speakers to either confirm or cancel their talks
 +    * Who has this problem: Conference organizers
 +    * Why this is important: Knowing which talks are actually being held is necessary for creating the conference schedule and, in case of cancellation,​ to accept another talk
 +    * Related: [[https://​github.com/​book/​Act/​issues/​15|GitHub issue 15: Cron/​Reminder email for unconfirmed talks until speaker confirms]]
 +  * As a sponsor, I don't want to register all my employees attending the conference separately
 +    * Who has this problem: Conference sponsors
 +    * Why this is important: For conference sponsors it isn't convenient to have every attendee to register and purchase her own ticket. ​ They also want _one_ invoice. ​ Confirmed with the main sponsor of the German Perl Workshop 2019.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​14|GitHub issue 14: New role for sponsors so they can bulk register / manage users]]
 +  * Having to creae a bunch of "​standard"​ pages for a conference Wiki is too time consuming
 +    * Who has this problem: Conference organizers
 +    * Why this is important: The Wiki is a place for attendees to exchange information. ​ "​Empty"​ Wikis are not inviting to contribute.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​13|GitHub issue 13: Templates for default wiki pages]]
 +  * I want to see events on my personal schedule
 +    * Who has this problem: Conference attendees
 +    * Why this is important: Attendees need to plan their stay including all the "​non-talk"​ stuff (e.g. registration).
 +    * Related: [[https://​github.com/​book/​Act/​issues/​12|GitHub issue 12: Events should show up on personal schedules]]
 +  * I want to see what's the next talk in a room
 +    * Who has this problem: Conference attendees
 +    * Why this is important: Sometimes there are changes to the schedule which the attendees have on their mobile phones, or they don't have the schedule available otherwise.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​10|GitHub issue 10: Schedule view by room]]
 +  * Printing the schedule is a mess
 +    * Who has this problem: Conference attendees preparing their visit
 +    * Why this is important: According to wolfsage, Each ACT owner likes to create their own layout/CSS, but maybe we should have a standard print CSS that works regardless, and they can edit it if they want? This would allow printing of good schedules
 +    * Related: [[https://​github.com/​book/​Act/​issues/​9|GitHub issue 9: Automatic CSS for printing of schedules]]
 +  * These badges are unreadable from more than 20cm distance!
 +    * Who has this problem: Attendees trying to figure out the name of the person they'​re talking to
 +    * Why this is important: Persons and their names are important. ​ The location and year aren'​t:​ Attendees can figure out where they are without consulting each others'​ badge.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​7|GitHub issue 7: Badge template + printing]]
 +  * I want to nudge all attendees who haven'​t paid in one go
 +    * Who has this problem: Conference organizers
 +    * Why this is important: Organizers are short on time before the conference. ​ Act could support them with "​standard"​ tasks.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​6|GitHub issue 6: Bulk email and templates]]
 +  * I want to be informed about new accepted talks
 +    * Who has this problem: People who are unsure whether the conference is worth it, or who need to convince their bosses or sponsors
 +    * Why this is important: The readiness to spend money for traveling, hotel, or sponsoring might depend on whether the conference offers talks which are relevant to one's targets.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​5|GitHub issue 5: Accepted Talks feed]]
 +  * The receipt that is auto-generated out of Act is not acceptable.
 +    * Who has this problem: Conference attendees who need to provide the receipt to their employer or similar
 +    * Why this is important: Being unable to get refunding for a conference ticket because the receipt doesn'​t fulfil the requirements is frustrating.
 +    * Related: [[https://​github.com/​book/​Act/​issues/​4|GitHub issue 4: Receipt Templates/​Fixes]]
 +
 +===== GitHub issues not included (yet) =====
 +  * [[https://​github.com/​book/​Act/​issues/​67|GitHub issue 67: "Other Act conferences"​ links sometimes 404]]
 +  * [[https://​github.com/​book/​Act/​issues/​46|GitHub issue 46: personal schedule star/unstar count handling is incorrect on multi-session talks]]
 +  * [[https://​github.com/​book/​Act/​issues/​44|GitHub issue 44: HTML title of a news entry should be the news title (not only "​News"​)]]
 +  * [[https://​github.com/​book/​Act/​issues/​40|GitHub issue 40: support generic key/value fields]]
 +  * [[https://​github.com/​book/​Act/​issues/​39|GitHub issue 39: please notify a range of sites/​online calendars of events]]
 +  * [[https://​github.com/​book/​Act/​issues/​38|GitHub issue 38: display rooms even when no talk is scheduled]]
 +  * [[https://​github.com/​book/​Act/​issues/​36|GitHub issue 36: include a "allow video recording"​ checkbox at talk submission/​edition]] - maybe implemented,​ no tests, maybe broken
 +  * [[https://​github.com/​book/​Act/​issues/​35|GitHub issue 35: include the talk title in the content of the page]] - implemented,​ no tests
 +  * [[https://​github.com/​book/​Act/​issues/​28|GitHub issue 28:Missing number in /stats]] - looks like a bug
 +  * [[https://​github.com/​book/​Act/​issues/​22|GitHub issue 22: CSS resources don't transfer correctly in PSGI branch]] - fixed, or isn't it?
 +  * [[https://​github.com/​book/​Act/​issues/​20|GitHub issue 20: All conference config should be editable from the web]] - done, via github push
 +  * [[https://​github.com/​book/​Act/​issues/​16|GitHub issue 16: Real talk descriptions vs teaser descriptions]] - implemented,​ or isn't it?
 +  * [[https://​github.com/​book/​Act/​issues/​11|GitHub issue 11: BOFs should be treated like talks]] - where'​s the problem?
 +  * [[https://​github.com/​book/​Act/​issues/​8|GitHub issue 8: Support for Facebook Connect]] - whatever this might be
 +  * [[https://​github.com/​book/​Act/​issues/​3|GitHub issue 3: Update the Wiki Toolkit to be more Robust/​extensive]]
 +  * [[https://​github.com/​book/​Act/​issues/​2|GitHub issue 2: Create events that are not tied to rooms]] - solved, or isn't it?
  
act-requirements-collection.txt ยท Last modified: 2019/05/28 11:36 by haj