a fedora council blog?

[Stephen John Smoogen]

On 16 April 2015 at 19:04, White, Langdon <langdon at fedoraproject.org> wrote:

>
>
>
> 2) what is the infra difficulty?
> a) do the maintainers have sufficient tech expertise to do the work? What
> is the impact of an outage? What level of uptime is required?
> b) how much content are we talking?
> c) how much money is available to spend?
>
>
Infrastructures difficulty is that if we run a service, we are expected by
its consumers to be subject matter experts in everything from layout and
plugins to account moderation.  We are not experts in PHP or in wordpress
and  by the time we have gotten to know it, we are being asked to move to
the next version of wordpress which seems to be completely different in
what it wants to do. This may be better in current versions, but I don't
know. [While this is core part of systems administration, we have ~100
changing services which we are supposed to be also subject matter experts
at the same time. Wordpress was considered to be something that would be
better run by people who do it day and day out versus when we get to it.]

Outages for blogs usually only affect services which tie into the blog...
which in the past ended up being something that another team had put in
place that we were not aware of. Usually nothing software production
related but that does not make it any easier for the ambassadors at a show
who can't use getfedora or start for some reason linked to the down
service. Levels of uptime are not something we have defined that I know of.

The amount of content is probably not going to be much. In the previous
blogs the majority of the content was I believe to be found to be comment
spam or FEDORA SUCKS USE XYZ spam.

Infrastructure has no funding for running a service outside of
infrastructure. Any such funding would need to come from whatever amounts
the Council could allocate.





> Personally, I would much rather see the answers to the questions above
> (and the others I didn't think of) before trying to design a solution. For
> example, wouldn't it be "better" to magically know which content was
> relevant to which user types? then allow them to add categories that they
> might enjoy? or remove ones they don't find relevant? Rather than splitting
> the blog? That seems like a perfectly, technically solvable problem.
> However, perhaps not, maybe it is important that contributors feel like
> they are in the "in crowd" with a "special" blog (not hidden content or
> anything), which shows their picture next to comments, allows for comments
> and trending, etc because they are "logged in" and has super cool hot dog
> related branding. I wouldn't know which of those to recommend without
> knowing about the above questions.
>
> Just some thoughts...
>
> and, btw, massive +1 for SaaS model deployments (a la wp.com), however,
> it comes with limitations on functionality, which.... see above :)
>
>
>> --
>> Matthew Miller
>> <mattdm at fedoraproject.org>
>> Fedora Project Leader
>> _______________________________________________
>> council-discuss mailing list
>> council-discuss at lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/council-discuss
>>
>
>
> _______________________________________________
> council-discuss mailing list
> council-discuss at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/council-discuss
>



-- 
Stephen J Smoogen.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/council-discuss/attachments/20150417/f56f0275/attachment.html>