-
-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sovereign Tech Fund and NLNet Application #1406
Comments
Thanks! I've joined the organization. By the way, it looks like the link above, in the 2024-10-11 section, is broken: Even though it looks like the organization was initially named Edit: I've noticed that https://github.com/orgs/GitoxideLabs/people, as viewed when logged out or when logged in with an account that is not a member of the organization, only shows me. Especially since this repository has already been moved to the organization, you may want to mark your own membership in the organization as public. I think you should have a drop-down menu on that page that lets you do so. |
Thank you for joining, and thanks for all the useful hints :). The link above is now fixed, and I set my group membership to public as well. |
This updates `Byron/gitoxide` URLs to `GitoxideLabs/gitoxide` in: - Markdown documentation, except changelogs and other such files where such changes should not be made. - Documentation comments (in .rs files). - Manifest (.toml) files, for the value of the `repository` key. - The comments appearing at the top of a sample hook that contains a repository URL as an example. When making these changes, I also allowed my editor to remove trailing whitespace in any lines in files already being edited (since, in this case, there was no disadvantage to allowing this). The gitoxide repository URL changed when the repository was moved into the recently created GitHub organization `GitoxideLabs`, as detailed in GitoxideLabs#1406. Please note that, although I believe updating the URLs to their new canonical values is useful, this is not needed to fix any broken links, since `Byron/gitoxide` URLs redirect (and hopefully will always redirect) to the coresponding `GitoxideLabs/gitoxide` URLs. While this change should not break any URLs, some affected URLs were already broken. This updates them, but they are still broken. They will be fixed in a subsequent commit. This also does not update `Byron/gitoxide` URLs in test fixtures or test cases, nor in the `Makefile`. (It may make sense to change some of those too, it is not really a documentation change.)
This updates `Byron/gitoxide` URLs to `GitoxideLabs/gitoxide` in: - Markdown documentation, except changelogs and other such files where such changes should not be made. - Documentation comments (in .rs files). - Manifest (.toml) files, for the value of the `repository` key. - The comments appearing at the top of a sample hook that contains a repository URL as an example. When making these changes, I also allowed my editor to remove trailing whitespace in any lines in files already being edited (since, in this case, there was no disadvantage to allowing this). The gitoxide repository URL changed when the repository was moved into the recently created GitHub organization `GitoxideLabs`, as detailed in GitoxideLabs#1406. Please note that, although I believe updating the URLs to their new canonical values is useful, this is not needed to fix any broken links, since `Byron/gitoxide` URLs redirect (and hopefully will always redirect) to the coresponding `GitoxideLabs/gitoxide` URLs. While this change should not break any URLs, some affected URLs were already broken. This updates them, but they are still broken. They will be fixed in a subsequent commit. This also does not update `Byron/gitoxide` URLs in test fixtures or test cases, nor in the `Makefile`. (It may make sense to change some of those too, but it is not really a documentation change.)
This updates `Byron/gitoxide` URLs to `GitoxideLabs/gitoxide` in: - Markdown documentation, except changelogs and other such files where such changes should not be made. - Documentation comments (in .rs files). - Manifest (.toml) files, for the value of the `repository` key. - The comments appearing at the top of a sample hook that contains a repository URL as an example. When making these changes, I also allowed my editor to remove trailing whitespace in any lines in files already being edited (since, in this case, there was no disadvantage to allowing this). The gitoxide repository URL changed when the repository was moved into the recently created GitHub organization `GitoxideLabs`, as detailed in GitoxideLabs#1406. Please note that, although I believe updating the URLs to their new canonical values is useful, this is not needed to fix any broken links, since `Byron/gitoxide` URLs redirect (and hopefully will always redirect) to the coresponding `GitoxideLabs/gitoxide` URLs. While this change should not break any URLs, some affected URLs were already broken. This updates them, but they are still broken. They will be fixed in a subsequent commit. This also does not update `Byron/gitoxide` URLs in test fixtures or test cases, nor in the `Makefile`. (It may make sense to change some of those too, but it is not really a documentation change.)
This issue tracks the status for the application to https://www.sovereigntechfund.de (STF) as well as to https://nlnet.nl .
Note that the STF is mutually exclusive, but the idea is to have options.
PLAN: apply - and if there could be funds, go all the way with website, opencollective, and whatever else there might be.
Tasks
Timeline
2024-06-18
Start filling out the form for NlNet but reach out them instead for guidance.
The idea is that my questions affect the STF similarly, and knowing what they think should help. Will not block on this for too long, and plan to do the STF application soonish.
2024-06-22
Can OpenCollective alleviate the need for a foundation to be able to receive an spend money (hassle-free, without taxes, but while allowing invoicing of sorts?)
Setup personal account.
gitoxide
eligible❓(see requirements)aren'tare tax-deductableParticularly interesting: one can incorporate yourself while still using features of the OSC platform as independent collective, without any platform fees. So if one wanted to create a foundation at some point, it could still use some of the tooling one has become accustomed to.
Applying to Open Collective Europe seems to be the way to go, but Ferrous Systems might be an option as well.
2024-06-23
Check how it would be possible to go for 'gemeinnütziger Verein' right away. Details are this chat.
Learnings: it needs 7 founding members, which is probably where this idea ends. However, if an incorporation would work, it would be really easy to use Wise for accounting.
Also took a first look at the STF application form.
2024-07-22
Create Gist to allow writing the text on the fly: https://gist.github.com/Byron/d25b140ca42626f0a18f62372b7c5290#tbd-titles-can-be-linked-to-from-the-pff-they-are-anchors . Plan is to write it while in the train or using public transportation.
2024-09-26
Reached out to Ferrous Systems to see if they want to host Gitoxide.
It's unclear to me how to create a collective for Gitoxide that is assigned to their host though, as the standard dialog for that talks about OpenCollective as fiscal host. However, it seems changing hosts is very possible, but let's be sure to wait to avoid receiving donations with the wrong fiscal host.
2024-10-01
Also sent the above text as email to ferrous-systems.com .
2024-10-04
Also sent the above text as email to Florian and Felix Gilcher.
2024-10-09
Applied to open collective.
2024-10-11
Got response from Open Collective, they need the repo to be part of an organization.
It's time to take that step then.
Create organization. Prep to move, and move!
Invited @EliahKagan as collaborator, which seems like a natural choice given his prior involvement and accomplishments. It's also a requirement to get the fiscal host approved on open collective, even though the collective itself is already there: https://opencollective.com/gitoxide
2024-10-22
Register on https://apply.sovereigntechfund.de , take a first look.
2024-11-23
The text was updated successfully, but these errors were encountered: