Re: Defining GNOME software (finally)

Michael Catanzaro wrote: > > On Mon, Jun 22, 2020 at 11:28 am, Allan Day wrote: > > The board is hoping to vote on this at its meeting later today. I > > don't think that the vote will have a huge impact on the Release > > Team, but if anyone has any reservation

Re: Defining GNOME software (finally)

Hi Release Team, The board is hoping to vote on this at its meeting later today. I don't think that the vote will have a huge impact on the Release Team, but if anyone has any reservations please let us know ASAP. Thanks! Allan On Mon, 15 Jun 2020 at 11:05, Allan Day wrote: >

Re: Defining GNOME software (finally)

Michael Catanzaro wrote: ... > On Mon, Apr 20, 2020 at 1:00 pm, Allan Day wrote: > > 2. We need to bring the definition of that software within the > > umbrella of the Foundation > > > > The basic idea we discussed was to have the Release Team act as a > > com

Re: Defining GNOME software (finally)

Hi everyone, Allan Day wrote: ... > At this point it's probably best for us to share the plan in more > detail and get more feedback... I've posted a more complete proposal on Discourse now - https://discourse.gnome.org/t/official-proposal-how-we-define-gnome-software/3371 . Ple

Re: Defining GNOME software (finally)

Michael Catanzaro wrote: ... > > We've considered this question a bit more on the board side, and think > > we can adjust the policy enough to allow some flexibility around the > > GNOME Gitlab group. I think we would like to see some alignment > > between the modulesets and the group, but it does

Re: Defining GNOME software (finally)

Allan Day wrote: ... > > To make sure we don't have misplaced expectations, please remember that > > this list cannot be used for deciding what repositories go into the > > GNOME/ group on GitLab, because probably 90% of the stuff currently > > there is not core and i

Re: Defining GNOME software (finally)

Michael Catanzaro wrote: ... > > Any suggestions for who should be chair? > > Does it have to be a permanent chair? > > With just one formal meeting per year, this doesn't feel necessary to > me, unless required by the bylaws. Yes, it's required by the bylaws. In some cases the Foundation might a

Re: Defining GNOME software (finally)

Thanks for the reply Michael - very helpful! Michael Catanzaro wrote: ... > So I propose that > we have the wiki page say that the canonical definition of "what is > GNOME?" is the list of BuildStream elements listed in > meta-gnome-core-developer-tools.bst, meta-gnome-core-os-services.bst, > met

Defining GNOME software (finally)

Hi Release Team, Many many moons ago, we had a call about GNOME trademarks and how the project defines its official software. The background to this was that the board has been told that: 1. We need to clearly state what GNOME's official software is, and 2. We need to bring the definition of

Re: Freeze break exception for the new lock screen

Michael Catanzaro wrote: ... > > It is equally not smart to never land the things we've worked on for > > years just because we put ourselves under the pressure of yet another > > deadlne. > > So far this exception has only one of two required approvals. Do you > want to give the second approval?

Re: Freeze break exception for the new lock screen

An initial version of the test plan can be found here: https://gitlab.gnome.org/Teams/Design/os-mockups/issues/44 Allan On Wed, 29 Jan 2020 at 11:38, Allan Day wrote: > > Michael Catanzaro wrote: > ... > > There are many, many, many more like these. Sorry for sending so many &g

Re: Freeze break exception for the new lock screen

Michael Catanzaro wrote: ... > There are many, many, many more like these. Sorry for sending so many > mails to this thread, but I just happen to remember this is a > particularly fragile portion of the codebase. ... Thanks, I'll try and include those in the test plan. I still feel that these is

Re: Freeze break exception for the new lock screen

Michael Catanzaro wrote: > > Would it be possible to arrange a freeze exception for the lock > > screen work, so we can plan on having another week to get it merged? > > We don't expect there to be any new strings and I'm happy to > > coordinate with docs and marketing. > > Certainly possible, but

Freeze break exception for the new lock screen

