Re: Gitlab hosting - Fwd: Transmitter - GUI for transmission-daemon and transmission-remote

2018-01-02 Thread Emily Gonyer 
On Tue, Jan 2, 2018 at 10:17 AM, Felipe Ferreira da Silva
 wrote:
>> Since Sébastien brought this up.
>>
>> Do we want to advertise hosting space if people are thinking of writing
>> GNOME applications as part of a greater desire to create a more solid
>> GNOME/GTK+ developer community?
>>
>> Advantages are that we would be more active in what our developers are
>> writing and see problems with development.  There would also be a path for
>> more maintainers in parts of the eco-system.  Also a place for new designers
>> to find tasks to do.
>>
>> The engagement/marketing team could start reaching out to developers to
>> host their GTK+/GNOME project there.  The only issue would be to understand
>> the costs of hosting as that could be problematic in the long term.  It
>> could be a great problem to have provided we have stable funding sources.
>>
>> Thoughts?
>>
>> sri
>
>
> Having a hosting space for potential GNOME apps certainly would attract a
> developer community, I believe.
>
> If hosting space is an issue, at least a single space where developers and
> designers could add a link and description to their project could energize
> these developers/designers to be more active on the GNOME community. Nothing
> like having your project receiving some attention ;)
>
> Felipe Ferreira da Silva
>
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Issues with hosting space seems like the only reason to not do so, but
if funds can be found to provide such, it seems like a great way to
build community and attract developers. Asking for space (or money to
provide it) may also be a great way to get funding, with easily
observable results. Perhaps Google, Red Hat or Canonical would be
interested in funding?

Emily


-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Every step is a first step if it's a step in the right direction. -
Sir Terry Pratchett
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: jhbuild

2012-12-24 Thread Emily Gonyer 
try sudo apt-get install wireless-tools libicu-dev - they are in
ubuntu's repos and should be a new enough version.

On Mon, Dec 24, 2012 at 8:29 AM, Lanoxx lan...@gmx.net wrote:
 Hi,

 I have already run jhbuild sysdeps --install, and also ran jhbuild build
 anjuta, with the first one I get this output:

 I: Using apt-file to search for providers; this may be slow.  Please wait.
 I: No native package found for alsa (/alsa.pc)
 I: No native package found for libv4l (/libv4l2.pc)
 I: No native package found for gl (/gl.pc)
 I: No native package found for libicu (/icu-i18n.pc)
 I: No native package found for soundtouch (/soundtouch-1.4.pc)
 I: No native package found for gmime (/gmime-2.6.pc)
 I: No native package found for exiv2 (/exiv2.pc)
 I: No native package found for taglib (/taglib.pc)
 I: No native package found for wavpack (/wavpack.pc)
 I: No native package found for libusb1 (/libusb-1.0.pc)
 I: No native package found for libatasmart (/libatasmart.pc)
 I: No native package found for xcb-dri2 (/xcb-dri2.pc)
 I: No native package found for libvpx (/vpx.pc)
 I: No native package found for libzeitgeist (/zeitgeist-1.0.pc)
 I: No native package found for libarchive (/libarchive.pc)
 I: No native package found for cairomm (/cairomm-1.0.pc)
 I: No native package found for exempi (/exempi-2.0.pc)
 I: No native package found for libmusicbrainz (/libmusicbrainz5.pc)
 I: No native package found for libgphoto2 (/libgphoto2.pc)
 I: No native package found for texinfo (/usr/bin/makeinfo)
 I: No native package found for wireless-tools (/usr/include/wireless.h)
 I: No native package found for gdbm (/usr/include/gdbm.h)
 I: No native package found for libdb (/usr/include/db.h)
 I: No native package found for cracklib (/usr/include/crack.h)
 I: No native package found for mpfr (/usr/include/mpfr.h)
 I: Nothing to install

 and with the second one I get this output:


 Required packages:
   System installed packages which are too old:
 (none)
   No matching system package installed:
 wireless-tools (required=25)
 libicu (icu-i18n.pc, required=4)
 jhbuild build: Required system dependencies not installed. Install using the
 command 'jhbuild sysdeps --install' or to ignore system dependencies use
 command-line option --nodeps

 The problem seems to be, that my system does not have the required packages
 (or rather they are there but the version is too low). So I am hoping that I
 can install the required dependencies (especially libicu and wireless-tools)
 with jhbuild somehow? The problem with libicu is for example that Ubuntu
 ships the version 4.1.1-8 but I need 4.1.1-10 otherwise the .pc files are
 missing).

 Kind Regards and merry christmas
 Lanoxx


 On 24/12/12 12:52, Sébastien Wilmet wrote:

 Hello,

 On Sun, Dec 23, 2012 at 09:53:36PM +0100, Lanoxx wrote:

 I am using jhbuild and trying to compile anjuta (with anjuta-extras)
 to test a patch that was applied recently on anjuta-extras.

 jhbuild build

 The gnome-love list would have been a better place, but anyway, you must
 mention the module you want to build:

 $ jhbuild list anjuta
 $ jhbuild build anjuta

 Or add it in your ~/.jhbuildrc.

 Best regards,
 Sébastien


 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: jhbuild

