From Fedora Project Wiki

No edit summary
(Added formatting)
Line 3: Line 3:


* DNS - Same as actual hosting
* DNS - Same as actual hosting
  - Possible to take care of this through fedoracommunity.org initiative
** Possible to take care of this through fedoracommunity.org initiative
  - projetofedora.org - Expires Dec 9, 2012
** projetofedora.org - Expires Dec 9, 2012
  - proyectofedora.org - Expires Oct 10, 2010
** proyectofedora.org - Expires '''Oct 10, 2010'''
  - Both domains are 'property' of Rodrigo Padula.
** Both domains are 'property' of Rodrigo Padula.


* Reliability (has there been problems keeping the sites up?)
* Reliability (has there been problems keeping the sites up?)
--None at all. It's just the assurance of knowing this will be alive after rodrigo leaves or whatever happens.
** None at all. It's just the assurance of knowing this will be alive after rodrigo leaves or whatever happens.[[User:Nushio|Nushio]] 00:26, 28 August 2010 (UTC)




Line 22: Line 22:


Code:
Code:
- Timpus (Java Webapp)
* Timpus (Java Webapp)
- Unnamed Web Survey Platform (Java Webapp)
* Unnamed Web Survey Platform (Java Webapp)
-RPMDev (Redmine / Ruby on Rails)  
** RPMDev (Redmine / Ruby on Rails)  
  - Documentation about using rpm/yum in spanish
*** Documentation about using rpm/yum in spanish
  - Some coding help for same
*** Some coding help for same
  - Some best practices around package management
*** Some best practices around package management
  - Organization about translating packaging documents
*** Organization about translating packaging documents
- Mailing lists for (Could be moved to @lists.fp.o without any loss)
** Mailing lists for (Could be moved to @lists.fp.o without any loss)
  - ceam (Central America)
*** Ceam (Central America)
  - revista (Fedora Magazine)
*** revista (Fedora Magazine)
  - usuarios (spanish fedora user support)
*** usuarios (spanish fedora user support)
  - devel (Spanish devel list)
*** devel (Spanish devel list)
 
** Wordpress for Latam ambassadors -- Blogs for latam countries
- Wordpress for Latam ambassadors -- Blogs for latam countries
** Wiki duplication efforts ( wiki.proyectofedora.org vs fedoraproject.org/wiki )
- Wiki duplication efforts ( wiki.proyectofedora.org vs fedoraproject.org/wiki )
** Be able to tie into FAS for users and authentication (Very Important)
- Be able to tie into FAS for users and authentication (Very Important)

Revision as of 00:26, 28 August 2010

Hosting:

  • Assurance of where the money's coming from (Rodrigo paid for hosting w/ RH Brasil money)
  • DNS - Same as actual hosting
    • Possible to take care of this through fedoracommunity.org initiative
    • projetofedora.org - Expires Dec 9, 2012
    • proyectofedora.org - Expires Oct 10, 2010
    • Both domains are 'property' of Rodrigo Padula.
  • Reliability (has there been problems keeping the sites up?)
    • None at all. It's just the assurance of knowing this will be alive after rodrigo leaves or whatever happens.Nushio 00:26, 28 August 2010 (UTC)


Social:

  • Be Official
  • To permit participation of all collaborators in World
  • To stimulate collaboration and utilization of official resources of Fedora
  • To avoid more than one resource with the same target
  • There is more collaborators in Fedora-admin instead possible group "Fedora-latam-admin"
  • All members of "Fedora-latam-admin" could help in all infra

Code:

  • Timpus (Java Webapp)
  • Unnamed Web Survey Platform (Java Webapp)
    • RPMDev (Redmine / Ruby on Rails)
      • Documentation about using rpm/yum in spanish
      • Some coding help for same
      • Some best practices around package management
      • Organization about translating packaging documents
    • Mailing lists for (Could be moved to @lists.fp.o without any loss)
      • Ceam (Central America)
      • revista (Fedora Magazine)
      • usuarios (spanish fedora user support)
      • devel (Spanish devel list)
    • Wordpress for Latam ambassadors -- Blogs for latam countries
    • Wiki duplication efforts ( wiki.proyectofedora.org vs fedoraproject.org/wiki )
    • Be able to tie into FAS for users and authentication (Very Important)