Notes-from-2019-Summit.md

@@ -111,7 +111,76 @@ Individual group principles:
 - CiviCRM community is focused on doing good.
 - Principles should instill security.
 
+#### White Team
 
+- Open source should be a principle.
+- We are producing software that enables organisations. (Versus “not a product” responses in “What is CiviCRM Not” questions earlier.
+- “Expect” is not the right word to get people involved in the community.
+- Don’t care about org structure / legal entity of orgs, remove “non-profit” from final point.
+- Question democracy as a core principle & background / reasons for including that point. 
+- Add do-ocracy as a principle, permit meritocratic / technocratic decisions. Not just voting.
+
+Erik wrapped up the exercise and, after lunch, presented a summary of “Reinventing Organizations”, a book dedicated to introducing new ways to operate and collaborate within a company and/or community.
+
+### Core Team Report
+
+Josh presented the financial status of the Core Team as can be seen on http://stats.civicrm.org/?tab=financials. Bottom line is that the Core Team financials are OK and as long as everyone is happy with the way things are running we are fine. But if significant changes are required they will have financial consequences. The Core Team is now on full pay again.
+
+### Establishment Committee Report
+
+Alice and Erik provided an update and led a discussion on the work, challenges and results of the establishment committee. The purpose of this session was not to report on the specific details of the document, but rather to talk about the process and the expectations going forward. Points include:
+
+- There’s a feeling that the summit in New Jersey wasn’t representative of the community and that its mandate was very challenging to achieve, especially within a 6 week time frame. In general, the term ‘governance’ has lost some of its meaning and, in Alice Aguilar’s words, is not the right word to use to reflect the work of the establishment committee or that of the recommended elected body.
+- There was no universal agreement on the committee on all points, however the debate and discussions were good. The committee wanted to put something out there, even though they didn’t come to a lot of agreements.
+- The committee focused heavily on what it perceived as CiviCRM’s guiding principles, and ultimately arrived at having home sort of elected body that adequately represents the community. What it specifically does remained up for debate, however there was a shift away from thinking of it as a “governing body”.
+
+Guy Iaccarino provided a recent history of CiviCRM, his efforts around promoting governance as well as why the governance summit came about. His main point about the objective of the summit was asked as “how do we get more people to the table to do more of the work in order to grow and have more impact?”
+
+One result of the establishment committee’s work is this summit, i.e. we needed to revisit ‘who we are’ and ‘who we want to be’ prior to implementing a ‘governance’ structure. Joe spoke about some of the community conflict around core team decision making and influencing project-wide decisions.
+
+Jamie McClelland highlighted how tensions in the community go up and down based on the health of the project, not because the tensions are resolved. Since the summit in 2018, tensions have gone down but, by and large, the health of the project has continued to improve.
+
+There was a lot of discussion on what the role of the elected body. As a community, we’d like an elected body to work with the community to determine how to grow our impact without compromising our culture of do-acracy. Attendees repeated several times that a primary role of the body is conflict management. In addition to helping coordinate and communicate the community’s priorities and needs, and the body should be tasked with managing the community’s responses/reactions (toxicity). 
+
+A final discussion point revolved around why the body needed to be elected. Mikey O’Toole spoke about the success of the documentation effort and how its continued to move forward without governance and guidance. “It’s a matter of allowing people to do what they are passionate about.” 
+
+In lieu of an elected body, should there be a community consultation working group? Does it need to be elected? Points favoring an elected body include:
+
+- The idea of elections is to help foster accountability. 
+- The role of the elected committee is not to control or manage the core team.
+- Elections are a way to invest power into people that may not otherwise naturally assume power. 
+- Elections provide legitimacy in the eyes of the community.
+
+### Planning For Real
+
+Olly Gibson led a process called “Planning for Real”, the intended result of which is to develop short term actions that we can do today (or over the very short term), medium term actions that we can document for future sprints, initiatives, etc., and long term objectives that help guide us. 
+
+The process started with documenting items that individuals felt would “make CiviCRM better” on to post it notes, and then grouping them based on themes. Individuals then volunteered to work on each theme and to prioritize the various items therein. 
+
+Short term action items are [documented here](https://docs.google.com/document/d/1nuAoebe8YlvKt1U-LX8_O0geAW1noXTlfJYqa2xXmig/edit) and have been added as tasks in Gitlab. Medium and longer term items [are listed here](https://lab.civicrm.org/marketing/events/community-summit-2019/wikis/Planning-For-Real).
+
+## Day 2
+
+### Planning For Real
+
+1. Discussing the grouping of the issues in Dev Process, Community, Extensions, Marketing + Communications, Core Development, User Interface + Experience, Architecture.
+2. Each team of 6 coming up with solutions for the post-its  in 60 minutes. Solutions should be practical, detailed and and split in short-term, medium-term and long-term. Groups can note that they think a post-it is not feasible, then document why and put it to the side.
+3. Hopefully we can do all the short-terms during the sprint, we will discuss what to do with medium and long turn
+
+Discussion in groups took place.
+
+In document:
+
+- Names, emails, @handles below section
+- Continue discussion & write up as needed
+
+Next steps:
+
+- At start of sprint we review short term actions & allocate if appropriate
+- A sprint task is to review medium & long term tasks
+- Will look at turning this into a roadmap
+
+In between: Michael McAndrew talks about sprint planning. Joe Murray suggests on first morning if people have clear ideas of what they want to work on they present so others can potentially join. Throughout the sprint there will be lightning talks and workshops/presentations. We will be balancing between getting things done and sharing knowledge/workshops/learning how to do stuff. Jaap suggest there is a group for newbies to have a somewhat longer workshop on development, training etc.