📚 node [[nonprofits should (almost) never write their own software]]
Welcome! Nobody has contributed anything to 'nonprofits should (almost) never write their own software' yet. You can:
  • Write something in the document below!
    • There is at least one public document in every node in the Agora. Whatever you write in it will be integrated and made available for the next visitor to read and edit.
  • Write to the Agora from social media.
    • If you follow Agora bot on a supported platform and include the wikilink [[nonprofits should (almost) never write their own software]] in a post, the Agora will link it here and optionally integrate your writing.
  • Sign up as a full Agora user.
    • As a full user you will be able to contribute your personal notes and resources directly to this knowledge commons. Some setup required :)
⥅ related node [[nonprofits should almost never write their own software]]
⥅ node [[nonprofits-should-almost-never-write-their-own-software]] pulled by Agora
📓 garden/neil/nonprofits-should-almost-never-write-their-own-software.md by @neil

Nonprofits should (almost) never write their own software

A : [[claim]]

From the [[Aspiration Manifesto]].

Being the tech lead for a non-profit that develops our own software - I fully agree. We are currently going through a process of trying to divest as much bespoke code as possible to pre-existing (FLOSS) software.

One alternative I see, where no other software exists for the desired purpose, is for non-profits to perhaps be incubators for the software, but always with an intention to [[exit to community]] / exit the software to cooperative.
📖 stoas
⥱ context
← back
2024 04 08

↑ pushing here
(none)

↓ pulling this
(none)
→ forward
(none)
🔎 full text search for 'nonprofits should (almost) never write their own software'