42
21
Fork
You've already forked sustainability
9

FOSS Sustainability Fund 2024 #45

Merged
earl-warren merged 4 commits from :otf-2024 into main 2024年05月16日 19:14:25 +02:00

Refs: forgejo/discussions#144 (comment)

- [x] draft https://pad.gusted.xyz/aOKqNgHJSFmAbMEvo8fXKg?view - [x] update depending on @Gusted @crystal feedback (no feedback, they were removed) - [x] create otf-2024@forgejo.org - [x] create OTF account - [x] share TOTP secret with Forgejo contributors `gopass show websites/apply.opentech.fund/otf-2024@forgejo.org` - [x] save application draft ![image](/attachments/699703ea-31ad-428c-8f31-b29ec9f8f936) - [x] submit https://apply.opentech.fund/foss-sustainability-fund/ Refs: https://codeberg.org/forgejo/discussions/issues/144#issuecomment-1778384
Contributor
Copy link

Done, credentials saved in gopass.

> - [ ] create otf-2024@forgejo.org Done, credentials saved in gopass.
oliverpool added the due date 2024年05月16日 2024年05月09日 19:11:21 +02:00
earl-warren approved these changes 2024年05月15日 12:44:01 +02:00
Dismissed
Contributor
Copy link

The TOTP secret was saved in gopass show websites/apply.opentech.fund/otf-2024@forgejo.org

The TOTP secret was saved in `gopass show websites/apply.opentech.fund/otf-2024@forgejo.org`
@ -0,0 +29,4 @@
- the test suite is not easy to use and it creates frictions for contributors.
- large parts of the codebase still lack test coverage which leads to regressions, security issues and hinders contributors' abilities to participate.
* Funding - Forgejo is governed by a majority of volunteers who are estimated to also accomplish 80% of the work alongside a paid staff of three people. There is not enough funding to employ additional paid staff to keep that balance as the number of volunteers joining the project continues to grow.
* Data portability - the code to migrate to and from other forge software (GitHub, GitLab, ...) only covers part of the data they contain.
Member
Copy link
  • Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. For software federation a huge innovation journey has to be accomplished.
* Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. For software federation a huge innovation journey has to be accomplished.
Contributor
Copy link

I agree with what you wrote. But I also acknowledge it is off-topic for this section. It exclusively list sustainability problems. I would love it if you can find a way to shortly and clearly explain why federation is in critical need of funding to ensure Forgejo is durable. I cannot figure it out 🤔

I agree with what you wrote. But I also acknowledge it is off-topic for this section. It exclusively list **sustainability problems**. I would love it if you can find a way to shortly and clearly explain why federation is in critical need of funding to ensure Forgejo is durable. I cannot figure it out 🤔
Member
Copy link

Agree, let me try it again:

  • Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Federation is essential feature for forgejo developer community growth.
Agree, let me try it again: * Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Federation is essential feature for forgejo developer community growth.
Member
Copy link

I agree with what you wrote. But I also acknowledge it is off-topic for this section. It exclusively list sustainability problems. I would love it if you can find a way to shortly and clearly explain why federation is in critical need of funding to ensure Forgejo is durable. I cannot figure it out 🤔

Btw, the same argument is true for Data portability. Should we improve this argument also?

  • Data portability - the code to migrate to and from other forge software (GitHub, GitLab, ...) only covers part of the data they contain. The freedom to move to and from forgejo will be important for a stable growth of the forgejo user base.
> I agree with what you wrote. But I also acknowledge it is off-topic for this section. It exclusively list **sustainability problems**. I would love it if you can find a way to shortly and clearly explain why federation is in critical need of funding to ensure Forgejo is durable. I cannot figure it out 🤔 Btw, the same argument is true for Data portability. Should we improve this argument also? * Data portability - the code to migrate to and from other forge software (GitHub, GitLab, ...) only covers part of the data they contain. The freedom to move to and from forgejo will be important for a stable growth of the forgejo user base.
Contributor
Copy link

I think this is different because:

a) data portability is already partially implemented and used
b) the problem is expressed: "only covers part of the data"

the consequences of the problem are not explained but it is probably (?) ok to assume the reader knows about this topic.

I think this is different because: a) data portability is already partially implemented and used b) the problem is expressed: "only covers part of the data" the consequences of the problem are not explained but it is probably (?) ok to assume the reader knows about this topic.
Contributor
Copy link

Agree, let me try it again:

  • Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Federation is essential feature for forgejo developer community growth.

This is a good description of the positive impact of Federation, I'm 100% in agreement. I think what is needed here is the negative impact of insufficient momentum on federation development. How will sustainability be negatively impacted?

The more the discussion goes the more I would like to have this included 👍 Only I still can't figure out how to word it.

