[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

FESCo Meeting Summary for 2007-01-18



Members Present 
      * Thorsten Leemhuis (thl) 
      * Brian Pepple (bpepple) 
      * Rex Dieter (rdieter) 
      * Jason Tibbitts (tibbs) 
      * Toshio Kuratomi (abadger1999) 
      * Christian Iseli (ch4chris) 
      * Warren Togami (warren) 
      * Josh Boyer (jwb) 
      * Tom Callaway (spot) 
      * Kevin Fenzi (nirik) 
      * Dennis Gilmore (dgilmore) 
      * Jeremy Katz (jeremy) 
      * Jesse Keating (f13) 
      * Bill Nottingham (notting) 
        
Absent
      * Andreas Bierfert (awjb) 
        
== Summary ==
EPEL Update 
      * Most of the outstanding issues are waiting on RedHat IS. 
      * It was brought up that EPEL should have separate guideline (e.g.
        latest and greatest vs. a more stable approach), and that the
        EPEL community should make this decision. 
        
Opening Core 
      * FAB accepted thl's proposal on the FESCo/Core cabal merge.
        Welcome to FESCo Jesse & Bill! 
      * f13, notting, and max will be added to the fesco-list. 
        
FESCo-successor name issue
      * It was decided to keep the name 'FESCo' after the Core/Extras
        merge. thl will send an e-mail to the mailing lists announcing
        this. 
        
Encourage co-maintainership
      * thl is going to send an e-mail to the mailing lists with his
        proposal. 
        
Firefox updates in stable often breaks packages
      * Will look at automating rebuilds of affected packages, though
        this won't before F7. 
      * For now, bpepple is going to form a group with other maintainers
        with packages affected by Firefox updates so rebuilds are
        handled more quickly. 
        
Disallow cvs-import for everything but the initial import
      * It was discussed how using cvs-import quite often overwrite
        previous changes done by other maintainers. 
      * The initial thought on how to fix this was to modify cvs-import
        to prevent this behavior, but many issues need further
        discussion before acting. Further brain-storming will occur on
        the mailing list, so as not to waste meeting time. 
        
What do we want to see in the approved-message in a review bug
      * People seeking sponsorship should definitely use checklist of
        items reviewed, so there is documentation of their knowledge of
        the packaging guidelines. 
      * If there is a discussion on issues in the review, then an
        APPROVED only is probably ok. 
        
Syslog-ng Patent Problems
      * RedHat Legal is currently reviewing this issue. 
        
Misc
      * FESCo meeting in the future will take place in #fedora-meeting
        beginning on 2007-01-25.

For full IRC log:
http://fedoraproject.org/wiki/Extras/SteeringCommittee/Meeting-20070118

Thanks,
/B
-- 
Brian Pepple <bpepple fedoraproject org>

gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B  CBDE 326A E936 810C C15E

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]