2012-12-23 Thread Emily Gonyer 
IME that means you need to go through and find all of those packages -
my suggestion is to install Synaptic (sudo apt-get install synaptic)
and then search for each of the listed packages and install -
preferring -dev packages when available.

Emily

On Sun, Dec 23, 2012 at 3:53 PM, Lanoxx lan...@gmx.net wrote:
 Hi,

 I am using jhbuild and trying to compile anjuta (with anjuta-extras) to test
 a patch that was applied recently on anjuta-extras.

 When I run jhbuild build, then I get a huge list of missing system
 dependencies:

 jhbuild build
 W: network-manager-applet has a dependency on unknown
 mobile-broadband-provider-info module
 W: epiphany has a dependency on unknown libwnck3 module
 Required packages:
   System installed packages which are too old:
 (none)
   No matching system package installed:
 wireless-tools (required=25)
 alsa (alsa.pc, required=1.0.19)
 gl (gl.pc)
 cairomm (cairomm-1.0.pc, required=1.8.4)
 cracklib
 gmime (gmime-2.6.pc, required=2.6.6)
 exiv2 (exiv2.pc, required=0)
 libdb
 gdbm
 soundtouch (soundtouch-1.4.pc, required=0)
 taglib (taglib.pc, required=1.5)
 texinfo
 wavpack (wavpack.pc, required=4.2)
 libusb1 (libusb-1.0.pc)
 libatasmart (libatasmart.pc, required=0.17)
 libv4l (libv4l2.pc)
 xcb-dri2 (xcb-dri2.pc, required=1.8.1)
 libvpx (vpx.pc)
 libzeitgeist (zeitgeist-1.0.pc, required=0.3.18)
 mpfr
 libarchive (libarchive.pc, required=2.8.0)
 libicu (icu-i18n.pc, required=4)
 jhbuild build: Required system dependencies not installed. Install using the
 command 'jhbuild sysdeps --install' or to ignore system dependencies use
 command-line option --nodeps

 I have already ran sanitycheck and bootstrap successfully? My OS is Ubuntu
 12.10.

 Best Regards
 and Merry Christmas
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Fallback mode is going away - what now ?

2012-11-21 Thread Emily Gonyer 
On Wed, Nov 21, 2012 at 9:11 AM, Debarshi Ray rishi...@lostca.se wrote:
 It won't go in the Settings.

 Why not? Why was the forced fallback in Settings instead of the Tweak Tool
 in the first place?

+1


 Cheers,
 Debarshi

 --
 There are two hard problems in computer science: cache invalidation, naming
 things and off-by-one errors.

 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Fallback mode is going away - what now ?

2012-11-21 Thread Emily Gonyer 
On Wed, Nov 21, 2012 at 9:56 AM, Matthias Clasen
matthias.cla...@gmail.com wrote:
 On Wed, Nov 21, 2012 at 9:50 AM, Emmanuele Bassi eba...@gmail.com 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.

 I don't think a separate session will work very well for this - for
 one thing, setting this up will require a number of settings to be
 tweaked (e.g. the one for the minimize button), and alternative
 sessions don't have the right infrastructure for that. The session
 chooser on the login screen is not the best designed part of the login
 experience either. And finally, if Ubuntu calls their pristine GNOME3
 session 'GNOME Classic', what would we call this one, GNOME Classic
 Plus ?!

