Re: Proposal: What's new
On Wed, 2009-11-18 at 10:34 +0100, Sven Herzberg wrote: Hi, Am Mittwoch, den 18.11.2009, 10:12 +0100 schrieb Patryk Zawadzki: The idea is to add another option called What's new to the Help menu in all GNOME applications. As the name suggest it would contain a Grandma-Readable™ changelog. This means something closer to the release notes than to Fixed #123, foo shouldn't dereference NULLs in foo::frobnicate(). Goals? Two really. One - to make it easier for users to discover newly introduced features. Two - to make it easier to write GNOME release notes. Sounds like a nice idea, really. But then I'm facing this question: How do I specify version numbers in a grandma-friendly way? Do we expect granny to know about version numbers? Do we write those only for major and minor version changes (like six-monthly releases)? Do we call the single sections Changes since Spring 2009 (to avoid version numbers)? Do we really have to show version numbers at all? All we have to do is list new features in a reverse chronological order and have some cut-off. This will show new features from this version and possibly some from older releases (which may be new to the user depending on how/when he updated). All the features that are listed are stuff that exists on the users installed version, so there is no need to specify what version the feature is. (They are all in this version.) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Backup
2009/11/18 Sandy Armstrong sanfordarmstr...@gmail.com: If you intend to propose your app for 2.32 (aka 3.0), note that the proposal period has not yet opened, but you can get a head start by trying to follow the GNOME release schedule, and potentially migrating your code and bug tracking from launchpad to gnome.org. Infrastructure things like this help to reduce some of the hurdles in module proposals. I've made a draft of the 'bid' I will send when the proposal period opens: http://live.gnome.org/DejaDup/GNOME I'm not prepared to abandon Launchpad just for the hope of inclusion, but releasing in sync with GNOME for the 2.30 cycle would be a good way to get familiar with GNOME cadence. -mt ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Window titles
On 17 Nov 2009, at 19:16, William Jon McCann wrote: Well, really now is the time. We are in the process of shaping the user experience for 3.0. I encourage designers from Sun, Novell, Canonical etc to get involved now - while there is still time. Absolutely agree, and as you'll hopefully have seen on the usability list and elsewhere recently, there's certainly some efforts to rejuvenate some kind of semi-formal usability group to get stuck right into it. I think we have some good ideas about how we want the HIG to evolve, just need to get started on that, and on some of the other usability activities we'd like to be doing, too. I've literally been begging for involvement from these companies for a year now. And unfortunately, we haven't gotten much if any help yet. I don't know why. Can't speak for the others, but on my front it's simply been lack of availability :/ I've been tied up with other Sun projects, and in non-work hours with moving house, amongst other things. All that means I've barely even had a chance to look at gnome-shell yet, either, let alone make any meaningful contribution to any discussions about it, which is rather frustrating. (It doesn't help that it's a bit of a pain to build and run on OpenSolaris at the moment, and that it doesn't work all that nicely on other distros running in VirtualBox, where it would be theoretically easier to play with). Cheeri, Calum. -- CALUM BENSON, Interaction Designer Sun Microsystems Ireland mailto:calum.ben...@sun.comOpenSolaris Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Branch notifications
From http://live.gnome.org/MaintainersCorner When you branch, please remember to let release-team, desktop-devel-list, gnome-doc-list, and gnome-i18n know. Since the git migration, we have automatic notifications for any branch using the standard gnome-MAJOR-MINOR scheme. They go out to release-team, gnome-doc-list, and gnome-i18n. Claude (gnome-i18n) and I (gnome-doc-list) agree that the automatic notifications are sufficient, and we don't need the redundant manual notification. That leaves release-team and desktop-devel-list. I haven't been sending my branch notification to d-d-l for a long time, and I think most other developers don't either. I think it's noise on this list. So if nobody objects, I'd like to remove the requirement to send branch notification emails at all. I'll replace it with something to the effect of Ensure that a notification is sent to these lists. If you use a standard branch name, this will happen automatically. If it doesn't, send an email manually. If nobody smacks me down in a few days, I'll make this change. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Branch notifications
Le vendredi 20 novembre 2009, à 15:03 -0600, Shaun McCance a écrit : From http://live.gnome.org/MaintainersCorner When you branch, please remember to let release-team, desktop-devel-list, gnome-doc-list, and gnome-i18n know. Since the git migration, we have automatic notifications for any branch using the standard gnome-MAJOR-MINOR scheme. They go out to release-team, gnome-doc-list, and gnome-i18n. Claude (gnome-i18n) and I (gnome-doc-list) agree that the automatic notifications are sufficient, and we don't need the redundant manual notification. That leaves release-team and desktop-devel-list. (release-team also receives automatic notifications) I haven't been sending my branch notification to d-d-l for a long time, and I think most other developers don't either. I think it's noise on this list. So if nobody objects, I'd like to remove the requirement to send branch notification emails at all. I'll replace it with something to the effect of Ensure that a notification is sent to these lists. If you use a standard branch name, this will happen automatically. If it doesn't, send an email manually. +1. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Branch notifications
Vincent Untz wrote: So if nobody objects, I'd like to remove the requirement to send branch notification emails at all. I'll replace it with something to the effect of Ensure that a notification is sent to these lists. If you use a standard branch name, this will happen automatically. If it doesn't, send an email manually. +1. I am fine with automatic message when it comes to updating jhbuild modulesets but still, the notification emails were opportunities to expose plans for future releases, and that's interesting to all. Certainly if there is nothing to say, there is not much point in posting to the mailing lists with SSIA emails, but if there are plans -- at branching time or whenever the maintainer feels like it -- I love to get them posted on ddl. Cheers, Frederic ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
