On Fri, Mar 6, 2015 at 4:07 PM, Tassia Camoes Araujo tas...@debian.org wrote:
I would then suggest to differentiate between the final #agreed and previous
(possible multiple) #proposed?
#proposed is not implemented atm [1]. Proposing an #agreed line is
trivial, though.
And really only state
Hi!
Thanks Marga for following up.
On Tue, Mar 03, 2015 at 12:51:42PM +0100, Giacomo Catenazzi wrote:
On 03.03.2015 11:46, Margarita Manterola wrote:
For future meetings I plan to:
1) When there seems to be agreement on something but it's not 100% clear do:
marga suggests: #agreed
On Tue, Mar 3, 2015 at 11:46 AM, Margarita Manterola
margamanter...@gmail.com wrote:
I'd be happy to hear any other suggestions that others may have regarding
how to improve our meetings to make them easier to follow without making
them take hours and hours.
That all sounds very good.
Margarita Manterola margamanter...@gmail.com writes:
1) When there seems to be agreement on something but it's not 100% clear do:
marga suggests: #agreed we should do foo/bar/baz
And then people can state clearly if they don't agree. This is not just
for me, anyone can suggest an
Hi,
Yesterday it was raised that our IRC meetings might be a bit stressful for
people that are not native English speakers, or that are not used to
following text discussions that go so fast.
I agree that this is a problem and good like to improve the way we do our
meetings.
For future meetings
also sprach Giacomo Catenazzi c...@debian.org [2015-03-03 12:51 +0100]:
I also find that sometime I'm trying to write an answer and
topic/agree were moved before I can press RETURN. On old meeting
there were a lot of silence periods, which was also not ideal.
Maybe we can just vote? Maybe
On 03.03.2015 11:46, Margarita Manterola wrote:
For future meetings I plan to:
1) When there seems to be agreement on something but it's not 100% clear do:
marga suggests: #agreed we should do foo/bar/baz
This could help, allowing a short answer (No), so who disagree can
have time to
