forgejo/discussions
49
43

Forgejo v8 Upgrade / Install Party #198

Closed
opened 2024年07月24日 12:13:29 +02:00 by fnetX · 5 comments
Owner
Copy link

continuation of a thought from #197

What do you think of a Forgejo install party, following the release. During my time spent with user research, it was pretty interesting to observe admins install and configure Forgejo, help them right away and learn about setups right away (IIRC @0ko wanted to learn about the Forgejo deployments, too).

It would also be interesting to ask admins not to prepare for the meeting and observe them from the start: do they read the release notes? Do they understand them? Do they have questions? Do they check things in detail? Do they just run an upgrade script and don't care? Do they make backups as recommended? Do they run into challenges?

I would be really motivated to do this in a live meeting where Forgejo contributors join and help.

This weekend would be a nice chance, but unfortunately, I cannot commit much time. Although early feedback is better than everything else, we might also just do a less useful (but still exciting) experiment and run it one week later, e.g. Friday 02 August.

continuation of a thought from https://codeberg.org/forgejo/discussions/issues/197 What do you think of a Forgejo install party, following the release. During my time spent with user research, it was pretty interesting to observe admins install and configure Forgejo, help them right away and learn about setups right away (IIRC @0ko wanted to learn about the Forgejo deployments, too). It would also be interesting to ask admins not to prepare for the meeting and observe them from the start: do they read the release notes? Do they understand them? Do they have questions? Do they check things in detail? Do they just run an upgrade script and don't care? Do they make backups as recommended? Do they run into challenges? I would be really motivated to do this in a live meeting where Forgejo contributors join and help. This weekend would be a nice chance, but unfortunately, I cannot commit much time. Although early feedback is better than everything else, we might also just do a less useful (but still exciting) experiment and run it one week later, e.g. Friday 02 August.
Author
Owner
Copy link

Given the Forgejo release is unlikely to happen before the weekend, this is actually fine.

I recommend to schedulle for Friday, August 2, 18.00 CEST or 16.00 UTC via https://talk.tchncs.de/room/90dd171d-51eb-47e7-be1f-b40f2643b4eb?invite=00228865-60ea-45e2-8880-139647f26ff0

I am pinging some Forgejo maintainers to see if there would be enough human power available, and will then try to advertize the event accordingly.

Given the Forgejo release is unlikely to happen before the weekend, this is actually fine. I recommend to schedulle for Friday, August 2, 18.00 CEST or 16.00 UTC via https://talk.tchncs.de/room/90dd171d-51eb-47e7-be1f-b40f2643b4eb?invite=00228865-60ea-45e2-8880-139647f26ff0 I am pinging some Forgejo maintainers to see if there would be enough human power available, and will then try to advertize the event accordingly.
Author
Owner
Copy link

My concept in a sketch:

  • people join the meeting and can have small talk and general exchange or ask specific questions
  • if they want, they are invited to join a breakout room and
    • if they didn't take a look at the release notes yet, they can read them and we observe if and how they understand them, if there are confusing points etc
    • they can perform the upgrade or installation and we observe their workflow and potential roadblockers
  • even if the user research aspect doesn't work out well, I do believe that this will give us important insights and eventually allow us to identify and fix bugs on the fly, together
My concept in a sketch: - people join the meeting and can have small talk and general exchange or ask specific questions - if they want, they are invited to join a breakout room and - if they didn't take a look at the release notes yet, they can read them and we observe if and how they understand them, if there are confusing points etc - they can perform the upgrade or installation and we observe their workflow and potential roadblockers - even if the user research aspect doesn't work out well, I do believe that this will give us important insights and eventually allow us to identify and fix bugs on the fly, together
Owner
Copy link

Friday, August 2, 18.00 CEST or 16.00 UTC

I will be available. 👍

I will think of stuff to do, good thing that you started planning beforehand this time.


Ping in first message did not work.

> Friday, August 2, 18.00 CEST or 16.00 UTC I will be available. 👍 I will think of stuff to do, good thing that you started planning beforehand this time. --- _Ping in first message did not work._

Is there post-mortem of this event that could be mentioned in the monthly report?

Is there post-mortem of this event that could be mentioned in the monthly report?
Author
Owner
Copy link

What about:

The install party was a nice community meetup and we got to know some Forgejo users. Some users performed their updates live and had only minor issues that were mostly caused by an issue on their end. Due to the lack of actual problems, some might have perceived it as boring. Finally, it was decided to also upgrade Codeberg to Forgejo v8, which was also a smooth experience.

What about: The install party was a nice community meetup and we got to know some Forgejo users. Some users performed their updates live and had only minor issues that were mostly caused by an issue on their end. Due to the lack of actual problems, some might have perceived it as boring. Finally, it was decided to also upgrade Codeberg to Forgejo v8, which was also a smooth experience.
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#198
Reference in a new issue
forgejo/discussions
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?