Hi Release Team, You might be aware that we've had plans for a redesigned lock screen for some time. Development on this has been proceeding this cycle. Some of it has landed already, and the other pieces are close to being ready (see my review here https://gitlab.gnome.org/GNOME/gnome-shell/merge

Release Team presentation at the GNOME Foundation AGM

Hi Release Team, The GNOME Foundation AGM is happening on Saturday, as part of GUADEC, and it would be great to have a short presentation from the release team. Any volunteers to do that? If you want to show slides, please just send me the raw text, preferably no later than Friday lunchtime. Tha

[release-notes] Created branch gnome-3-28

The branch 'gnome-3-28' was created pointing to: 5fb4ab8... Update Turkish translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: Buildstream documentation feedback

Tristan Van Berkom wrote: ... > I've made changes to both the wiki and the BuildStream user manual > installing section, and think I have addressed all of your points > mentioned in this email. Thanks Tristan! From a cursory look, the wiki page seems much better. I'll hopefully provide more feedb

Buildstream documentation feedback

Hi all, Today was my first experience using Buildstream, which I did by following the guide on the GNOME wiki . I got blocked by an issue , but I wanted to provide some notes on my experie

Re: Call with the Board of Directors

Allan Day wrote: ... > An issue has come up which the Foundation Board of Directors needs to > speak to you about. It's a legal thing so I can't provide details here, but > I can fill any of you in privately if you'd like more information. > > It would be great if

Call with the Board of Directors

Hi Release Team, An issue has come up which the Foundation Board of Directors needs to speak to you about. It's a legal thing so I can't provide details here, but I can fill any of you in privately if you'd like more information. It would be great if some of you could join a call next week. I've

Re: 3.26 retrospective

Andre Klapper wrote: ... > > The issue I've identified is large changes landing just before the > > freeze. Typically these large changes require subsequent smaller > > changes to make them release-ready, which often requires close design > > involvement. > > I don't know the best solution either

Re: 3.26 retrospective

Hey Michael, Thanks for your quick reply. Do bear in mind that these are just ideas; I'm happy to discard any that don't make sense! wrote: ... > Extend the UI freeze (or create a freeze period for major UI changes) and >> require that breaks get design approval. >> > > What would extending the

3.26 retrospective

Hi all, I personally found 3.26 to be a difficult release and thought that it might be useful to share some of my experiences, along with some thoughts on how to improve things for next time around. The issues I encountered: 1. We had two big features that landed very close to UI freeze, both

UI/hardcode freeze break request for GNOME Shell

Hi all, This is a break request that changes some visual styling in GNOME shell. The code changes are deliberately minimal. However, the visual change is noticeable. The design team recognise that it is late in the cycle but we'd be unhappy putting the release out in its current state. The bug c

[release-notes] Created branch gnome-3-26

The branch 'gnome-3-26' was created pointing to: ab83e0a... Update French translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

[release-notes] Created branch gnome-3-24

The branch 'gnome-3-24' was created pointing to: 89bf4d5... Update Turkish translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

[release-notes] Created branch gnome-3-22

The branch 'gnome-3-22' was created pointing to: 1021c57... Updated Polish translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

[release-notes] Created branch gnome-3-20

The branch 'gnome-3-20' was created. Summary of new commits: 9c53ba0... prepare for 3.20 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: Moduleset review

It would be great to sync GNOME continuous with the revamped modulesets: I've recently been using continuous to test 3.19.x, and there are quite a few core apps that are missing (as well as some not so interesting apps that are included). Allan On Thu, Feb 4, 2016 at 10:32 AM Allan Day

Re: Moduleset review

PM, Michael Catanzaro wrote: ... > I've just landed this. It got delayed a bit as I found I had broken a > few things. Thanks for taking it forward, Michael! Allan ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-

Re: Moduleset review

Michael Catanzaro wrote: > On Mon, 2016-01-11 at 18:37 +, Javier Jardón wrote: >> This has been merged now > > Thanks for working on this, Javier; I think our modulesets are much > better now. I posted a follow-up patch for the metamodules here: And thanks to you for doing a much more thoroug

Re: Test days

