From Fedora Project Wiki

< FWN‎ | Beats

(WikiNames, past tense. Capitalize titles. Nice readable work.)
Line 8: Line 8:
Contributing Writer:  HuzaifaSidhpurwala
Contributing Writer:  HuzaifaSidhpurwala


=== More Puppet Training! ===  
=== Planning a future L10N infrastructure (including Fedora) ===


[[MikeMcGrath|Mike McGrath]] wrote on the @fedora-infrastructure-list [1] that he is going to hold a couple of trainings for Puppet on fedora-infrastructure. He asked if any one had questions etc to be included in the training.
[[AsgeirFrimannsson|Asgeir Frimannsson]] wrote on the @fedora-infrastructure-list [1] about his views on the current localisation infrastructure. He summarises the current infrastructure which is used by the localisation team, which includes the version control system and other online tools. He also discusses transifex. He also discusses the requirements for a system where the translation lifecycle would be managed within 'Translation Repositories'


[1] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00001.html
[1] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00108.html


=== Removal of Old Projects from fedorahosted. ===


[[SusmitShannigrahi|Susmit Shannigrahi]] reminded[2] the list that, Fedora has a policy to remove _any_ hosted projects that are not altered or updated for last six months. Susmit provided a list of projects, which fell into this category and they will soon be removed.
=== Puppet training ===


[2] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00050.html
[[MikeMcGrath|Mike McGrath]] wrote on the @fedora-infrastructure-list [2] that he is going to hold a puppet training next wednesday. He also posted an ogg and the slide deck [3] to which his live training will be identical.  


=== Beta Freeze ===
[2] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00124.html


[[MikeMcGrath|Mike McGrath]] reminded[3] everyone that the beta freeze is going to live and it will end on
[3] http://mmcgrath.fedorapeople.org/puppet/
2008-09-24. This is the first pre-release freeze type the infrastructure team has had[4].  


[3] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00096.html
=== Fedora 10 Beta Release Planning Meeting ===


[4] http://fedoraproject.org/wiki/Infrastructure/SOP/Release#Change_Freeze
[[JohnPoelstra|John Poelstra]] wrote on the @fedora-infrastructure-list [4] about the Fedora 10 Beta Release Planning Meeting. He has also posted the list of participants and the meeting logs.
 
[4] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00135.html
 
=== Infrastructure update notice ===
 
[[PaulFrields | Paul W. Frields ]] wrote on the @fedora-infrastructure-list [5] about the announcement which went out on the fedora-announce-list [6]. Paul confirmed that all of our services were back online now.
 
[5] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00140.html
 
[6] http://www.redhat.com/archives/fedora-announce-list/2008-September/msg00009.html
 
=== app2 disk space ===
 
[[MikeMcGrath|Mike McGrath]] wrote on the @fedora-infrastructure-list[7] about the recent disk alerts on app2. It seems that the host was not built with enough disk space similar to app1.
It does raise a point about storage for transifex though.  Basically each host running transifex or damned lies, keeps a local copy of every scm as part of its usage. For performance
reasons that should not change but its something we'll want to figure out long term. So after the freeze the host is going to be rebuilt.
 
[7] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00155.html

Revision as of 08:36, 22 September 2008

Infrastructure

This section contains the discussion happening on the fedora-infrastructure-list

http://fedoraproject.org/wiki/Infrastructure

Contributing Writer: HuzaifaSidhpurwala

Planning a future L10N infrastructure (including Fedora)

Asgeir Frimannsson wrote on the @fedora-infrastructure-list [1] about his views on the current localisation infrastructure. He summarises the current infrastructure which is used by the localisation team, which includes the version control system and other online tools. He also discusses transifex. He also discusses the requirements for a system where the translation lifecycle would be managed within 'Translation Repositories'

[1] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00108.html


Puppet training

Mike McGrath wrote on the @fedora-infrastructure-list [2] that he is going to hold a puppet training next wednesday. He also posted an ogg and the slide deck [3] to which his live training will be identical.

[2] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00124.html

[3] http://mmcgrath.fedorapeople.org/puppet/

Fedora 10 Beta Release Planning Meeting

John Poelstra wrote on the @fedora-infrastructure-list [4] about the Fedora 10 Beta Release Planning Meeting. He has also posted the list of participants and the meeting logs.

[4] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00135.html

Infrastructure update notice

Paul W. Frields wrote on the @fedora-infrastructure-list [5] about the announcement which went out on the fedora-announce-list [6]. Paul confirmed that all of our services were back online now.

[5] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00140.html

[6] http://www.redhat.com/archives/fedora-announce-list/2008-September/msg00009.html

app2 disk space

Mike McGrath wrote on the @fedora-infrastructure-list[7] about the recent disk alerts on app2. It seems that the host was not built with enough disk space similar to app1. It does raise a point about storage for transifex though. Basically each host running transifex or damned lies, keeps a local copy of every scm as part of its usage. For performance reasons that should not change but its something we'll want to figure out long term. So after the freeze the host is going to be rebuilt.

[7] https://www.redhat.com/archives/fedora-infrastructure-list/2008-September/msg00155.html