Edit Info Other
Login

Diff for "Infrastructure"

Differences between revisions 11 and 28 (spanning 17 versions)
Revision 11 as of 2008-04-22 09:37:08
Size: 4114
Editor: XavierLamien
Comment:
Revision 28 as of 2009-11-18 12:44:04
Size: 2092
Editor: XavierLamien
Comment: Fixed list info link
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Infrastructure = # acl Known:read
Line 4: Line 4:
The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repository. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by:
Line 6: Line 5:
 * IRC
  You can find the #rpmfusion channel on [http://freenode.net/ freenode].
The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repositories. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by:
Line 9: Line 7:
## We should talk about an potential Fedora-infrastructure-list@ or Admin@ to add
##
## * Mailing list
## The mailing list for the RPM Fusion Infrastructure is [http://rpmfusion.org/mailman/listinfo/rpmfusion-infrastructure-list ##rpmfusion-infrastructure-list@rpmfusion.org].
 * '''IRC'''
  You can find the #rpmfusion channel on [[http://freenode.net/|freenode]].
Line 14: Line 10:
== Our Infrastructure ==  * '''Mailing list'''
  The mailing list for the RPM Fusion Infrastructure is [[http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-sysadmin|rpmfusion-sysadmin@rpmfusion.org]].


== Contribute to RPM Fusion Infrastructure ==
Ready to work with the RPM Fusion Infrastructure team? We're looking for smart, volunteers, dedicated system administrators and developers to help maintain our systems and also write some code. The RPM Fusion Infrastructure team is also a way to give back to the community.
## Go take a look at our [Getting Started page


== Our Architecture ==
Line 25: Line 31:
 * `puppet1.lxtnow.podzone.net`
   * System Management server (PuppetMaster)
Line 34: Line 42:
 * `buildsys@` : ThorstenLeemhuis  * `buildsys@` : Build system list
Line 36: Line 44:
 * `cvsadmin@` : XavierLamien  * `cvsadmin@` : CVS Admin list
Line 39: Line 47:
== Pending == === Mailing Lists ===
Line 41: Line 49:

 ||<rowstyle="color: white; background-color: #3074c2; font-weight: bold; text-align: center;"> '''Task''' || '''Owner''' || '''Status''' || '''Notes''' ||
 ||||||||<rowstyle="color: black; background-color: #eeeff1; text-align: center"> '''Work in Progress / To do''' ||
 ||<rowstyle="text-align: center"> FDS || MatthiasSaou ||<bgcolor="#00FF00"> Done || Set up the Fedora Directory Services ||
 ||<rowstyle="text-align: center"> Plague Server || ThorstenLeemhuis ||<bgcolor="#00FF00"> Done || Set up the build system ||
 ||<rowstyle="text-align: center"> FAS version 2 || XavierLamien ||<bgcolor="#00FF00"> Done || Set up the Fedora Account System 2 ||
 ||<rowstyle="text-align: center"> FAS2 database || XavierLamien ||<bgcolor="#00FF00"> Done || Set up the new database for fas2 ||
 ||<rowstyle="text-align: center"> CVS - Modules || XavierLamien ||<bgcolor="#00FF00"> Done || Add script to create new modules on cvs repo ||
 ||<rowstyle="text-align: center"> CVS - Branches || XavierLamien ||<bgcolor="#00FF00"> Done || Add script to [create|add] branches on pkgs ||
 ||<rowstyle="text-align: center"> CVS/Cert || XavierLamien ||<#0000FF> 80% || Make the cvs works against CA certification ||
 ||<rowstyle="text-align: center"> CVS/Pkgs || XavierLamien ||<#FF0000> -> || Make import packages works well after Clean cert from above taks ||
 ||<rowstyle="text-align: center"> Repo || '''Unassigned''' ||<#FF0000> 0% || Where to host the Repository ?[[BR]]on Pix server ? ||
 ||<rowstyle="text-align: center"> Merge of packages || '''Unassigned''' ||<#FF0000> 0% || Availability of packages into rpmfusion repo||
 ||<rowstyle="text-align: center"> Website theme || '''Unassigned''' ||<#FF0000> 0% || Add something which match with RPM fusion logo ||
 ||<rowstyle="text-align: center"> Mailling list || '''Unassigned''' ||<#FF0000> ?? || {i} Add and rpmfusion-infrastructure-list@ or Admin@ ||
 ||<rowstyle="text-align: center"> Irc Channel || '''Unassigned''' ||<#FF0000> ?? || {i} Add and rpmfusion-admin channel ?? ||
 ||||||||<rowstyle="color: black; background-color: #eeeff1; text-align: center"> '''Tasks Closed''' ||
 ||<rowstyle="text-align: center"> FAS - Userbox || XavierLamien ||<#0000FF> 50% || Make the FAS able to create shell account on new users ---> {i} Canceled ||
 ||<rowstyle="text-align: center"> FAS - Groupbox || XavierLamien ||<#0000FF> 50% || Fix group list on user edit page ---> {i} Canceled ||
See [[http://lists.rpmfusion.org|Mailing Lists]].

About Us

The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repositories. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by:

Contribute to RPM Fusion Infrastructure

Ready to work with the RPM Fusion Infrastructure team? We're looking for smart, volunteers, dedicated system administrators and developers to help maintain our systems and also write some code. The RPM Fusion Infrastructure team is also a way to give back to the community.

Our Architecture

Servers and Services

Domain Names

  • rpmfusion.org : For all visible services.

  • rpmfusion.net : For all non-visible services (low level hostnames for example).

Email Addresses

These are all @rpmfusion.org email addresses :

  • buildsys@ : Build system list

  • accounts@ : XavierLamien

  • cvsadmin@ : CVS Admin list

  • noreply@ : /dev/null

Mailing Lists

See Mailing Lists.

Infrastructure (last edited 2023-11-14 09:37:58 by anonymous)