Ask HN: Supporting a volunteered software project post-delivery
One of the hard things is the question of support and maintenance after the volunteer delivers the project.
Volunteers aren't going to want to be tied to a project forever, though I expect many will be happy to give some support.
Charities on the other hand won't always have the resources to pay for third party support.
My question is, what are some potentially viable ways to either avoid this problem in the first place or to provide an adequate level of support once the volunteer moves on.
All I can think of is ...
1. Handover to an internal team, assuming one exists 2. Limited support post delivery, which cramps the project in the first place 3. Just accepting that support is expensive, which also cramps the project. 4. Hoping that other volunteers will step in as needed, which won't always work for some kinds of support like urgent bug fixes 5. An agreement that all deliverables must be open-sourced, thus increasing the number of people who could potentially help out in a pinch
What else?