<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear LOC,<br>
<br>
While planning sessions and workshops, please don't forget these
dedicated to FOSS4G education. Some time ago we were discussing the
possibility to have education pointed out as a special topic in a
general track.<br>
<br>
Please let me know when the proper time comes to move on with this
topic.<br>
<br>
Regards,<br>
Ela<br>
Your contact point of the ICA-OsGeo Lab Network :-)<br>
<span style="font-size:10.0pt;color:gray"><br>
</span>
<div class="moz-cite-prefix">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#595959" lang="EN-US">----------------------------------------------------------<br>
Elżbieta
Wołoszyńska-Wiśniewska<br>
Head of Education Unit<br>
Deputy Country Coordinator of GLOBE Program</span></p>
<p class="MsoNormal"><span style="font-size:
9.0pt;color:#595959" lang="EN-US">UNEP/GRID-Warsaw Centre<br>
Sobieszynska 8, 00-764 Warsaw<br>
phone.: +48 22 840 6664 ext. 116<br>
fax: +48 22 851 6201<br>
</span><a href="http://www.gridw.pl"><span
style="font-size:9.0pt" lang="EN-US">http://www.gridw.pl</span></a><span
class="MsoHyperlink"><span style="font-size:9.0pt"
lang="EN-US"><br>
</span></span><a href="http://mass4education.eu"><span
style="font-size:9.0pt" lang="EN-US">http://mass4education.eu</span></a><span
class="MsoHyperlink"><span style="font-size:9.0pt"
lang="EN-US"> </span></span><u><span lang="EN-US"><br>
</span></u><b><span style="font-size:9.0pt;color:#000066"
lang="EN-US"><br>
PLEASE
CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL</span></b></p>
<p class="MsoNormal"><b><span
style="font-size:9.0pt;color:#000066" lang="EN-US"> </span></b><b><span
style="font-size:9.0pt;color:#000066" lang="EN-US"></span></b>W
dniu 2015-10-21 o 08:49, <a class="moz-txt-link-abbreviated" href="mailto:till.adams@fossgis.de">till.adams@fossgis.de</a> pisze:<br>
</p>
</div>
</div>
<blockquote cite="mid:91b0a7c368bbf90ad1d72e9184f7073c@fossgis.de"
type="cite">Hi all,
<br>
<br>
Darrrell, Marc, Volker, thanks for your comments on that.
<br>
@Marc, I do not feel in a pitiable situation ;-) - other teams had
and always will have the same problem ;-)
<br>
<br>
Although I like to pick up proposals and also like to cash in from
experiences past teams made, I'd like us to keep the suggested
weekly IRC meeting. From my own company experience I know that
meetings, that are not once a week or once a month don't work. You
never know, is it this week, is it next week or was it last
week...?
<br>
<br>
Also, if we recognize, that IRC is not appropriate we can change
every time ;-)
<br>
<br>
So, first IRC meeting for LOC will be 26.10.2015 at 5 p.m. CET:
<br>
<a class="moz-txt-link-freetext" href="http://www.timeanddate.com/worldclock/fixedtime.html?msg=FOSS4G+Weekly+IRC+Meeting&iso=20151026T17&p1=312&ah=1">http://www.timeanddate.com/worldclock/fixedtime.html?msg=FOSS4G+Weekly+IRC+Meeting&iso=20151026T17&p1=312&ah=1</a>
<br>
<br>
Thanks, Till
<br>
<br>
<br>
<br>
<br>
<br>
Am 2015-10-21 00:12, schrieb Volker Mische:
<br>
<blockquote type="cite">Hi all,
<br>
<br>
I don't agree with Darell and Marc. Meeting over IRC can also be
very
<br>
efficient and I've seen those meetings. The problem with running
them
<br>
over voice is that people there also need to be efficient, if
there are
<br>
not, text can be faster. I see several advantages:
<br>
<br>
- Many people can "speak" at once
<br>
- You don't need to interrcommiserateupt someone
<br>
- It's easier to speak up and disagree (e.g. if you are more of
a
<br>
silent person)
<br>
- You have everything in written
<br>
- Watchers can just join an lurk
<br>
- You might want to attend, mostly for listening or just for
one small
<br>
item, you can do something next to it
<br>
<br>
Cheers,
<br>
Volker
<br>
<br>
On 10/20/2015 11:51 PM, Marc Zakelijk wrote:
<br>
<blockquote type="cite">I agree with Darrel; voice beats text in
efficiency.
<br>
commiserate
<br>
I see where Jeff comes from.
<br>
But for needed history and monitoring a central doc will
suffice when at least capturing;
<br>
- planning per sub-committee and master planning
<br>
- each agenda item has; A(ctivity statement ), B((enefit
clearly defined, otherwise activity ditched), C(oncern or
risk assessment of intended action success) and D(o r action
stated to overcome concern)
<br>
- each activity has people who are R(responsible, who has to
Do something), A(countable, who monitors progress), (to be)
C(onsulted, for possible advice), (to be) I(nformed, but stays
out of the way as much as possible ;-)
<br>
- there is only 1 Responsible person per task, 1 Accountable,
a few to be Consulted, and more to be Informed
<br>
- is a task or activity too large for one person it gets
divided into smaller tasks with maybe more people involved
<br>
<br>
I commiserate with Till.
<br>
Before everyone suffers from inertia;
<br>
- Without a Program (you can read Product) there is no idea of
who feels/is invited as audience/Buyers of tickets (academia,
developers, non-tech end-users, public sector orgs, NGO's,
commercial orgs, etc)
<br>
- Without an intended audience-segmentation there is no
effective promotion possible, nor can sponsors be sure their
particular audience is present.
<br>
- Without targeted promotion the overall attendance suffers
and cross-pollination between sub-groups suffers too.
<br>
- Without sponsors it will be a rather Spartan affair or very
expensive.
<br>
<br>
My two cents.
<br>
<br>
Vriendelijke groet,
<br>
Marc Vloemans
<br>
<br>
<br>
<blockquote type="cite">Op 20 okt. 2015 om 22:53 heeft Darrell
Fuhriman <a class="moz-txt-link-rfc2396E" href="mailto:darrell@garnix.org"><darrell@garnix.org></a> het volgende geschreven:
<br>
<br>
For 2014 we started with bi-weekly meetings and only moved
to weekly meetings in August. I thought it was sooner than
that, but apparently not.
<br>
<br>
I totally disagree about the IRC/Slack thing, IMNSHO. It’s a
far, far slower way to communicate than voice. A well run
meeting is going to be many times faster.
<br>
<br>
The main thing is:
<br>
<br>
Designate a note taker to:
<br>
• Track New TODOs
<br>
* Track decisions made
<br>
<br>
The note taker is always different from the person running
the meeting.
<br>
<br>
At each meeting, we created a google document for the next
meeting, and people could add to the agenda at any time up
until the time of the meeting. Notes were then taken in that
same document.
<br>
<br>
Always follow up on old TODOs, both to nag and to check for
relevancy.
<br>
<br>
If you want an effective meeting, learn how to run an
effective meeting. They don’t happen by accident.
<br>
<br>
Darrell
<br>
<br>
<br>
<br>
<blockquote type="cite">On Oct 19, 2015, at 06:31, Jeff
McKenna <a class="moz-txt-link-rfc2396E" href="mailto:jmckenna@gatewaygeomatics.com"><jmckenna@gatewaygeomatics.com></a> wrote:
<br>
<br>
Yes at some point soon you should move to a weekly
meeting. I have seen some past committee teams use IRC
successfully (there is the #foss4g channel on freenode
that is mostly empty, awaiting your use), and also phone
conference calls using audio (it could be a weekly hangout
with audio). But personally I find that IRC meetings are
much more "get down to business" than the audio calls ("hi
how was your weekend?"), so I have a preference for the
IRC text chat (or Slack, but that seems to offend some
Open Source "oldtimers" so IRC it is, ha).
<br>
<br>
-jeff
<br>
<br>
<br>
<br>
<blockquote type="cite">On 2015-10-19 5:41 AM,
<a class="moz-txt-link-abbreviated" href="mailto:till.adams@fossgis.de">till.adams@fossgis.de</a> wrote:
<br>
Hi LOC!
<br>
<br>
This is a really honest eamil but unfortunately it looks
like, that it
<br>
is necessary.
<br>
I know, that everybody involved in LOC also has a normal
job and I also
<br>
understand that not everybody of you can act like I am
doing.
<br>
<br>
But...we are now in a situation where I really must
**rely** on
<br>
everybody's contributions!
<br>
<br>
I think that at least it should be possible to everyone,
who gets asked
<br>
about s.th. which is in your personal area of
responsibility to reply to
<br>
a question in a short email.
<br>
And if the reply is: "Sorry, I am short in time for now,
but I will work
<br>
on this on [...]" - that's also fair and nobody will be
angry about that.
<br>
<br>
!!!The worst thing you can do (to all other people
involved in LOC) is
<br>
to do/write/say nothing!!!
<br>
<br>
Please note, that we are far away from having too much
time for
<br>
organization and I really would like to get us all in
motion for the
<br>
upcoming tasks!
<br>
The most urgent things are:
<br>
<br>
-> add more info on the homepage (@Anja, Carmen asked
last week about
<br>
having a meeting this week?)
<br>
-> fix sponsorship and exhibition packages (@Arnulf
and @Hinrich: still
<br>
no reply from you)
<br>
-> fix our contract with WCCB (wrote a question on
this a few minutes ago)
<br>
-> fix of our timetable and with that all the
upcoming tasks
<br>
<br>
So please, please let us get these things in motion!
<br>
<br>
Maybe having a hangout or IRC chat once a week would
make communication
<br>
easier? Our monthly meetings are good but mainly
restricted to people
<br>
located in Bonn
<br>
What do you think? Any other ideas on that?
<br>
<br>
<br>
So far, Till
<br>
</blockquote>
_______________________________________________
<br>
FOSS4G2016 mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:FOSS4G2016@lists.osgeo.org">FOSS4G2016@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss4g2016">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
FOSS4G2016 mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:FOSS4G2016@lists.osgeo.org">FOSS4G2016@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss4g2016">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
FOSS4G2016 mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:FOSS4G2016@lists.osgeo.org">FOSS4G2016@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss4g2016">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a>
<br>
<br>
</blockquote>
_______________________________________________
<br>
FOSS4G2016 mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:FOSS4G2016@lists.osgeo.org">FOSS4G2016@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss4g2016">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
FOSS4G2016 mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:FOSS4G2016@lists.osgeo.org">FOSS4G2016@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss4g2016">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a>
<br>
</blockquote>
<br>
</body>
</html>