From Fedora Project Wiki

< SIGs‎ | KDE‎ | Meetings

No edit 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]]
*  
* [[KevinKofler]]
* [[RexDieter]]
* [[StevenParrish]]
* [[ThanNgo]]
* [[RadekNovacek]]
* [[LukasTinkl]]
* [[User:Thomasj|ThomasJanssen]]


== Agenda ==
== Agenda ==


* topics to discuss:
* topics to discuss:
** kde-4.5 rc3 status
** Sebastian Trueg recommends to set /proc/sys/fs/inotify/max_user_watches to very high value for Nepomuk
** Sebastian Trueg recommends to set /proc/sys/fs/inotify/max_user_watches to very high value for Nepomuk
** Solid DeviceKit backend
* recent bugs:
* recent bugs:
**
**
Line 18: Line 26:
== Transcript ==
== Transcript ==


The transcript will be made available after the meeting.
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-07-27/kde-sig.2010-07-27-14.02.html Meeting minutes]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-07-27/kde-sig.2010-07-27-14.02.log.html Full log]


== Summary ==
'''kde-4.5 rc3 status'''
* kdegames trademark issues
** can we omit affected games (and move to RPM Fusion?)
*** not easy to maintain -trademark patch
*** games, handbook, translations tied to it...
** ''ACTION'': jreznik to contact kde legal and kdegames maintainers about trademark issues
** ''ACTION'': than to provide list of affected files
* otherwise kde-4.5 rc3 is built and already in kde-unstable repo
'''set /proc/sys/fs/inotify/max_user_watches to very high value for Nepomuk'''
* Sebastian Trueg recommends it on kde-packagers mailing list
* we're not sure what does it mean for us
** what's happen when limit is reached?
** what about memory consumption when higher number is set?
*** ''ACTION'': jreznik to ask Sebastian
* mjg59 says it's  probably justifiable to increase it and he thinks increasing the value increases memory usage in itself, but it does increase the amount of kernel resources a user can allocate
* ''ACTION'': rdieter to contact fedora devel/kernel folks about raising /proc/sys/fs/inotify/max_user_watches
'''Solid DeviceKit backend'''
* ltinkl is working on dk backend, targetting Fedora 15 and KDE 4.6


== Summary ==
'''open discussion'''
* rdieter would like to throw out a tease that there's a good chance we'll be bringing a good qt/kde presence to fudcon zurich , pending some financial/logistical details


== Comments ==
== Comments ==

Latest revision as of 15:47, 27 July 2010

Meeting Time

Participants

Agenda

  • topics to discuss:
    • kde-4.5 rc3 status
    • Sebastian Trueg recommends to set /proc/sys/fs/inotify/max_user_watches to very high value for Nepomuk
    • Solid DeviceKit backend
  • recent bugs:

Transcript

Summary

kde-4.5 rc3 status

  • kdegames trademark issues
    • can we omit affected games (and move to RPM Fusion?)
      • not easy to maintain -trademark patch
      • games, handbook, translations tied to it...
    • ACTION: jreznik to contact kde legal and kdegames maintainers about trademark issues
    • ACTION: than to provide list of affected files
  • otherwise kde-4.5 rc3 is built and already in kde-unstable repo

set /proc/sys/fs/inotify/max_user_watches to very high value for Nepomuk

  • Sebastian Trueg recommends it on kde-packagers mailing list
  • we're not sure what does it mean for us
    • what's happen when limit is reached?
    • what about memory consumption when higher number is set?
      • ACTION: jreznik to ask Sebastian
  • mjg59 says it's probably justifiable to increase it and he thinks increasing the value increases memory usage in itself, but it does increase the amount of kernel resources a user can allocate
  • ACTION: rdieter to contact fedora devel/kernel folks about raising /proc/sys/fs/inotify/max_user_watches

Solid DeviceKit backend

  • ltinkl is working on dk backend, targetting Fedora 15 and KDE 4.6

open discussion

  • rdieter would like to throw out a tease that there's a good chance we'll be bringing a good qt/kde presence to fudcon zurich , pending some financial/logistical details

Comments