[FOSS4G-Oceania] Call for writers

[John Bryant]

Thanks Adam.

A couple of quick thoughts on how this committee can help in general:

*Eyeballs on the website*. If we're ramping up our outreach into the
broader community, we can probably expect more people to be coming to our
website, and we need it to clearly communicate what they know. If you have
observations, or even better, actionable suggestions on how to improve the
website, please shout them out.

*Generate ideas on messaging for our media pipeline*. Check out this new media
pipeline sheet
<https://docs.google.com/spreadsheets/d/1047xhr8aUdaESgvrD-1dFd4Awqh4DgBRy_0A7am7Jzg/edit#gid=0>,
the idea here is to plan ahead and be proactive about our messaging and
PR... if there are things to add, please do. Community Day stuff might be
something worth putting in here, for example. Some messages might be more
timing-sensitive than others, but if we take this approach, we can schedule
less timing-sensitive messages in between the others. With a pipeline in
place, it will become easier to plan ahead and share the load, I think.
Feedback on this approach very much welcome.

Cheers
John

On Sun, 19 Aug 2018 at 18:28, adam steer <adam.d.steer at gmail.com> wrote:

> Hey all, happy to help also.
>
> I'll be out of range tomorrow though.
>
> Cheers
>
> On Sun., 19 Aug. 2018, 17:10 John Bryant, <johnwbryant at gmail.com> wrote:
>
>> Thanks Cameron & Ed, will be great to get the extra input.
>>
>> Ed, 3pm tomorrow should be fine for me, catch you then. If anyone else
>> want to join that convo, let us know and we'll run a Google Hangout.
>>
>> If anyone else wants to just put their hand up for some occasional
>> content writing or editing, I'm sure we can use that too... just say the
>> word and we'll make a list of contributors.
>>
>> Thanks!
>> John
>>
>>
>>
>> On Sun, 19 Aug 2018 at 12:04, Edoardo Neerhut <ed at mapillary.com> wrote:
>>
>>> I put my hand up for content writing but have been slack.
>>>
>>> It would be great to have a chat about this tomorrow to kick it off. Any
>>> interested parties can discuss a good flow for the pipeline, our general
>>> tone, and the channels we should be broadcasting on.
>>>
>>> Aware most of this has been solved already, but would be helpful to get
>>> up to speed.
>>>
>>> If this sounds alright, 3pm tomorrow?
>>>
>>> On Sat, 18 Aug 2018 at 09:38, Cameron Shorter <cameron.shorter at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On 17/8/18 12:19 pm, John Bryant wrote:
>>>> > Clearly we're heading into a phase where we need to be increasing our
>>>> > communications... but I'm feeling pretty swamped with writing news
>>>> > items, web page content, tweets, emails, etc... can I call out for
>>>> > some help with this aspect? Would be great to have a bit of a crew of
>>>> > writers to tag team this stuff, and help generate content for the
>>>> > media pipeline.
>>>> John, I'm fairly time poor, but should usually be able to help for an
>>>> hour or two a week with writing or reviewing (typically over the
>>>> weekend). Press release type material is probably where I can add most
>>>> value. Feel free to reach out to me if you have something specific you
>>>> want help with.
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Cameron Shorter
>>>> Technology Demystifier
>>>> Open Technologies and Geospatial Consultant
>>>>
>>>> M +61 (0) 419 142 254
>>>>
>>>> _______________________________________________
>>>> FOSS4G-Oceania mailing list
>>>> FOSS4G-Oceania at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>>
>>> _______________________________________________
>>> FOSS4G-Oceania mailing list
>>> FOSS4G-Oceania at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>>
>> _______________________________________________
>> FOSS4G-Oceania mailing list
>> FOSS4G-Oceania at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/foss4g-oceania
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/foss4g-oceania/attachments/20180820/f7dd0722/attachment.html>