Workflow sketch: Projects #7

Open
opened 2024年10月14日 18:22:32 +02:00 by fnetX · 0 comments
Owner
Copy link

The target audience for the project side are both user testers / researchers as well as project maintainers / developers who would like to get into the topic without committing to live user interviews.

The general setup could look like this:

  • an instance is set up and connected with a software development platform like Codeberg
  • users can use OAuth to sign in to the platform
  • the software ensures a consistent mapping between the user/org scopes (so that "codeberg" and "forgejo" map to the respective organizations on Codeberg.org, respectively)
  • it would probably need to handle renames and updates to user data gracefully
  • permissions could be mirrored from Forgejo instances (e.g. members of the Owners team are treated as admins of an organization and can manage further permissions for a project, and enable certain Forgejo teams (e.g. "user research") to gain more privileges, too

The basic idea for a management would be:

  • you see a list of research topics and a way to add new
    • adding a new one allows you to configure details like name, introduction, some custom text, session length (and potentially something like an "end date" in the future)
    • edit and delete functionality present
    • access / permission management for the data
  • there is an indicator of available and unseen recordings per topic

I will move my ideas regarding review of sessions to a separate issue.

The target audience for the project side are both user testers / researchers as well as project maintainers / developers who would like to get into the topic without committing to live user interviews. The general setup could look like this: - an instance is set up and connected with a software development platform like Codeberg - users can use OAuth to sign in to the platform - the software ensures a consistent mapping between the user/org scopes (so that "codeberg" and "forgejo" map to the respective organizations on Codeberg.org, respectively) - it would probably need to handle renames and updates to user data gracefully - permissions could be mirrored from Forgejo instances (e.g. members of the Owners team are treated as admins of an organization and can manage further permissions for a project, and enable certain Forgejo teams (e.g. "user research") to gain more privileges, too The basic idea for a management would be: - you see a list of research topics and a way to add new - adding a new one allows you to configure details like name, introduction, some custom text, session length (and potentially something like an "end date" in the future) - edit and delete functionality present - access / permission management for the data - there is an indicator of available and unseen recordings per topic I will move my ideas regarding review of sessions to a separate issue.
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/usertesting#7
Reference in a new issue
Codeberg/usertesting
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?