[FOSS4G-Oceania] FOSS4G-Oceania Digest, Vol 10, Issue 5
Emma Hain
emmahain at gmail.com
Fri Mar 15 22:26:59 PDT 2019
Hi All
If there is someone else who wants to chair the program, then I would rather support them then co-chair. I would rather be an apprentice.
Emma Hain
> On 15 Mar 2019, at 8:34 am, foss4g-oceania-request at lists.osgeo.org wrote:
>
> Send FOSS4G-Oceania mailing list submissions to
> foss4g-oceania at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
> or, via email, send a message with subject or body 'help' to
> foss4g-oceania-request at lists.osgeo.org
>
> You can reach the person managing the list at
> foss4g-oceania-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of FOSS4G-Oceania digest..."
>
>
> Today's Topics:
>
> 1. Re: FOSS4G SotM Oceania 2019 Committee Roles (Alex Leith)
> 2. Re: FOSS4G SotM Oceania 2019 Committee Roles (adam steer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 15 Mar 2019 09:07:01 +1100
> From: Alex Leith <alexgleith at gmail.com>
> To: adam steer <adam.d.steer at gmail.com>
> Cc: foss4g-oceania <foss4g-oceania at lists.osgeo.org>, Cameron Shorter
> <cameron.shorter at gmail.com>, Emma Hain <emmahain at gmail.com>
> Subject: Re: [FOSS4G-Oceania] FOSS4G SotM Oceania 2019 Committee Roles
> Message-ID:
> <CAEvGJspu5vhqGSPcPaCUs+4NrVDEXFoN9pAUuA9zZeqmNjHr6g at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Oh, I'm happy not to chair and also happy not to co-chair!
>
> I don't think we should really have formalities around co-chairs... the
> whole point of the chair is having an individual take responsibility and
> ownership of a task.
>
> So consider my offer to be one of support!
>
>> On Fri, 15 Mar 2019 at 09:04 adam steer <adam.d.steer at gmail.com> wrote:
>>
>> hey all
>>
>> Emma Hain also expressed interest in co-chairing (on both the gdrive doc
>> and off-list) - perhaps I should have written that into the proposal! And
>> Alex - of course your input is welcome and given the risks identified with
>> my ‘chairdom’ I think you should also propose to chair.
>>
>> to follow due process; if both Alex and Emma have a strong interest as
>> committee co-chair, we should gather proposals and vote as a community.
>>
>> we didn’t really define what should happen if there are multiple interests
>> in co-chairing - I think we just assumed that a chair would handpick a team
>> more or less undemocratically (which is also fine) - but I can be, and
>> often am, wrong!
>>
>> And I agree with Cameron. I’d hoped to express that I’d aim to develop the
>> programme with input from everyone (including 2018’s successful model and
>> feedback from it); and as chair, the key roles are herding the cats and
>> picking up slack (with respect to the fact that everyone is a volunteer
>> here, and everyone has busy other lives).
>>
>> Cheers
>>
>>> On Fri, 15 Mar 2019 at 08:38, Alex Leith <alexgleith at gmail.com> wrote:
>>>
>>> Hey Cameron
>>>
>>> Absolutely agree. From the do-ocracy that we have all experienced last
>>> year, to the principles of 'disagree and commit
>>> <https://en.wikipedia.org/wiki/Disagree_and_commit>' when decisions
>>> don't go one's way, I think that we know that we can make better decisions
>>> and get a lot done by working together.
>>>
>>> Cheers,
>>>
>>> On Fri, 15 Mar 2019 at 08:30 Cameron Shorter <cameron.shorter at gmail.com>
>>> wrote:
>>>
>>>> Great to see people step up, and as I'm mentioned numerous times before,
>>>> I'm super impressed with the quality of people in our team.
>>>>
>>>> Some thoughts on the subtle differences between leaders/despots/managers.
>>>> Great leaders are really good at capturing the collective opinion of the
>>>> team, helping each member in the team shine and reach their personal goals
>>>> and potential. It often involves creating space for people to step up. It
>>>> sometimes involves stepping back from an opinion you might have. It also
>>>> involves stepping in and taking up the slack and doing the dirty work when
>>>> no one steps up.
>>>>
>>>> Adam, Alex, I see these characteristics in you both (as I do with the
>>>> rest of the team), and expect you would make use of these principles?
>>>>
>>>>> On Fri, 15 Mar 2019 at 08:19, Alex Leith <alexgleith at gmail.com> wrote:
>>>>>
>>>>> Hey Adam
>>>>>
>>>>> I'm happy to co-chair/sub-chair with you, if you take the Program Lead
>>>>> role on.
>>>>>
>>>>> I've got some strong opinions about the format. I think what we did
>>>>> last year worked really well, aside from the panel session, which was good,
>>>>> but was the weakest link.
>>>>>
>>>>> I think the key components of the program are:
>>>>>
>>>>> 1. Keynotes - we did well here last year, so let's try to do at
>>>>> least as good this year!
>>>>> 2. Program - Sessionize sounds like the way to go regarding
>>>>> logistics, and hopefully, again, we have a strong pool of talks to choose
>>>>> from.
>>>>> 3. Format - again, my opinion, but the format
>>>>> <https://docs.google.com/spreadsheets/d/1tmqjTjK2w6qmbpGJo9_zZVkduPAYU4qTJm2x7K-TY7Q/edit>
>>>>> worked well last year. If we can work out how to make the panel session
>>>>> shine, that will round it off!
>>>>>
>>>>> Also a note that Stephen Lead did an incredible job organising the
>>>>> lightning talks, and I'd suggest we approach him again for this year. He'll
>>>>> probably be ok to be involved from an earlier point too.
>>>>>
>>>>> Cheers,
>>>>>
>>>>>> On Fri, 15 Mar 2019 at 08:11 adam steer <adam.d.steer at gmail.com> wrote:
>>>>>>
>>>>>> Hi Daniel
>>>>>>
>>>>>> Apologies for a slow response, I’ve been turning this over a lot.
>>>>>> ...and thanks Ed for the great example of what to write! I add one extra
>>>>>> item - ‘risks’.
>>>>>>
>>>>>> *Role*
>>>>>> I’ve self-nominated to chair the program committee
>>>>>>
>>>>>> *Why*
>>>>>> I’m passionate about making OSGeo SotM Oceania different from ‘another
>>>>>> industry/science meeting’. The 2018 event is a fantastic base to build on;
>>>>>> and will be a hard act to follow. I don’t have any preset ideas about what
>>>>>> a program should look like; aside from some loose concepts around embracing
>>>>>> the whole community as much as possible, open-mindedness, raising new
>>>>>> voices, trying to avoid default options where we can, being open to how the
>>>>>> world changes between last time and now; and keeping that heady mix of
>>>>>> technical excellence and community-mindedness bubbling away!
>>>>>>
>>>>>> The programme committee also has a great set of resources (including
>>>>>> everyone reading this right now) to help figure out what will work and what
>>>>>> won’t; as well as seeing what boundaries we can push to engage people in
>>>>>> new ways (if we need to).
>>>>>>
>>>>>> My aim as chair is to more or less draw on all those resources; and do
>>>>>> the legwork which helps other people shine. Help keep barriers to
>>>>>> participation as low as possible, keep the programme committees life sane,
>>>>>> and support the delivery of a conference that is a success - which in turn
>>>>>> supports the main game: promoting, strengthening and building the open
>>>>>> geospatial community in Oceania.
>>>>>>
>>>>>> *Responsibilities I’m uncertain about*
>>>>>> From my view the responsibilities of the program chair seem pretty
>>>>>> clear - one of which is to delegate as much as possible to, for example,
>>>>>> the good mojo/community day team or the academic subcommittee (if one
>>>>>> exists); and another of which is to gather as much support as possible for
>>>>>> putting the actual program together. There are heaps of uncertainties about
>>>>>> how it will all work right at this point, there is no clear idea of what a
>>>>>> program might look like - we’ll work it out together!
>>>>>>
>>>>>> *Risks*
>>>>>> I’m waiting to hear about a job move which would see me wind my OSGeo
>>>>>> Oceania activities back a lot after about May 2019. I should know this
>>>>>> week, but may not find out until later in the month. In the event that
>>>>>> happens; I’ll work with the LOC to replace myself/hand over ASAP.
>>>>>>
>>>>>> …or another move which would do the opposite and land me right in
>>>>>> ground zero for 2019. So uncertainty abounds.
>>>>>>
>>>>>> With that in mind it’d be awesome to have someone nominate themselves
>>>>>> as committee co-chair; which there has been some out-of-list discussion
>>>>>> about already. From what I saw in 2018 there’s definitely enough work to
>>>>>> share around.
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> --
>>>>>> Dr. Adam Steer
>>>>>> http://spatialised.net
>>>>>> https://www.researchgate.net/profile/Adam_Steer
>>>>>> http://au.linkedin.com/in/adamsteer
>>>>>> http://orcid.org/0000-0003-0046-7236
>>>>>> +61 427 091 712 <+61%20427%20091%20712>
>>>>>> skype: adam.d.steer
>>>>>> tweet: @adamdsteer
>>>>>> _______________________________________________
>>>>>> FOSS4G-Oceania mailing list
>>>>>> FOSS4G-Oceania at lists.osgeo.org
>>>>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>>>>
>>>>> --
>>>>>
>>>>> Alex Leith
>>>>> 0419 189 050
>>>>> _______________________________________________
>>>>> FOSS4G-Oceania mailing list
>>>>> FOSS4G-Oceania at lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>>>
>>>>
>>>>
>>>> --
>>>> Cameron Shorter
>>>> Technology Demystifier
>>>> Open Technologies and Geospatial Consultant
>>>>
>>>> M +61 (0) 419 142 254 <+61%20419%20142%20254>
>>>>
>>>>
>>>>
>>>> --
>>>
>>> Alex Leith
>>> 0419 189 050
>>>
>>
>>
>> --
>> Dr. Adam Steer
>> http://spatialised.net
>> https://www.researchgate.net/profile/Adam_Steer
>> http://au.linkedin.com/in/adamsteer
>> http://orcid.org/0000-0003-0046-7236
>> +61 427 091 712 <+61%20427%20091%20712>
>> skype: adam.d.steer
>> tweet: @adamdsteer
>>
> --
>
> Alex Leith
> 0419 189 050
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/foss4g-oceania/attachments/20190315/08a029be/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 15 Mar 2019 09:34:40 +1100
> From: adam steer <adam.d.steer at gmail.com>
> To: Alex Leith <alexgleith at gmail.com>
> Cc: foss4g-oceania <foss4g-oceania at lists.osgeo.org>, Cameron Shorter
> <cameron.shorter at gmail.com>, Emma Hain <emmahain at gmail.com>
> Subject: Re: [FOSS4G-Oceania] FOSS4G SotM Oceania 2019 Committee Roles
> Message-ID:
> <CAFORoyiQ8zgvRzkvYOUH-X0dWqkbUOCiaCTvx7MOi8bi5iVCoQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> thanks Alex, I see it’s something you’re super passionate about, and as I
> mentioned 2018 set a high bar - hence the suggestion to put a hat in! It’ll
> be great to have your input however it rolls.
>
>
>
>
>
>
>
>
>
>
>
>> On Fri, 15 Mar 2019 at 09:07, Alex Leith <alexgleith at gmail.com> wrote:
>>
>> Oh, I'm happy not to chair and also happy not to co-chair!
>>
>> I don't think we should really have formalities around co-chairs... the
>> whole point of the chair is having an individual take responsibility and
>> ownership of a task.
>>
>> So consider my offer to be one of support!
>>
>>> On Fri, 15 Mar 2019 at 09:04 adam steer <adam.d.steer at gmail.com> wrote:
>>>
>>> hey all
>>>
>>> Emma Hain also expressed interest in co-chairing (on both the gdrive doc
>>> and off-list) - perhaps I should have written that into the proposal! And
>>> Alex - of course your input is welcome and given the risks identified with
>>> my ‘chairdom’ I think you should also propose to chair.
>>>
>>> to follow due process; if both Alex and Emma have a strong interest as
>>> committee co-chair, we should gather proposals and vote as a community.
>>>
>>> we didn’t really define what should happen if there are multiple
>>> interests in co-chairing - I think we just assumed that a chair would
>>> handpick a team more or less undemocratically (which is also fine) - but I
>>> can be, and often am, wrong!
>>>
>>> And I agree with Cameron. I’d hoped to express that I’d aim to develop
>>> the programme with input from everyone (including 2018’s successful model
>>> and feedback from it); and as chair, the key roles are herding the cats and
>>> picking up slack (with respect to the fact that everyone is a volunteer
>>> here, and everyone has busy other lives).
>>>
>>> Cheers
>>>
>>>> On Fri, 15 Mar 2019 at 08:38, Alex Leith <alexgleith at gmail.com> wrote:
>>>>
>>>> Hey Cameron
>>>>
>>>> Absolutely agree. From the do-ocracy that we have all experienced last
>>>> year, to the principles of 'disagree and commit
>>>> <https://en.wikipedia.org/wiki/Disagree_and_commit>' when decisions
>>>> don't go one's way, I think that we know that we can make better decisions
>>>> and get a lot done by working together.
>>>>
>>>> Cheers,
>>>>
>>>> On Fri, 15 Mar 2019 at 08:30 Cameron Shorter <cameron.shorter at gmail.com>
>>>> wrote:
>>>>
>>>>> Great to see people step up, and as I'm mentioned numerous times
>>>>> before, I'm super impressed with the quality of people in our team.
>>>>>
>>>>> Some thoughts on the subtle differences between
>>>>> leaders/despots/managers.
>>>>> Great leaders are really good at capturing the collective opinion of
>>>>> the team, helping each member in the team shine and reach their
>>>>> personal goals and potential. It often involves creating space for people
>>>>> to step up. It sometimes involves stepping back from an opinion you might
>>>>> have. It also involves stepping in and taking up the slack and doing the
>>>>> dirty work when no one steps up.
>>>>>
>>>>> Adam, Alex, I see these characteristics in you both (as I do with the
>>>>> rest of the team), and expect you would make use of these principles?
>>>>>
>>>>>> On Fri, 15 Mar 2019 at 08:19, Alex Leith <alexgleith at gmail.com> wrote:
>>>>>>
>>>>>> Hey Adam
>>>>>>
>>>>>> I'm happy to co-chair/sub-chair with you, if you take the Program Lead
>>>>>> role on.
>>>>>>
>>>>>> I've got some strong opinions about the format. I think what we did
>>>>>> last year worked really well, aside from the panel session, which was good,
>>>>>> but was the weakest link.
>>>>>>
>>>>>> I think the key components of the program are:
>>>>>>
>>>>>> 1. Keynotes - we did well here last year, so let's try to do at
>>>>>> least as good this year!
>>>>>> 2. Program - Sessionize sounds like the way to go regarding
>>>>>> logistics, and hopefully, again, we have a strong pool of talks to choose
>>>>>> from.
>>>>>> 3. Format - again, my opinion, but the format
>>>>>> <https://docs.google.com/spreadsheets/d/1tmqjTjK2w6qmbpGJo9_zZVkduPAYU4qTJm2x7K-TY7Q/edit>
>>>>>> worked well last year. If we can work out how to make the panel session
>>>>>> shine, that will round it off!
>>>>>>
>>>>>> Also a note that Stephen Lead did an incredible job organising the
>>>>>> lightning talks, and I'd suggest we approach him again for this year. He'll
>>>>>> probably be ok to be involved from an earlier point too.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> On Fri, 15 Mar 2019 at 08:11 adam steer <adam.d.steer at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Daniel
>>>>>>>
>>>>>>> Apologies for a slow response, I’ve been turning this over a lot.
>>>>>>> ...and thanks Ed for the great example of what to write! I add one extra
>>>>>>> item - ‘risks’.
>>>>>>>
>>>>>>> *Role*
>>>>>>> I’ve self-nominated to chair the program committee
>>>>>>>
>>>>>>> *Why*
>>>>>>> I’m passionate about making OSGeo SotM Oceania different from
>>>>>>> ‘another industry/science meeting’. The 2018 event is a fantastic base to
>>>>>>> build on; and will be a hard act to follow. I don’t have any preset ideas
>>>>>>> about what a program should look like; aside from some loose concepts
>>>>>>> around embracing the whole community as much as possible, open-mindedness,
>>>>>>> raising new voices, trying to avoid default options where we can, being
>>>>>>> open to how the world changes between last time and now; and keeping that
>>>>>>> heady mix of technical excellence and community-mindedness bubbling away!
>>>>>>>
>>>>>>> The programme committee also has a great set of resources (including
>>>>>>> everyone reading this right now) to help figure out what will work and what
>>>>>>> won’t; as well as seeing what boundaries we can push to engage people in
>>>>>>> new ways (if we need to).
>>>>>>>
>>>>>>> My aim as chair is to more or less draw on all those resources; and
>>>>>>> do the legwork which helps other people shine. Help keep barriers to
>>>>>>> participation as low as possible, keep the programme committees life sane,
>>>>>>> and support the delivery of a conference that is a success - which in turn
>>>>>>> supports the main game: promoting, strengthening and building the open
>>>>>>> geospatial community in Oceania.
>>>>>>>
>>>>>>> *Responsibilities I’m uncertain about*
>>>>>>> From my view the responsibilities of the program chair seem pretty
>>>>>>> clear - one of which is to delegate as much as possible to, for example,
>>>>>>> the good mojo/community day team or the academic subcommittee (if one
>>>>>>> exists); and another of which is to gather as much support as possible for
>>>>>>> putting the actual program together. There are heaps of uncertainties about
>>>>>>> how it will all work right at this point, there is no clear idea of what a
>>>>>>> program might look like - we’ll work it out together!
>>>>>>>
>>>>>>> *Risks*
>>>>>>> I’m waiting to hear about a job move which would see me wind my OSGeo
>>>>>>> Oceania activities back a lot after about May 2019. I should know this
>>>>>>> week, but may not find out until later in the month. In the event that
>>>>>>> happens; I’ll work with the LOC to replace myself/hand over ASAP.
>>>>>>>
>>>>>>> …or another move which would do the opposite and land me right in
>>>>>>> ground zero for 2019. So uncertainty abounds.
>>>>>>>
>>>>>>> With that in mind it’d be awesome to have someone nominate themselves
>>>>>>> as committee co-chair; which there has been some out-of-list discussion
>>>>>>> about already. From what I saw in 2018 there’s definitely enough work to
>>>>>>> share around.
>>>>>>>
>>>>>>> Cheers
>>>>>>>
>>>>>>> --
>>>>>>> Dr. Adam Steer
>>>>>>> http://spatialised.net
>>>>>>> https://www.researchgate.net/profile/Adam_Steer
>>>>>>> http://au.linkedin.com/in/adamsteer
>>>>>>> http://orcid.org/0000-0003-0046-7236
>>>>>>> +61 427 091 712 <+61%20427%20091%20712>
>>>>>>> skype: adam.d.steer
>>>>>>> tweet: @adamdsteer
>>>>>>> _______________________________________________
>>>>>>> FOSS4G-Oceania mailing list
>>>>>>> FOSS4G-Oceania at lists.osgeo.org
>>>>>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>>>>>
>>>>>> --
>>>>>>
>>>>>> Alex Leith
>>>>>> 0419 189 050
>>>>>> _______________________________________________
>>>>>> FOSS4G-Oceania mailing list
>>>>>> FOSS4G-Oceania at lists.osgeo.org
>>>>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cameron Shorter
>>>>> Technology Demystifier
>>>>> Open Technologies and Geospatial Consultant
>>>>>
>>>>> M +61 (0) 419 142 254 <+61%20419%20142%20254>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>
>>>> Alex Leith
>>>> 0419 189 050
>>>>
>>>
>>>
>>> --
>>> Dr. Adam Steer
>>> http://spatialised.net
>>> https://www.researchgate.net/profile/Adam_Steer
>>> http://au.linkedin.com/in/adamsteer
>>> http://orcid.org/0000-0003-0046-7236
>>> +61 427 091 712 <+61%20427%20091%20712>
>>> skype: adam.d.steer
>>> tweet: @adamdsteer
>>>
>> --
>>
>> Alex Leith
>> 0419 189 050
>>
>
>
> --
> Dr. Adam Steer
> http://spatialised.net
> https://www.researchgate.net/profile/Adam_Steer
> http://au.linkedin.com/in/adamsteer
> http://orcid.org/0000-0003-0046-7236
> +61 427 091 712
> skype: adam.d.steer
> tweet: @adamdsteer
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/foss4g-oceania/attachments/20190315/ac72a011/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> FOSS4G-Oceania mailing list
> FOSS4G-Oceania at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>
>
> ------------------------------
>
> End of FOSS4G-Oceania Digest, Vol 10, Issue 5
> *********************************************
More information about the FOSS4G-Oceania
mailing list