From Fedora Project Wiki

< SIGs‎ | KDE‎ | Meetings

(Created page with '== Meeting Time == * [http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=05&day=11&hour=14&min=0&sec=0 2010-05-11 14:00 UTC] * #fedora-meeting on freenode ==...')
 
(Meeting summary)
 
(2 intermediate revisions by 2 users not shown)
Line 6: Line 6:
== Participants ==
== Participants ==


The list of participants will be filled in after the meeting.
<!--
* [[JaroslavReznik]]
* [[JaroslavReznik]]
* [[KevinKofler]]
* [[KevinKofler]]
Line 15: Line 13:
* [[ThanNgo]]
* [[ThanNgo]]
* [[User:Thomasj|ThomasJanssen]]
* [[User:Thomasj|ThomasJanssen]]
-->


== Agenda ==
== Agenda ==


* topics to discuss:
* topics to discuss:
** List of critical KDE packages for new update policy (requested by FESCo)
** Default install paths for apidocs
** Duplicate menu entries, e.g. [https://bugzilla.redhat.com/show_bug.cgi?id=591089 #591089]:
*** Do we consider these bugs?
*** Or do we want to follow upstream and keep the dupes where upstream has them?
*** If we consider them bugs, do we want to fix these in updates? Or only in new releases?
*** Do we want these to be blockers for F14? The GNOME folks consider these release blockers.
** KDE SC 4.4.3 status
* recent bugs:
* recent bugs:
** (none)
** (none)
Line 26: Line 29:
== Transcript ==
== Transcript ==


The transcript will be made available after the meeting.
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-05-11/kde-sig.2010-05-11-14.02.html Meeting minutes]
<!--
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-05-11/kde-sig.2010-05-11-14.02.log.html Full log]  
UPDATE ME!
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-04-27/kde-sig.2010-04-27-14.09.html Meeting minutes]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-04-27/kde-sig.2010-04-27-14.09.log.html Full log]  
-->


== Summary ==
== Summary ==


The summary will be written after the meeting.
'''KDE SC 4.4.3 status'''
* kde-l10n needs respin and build
* ''ACTION:'' ltinkl to respin and build kde-l10n and to prepare Bodhi update
 
'''Duplicate menu entries'''
* See [https://bugzilla.redhat.com/show_bug.cgi?id=591089], [https://bugzilla.redhat.com/show_bug.cgi?id=591093], [https://bugzilla.redhat.com/show_bug.cgi?id=591097]
** Do we consider these bugs?
** Or do we want to follow upstream and keep the dupes where upstream has them?
** If we consider them bugs, do we want to fix these in updates? Or only in new releases?
** Do we want these to be blockers for F14? The GNOME folks consider these release blockers.
* ''AGREED:'' on Kevin Kofler's proposal - report upstream, follow upstream's decision, don't treat it as a release blocker
 
'''Default install paths for apidocs'''
* we are inconsistent in apidocs directories naming and location
** soprano contains version, some apidocs are installed in doc/lib-apidocs/, some doc/HTML/en/lib-apidocs
** we need consistent naming and common install location
*** ''AGREED:'' apidocs not to be installed to version specific directories
*** ''AGREED:'' on adapting to KDevelop needs, rdieter to check it
* final decision postponed to next meeting


== Comments ==
== Comments ==

Latest revision as of 15:14, 11 May 2010

Meeting Time

Participants

Agenda

  • topics to discuss:
    • Default install paths for apidocs
    • Duplicate menu entries, e.g. #591089:
      • Do we consider these bugs?
      • Or do we want to follow upstream and keep the dupes where upstream has them?
      • If we consider them bugs, do we want to fix these in updates? Or only in new releases?
      • Do we want these to be blockers for F14? The GNOME folks consider these release blockers.
    • KDE SC 4.4.3 status
  • recent bugs:
    • (none)

Transcript

Summary

KDE SC 4.4.3 status

  • kde-l10n needs respin and build
  • ACTION: ltinkl to respin and build kde-l10n and to prepare Bodhi update

Duplicate menu entries

  • See [1], [2], [3]
    • Do we consider these bugs?
    • Or do we want to follow upstream and keep the dupes where upstream has them?
    • If we consider them bugs, do we want to fix these in updates? Or only in new releases?
    • Do we want these to be blockers for F14? The GNOME folks consider these release blockers.
  • AGREED: on Kevin Kofler's proposal - report upstream, follow upstream's decision, don't treat it as a release blocker

Default install paths for apidocs

  • we are inconsistent in apidocs directories naming and location
    • soprano contains version, some apidocs are installed in doc/lib-apidocs/, some doc/HTML/en/lib-apidocs
    • we need consistent naming and common install location
      • AGREED: apidocs not to be installed to version specific directories
      • AGREED: on adapting to KDevelop needs, rdieter to check it
  • final decision postponed to next meeting

Comments