For what it's worth, I have 22 February and 7 March in my calendar as test days. I'll probably informally ask people if they want to join me, at the least. Allan On Thu, Nov 26, 2015 at 4:36 PM, Sriram Ramkrishna wrote: > > > On Thu, Nov 26, 2015 at 8:30 AM Allan Day wrote:

Re: Test days

Javier Jardón wrote: ... >>> [1] https://bugzilla.gnome.org/show_bug.cgi?id=750726 > > Seems Andrea from sysadmin team is going to take a look this weekend Fantastic news! Looking at the calendar, I'm wondering about doing two explicit rounds of testing: one a week after UI freeze is scheduled,

Re: Test days

Javier Jardón wrote: ... > Great idea, but I think first we should fix the generation of ISO > images from continuous [1] so the people can test the latest. Not sure > what is blocking that fix Or perhaps setting the test days would help to put pressure on these issues? Is there anyone other than

Test days

Hi all, We didn't do very well with testing last release. I'm going to set myself a few reminders to do testing this cycle. But this got me wondering whether this should be something that's on the release schedule? That way we could use the opportunity to invite other contributors to do their own

Re: Signing apps on Google Play store

Frederic Peters wrote: ... > I still have no idea on technical details, and I'm still reluctant on > releasing an .apk we would receive, no question asked... I'm in favour of us releasing this app under a GNOME account. However, I also agree that we should decide what kind of quality controls wou

Re: Google Play account

Ankit wrote: > I've put GeoclueShare in the wiki: https://wiki.gnome.org/Apps/GeoclueShare Thanks for this, Ankit! Looks very nice, and there is a lot of useful information on there. If this page is going to help members of the GNOME community get involved with the app, one thing it probably nee

Release code names

Hi all, I'm working on the release notes for 3.18, and I will also be working on release promotion. During GUADEC, the board and Release Team agreed to name September release after the GUADEC host city, and each March release after the GNOME.Asia host city. I have some questions about this: 1. I

Re: Google Play account

Zeeshan Ali (Khattak) wrote: ... > Release team is usually pretty busy and thin on resources so I'm not > sure if they could take more work/responsibility on their shoulders, > but I'll ask (adding to CC). Dealing with these kinds of issues is why we have a Release Team. >> A good starting point

[release-notes] Created branch gnome-3-18

The branch 'gnome-3-18' was created pointing to: fd2841a... Updated Turkish translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: 3.18 topics: application revival

Hi all, Just a quick message to let you know that I haven't forgotten about this discussion. Since we last talked, I've been working with Jakub and the relevant maintainers to draw up roadmaps for each of the priority apps. I'm now doing some publicity work around these, through a series of blog p

Empathy/Telepathy Future

Hi all, We've recently discussed this in a different thread, but I thought that it probably deserves one of its own. In short: Empathy and Telepathy haven't got development time for quite a while, and the Empathy UX isn't great. At the same time, popular chat protocols are mostly closed nowadays,

Re: 3.18 topics: application revival

Frederic Peters wrote: ... >> 4) A "GNOME apps" hackfest. >> >> 5) A "GNOME apps" online sprint - come up with a list of bugs and get >> designs in place. Advertise for volunteers and have people ready to >> review bugs. > > I have experimented a bit today[1] and I'd like to add a middle ground >

Re: 3.18 topics: application revival

Matthias Clasen wrote: ... > Maybe we do something to improve this situation, from the release team > ? Some ideas I had: > > 1) Patch review days - ask the community to spend a day focused just > on bugs and patches of one app, with the goal of working through the > backlog and making visible pro

Re: Let's not do feature proposals for 3.17.x

I've put the new page under ReleasePlanning, and filled in some features that are in the works for 3.18: https://wiki.gnome.org/ReleasePlanning/FeaturePlans Allan ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-te

Let's not do feature proposals for 3.17.x

No one's really following the feature proposal process, and it's not doing us any good. When we last discussed this, Matthias said that it would be good to replace the existing process with something that lets people (particularly distros) know what to expect from each release. My suggestion woul

[release-notes] Created branch gnome-3-16

The branch 'gnome-3-16' was created pointing to: b55779b... Initial Hungarian translation from 3-12 branch ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Minor UI freeze break - bug 745095

Hi all, With the notification redesign landing so late, it had some rough edges in certain places. I'd like to land a small CSS patch to take care of some of those. Bug 745095 [1] has the details, including before and after screenshots [2]. Thanks, Allan [1] https://bugzilla.gnome.org/show_bug.

Re: Initial List of 3.16 Target Bugs

Andre Klapper wrote: > Just commenting on term confusion; no other content. ... >> I've been using gnome-version to mark project level priorities. > > I think/hope you mean "GNOME Target". > Because "GNOME version" does not have a 3.15/3.16 entry yet (and is not > meant for planning but desribes i

Re: Initial List of 3.16 Target Bugs

Andre Klapper wrote: > On Sun, 2014-11-23 at 22:11 +, Javier Jardón wrote: >> But I think it would be good to ping the maintainers to suggest them >> to put the GNOME target field in the bugs we think are important, so >> we know which ones are willing to work on the problem for the next >> re

Initial List of 3.16 Target Bugs

Hi all, I've been busy putting together a list of target bugs for 3.16. You can see them here: https://bugzilla.gnome.org/buglist.cgi?cf_gnome_target=3.16;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO Keeping the list to a

Re: New release processes

Hi all, Sorry that I let this slip. I had to take some time out, and am just getting back into things. I've started a draft list of issues that we could track for 3.16, please feel free to add to it: https://wiki.gnome.org/AllanDay/ThreePointSixteenTargetBugs Shall we have a meeting to discuss t

Permission to come aboard

Hi all, I'd like to join the Release Team. I'll need to be included in meetings and be able to change the gnome-target on bugs for the UX quality initiative we discussed recently. But I think I can also be of help more generally. Let me know what you think, Allan

Re: New release processes

Allan Day wrote: ... >> Then we can have a meeting and build list between all of us. >> Should we arrange the meeting time already? what about at some point >> just after the 3.14.1 release? > ... > > Sounds great to me. 3.14.1 is scheduled for release on 13 October.

Re: New release processes

Javier Jardón wrote: ... >> * Identify priority bugs at the start of the cycle. Allow people to >> suggest their own bugs. > > Yeah, lets allow maintainer to set the gnome-target in their modules. > I think we already allow this. I think they can set target-milestone (not gnome-target). That cou

Re: New release processes

Matthias Clasen wrote: ... > Right, so here is what I suggest we could do to avoid a repeat of the > feature proposal fiasko from last cycle: > > Instead of clamoring for feature proposals on desktop-devel-list, we, > as the release team could go out and suggest waht we think would be > great feat

Re: New release processes

Allan Day wrote: ... > Here's my attempt to summarise the processes that we discussed in > yesterday's meeting. I've had to fill in some gaps and make some > guesses. It's very much a draft. ... I was hoping that we would push forward with these new processes for

Re: To Do List

Allan Day wrote: ... > It should probably be merged into: > > https://wiki.gnome.org/ReleasePlanning/Tasks ... I just did it. Feel free to revert though. Allan ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-tea

To Do List

Hi all, I was struggling to figure out what was outstanding after the BoF at GUADEC, so I converted the notes into a task list on the wiki: https://wiki.gnome.org/ReleasePlanning/ToDo I know there's a risk of this going stale. It's only really of use if there's going to be RT meetings where the

Re: cleaning up categories

Frederic Peters wrote: ... > At GUADEC we discussed cleaning the various categories we have for our > modules, to make things more understandable and to share things > between our various services. ... > Where do we go from here? Sorry for not replying to this sooner, Fred. I was a bit confused a

[release-notes] Created branch gnome-3-14

The branch 'gnome-3-14' was created pointing to: 407c2c0... OPW-Updated Greek translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: moduleset review

