... | ... | @@ -100,4 +100,75 @@ Results from the Planning For Real exercise, specifically medium and long term a |
|
|
* 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 |
|
|
\ No newline at end of file |
|
|
### 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 https://lab.civicrm.org/dev/core/issues/300?
|
|
|
* 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
|
|
|
|
|
|
|
|
|
|