$ su -c "yum install VirtualBox-OSE"
$ su -c "/etc/sysconfig/modules/VirtualBox-OSE.modules"
$ virtualbox
$ su -c "/etc/sysconfig/modules/VirtualBox-OSE.modules"
$ su -c "yum install bridge-utils"
RPM of PHP 5.3.14 are available for Enterprise Linux in remi repository.
RPM of PHP 5.4.4 are available for Fedora in remi repository and for Enterprise Linux in remi-test repository.
Read the announcement : PHP 5.4.4 and PHP 5.3.14 released!
Use YUM to install : yum --enablerepo=remi update php-\* This versions will also be soon available in the official updates for: Fedora 17 - PHP 5.4.4 For all questions or help, please use the Forums.... Lire php-5.3.14 and php-5.4.4
The upcoming release of Deltacloud 1.0 is a huge milestone for the project: even though no sausages were hurt in its making, it is still chockful of the broadest blend of the finest IaaS API ingredients. The changes and improvements are too numerous to list in detail, but it is worth highlighting some of them. TL;DR: the release candidate is available now.
With this release, Deltacloud moves another step towards being a universal cloud IaaS API proxy: when we started adding support for DMTF CIMI as an alternative to the ‘classic’ Deltacloud API, it became apparent that adding additional frontends could be done with very little efforts. The new EC2 frontend proves that this is even possible for API’s that are not RESTful. With that, Deltacloud allows clients that only know the EC2 API to talk to various backends, including OpenStack, vSphere, and oVirt.
The EC2 frontend supports the most commonly needed operations, in particular those necessary for finding an image, launching an instance off of it and managing that instance’s lifecycle. In addition, managing SSH key pairs is also supported. We hope to grow the coverage of the API in future releases to the point where the EC2 frontend is good enough to support the majority of uses.
The debate around the ‘right’ cloud IaaS API is heated and continues, especially around standards, and we still see the right answer to this debate in a properly standardized, broadly supported, and openly governed API such as DMTF’s CIMI — yet it is undeniable that EC2 is the front runner in this space, and that large investments into EC2’s API exist; it is Deltacloud’s mission to alleviate the resulting lockin, and the addition of the EC2 frontend allows users to experiment with different backend technologies while migrating off the EC2 API on their own pace.
One issue that the EC2 frontend brings to the forefront is just how unsuitable that API is for fronting different backend implementations: IaaS API’s that are designed for this purpose provide extensive capabilities for client discovery of various features. EC2 on the other hand provides no way for providers to advertise their deviation from EC2’s feature set, and no possibilities for clients to discover them.
We continue our quest to support the fledgling CIMI standard as broadly and as faithfully as possible. With this release, we introduce support for the CIMI networking API; for now only for the Mock driver, but we are looking to expand backend support for networking as clouds add the needed features for them.
Besides the core CIMI API, which is purely a RESTful XML and JSON API, work also continues on the simple human-consumable HTML interface for it; we’ve learned from designing the Deltacloud API and helping others using that API, that a web application that stays close to the API, but is easy to use for humans is an invaluable tool. With this release, that application can now talk to OpenStack, RHEV-M/oVirt, and EC2 via Deltacloud’s CIMI proxy.
With three frontends, it’s become even more urgent that the three frontends can be run from the same server instance to reduce the number of daemons that need to be babysat. Thanks to an extensive revamp of the guts of Deltacloud to turn it into a modular Sinatra app it is now possible to expose all three frontends (or only one or two) from the same server.
We now also base our RESTful routes and controllers on sinatra-rabbit — only fitting since sinatra-rabbit started life as the DSL we used inside Deltacloud for our RESTful routing and our controllers.
A lot of work has gone into rationalizing the HTTP status codes that Deltacloud returns, especially when errors occur; in the process, we learned quite a bit about just how fickle and moody vSphere can be.
Other drivers have seen major updates, not least of which the OpenStack driver, which now works against the OpenStack v2.0 API; in particular, it works against the HP cloud — with the EC2 frontend, Deltacloud provides a capable EC2 proxy for OpenStack. We’ve also added a driver for the Fujitsu Global Cloud Platform, which was mostly written by Dies Köper of Fujitsu.
The release candidate for version 1.0.0 is out now, packages for rubygems.org, Fedora and other distributions will appear as soon as the release has passed the vote on the mailing list.
Selamat buat teman2 di Malang yang udah sukses mengadakan Release Party Fedora 17 pada hari Minggu, 10 Juni 2012 bertempat di Laboratorium Teknologi Informasi, Lantai 5 Gedung Kuliah Bersama (GKB) 3 di Universitas Muhammadiyah Malang.
Dengan kerjasama teman2 KaliUMM (Komunitas Linux Universitas Muhammadiyah Malang) dan KOLAM (KPLI Malang) dan di handle oleh salah satu kontributor Fedora Indonesia, tepatnya Koordinator L10n Indonesian Team, Teguh Dwicaksana.
Pengen tau gimana serunya Release Party ini bisa lihat langsung di wiki report Release Party ini : https://fedoraproject.org/wiki/Release_Party_F17_Malang
Surakarta dan Malang udah punya semangat Beefy Miracle, ayo kota2 lain di Indonesia, kalian selanjutnya! 
In this period many things that should not to come, instead are coming.
After the new about an unexpected entry that contributes with 1% of total development of Linux kernel, after the nearly certain announcement of UEFI Secure Boot implementation in Fedora (starting from Fedora 18 for the next machines branded with Windows 8), yesterday the Skype 4 (by Microsoft) for Linux has been released, like a bolt from the blue, throught the ovation from the its unwitting fans.
My first worry has been: “in this way, in a no more distant future, Fedora and in general the GNU/Linux distros will be meaningless”.
Microsoft is a multinational corporation, its target is to dominate the software business, throught proprietary software strategies and monopolistic business practices; that’s mine, is only mine; that’s not mine, could be it in future. Exactly the opposite of free and opensource software.
Microsoft imposes the UEFI Secure Boot on the machines “Windows 8 branded” and therefore indirectly imposes to the others operating systems a need of a own -Microsoft- sign.
Microsoft contributes to the Linux kernel development for the own profit (Hyper-V hypervisor implementation), not for a natural team spirit with the FOSS communities.
Microsoft builds Skype 4 for Linux to consolidate the use of the own famous VoIP software in GNU/Linux systems without release the sources; unlike Ekiga, for example, that releases the sources freely both for GNU/linux and for Windows.
All that (and much more) limits drastically the GNU/Linux prospectives; i’m not happy if Skype 4 for Linux is here, i’m not happy if the paranoias of UEFI SecureBoot “break the balls” to Fedora.
I’ve been trying to find a way to algorithmically generate sheet music. In looking into both Lilypond and ABC one thing is apparent: they are both based on the Major scale, which make s the notation weird. If you are only concerned about major scales.
I am going to use ABC notation for my argument, but, while the details are different, the reason still holds for Lilypond as well.
For ABC, the C Major scale is CDEFGAB. Makes sense?
No. It doesn’t. Why is A a higher note than C when A is a lower ASCII value?
Its not like you can keep from putting in an additional note of a different case when doing a scale anyway. When practicing A C Scale you go from C to C, you don’t stop at B. So really it should be
CDEFGABc
What modern musicians seem to have forgotten is that it is the relative minor, the Aeolean mode, that was the basis for musical notation, not the major. That is why it starts with A when there are no accidentals. What is the lowest note on the piano? Also an A.
The highest note on the piano is a C. But in the ABC notation,
If we wanted an completely unambiguous grammar for musical notation, it would be pitch/duration. Either an offset from the lowest A on the Keyboard (1) or a combination of the letter and the octave. Middle A is the 4th A on the Keyboard, so it would be A4. To avoid mixing duration and pitch it probably would be easier to say 4A. That has the added value of Orienting the reader to the portion of the keyboard nearest to the key prior to indicating the exact key. Additionally, repeating the octave would not be necessary for notes in the same octave.
So our major scale would become 4CDEFG5ABC. Yes, doing a trill between G and A would require a lot of extra notes but that is already the case for B to C trills when the notes require additional tick marks or other indicating factors.
Our relative minor scale is now 4ABCDEFG5A.
The cloning and filtering functionality is one of the most used features in Pulp v1. In v2, I wanted to expand on the capabilities based on feedback I’ve been hearing from the community and their use of cloning. The result is that the v1 notion of cloning is gone entirely.
The v2 model supports a much less tight coupling to the yum repository on the filesystem. Instead of having a single working area on disk where changes are instantly made visible, the driving operation in Pulp has been split between the process of importing RPMs into a repository (synchronization) and the process by which they are made available to outside consumers (publishing).
This split provides an opportunity for a significant manipulation of the contents of a repository before it is ever made live. RPMs imported into the server can be treated as building blocks that are easily manipulated in the database to quickly build up entirely new repositories before they are published.
Additionally, the v2 model has a stronger understanding of the relationship between a package and a repository, allowing us to track metadata about the association itself, such as when it was associated to a repository. This model comes into play in the unit copy feature and gives us a basis for more advanced association management in the future (for instance, the ability to version a repository at a point in time).
The unit copy functionality works by specifying a source repository and criteria to use to match packages in it. Matching packages will be associated with a specified destination directory. Unlike v1 cloning, there is no restriction on the source repository; multiple copy calls can be issued against different source repositories to populate the destination repository. Criteria can be specified as regular expressions or greater than/less than comparisons against any field in the package, everything from the name and version fields to vendor and license values. Once the destination repository is fully populated, it can be published to make the repository contents publicly accessible.
Before I go on it’s important to highlight that the idea of unit copy refers to its association with a repository. Pulp will still maintain a single storage on the filesystem of an RPM; what is copied is only the database’s understanding of which packages are associated with which repositories.
For this demo, I created two repositories.
The “pulp-f17″ repository was created using Pulp’s testing repository for Fedora 17 as the feed. It has been synchronized multiple times over the course of a few days. The pulp-* RPMs had new versions released in that time, however the dependencies (for example, python-okaara) have not changed.
The “dest” repository was created without a feed. It doesn’t need one; it will be populated by units selectively copied from the pulp-f17 repository and then manually published to make its contents available.
Below is a list of the names and versions of packages in the pulp-f17 repository for reference.
gofer-0.69 gofer-package-0.69 grinder-0.1.3 m2crypto-0.21.1.pulp m2crypto-debuginfo-0.21.1.pulp mod_wsgi-3.3 mod_wsgi-debuginfo-3.3 pulp-0.0.295 pulp-admin-0.0.295 pulp-cds-0.0.295 pulp-client-lib-0.0.295 pulp-common-0.0.295 pulp-consumer-0.0.295 pulp-selinux-server-0.0.295 python-gofer-0.69 python-isodate-0.4.4 python-oauth2-1.5.170 python-okaara-1.0.18 python-qpid-0.7.946106 python-rhsm-0.96.4 python-webpy-0.32
Unit copies are done through the pulp-admin repo copy commands. Beneath the copy section is a separate command by type of unit being copied. At the time of this article, only RPMs, SRPMs, and DRPMs are supported, but in the future errata and potentially kickstart trees will be supported.
At minimum there are two required parameters: the source repository (--from-repo-id) and the destination (--to-repo-id). Without any criteria, this will have the effect of copying all of the RPMs in the source into the destination. If an RPM to be copied already exists in the destination, it is ignored.
That’s not terribly interesting in and of itself. The power of this feature comes in the criteria available to select units to copy. Before I get to that, the --dry-run or -d flag will display a list of packages that match the criteria without actually performing the copy. Also keep in mind that packages can be copied from multiple different source repositories using multiple calls to the copy commands; for expediency this demo will only cover a single source repository.
The simplest form of criteria is a regular expression match against a field in each RPM. The format of this argument is to pass in the field name and associated regular expression. For instance, to match on RPM names that start with “p”, the full argument string would be --match "name=^p.*".
Multiple fields can be matched by specifying as many arguments as necessary. For example, to match on names that start with “p” whose architecture is “noarch”, two arguments would be specified: --match "name=^p.*" --match "arch=noarch". A full (dry run) example of this can be seen below:
$ pulp-admin repo copy rpm --from-repo-id pulp-f17 --to-repo-id dest -d --match "name=^p.*" --match "arch=noarch" +----------------------------------------------------------------------+ Matching Units +----------------------------------------------------------------------+ Filename: pulp-0.0.295-1.fc17.noarch.rpm Filename: pulp-admin-0.0.295-1.fc17.noarch.rpm Filename: pulp-cds-0.0.295-1.fc17.noarch.rpm Filename: pulp-client-lib-0.0.295-1.fc17.noarch.rpm Filename: pulp-common-0.0.295-1.fc17.noarch.rpm Filename: pulp-consumer-0.0.295-1.fc17.noarch.rpm Filename: pulp-selinux-server-0.0.295-1.fc17.noarch.rpm Filename: python-gofer-0.69-1.fc17.noarch.rpm Filename: python-isodate-0.4.4-4.pulp.fc17.noarch.rpm Filename: python-oauth2-1.5.170-2.pulp.fc17.noarch.rpm Filename: python-okaara-1.0.18-1.fc17.noarch.rpm Filename: python-qpid-0.7.946106-1.fc17.noarch.rpm Filename: python-rhsm-0.96.4-1.fc17.noarch.rpm Filename: python-webpy-0.32-8.fc17.noarch.rpm
Selecting packages that do not match a regular expression uses the same syntax to the --not argument. For example, to list all packages in the repository that are dependencies of Pulp but not actually part of Pulp itself:
$ pulp-admin repo copy rpm --from-repo-id pulp-f17 --to-repo-id dest -d --not "name=^pulp.*" +----------------------------------------------------------------------+ Matching Units +----------------------------------------------------------------------+ Filename: gofer-0.69-1.fc17.noarch.rpm Filename: gofer-package-0.69-1.fc17.noarch.rpm Filename: grinder-0.1.3-1.fc17.noarch.rpm Filename: m2crypto-0.21.1.pulp-7.fc17.x86_64.rpm Filename: m2crypto-debuginfo-0.21.1.pulp-7.fc17.x86_64.rpm Filename: mod_wsgi-3.3-3.pulp.fc17.x86_64.rpm Filename: mod_wsgi-debuginfo-3.3-3.pulp.fc17.x86_64.rpm Filename: python-gofer-0.69-1.fc17.noarch.rpm Filename: python-isodate-0.4.4-4.pulp.fc17.noarch.rpm Filename: python-oauth2-1.5.170-2.pulp.fc17.noarch.rpm Filename: python-okaara-1.0.18-1.fc17.noarch.rpm Filename: python-qpid-0.7.946106-1.fc17.noarch.rpm Filename: python-rhsm-0.96.4-1.fc17.noarch.rpm Filename: python-webpy-0.32-8.fc17.noarch.rpm
RPM fields can be compared against a value as well. The client supports greater than (--gt), greater than or equal to (--gte), less than (--lt), and less than or equal to (--lte) comparisons. The format is the same, specifying both the field name and the value to use as the comparison.
For example, to copy only packages whose version is at least 1.0:
$ pulp-admin repo copy rpm --from-repo-id pulp-f17 --to-repo-id dest -d --gt "version=1.0" +----------------------------------------------------------------------+ Matching Units +----------------------------------------------------------------------+ Filename: mod_wsgi-3.3-3.pulp.fc17.x86_64.rpm Filename: mod_wsgi-debuginfo-3.3-3.pulp.fc17.x86_64.rpm Filename: python-oauth2-1.5.170-2.pulp.fc17.noarch.rpm Filename: python-okaara-1.0.18-1.fc17.noarch.rpm
As I mentioned above, we have a much stronger understanding of the association between a repository and a package. Part of that is tracking when it was added to the repository. This allows us to specify criteria such as “Copy all packages added in the last 30 days.”
In my demo setup, the Pulp version was updated on June 8th, however many of the dependencies did not have new versions released in that build. For the purposes of this demo, let’s assume that I promote content from the live repository (pulp-f17) into an unstable repository (dest) once a month. To see what qualifies for promotion in June, I’d run:
pulp-admin repo copy rpm --from-repo-id pulp-f17 --to-repo-id dest -d --after 2012-06-01 +----------------------------------------------------------------------+ Matching Units +----------------------------------------------------------------------+ Filename: pulp-0.0.295-1.fc17.noarch.rpm Filename: pulp-admin-0.0.295-1.fc17.noarch.rpm Filename: pulp-cds-0.0.295-1.fc17.noarch.rpm Filename: pulp-client-lib-0.0.295-1.fc17.noarch.rpm Filename: pulp-common-0.0.295-1.fc17.noarch.rpm Filename: pulp-consumer-0.0.295-1.fc17.noarch.rpm Filename: pulp-selinux-server-0.0.295-1.fc17.noarch.rpm
Again, that example matches packages added to the repository after June 1st. New versions of a package qualify as new packages and will be picked up as part of this criteria. The format to --after (and its opposite, --before) is an iso8601 formatted timestamp; I simply omitted the time component.
Once the desired packages have been copied (don’t forget to remove the -d flag to actually commit the copy), the destination repository can be published to build and expose the new repository (or simply update the repository if it was already published). I’ll cover publishing in v2 in a separate post, but for completeness the command is: pulp-admin repo publish run --repo-id dest.
As usual, don’t quote me on any of this. I don’t have an idea yet on where any of this would fit in to our priorities, but I can at least say a few words about how I want to see this evolve.
The first step would be adding the ability for the server to saved named criteria. While this can somewhat be achieved by client-side scripts (or a CLI extension, but again, more on that in a separate article), I think it makes sense as a server-side concept. The idea would be to define regular criteria values and use an identifier to run that criteria again in the future.
Our scheduler in v2 is significantly more flexible in terms of the amount of work it takes on the server to use it, so I’d like to see copy calls get scheduled and incorporated into a normal scheduled sync workflow. Along the same lines, I’d like to be able to batch the copy call at the end of a sync, which would greatly aid in automation. The idea would be to tell the Pulp server to sync a repository, for example, every Sunday at 1am and then copy all newly synchronized packages into an unstable repository.
The user guide entry for unit copy can be found at: http://pulpproject.org/v2/rpm-user-guide/admin-client/repo/units.html#copy-packages-between-repositories
I make today an new tutorial about the trips and tricks with Ogre 3D engine using Blender 3D.
If you want to see this , you can go on tutorials part from my site.
This is the just an result of my simple example.
The result is show in next image sample.
Wallaby 0.15.0 includes a new feature called the skeleton group. (This feature was available in earlier versions of Wallaby, too, but it was experimental and had some rough edges.) Find out how the skeleton group makes configuration more flexible by reading all about it.
I just got into this whole Fedora packaging thing and found myself annoyed by all the waiting-on-koji-to-build. It's always the same kind of thing:
$ git commit -a -m 'Initial commit (#12345)' $ fedpkg push $ fedpkg build <wait wait wait> $ fedpkg switch-branch f17 $ git merge master $ fedpkg push $ fedpkg build <wait wait wait> $ fedpkg update <type type type> $ bodhi --buildroot-override BLAH $ fedpkg switch-branch el6 $ git merge master $ fedpkg push $ fedpkg build <wait wait wait> $ fedpkg update <type type type> $ bodhi --buildroot-override BLAH $ echo "le sigh"
I had to do this for the whole python-tw2 stack; it was unbearable I tell you!
In answer, I wrote a baby scriptlet called ship-it to smooth it over. It uses the unbelievably re__dict__ulous pbs python module to do the dirty work (coming soon to a Beefy Miracle near you as python-pbs-subprocess):
#!/usr/bin/env python """ Script for merging, pushing, building, updating, and buildroot-overriding changes to a package on multiple branches. Run this after you have made a change, committed and built the master branch for your new package. """ import argparse import textwrap # The pbs module is amazing. from pbs import git, fedpkg, bodhi, rpmspec, glob branches = [ { 'short': 'f17', 'long': 'fc17', }, { 'short': 'el6', 'long': 'el6', }, ] def config(): parser = argparse.ArgumentParser( description=textwrap.dedent(__doc__), formatter_class=argparse.RawDescriptionHelpFormatter, ) parser.add_argument( '--user', dest='user', help='Your FAS username.') parser.add_argument( '--type', dest='type', help="Type. (bugfix, enhancement, security)") parser.add_argument( '--bugs', dest='bugs', help="Specify any number of Bugzilla IDs (--bugs=1234,5678)") parser.add_argument( '--notes', dest='notes', help='Update notes') parser.add_argument( '--duration', dest='duration', type=int, default=7, help="Duration of the buildroot override in days.") parser.add_argument( '--forgive-build', dest='forgive', action='store_true', default=False, help="Don't stop the script if a build fails.") args = parser.parse_args() required_args = ['user', 'type', 'bugs', 'notes'] for required in required_args: if not getattr(args, required): parser.print_usage() raise ValueError("%r is required." % required) return args def main(): args = config() spec = glob("*.spec")[0] nevr = rpmspec(q=spec).split()[0].rsplit('.', 2)[0] print "Processing %r" % nevr for branch in branches: nevra = nevr + '.' + branch['long'] print "Working on %r, %r" % (branch['short'], nevra) print git.checkout(branch['short']) # Merge, push, build git.merge("master", _fg=True) fedpkg.push(_fg=True) if args.forgive: try: fedpkg.build(_fg=True) except Exception, e: print str(e) else: fedpkg.build(_fg=True) # Submit a new update. kwargs = { '_fg': True, 'new': True, 'user': args.user, 'type': args.type, 'notes': args.notes, } bodhi(nevra, **kwargs) # Buildroot override kwargs = { '_fg': True, 'user': args.user, 'buildroot-override': nevra, 'duration': args.duration, 'notes': args.notes, } bodhi(**kwargs) if __name__ == '__main__': main()
I have prepared a little talk for about the Pomodoro technique and an useful tool for be used in gnome-shell. The date is Saturday, Jun 16 in Hotel Masión Teodolinda at 14:00. If you want to know more about it, read this previous post. Download here.
As some readers may already be aware, Eucalyptus has started publishing code from the Eucalyptus 3 development branch on launchpad. The build process has a fairly sizable set of dependencies, so I'd like to give a quick example of how I built and installed this code on a Fedora 16 system. I started with a minimal x86_64 install.
$sudo yum install greybird-* elementary-icon-theme
%a %B %d, %Y %I:%M %pUsing musescore , I wrote out a handful of the Eight Tone Scales.
Here is what they sound like.
Of course, to really explore these, they would need to be rearranged. I’m most interested to hear how the various modes sound, and to see which work on top of the more common chords.
Hey! I was at the USENIX Women in Advanced Computing 2012 Summit earlier this week and am blogging the talks from it. You can view more of my posts about this conference under the wiac12 category on this blog.
Sherry: I think as a female engineer, one thing I definitely wish I’d known is to market yourself. There are many ways to market yourself that aren’t just about going to presentations, to your boss, or to your upper manager. If you want to be well-respected among other engineers, especially as the only female, you should tell the people around you about the hard problems you’ve been solving. Do this at lunchtime, in the hallway – but say it with enthusiasm. You’ll gain so much respect from the other engineers, who will also support you. I wish I had known that – once I learned that, my career advanced tremendously.
Margo: It’s okay to ask questions. Be confident enough to ask questions. I was a young engineer at Stratus and I’d been asked to do this fairly straightforward task. There was a part I fundamentally didn’t understand. Instead of asking, I did something really stupid – when I had my code review, my boss looked at me and said, “You didn’t ask, did you? You could have just asked!” For a variety of reasons – it’s not just us, the guys have this problem too – you feel like you’re suddenly stupid if you have to ask a question. Being confident enough to ask questions and hvae them answered is important.
Jessica: To make a sweeping generalization, if you have opportunities in front of you – just say “yes.” Commit to the conference talk, even if you’re afraid it’s over your head. Go to the dangerous start-up. Don’t freak out about it. If people are confident in you, take them up on it. Okay, don’t actually say yes to everything – I mean – if you feel something is too much of a reach – just do it.
Jessica: In the startup scene, I think the situation has definitely gotten better. If you surround yourself with people who want to succeed… well, they want the best people. The places where people assume I’m ‘in HR’ are places like conferences or on the internet. This doesn’t happen with the real people I work with day-to-day. I’m working with young people. I hesitate to talk about a generational difference there, but people I’m working with who are older and further away from my day-to-day work are the ones I have more of the problems with.
Margo: I’ve been fortunate and I’ve made my own fortune. I’ve been pretty comfortable with who I was. I have two much older brothers: both were salutatorians, and both were beaten by the smart girl for valedictorian. It never entered my mind that I was weird because I was doing computers, even though I was one of 3 people in the program. I had the attitude that I belonged and I’ve never questioned that. But I’ve also met idiots:
The first company I worked at out of college – a bunch of us got our own coffee machine because the office machine was horrid. I would buy the coffee and take care of that, and Alan would supply the cream. A new guy started, and we invited him into our coffee club. Later, he came to me and complained that there was no cream. I explained to him, “Mike, what don’t you get? I do the coffee, Alan does the cream.”
He said, “but I can’t bother him about that.”
“You can bother me? Get out of my office,” I told him.
There’s no reason to put up with any crap. Don’t do it. Later that day, I ran into him and I said, “Don’t talk to me, I’m still really mad at you.”
In response, he asked, “Can you get me a cup of coffee?”
I talked to my manager about it. This situation could have gotten out of control if I hadn’t been clear that it was way out of line. This was back in 1983. You can bring a huge amount of power to the situation by making it clear what was not okay and laughing at them.
Jennifer: Looking back, I realized all the sys admin teams I’ve been on have been mostly women with a few men. Now I’m on a 4-women, 6-guy team. On most of these teams I’ve been on, I had management support and didn’t have any issues like that. I did see these kinds of things when I was an astronomy/physics major, though: a lot more there. I handled it. My father always told me, “You can do whatever you want to do. Don’t let them get to you.”
Sherry: I went to college in China. In college, half of the engineering class was women. We were never treated differently and never given the excuse not to be the best just because we are female. When I came here for grad school, there were only two women in the entire computer engineering division. I have a 14-year-old daughter now, so I’m very conscious to not let her get away with anything. I tell her, “Just because you’re a girl isn’t an excuse to not do well. Put the effort into the homework to excel and be number one.” As a society, if you don’t give young ladies excuses and if you tell them that they are expected to do just as well, they will naturally do it. Just as with Jessica – I don’t think the guys in the company think of you as female. When I was on the kernel group, they treated me like another person and expected me to be competent and to do my job.
A lot of women in tech fields or academics have imposter syndrome, where they think they don’t really know what they are doing and people are going to find out that they are a fraud. These are intelligent, smart women who are good at what they do. I read about it and related to it, and I’ve found a lot of women are like this. Have you ever felt you had to act “as if” – you know on paper you have the skill set, but you don’t feel you can do it? What experience have you had with imposter syndrome?
Rikki: I had that at my job at Linux New Media when they first hired me to open their North American office and launch the magazine. I was able to do it, knew in my head that I could do it, but I was shocked that other people felt I could do it.
Sherry: One line I love saying to my female clients is “fake it until you can make it.” I have moved around all pieces of the system and software stack. I started with hardware, to application level, now I’m into networking. What I’ve found is:
I was tasked to lead 20 engineers on a project. I’d never led an effort like that before, but I knew I could pull it off. Have the confidence to believe in yourself, and think of the experience and support you’ll get.
Jessica: Commit yourself to things, even if it’s a stretch. All the time I struggle with imposter syndrome type things. An important part of it is that the people I work with are wonder kids who came out of MIT and they programmed before they came to college. I started programming in college, so I feel like I’m playing catch-up and I have to work harder to close that gap. I have to compensate for the extra time they had. Part of the way I do that is that I sign up to do things when they seem hard to me so I can prove to myself I can do it. Once you stack up enough of those data points, you can reflect back on what you achieved and know you can do it.
Emily: My male colleagues also feel that same way. It’s not just the women.
Rikki: I agree. It’s more common with women but men definitely feel it too.
Sherry: When I started in grad school, I worked as a system administrator. My husband at the time was a lead system administrator. We’re all called in at 4 AM, when a system went down. I had to do all the typing and he told me what to do – instructing me what to type and what to do. Nothing happened – it didn’t fix it. I told him, “You told me to type all of this on a production server, and you don’t even know if it will work!?”
It’s just like Emily said, and all the male colleagues do the same thing – so fake it until you make it.
Margo: sometimes I don’t think they are quite as aware they are faking it. I advise a lot of students. At one point I had a student couple, a man and a woman. She came into my office after class and said she didn’t get it, not as much as the guys do. “I know I get good grades, but at some point they’ll figure out I’m not really good.” This was before I knew the term ‘imposter syndrome.’
She felt they knew what all of the answers because when I called on the men in class, I didn’t reject their answers outright even if they were wrong. I try to find the most correct part of students’ answers and gently correct them. So I told this woman student my secret, “Listen to the answers the guys are giving in class. They’ll answer every single question – try to figure out what they really know vs what it sounds like they know.”
She came back and realized she knew just as much as they did. So embrace your inner imposter.
Jessica: Awareness of the ‘imposter syndrome’ really made a big difference for me. This is a thing you’re doing mentally to yourself.
Lois: I know through grad schoolat Harvard, my husband talked about how the more you know, the more you know you don’t know. You’re so aware of what you don’t know that you feel like a fraud.
Margo: I’ve never really had a problem of not speaking up, but one of my best friends in grad school was the only woman in her group. She would say, “Let’s do X.” The advisor would not hear it. A guy would say the same thing and the advisor would hear it.
One of the other students looked at the advisor and asked, “Why do you do that? She just said that 5 minutes ago.”
The advisor had no idea he did that. Fortunately, the other guys spoke up. Somebody in the room has to speak up.
I had this happen to me once on a panel about leadership in engineering. I was with some high-ranking guy in the military, some executive. I had said something, and two people down, someone said, “Joe said such and such” in reference to my comment. Another woman in the audience caught my eye and mouthed, “You said that.”
Someone else on the panel spoke up and said, “Actually, Margo said that.”
It’s so much powerful when a third party observes you’ve done something. Be that third party: this is something you can do for your female colleagues. When it comes from a third party, it’s incredibly jarring because when people do this kind of stuff, they don’t even know they’re doing it.
Jennifer: I’m on a non-profit board. In the last meeting I said, “You know, when I say something, you guys don’t pay attention.”
“Really, we’re doing that?” one of them asked me.
The next few meetings, I noticed that he was really making sure that I was saying something. The group also started noticing some of the more quiet guys should say something, too. Sometimes the guys have blinders on – I had to speak up for myself because the other seven guys didn’t have a clue.
Sherry: I have a trick or advice if you’re in a meeting with a lot of other people you don’t know. Be the best-dressed person in the meeting – they will always look for you for acknowledgement. I made sure I wore a suit, and they always look for me for acknowledgement.
Jessica: I have a sad observation about kids. I’ll be helping teach an elective class in a high school in the Boston area. We brought a bunch of kids from the class to Google to give them a tour and brainstorm topics they wanted to cover in class. There were a bunch of girls with a bunch of boys – on the tour, the girls were all on the back of the tour. They were at the back of the group while we were talking to engineers. They didn’t suggest topics and I had to shunt them to the front so the engineers could call on them and get them to ask questions.
These are high school girls… it starts really early, this not wanting to step forward. Whatever we can do for the girls that we know, culturally and in school – it starts really young, so it would be good to combat it while they are young.
Margo: I have a 14-year old son who plays World of Warcraft, with adults. It came out one night at dinner that he plays with a voice synthesizer: It makes him a 28-year old woman.
“Why is that?” I asked him..
“Well, if you’re a guy and you tell people what to do, they tell you to shut the ‘F’ up. But if you’re a woman, they listen to you.”
Jessica: It’s such a hard problem to unpack. I do a lot of STEM volunteering, especially with middle school girls. I ask them – “Does anybody ever tell you that you can’t do that or you can’t go into science?”
They laugh at me – “Of course we can do math.” At that level, they have confidence in their abilities. Something is happening in between middle school and high school. I don’t have the answers, though.
Jennifer: I was with a friend at a middle school TAG expo. These two girls came up to me, not my friend. They asked, “How can we be astronauts? We really want to be astronauts!”
Did they come up to me because I’m the female, or because I was closest to them? I think sometimes to get to some of the high schoolers, it helps if you go out there and say you’re having fun working on compute but you also still do girl things like make quilts. It gets the girls to realize that they’re not weird that they think math and science and chemistry are fun – not that it’s something that’s weird. You have to go out there and let them know that it’s okay to do this.
When I went thourgh astronomy and physics, I had mentors who were told they wouldn’t get telescope time because they were woman and they told me, “You’re not going to be that way.” So be a mentor.
Sherry: I have a 14-year old girl; I don’t know if she’ll get into engineering. I try to be a good role model and show that I’m having a fun time. I try to take her to conferences so she sees that I know my stuff; she’s come to Google and Sun and watched me at work. So, she knows it’s possible and that she can be as good as she wants to be at it. She knows a lot of other females in engineering and in the tech industry, too. I want her to believe she can be good at anything she wants to be good at.
Margo: The first person I would describe as a mentor had been my professor when I was an undergrad, then he left the school at the same time I did and ended up consulting at the company I ended up at in 1983. Today, we’re writing a grant proposal together. He totally believed in me, and it was never even all that explicit – he said things like, “Oh, she’s really good so I want her on my team.” He was instrumental, though, in what happened to me over the next 10-15 years. He was very clearly a mentor.
When I was a young faculty member at Harvard, there were two senior faculty who made it clear that it was their job in life to help make me succeed. They were there for me, running interferenece – their implicit message was “We believe in you and will do what we can.”
I use that same line with my junior colleagues now. “It’s all about you, I’m here to help you succeed.” Create that kind of faith in your junior colleageues.
Jennifer: I was in a place where I have a degree in astronomy and physics, I’m doing data analysis and talking to scientists, and I’m bored out of my mind. NASA has a program called ‘Circle mentors’ – if you had something you were interested in, they would find a manager who was not in your direct chain. A manager from NOAA mentored me. This manager said, “Go! Your assignment is to find someone you want to talk to.”
I went to our system administrator to determine if I wantred to do programming or system administration. I talked to Laura Carrier, before she went on maternity leave. When she came back, she offered me a job. She really gave me the opportunity, but it was that manager at NOAA who said, “You should go do this, come back, feel free to be able to pick out what you want to do and talk to people who do it to figure it out.”
Laura was a great mentor, she sent to me LISA. I’ve had more mentors since then, too. Circle mentoring is great because those mentors can look at you from an outside point of view – they’re not in your management chain – but they can also give you structured help and figure out where you need to go and what you can do for the company.
Jessica: I haven’t had a ton of mentorship. My parents aren’t technical and I was a really serious kid. There’s a photo of me at age two: I was wearing an acid wash jean jumper thing with a lunchbox, sitting on the corner of the house watching the schoolbus go by. I wanted to go. I was really serious as a kid and wanted to study since I was young. I didn’t have a lot of explicit mentorship, but something is true for me that has been true for a lot of women I know – I didn’t get the structure from my parents or family but I got it in high school. My science and calculus teachers were all women.
Jessica: Not getting mistaken for a booth babe is a priority for me. It’s really annoying. I have wonderful teammates who will say, ‘Hey bro, I’m not technical, you need to talk to her.’ It’s a problem at conferences still, but it’s not a problem at work. I don’t normally think about cltohing, I wear turtlenecks and jeans all the time.
Margo: I wear dresses but it’s a problem when you’re running wires on the floor. I want other women to know it’s okay to be a girlm though. It’s a message that doesn’t come across very often. There are women who like to dress up and wear skirts – that’s okay, it doesn’t mean you’re not a hacker.
One of my students ended up going to a consulting firm. She was fashionable, she looked really nice in clothes, and she wore nice clothes. She had one of her teammates tell her that dressing nicely was ‘inappropriate’. She sent me and email asking for advice. I told her, “This is his problem, not yours.” But there is this problem if you want to be taken seriously: looking too good is a detriment, and that kind of sucks.
Emily: When I was starting out as a sysadmin, sometimes I would wear a skirt. The number of guys who needed me to crawl under their desk increased, so that trained me to not wear skirts.
Sherry: I enjoy wearing skirts, I wear them almost every day and I feel very comfortable. Whenever I go to a meeting or more serious conference, I do wear my suit and try to look more respectable. I want everyone to look to me for acknowledgement!
Jennifer: I do wear a dress every now and then. I did on my wedding day. But I’m in a collared shirt now: this is ‘dressed-up’ for Goddard. Sometimes one of my colleagues will wear a skirt so she can say she can’t crawl under a desk. It’s never bothered me. The scientists have to dress up, but if you show up in a suit or tie where I work the support staff will ask you, “Where are you interviewing?”
Sherry: Dressing is a thing for the guys. They’ll dress differently so they stand out. One of my friends wears a tie every single day. He said it’s because he wants people to remember him.
Rikki: In my old job, I asked someone if they had a funeral that day and they did!
Ryan: On the top of my newsfeed right now is a Wired article – it says that the Facebook New York office dresses more nicely than the West coast office.
Margo: How many people have read the book Woman Don’t Ask? Go right now, buy it, and read it cover-to-cover. Next time it’s time for your annual review or job review – go read the book – we don’t ask, and we don’t get. There is nothing wrong with asking if you want a raise or higher salary. It’s a fabulous book.
Rikki: Not only do you have to ask… I also have all of the reasons why I got the number that I’m asking for… “I live here, and have this level of expreience, and this is the average.” But I wait until they ask, I don’t tell them the reasons up-front.
<stonrg>Margo: I have a friend who is the top soccer producer for ESPN. When she first worked with ESPNm she had been a freelancer; she did all of the World Cups and Olympics. Soccer is very technically-challenging to produce. She was one of the most talented in the company. I sat her down and told her why she can ask for whatever she wanted. She’s a confident, accomplished woman, but I had to give her all the reasons. She went in and pretty much got it.
Cat: I don’t think this only applies to money. When I was talking to Google, I came from a job where I was working 75% time. I asked for two days a week to work from home. I asked and I got it, even though they have a reputation against supporting that.
Jennifer: For the longest time, it was a joke between me and my husband that I made more money than he did. I don’t know where I learned how to negotiate. My choir teacher in HS was always like, “We’ll shoot for the sun. Shoot for the best and if we don’t make it, that’s fine, we’ll hit the moon.”
Don’t just aim for the moon. You’ll get a little bit more than what you thought if you shoot for more.
Sherry: I don’t know how many of you have been to China or Beijing. There’s a silk market there. The opening price is always 200% – 300% of its value. You negotiate by cutting the price down to the bare minimum. Offer 10%… when they say no, walk away, find the next seller, offer him 20%… by walking around and making offers like this, you’ll figure out the right price.
If you’re a seller, don’t ever aim low. If you’re a buyer, don’t ever aim high. Always ask for what you want: the worst case is they say no. If you don’t, ask you’ll never get it.
Jessica: I had a boyfriend in CS who told me that I could negotiate my salary for my internship. I tried and they incredulously gave me the money and then changed their policy to not allow it again. I was fortunate that someone recognized that I needed help and gave me guidance.
Margot: The numbers are apalling. You and I went through at the heyday when there were the most women in compute rscience. If we look at other countries like China, we can see that it doesn’t have to be that way. What is it about our society that this happen? I think it’s an American statement. Even in Europe, it’s better. The CRA does a study every year… it’s terrible.
One thing we might be able to do to make it a little bit better – unless we change the culture completely – is to not require so much personal sacrifice to enter the professional. For mid-career jobs, we construct the jobs in ways that requiring you making enormous sacrifices in your personal life to succeed. In general, women will refuse to do that. Why would enter this field if I can do something else and not sacrifice my personal life and satisfaction?
One of the best engineers I know is a woman who decided she only wanted to work 20 hours a week to see her kids. She gets more done in those 20 hours than most of my male colleagues get done in months. Most of the men in the group have families and children, but only two have ever decided to work part-time. The way the jobs are constructed, it’s hard to have a life. Having a life is good.
Jennifer: I see a lot of women in science. One of our associate chiefs had children. A colleague of mine, his wife retired from NOAA after 30 years… I see it in little pockets. I see women scientists coming up at Goddard saying they have their twins, and their life, and science. And I’m seeing guys doing things when their wives have the career. It’s in pockets; I don’t think it’ll be a broad swell, but I see it in the science part. The women scientists are married and have their kids, are going forward with their career, and the men and partners are supporting them.
Jessica: In the last couple of years there have been a lot of really positive changes in programming and open source communities that signal to me that we’ll eventually get there. I devote a ton of my energy to doing progamming outreach for women. I do a lot with the python programming langauge; I’m on their board of directors and outreach committee. In the python community, there’s been a tremendous increase in awareness of gender diversity and issues, calling out of bad behavior of men, and a lot more positive stuff going on. There’s also the Debian women group and the GNOME womens’ outreach program… these give me great hope for more support for outreach to women in the community.
So then it becomes a question: “If there’s support there, are there women who will rise up and take charge?” Open source is ready, I think.
Sherry: I do notice that there are a lot more researchers – most of the doctors at the hospital my family goes to are female, so I think there are more females advancing in science. At Google, there are actually a lot of women. Sabrina and Kat can attest to that.
Jennifer: I worked at LPM, and we were 6 years behind in Voyager translation for nitrate tapes. Six years of backlog done – I didn’t write the program. I could, however, get the data out and written for the scientists, but I realized that I had this detail. It involved higher-level math… I was taking a spherical trigonometry, in second-level astronomy. I’m talking about the project while my parents are in the room. My mom turns to my dad and goes, “Do you understand what she’s saying?”
My dad goes, “Not a clue.”
I know more math than my parents: that’s a good thing. But you hit a limit. Working with the VAX tapes is a logical problem. I know how to do it. I think that’s what got me on that track, even though I have astrophysics degree… I realized I missed pounding my head against the wall on a system problem.
Jessica: I didn’t start out in Computer Science. I was in Chemistry and I got that degree, but I had a bunch of friends who were CS majors. They were learning a class of material that was very differnt than what I was doing. My friends taking computer science were really learning a toolbox of tools for solving more arbitrary problems in the world, and that seemed powerfully compelling for me. I felt I had to get in on it, so I took one of the last famous 6001 CS courses at MIT. I got an internship, and an on-campus apprenticeship. I was totally hooked.
The power of CS was evident to me at the beginning. A pivotal point for me was my very first experience in an open source project. For a lot of women, this is either not an experience (they don’t do it at all) or a negative experience. I was an intern at VMWare using a python library called twisted. I muttered, “The documentation sucks. I’m going to send an email to the mailing list saying the docs sucks.” I asked if I could help because it sucked. Instead, the maintainers made a conscious decision to welcome me and encourage me to submit patches, and helped me along the way. That has turned into years of friendship. I’m now the maintianer of that project and writing a book with O’Reilly.
Gliff made a point of making my first expreience a positive one. It makes it clear to me that it’s important, as we go through our CS/open source careers, that people are having positive first experiences. You may not know that it’s their first experience, so try your best to promote a positive experience for everyone. You have the opportunity to help that person who submitted a crappy bug report to continue to try. I would encourage you all to think about that: “Teachable moments.”
Jessica: I tell all of the women who I know who are awesomely technical to submit a talk. I tell them that they should go to this conference, or talk at this user group event. Some of them wouldn’t do it without repeated prodding, and the best way to get women to step into leadership positions is to tell them they should do it.
As organizers for the Boston Python User Group, we’ve constructed a programming pipeline to get women into the python community. We don’t construct a separate space for women. We run it as part of the existing community. We run intro to python events for women with a custom curriculum that is appropriate for any absolute beginners. It’s hands on, applied, low-pressure, and free. There’s no financial committment. We have followup events and try to integrate women into the user group and get them to step up into leadership positions.
We’ve taken the user group from 0% women to over 15% women – consistently, at large 100-120 person events. It’s been a huge improvement over the past 18 months. We’ve also has tremendous community support – we’ve received grants from the Anita Borg foundation and it’s been replicated in other cities in the US: Philly, DC, Portland, Indianapolis. The Boston Ruby community is also emulating our philosophy. That’s something that we’re doing. It’s exciting. We want long term, measurable success. Working within an existing community can be effective. If people are interested in talking about this, I would love to talk to you.
Jennifer: I’ve done a lot of mentoring in the model rocket community, for kids and women. I don’t don’t think I’d ever thought about doing it in the sys admin world. The women I’ve worked with are at the same level or above me. If a young woman came up to me, I’d like to mentor them. If you haven’t mentored in computing but you’ve mentored in another area, I still think it’s a good thing – even if it doesn’t channel into the computer stuff.
Margo: We should commend all of those men who took the time to come and spend the day with us. Here are some suggestions:
Those are some great first steps. Each of you guys and gals should find two of your male or female friends to bring next year to make the discussion bigger and broader.
Ryan: We’re rying to hire more women at Facebook. I manage women sometimes on tech lead projects, and I want to understand because we’re not recruiting as many women as we should. I also volunteer at schools and want to learn about more that I can do. I’m taking notes and sending them to engineering managers.
Sherry: Thinking back, I don’t have a person I went to for advice as a mentor, but throughout my whole career I had a lot of management and senior technical people who let me do what I wanted to do. Positive feedback loops with them helped me and made me feel more confident. I would go to them to talk to them about a brilliant idea I had – that kind of encouragement is positive in helping female engineers’ development. Make a point of encouarging their ideas.
Margo: My standard list of logistical things you can bring to your organizations to support women:
Rikki: One really strong mentor I had – I hadn’t worked at the company very long -after a conference call he called me and asked why I didn’t speak up. Afterwards, it didn’t take long for me to start speaking up. He’s the one who encouraged me to start the Rose blog, which was my women in open source blog. I got to meet so many people from having that blog. I wouldn’t have thought of it if he hadn’t suggested it. He called me out when I did things that wouldn’t help my career. But that one phone call helped me more than anything.
Sherry: I definitely feel that way. I feel like I have to know more, and I think that’s it’s partially the attitude that the more you know, the more you know you don’t know. The guys seem secure with what knowledge they already have. They feel strong in the knowledge they have, and women with the same amount of knowledge feel insecure about it. So I think it’s more about how you feel about it rather than how much you actually know. If you don’t feel confident about yourself, nobody else will.
<stonrg>Margo: This is one of my favorite topics. Part of it is being confident in what your decisions are. I was the first woman to have a child in the school of engineering (I was only the second woman to work in the school of engineering, though.) So, they didn’t know how to handle maternity leave. The dean asked me what I was going to do.
“I’ll teach in the fall and finish up, and bring the baby into the office with me for the Spring,” I told him.
He said okay – kudos to him – so I took my kid to work for 7 months. There are some environments where this doesn’t work. But it doesn’t occur to us to ask.
One of my college classmates – she had done this at a tiny startup. What a cool idea, to be a mom and be at work. It was fabulous. Think outside the box: what works for you? Feel free to make decisions that work for you and figure out how to juggle it. My kid is graduating from 8th grade tomorrow. I’m organizing the party… so I’m juggling. I’m not here at the conference as much as I normally would be, but it’s okay. It’ll go ok.
Jennifer: I like to joke with my manager… “I’m taking every other Friday off, if you don’t give it to me I’ll go postal.” I have other obligations that I want to do. Early on in my career, I felt like I had the time because I didn’t have kids. I am contributing even without kids, though – I need every other Friday off to help my ‘rocket kids.’ Family always comes firs. My officemate has 2 kids, drives an hour away, has a weird work schedule… but your job is always going to be here. Even if you do or don’t have a child – if your work life is good, do what you need to do. It’s been a good environment where I’m at. If you don’t come to work happy, if affects everything else.
Sherry: I have a 14-year-old firl who graduated from 8th grade and an 11 year old boy. I’m probably not the best example, but I was leading the most difficult projects – dynamic configuration – when he was born. I would put him to bed and I wouldn’t sleep thorugh the night. But I truly love what I do, and that to me was not a sacrifice. At the same time, I feel so fortunate to have my children and my life outside of work.
Linus’ license plate is ‘DADOF3.’ The OS is his hobby; his job is as a father and he’s working so he can be a father. If you don’t step out of your work to really live your life, you’ll lose your perspective and not know what’s really truly impotant. You really have to enjoy every step of it. If you feel you’re making a sacrifice, you may regret it later. So make sure you’re enjoying it.
Jessica: My youthful perspective is on the start up, all-in, intense side. That situation is a little different. The reason why they founders of the start-up picked me – they knew I was good and would be all in. It was all the time, 6 days a week. So I also want to say – women, if they want to, are capable of committing the same level that men are, and they shouldn’t be afraid of doing that if that’s what they want to do. Make sure you express that you’re able to commit yourself, because sometimes there’s a perception that women won’t.
Just to let you know that I've packaged Greybird theme (an Xfce theme from Shimmer project) for fedora 17+, after the installation and activation your Xfce desktop should look to something like this screenshot (from Xfce.org): 
yum install greybird-*
Tema default Adwaita untuk di sisi kiri atas panelnya, menggunakan tulisan “Activities“, ataupun tema yg kebanyakan ada di deviantart tetap masih menggunakan default “Activities“, nah buat yang boring ingin menjadi seperti logo, berikut tutorialnya.
Caranya sih simple cuma edit Gnome-Shell.css, defaultnya ada di ~/.themes/themesname/gnome-shell/
Bisa menggunakan vi atau editor yg lain :
~/.themes/themesname/gnome-shell/gnome-shell.css
Terus tambahkan line ini di sebelum .panel-menu { :
#panelActivities {
border: none;
background-image: url("your-logo1.png");
background-position: 0 0;
width: 58px;
height: 24px;
color: rgba(0,0,0,0.0);
}
/* Kalau mau make efek blink2 gt, pake'logo yg berbeda
#panelActivities:hover {
transition-duration: 300;
background-image: url("your-logo2.png");
background-gradient-direction: vertical;
background-gradient-start: rgba(255,255,255,0.0);
background-gradient-end: rgba(255,255,255,0.0);
box-shadow: inset 0px 0px 1px 1px rgba(255,255,255,0.0);
}
#panelActivities:active,
#panelActivities:overview {
background-image: url("your-logo1.png");
background-gradient-direction: vertical;
background-gradient-start: rgba(140,200,255,0.0);
background-gradient-end: rgba(61,149,231,0.0);
box-shadow: inset 0px 0px 1px 1px rgba(255,255,255,0.0);
}
Nah jika ingin mengganti dgn logo Fedora, seperti ini :
Bisa download yg udah saya buat > 