Javier Jardón wrote: ... >> https://wiki.gnome.org/AllanDay/Modulesets > > Thanks for working on this! > > Only wanted to point that gnome-suites-core-deps contain the dependencies for > core, not only non-GNOME dependencies (GTK+ and GLib are there for example). > Maybe we can be more strict and

Re: moduleset review

Allan Day wrote: >>> 2) Drop gnome-system-log from core-apps, replace with gnome-logs >>> 3) Move gnome-dictionary, gucharmap, totem, eog, empathy, evince to apps >>> 4) Move file-roller, gnome-clocks, gnome-documents, gnome-photos, >>> gnome-weather to core-a

Re: moduleset review

Javier Jardón wrote: ... >> 2) Drop gnome-system-log from core-apps, replace with gnome-logs >> 3) Move gnome-dictionary, gucharmap, totem, eog, empathy, evince to apps >> 4) Move file-roller, gnome-clocks, gnome-documents, gnome-photos, >> gnome-weather to core-apps > > Before move stuff, Id lik

New release processes

Hi all, Here's my attempt to summarise the processes that we discussed in yesterday's meeting. I've had to fill in some gaps and make some guesses. It's very much a draft. One issue that we didn't agree on during the BoF - I've moved the governance (ie. when the Release Team has a formalised oppo

Re: status icon freeze break request

Any update on this? I'm going to be taking screenshots for the release notes later, and it would be good to know whether the icon updates will make it into the final release. Allan On Mon, Mar 17, 2014 at 2:40 PM, Matthias Clasen wrote: > On Mon, Mar 17, 2014 at 10:32 AM, Jakub Steiner wrote: >

Re: status icon freeze break request

Andre Klapper wrote: ... > Clueless as I haven't seen a before/after screenshot, but we're not > talking about stuff like > https://git.gnome.org/browse/gnome-user-docs/plain/gnome-help/C/figures/network-error-symbolic.svg?h=master > ? These icons are for the offline/disconnected states for mobil

Re: status icon freeze break request

Ekaterina Gerasimova wrote: ... > Screenshots are the most labour intensive part of docs to update, both > for the docs team and translators. If it affects the wireless network > icon, then I would prefer for the change to wait until after the > release as we're running out of time now. As previo

Re: status icon freeze break request

Matthias Clasen wrote: > Will this affect screenshots taken for the release notes ? I guess we > don't usually take those while offline. I don't think it will. Having a decision on this freeze break will possibly help us decide what to take shots of though. Jakub Steiner wrote: >> I'd like to r

[release-notes] Created branch gnome-3-12

The branch 'gnome-3-12' was created pointing to: 65a51ae... Added Greek translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Re: Intent to ask for freeze break

Shaun McCance wrote: ... >> This is just a heads-up that, if I can manage to get everything done >> this weekend, I intend to ask for a freeze break to implement Allan's >> designs for Yelp: ... > Not happening. Too much left to do, too unstable, and too many design > questions still unanswered. W

Re: Module Organisation

Matthias Clasen wrote: > Currently, we have the following metamodules in jhbuild: > > meta-gnome-core > meta-gnome-core-shell > meta-gnome-core-extras > meta-gnome-core-utilities > meta-gnome-core-os-services > meta-gnome-devel-platform > meta-gnome-extended-devel-platform > meta-g

Module Organisation

Hi all, I often find it hard to figure out which module lives where, and I think that consistently organised modules would help people to understand what we are trying to build. In terms of what we are building, there are three primary classifications of modules: * Core * Core apps * Apps Th

Re: Freeze Break Request: Session Menu Heading

Matthias Clasen wrote: >>> Im not a designer, but should the "Session" entry exist at all? >>> Anyway, Its a small change, so 1/2 for release team >> >> Ha, yes. I think you're right. Let's say we'll just remove it. I'm >> assuming we still have your +1. :) >> > > +1 to putting the lost styling ba

Re: Freeze Break Request: Session Menu Heading

On Thu, Aug 29, 2013 at 8:59 PM, Javier Jardón wrote: > On 29 August 2013 20:43, Allan Day wrote: >> Hi everyone, >> >> We've got a small cosmetic change that we'd like to make. The session >> menu in the login screen was changed in 3.10. Unfortunately, the

