| Re: [che-dev] Remove regular team updates within Community meeting |
IMO, a list of github issues is simply not an good picture of what is going on in the various teams: I'm more interested in hearing about what is important and what the big picture looks like. However, I don't think spending time in the meeting on a progress report is worth the time: there is hardly ever any interaction about the team reports. And if there is only one person talking, you should not have a meeting, you should write a mail. So what I propose is this:
- team leads put a section into the community meeting doc (sorry
leads ;-)). For red-hatters, the info should already exist in the
Wednesday report. deadline is 15:00h CET.
- if there is anything to be discussed, we can do it during the
meeting.
- if there are no topics, the meeting is cancelled.
/Thomas
Problem with Github is that you have to actively look for the information (which is not trivial - apply all the filters, labels might not always match, sprints does not match the weeks, different teams can have different sprints, ...) so it's easy to miss something that might be in your interest and you don't know about it. The benefit of having such updates on weekly call is that you get the information passively. You just attend the call and others tell what's going on and you may hear something that might be important for you.
However, I think that community call is not mandatory. It's not a company meeting or such. So teamleads or whoever else can give whatever information they think might be useful for others. They don't have to describe in detail all the issues the team is working on. They don't have to give any update at all. Same for others, if they don't want to hear the team updates, they can leave the call earlier.
So I wouldn't completely remove this part of the community call, but I would consider updating the form.
On Tue, Nov 10, 2020 at 10:41 PM Artem Zatsarynnyi <azatsary@xxxxxxxxxx> wrote:
_______________________________________________Hello folks,
Last Che Community meeting I've raised a topic to discuss the usefulness of the regular updates given by the teams involved in Che development.
As there were different opinions and we weren't able to achieve a consensus on the subject, I decided to continue discussing it offline.
A bit of background for those who weren't able to attend the latest meeting or not attending it on a regular basis:usually, at the end of every Che Community meeting, Red Hat team leads give an update
on the teams' work done during the past week and what is planned for the current week.
First, it's prepared in a written form in every Che Community meeting document, e.g. [1]
and then every team lead is retelling it, one by one.
As you see, in 99% these updates look like a list of the issues' titles given from GitHub with the links attached.
Actualy it represents nothing more than just the sprints issues that are publicly available on GitHub for everyone.
So, I expressed my doubts if we really need such a regular part of our Community meeting.
Does it really make sense of preparing it and giving it during every call?During the call, I proposed to remove this part. Some people are sharing this opinion with me. Some people were against that.
As I remember, there were suggestions to convert it to a different form, e.g.:- provide the written updates weekly to the community chat- make it convenient to see on GitHub (maybe labeling the sprint issues with the "current-sprint" label and posting a GitHub query somewhere?)
In this follow-up thread, I want to ask the Community if someone would find it helpful to get such info about the current Che work?
Or being able to get information related to the interesting area from GitHub, by tracking the issues/PRs, is completely enough?
I believe we can remove the "team updates" part from our Community meeting. And there's no need to provide it in a written form.Since all the information is already present on GitHub, it's already labeled and marked with the corresponding milestones.I guess people are tracking needed info on GitHub, but not waiting for the weekly updates on a meeting.
---
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
--
Michal Vala
Senior Software Engineer, Eclipse Che
Red Hat Czech
_______________________________________________ che-dev mailing list che-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev