Re: Opportunity for participation in Gnome releases
On Thu, 2005-10-06 at 11:48 +0200, Murray Cumming wrote: [snip] Is this just a matter of hosting the .ical file on our http server? Yes, as simple as that :-) and of course, publish the url prominently where the target audience can see it. Evolution users need only to create a new calendar (choose type 'On The Web'), enter the url and a name. That would do. Harish ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Opportunity for participation in Gnome releases
tor, 06,.10.2005 kl. 14.08 +0530, skrev Harish Krishnaswamy: On Wed, 2005-10-05 at 16:55 -0600, Elijah Newren wrote: - Creating an ical file for the 2.13 srelease cycle Please find attached an ical file for the 2.13 release cycle. You can import this into your Evolution calendar. I find it slightly amusing that Evolution gives me the choice between saving the file to disk or opening it in Korganizer :-) Cheers Kjartan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 04 Oct 2005 17:40:23 +0200, Rodrigo Moya wrote: It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session Given that libnotify messages aren't really meant for large amounts of text, I'm not sure that it's the right place to use it. Most MOTD messages on my university network are too large to fit in a notification and require at least basic formatting etc. I'd go for popping up a dialog in all cases, actually. thanks -mike (a notification-daemon author) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Thu, 2005-10-06 at 12:03 +0100, Mike Hearn wrote: On Tue, 04 Oct 2005 17:40:23 +0200, Rodrigo Moya wrote: It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session Given that libnotify messages aren't really meant for large amounts of text, I'm not sure that it's the right place to use it. Most MOTD messages on my university network are too large to fit in a notification and require at least basic formatting etc. I'd go for popping up a dialog in all cases, actually. can't the notification daemon use scrolling when the messages are too big? -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Thu, 06 Oct 2005 16:26:16 +0200, Rodrigo Moya wrote: can't the notification daemon use scrolling when the messages are too big? Well, it could, but you have to keep the use cases for libnotify in mind: short, asynchronous notifications where it doesn't really matter if the user misses them. eg: - Manya has come online - Battery is low - You've got mail It's not meant for: - Informing the user of something they just initiated (I'm looking at you Robert ;) - Displaying user-critical information, which I'd rate MOTD as - Displaying arbitrary widgets. A scrollbar or some auto-scroll inside a notification would make them too complex in my view, and besides why bother when putting a text view or better a GtkMozEmbed inside a GTK+ window is so easy? thanks -mike ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Gnome-utils branched
Hey all, gnome-utils has been branched for gnome 2.12. Stable releases should use the gnome-2-12 branch, while earth-shattering improvements will happen on HEAD. Cheers Vincent ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On Wed, 2005-10-05 at 00:50 +0200, Rodrigo Moya wrote: Maybe we want a desktop-devel-patches@ list? Regardless of where the canonical place to store patches is (mailing list archive or Bugzilla), I think it is valuable to make it easy for groups of interested people to review incoming patches, even if they're not the official maintainer of the module or are actively tracking Bugzilla for that module. More eyes spot problems more easily. Probably just need a Bugzilla hack where if a patch is attached to a bug (or an existing one is updated) it gets autosent to some mailing list. Digging about it's kind of like this: http://bugzilla.gnome.org/reports/patch-diligence-report.cgi Except we want to make it push instead of pull so to speak =) And we'd probably want to restrict it to modules in the official core so as to not drown in the noise; also people interested in other modules can just watch that module's bugs anyways. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On 06/10/05, Colin Walters [EMAIL PROTECTED] wrote: Probably just need a Bugzilla hack where if a patch is attached to a bug (or an existing one is updated) it gets autosent to some mailing list. Digging about it's kind of like this: http://bugzilla.gnome.org/reports/patch-diligence-report.cgi Except we want to make it push instead of pull so to speak =) Sounds like a good place to use an RSS feed to me. -- Marc O'Morain http://marcomorain.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
More general patch notification? [Was: Re: gnome-utils patch]
On 10/6/05, Colin Walters [EMAIL PROTECTED] wrote: On Wed, 2005-10-05 at 00:50 +0200, Rodrigo Moya wrote: Maybe we want a desktop-devel-patches@ list? Regardless of where the canonical place to store patches is (mailing list archive or Bugzilla), I think it is valuable to make it easy for groups of interested people to review incoming patches, even if they're not the official maintainer of the module or are actively tracking Bugzilla for that module. More eyes spot problems more easily. Probably just need a Bugzilla hack where if a patch is attached to a bug (or an existing one is updated) it gets autosent to some mailing list. Digging about it's kind of like this: http://bugzilla.gnome.org/reports/patch-diligence-report.cgi Except we want to make it push instead of pull so to speak =) And we'd probably want to restrict it to modules in the official core so as to not drown in the noise; also people interested in other modules can just watch that module's bugs anyways. Could you clarify some? I'm hoping to find some time to work on patch stuff in bugzilla in the coming months (if Olav doesn't beat me to it--he's getting all kinds of bugzilla stuff done right now) and some kind of auto-notification/reminder was already on my list; it'd make sense to tackle something like this at the same time if I can. So, a few questions, for you and others that might be interested: What kind of information is wanted? Is it just a sheer number of unreviewed patches and a percentage compared to total as found in the patch-diligence-report you linked to? Would it be more along the lines of short patch descriptions? Are corresponding bug #s (links?) w/ priority, severity, product, or component wanted? An updated report sent out every N days with new patches, or emails sent out the very instant a patch is attached (the former is easier, as we already have the infrastructure for it; see http://bugzilla.gnome.org/reports/patch-report.cgi?product=metacitymax_days=7 for which we also have a little front end at http://bugzilla.gnome.org/reports/patch-status.cgi). How is the information wanted? A mailing list? An RSS feed (The former shouldn't be too hard to add. We also have code that does the latter for something else that could be used here; take a look at bugs for beginners can be found at http://bugzilla.gnome.org/reports/keyword-search.cgi?keyword=gnome-love and the corresponding RSS feed at http://bugzilla.gnome.org/reports/keyword-search-rss.cgi?keyword=gnome-love) Cheers, Elijah ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: session autostart
On Thu, 2005-10-06 at 18:26 +0200, Rodrigo Moya wrote: Hi So, given the recent urge to speed up gnome-session, and with the libgnomeservice pending integration, what do you think about having a BOF in the summit about gnome-session? Thus, we can discuss in person what could be done to speed it up (I've got some changes in my local copy that speed it up a little bit, although there's still a lot of room for improvement) and how the libgnomeservice/autostart thing can be better implemented and integrated. Does that sound good? Yes. Mark it on the schedule. We also need to talk about the dbus changes needed with Havoc. -- John (J5) Palmieri [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: session autostart
On Thu, 2005-10-06 at 13:29 -0400, John (J5) Palmieri wrote: On Thu, 2005-10-06 at 18:26 +0200, Rodrigo Moya wrote: Hi So, given the recent urge to speed up gnome-session, and with the libgnomeservice pending integration, what do you think about having a BOF in the summit about gnome-session? Thus, we can discuss in person what could be done to speed it up (I've got some changes in my local copy that speed it up a little bit, although there's still a lot of room for improvement) and how the libgnomeservice/autostart thing can be better implemented and integrated. Does that sound good? Yes. Mark it on the schedule. We also need to talk about the dbus changes needed with Havoc. ok, added it to Saturday's schedule, at 4.45 PM. -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: nautilus-cd-burner branched for 2.12
On 10/6/05, William Jon McCann [EMAIL PROTECTED] wrote: Hello, I have branched nautilus-cd-burner. The stable branch is gnome-2-12 and development continues on HEAD. No big plans for GNOME 2.14 - just fixing bugs. Anyone who has penciled in 'make gdm and screensaver rock my sox' for 2.14 gets a totally free pass on all other modules they maintain. :) [Heck, you get a free pass from me just for everything you've done in 2.12...] Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Gnome-utils branched
On 10/6/05, Vincent Noel [EMAIL PROTECTED] wrote: Hey all, gnome-utils has been branched for gnome 2.12. Stable releases should use the gnome-2-12 branch, while earth-shattering improvements will happen on HEAD. _ 2.13? (everyone play 'fill in the blank' first, then when vincent responds, play 'fill in the wiki') Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Gnome-utils branched
On 10/6/05, Luis Villa [EMAIL PROTECTED] wrote: _ 2.13? (everyone play 'fill in the blank' first, then when vincent responds, play 'fill in the wiki') I have no idea what you're talking about. What is a wiki anyway ? Cheers Vincent ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: [gnome-love] Re: Opportunity for participation in Gnome releases
On 10/6/05, Luis Villa [EMAIL PROTECTED] wrote: On 10/6/05, Murray Cumming [EMAIL PROTECTED] wrote: [snip] Just a thought - A web calendar hosted by the release team would be useful to push new/modified notifications, marginally scoring over the ical file. [snip] Is this just a matter of hosting the .ical file on our http server? We used to have one on gnome.org/start/ - should still be in CVS. Yes, http://cvs.gnome.org/viewcvs/gnomeweb-wml/www.gnome.org/start/2.9/schedule.ics?rev=1.1view=log, for example. I guess we could make a 2.13 directory, stick the ical file there, and then link to it from http://live.gnome.org/TwoPointThirteen. But doesn't the wiki have a way to upload small files directly? If so, wouldn't it be easier to do that? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: sound init in gnome-settings-daemon
quote who=Rodrigo Moya Looking at how to improve gnome-session startup, I found both gnome-session and gnome-settings-daemon are starting ESD. I guess we really want one of them to start it, so which one should be removed? My first thought is to remove the one in g-s-d. Is that ok? Or am I missing anything? I agree - I tend to think g-s-d is managing a bunch of sessiony stuff atm because they're settings related (esd, xscreensaver, etc). These are probably best managed as services to the desktop, as part of the session. - Jeff -- linux.conf.au 2006: Dunedin, New Zealand http://linux.conf.au/ That whole 'you complete me' thing is just tragic and totally unrealistic. Go complete yourself. - Anon ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
