[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    www/areas/kde-ev/meetings
From:       Jonathan Riddell <jr () jriddell ! org>
Date:       2005-09-28 0:57:14
Message-ID: 1127869034.212021.16052.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 464645 by jriddell:

"last Friday" -> "Friday Aug 26th"


 M  +1 -1      2005-working-groups-discussion.php  


--- trunk/www/areas/kde-ev/meetings/2005-working-groups-discussion.php #464644:464645
@@ -7,7 +7,7 @@
 
 <h2>Summary</h2>
 
-<p>There was an open meeting for 3 hours at aKademy 2005 discussing how to make \
working groups for KDE and allow e.V. to give KDE technical guidance, as agreed at \
the e.V. assembly last Friday.  The idea of the working groups is to create a \
structure which will formalise some roles within KDE and enhance coordination within \
KDE, communication between parts of KDE and delegation.  In doing so they will be \
able to make decisions and perform conflict resolution.  The meeting brainstormed a \
list of groups and brought it down to four groups with various responsibilities (show \
mind map).  The "non-technical administration" group was later dropped because it \
covered most areas that are the direct responsibility of the e.V. board.  There was \
some discussion about whether we should go with the groups that came out of the \
discussion following the brainstorm or groups that are self-forming, it was decided \
to go with the former.  There will be meetings a few times a year with 1 person f  \
rom each working group and the e.V. board to report back on their areas of KDE.  \
Decisions will be made by the e.V. membership at the highest level, the e.V. board \
plus working group Representatives next and the working groups themselves below that \
(with the normal bazaar development below that).  Most decisions will be taken at the \
lowest levels, escalating as needed.  Three groups are now going to decide how to \
form each group, technical, marketing and human-computer interaction and proposals \
for each group will be brought back to the e.V. soon.</p> +<p>There was an open \
meeting for 3 hours at aKademy 2005 discussing how to make working groups for KDE and \
allow e.V. to give KDE technical guidance, as agreed at the e.V. assembly on Friday \
Aug 26th.  The idea of the working groups is to create a structure which will \
formalise some roles within KDE and enhance coordination within KDE, communication \
between parts of KDE and delegation.  In doing so they will be able to make decisions \
and perform conflict resolution.  The meeting brainstormed a list of groups and \
brought it down to four groups with various responsibilities (show mind map).  The \
"non-technical administration" group was later dropped because it covered most areas \
that are the direct responsibility of the e.V. board.  There was some discussion \
about whether we should go with the groups that came out of the discussion following \
the brainstorm or groups that are self-forming, it was decided to go with the former. \
There will be meetings a few times a year with 1 p  erson from each working group and \
the e.V. board to report back on their areas of KDE.  Decisions will be made by the \
e.V. membership at the highest level, the e.V. board plus working group \
Representatives next and the working groups themselves below that (with the normal \
bazaar development below that).  Most decisions will be taken at the lowest levels, \
escalating as needed.  Three groups are now going to decide how to form each group, \
technical, marketing and human-computer interaction and proposals for each group will \
be brought back to the e.V. soon.</p>  
 <p>These notes are written in the third person because they often paraphrase rather \
than quoting directly.</p>  


[prev in list] [next in list] [prev in thread] [next in thread]