- How do we securely integrate this into internal systems here at the Church that are currently under development without exposing sensitive and critical data to the community. If we provide API's or other Web services to integrate into these systems, do we expose the Church and the privacy of the data to people wanting to use those API's for non-approved purposes?
- How do we maintain quality of the code that is being submitted.
- How do we prevent code from being submitted and accepted that has "back doors" into confidential data.
- How do we best "beta test" such software?
- Should we open this application up to anyone who would like to contribute?
- What roles should the community play? (Development, Documentation, User Interaction, QA, Project Management, others I'm missing). How would we handle these roles. It is easy to say "all of these" but how would we do that? How do we have a community project manage the app, for example?
- What should we be concerned with that I've not mentioned?
- Assign responsibility to priesthood bearers and sisters for particular individuals and families.
- Report on activities (visiting, calling, writing...) by those assigned responsibility to watch over another.
- Make confidential comments visible only to Bishops/Branch Presidents.
- Produce reports including: who is assigned to who, who is not assigned a responsibility to watch over another, who has no one assigned to watch over them, summary of activities by the assigned and by those watched over.
- All this must be available via the web.
Tom