Commit 358bf8a1 authored by eileen's avatar eileen 🎱
Browse files

formatting fixes

parent 069c863b
What is product maintenance?
**What is product maintenance?**
The ultimate goal is to ship a product that is free of bugs and regressions while ensuring code maintainability is improving and supporting the efforts of contributors to improve the product.
......@@ -15,13 +15,12 @@ In very practical terms that means keeping the first 3 columns on this board emp
There are a bunch of other tasks that are done by the same people outside of this definition of product-maintenance. For example a fundamental function of the core team is to maintain all the infrastructure for the release process, for testing and for CiviCRM in general. This is absolutely necessary for product maintenance but I'm not including that in this definition. I'm also leaving security work under the security team hat and the significant core time that goes into improving compatibility (drupal 8, Wordpress enhancements, accessibility) to live under some under category.
Who is the product maintenance group?
**Who is the product maintenance group?**
It is an informal voluntary group organised through the product-maintenance channel on chat, which basically consists of the core team, a group of key people (Jitendra (Fuzion) , Monish (JMA), Seamus and myself) who put in regular substantive time to this work, outside of any customer work or 'scratching their own itch work' and a number of people who do the same on a more ad hoc basis (there are too many to fairly mention but I usually make a point of a call out to someone who has been notably recently contributing & Michael McAndrew stands out right now.)
A few years back CiviCRM partners were presented with a decision to find a way to fund a full core team or accept it being cut back to a skeleton team and to step up to make this work. Partners were generally clear they preferred to give time than money and we wound up attempting the latter. We found ourselves in a situation where partners & community members were submitting bug fixes that were not getting reviewed due to lack of reviewer resource, long-standing data integrity bugs were being left open while people fixed some very niche bugs, reviewer time was being squandered on issues that were really not review-ready, or where the submitter was not responding to reviewer input, and we didn't have a way to prioritise the time people were prepared to put into product maintenance.
......@@ -30,7 +29,7 @@ A few years back CiviCRM partners were presented with a decision to find a way t
It was also apparent that there were some people who were collaborating very well on addressing bugs, code quality and testing issues and reviewing and the best return on effort was to try to improve co-ordination of these people before trying to cast the net wider. I proposed some initial goals which were basically 'get critical issues down to 0 and keep them there', 'get open PRs under 155', 'get to the point where we have no PRs more than one year old' and 'figure out how to get on top of regressions'.
I feel like we have achieved out initial goals.
......@@ -38,7 +37,7 @@ We got bugs identified as critical down to zero and kept them there, even after
We have got PRs down substantially.
We are now aggressively triaging to find regressions, analysing them and putting out fixes in patch releases.
Where next?
**Where next?**
I think the goals are basically to keep the first 3 columns here empty and focus on getting the PRs down and I have quite a lot of thoughts on the latter.
......@@ -59,7 +58,7 @@ On the other hand there is a real cost to having non-reviewable inactive PRs in
Some more detailed thoughts on the review queue are over here
What do I do if I want to help?
**What do I do if I want to help?**
Jump on the product maintenance channel on chat - our main to-do lists are the first 3 columns of
......@@ -70,7 +69,7 @@ and
So, does this mean you will fix any regressions I hit or bugs I see as critical?
**So, does this mean you will fix any regressions I hit or bugs I see as critical?**
Erm maybe. The product maintenance group (like all volunteer workers) works on what I call an 'exploitation contract'. They agree to work for free & be exploited within limits that they probably can't and won't clearly articulate but which they will quickly identify a breach of. So we need to be very mindful of respecting volunteer time. Hence....
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment