Skip to content
Snippets Groups Projects

Planning For Real

Last edited by MikeyMJCO

Results from the Planning For Real exercise, specifically medium and long term action items grouped by theme. Original notes can be found here

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

Community

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
  • 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

Core Development

UI & UX

Architecture

  • Kill the site key (we just need an API key)
  • Create documentation and a composer install as an example template pre configured for orgs that refunds and credit notices
  • Tag all code where BAO stuff is in the form and visa versa (in prep for a step 2 where it is actually moved
  • Define ideas for a conversational interfaces
  • Set up a large install demo to explore performance issues

Development

Medium Term Action Items

  • Documentation requirements on Core PRs
  • Improve the usability of developer docs for newer developers / reduce assumed knowledge
  • Move remaining wiki related documentation content.
  • Improve PR processes - how long is too long for a stalled PR? When should stale PRs be changed back to issues.
  • Improve developer onboarding experience.
  • Developer training program/guide with crowd-sources localized translations.
  • Increase PR reviewer pool - consider Drupal style PR review trading requirements?
  • Upskill community in Angular JS?
  • Improve transparency in our collaborative approach to development and how coding standards are determined/set.

Long Term Action Items

  • Project Roadmap
  • Work on how to redirecting funding from deprecated areas to newer / sustainable functionality
  • Comprehensive new contributor process development/community consultation.
  • Broad roadmap for CT’s intended direction - community roadmap.
  • Improve Civi DX ['developer experience'?].
  • Less “shop” repos - more composer driven Civi as standard.

Community

Medium Term Action Items

  • More Local + regional Meetups
    • As much real life contact as possible
    • Do more Toronto Civi Meetups
  • Create a workgroup how we can be “explicit that we are open for all people which are momentarily underrepresented in the community”

Long Term Action Items

  • Develop an asset succession plan (how are the CiviCRM rights are going to be preserved for the project for the time after the actual holders) → not to take now
  • We can do better in creating inclusive ways to share. Discuss future vision/ roadmap for the project
  • Create a clear and understandable process framework for decision making and write it down and agree all on it!
  • Not clear tasks (we need to talk more about it):
    • Support forums in non - English
    • Support forums
    • Better tools for community support, SE is not good for discussions
    • More funding for Core Team
    • Global Core team in all global region
    • Kill ESR (what is your problem here?)
    • Less drive for central coordination
    • Mature partner programme (QA, reciprocal values)
    • Free tier CiviCRM horsting (like Mailchimp)
    • Forum for established partners to community members; talk about challenges
  • Potential for conflict
    • Ratings for service providers

Extensions

Medium Term Action Items

  • STRIPE ACH Payments [request]
  • Social Media Integration [request]
  • Aggregation in API4 (SUM/AVG/etc.) [request]
  • Case in API4 [request]
  • LineItem Editor should go in core. Group recommendation: no, but extension should be shipped with core
  • Cultural extension list
  • Extension owner transfer / maintenance process
  • Extension auto-updates (if enabled / requested)
  • Get more payment processors giving money to core team (negotiation, implementation, stats through pingback)
  • IATS removed from core (not shipped with)
  • Civi not finding extensions when everything is right ???
  • Funding model for extension maintenance (market place, pay for extension, provide funding for dev + core team approval)
  • Users should be able to subscribe to email updates from extensions, e.g. gives a way to tell people about important updates
  • Extensions should have 5-Star ratings, user comments
  • One maintainer per extensions on extensions page
  • Allow release note feed
  • Extensions should be better documented
  • More extensions in CI testing
  • Better extension screen (filters + good looks)
  • Review process should consider documentation as well
  • CiviTutorial shipped with core
  • Documentation of CiviAccounts data flow
  • In-App notices for extensions

Long Term Action Items

  • Views for Wordpress [request][Hint: look at the plugin “Content Views CiviCRM”]
  • Payment processors for underserved countries [request]
  • Move CiviCase into an extension
  • Living extension ecosystem
  • Make extension income available to developers
  • Living extension ecosystem

Marketing & Communications

Medium Term Action Items

  • Challenge our vision: e.g. “All organisations in the world are using CiviCRM” (hehe, but some truth in it), (our mission is already accomplished)
  • Outreach for “new markets” (e.g. Africa, South Americas, …)
  • Create high level promotional videos
  • Support material for onboarding process of new community members
  • Ask partners to ask their clients for reviewing website civicrm.org -> areas for improvement
  • Ask partners to reach out for their clients in order to get reviews on sites like capterra
  • Develop sample strategy for local market growth

Long Term Action Items

Core Development

Medium Term Action Items

  • Improve cultural localization options for names, e.g. middle names
  • Users should always receive transactional messages in their preferred language
  • Each civi admin page to have an individual class
  • → is this solved by dev/core#300 (closed)?
  • Review the way UK counties are handled in Civi.
  • Permissions in Groups, i.e. “Event organizers”/”Member organizers”
  • → needs more spec. Is it covered by existing hooks (so implementable as an extension?)
  • Make Mailing Reports use graphs for things like clicks
  • → maybe an extension?
  • Make installation process easier
  • Make writing payment processor easier and better

Long Term Action Items

  • OpenAPI 3.0
  • Have a more global/flexible financial/accounting support
  • → extension?
  • In-App Bug-Reporting / (Feature) Requests
  • → needs more spec
  • Functional Stability
  • → not actionable
  • Developer friendly SAAS (Spark 2.0)
  • → needs more details
  • Issues with direct debit payment processor: pending memberships
  • → needs clarification. Isn’t this about an ext?
  • How to manage documents? In Civi or in Drupal or both?
  • → needs clarification

User Interface & User Experience

Medium Term Action Items

  • Address issues around unsubscribe/opt-out process (see above)
  • Deliver inline tutorial (ie link from events page creation to events docs, related video tutorial)
  • Improve membership, contribution and main page dashboard & workflows (ie charting, graphing)
  • Chart / graph civiemail stats & graphs (check with reporting group) - get up to spec of MailChimp reporting
  • To match the normal extension install & update experience for each CMS (typically one click install/update)
  • UI flow of creating reports
  • Improve the tag management system as it’s clunky:

Long Term Action Items

  • Salesforce theme?
  • Decouple theme templates from specific CSS/JS frameworks to allow for alternative CSS/JS frameworks to be used.
  • Improve mapping of fields during import (e.g. preset mappings from NationBuilder/Salesforce/etc)

Architecture

Medium Term Action Items

  • Have a clear process for identifying libraries that should be deprecated and ideas for how they should be replaced. This includes extensively used libraries like Quickform, DB, and smarty
  • Configure permissions from within CiviCRM / Bring back standalone CiviCRM
  • Create CiviNative CMS independent alternative to Caldera and Webform
  • Create CMS independent alternative to views
  • Create a Drupal 8 installer for non technical users
  • Create infarstructure that allows us to create things like a stripe donation form within CiviCRM.

Long Term Action Items

  • Unit test everything
  • “Get rid of quickform” ← but replace it with what?
  • “Lean core”
  • Take CiviGrant out of core to make core leaner. ← Joe tried it and thought it wasn’t worth it but thought is this where I want to spend a couple of pro-bono. If we want to do it, we might need to pay someone to

Comments

    Please register or sign in to add a comment.