> Agree, let me try it again: > > * Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Federation is essential feature for forgejo developer community growth. This is a good description of the positive impact of Federation, I'm 100% in agreement. I think what is needed here is the **negative** impact of insufficient momentum on federation development. How will sustainability be negatively impacted? The more the discussion goes the more I would like to have this included 👍 Only I still can't figure out how to word it.
Member
Copy link

Okay, I try to be negative:

  • Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Without sustainable progress on federation the community growth needed is in danger.

If someone can imagine better wording help is very welcome.

Okay, I try to be negative: * Federation - insufficient momentum on federation development. Federation will allow community building and collaboration on OpenSource above the single forgejo instance borders. Without sustainable progress on federation the community growth needed is in danger. If someone can imagine better wording help is very welcome.

Federation is a solution to a problem rather than a problem. I propose to word it this way:

Scaling out - federation is not implemented and requires Forgejo to scale up instead of scaling out. It is orders of magnitude more costly and complex to design a centralized software that can scale up to 10,000,000 users than a federated software that can support 100,000 users spread over 100 instances.

It is more words than other lines because the problem needs to be explained with an example. The reviewer is unlikely to know why federation is critical to sustainability.

Federation is a solution to a problem rather than a problem. I propose to word it this way: > Scaling out - federation is not implemented and requires Forgejo to scale up instead of scaling out. It is orders of magnitude more costly and complex to design a centralized software that can scale up to 10,000,000 users than a federated software that can support 100,000 users spread over 100 instances. It is more words than other lines because the problem needs to be explained with an example. The reviewer is unlikely to know why federation is critical to sustainability.

69603106d5 add the proposed sentence and trim content from other lines to keep the number of words under 500 as required by the application form.

https://codeberg.org/forgejo/sustainability/commit/69603106d51f13e49323bf0c3d65835b0f1357d0 add the proposed sentence and trim content from other lines to keep the number of words under 500 as required by the application form.
oliverpool left a comment
Copy link

Looks good, thank you so much!

One suggestion regarding the (lack of) mention of gitea.

Looks good, thank you so much! One suggestion regarding the (lack of) mention of gitea.
@ -0,0 +315,4 @@
- Binary downloads https://codeberg.org/forgejo/forgejo/releases
- Runtime - Forgejo is a standalone binary that includes all its Go and JavaScript dependencies
- Go https://codeberg.org/forgejo/forgejo/src/branch/forgejo/go.mod
- infrastructure (chi, cors, swagger, gocron, ...)

There is no mention of gitea anywhere. I think it would be appropriate to indicate it as an upstream dependency:

 - infrastructure (gitea, chi, cors, swagger, gocron, ...)
There is no mention of `gitea` anywhere. I think it would be appropriate to indicate it as an upstream dependency: ``` - infrastructure (gitea, chi, cors, swagger, gocron, ...) ```

done at 7426ac7009

done at 7426ac7009f17f7fa24ae52bd799125297a3787e
Ghost marked this conversation as resolved

Submitted.

image

Submitted. ![image](/attachments/9c748336-c1d9-4024-8a65-fc761bab6d7f)
Contributor
Copy link

From: app@apply.opentech.fund
To: otf-2024@forgejo.org
Subject: Your application to Open Technology Fund: Forgejo (https://forgejo.org)

Dear Forgejo Contributors,

We appreciate your Forgejo (https://forgejo.org) application submission to the Open Technology Fund.

We will review and reply to your submission as quickly as possible.

If you have any questions, please submit them here: https://apply.opentech.fund/apply/submissions/16780/#communications

If you have issues accessing the submission system or general inquiries, please email us at hello@opentech.fund.

For more information about our support options, review process, and selection criteria, please visit our website at https://www.opentech.fund/.

Project name: Forgejo (https://forgejo.org)
Contact name: Forgejo Contributors
Contact email: otf-2024@forgejo.org

Kind Regards,
The OTF Team

> From: app@apply.opentech.fund > To: otf-2024@forgejo.org > Subject: Your application to Open Technology Fund: Forgejo (https://forgejo.org) > > Dear Forgejo Contributors, > > We appreciate your Forgejo (https://forgejo.org) application submission to the Open Technology Fund. > > We will review and reply to your submission as quickly as possible. > > If you have any questions, please submit them here: https://apply.opentech.fund/apply/submissions/16780/#communications > > If you have issues accessing the submission system or general inquiries, please email us at hello@opentech.fund. > > For more information about our support options, review process, and selection criteria, please visit our website at https://www.opentech.fund/. > > Project name: Forgejo (https://forgejo.org) > Contact name: Forgejo Contributors > Contact email: otf-2024@forgejo.org > > Kind Regards, > The OTF Team >
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
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2024年05月17日

Dependencies

No dependencies set.

Reference
forgejo/sustainability!45
Reference in a new issue
forgejo/sustainability
No description provided.
Delete branch ":otf-2024"

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?