E-mail
After a bunch of discussion, we have worked out a model of support commitment between the core team and the accounting integration team that can be used on this project and other Make It Happen initiatives being implemented by teams other than the core team:
- The Accounting Integration team will take responsibility for producing documentation on the wiki and elsewhere to help users through the change. This will include ERDs, API enhancements if any, sample documentation for changing a custom report, and likely a screen cast or two. Documentation will be updated to reflect bug fixes.
- Once an issue is filed Joe will propose a technical solution, it'll be reviewed by the rest of the Accounting Integration team including Dave G, and once approved, Web Access will implement the fix, and Joe will test it. Likely Dave or someone else on the core team will also review Accounting Integration patches / commits. The Accounting team excluding Web Access and the core team commit to providing this for 6 months minimum after the stable release of the data schema.
- The Accounting Integration team will monitor and respond on the forums if the amount of traffic / bugs / posts is fairly high. We expect this will likely require 2 - 3 hours per day in the forum for the heaviest week or two right after release. As things settle we will handle it via a single nightly review of all posts in the forum. The Accounting Integration team will take responsibility to work with users in an Accounting Integration forum to produce JIRA issues for confirmed bugs. When the forum is no longer regularly producing real new bug reports (probably between 6 or 8 weeks after release), the Accounting Integration team will no longer be expected to actively monitor the forum. From then until 6 months after the stable release, the Accounting Integration team will respond to posts brought to their attention as being reasonable prospects for bugs, and will go through the issue and fix process detailed above.
- The team will need to help ensure and fix the tests during the 4.1.x release cycles and ensure it has a high success rate. Ideally we'd want more tests to be added when bugs are found.
- The IRC channel will be used to facilitate communication and problem solving when communicating via the forum becomes cumbersome. Accounting Integration team members may monitor IRC in order to alleviate the work that would normally occur through the Forum. In addition to the formal commitments above focused on identifying and fixing bugs, we expect that the community including us as members will continue to assist users of all abilities in the forums and on IRC to make good use of CiviCRM and all of its abilities.
- We're expecting that different individuals will be responsible for the forum on different days of the week during the initial period, and possibly by month or week later on. Suffice it to say that we are taking on the responsibilities identified above, and do not expect either Web Access or the core team to be responsible for this. (Of course, we'd love your help especially if there are issues that may not be related to Accounting Integration that we're trying to figure out.)
Labels:
