From Fedora Project Wiki
(Tracker Bug)
(Targets)
Line 13: Line 13:
 
* '''have several "interested parties" that will help once we are building packages/trees'''
 
* '''have several "interested parties" that will help once we are building packages/trees'''
 
* set up externally/publically available koji instance
 
* set up externally/publically available koji instance
* [https://67-207-134-195.slicehost.net/koji/ first sample koji instance] (non-functional atm.)
+
* [https://s390.koji.fedoraproject.org/koji/ s390x koji instance]
 
* identified build guests within Red Hat (internal access only at first)   
 
* identified build guests within Red Hat (internal access only at first)   
 
* identified persistent storage (> 2 TB anticipated in first year alone)
 
* identified persistent storage (> 2 TB anticipated in first year alone)

Revision as of 15:16, 12 February 2009

Fedora s390x

  • IRC: #fedora-s390x on irc.freenode.net
  • Mailing List: fedora-s390x
  • Regular IRC meetings: TBD

Targets

  • short term goals:
  • build all F-10 packages which then will be used to bootstrap F-11
  • add all required patches to F-11 CVS
  • reached out to known interested parties in community
  • reaching out (through contacts) to IBM community (.de)
  • have several "interested parties" that will help once we are building packages/trees
  • set up externally/publically available koji instance
  • s390x koji instance
  • identified build guests within Red Hat (internal access only at first)
  • identified persistent storage (> 2 TB anticipated in first year alone)
  • temporary location (while we sort out long term permanent location)
  • start F-11 composes
  • identify the resources used for composes
  • get F-11 s390x bootable
  • this is blocking on the external dedicated environment issue (above)

People

History

FUDcon 2008 was an excellent event. During the conference, a session on secondary arches was presented and there was an excellent effort made to reach out to new arches.

Tracker Bugs

If excluding s390/s390x architectures you need to make the bug block F-ExcludeArch-s390x

to see whats currently blocking visit Bugzilla

If a bug is specific to s390/s390x architectures make the bug blocking ZedoraTracker

to see not yet resolved issues visit Bugzilla