Sorry, I must have misunderstood what you meant.
If all you're saying is that sometimes, it's good to call a meeting to
make a decision, I don't think we disagree.
On Thu, Apr 25, 2013 at 4:56 PM, Milan Sreckovic wrote:
>
>
> On 2013-04-25, at 2:07 PM, Justin Lebar wrote:
>
>>> Justin pointed o
On 2013-04-25, at 2:07 PM, Justin Lebar wrote:
>> Justin pointed out his earlier post and the apparent disagreement I had with
>> it with the
>> "pick a long thread topic" example - and he has a point. I meant it as an
>> example, and
>> didn't say as much, and I meant more to focus on decis
> Justin pointed out his earlier post and the apparent disagreement I had with
> it with the
> "pick a long thread topic" example - and he has a point. I meant it as an
> example, and
> didn't say as much, and I meant more to focus on decision making, and didn't
> say that
> either.
I also mea
Justin pointed out his earlier post and the apparent disagreement I had with it
with the "pick a long thread topic" example - and he has a point. I meant it
as an example, and didn't say as much, and I meant more to focus on decision
making, and didn't say that either.
I agree the general engi
Every good meeting needs a conflict - a meeting about whether we should have
the platform meeting would be a great meeting. If we are too large to actually
have a meeting where something could be argued or decided, we probably don't
need that meeting.
Status meetings are useful, but as was p
Lawrence Mandel wrote:
However, I have had people tell me that they do get some value from this
meeting.
What value did they get and what role did they have at mozilla? I am
wondering if the audience for this meeting is no longer mozilla platform
engineers.
__
- Original Message -
> On Thu, Apr 25, 2013 at 8:02 AM, Lawrence Mandel <
> lman...@mozilla.com > wrote:
> > My understanding from speaking with a few people is that the
> > platform
> > meeting was once useful to engineers.
>
> Well, part of that probably has to do with the fact that Mo
> Lawrence Mandel wrote:
> > However, I have had people tell me that they do get some value from
> > this meeting.
>
>
>
> What value did they get and what role did they have at mozilla? I am
> wondering if the audience for this meeting is no longer mozilla
> platform
> engineers.
In the meeti
On Thu, Apr 25, 2013 at 8:02 AM, Lawrence Mandel wrote:
> My understanding from speaking with a few people is that the platform
> meeting was once useful to engineers.
Well, part of that probably has to do with the fact that Mozilla used to be
a much smaller org. In 2008 most of platform enginee
- Original Message -
> I think if we need to find reasons to keep a meeting relevant, we
> need
> to kill the meeting. Lawrence, you should just discontinue the
> meeting
> for a few weeks and see if we really need it. I bet we wont.
My understanding from speaking with a few people is
- 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 no
On 4/25/2013 1:07 AM, Ehsan Akhgari wrote:
On 2013-04-24 3:35 PM, Benjamin Smedberg wrote:
On 4/24/2013 3:13 PM, Justin Lebar wrote:
and last time I checked there's no way
to get notified when a meeting's notes are up (via RSS or e-mail or
whatever).
https://blog.mozilla.org/meeting-notes/arch
On Thu, Apr 25, 2013 at 8:54 AM, Doug Turner wrote:
> I would much rather see us spend the time to curate what's important -- what
> platform people should/must read. Someone started a Reddit subgroup
> r/MozillaTech. This subgroup is much more relevant to the work that my team
> is doing than t
I think if we need to find reasons to keep a meeting relevant, we need
to kill the meeting. Lawrence, you should just discontinue the meeting
for a few weeks and see if we really need it. I bet we wont.
I would much rather see us spend the time to curate what's important --
what platform peo
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 followe
On 2013-04-24 3:35 PM, Benjamin Smedberg wrote:
On 4/24/2013 3:13 PM, Justin Lebar wrote:
and last time I checked there's no way
to get notified when a meeting's notes are up (via RSS or e-mail or
whatever).
https://blog.mozilla.org/meeting-notes/archives/tag/mozillaplatform and
it shows up on
+1 to meeting notes being mailed out or on a feed somewhere.
I generally avoid big meetings like the plague because the density of
discussion that I'm interested in is too low to warrant my full attention,
and I'm not great at context-switching to and from my own work either. I
usually just sit th
On 4/24/2013 3:13 PM, Justin Lebar wrote:
and last time I checked there's no way
to get notified when a meeting's notes are up (via RSS or e-mail or
whatever).
https://blog.mozilla.org/meeting-notes/archives/tag/mozillaplatform and
it shows up on the "projects" planet as well.
--BDS
_
- Original Message -
> One thing I love about the MoCo meetings is that if I don't go, I
> don't miss anything except the chance to ask questions: mbrubeck &co
> create detailed minutes (really, transcripts) of every meeting, which
> I can read on my schedule. He then e-mails the transcr
One thing I love about the MoCo meetings is that if I don't go, I
don't miss anything except the chance to ask questions: mbrubeck &co
create detailed minutes (really, transcripts) of every meeting, which
I can read on my schedule. He then e-mails the transcript out to
everyone, so I don't even ha
tl;dr
I would like to make the platform meeting more relevant for engineers. I have
already made some changes (see below) and am interested in your feedback on
what you would like to get out of this meeting. If you don't currently attend,
what would make this meeting relevant for you?
---
Sinc
21 matches
Mail list logo
