Your favorite CMS running docs.fedoraproject.org?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We are looking for a team of people who want to deploy and maintain a
new CMS for Fedora Docs.  It may become the CMS that runs all of
fedoraproject.org that is not a wiki.[0]

Which CMS?  There's the fun part.  You pick your favorite.

Best is if you are already passionate about a particular CMS solution.
You need to be willing to:

  * Deploy the installation to Fedora Infrastructure

  * Maintain it as part of the Infrastructure and Websites teams[1]

  * Have experience with the CMS to be able to expand it to meet
    Fedora's needs[2], preferably as part of the upstream

  * Be willing to package whatever is needed for Doc's CMS instance
    that isn't already in Fedora

  * Work as part of a team of three or more fellow Fedorans[3]

Skills include web systems administration, design (graphics, CSS)
and/or coding (PHP, Python, Java, etc.) in the particular CMS
solution, and perhaps some understanding of content management.

For more information:

https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites
http://www.redhat.com/archives/fedora-docs-list/2009-January/msg00077.html
https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites#Team_requirements_for_deployment_and_maintenance

(Separate copies sent to fedora-art-list, fedora-devel-list, and
fedora-list; separate discussion threads for each location is
preferred.)

Thanks - Karsten

[0] We are not replacing the wiki.  The wiki serves a different
    purpose than a full CMS.  The CMS would cover <10% of Fedora
    content, such as:

https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites#Target_.28sub-.29domains_and_paths

[1] http://fedoraproject.org/wiki/Infrastructure
    http://fedoraproject.org/wiki/Websites

[2] https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites#Solution_requirements
    https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites#Team_requirements_for_deployment_and_maintenance

[3] We don't want to overburden one individual; we need to avoid
    having one person be a single point of failure.  In addition, it
    would be good if no more than one of the people on the team is
    already busy with work from Infrastructure.  The goal is to
    increase the pool of people, not divide it further.

-- 
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41

Attachment: pgpKblFSkA0nb.pgp
Description: PGP signature

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux