On Sun, Apr 27, 2014 at 6:18 PM, Richard Hartmann
richih.mailingl...@gmail.com wrote:
On Mon, Apr 28, 2014 at 12:08 AM, Philipp Hug deb...@hug.cx wrote:
If we had DebConf15 chairs, they could be involved from the beginning
without having to bother about DC14 at the same time
This would make
also sprach Brian Gupta brian.gu...@brandorr.com [2014-04-28 13:36 +0200]:
I think one thing that has helped me in the past is to keep in mind
that when I work on something in a DebConf subteam, that we are
working on a proposal for presentation to the larger team, and need to
understand that
Hello Martin,
On 28.04.2014 14:05, martin f krafft wrote:
also sprach Brian Gupta brian.gu...@brandorr.com [2014-04-28 13:36 +0200]:
I think one thing that has helped me in the past is to keep in mind
that when I work on something in a DebConf subteam, that we are
working on a proposal for
also sprach Giacomo Catenazzi c...@debian.org [2014-04-28 14:53 +0200]:
You focus too much on quick decisions, but then you will find your
team alone when approaching DC15.
There's a fundamental problem here to which you are alluding, and
the way to solve it is not by delaying decisions and
Hi Lucas,
As you don't seem to willing to change the current frustrating setup,
please consider the following 2 changes to it:
* Delegation of chairs per DebConf period:
Currently DC15 is in the hot phase of setting up and signing contracts
and other important issues from Debian's PoV.
At the
On Mon, Apr 28, 2014 at 12:08 AM, Philipp Hug deb...@hug.cx wrote:
If we had DebConf15 chairs, they could be involved from the beginning
without having to bother about DC14 at the same time
This would make sense, imo. This is something the chairs could decide
by themselves.
I also note that
Hi,
There has been various questions raised about several topics related to
DebConf15 organization. I'm trying to wrap-up a single answer covering all
questions.
Sorry for not replying earlier. I was travelling during the past week, and
ended up having much less free time than I expected. I
