| A | B | C | |
|---|---|---|---|
1 | tfor | Face to face is much easier than forum posts | n |
2 | Training | People have different learning styles | n |
3 | user know how exchange | A map of places of users and developers so people can connect locally for meet-ups (community registry to search for your buddy) | n |
4 | Screencasts | Active management of Screencasts | n |
5 | Infrastructure | Are there better integrated tools or app for bug tracking discussions, docs, wiki, etc to find better answers. | n |
6 | New Contributers | As a newcomer, how do I get connected to the CiviCRM community | n |
7 | New Contributers | Barriers to entry—upgrade complexity | n |
8 | Hosting | Better hosting community to keep folks from making mistakes that can be avoided including best practices | n |
9 | Support Communication | Better promotion of 3rd party extensions | n |
10 | Infrastructure | Bugtracker needs more user friendly terms for easier searches especially for newbies and users | n |
11 | user know how exchange | Build a community of non0profits and developers in Mexico and other countries in Latin America | n |
12 | New Contributers | Can the project be less demanding (expectant) of contributors | n |
13 | Reports | Can we add more fields to the default reports? | n |
14 | MIH | Can we crowd-source MIH seeds? | n |
15 | Extensions | Can we give the Extensions page on CiviCRM.org some love? | n |
16 | user know how exchange | Cici should trim core and split out add on features | n |
17 | Forums Q&A | Civi is getting very complex—need easy way to find specialists in forums | n |
18 | Documentation | CiviCRM community and language is still really technical | n |
19 | Support Communication | CiviCRM deserves more outreach | n |
20 | Support Communication | CiviCRM expert exchange | n |
21 | Documentation | Clear explanations of the limits of CiviCRM | n |
22 | user know how exchange | Define different special interest groups that can connect with each other in different ways | n |
23 | user know how exchange | Define less technical methods of contributing for users and publicize those methods | n |
24 | Extensions | Develop and organize/share extension and non-core “hacks” | n |
25 | user know how exchange | Direct community users to civi comm, bridge the gap between users and developers | n |
26 | Extensibility | Extensions list or site - paragraph / hosting extensions | n |
27 | Forums Q&A | FAQ's needed | n |
28 | Forums Q&A | Find a better entry point for non-technical users to participate in the community and support—forums and IRC are intimidating | n |
29 | Forums Q&A | Forum search is hard and confusing | n |
30 | Forums Q&A | Forums need a “technical comfort-level meter” to filter searches and remind responders of language to use | n |
31 | IRC | Have a “welcome crew” on IRC | n |
32 | Make it Happen | Help tech people (non-programmers) bridge gap from non-profit staff and hard-core programmers. | n |
33 | Paid Support | Helpful to have someone knowledgeable connecting organization staff and consultants | n |
34 | Support Communication | How can CiviCRM become more accessible to NPOs with lowest budgets/lowest tech capacity? | n |
35 | Sprints and meetups | How can we conferences more locally? Or Groups? | n |
36 | Support Communication | How can we create and publicize (or virtualize!) CiviCRM trainings in the US South? | n |
37 | Paid Support | How can we get more orgs to give back? | n |
38 | user know how exchange | How can we use bar coding | n |
39 | WordPress | How do I connect with WordPress Civi users? | n |
40 | MIH | How do non-code contributions get lovingly recognized? | n |
41 | Hosting | How to get feedbackon hosoting solutions work best for the community | n |
42 | user know how exchange | I want to know more about fundraising, using forms, integrating with website | n |
43 | Appreciate ptp Nd palante tech | I'd like to know more about powerbase | n |
44 | New Contributers | If you're 80% there—share | n |
45 | Documentation | Improve wiki for better documentation sharing so it is esy to use and find information | n |
46 | Support Communication | Involve more people in training/tracking support requests to make the process more responsive | n |
47 | user know how exchange | It can be frustrating how things are fragmented: IrG, book, forums, but trackers and wiki | n |
48 | Support Communication | It can be hard to navigate/understand the issue queue | n |
49 | Paid Support | It can hard to find a consultant—matching up orgs with consultants around what resources the org has/what cons. Can provide | n |
50 | Extensions | It would be helpful to have a better central directory of extensions, modules, etc. | n |
51 | Documentation | Literature to helps to get by; not techie | n |
52 | Reports | Make downloading and trying new reports easier. | n |
53 | Reports | Making custom reports should be fun | n |
54 | Extensibility | More and better ways to connect support providers with end-user looking for support | n |
55 | Support Communication | More and better ways to connect users with other users for peer-support | n |
56 | Documentation | More case studies from smaller implementations | n |
57 | user know how exchange | More CIVI troubleshooters to stop people from making costly mistakes | n |
58 | UI | More design functionality ie. Ability to change apperance via UI | n |
59 | Documentation | More documentation and demos on new features so we know how to use them | n |
60 | Paid Support | More end-user administratability | n |
61 | user know how exchange | More love for reporting bugs without providing a fix | n |
62 | Documentation | More organized documentation | n |
63 | New Contributers | More resources for new developers (video tutorials) | n |
64 | CiviCase | More tight implementation; how to use relationally with API; cleaner interface | n |
65 | user know how exchange | Need better docs with changes for each version | n |
66 | New Contributers | Need lower barriers to entry—installation profiles | n |
67 | Forums Q&A | Need more forum mentors/responders | n |
68 | Paid Support | Need simplified match-up between organizations that need more and who can provide it | n |
69 | Sprints and meetups | Need to go to Argentina and Chili to learn the implementation of Civi | n |
70 | user know how exchange | Newsletter or e-mail: Best of week, topic, etc. | n |
71 | Forums Q&A | Not everyone comfortable with forums | n |
72 | Infrastructure | Once connect to community great discussion on boards, bug report, and irc but no integration of them all - unified communications | n |
73 | user know how exchange | online virtual meetups so people in remote communities can benefit from common knowledge | n |
74 | Support Communication | Options for context specific support in the UI—deeper support | n |
75 | Paid Support | Paid feature request board (bounty board) | n |
76 | Hosting | Standardized hosting community | n |
77 | Make it Happen | There are users out there that want to help out with testing. How to connect them with developers? | n |
78 | UI | There is nothing obvious about CiviCRM—it can be developer driven and developers don't always pay attention to UI | n |
79 | Foundation | Time for an independent CiviCRM Foundation? | n |
80 | MIH | Two words: smart tags | n |
81 | Extensibility | Unified place to post new code, extensions, customizations so they are easy to find. | n |
82 | Hosting | Use civiCRM.org to host static info like hosting companies instead of wiki | n |
83 | Forums Q&A | Use webinar tools to bridge gap between forums and face to face | n |
84 | user know how exchange | User group directory | n |
85 | Sprints and meetups | Video recording of meetups | n |
86 | IRC | What are best practices for donation processing and supporter relations? | n |
87 | user know how exchange | What are resources and features of community? How do I connect? | n |
88 | Lobo & Core Devs | What can we do to increase communications between developers, users and newbies | n |
89 | IRC | What is an IRC? Everyone says its great (give users and intro) | n |
90 | WordPress | WordPress support dilutes focus. | n |
91 | WordPress | WordPress users will demand features and they contribute little. | n |
92 | API | Would like teams to take more control of parts (ie. API Team) | n |
93 | Marketing | Advocacy support will help grow community! | n |
94 | forums | allow people to vote up answers on the support forums | n |
95 | Marketing | Are there any “How to do X” in CiviCRM? | n |
96 | Marketing | Barrier to entry – not knowing the limits vs capabilities (i.e. assessment) | n |
97 | forums | being aware of forum questions going unanswered | n |
98 | community | better awareness and marketing for the community aspect | n |
99 | Social Media | Better integration with social media for digital activism | n |
100 | consulting | better knowledge base vs. influence | n |