Various updates to the FAQ #662

fnetX · 2025-08-12T21:00:28+02:00

fnetX commented

2025-08-12 21:00:28 +02:00

No description provided.

fnetX referenced this pull request

2025-08-12 21:01:26 +02:00

WIP: FAQ: Remove avatar size constraints, adjust headers #661

renovate-bot commented

2025-08-12 21:04:44 +02:00

Surge PR preview deployment was removed

Surge PR preview deployment was removed

momar reviewed

2025-08-12 21:28:34 +02:00

content/getting-started/faq.md

					
				@ -161,0 +172,4 @@

				  Adding billing systems and expanding our infrastructure to act as a generic hosting for all kinds of proprietary projects is a lot of effort for little benefit. It would likely hurt our community aspects and is challenging due to us being bound to the bylaws of the non-profit association. We're happy with our organic growth and don't need to accelerate it further.

				- Storage and CI/CD resources: We'll happily accept projects of any size.

				  However, if we determine that your resource demand is higher than necessary,

				  we won't sell a free pass for wasting precious computing resources.

I think that last part sounds a bit passive-aggressive, maybe it could be a bit more positive while still bringing the point across. What about something like this?

We'll happily accept cool projects of any size independent from payment or donations. However, if you're using an unproportionally huge amount of resources, we'd rather ask you to pay some attention to the environmental impact of your project first, instead of having anyone pay huge amounts of money to ignore it.

I think that last part sounds a bit passive-aggressive, maybe it could be a bit more positive while still bringing the point across. What about something like this? > We'll happily accept cool projects of any size independent from payment or donations. However, if you're using an unproportionally huge amount of resources, we'd rather ask you to pay some attention to the environmental impact of your project first, instead of having anyone pay huge amounts of money to ignore it.

👍 2

fnetX marked this conversation as resolved

momar approved these changes

2025-08-12 21:29:06 +02:00

n0toose reviewed

2025-08-12 22:02:49 +02:00