Ubuntu calls GNOME Shell session just GNOME for reference... GNOME
Classic is fallback mode.

Otherwise I agree - I don't think this should be a seperate session,
but a simple change in settings, a button or toggle somewhere in
settings to make gnome-shell a more traditional desktop.


 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GnomeGoal for 3.8: DesktopFileKeywords

2012-11-16 Thread Emily Gonyer 
I think that's a great point. Being able to type in 'games' or
'internet' or 'office' and seeing a list of applications in that
category would be fantastic.

Emily

On Fri, Nov 16, 2012 at 9:57 AM, Jeremy Bicha jbi...@ubuntu.com wrote:
 On 14 November 2012 19:05, Jeremy Bicha jbi...@ubuntu.com wrote:
 On 4 November 2012 22:22, Matthias Clasen matthias.cla...@gmail.com wrote:
 We've had good success with 'adopting' a few GnomeGoals[1] as official
 targets for 3.6, and we want to repeat this for 3.8.

 And here are new goals that we want to tackle this cycle:

 DesktopFileKeywords - add a Keywords field to desktop files, to
 improve gnome-shell search for applications. This goal doesn't require
 any programming skills.

 And one more suggestion: should GNOME Shell look at the Categories
 field too? Specifically, typing in game doesn't really return
 results now, even though the Games menu heading has several games
 installed. Since most games available are not GNOME games, it may take
 us a while before developers think about adding the Keywords field.

 Jeremy
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: taking features away (compact view removed from Nautilus)

2012-07-02 Thread Emily Gonyer 
On Mon, Jul 2, 2012 at 4:38 AM, Allan Day allanp...@gmail.com wrote:
 Adam Dingle a...@yorba.org wrote:
 I realized recently to my surprise and dismay that the compact view has been
 removed from Nautilus:

 Adam, if you wanted to discuss this change, you could have done so on
 the bug or on the Nautilus mailing list, or by asking on
 #gnome-design. I would have been happy to have given you some
 background on why the decision was made.

 Jon has been doing some fantastic work on Nautilus recently. It was
 getting very little - if any - developer attention and he has stepped
 up to make dramatic improvements, including addressing long-standing
 complaints. I'm really excited about the next release of Nautilus
 thanks to his work; instead of having no movement whatsoever, we are
 going to have lots of great improvements to talk about.

 There has been a bunch of discussion around these changes. Not the
 mailing list approach that you seem to want, but the existing Nautilus
 maintainers have been involved and a range of design people have been
 consulted. I personally agreed with removing compact view - I think
 it's a good change.

 ...
 I'd like to end on a constructive note.  I propose that GNOME adopt the
 following policy.  No major feature will be removed from a core GNOME
 application before a discussion has occurred on a public mailing list such
 as this one (or on a Bugzilla bug, with a prominent mailing list
 announcement pointing to the bug in question).  I also propose that all such
 feature removals that have occurred in the 3.6 development cycle be reverted
 until such discussion has occured .

 I strongly disagree with that suggestion. I don't think it would be
 workable, and I don't think it would make GNOME a better place to
 work. There is still time to discuss changes that have been made; we
 don't need to wrap ourselves up in policies.

 The features in core GNOME apps are the result of years of hard work and
 consensus building by our community.
 ...

 There is no consensus. There are features that some people have gotten
 used to, and there has been a long period of adding features without
 considering how they fit into the whole.

 No one objects when you add a feature, yet features can ruin a design
 if you keep adding them. Nautilus has been at saturation point for a
 while; it's at the stage where it's actually very difficult to improve
 it without taking something away.

 Allan
 --
 IRC:  aday on irc.gnome.org
 Blog: http://afaikblog.wordpress.com/
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Then I guess the question becomes how we can involve the greater GNOME
 community in these sorts of decisions. Existing designers and
 developers may have been consulted, but they are not the only ones
 affected. The choices that a handful of people are making affect
 everyone who uses GNOME, though the community is rarely consulted or
 even notified until the change has been made and all but finalized. I
 suspect that I am not the only one disturbed and disappointed by what
 seem like rapid changes to existing projects without public
 discussion. If there was discussion regarding the removal of compact
 view and later icon mode with text, I'd like to know when and where it
 occurred as well as when and where I should keep an eye out for future
 changes and removals.

 As I understand it (and I'm rather new to the development community,
 so I may be wrong), adding features, new modules, etc to GNOME is an
 often lengthy (and perhaps more importantly, transparent) process of
 proposal, review, design and re-design, which seems proper. It serves
 to keep GNOME running smoothly and the community at large involved in
 development. Unfortunately though, the process for removing features
 doesn't appear to be nearly as robust and/or transparent.

 A handful of developers and/or designers talk amongst themselves and
 decide to remove features without consulting the community at large.
 As a result changes like the ones above occur rapidly over an hour or
 perhaps a day, without any sort of public discussion or even
 notification (aside from postings on bugzilla and git, which
 apparently occur after discussion). And then on release day we are
 surprised that feature XYZ has been removed. Since the removal
 occurred a month or more back, we are told that we had ample time to
 disagree and since we failed to do so, tough luck. However, since the
 removals are done quietly without so much as a blog posting this seems
 disingenuous at best - even when posters replied within a few hours
 [1] to the change on bugzilla, they were all but ignored (at least
 publicly) by those affecting the change.

 I have long been under the impression that since GNOME is a free
 software project, development is (or at least should be) done in a
 public, transparently and with inclusion as a

