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

Add a (post-choice) survey to determine who is using Chooser and for what purposes #389

Open
brylie opened this issue Jan 27, 2022 · 1 comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@brylie
Copy link
Contributor

brylie commented Jan 27, 2022

We would like to know more about the types of people who use the CC license Chooser. E.g., are they artists, academics, publishers, etc.? Where are they located?

Determine how we might allow the communications team to provide a non-invasive exit survey for Chooser users to gain more insights into the tool's use.

@brylie brylie added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Jan 27, 2022
@codewithmide
Copy link

We would like to know more about the types of people who use the CC license Chooser. E.g., are they artists, academics, publishers, etc.? Where are they located?

Determine how we might allow the communications team to provide a non-invasive exit survey for Chooser users to gain more insights into the tool's use.

Hello, would you suggest that we add a new input element in the attribution details with the options you have stated above?
Screenshot 2023-03-21 at 14 45 06

@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 💻 aspect: code Concerns the software code in the repository labels Aug 7, 2024
@TimidRobot TimidRobot moved this to Backlog in possumbilities Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

3 participants