42
21
Fork
You've already forked sustainability
9

Initial Dutch government OSPO call #137

Merged
Gusted merged 7 commits from :dutch-ospo into main 2025年11月23日 18:50:27 +01:00
See https://codeberg.org/forgejo/discussions/issues/412 and #136
@ -0,0 +133,4 @@
== Experience with large institutions/governments
/Gi:Haveyouworkedwithgovernmentsinb4?
Member
Copy link

inb4 -> before

"inb4" is "in before" as in "a prediction that something will happen".

P.S. I generally don't oppose using coded speech like that because the meeting notes are written from the perspective of the author, so I'm deliberately choosing to correct whatever deviates from "the tone" of what transpired.

`inb4` -> `before` "inb4" is "in before" as in "a prediction that something will happen". P.S. I generally don't oppose using coded speech like that because the meeting notes are written from the perspective of the author, so I'm deliberately choosing to correct whatever deviates from "the tone" of what transpired.
Author
Contributor
Copy link

TIL. Thanks!!

TIL. Thanks!!
MultisampledNight marked this conversation as resolved
@ -0,0 +1,305 @@
#import"@preview/flow:0.3.2":*
#show:note.with(
title:"ForgejoDutchGovermentcallnotes",
Member
Copy link

Typo: Goverment -> Government

Typo: `Goverment` -> `Government`
Author
Contributor
Copy link

Ran typos over it, it spotted a few other typos as well. Thanks!! Fixed.

Ran `typos` over it, it spotted a few other typos as well. Thanks!! Fixed.
MultisampledNight marked this conversation as resolved
Author
Contributor
Copy link

Also compiled to a PDF. Let me know if that is undesired, will just revert that commit then.

Positive sidenote: Getting useful and boilerplate-free feedback like this greatly reduces my anxiety regarding the branch state before opening a PR. I feel much more comfortable to open a PR under any Forgejo repo now.

Also compiled to a PDF. Let me know if that is undesired, will just revert that commit then. Positive sidenote: Getting useful and boilerplate-free feedback like this greatly reduces my anxiety regarding the branch state before opening a PR. I feel much more comfortable to open a PR under any Forgejo repo now.
Member
Copy link

I feel much more comfortable to open a PR under any Forgejo repo now.

I am glad to hear that. I think it's a thing that also comes with experience, because at the beginning I was like "oh no, I made a typo, what will be made of my own permanent record!" and nowadays I just force-push literally a thousand times in real-time. :D

It's fineee.

> I feel much more comfortable to open a PR under any Forgejo repo now. I am glad to hear that. I think it's a thing that also comes with experience, because at the beginning I was like "oh no, I made a typo, what will be made of my own *permanent record*!" and nowadays I just force-push literally a thousand times in real-time. :D It's fineee.
n0toose approved these changes 2025年11月12日 16:40:16 +01:00
Dismissed
n0toose left a comment
Copy link

Worth squashing and merging, I find. I think this is fine and the PDF will land in Git LFS anyways on its own. :)

P.S. I contributed to the protocol myself, not sure if this should exclude me from approving this PR.

Worth squashing and merging, I find. I think this is fine and the PDF will land in Git LFS anyways on its own. :) P.S. I contributed to the protocol myself, not sure if this should exclude me from approving this PR.

@n0toose wrote in #137 (comment):

P.S. I contributed to the protocol myself, not sure if this should exclude me from approving this PR.

I think, the opposite is true. People who participated should approve it! (I participated only reading the live protocol. That doesn't count ☺️)

@n0toose wrote in https://codeberg.org/forgejo/sustainability/pulls/137#issuecomment-8249849: > P.S. I contributed to the protocol myself, not sure if this should exclude me from approving this PR. I think, the opposite is true. People who participated should approve it! (I participated only reading the live protocol. That doesn't count ☺️)
@ -0,0 +129,4 @@
/O:https://forgejo.org/2024-02-forking-forward/
-Norelationexceptforsecurityreleases
-Attemptsatcooperationandcoordinationdidnotworkoutqwq
Owner
Copy link

qwq?

qwq?
Member
Copy link

I think the author intended to convey an expression of disappointment using internet speech, see also: https://www.urbandictionary.com/define.php?term=qwq

I think the author intended to convey an expression of disappointment using internet speech, see also: https://www.urbandictionary.com/define.php?term=qwq
Author
Contributor
Copy link

Given the confusion, I'll adjust this. Thanks!

Given the confusion, I'll adjust this. Thanks!
Gusted marked this conversation as resolved
@ -0,0 +144,4 @@
/Gu:Yes,butusuallyrathertechnicalquestions
-e.g."Whyisthisslow?","HowcanIprofilethis?"
-Resultinissueslikeanyother
Owner
Copy link

like any other...? IIRC it was something along the lines of "This then usually results in issues being opened and is then treated like any other issue, no prioritization"

like any other...? IIRC it was something along the lines of "This then usually results in issues being opened and is then treated like any other issue, no prioritization"
Member
Copy link

I interpreted this the way you are describing, but this was "obvious" to me because I was there. It may not be obvious for others.

I interpreted this the way you are describing, but this was "obvious" to me because I was there. It may not be obvious for others.
Author
Contributor
Copy link

Acknowledged -- requires excessive context to understand atm. Will fix.

Acknowledged -- requires excessive context to understand atm. Will fix.
MultisampledNight marked this conversation as resolved
Gusted left a comment
Copy link

Thanks!

Thanks!
Sign in to join this conversation.
Labels
Clear labels
NLnet
2022年08月01日
NLnet grant application submitted August 2022
NLnet
2022年12月01日
NLnet grant application submitted December 2022
NLnet
2024年04月01日
NLnet grant application submitted April 2024

Archived

NLnet
2024-04-364
NLnet grant application submitted April 2025 (was "backported" by NLnet internally)
OTF
2024年05月17日
OTF grant application submitted May 2024

Archived

STF
2024年08月15日
Sovereign Tech Fund application submitted August 2024
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
5 participants
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
forgejo/sustainability!137
Reference in a new issue
forgejo/sustainability
No description provided.
Delete branch ":dutch-ospo"

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?