content/getting-started/faq.md

					
				@ -161,0 +164,4 @@

				However, as we want to provide every free/libre software project with equal chances and the resources they need,

				we do not require payment for any specific service.

				For your convenience, we allow [small amounts of work](#how-about-private-repositories%3F) that are not 100% compliant.

suggestion: certain works

small amounts of work sounds like "small amounts of work you've put in" or "we allow noncompliant repos as long as you've only worked a low amount on them"

suggestion: `certain works` small amounts of work sounds like "small amounts of work you've put in" or "we allow noncompliant repos as long as you've only worked a low amount on them"

"certain works" on the other hand sounds like it depends on the (type of) work. Currently, we only care about the size.

I spotted one use of "small amounts of works" online: https://guides.lib.umich.edu/c.php?g=283105&p=6687646

It's a minor grammar fix that gets the nuance across exactly as you want it without altering the substance.

I spotted one use of "small amounts of works" online: https://guides.lib.umich.edu/c.php?g=283105&p=6687646 It's a minor grammar fix that gets the nuance across exactly as you want it without altering the substance.

👍 1

fnetX marked this conversation as resolved

content/getting-started/faq.md

					
				@ -161,0 +168,4 @@

				However, we do not allow payment for exceptions to the rules.

				- Proprietary or private content: We're on a mission to support free/libre software development.

I think it might be worth saying that our nonprofit status depends on this (Bylaws etc.) more directly in a single sentence. "challenge" (mentioned later) is vague.

content/getting-started/faq.md

					
				@ -161,0 +169,4 @@

				However, we do not allow payment for exceptions to the rules.

				- Proprietary or private content: We're on a mission to support free/libre software development.

				  Adding billing systems and expanding our infrastructure to act as a generic hosting for all kinds of proprietary projects is a lot of effort for little benefit. It would likely hurt our community aspects and is challenging due to us being bound to the bylaws of the non-profit association. We're happy with our organic growth and don't need to accelerate it further.

our community aspects: which?

ideas:
"it would deter people from volunteering"
"we wouldn't give projects what they need, we'd only give them privileges based on how much the owner is willing to pay"

our community aspects: which? ideas: "it would deter people from volunteering" "we wouldn't give projects what they *need*, we'd only give them *privileges* based on how much the owner is willing to pay"

I don't know if this is a level of detail appropriate to the FAQ.

content/getting-started/faq.md

					
				@ -161,0 +171,4 @@

				- Proprietary or private content: We're on a mission to support free/libre software development.

				  Adding billing systems and expanding our infrastructure to act as a generic hosting for all kinds of proprietary projects is a lot of effort for little benefit. It would likely hurt our community aspects and is challenging due to us being bound to the bylaws of the non-profit association. We're happy with our organic growth and don't need to accelerate it further.

				- Storage and CI/CD resources: We'll happily accept projects of any size.

				  However, if we determine that your resource demand is higher than necessary,

"than necessary"?

I'd say " justifiably", because that might insinuate that "users may provide a justification" wherever the resource usage is not too high beyond reasonable doubt.

but I "really* like the "any size" part. I think you could strengthen it further by saying something like "even if your project uses a lot of resources, well, uh, that's what people give us money for so we'd like to make it work!" – it would definitely be relieving to all of those game developers.

"than necessary"? I'd say " justifiably", because that might insinuate that "users may provide a justification" wherever the resource usage is not too high beyond reasonable doubt. but I "really* like the "any size" part. I think you could strengthen it further by saying something like "even if your project uses a lot of resources, well, uh, that's what people give us money for so we'd like to make it work!" – it would definitely be relieving to all of those game developers.

fnetX marked this conversation as resolved

gedankenstuecke reviewed

2025-08-12 22:11:14 +02:00

gedankenstuecke left a comment

With my suggestions I tried to keep the spirit you went for and suggested @fnetX, trying to balance both the firm stance/clarity with not being too negative.

content/getting-started/faq.md

					
				@ -161,0 +164,4 @@

				However, as we want to provide every free/libre software project with equal chances and the resources they need,

				we do not require payment for any specific service.

				For your convenience, we allow [small amounts of work](#how-about-private-repositories%3F) that are not 100% compliant.

Maybe also worth mentioning here that this also applies to the storage quotas generally?

If you need more storage than the default quotas for your FOSS work, [you can request a higher quota](link here). For your convenience, we also allow [small amounts of works](#how-about-private-repositories%3F) that are not 100% compliant

Maybe also worth mentioning here that this also applies to the storage quotas generally? ``` If you need more storage than the default quotas for your FOSS work, [you can request a higher quota](link here). For your convenience, we also allow [small amounts of works](#how-about-private-repositories%3F) that are not 100% compliant ```

@gedankenstuecke this is literally explained in the question above. I don't think that we should provide every answer to every question. One answer per question is enough :)

gedankenstuecke marked this conversation as resolved

content/getting-started/faq.md

					
				@ -161,0 +166,4 @@

				we do not require payment for any specific service.

				For your convenience, we allow [small amounts of work](#how-about-private-repositories%3F) that are not 100% compliant.

				However, we do not allow payment for exceptions to the rules.

However, we do not accept any payments for exceptions to our rules:

``` However, we do not accept any payments for exceptions to our rules: ```

fnetX marked this conversation as resolved

content/getting-started/faq.md

					
				@ -161,0 +168,4 @@

				However, we do not allow payment for exceptions to the rules.

				- Proprietary or private content: We're on a mission to support free/libre software development.

- **Proprietary or private content**: The goal of our non-profit association is to support free/libre software development, not to become a "general-purpose Codeforge" like commercial Codeforges are. Adding such payment-based support for proprietary features would not only potentially challenge our non-profit status, but also hurt our community aspect.  It would also require substantial time & energy to support such efforts, that we would rather spend on support free/libre projects.

``` - **Proprietary or private content**: The goal of our non-profit association is to support free/libre software development, not to become a "general-purpose Codeforge" like commercial Codeforges are. Adding such payment-based support for proprietary features would not only potentially challenge our non-profit status, but also hurt our community aspect. It would also require substantial time & energy to support such efforts, that we would rather spend on support free/libre projects. ```

fnetX marked this conversation as resolved

content/getting-started/faq.md

					
				@ -161,0 +170,4 @@

				- Proprietary or private content: We're on a mission to support free/libre software development.

				  Adding billing systems and expanding our infrastructure to act as a generic hosting for all kinds of proprietary projects is a lot of effort for little benefit. It would likely hurt our community aspects and is challenging due to us being bound to the bylaws of the non-profit association. We're happy with our organic growth and don't need to accelerate it further.

				- Storage and CI/CD resources: We'll happily accept projects of any size.

- **Storage and CI/CD resources**: We happily accept free/libre projects of any size, within the realm of what our infrastructure can provide, independent of donations or payments. However, given that our infrastructure and the environment are common goods, please do not be wasteful with these resources and try to optimize your use of them. If your project hits to our resource limits despite best efforts of optimising, please reach out to us via email to discuss options.

``` - **Storage and CI/CD resources**: We happily accept free/libre projects of any size, within the realm of what our infrastructure can provide, independent of donations or payments. However, given that our infrastructure and the environment are common goods, please do not be wasteful with these resources and try to optimize your use of them. If your project hits to our resource limits despite best efforts of optimising, please reach out to us via email to discuss options.

"via email" is usually not the good idea. Chances are high that we won't manage to actually discuss with them. If possible, everything should be discussed in public, to allow other community members to respond.