----- Original Message ----- > I can definitely tell you what I liked and disliked about these > meetings, and why I stopped going to them. > > * Too many status updates. Putting the status updates in the wiki is > great. Reading over them when a lot of people are listening > synchronously is not. The KISS rule needs to be followed, if it's > more > than 3-4 one line bullet points per category, you're probably giving > too > much information. If you're listing tons of bug numbers with their > summaries, you probably want to link to another wiki page for those > who > are interested in the details.
I have been trying to get more discussion about wip rather than just status. I agree that having someone read the wiki out load is not that useful. > * The order of the meeting is extremely important. I suggested to JP > a > while ago that we should begin the meeting with the roundtable > section, > in order to basically filter the stuff that is really interesting to > engineers at first, so that we can leave after that part if the rest > of > the meeting is not interesting. But if we stopped reading over > status > updates, a lot of that time would have been solved anyway. This was my goal for the key issues section at the top. We haven't gotten to this point but I would like to surface interesting information first. > * Agenda. Be very strict about only talking about stuff that is on > the > agenda at least 10 minutes before the meeting, in order to let people > know whether they're interested in attending. I found out that at > many > times I merely attended to figure out _if_ something interesting is > being discussed, which is a waste of time. This is an interesting idea. This isn't really the culture wrt Mozilla meetings but is something that we can strive towards. > * Having minutes, but not decisions. I think that discussing the > active > issues on mailing lists _could_ be useful if it's limited to 1-2 > minutes, but we should absolutely not use this meeting as a venue for > making decisions since not all of the people with useful feedback > might > be attending, as previously noted. Agreed. The goal is to get the right people involved in the mailing list discussion. > * Have more interesting content for hackers. I think that most of > the > content of the current meetings are project/product level updates, > which > are interesting to read in a wiki page, but not that interesting. I > would really like it a lot more if I could go up and say hey guys, by > the way I added this cool class to MFBT recently which you can use to > do > this cool thing, or, hey, we're seeing this crash which we have a > hard > time reproducing, can anybody help out? Yes! This is exactly the type of content I would like to see in the meeting. To reiterate, if engineers are to meet, I want the discussion to focus on what's actually useful to engineers. What have you hacked recently? How did you make your job easier? What anti-pattern did you recently find? Lawrence > I'd definitely love to attend the meeting in the future to see if it > has > improved enough to make me a usual attendee again! :-) > > Cheers, > Ehsan > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
