[TYPO3-typo3org] What should happen to buzz.typo3.org?

[ben van 't ende]

Hey Guys,

I would really like to keep it a separate website under someone else's
responsibility then the current typo3.org team. The site needs to have a much
different design and look like a blog. Like www.t3blog.com, not the design of
course, but the concept. Of course we use TYPO3 for that. It should also be
do-able to do a design contest for the site design or maybe the french guys can
also take care of that. Another thing that speaks against having it under the
typo3.org concept is that it creates a number of dependencies, which might make
it hard to do changes and will have everything look the same.

All in all it is not something that will be done in a day, but should also not
be such a challenge as typo3.org.

gRTz ben



On 25/06/12 20:50, Tolleiv Nietsch wrote:
> Hi,
> 
> actually for many reasons I'd prefer if we could include as many of the current
> sites under the new typo3.org setup as possible.
> 
> The most important reason for that preference is manpower. Every single site
> lacks manpower already, joining them together at least keeps us focussed on one
> site and doesn't split forces into many small teams which tend to loose focus.
> 
> Unfortunately my freetime is very limited in the next months, but you can count
> me in for sprints related to that topic.
> 
> Cheers,
> Tolleiv
> 
> 
> Steffen Gebert schrieb:
> Dear community,
> 
> I'd like to ask for your opinion and ideas, what should happen with our
> blog site http://buzz.typo3.org
> 
> Its state is disastrous - it looks ugly, uses an extremely outdated
> TYPO3 version, and enabling a user to write own blog posts is just a PITA.
> 
> I see a few options:
> (1) shut it down without any replacement
>      - IMHO no option
> (2) integrate it into typo3.org (maybe under Community)
> (3) keep the subdomain to make clear that it's user-generated content
> and revamp it based on modern software (let it be TYPO3 with any blog
> extension, Wordpress, or some other $blogSoftware).
> 
> The requirements that I would expect:
> (1) every typo3.org user must be able to write blog posts (without an
> admin having to set anything up)
> (2) teams must be able to have a team blog. Importing team structure
> from forge.typo3.org would be amazing
> (3) the most important point: we need a team of a few people that feel
> responsible and maintain that web site. The server team would provide a
> vhost, only the $blogSoftware itself has to be maintained.
> 
> Your opinion? You're in?
> 
> Kind regards
> Steffen
> 
> 

-- 
TYPO3 Community Manager