Re: Design in the open

2012-05-04 Thread Emily Gonyer 
As someone who is just starting to become involved in design  development
after many years of using open source  free software, I find these
discussions fascinating on multiple levels. For whatever reason I have
always found communities in free/open source software to be rather
intimidating, which is probably why its taken me so long to become
involved. I suspect this is true for many people, and I fully support
anything and everything that makes it easier for people to become involved
and thereby feel connected to the project.

The article was definitely interesting and as I think about it more and
more, I can certainly see how developing a 'planning language' would be
helpful to GNOME. With that in mind, I suspect a first step would be to
start a wiki page of GNOME Design Terms, with a list of terms and their
(community-defined) definitions in relation to GNOME Design. Examples can
be added as development proceeds, until we end up with a wiki page
explaining our 'planning language' which we can point new people to when
they are becoming involved. Such a page/language would certainly streamline
and simplify the design process, and allow new (potential) contributors to
write proposals and suggestions in a way that makes it easier for everyone
to understand and critique them.

Another idea would be to begin giving users a simple way to provide
feedback on what they prefer in design. This could be done via a GNOME
Design Blog or similar, where posts focus on upcoming features along with
examples to be voted on – do users prefer buttons/menus/etc that look like
X, Y, or Z? Should we remove minimize/maximize/close buttons? Do users want
a journal? How important is privacy to you? Etc. Require users to register,
and when they do so ask if they'd like to sign up for a (weekly? monthly?)
news letter regarding the ongoing development of GNOME and related
technologies/applications, as well as new polls, blog posts, etc.
Essentially, create a new level of GNOME membership, below the Foundation
level, with a much lower bar for inclusion – require only a name and a
(verified) email address – and allow almost anyone to participate in the
ongoing discussions and development of GNOME.


Emily

On Fri, May 4, 2012 at 1:03 AM, Diego Escalante Urrelo die...@gnome.orgwrote:

 On Thu, May 3, 2012 at 5:19 PM, Federico Mena Quintero
 feder...@gnome.org wrote:
 
  As a way to solve these issues, I'd like to follow up on an idea which I
  sketched during last year's Desktop Summit - namely, about constructing
  a pattern language for Gnome's design based on the good things that what
  we have and what other systems have done well.

 This. +1.

 From my experience on film stuff, having a way to refer to those
 things that look good or bad is essential to have collaboration
 between different specialists.

 Framing shots would be impossible if there wasn't an abstract way of
 describing them (flat/deep, warm/cold, lenses, etc).

 Sound designers/editors, photography directors, even actors, need to
 be aware of this language for efficient communication during
 production.

 I have been thinking lately that film making has many similarities
 with Free Software development. Being both abstract things with an
 audiovisual result that involves many different specialists.

 A common language of patterns is an awesome idea. I'd encourage
 Federico to expand on the subject.
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/desktop-devel-list




-- 
Whatever you can do, or dream you can, begin it. Boldness has genius, power
and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that counts
can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Module Proposal: Zeitgeist

