Accédez au panneau de paramètres de Mingle à l’adresse <votresite.com>/admin/site_settings/category/all_results?filter=mingle. Sélectionnez un groupe, configurez une période et choisissez un utilisateur pour envoyer le message. Mingle est désactivé par défaut pour vous assurer de tout configurer comme vous le souhaitez, alors assurez-vous de l’activer une fois prêt.
Accédez à la catégorie Staff ; vous devriez y voir un nouveau sujet avec « Mingle » dans le titre. C’est le modèle de votre message ! Cliquez dessus, lisez les instructions et personnalisez un message à envoyer à vos utilisateurs.
Notez que vous pouvez spécifier plusieurs groupes à mélanger en utilisant le format suivant pour mingle_group_name :
groupe_1|groupe_2|groupe_3
Vous pouvez également modifier la taille des groupes dans lesquels les personnes sont placées (la valeur par défaut est les paires) en changeant l’option « Taille du groupe Mingle ».
Si vous souhaitez définir une heure spécifique pour le prochain match, vous pouvez le faire en cliquant sur « modifier » à côté de la prochaine heure d’exécution planifiée ; Si vous modifiez le type d’intervalle ou le nombre d’intervalles (par exemple, passer de 3 à 4 semaines, ou de 3 jours à 3 semaines), Mingle recalculera automatiquement le travail existant pour l’intervalle de temps spécifié.
En cas de problème
Vous pouvez voir le prochain Mingle planifié dans votre file d’attente Sidekiq à l’adresse <votresite.com>/sidekiq/scheduled ; c’est celui nommé Jobs::Mingle. L’ajouter à la file d’attente l’exécutera immédiatement et en planifiera un autre pour le futur.
Si vous vous retrouvez sans travail planifié là-bas, désactivez simplement puis réactivez le plugin Mingle, et il devrait revenir.
Pour arrêter la planification des Mingles, désactivez simplement le paramètre mingle_enabled (cela tuera également le Mingle actuellement planifié).
Si vous avez abîmé votre modèle au-delà de toute réparation , vous pouvez récupérer le modèle original en exécutant :
/var/discourse/launcher enter app
rails c
Mingle::Initializer.new.reinitialize!
Contribution
Rapports de bugs
Il s’agit actuellement d’un plugin bêta (je l’ai écrit hier ), alors essayez-le et signalez tout problème en me mentionnant (@gdpelican) dans ce sujet ou dans la liste des problèmes.
Créez votre branche de fonctionnalité (git checkout -b ma-nouvelle-fonctionnalité)
Validez vos modifications (git commit -am 'Ajouter une fonctionnalité')
Poussez vers la branche (git push origin ma-nouvelle-fonctionnalité)
Créez une nouvelle demande de fusion
Soyez un contributeur open source incroyable !
Ce qui pourrait se passer ensuite
Pour l’instant, les appariements sont complètement aléatoires, mais peut-être qu’il existe une meilleure méthode, en tenant compte du fait qu’une paire particulière a déjà été appariée, si ce sont des vétérans chevronnés ou des débutants, etc.
Actuellement, s’il y a un nombre impair de personnes dans le groupe, une personne est « laissée de côté » pour chaque ensemble de matches. Il serait agréable d’ajouter cette personne à un message à trois personnes, ou de faire autre chose que de l’ignorer.
Je pense que nous aurons peut-être besoin d’une prise en charge d’un élément « par défaut » à placer dans le modèle si, par exemple, un utilisateur n’a pas un champ personnalisé particulier défini (pour l’instant, il mettra simplement la chaîne vide, ce qui pourrait créer des phrases étranges comme « Saviez-vous que Flynn ? »).
Very cool!
I think the ability to set the day of week and time of day to do the matchups would be on my immediate wishlist, so people would get the message when they are likely to be around and ready to reply.
And I think multiple text templates would be even better, to keep the bot from repeating itself each time it sends out the scheduled messages, and allow varying the number of people in each message. So you could mingle with just one person one month, then get a group message with 3-5 people the next and so on accompanied by a message template that matches the number of participants.
Yeah, I agree, but copy isn’t my super-strong suit, and of course I would think that every community would want some level of customization there; online communities being a quite different message than in-person work communities, for example.
Maybe you or @erlend_sh or @HAWK or some of the other more wordsy-minded folks could help me get to a better default message there? PRs are, of course, welcome. (I also need to shuffle it around so that that default text there is translatable)
EDIT: if you try this out in your community, I’d love to see what you put for your templates; feel free to send em to me and I’ll cobble together a better default at some point.
I have an idea: to make this viable for new or inactive forums, what about being able to match users that have last signed in the last 7 days (or any set time) so that mingles can be expected to be active. Because if random users get paired, there can be a good chance of pairing with an inactive user. Just a thought
This is so awesome that it makes me want to break my rule of not installing new plugins until they’ve been tested for a while!
One quick suggestion regarding wording: I think it would sound much more inviting if the message title said “You’ve been invited to a mingle” instead of “You’ve been matched for a mingle”.
And some ideas for further development:
It would be very useful to match pairs from different groups. (e.g. on one of my sites users are members of groups to reflect their background (from what perspective they are interested in the forums subject matter) and while it could be useful to match people from the same background (strengthen bonding social capital) it would also be great to match people from different backgrounds (strengthen bridging social capital).
It may be useful to be able to specify the size of the mingle groups. I’m not sure about this because you may need to do it in diads in order to maximize likelihood that a conversation actually takes off (if you know, it’s only you and one other person, you may feel more inclined to respond than if you know there are others who can respond instead of you). But, given that the vast majority of any forum is passive, it may also be so that neither of the two matched users responds at all, so that nothing happens at all, wheras if you have, say, four people in a group, you have double the chance that someone makes the first step. And with three instead of one potential respondent, chances are that at least one of them responds. And once that has happened, chances are that the other two also chime in. It’s a matter of trying out, I guess, but my prediction would be that diads will only work if one or both users are rather active/committed users (which gives us yet another reason for suggestion 1 above).
(NB: this is waiting on a PR to core to add the plugin outlet, so it won’t show up today.)
So you can now go “I want the events to happen every 4 weeks”, and then change the time of the next event to be, say, Tuesday at 2pm or whatever you fancy.
I’ve made it so that the group input can accept multiple group names delimited by |. So you can put
marketers|engineers
And get matches from both groups (note that there will still be inter-group matches, this simply takes users from both groups and mixes them up)
I merged a PR to translate it into Russian, thanks @Stranik!
Some thoughts on other feedback:
Re having multiple templates. Yes? But I’m not totally convinced of the right method here yet. As an admin, I think I’d much rather update my single template and know what’s going out, rather than having three templates that could go out. Also, since it’s a topic with an edit history, if I want to go back to a previous version, it’s really easy to do so, meaning you don’t gain a whole ton from having multiple templates; a single topic can currently hold multiple templates through the edit history.
I’m not certain about a recency threshold just yet, but I’m considering it.
Also, could you make this a Wiki topic plz @codinghorror? [Side note, I wonder if there’s appetite for a setting which allows all topics in a category to be wiki topics automatically]
I am so excited for this! I’m now wondering what’s the easiest way for people to move in and out of being paired for a mingle. For example, is there a way to pre-message people in a group and say something like:
Get ready to mingle! If you want to be paired up with another member of the community on August 27th, click here to sign up. If you want to wait until next time, no action needed.
Note: Not interested in mingling anymore? Click here to opt-out of these emails
This would also address the issue @nexo brought up re: inactive users.
Or, maybe a workaround is for the group admin to clear out the group each time and have people add themselves back in? That sounds like a lot of work, though…
I think you can totally handle this manually for the time being.
Create a new group, minglers for example, and set it to be public and anyone can join and leave
Send out a message to trust_level_1 (or everyone, or people you care about), introducing the program and explaining that it’s opt-in. Include a link to yoursite.com/groups/minglers, and instruct them to click ‘Join’ if they want to be a part.
One-click opt-out seems like a thing we could consider, but for now you could customize your PM template to have something like
Not interested in mingling in the future? Click [here](yoursite.com/groups/minglers) and select ‘Leave’ to opt-out.
This also seems to be related to “oops” page crashes, in that mingle and the Iconified Header Links theme somehow conflict. When both are active my rebuild always fails. To fix it I have to:
enter safe-mode
disable Iconified Header Links
load index page
re-enable Iconified Header Links
This only happens when Mingle is installed and active.
This is pretty neat - thanks for creating this plugin and sharing it with the community! Is anyone using it with success? How is it going?
I was just talking with some colleagues in my community about bringing people together around themes of shared interest. E.g. people we know to have shared interest who we think should meet. We already do it on an ad hoc basis, but this plugin came to mind as a means to systematize it and not create more opportunities for connecting and engaging.
I wonder if there might be scope and interest to combine this with the Events Plugin 📆 by @angus, to allow for the creation of scheduled mingle events. The events modal when creating an event topic could have a “this is a mingle!” option, which when selected opens up options to set it up including the message template.
Other ideas that spring to mind:
ability to customize the “host” user who sends the mingle messages, e.g. it could be a moderator in charge of the mingle event.
ability to include a group in the message and add tags for coordinating any followup, which would work well with the Tickets Plugin 🎟 by @angus
ability to specify user fields for matching for a specific mingle event, e.g. to connect up people from same country or who share some datapoint in user custom fields
Separately from this it’s occurring to me that it would be interesting to be able to grab a list of users in a particular topic or message, and add them to a discourse group to use for various purposes like this. I suspect there’s already a data explorer query for this (is there?) but some UI method for admins would be neat. Being able to take the people who have contributed to an active topic and obviously have shared interest and starting a mingle event for them would be super interesting.
And finally, I’d love to see the Voice recording plugin by @pawel get some love, which would really make mingling a heck of a lot more dynamic and fun… letting people save recorded messages to each other.
Here are the /logs errors from hitting it again earlier today:
ArgumentError (comparison of Integer with nil failed) /var/www/discourse/app/models/theme.rb:132:in `sort!'
3:24 pm
Failed to handle exception in exception app middleware : comparison of Integer with nil failed
3:24 pm
The weird thing is, even after removing mingle entirely, including the themes it adds, my site remains broken until I disable Iconified Header Links. Yet, it only ever happens when mingle starts off in the mix. I’m not sure what to make of that, but it seems worth noting.
Any chance you will further develop this plugin to ensure that mingle matches are not from within the same group, when mingling groups? I’m creating a discourse community that will have several user types, all related with one another in the same industry of engineering, and I’d like to mingle them in ways that will be mutually beneficial. It would be less beneficial to mingle those of the same group, at least for my use case. Thoughts?
Circling-back on this. My forum has a focus on humanitarian engineering, and I will have groups of mentors and proteges, as well as those seeking and providing help. It would be great to connect these folks in a targeted way. Has there been any development in ensuring that mingle will not match folks within the same group?
pour Discourse, inspiré par le bot Slack Donut et initialement discuté ici. [Bonjour @debryc !]
, vous pouvez récupérer le modèle original en exécutant :
, vous pouvez récupérer le modèle original en exécutant :
), alors essayez-le et signalez tout problème en me mentionnant (@gdpelican) dans ce sujet ou dans la liste des problèmes.
Il serait agréable d’ajouter cette personne à un message à trois personnes, ou de faire autre chose que de l’ignorer.
