Pad for collaborative editing https://pad.gusted.xyz/3nv_0D4bTYy2rWa3LC96oQ#
User Research for the Roadmap #20
It would be worth reaching out to bernat & belen asking for mentoring. And hosting at the OSD FOSDEM room maybe.
Asked bernat https://mastodon.online/@dachary/109303652147281447
@Ryuno-Ki reached out to bernat regarding User Research https://mastodon.online/@dachary/109303652147281447 and he is one of the organizers of the OSD room at FOSDEM 2023. It would be a good context to be in for the final stage, when people get together to sort out the material collected with interviews etc. Would you like to follow-up with this and hopefully secure a room for a full day with their help (or not)?
I can do that. I have prior contact with the FOSDEM staff as well as a devroom organiser so I can figure out the steps needed. Or do we want to work on this under the umbrella of Open Source Design (OSD)?
I'd love to have some positive resonance first to make sure it's worth the effort.
Today, we talked about doing Affinity Mapping on some interviews (so interviews have to be done first).
Or do we want to work on this under the umbrella of Open Source Design (OSD)?
That would work for me.
I would avoid committing to a roadmap and instead open an issue tracker once the name is chosen. I believe the excitement of an unknown future will attract more of the kind of people you want to help make this a long-term sustainable project.
Of cuorse you could have some guidelines about what kinds of problems are both valid to tackle and worth maintaining, or you could let those guidelines themselves emerge from discussion.
If time allows it, we thought about picking up https://forum.forgefriends.org/t/use-case-ux-ui-code-to-create-a-federated-issue/774 (i.e. Penpot) again yesterday.
I can't tell the priority of this right now, though.
Also, it feels like this issue tries to handle too many things at once, so it might be better to break it up into smaller ones and close it.
I can't tell the priority of this right now, though.
Also, it feels like this issue tries to handle too many things at once, so it might be better to break it up into smaller ones and close it.
Agreed. This is in "meta" though and I believe user research deserves a repository of its own.
The OSD devroom is at https://fosdem.org/2023/schedule/track/open_source_design/
Bernat responded positively:
https://social.ei8fdb.org/@bernat/109309086093790143
First round of video call will be between him and @dachary.
Mainly, because Dachary is a bit flexibler with time schedule than me, so Bernat can already be set in picture before I will go into details.
In order to have the survey done as Codeberg, I can propose to the presidium to randomly email some Codeberg users with some recent activity and call them to get back in touch if they are interested.
Other than that, we can happily host announcements etc, but I think it's better done by not only picking the "proactive" user bubble.
@dachary Since I joined the last coworking space after you already lost the recording, the questions for interview ideas were not recorded.
Can you remember some prompts? I'm confident I can come up with things we are interested in or should keep in mind.
Feel free to create a pad if that's more in your way of working.
I don't really. A reason why I make notes and record things is that my memory is not very good.
Nevermind. codename/meta#20 (comment) 🤦
I could update at least some questions that I had on top of my mind as well as some links to further research on pitfalls.
Today I learned about https://nitter.net/giteaio/status/1542539195171983360#m and will look into whether we can adapt some of the questions shared as replies to that tweet.
Done.
User Research discussion scheduled at 6pm UTC+1 today with bernat at https://meet.jit.si/NovelMarginsSeparateDifferently everyone interested is welcome.
Recoding of the discussion is here https://cloud.forgefriends.org/s/isNsNsQ49EBLQTX
URLs discussed during the discussion
@dachary Only today I came around to listen to the recording.
Has there been any update to the survey questions?
Nothing was done. There are a lot of actionable items though :-)
Yepp, that's why I was asking: avoiding duplication of effort.
I will focus on the grant application first, though.
@rudolphfroger thanks for taking the time to file this feature request. Forgejo is still in its infancy and trying to figure out how to build a sensible roadmap. It would be great to have enough resources to implement all feature requests, but the reality is that some of them will happen sooner rather than later. IMHO this should be driven by user needs and it is the reason for this issue.
I get that it is a lot to take in when you just have a rather simple and straightforward feature request. I'm hoping you would be available for an interview or to fill a survey that would help Forgejo build a roadmap that you would approve.
What do you think?
https://communityblog.fedoraproject.org/community-design-team-part-1/ would they be inclined to help with Forgejo?
Introducing the Community Design Team
This is the first part of a two-part blog post series introducing the Community Design Team (CDT) to the Fedora Community. In this post, we’ll introduce you to all of the wonderful team members and the projects they’ve been working on. In Part 2, we’ll explain how you can reach our team, make a request, and work with us!
@rudolphfroger thanks for taking the time to file this feature request. Forgejo is still in its infancy and trying to figure out how to build a sensible roadmap. It would be great to have enough resources to implement all feature requests, but the reality is that some of them will happen sooner rather than later. IMHO this should be driven by user needs and it is the reason for this issue.
I get that it is a lot to take in when you just have a rather simple and straightforward feature request. I'm hoping you would be available for an interview or to fill a survey that would help Forgejo build a roadmap that you would approve.
What do you think?
Sure, I'd like to help. I totally understand that developer time is scarse, especially so on community projects. I can also try if I can help with a PR or maybe I can check if my company can sponsor the feature, if that's an option.
Do you mind to fill an issue with forgejo/funding repo if your company would sponsor feature development? Would be amazing!
Sure, I'd like to help. I totally understand that developer time is scarse, especially so on community projects. I can also try if I can help with a PR or maybe I can check if my company can sponsor the feature, if that's an option.
@rudolphfroger could you please try to fill this survey? It is perfectly fine if you focus on telling stories directly related to the feature you would like to see implemented. It would go a long way to put it on the map / roadmap.
We're at the very first steps of user research, please be blunt if something is confusing or does not make intuitive sense.
User research is happening in https://codeberg.org/forgejo/user-research now.
No due date set.
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?