Freeze Break Request: Session Menu Heading

Hi everyone, We've got a small cosmetic change that we'd like to make. The session menu in the login screen was changed in 3.10. Unfortunately, the "Session" heading lost its styling, so it looks like a regular menu item. The change simply involves making "Session" bold. Here's a screenshot from

[release-notes] Created branch gnome-3-10

The branch 'gnome-3-10' was created pointing to: 4772b70... Updated Brazilian Portuguese translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Freeze Break Request: System Icon Spacing

Hi everyone, This is a very small visual change, which will only impact screenshots. Details are in the bug report [1], including a before and after screenshot (before is on top): https://bug706796.bugzilla-attachments.gnome.org/attachment.cgi?id=253131 Thanks, Allan [1] https://bugzilla.gnom

Re: A first look at 3.10 blockers

I've had a quick look, and these are some of the bugs I'd like to have on the blocker list: 691316 photos - no minimum size set 700726 music - only checks for new music at start 696166 control-center - have lock screen curtain background configurable 691187 control-center - Battery life estimation

Re: shell freeze break request

Matthias Clasen wrote: > Looks like a step in the right direction - but I feel that we probably > need some more here. But I'm fine with taking this change for 3.7.92. I agree. This is meant as a short term fix for 3.8. We can look at it again for 3.10. Allan -- IRC: aday on irc.gnome.org Blog:

Re: Freeze break request for bug 694796

Michael Hill wrote: > +1 from docs team. > > Mike Thanks Mike! I've pushed the fix. Allan -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team

Re: Freeze break request for bug 694796

Frederic Peters wrote: > Allan, ideally you should make sure patches are marked as reviewed and > accepted before asking for freeze breaks; as I am not sure the comment > Rui made came after your request. Sorry, I hadn't realised that. I'm not usually the one filing the patches. :) Thanks Fred!

[release-notes] Created branch gnome-3-8

The branch 'gnome-3-8' was created pointing to: 9a8ae8a... Revert "Add Esperanto translation" ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.

Freeze break request for bug 694796