2012-05-03 Thread Emily Gonyer 
You know, when I first stumbled on zeitgeist running on my system a year or
so ago, I didn't know what in the world it was doing, although it appeared
to be logging... something. And I think I probably forced it to quit out of
pure habit, before going online to figure out what it was actually doing.
For the next few months I was pretty ambivilant about having it logging
stuff on my system, and continued to kill it occasionally without really
know what it was doing :p. And then I realized something - its actually
quite useful. By keeping *ALL* logging in one place, it makes it much
easier to keep track of, and also much easier to make sure that only those
applications, etc which you want to be logged are actually logged. Of
course, this is made immeasurabley easier w/ the awesome privacy settings
in Ubuntu 12.04 (I'm honestly not sure - does such a thing exist in other
distros?).

Anyhow, to the point at hand...  With GNOME-Clocks, having zeitgeist keep
track of alarms, timers, etc makes sense since it allows users to close
clocks when not in direct use, thereby saving resources while also keeping
their alarms/timers/etc in place. The same I imagine is true for
Epiphany/Web as well as many other programs. It also of course enables
users to easily erase logs if/when they so choose, which is, IMHO just as
important these days as keeping logs in the first place, if not more so.

Emily

--
Whatever you can do, or dream you can, begin it. Boldness has genius, power
and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that counts
can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.6 Feature: Totem - Videos

2012-04-24 Thread Emily Gonyer 
I really like web and agree that adding torrent support would be awesome,
but a larger priority for me is more options for privacy/cookie handling.
As it is the only options (at least, that I see) are to accept all cookies,
only those from sites you visit, or none. No options for deleting cookies
when you close web, or even for accepting cookies on a per-cookie-basis as
in most every other browser, or for deleting single cookies (you can only
clear them all at once - an even that option is slightly hidden away).
Otherwise, I really like web - its lightweight and quite fast, even
compared to my long-time favorite browser Opera :)

Emily

On Tue, Apr 24, 2012 at 7:36 AM, Piñeiro apinhe...@igalia.com wrote:

  On 04/24/2012 04:33 AM, Alberto Ruiz wrote:



 2012/4/24 Federico Mena Quintero feder...@gnome.org

 * Some sort of connection with a BitTorrent client.  I know this is
 treading on taboo ground, but I assume that a lot of people download
 torrents and then manually have to select which of the downloaded files
 to view with Totem - it's just cumbersome.


  If you ask me, I think torrents should be integrated in the browser, no
 other browser implements this and would make the torrent downloading
 experience much more transparent to the user.


 Just a nitpick about no other: opera has bittorrent integration:

 http://help.opera.com/Linux/9.00/en/bittorrent.html

 BR

 --
 Alejandro Piñeiro Iglesias


 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/desktop-devel-list




-- 
Whatever you can do, or dream you can, begin it. Boldness has genius, power
and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that counts
can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Module Proposal: Zeitgeist

2012-04-22 Thread Emily Gonyer 
Then the design team ought to be more open about what exactly 'their'
vision for gnome is, as well as open to other ideas/concepts. Insisting on
doing things their way, while being extremely vague as to what exactly
their way *is* is not helpful to the rest of the community who is trying to
get stuff done. IMHO the entire community is rather insulated from itself
and rather hard to break into w/o serious help from someone already on the
'inside' as it were. If you haven't been around for years, no-one seems to
particularly care what you have to say. Even finding these sorts of
discussions isn't exactly easy, let alone making your voice heard.


Emily

On Sun, Apr 22, 2012 at 10:11 AM, Florian Müllner fmuell...@gnome.orgwrote:



 On Sat, Apr 21, 2012 at 9:28 PM, Luis Medinas lmedi...@gnome.org wrote:

 do you really want to start talking about what the community think about
 this ? Because if you want to start talking i recommend to see how many
 threads we have, specially on gnome-shell ml, about design decisions that
 makes the community powerless against the almighty Design Team.


 ... and from before the design team even existed, there are even more
 threads about design decisions that make the community powerless against
 the almighty GNOME Developers - the (rightful) answer to that is usually
 don't just complain, get involved. The same still holds true with the
 design team - really, those folks would *love* seeing more people getting
 involved.


 Regards,
 Florian

 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/desktop-devel-list




-- 
Whatever you can do, or dream you can, begin it. Boldness has genius, power
and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that counts
can be counted. - Albert Einstein
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list