Re: Community management of main fd.io website
St Leger, Jim
I haven’t been directly involved in this discussion. But my observations are that there is an effort in FD.io to improve some of the content and documentation (which is always commendable) but also some level of frustration with how to get that content updated and published on the website and/or wiki pages.
My past experience both here and in other projects has me conclude:
- Use a marketing team for the “pretty” public facing content. This would be all the fd.io facing material. FD.io has a marketing committee that should own and drive that effort. They should also be working with the broader LFN marketing advisory committee for support, ideas, etc.
- Use the technical community for technical content that predominantly shows up on the wiki, developer targeted pages. If req’d the FD.io TSC could ask the LFN TAC for help (though I don’t suspect that’s needed.)
I don’t know why we’d ever want to get the communities technical experts working on non-wiki tech pages. And if there’s some gaps wrt support from the marketing team then perhaps the topic should be brought up there and addressed head-on.
Hope this perspective helps a bit. Let me know what “we already tried that” or other barriers exist. Then let’s get the right folks to step up, own them, and resolve them. Our tech experts can then focus on creating the best technical documentation and not worry about website layout, etc.
P.S. I’d join the discussion tomorrow, but I’ll be in a plane.
From: main@... [mailto:main@...] On Behalf Of Edward Warnicke
Sent: Wednesday, June 5, 2019 11:00 AM
To: Kinsella, Ray <ray.kinsella@...>
Subject: Re: [FD.io] Community management of main fd.io website
Totally. There was some discussion after you left about whether to take a vote or wait a week. The consensus was that you had seemed very supportive, and so we felt comfortable proceeding.
Our intention was not to preclude any further discussion you think might be productive. Lets talk about it tomorrow :)
On Wed, Jun 5, 2019 at 12:13 PM Kinsella, Ray <ray.kinsella@...> wrote: