[MCH Team:Info] [Content] Team Content invite

[Noor]

I can attend the BBB meeting then (for whatever time frame you need, just
ping me on IRC), but anything I need to know will have to be messaged via
text chat.

I think the idea of "Team:Info offering hands-on help to other teams" is
more for when other teams don't have the time or energy or writing
experience to write a blog post. If Team:Content or any other teams want to
do the writing work themselves, I'll do the proofreading and any help with
formatting for the blog. Other than spelling or formatting errors, I'm
going to work with the author(s) together and come to a consensus.

I may also suggest toning down some things, but I have no intention of
coming off as a mealy-mouthed corporate sales advisor. It's a balance I'm
struggling with as well.

Noor

On Sun, Nov 1, 2020 at 8:51 PM Walter van Holst <walter.van.holst at xs4all.nl>
wrote:

> On 01-11-2020 19:41, Arnout Engelen via Content wrote:
> > Hi Aschwin,
> >
> > Thanks for reaching out!
>
> What is this reaching out? What do you mean by it? Let's not copy the
> meaningless Silicon Valley lingo, shall we?
>
> > As discussed with Claudia last month, our proposal would be that you
> > can collaborate on your posts as a team in wordpress, and once one is
> > ready you can ping Team:Info for a final review and publishing. This
> > way we can coordinate the blog with other communications. We would
> > also like to provide hands-on help with actually writing the blog
> > posts for those teams that would appreciate that - the volunteer who
> > is interested in that isn't onboarded just yet, though.
> >
> > Would that work for you? I think this could be pretty quick and light
> > - if it turns out to be too heavy then of course we can always
> > course-correct.
>
> My preference for the process is that Team:Info's editorial influence is
> limited to linguistic issues (you have a native speaker on your end, so
> do we) and flagging up blog posts that really would not add to the
> event. As well as that blogposts are personal. Team:Content is a bunch
> of unruly personalities, as it should be, and having that shine through
> in the blog posts is a feature, not a bug.
>
> So yes, you get to give a final go/no-go on any posts, but there'll be
> no real substantive input on the posts unless the author allows for that.
>
> Having worked with professional editors *as well as* corporate
> mealy-mouthed communications advisors, I prefer the former category and
> would like you to take on that particular mantle.
>
> So yes, the lighter the process, the better.
>
> Regards,
>
>  Walter
> _______________________________________________
> Info mailing list
> Info at lists.mch2021.org
> https://lists.mch2021.org/mailman/listinfo/info
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mch2021.org/pipermail/info/attachments/20201101/e3bc9da8/attachment.html>