<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Ok, I can see there’s a general preference to keep things in line with what’s worked to-date .. but can I suggest that we move away from the formal RFP / competitive selection process, and instead work directly with interested LOCs to collaboratively come up with a series of options to choose from? The competitive structure feels like it pushes everyone into a “pick from option a, b, or c” instead of working together with the local groups to make all options as solid as possible.</div><div class=""><br class=""></div><div class="">Issues like the “all events proposed August dates, but no one wants August” can be addressed directly through this process if we can get away from a strict bureaucratic process.</div><div class=""><br class=""></div><div class="">Admittedly at the end of the day, one option has to be selected, and for that a vote is needed — but I think we would get far stronger options on the table if the committee was actually working with the LOCs to prepare them.</div><div class=""><br class=""></div><div class="">That would provide opportunity to go back to the board if we need clarification on priorities, etc.. through the process.</div><div class=""><br class=""></div><div class="">Dave</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 1, 2016, at 5:29 PM, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Re: local vs global PCO: Something in between might be better.
Something floated and seriously considered a few years back was to
have a paid position at OSGeo whose primary responsibility is to
support FOSS4G LOC's. OSGeo would need to decide whether it can
afford such a position.</p><p class="">Re: Conference committee vs Board selecting conferences. There
will likely always be many board members with interest and
experience in conferences. If a board member wishes to contribute
to discussion about conferences, it should be done on the
conference email list. If the board member wishes to put in the
extra effort required to research conference proposals and help
with conference selection, they should join the conference
committee. Of course, the board should have final say and veto
over a conference committee decisions, and can also provide OSGeo
goals which flow down to the conference committee.<br class="">
</p><p class=""><br class="">
</p>
<div class="moz-cite-prefix">On 1/06/2016 9:46 pm,
<a class="moz-txt-link-abbreviated" href="mailto:till.adams@fossgis.de">till.adams@fossgis.de</a> wrote:<br class="">
</div>
<blockquote cite="mid:4b3ed44a6668bd6dfb7d35983eba3c87@fossgis.de" type="cite" class="">Hi,
<br class="">
<br class="">
just two cents from LOC 2016:
<br class="">
<br class="">
to 1.: I also do not like the idea of a fixed PCO. Our (2016) PCO
is locally rooted, they know the venue, the city, the things you
can do on a local base. It would be dangerous not to have the
possibility to catch hold of this knowledge. Also, in my eyes,
having always the same PCO means that FOSS4G conferences get equal
and equal. One of the things I like, is that LOC's have the
freedom to do something new, to add in new elements into a
conference. That keeps FOSS4G living and kind of surprising. The
same PCO bears the danger to do "business as usual" year to year.
<br class="">
<br class="">
Pricing:
<br class="">
If the board decides that we want cheaper/free tickets for
students/people from 3rd world countries, the board must take over
full financial risk for every event (as it should be in general in
my eyes). Offering such reduced fees leads to a very very
difficult situation of financial planning for LOC's.
<br class="">
<br class="">
Regards, Till
<br class="">
<br class="">
<br class="">
<br class="">
Am 2016-05-31 19:43, schrieb Steven Feldman:
<br class="">
<blockquote type="cite" class="">Summing up my views on various topics on
this mail thread
<br class="">
<br class="">
I am in the camp that says that the current process sort of
works,
<br class="">
there is always room for improvement but I would be against
Dave’s
<br class="">
approach of locking us into a fixed PCO and pushing the
selection to
<br class="">
the Board.
<br class="">
<br class="">
1) Is there a PCO with expertise to operate across the whole
globe? I
<br class="">
doubt that any of the smaller cost effective providers could
offer
<br class="">
that service
<br class="">
2) The key to a successful event is an energetic and imaginative
LOC,
<br class="">
the current process has thrown up a heck of a lot of good teams
who
<br class="">
have worked immensely hard. Would a change to a board determined
<br class="">
choice of city have the same effect?
<br class="">
3) there is nothing to stop the Board suggesting to a city/LOC
that
<br class="">
they should submit a proposal. the initial letter is very simple
and
<br class="">
quick
<br class="">
<br class="">
BTW we still have an outstanding topic to get a board decision
on how
<br class="">
we wish to interface with Location Tech on the global event. Can
they
<br class="">
be a PCO, underwriter and joint promoter of the event? This
topic
<br class="">
generated a lot of debate (some of which was regrettable in
tone) when
<br class="">
we were choosing for 2017. It would be good to be clear on this
before
<br class="">
starting the 2018 process.
<br class="">
<br class="">
There has been some discussion about the cost of FOSS4G, whether
it
<br class="">
is too expensive, how it could be reduced etc. I have helped to
<br class="">
organise a lot of events and I do not know how you can run an
event
<br class="">
without incurring expenses (venues, catering, AV, wifi,
registration
<br class="">
etc) of course there are cheaper ways of doing things but they
are
<br class="">
rarely done for nothing. So the delegate price is a function of
<br class="">
choices on venue etc, the level of sponsorship that we can
attract (in
<br class="">
recent years between $10 and $20 per delegate approx) and the
level of
<br class="">
surplus returned to OSGeo (in recent years between $10 and $15
per
<br class="">
delegate approx) and the number of free entries that we offer to
<br class="">
speakers, workshops, students and those from less advantaged
<br class="">
communities. It would be helpful if the Board could set some
policy on
<br class="">
this topic before we go out for the 2018 call.
<br class="">
<br class="">
I agree with that we should have a more transparent way of
evaluating
<br class="">
bids as CC chair perhaps I should put together a straw man of
<br class="">
selection criteria (a bit like tender making criteria)? Possible
<br class="">
criteria could include - ticket cost, travel cost, accommodation
cost,
<br class="">
strength of LOC, any requirements for an OSGeo financial
guarantee,
<br class="">
risk, innovation, outreach programme, grant programme, etc.
<br class="">
<br class="">
There is a lot of work involved in assessing bids, I am in
favour of
<br class="">
leaving the selection to the CC with the Board having the final
<br class="">
approval. This reduces workload on the board (except those
members who
<br class="">
are also CC members).
<br class="">
<br class="">
Re membership of CC. I remain of the opinion that it should
comprise
<br class="">
up to 12 past chairs or vice chairs of global and regional
events with
<br class="">
selection by the Board if there are more candidates than places
(norm
<br class="">
should be to retire from CC after a max of 4 or 5 years, enough
is
<br class="">
enough after all!). You don’t need to be a member of the CC to
express
<br class="">
opinions on the CC list or to contribute time in working on
policies
<br class="">
etc on the wiki, but past experience should be a criteria for
being
<br class="">
one of those voting.
<br class="">
<br class="">
I have suggested in the past that the CC should have the ability
to
<br class="">
influence the timing of regional events that might conflict with
the
<br class="">
global event. One way would be requiring anyone who wanted to
use the
<br class="">
FOSS4G brand for an event to apply to CC with their proposed
dates.
<br class="">
Need not be a cumbersome process but would establish a way to
avoid
<br class="">
conflicts.
<br class="">
<br class="">
It would be great to have a f2f between board and CC members
when we
<br class="">
are all in Bonn, no time will be perfect for everyone so how
about
<br class="">
16.00-17.00 on Wednesday 25th August (finishing well before the
AGM)?
<br class="">
Till has offered to allocate a room to us. Shall I set up a
doodle
<br class="">
with a couple of time slots for people to choose or just go for
this
<br class="">
one?
<br class="">
<br class="">
______
<br class="">
Steven
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On 31 May 2016, at 16:01, Helena
Mitasova <a class="moz-txt-link-rfc2396E" href="mailto:hmitaso@ncsu.edu"><hmitaso@ncsu.edu></a> wrote:
<br class="">
<br class="">
Dave,
<br class="">
<br class="">
I agree with Maxi. I have been involved with conference
committee for many years and served on steering committees for
academic track
<br class="">
on quite a few of them and I actually like the current system
where we have FOSS4G NA organized by LocationTech and the
other
<br class="">
conferences organized in quite diverse ways by LOC. I think
LocationTech has done a great job for the conference in
Raleigh,
<br class="">
I liked the way how it was organized.
<br class="">
But at the same time, as Venka mentioned some time ago,
conferences organized by LOC help build the community and
broaden
<br class="">
the cultural experience - each LOC brings something new to the
conference and I think that is a good thing,
<br class="">
as the diversity of approaches makes the conference series
more robust.
<br class="">
<br class="">
I think that Maxi’s suggestion for more transparent evaluation
would help to clear some misunderstanding on the votes
<br class="">
both at the conference committee level and the board level.
<br class="">
<br class="">
Regarding Cameron’s note about the need for experience with
conferences when making the decisions, when you look at the
board members,
<br class="">
you can see extensive experience with organizing FOSS4G
conferences at all levels for many years, including running
the conferences
<br class="">
and working with LOCs.
<br class="">
<br class="">
On the more practical side, for 2018 RFP we will need to
address the timing of FOSS4G NA and FOSS4G Global becuase
<br class="">
they are geting too close with May too late and August too
early (and a vacation time!).
<br class="">
<br class="">
Helena
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On May 31, 2016, at 8:21 AM, Dave
McIlhagga <a class="moz-txt-link-rfc2396E" href="mailto:dmcilhagga@mapsherpa.com"><dmcilhagga@mapsherpa.com></a> wrote:
<br class="">
<br class="">
Hi Cameron and Maxi,
<br class="">
<br class="">
Thanks for the quick feedback on this.
<br class="">
<br class="">
The decision (ie who makes it) I think here is less of the
issue than the actual process itself.
<br class="">
<br class="">
Does anyone else feel that we could do a better job here if
we scrapped this competitive LOC process and instead worked
to compare potential cities/countries and make a decision
this way?
<br class="">
<br class="">
FOSS4G-NA has worked this way for several years, and it
seems like a much more collaborative approach to making a
decision, instead of the bureaucratic RFP-like process we’ve
put in place that really locks us in to a pre-set path.
<br class="">
<br class="">
Dave
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On May 31, 2016, at 1:44 AM,
Massimiliano Cannata <a class="moz-txt-link-rfc2396E" href="mailto:massimiliano.cannata@supsi.ch"><massimiliano.cannata@supsi.ch></a>
wrote:
<br class="">
<br class="">
Dear all
<br class="">
Thanks for sharing your thoughts.
<br class="">
<br class="">
I see the current process quite fine with conf com
evaluating the proposal and the board confirm or
eventually override the rank given.
<br class="">
<br class="">
The only thing i can suggest is to have a transparent
process of evaluation in the sense of having well defined
evaluation criteria justified by voting members.
<br class="">
E.g.: Not only my vote for A but for A-prices: 7 out of 10
with short motivation.
<br class="">
<br class="">
In this way results are transparent and easier to be
understood.
<br class="">
<br class="">
Cameron, i think that saying that if you didn't run a big
conference you are not eligible for voting is deeply
wrong.
<br class="">
It is like excluding users from PSC because are not
developers. Diversity of visions and ideas and point of
view brings often innovation and improve the processes.
<br class="">
<br class="">
Maxi
<br class="">
Il 30/Mag/2016 23:52, "Cameron Shorter"
<a class="moz-txt-link-rfc2396E" href="mailto:cameron.shorter@gmail.com"><cameron.shorter@gmail.com></a> ha scritto:
<br class="">
Dave,
<br class="">
<br class="">
I like where you are going with this email thread.
<br class="">
<br class="">
I'll expand to say that making an informed decision about
FOSS4G city selection involves:
<br class="">
<br class="">
1. A significant time studying proposals
<br class="">
<br class="">
2. Significant experience understanding the complexities
running a conference (as experienced by prior foss4g
committees)
<br class="">
<br class="">
Unless board members have been involved in running a
conference they would likely need to defer to expertise of
others in making a FOSS4G decision.
<br class="">
Volunteer effort is thin in both the conference committee
and the board committee (to the level required to
understand a FOSS4G proposal). I agree with Dave about
outsourcing this work.
<br class="">
As it stands, I think the conference committee is better
qualified to make a better decision on FOSS4G selection.
But board input should be welcomed.
<br class="">
<br class="">
Warm regards, Cameron
<br class="">
<br class="">
On 31/05/2016 1:11 am, Dirk Frigne wrote:
<br class="">
<blockquote type="cite" class="">Dave,
<br class="">
<br class="">
Thank you for your mail.
<br class="">
It is very informative, and I will put a topic on the
next board meeting
<br class="">
on June, 9. I think the points we should discuss at the
board level are:
<br class="">
<br class="">
1. What does the board expect from the conference
committee, so it can
<br class="">
make a right decision.
<br class="">
2. What is the vision of the board concerning the most
important event
<br class="">
of OSGeo.
<br class="">
<br class="">
It is clear FOSS4G (main and side events) become more
and more important
<br class="">
to outreach to new potential members, and to connect and
'energise' the
<br class="">
current members. Almost every week there is a FOSS4G
event somewhere on
<br class="">
this planet. It should be great to have an overview list
of all the
<br class="">
FOSS4G events taken place in the last 10 years. I've
seen a slide by
<br class="">
Till about the global FOSS4G events with the number of
attendees, but an
<br class="">
overview of all the events would give a good insight in
the importance
<br class="">
of the movement.
<br class="">
<br class="">
I will be in Bonn and open for a face2face meeting with
other members of
<br class="">
the committee to discuss these topics.
<br class="">
<br class="">
Dirk.
<br class="">
<br class="">
On 30-05-16 16:07, Dave McIlhagga wrote:
<br class="">
<br class="">
<blockquote type="cite" class="">Steven,
<br class="">
<br class="">
First of all - I think this committee has done a lot
of really good and
<br class="">
very important work over the years, so for everyone
here please don’t
<br class="">
take any of this as a criticism of the work that’s
been done in the
<br class="">
past. I think we’ve done the best we can with what
we’ve had to work
<br class="">
with and the mandate of the committee.
<br class="">
<br class="">
Note: I’ve cc’d the board here as some of this needs
to be discussed at
<br class="">
the board level not just within this committee.
<br class="">
<br class="">
<br class="">
I have a few areas of concern that I think are worth a
discussion here:
<br class="">
<br class="">
<br class="">
1. *Who Decides?*
<br class="">
<br class="">
I believe we need to separate out the “Doing” from
“Decisions” —
<br class="">
Committee’s are put in place to handle the
_/workload/_ that would be
<br class="">
too onerous for the board, and to make decisions that
individually have
<br class="">
_/relatively low impact on the organization as a
whole/_. The Board is
<br class="">
responsible for making the _/decisions that will have
significant impact
<br class="">
on the organization/_.
<br class="">
<br class="">
With that in mind — my suggestion here is that
regardless of the process
<br class="">
we go through to decide on locations for future
events, organizing
<br class="">
committees, timing etc.., (more on this below) the
board should be
<br class="">
making the ultimate decision on the annual event, if
for no other reason
<br class="">
than it’s financial impact on the organization. Any
event could have +/-
<br class="">
$100,000 impact on the organization, and this today is
the primary
<br class="">
source of funding for OSGeo. By definition, that makes
this decision the
<br class="">
most important decision OSGeo makes every year.
<br class="">
<br class="">
Having said that — as we all know here, there is a ton
of leg work that
<br class="">
precedes making this decision — and that’s where the
work of this
<br class="">
committee should be focused. If this group can be in
the business of
<br class="">
_running and managing_ the process of putting on the
conference each
<br class="">
year, and _advising_ the board on options, pros/cons,
etc.. ie. helping
<br class="">
the board to make an informed decision, then we’re
doing our job as a
<br class="">
committee. Then the board can make this key decision
based on the
<br class="">
direction the board is taking the organization. Is
fundraising
<br class="">
important? Is hosting the event in places OSGeo is
strong important? Or
<br class="">
maybe in places it’s weak and wants to grow? Depending
on budget plans
<br class="">
and many other factors — the answers to these
questions can be quite
<br class="">
different.
<br class="">
<br class="">
<br class="">
2. *Selection Process*
<br class="">
<br class="">
I feel that the competitive process we’ve established
that was arguably
<br class="">
well suited for the early days of OSGeo (it was
definitely a step
<br class="">
forward from yours truly choosing - which was the
process pre-OSGeo) —
<br class="">
has run it’s course. With the amount of experience we
have under our
<br class="">
collective belts, and the size of the events we’re
dealing with, why do
<br class="">
we every year need to more or less start from scratch,
and waste
<br class="">
valuable community volunteer time in competition
rather than doing
<br class="">
something collaboratively?
<br class="">
<br class="">
A very simple example of where the current process
fails to meet OSGeo’s
<br class="">
needs is the proposed dates from the most recent
selection process.
<br class="">
Every proposal suggested an August date for the event
… why? Because it
<br class="">
was the cheapest period to rent venues, and could as a
result drive the
<br class="">
most profit for OSGeo, increasing every LOCs chance of
being selected.
<br class="">
That’s possibly the right way to do things … but it
also means
<br class="">
overlapping with many peoples vacation periods,
meaning many attendees
<br class="">
that would typically come, won’t. Was that a good
thing? The competitive
<br class="">
process meant right or wrong, we were more or less
“stuck” with an
<br class="">
August date.
<br class="">
<br class="">
<br class="">
What if instead we did something along the following
(this is just to
<br class="">
get the brain juices flowing, not definitive):
<br class="">
<br class="">
1. Find a PCO we can work with year-after-year … this
would make life
<br class="">
simpler for the committee, and cheaper for OSGeo as
there’s no
<br class="">
year-after-year re-learning. It also means we can much
more effectively
<br class="">
learn from our mistakes and have consistent
relationships to work with
<br class="">
to put on a better show every year.
<br class="">
<br class="">
2. We come up with a predictable date/schedule so that
attendees and
<br class="">
critically sponsors can plan around it
year-after-year.
<br class="">
<br class="">
3. Committee looks into optional cities/countries to
host through a lens
<br class="">
of a combination of availability, cost, transport
access, and access to
<br class="">
locals who could help form a LOC. If this sounds like
a lot of work …
<br class="">
well that’s why you have a PCO you work with year
after year, who can do
<br class="">
the leg work on this for you efficiently and far
better than any of us
<br class="">
can. This also gives you *negotiating* position with
the various
<br class="">
venues/hotels/cities. With a conference the size of
FOSS4g, most cities
<br class="">
have one venue that can support it … not much
bargaining room when
<br class="">
you’re the LOC. But when you’re OSGeo that go to any
city .. you can
<br class="">
negotiate.
<br class="">
<br class="">
4. All of this combined allows us to consult the board
on options we’re
<br class="">
finding, fine tune based on the board’s needs — and
ultimately work in
<br class="">
collaboration with the board to come up with a
selected city, that has a
<br class="">
high chance of success given we’re putting our
collective knowledge and
<br class="">
the PCOs together without having to pick “one proposal
vs. another”.
<br class="">
<br class="">
<br class="">
<br class="">
I’m not sure if this is all making sense — sometimes
email isn’t the
<br class="">
best communicator, but I guess my point is, I think we
can do a lot
<br class="">
better than the current process, and arguably with far
less cumulative
<br class="">
volunteer time when you combine the efforts of the
committee and X
<br class="">
bidding LOCs.
<br class="">
<br class="">
Worth a discussion at least I’d suggest?
<br class="">
<br class="">
<br class="">
Thanks,
<br class="">
<br class="">
Dave
<br class="">
<br class="">
<br class="">
<br class="">
Dave McIlhagga
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:dmcilhagga@mapsherpa.com">dmcilhagga@mapsherpa.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:dmcilhagga@mapsherpa.com"><mailto:dmcilhagga@mapsherpa.com></a>
<br class="">
<br class="">
<br class="">
/Maps at your fingertips/
<br class="">
/
<br class="">
/
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="http://www.mapsherpa.com/">www.mapsherpa.com</a> <a class="moz-txt-link-rfc2396E" href="http://www.mapsherpa.com/"><http://www.mapsherpa.com></a>
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On May 27, 2016, at 1:25 AM,
Steven Feldman <<a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:shfeldman@gmail.com"><mailto:shfeldman@gmail.com></a>
<br class="">
<blockquote type="cite" class="">wrote:
<br class="">
</blockquote>
<br class="">
Dave
<br class="">
<br class="">
Surely the board should delegate important tasks to
its committees not
<br class="">
take on more work?
<br class="">
<br class="">
It sounds like you think something has gone wrong
with the selection
<br class="">
process, can you explain?
<br class="">
<br class="">
Steven
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On 26 May 2016, at 19:28,
Dave McIlhagga <<a class="moz-txt-link-abbreviated" href="mailto:dmcilhagga@mapsherpa.com">dmcilhagga@mapsherpa.com</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:dmcilhagga@mapsherpa.com"><mailto:dmcilhagga@mapsherpa.com></a>
<br class="">
<blockquote type="cite" class="">wrote:
<br class="">
</blockquote>
<br class="">
Steven,
<br class="">
<br class="">
I couldn’t agree more — this committee has
probably the single
<br class="">
biggest impact of any OSGeo activities on the
Foundation,
<br class="">
particularly from a financial perspective.
<br class="">
<br class="">
If we’re going to look at this — I think we should
look at the whole
<br class="">
picture of how we do things here. It has long been
a concern of mine
<br class="">
that the most important decision that OSGeo makes
every year is
<br class="">
effectively delegated away by the board who is the
elected group in
<br class="">
fact charged with representing the interests of
the membership.
<br class="">
<br class="">
The number 1 change I would recommend is that this
committee provide
<br class="">
all of the logistical services to review
conference options, help
<br class="">
local organizing committees, and all of the other
leg work a
<br class="">
committee exists to handle. But the over-riding
guidance of what the
<br class="">
international FOSS4G annual conference should be
all about, how OSGeo
<br class="">
decides where/how conference is hosted and run
each year, should
<br class="">
really be in the domain of the Board.
<br class="">
<br class="">
This group can help that process out extensively
given the breadth of
<br class="">
experience of the members. If it makes sense to
continue the RFP
<br class="">
process as we have in the past (which I’m not
convinced of) - then
<br class="">
this committee can manage that whole process, but
I don’t believe we
<br class="">
should be casting the votes. It’s too important a
decision for the
<br class="">
Foundation. Providing experience, perspective, and
commentary on
<br class="">
proposals to the board is reasonable — but I feel
it’s time that the
<br class="">
board take back this decision making authority.
<br class="">
<br class="">
Technically, the board does approve the decision
of the committee —
<br class="">
but this has never been overturned, and in my
opinion, the year we
<br class="">
failed in China was a direct outcome of this
process - I don’t think
<br class="">
we’ve really learned our lesson from that yet.
<br class="">
<br class="">
Dave
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On May 26, 2016, at 12:40
PM, Steven Feldman <<a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:shfeldman@gmail.com"><mailto:shfeldman@gmail.com></a>
<br class="">
<blockquote type="cite" class="">wrote:
<br class="">
</blockquote>
<br class="">
Andrea
<br class="">
<br class="">
Definitely not my intention to indicate support
no process.
<br class="">
<br class="">
Conference Committee is imho second most
important committee of
<br class="">
OSGeo, my view is it should have process for
selection, clear bounds
<br class="">
of authority and expectations on members.
<br class="">
<br class="">
Would be good to hear views from a broad cross
section of current
<br class="">
and past members
<br class="">
<br class="">
Steven
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On 25 May 2016, at
22:01, Andrea Ross <<a class="moz-txt-link-abbreviated" href="mailto:andrea.ross@eclipse.org">andrea.ross@eclipse.org</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:andrea.ross@eclipse.org"><mailto:andrea.ross@eclipse.org></a>
<br class="">
<blockquote type="cite" class="">wrote:
<br class="">
</blockquote>
<br class="">
Steven, All
<br class="">
<br class="">
Are you stating no process or criteria because
you believe that's
<br class="">
best, or to draw attention to it being a very
bad idea? I can't
<br class="">
tell through email. :-)
<br class="">
<br class="">
Andrea
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On 25/05/16 13:08,
Steven Feldman wrote:
<br class="">
I thought that had been agreed by nearly
everyone who commented
<br class="">
although there may have been one or two
objections including mine.
<br class="">
<br class="">
It seems that if you want to join conference
committee there is no
<br class="">
process or criteria, you say you want to
join and then you can.
<br class="">
Quite what happens when you go silent I
don't know? Membership
<br class="">
allows vote for location of FOSS4G which
raises question about
<br class="">
potential "packing" of vote but so far we've
not had a problem so
<br class="">
maybe not an issue.
<br class="">
<br class="">
If Maxi wants to be a member, I guess he is
one. @Maxi, feel free
<br class="">
to add yourself to the current members list
<br class="">
<br class="">
Steven
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">On 24 May 2016, at
15:19, Venkatesh Raghavan
<br class="">
<
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:venka.osgeo@gmail.com">venka.osgeo@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:venka.osgeo@gmail.com"><mailto:venka.osgeo@gmail.com></a>
<br class="">
<blockquote type="cite" class="">wrote:
<br class="">
</blockquote>
<br class="">
On 2016/05/24 20:13, Cameron Shorter
wrote:
<br class="">
Conference Committee,
<br class="">
I'd like to propose that we invite
Andrea Ross to join the OSGeo
<br class="">
Conference Committee.
<br class="">
<br class="">
</blockquote>
Firstly, we need to decide on the request
from Maxi to join
<br class="">
the conference committee which was
seconded by me.
<br class="">
<br class="">
Venka
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">+1 from me,
Cameron Shorter.
<br class="">
<br class="">
My reasoning is that Andrea has a lot of
experience running
<br class="">
conferences,
<br class="">
especially through his involvement with
LocationTech, and there are
<br class="">
synergies that could be gained by
aligning OSGeo and LocationTech
<br class="">
effectively.
<br class="">
<br class="">
I note that there have been concerns
aired previously about
<br class="">
LocationTech
<br class="">
competing to take over OSGeo's flagship
FOSS4G event. I'm of the
<br class="">
opinion
<br class="">
that we should be mindful of this, but
we should discuss the options
<br class="">
openly and I believe we can find a
solution favourable for all. An
<br class="">
effective way to support this
conversation is to invite Andrea
<br class="">
to be one
<br class="">
vote among our conference committee.
<br class="">
<br class="">
Warm regards, Cameron
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On 24/05/2016
6:31 am, Andrea Ross wrote:
<br class="">
Dear Steven, & Everyone
<br class="">
<br class="">
I've not been invited to the
conference committee, but I will be in
<br class="">
Bonn, and I'm always glad to
chat/meet.
<br class="">
<br class="">
Kind regards,
<br class="">
<br class="">
Andrea
<br class="">
<br class="">
On May 22, 2016 3:04:03 AM EDT, Steven
Feldman
<br class="">
<
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:shfeldman@gmail.com"><mailto:shfeldman@gmail.com></a>
<br class="">
<blockquote type="cite" class="">
<br class="">
</blockquote>
wrote:
<br class="">
<br class="">
Who is going to be in Bonn for FOSS4G?
<br class="">
<br class="">
It's an opportunity for the Conference
Committee and interested
<br class="">
people to meet face to face, we could
discuss some of the topics on
<br class="">
the 'outstanding
<br class="">
list'
<br class="">
<br class="">
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Conference_Committee_2016_Priorities">http://wiki.osgeo.org/wiki/Conference_Committee_2016_Priorities</a>
<br class="">
<br class="">
<a class="moz-txt-link-rfc2396E" href="http://wiki.osgeo.org/wiki/Conference_Committee_2016_Priorities"><http://wiki.osgeo.org/wiki/Conference_Committee_2016_Priorities></a>
<br class="">
<br class="">
and we could start preparing the call
for 2018
<br class="">
<br class="">
Anyone interested?
<br class="">
<br class="">
Steven
<br class="">
<br class="">
<br class="">
------------------------------------------------------------------------
<br class="">
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:Conference_dev@lists.osgeo.org"><mailto:Conference_dev@lists.osgeo.org></a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
<br class="">
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
</blockquote>
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-rfc2396E" href="mailto:Conference_dev@lists.osgeo.org"><mailto:Conference_dev@lists.osgeo.org></a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Conference_dev@lists.osgeo.org"><mailto:Conference_dev@lists.osgeo.org></a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Conference_dev@lists.osgeo.org"><mailto:Conference_dev@lists.osgeo.org></a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Conference_dev@lists.osgeo.org"><mailto:Conference_dev@lists.osgeo.org></a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
</blockquote>
</blockquote>
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________
<br class="">
Board mailing list
<br class="">
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a>
<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
</blockquote>
<br class="">
--
<br class="">
Cameron Shorter,
<br class="">
Software and Data Solutions Manager
<br class="">
LISAsoft
<br class="">
Suite 112, Jones Bay Wharf,
<br class="">
26 - 32 Pirrama Rd, Pyrmont NSW 2009
<br class="">
<br class="">
P +61 2 9009 5000, W
<br class="">
<a class="moz-txt-link-abbreviated" href="http://www.lisasoft.com/">www.lisasoft.com</a>, F +61 2 9009 5099
<br class="">
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
_______________________________________________
<br class="">
Board mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a>
<br class="">
</blockquote>
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
<br class="">
Helena Mitasova
<br class="">
Professor at the Department of Marine,
<br class="">
Earth, and Atmospheric Sciences
<br class="">
and Center for Geospatial Analytics
<br class="">
North Carolina State University
<br class="">
Raleigh, NC 27695-8208
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:hmitaso@ncsu.edu">hmitaso@ncsu.edu</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://geospatial.ncsu.edu/osgeorel/publications.html">http://geospatial.ncsu.edu/osgeorel/publications.html</a>
<br class="">
<br class="">
"All electronic mail messages in connection with State
business which are sent to or received by this account are
subject to the NC Public Records Law and may be disclosed to
third parties.”
<br class="">
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
<br class="">
</blockquote>
<br class="">
_______________________________________________
<br class="">
Conference_dev mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br class="">
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W <a class="moz-txt-link-abbreviated" href="http://www.lisasoft.com/">www.lisasoft.com</a>, F +61 2 9009 5099</pre>
</div>
_______________________________________________<br class="">Board mailing list<br class=""><a href="mailto:Board@lists.osgeo.org" class="">Board@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/board</div></blockquote></div><br class=""></body></html>