Project Hosting

DevProgress invests in Community Architecture and infrastructure that supports all our projects generally. The projects we are willing to pay for, so far, have been generated by campaign asks. We're hopeful that some community ideas will come up with metrics and can make their case for funding based on the metrics doc we posted in #team-metrics, but, Generally, even the projects that have come from campaign asks have zero hosting costs. We have taken a 'lowest common denominator' approach to deploying solutions, so that after the campaign is done, we can be as financially sustainable as possible.

Volunteers can choose pay for domain registration, AWS, Advertising, or other costs during development, and if the project is adopted by the campaign, the campaign can assume those costs, but projects should NOT build based on this assumption. This question needs to be answered on a case-by-case basis, and in the event that we do incur some kind of costs related to official campaign activity, those costs will be considered in-kind donations. Right now, projects in development (not in production, not officially adopted) are not considered in-kind contributions to the campaign. Again case-by-case basis. We really really really prefer static pages and client side development because: It is often more secure, it is harder to take down with a DDoS, it is often less complex, it is super easy to deploy (github pages, Amazon s3, other VPS).

However, if a dynamic application is absolutely necessary, we do have a DevProgress Heroku account that can be used, ping @bradyk or @decause for more information.