FWN/Beats/Infrastructure

From FedoraProject

< FWN | Beats(Difference between revisions)
Jump to: navigation, search
(Fedora Security Policy)
(Infrastructure)
Line 8: Line 8:
 
Contributing Writer:  [[HuzaifaSidhpurwala|Huzaifa Sidhpurwala]]
 
Contributing Writer:  [[HuzaifaSidhpurwala|Huzaifa Sidhpurwala]]
  
=== Why Puppet uses config instead of configs ===
+
=== Automating hosted projects? ===
  
[[SusmitShannigrahi|susmit shannigrahi]] asked[1] on the @fedora-infrastructure-list asked why, in the fedora-infrastructure implementation of puppet when we add a new file, in the .pp file the path is written as puppet:///config where as the actual path of the file is in the configs directory. To this Jeroen van Meeuwen answered [2] by saying that the [config] fileserver mount may point to /path/to/configs which may allow this discrepancy to exist.
+
[[PaulFrields|Paul W. Frields]] asked[1] on the @fedora-infrastructure-list if it was possible to automate the creation of projects on the fedorahosted.org site. Since some potential contributors may need more instantaneos result and not wait for an admin to create the project.
  
[1] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00084.html
+
[1] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00124.html
  
[2] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00085.html
+
To this [[SethVidal|Seth Vidal]] replied[2] that a part of the benefit of this being manual is that
 +
the admin can do a bit of sanity check before the project is created.
  
=== Fedora Security Policy ===
+
[2] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00125.html
 
+
[[MikeMcGrath|Mike McGrath]] wrote[3] on the @fedora-infrastructure-list about the proposed Fedora Security Policy. Mike asked that he would like everyone in the sysadmin-* group to be compliant with this policy.
+
 
+
[3] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00103.html
+
 
+
On this thread several people commented about changes they would propose in iptables[4] & [5]
+
 
+
 
+
[4] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00105.html
+
 
+
[5] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00107.html
+
 
+
=== Alpha Release Readiness ===
+
 
+
[[JohnPoelstra| John Poelstra ]] wrote [6] on the @fedora-infrastructure-list about the Alpha Release Readiness meeting on the 3rd Feb 2009. Mike McGrath replied[7] that he will be attending the meeting on the behalf of the Infrastructure team.
+
 
+
[6] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00112.html
+
 
+
[7] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00114.html
+

Revision as of 03:40, 2 February 2009

Infrastructure

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

http://fedoraproject.org/wiki/Infrastructure

Contributing Writer: Huzaifa Sidhpurwala

Automating hosted projects?

Paul W. Frields asked[1] on the @fedora-infrastructure-list if it was possible to automate the creation of projects on the fedorahosted.org site. Since some potential contributors may need more instantaneos result and not wait for an admin to create the project.

[1] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00124.html

To this Seth Vidal replied[2] that a part of the benefit of this being manual is that the admin can do a bit of sanity check before the project is created.

[2] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/msg00125.html