- Minneapolis
- https://agaric.coop
-
I try to aid struggles for justice and liberty, or try not to do harm in the meantime. He is a web developer with Agaric Technology Collective and an organizer of People Who Give a Damn.
-
Joined on
2022年09月08日
@Gusted yeah, i tried with all permissions even though i'd already given all read permissions, but after i figured out after initially posting, this is the message Forgejo gives in response to the...
As updated above, a workaround is simply to enable the repository on the GitLab side. In our case there happened to be a single over 8 year old file in the repository from before we turned it...
OK, after deleting the Library of Congress Authority ID (which i put in the "LCCN" identifier from the copyright page, 2017042771, for; maybe that was incorrect?) it created the work.
Cool, good to know! In our case it is definitely a mix of public and private, but maybe we could/should run two forges, one for private client work and one for public...
OK i'm old-school, but client-side validation is never a replacement, but rather an enhancement, for server-side validation, so protecting the loss of entered content should still be handled on...
This is not a minor issue— losing user input is moderate to severe. The exact same problem comes up when editing an organization's settings. And lets look at it in the context that it just...
When an admin invites a person to an org by e-mail address, and then an admin creates an account for them (with the same e-mail address) and adds them to that org, the initial e-mail remains in...
Update: The invite link in the initial e-mail does work for a person to add themselves to an organization once that person has an account and is able to log in, but i doubt anybody will be going...
To describe the use-case a little bit better, we are a web development firm (a cooperative building open source solutions, but any tech services agency would run into the same issue using Forgejo,...
fnetX's proposal above is good but i think should be a separate issue.
The current state of Forgejo invitations when the...
On the database level, it looks like what i feared would be the hard part (keeping the existing labels working for the original repo when moved to the org) would be easy to do: fill in the...
100% agree on the importance of allowing confidential (private) tickets in the issue queue of a public repository, especially for open source free software development.
The corresponding issue...
@algernon given that i am at-mentioning you with the @ symbol and presumably would never do that for a group— is it possible still to use a different reserved symbol? Also having two @s in...
Coming to give a big +1 to this and to say that Agaric has the exact same need. To aid discoverability (because i looked hard to avoid opening a duplicate issue) here is what i searched for:
...