Community Engagement issueshttps://lab.civicrm.org/community/community-engagement/-/issues2021-04-03T09:57:08Zhttps://lab.civicrm.org/community/community-engagement/-/issues/18Consider Loomio for certain community decisions/discussions?2021-04-03T09:57:08ZnicolConsider Loomio for certain community decisions/discussions?Unlike other web voting systems which try to settle decisions only via a total number of votes, Loomio was born out of the consensus-decision-making systems used by its developer, New Zealand's [Enspiral](https://enspiral.com/). In conse...Unlike other web voting systems which try to settle decisions only via a total number of votes, Loomio was born out of the consensus-decision-making systems used by its developer, New Zealand's [Enspiral](https://enspiral.com/). In consensus-led decision-making, the goal is to get as many people on board with a decision as possible (the details vary - in some instances, everyone must agree, in others, it needs to be a high percentage, in others just a majority, but with no blocks). As a result, as a voting system, it introduces a few key ideas with which you can structure polls: you can abstain, you can change your vote, seek clarification, and offer the ability to 'block' - and discussion is threaded throughout the voting process.
Anyway, I noticed that Version 2.0 has [just come out](https://blog.loomio.org/2019/09/18/what-is-new-in-loomio-2.0-and-beta-release/?utm_campaign=whats-new-2.0-social&utm_term=social) and thought, given the wider question of bringing more community participation into CiviCRM decision-making, as well as the question of how people who can't/won't/shouldn't fly around the world to summits can ensure their voice is heard, is it something we should be exploring for CiviCRM's bigger questions? (such as CIVICRM vs civicrm vs Civicrm vs CiviCRM :)
It's FLOSS, and while there isn't LDAP yet so it could integrate seamlessly with Gitlab and Matter, there does seem to be [a fair amount of demand](https://www.loomio.org/d/AF8Xb0c6/ldap-authentication-way-past-due) for that. Also, FWIW and IMHO, a Loomio/CiviCRM bridge would be pretty app[ealing for any membership organisation trying to increase governance/participation.
![image](/uploads/55fa50bc51d1107d960faefed13c3064/image.png)
Version 2 also lets you schedule meeting/call times:
![image](/uploads/03fc2ec43ee1a26d64b588989d9e7066/image.png)https://lab.civicrm.org/community/community-engagement/-/issues/13How to attract / acquire new talent2019-11-27T16:59:48ZErikHommelHow to attract / acquire new talentOne of the point coming out of the Barcelona Community Summit 2019 was the need to attract new talent. This could be specifically developers but also broader: how do we maximize the change that people thinking about career moves or at th...One of the point coming out of the Barcelona Community Summit 2019 was the need to attract new talent. This could be specifically developers but also broader: how do we maximize the change that people thinking about career moves or at the beginning of their career become aware of CiviCRM as an option.
From the past and from our technical background the "easy" answer is to target the Drupal/Joomla/Wordpress/Backdrop developers. That makes sense as they are already aware of our CMS. The downside is that we uphold our own limits? And also it is my personal belief that a CMS is a totally different kind of animal from a CRM.
In our (Björn Endres from Systopia and me) search to do some marketing initiative in the Scandinavian marketplace we had a discussion with a marketing professional who gave the feedback that we should not look for CMS developers but developers that want to do social good and have an impact on the world as to him that was much more defining in our stories.
Anyway, this issue is really about collecting the ideas in the community on how to attract new talent, share experiences and see if there are chances of doing things together. Feedback highly appreciated!!https://lab.civicrm.org/community/community-engagement/-/issues/25Manchester Sprint Feedback2022-11-28T22:13:58ZMichael McAndrewManchester Sprint FeedbackHello there,
We hope that you enjoyed the sprint in Manchester. If you have any thoughts or ideas on things we could do better and improve for next time, please share them below.
If you have any feedback that you would like to share in...Hello there,
We hope that you enjoyed the sprint in Manchester. If you have any thoughts or ideas on things we could do better and improve for next time, please share them below.
If you have any feedback that you would like to share in private, please email michaelmcandrew@thirdsectordesign.org or olivergibson@northbridgedigital.co.uk.https://lab.civicrm.org/community/community-engagement/-/issues/262023 Manchester Admin training2023-11-07T17:55:58Zaydunsaidan.saunders@squiffle.uk2023 Manchester Admin trainingTraining is Wednesday 29th & Thursday 30th November. This gitlab is for planning and preparation around it. [Event Info](https://civicrm.org/civicrm/event/info?id=1710&reset=1) [Booking Page](https://civicrm.org/civicrm/event/register...Training is Wednesday 29th & Thursday 30th November. This gitlab is for planning and preparation around it. [Event Info](https://civicrm.org/civicrm/event/info?id=1710&reset=1) [Booking Page](https://civicrm.org/civicrm/event/register?id=1710&reset=1)
# Trainers
Aidan, Rebecca, Sarah
# Capacity / Signups
As of 2023/11/07 : 6 registered, 2 incomplete. Room capacity is about 14.
# Agenda
Based on https://docs.civicrm.org/training/en/latest/courses/admin-2-day/ Update to include more SearchKit/FormBuilder
# Preparation
Ideally want each participant to have a local install to play with.
See https://docs.civicrm.org/dev/en/latest/tools/buildkit/virtual/
Virtual image needs updating.
# Pre-training survey form
Ask about CiviCRM experience, particular topics of interest, what they hope to get from it.
Form TBD
# Pre-training mail to go with form
- form link
- virtual image info
- get Mattermost loginhttps://lab.civicrm.org/community/community-engagement/-/issues/21Establish quaterly community calls2022-01-18T14:06:25Zjoshjosh@civicrm.orgEstablish quaterly community callsThe Community Council and the Core Team are working together to create quarterly community calls. This issue will be used to define various details associated with the calls, for example:
- dates, timezones
- agenda, format
- advanced c...The Community Council and the Core Team are working together to create quarterly community calls. This issue will be used to define various details associated with the calls, for example:
- dates, timezones
- agenda, format
- advanced communications, results, minutes, etc.
- registration on c.o or other or not at all
- system requirements, recordings
Adding @tricia.gbinigiejoshjosh@civicrm.orgjoshjosh@civicrm.org2021-03-27https://lab.civicrm.org/community/community-engagement/-/issues/20Installer should ask analytics-related questions2020-02-27T01:42:06ZJonGoldInstaller should ask analytics-related questionsIt looks like there's a plan underway to make the 2019 installer the standard installer: See https://lab.civicrm.org/dev/core/issues/1615.
Several years ago, we discussed adding additional installer questions to improve our communicatio...It looks like there's a plan underway to make the 2019 installer the standard installer: See https://lab.civicrm.org/dev/core/issues/1615.
Several years ago, we discussed adding additional installer questions to improve our communications/analytics. If we're rolling out a new installer, let's reopen discussion.
Proposals I recall are checkboxes for the following:
* Allow signing up for CiviCRM newsletter (aka "get added to c.o/civicrm") from the install screen.
* Allow collecting the Default Organization data for similar purposes.
* It's OK to contact the evaluator for assistance with evaluation.
* There was also discussion of a field, hidden from the UI, that indicated that the installer was managed by a partner (and an optional field for the installer's name). This would allow us to a) get a sense of how many sites are being implemented by partners, b) in-app communication could be tailored based on whether a partner is involved.
Some of this got bogged down in, "Oh, it's not fair if one shop hogs all the evaluation calls" - but honestly, 5 years later that feels like the least of our concerns. We should implement whichever of these feels uncontroversial.
I'll also propose:
* Contact me if we have an unpatched security issue.
@joshhttps://lab.civicrm.org/community/community-engagement/-/issues/14Add GL projects to MM channel descriptions2019-10-13T19:26:58Zjoshjosh@civicrm.orgAdd GL projects to MM channel descriptionsWhere possible, cite the appropriate GL project in mattermost channel descriptions.Where possible, cite the appropriate GL project in mattermost channel descriptions.joshjosh@civicrm.orgjoshjosh@civicrm.orghttps://lab.civicrm.org/community/community-engagement/-/issues/2Get Mattermost registrations into civicrm.org Civi2020-05-29T02:21:51ZJonGoldGet Mattermost registrations into civicrm.org Civihttps://lab.civicrm.org/community/community-engagement/-/issues/24Meta - recognizing community engagement2022-10-29T21:00:20ZbgmMeta - recognizing community engagementVery random notes from discussions at the Manchester 2022 sprint, in no particular order. Feel free to add more.
- [ ] infra/gitlab#43 When someone opens an issue on Gitlab for the first time, add a "new-contributor" label (apparently D...Very random notes from discussions at the Manchester 2022 sprint, in no particular order. Feel free to add more.
- [ ] infra/gitlab#43 When someone opens an issue on Gitlab for the first time, add a "new-contributor" label (apparently Drupal are working with Gitlab about this? but it will take a while, and adding a label is simple)
- [ ] infra/gitlab#43 Post "new-contributor" alerts in a mattermost channel, where people interested could follow and help engaging with the request
- [ ] Contributor listing on the website (there is already an issue for this somewhere, we were waiting after SearchKit, but that's now usable for our requirements)
- [ ] (very old problem) people willing to be pinged on certain topics
- Joe uses email filters for subscribing to specific labels?
- Justin mentioned it would be nice to have a ping in new issues, after 2 weeks if no engagement, to try to keep it alive and moving forward (and that ping could ping more people based on tags or keywords)
What we already do (please complete this list):
- Jaap does Gitlab issue triage, and tries to be more attentive to first-time contributors
- Eileen, Seamus and DaveD keep a very close eye on Github pull-requests, and often spend a lot of time helping with the "other 50%" required for a PR to be merged.
- Developer trainings at in-person events
- Monthly release blog posts mention who contributed code and commented on PRs.
- Monthly release blog posts mention new extensions (still a form of recognition)
- Dev-digest will try to bring some attention to specific issues that need wider feedbackhttps://lab.civicrm.org/community/community-engagement/-/issues/232022 Manchester developer training2022-09-30T18:15:42Zeileen2022 Manchester developer trainingManchester training runs from 6-7 Oct & this gitlab is for planning and preparation around it. [The signup form is here](https://civicrm.org/civicrm/event/info?reset=1&id=1674)
# Capacity / signups
As of writing we have
Capacity ?
Cap...Manchester training runs from 6-7 Oct & this gitlab is for planning and preparation around it. [The signup form is here](https://civicrm.org/civicrm/event/info?reset=1&id=1674)
# Capacity / signups
As of writing we have
Capacity ?
Capacity on the event page : 12 (I just increased it to 12 but maybe 14)
Catering ordered for : 10
Trainers: 4 (Matt, Aiden, Tim, Eileen)
Signups: 10
Paid 6
Not yet paid 4
Per the image we can probably increase the number of spaces to 14 fairly comfortably & I propose we do that. We should also determine if all the not-yet-paid are serious (two have been in touch and are known to us - the last two are new to our database and may not be genuine sign-ups). (I just enabled waitlist functionality on it in the course of writing this)
![image](/uploads/1a5ace18cee35aa4947032c965bd4e0e/image.png)
# Preparation
Generally when we run sprints getting a functional development environment running is challenging for some people, although we know that at least three people will already have them. Our goal is that people are prepared for the spring by having either
- a functional local developer environment with CiviCRM & preferably civix and buildkit already installed or
- virtual box installed and we will provide a USB stick with an image on it
Our preference is for the former but in the case of the latter it seems the image/s we bring will depend somewhat on the devices people bring - so we need to gather that information. In order to do that I (Eileen) will send a pre-spring email to attendees.
# Agenda (rough)
### Day one -
**Morning**
Introductions
Key concepts: APIs, Hooks, Extensions, Entities, Pages, Forms [xml, DAO, BAO, Managed Entities, Settings ?], CMS/UF (**Matt**)
Setting up dev-env / Civi / buildkit
**Afternoon**
Admin UI - show how it works with the packaged search, exporting, searches show debug (**Aidan**)
Rest of the day structured around creating `CiviGoat` (or another extension) with basic features - with an entity, Page, settings, search kit,
Civix - create first extension
API - explorer etc
Unit tests
Creating entities / accessing them via search kit/ form builder
Creating settings
Big E / ts()
### Day two
**Morning**
Debugging live sites. ConfigAndLog, Query logging
PR process & giving code back
**Afternoon**
Flexible to adjust to what we did and didn't cover
# Pre-sprint survey form:
https://docs.google.com/forms/d/e/1FAIpQLSf8xoYweZfXW7wM4jSmI9ezbWdKv4_1fr-QfhBKaJwf9IFnqQ/viewform?usp=sf_link
# Pre-sprit email text
Hello,
Thank you for signing up to the [CiviCRM developer training](https://civicrm.org/civicrm/event/info?id=1674&reset=1) - we look forward to seeing you.
The training will start at 9am on October 6th, 2022 and you will need to bring a laptop to work on while there. You will need to have a working development environment, including Civix and preferably Buildkit. If you do not already have one, then we need you to either connect with us on [chat](https://chat.civicrm.org/civicrm/channels/sprint) to get one set up, or install [VirtualBox](https://www.virtualbox.org/) (which will make it easy for us to set up your development environment for you after you arrive).
To help us prepare please fill in [this google form](https://docs.google.com/forms/d/1uNFEJaN5kS6vHd53flvl_Mfz-7JNE4Z_wdgMi4v8tdc/edit) with details about your experience and your development environment.
If you have not paid please do so to secure your place as places are limited.
In open source manner we are tracking our preparations for the training in gitlab - see https://lab.civicrm.org/community/community-engagement/-/issues/23
**Assignments / Action Items:**
Tim: Update VirtualBox. Get USB keys.
Matt: Key concepts plan
Aidan: Admin UI plan
Eileen: Send surveyhttps://lab.civicrm.org/community/community-engagement/-/issues/12Evaluate uservoice.com for a user community2020-06-12T12:28:55ZJoe McLaughlinEvaluate uservoice.com for a user communityI recently started using mattermost.uservoice.com , one of Mattermost's user communities. I like the ability for users to request new features, upvote other feature requests, etc. civicrm.stackexchange.com does not work well enough as a ...I recently started using mattermost.uservoice.com , one of Mattermost's user communities. I like the ability for users to request new features, upvote other feature requests, etc. civicrm.stackexchange.com does not work well enough as a user community - it's great for what it is designed for, a Q and A site.
cc:https://lab.civicrm.org/community/community-engagement/-/issues/11Review and revise CiviCRM Code of Conduct2020-04-28T12:01:05Zjoshjosh@civicrm.orgReview and revise CiviCRM Code of ConductThe [current CiviCRM Code of Conduct](https://civicrm.org/code-of-conduct) was adopted in 2016 and is fairly boiler plate stuff, and is slanted toward conduct at events. We should review it in conjunction with Eileen's #5 and make any ne...The [current CiviCRM Code of Conduct](https://civicrm.org/code-of-conduct) was adopted in 2016 and is fairly boiler plate stuff, and is slanted toward conduct at events. We should review it in conjunction with Eileen's #5 and make any necessary revisions and improvements. Some past discussion can be [found here](https://lab.civicrm.org/marketing/events/community-summit-2019/issues/10).
Working document here: https://docs.google.com/document/d/17Ogt364gj2Kl94wr52gqplnSgDmICD5VSI4OYmrlv9U/edit?usp=sharinghttps://lab.civicrm.org/community/community-engagement/-/issues/10Debian integration2022-06-13T01:10:29ZDmitry SmirnovDebian integrationThis ticket is to log Debian integration effort.This ticket is to log Debian integration effort.Dmitry SmirnovDmitry Smirnovhttps://lab.civicrm.org/community/community-engagement/-/issues/9Gitlab digest2019-08-07T19:01:06ZJonGoldGitlab digestThis issue is to track discussion on a "Gitlab digest". The digest is a regularly-scheduled (weekly?) email that shows all issues on Gitlab that need further discussion before moving forward. This should hopefully fix a bottleneck in t...This issue is to track discussion on a "Gitlab digest". The digest is a regularly-scheduled (weekly?) email that shows all issues on Gitlab that need further discussion before moving forward. This should hopefully fix a bottleneck in the development process, and provide a concrete way for non-developers to engage with the direction of the software development. Nicolas has explored some of what's necessary to automate the creation of this digest.https://lab.civicrm.org/community/community-engagement/-/issues/8Language/topic-specific support2020-05-04T14:27:15ZbgmLanguage/topic-specific supportWe currently have this space for region-specific discussion (mostly meetups):
https://lab.civicrm.org/community/region
I would be tempted to create projects such as:
* ~~Canada (where folks could post in English or French)~~
* France...We currently have this space for region-specific discussion (mostly meetups):
https://lab.civicrm.org/community/region
I would be tempted to create projects such as:
* ~~Canada (where folks could post in English or French)~~
* France or Francophonie
(I want to avoid creating spaces that will struggle to get critical mass, or which will have a fair amount of overlap, ex: Quebec)
edit: based on the discussion, I changed the proposal title from "region/language-specific support" to only "language-specific support".https://lab.civicrm.org/community/community-engagement/-/issues/4Asia/Pacific CiviCRM monthly meet-up2021-09-07T19:37:37Zjustinfreeman (Agileware)Asia/Pacific CiviCRM monthly meet-upThis is an initiative to start a monthly on-line meeting to catch-up and discuss all things CiviCRM with people located in the Asia/Pacific region.
The motivation is that I find it really hard to attend the US timezone meetings and give...This is an initiative to start a monthly on-line meeting to catch-up and discuss all things CiviCRM with people located in the Asia/Pacific region.
The motivation is that I find it really hard to attend the US timezone meetings and given there is a growing number of interested CiviCRM people in our region of the World, why not start our own regular meetups.
This invitation is open to all CiviCRM people in Asia/Pacific, similar timezone to [AEDT]( https://www.timeanddate.com/time/zones/aedt) . This includes end users, Developers / Contributors and Partners.
**Meeting agenda**
We'll try and keep meeting duration to 1 hour so that it doesn't impact too much on your day.
* Introductions and welcome to new people
* Discuss what's going on in the wider CiviCRM community
* Discuss new projects or challenges
* Useful or new CiviCRM extensions
* PRs, bugs etc.
* Volunteer for next meeting chair, someone needs to step up! (Rotating chair).
**Meeting schedule**
Next Meeting schedule: **Thursday, 24th September at 2pm** [AEDT](https://www.timeanddate.com/time/zones/aedt)
Next chair: **Seamus**
We meet on the 4th Thursday of each month at 2pm [AEDT](https://www.timeanddate.com/time/zones/aedt).
**Meeting details**
We use Google Meet:
* To join the video meeting, click this link: https://meet.google.com/vdg-vroc-jkm
* Otherwise, to join by phone, dial +61 2 9051 3228 and enter this PIN: 379 272#
* To view more phone numbers, click this link: https://tel.meet/vdg-vroc-jkm?hs=5
**Timezone converter**
Use the following link to convert to your local timezone, https://www.timeanddate.com/worldclock/converter.html?iso=20190411T040000&p1=57