|
|
Results from the Planning For Real exercise, specifically medium and long term action items grouped by theme.
|
|
|
|
|
|
# Short Term Action Items
|
|
|
|
|
|
The following are short term action items identified at the community summit. Where possible, we link to issues that were created as a result. These are broken into groups.
|
|
|
|
|
|
## Development
|
|
|
|
|
|
- [Developer Training Docs Book](https://lab.civicrm.org/documentation/docs-publisher/issues/91)
|
|
|
- [Improve documentation of APIs](https://lab.civicrm.org/documentation/docs-publisher/issues/92)
|
|
|
- [Make developer docs more accessible to new Civi devs.](https://lab.civicrm.org/documentation/docs-publisher/issues/93)
|
|
|
- [Refocus resources away from maintaining “toxic” or “broken” code towards replacing them.](https://lab.civicrm.org/dev/user-interface/issues/5)
|
|
|
- How to contribute guide in docs.
|
|
|
|
|
|
## Community
|
|
|
|
|
|
- Identify missing features; document what process should be followed (@jaapjansma)
|
|
|
- Better onboarding and providing mentorship for newbies
|
|
|
- Better talent acquisition for development
|
|
|
- Reduce dependencies of single point of failures (aka Grow the core team, clone Eileen, and so on)
|
|
|
- Extend Civi comunity into new countries < same as > Targeted funding for languages / translations that are underserved (only figure out where in the documentation is written “How can I get involved?”)
|
|
|
- Do a personal survey with the newbies to find out what they missed and what they would desire!
|
|
|
- [Open an issue on Gitlab that explains our desire to get better at recruiting new talent (devs or others) and asks our community ideas on this topic.](https://lab.civicrm.org/community/community-engagement/issues/13)
|
|
|
- Check if the docs for onboarding reflect correctly how to figure out if what you are planning to do is already been done (links to extension list, git lab, and so on)
|
|
|
- [Make a how to for GSOC, what is there to do, what is the normal process for this](https://lab.civicrm.org/community/gsoc/issues/7)
|
|
|
- [Define better what a working group is, how is it organised, what is it for; what will be the outcome (“helping people to get involved”) → make a one pager on the website to explain better what there already is](https://lab.civicrm.org/marketing/civicrm-website/issues/155)
|
|
|
- Draft for conflict solving process
|
|
|
- Have better structures for conflict solving
|
|
|
- How do we handle toxic behaviour in the community
|
|
|
- Stop relighting the same conversations
|
|
|
- We need a mechanism for community conflict resolution
|
|
|
- Process for productive disagreement
|
|
|
- let bygones be bygones
|
|
|
- Improve the CiviCRM resilience if the effects (shit) of bad decisions are hitting the fan
|
|
|
- Ratings for service providers
|
|
|
- Partners can put testimonials on their company pages
|
|
|
- Reinstate the Extension reviewing process and try to make it community driven (together with a handover process); connect it with core fundings somehow (means that the reviewer gets paid with core money) (Olly Gibson)
|
|
|
- Community framework. Marketing calls, partner calls, intro webinars - what volunteer tasks take place. How can we make these ‘temporary duties’. Like 6 months leading calls only (josh olly)
|
|
|
|
|
|
## Extensions
|
|
|
|
|
|
- Mosaico-templates display in alphabetical order (matt wire)
|
|
|
- Approve Shoreditch (eileen)
|
|
|
- CiviMobile Drupal8 compatibility (sergiy)
|
|
|
- Encourage (force) the community to put more unit tests (sergiy)
|
|
|
- Dependencies for extensions
|
|
|
- New extension manager (as extension) (luciano, bjorn, mikey)
|
|
|
- CiviMobileAPI extension review (tim)
|
|
|
- Site breaks on missing extension (https://github.com/totten/afform/pull/29) (eileen)
|
|
|
- CiviDiscount: Needs ability to search for code usage via normal search interface (this doesn’t exist currently)
|
|
|
|
|
|
## Marketing
|
|
|
|
|
|
- [Website: SEO, Identify search words, Implement](https://lab.civicrm.org/marketing/civicrm-website/issues/132)
|
|
|
- [Website: Translation](https://lab.civicrm.org/marketing/local-sites/issues/5)
|
|
|
- Website: Article about Privacy/Security/Autonomy.
|
|
|
Headline: “Get the powerful open source” -> add “privacy”
|
|
|
“Nationbuilder and Salesforce should not be an option!” Surveillance capitalism, don’t sell your constituents data. (detlev)
|
|
|
- Compile list of strengths within the website and the marketing materials (usha)
|
|
|
- Create marketing plan, which actions and resources will we need
|
|
|
- [Spark Promotion: Menu on civicrm.org “Start now” with link to spark](https://lab.civicrm.org/marketing/spark-promotion/issues)
|
|
|
- Connect to “Association for Progressive Communication” (APC, South Africa) and inform their members about CiviCRM (jamie mcclelland)
|
|
|
- [Simple marketing materials: “elevator pitch”, “standard presentation.ppt”](https://lab.civicrm.org/marketing/marketing-assets)
|
|
|
- [Marketing material: pdf’s for Stickers etc. (with new Logo)](https://lab.civicrm.org/marketing/marketing-assets)
|
|
|
- Website: create landing page for specific reach (julie)
|
|
|
- CiviCRM News Dashboard: Different for users vs. developers. Prepare a standard “community dashboard” (Josh)
|
|
|
|
|
|
|
|
|
-----
|
|
|
|
|
|
# Development
|
|
|
|
|
|
### Medium Term Action Items
|
... | ... | |