I'll start with a clarifications/answers post.
I would slightly revise this to a goal of "minimal" documentation on the website, as @LN points out there should be basic descriptions (which some might argue is documentation). My understanding of the trajectory we have been moving towards is the majority of documentation in Sphinx. My thought is the website should act as landing page with brief descriptions and direct you to the forum, the documentation site you need, etc.
As @Jeff_Beorse said the ODK2 documentation has already been ported to Sphinx (see PR #480).
Splitting the documentation into different URLs is the same issues discussed here:
Based on the thought to have separate URLS for separate audiences I think it makes sense to have 4 URLs for documentation (developer vs user, ODK1 vs ODK2) with the updated website acting as the main landing page.
AND
Donations through the web have not been a significant source of funding. Historically it has not been enough to covered our hosting costs. There were more donations when ODK first started; however, it has fallen to like $75 a year last time I inquired.
As I recall, the last time the PMC discussed the donation issue we decided not to prioritize trying to find a non-profit replacement vehicle as the amounts were small. Once the final decision is made about the final organizational form of ODK by the transition board (whole concept note discussion, etc) it would probably become clear how best to setup a new donation system and whether that system could still be tax deductible. The one nice thing about UW handing the donations is that they handle everything including IRS reporting and then put the money into an account (as @downey notes does have certain governmental restrictions).
I do not think there is an official guide written up, might be a good thing to do. Here is a brief list or terms that we started trying to use to avoid confusion.
- Tool - This refers to a packaged piece of software that person will use to perform a task. Tools can be mobile, PC, or cloud based. Examples include Collect, Briefcase, Aggregate, Services, Suitcase.
- Tool Suite - A set of compatible tools that can be used interchangeably. For example both Build and XLSForm perform similar functions and are both part of the same Tool Suite. Examples of separate tools suites: ODK 1 vs ODK 2.
- Application - The special use or purpose to which ODK is being used. Basically, The usage of software tool(s) to solve a problem. For example ODK can be used as Polio data collection application or a Malaria data collection application.
- App - An Android native executable application (software that runs on Android). Examples: Collect, Survey, Tables