Hello,
>What are your views on ensuring that major parts of the system are maintained >more sustainably, easing off too much workload on just a few people? This is something that should be handled from inside the team itself... Burnout is something many people have experienced, and I sadly don't have any answer for that, except that we might have some psychologist service that provides support for people with too much workload. Burning out is not funny, and asking for help is way more difficult. >2. As an extension of previous question, this is also true for some of the DPL >delegated >teams. Lot of work and less bandwidth, and the role in some of these teams are >directly >related to package maintenance. How do you go about it here? I would try to check on a case-by-case basis, there is no general answer for specific questions. Burning out is a personal issue, and we should try to help people as well as we spot them. Maybe DAM/CT can help identify those, because sometimes being under pressure means more critical way of communicating. >3. I read in at least 2 of all DPL candidate platforms this year that they >intend to >promote in-person meetings and f2f meetings. That sounds good. >However, there are always travel constraints for many contributors or even >time synchronization problems. How do you ensure that people who do not get to >attend such >meetings also get a chance to participate? By scheduling them via multiple people and timezones, we can achieve a goal without many troubles. E.g. european people can have chatting with asian and american people without much effort (one in the morning, the other in the afternoon). G.
