There is a small team (5-7 people who are a part of a larger 15-person entity) of experienced software developers. They are all currently learning a lot of new stuff in a new technology we are employing.
We have hackathons, documentation, central Wikis etc. and are talking in RL a lot. They do not work in a common project though, so there is no project infrastructure like Scrum meetings or the like.
We would like to avoid the situation where people invent the wheel over and over again. Normally we would just drop them in a room, close the door, and let them tell each other what they are working on in a relaxed manner. It would be enough, for example, if one of the guys works on session management at the moment, and another guy starts working on session managament in their project as well, for both of them to know that they are working on similar stuff. Now that they know, they can talk about it in private, later, and exchange best practices etc..
We had similar phases in the past (most parts of the team know each other for many years). It often got ugly because most of them are quite headstrong, competent and "alpha". What happens is that one person tells the others what he is doing, and instantly 3 of the others start taking his solution apart, pointing out deficiencies, arguing about why their solution is better and all that. As strong as most of them are, few of them are very emotionally stable; so everyone takes criticism in a not so good way.
Note that they know/like each other well normally, i.e. when going to lunch; the problem is not general animosities, power-struggles or such.
Is there a good meeting/communication workflow or structure which is easy to explain, simple to handle (by people who naturally scoff at such things), and has the explicit goal of letting people tell each other things without the emotional backfiring of others criticizing all the time?
Bonus points if the method does not require a dedicated leader / moderator but works self-regulating.
Again: they are part of the same organizational team, but they work on different projects, so it's not just a SCRUM or something like that, and there is not a person like a project lead who can just decide stuff (there are no technical decisions to make, at these meetings). I am not looking for a project method, but for a communication method to keep their discussions on a factual level. The goal is to avoid the wasted energy of long discussions of which approach to a particular solution is best.