Hi all, We've introduced new iBus character popups this cycle - these are the menus that let you choose different characters when using an input method. We got some early feedback that we'd like to address with these, basically by changing how the popups are themed. This is tracked in bug 694796 [

Re: 3.8 Release Notes Writing

Andre Klapper wrote: > [Not CC'ing marketing-list@ yet] > > It's time to start preparing the GNOME 3.8 release notes. > > I won't have time to help this year, but maybe I can help out with some > smaller sections. > > Had a quick chat with Allan Day (

Re: Fallback mode is going away - what now ?

Florian Müllner wrote: ... >>> The Tweak Tool shouldn't have anything to do with extensions. They are >>> something that you install and run as a part of the system, not >>> something to be "tweaked" via settings. > > While I agree with you that gnome-tweak-tool (and package managers > (*)) are no

Re: Fallback mode is going away - what now ?

Matthias Clasen wrote: >> to be fair, I'd envision this as a completely separate session that >> you need to install and select, similar to what Ubuntu does — >> especially if we want to call it "GNOME Classic". Agreed. > I don't think a separate session will work very well for this - for > one

Re: live image

Hey Ray, Ray Strode wrote: ... > I put together a live image with a jhbuild built in it here: > > http://ftp.acc.umu.se/pub/gnome/misc/testing/GNOME-3.5.1-LiveUSB.iso ... > It's a little hacked together, at the moment.  I'd like to get the > process I used more refined and potentially automated s

Re: GNOME Shell Modal Dialog Tweakage

On Mon, Mar 12, 2012 at 2:21 PM, Shaun McCance wrote: > On Mon, 2012-03-12 at 10:40 +0000, Allan Day wrote: >> The first is the apparent lack of consensus. I was following what I >> understood to be good practice, and even went out if my way to be >> considerate toward

Re: 3.4 Release Notes

On Fri, Mar 9, 2012 at 3:53 PM, Vinicius Depizzol wrote: > On Thu, Mar 8, 2012 at 18:53, Sriram Ramkrishna wrote: >> >> My main objection would be translation.  One of the problems is that I would >> like to see our content/news/release notes translated so that we can have >> greater coverage.  I

Re: GNOME Shell Modal Dialog Tweakage

On Sun, Mar 11, 2012 at 1:02 AM, Shaun McCance wrote: > Replying to two in one, to save electrons. > > On Sat, 2012-03-10 at 13:03 -0500, Matthias Clasen wrote: >> On Sat, Mar 10, 2012 at 9:49 AM, Allan Day wrote: >> >> >> >> Now, if we want to define and w

Re: GNOME Shell Modal Dialog Tweakage

On Sat, Mar 10, 2012 at 2:35 PM, Shaun McCance wrote: >> I'd also add that one sentence is not an adequate amount of guidance >> for this process. > > The sentence looks clear to me. It doesn't say "maybe" or "only major" > or "at your discretion". It says "No UI changes". > > "No UI changes may b

Re: GNOME Shell Modal Dialog Tweakage

On Sat, Mar 10, 2012 at 11:13 AM, Andre Klapper wrote: > On Fri, 2012-03-09 at 18:36 +0000, Allan Day wrote: >> And yet there is also an understanding that minor cosmetic changes >> don't need a UI freeze exception. > > https://live.gnome.org/ThreePointThree#Schedule sa

Re: GNOME Shell Modal Dialog Tweakage

On Fri, Mar 9, 2012 at 4:55 PM, Shaun McCance wrote: > On Fri, 2012-03-09 at 11:33 -0500, Matthias Clasen wrote: >> On Fri, Mar 9, 2012 at 10:48 AM, Andre Klapper wrote: >> > Hi Allan, >> > >> > On Thu, 2012-03-08 at 18:50 +, Allan Day wrote: >>

Re: GNOME Shell Modal Dialog Tweakage

On Fri, Mar 9, 2012 at 3:48 PM, Andre Klapper wrote: > Hi Allan, > > On Thu, 2012-03-08 at 18:50 +0000, Allan Day wrote: >> I've just pushed a minor change to the GNOME Shell theme [1]. This is >> a small visual change [2, 3], and it doesn't >> affect anyt

Re: 3.4 Release Notes

On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna wrote: > > > On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper wrote: >> >> >> I was thinking of switching from Docbook to Mallard for 3.6 (I didn't >> have time to prepare this for 3.4 already). >> The advantages of "GNOME 3 page style" are unclear

Re: 3.4 Release Notes

Thanks for kicking this off, Andre! I'll be sure to chip in where I can. My last blog post [1] might be useful, too. Now, a question. We typically keep the release notes secret until the release itself. At least one member of the press has told me that this makes it quite difficult for him to cove

Re: 3.2 Release Notes: Featured Apps

On Sun, Sep 11, 2011 at 11:58 AM, Olav Vitters wrote: > On Wed, Sep 07, 2011 at 01:43:33PM +0200, Olav Vitters wrote: >> I'll also try and assist in the release notes. I'll assist, so if you >> (Andre/Alan/sri) think something I wrote is bad, just change please. > > I've changed loads of things. S

Re: Power settings ui freeze break request

On Fri, Sep 2, 2011 at 6:00 PM, Bastien Nocera wrote: > On Fri, 2011-09-02 at 18:51 +0200, Frederic Peters wrote: >> Matthias Clasen wrote: >> >> > On Thu, Sep 1, 2011 at 10:57 AM, Shaun McCance wrote: >> > > On Thu, 2011-09-01 at 15:41 +0100, Allan Day wrote:

Re: Power settings ui freeze break request

On Thu, Sep 1, 2011 at 2:01 PM, Shaun McCance wrote: > On Thu, 2011-09-01 at 12:12 +0100, Allan Day wrote: ... >> The new design has been reviewed by several members of the design >> team. I've checked the user documentation and, from what I can tell, >> these changes

  1   2   >