Last week I published a new app to the Ubuntu Store, which isn’t anything particularly new, but this time I didn’t use my normal license, instead I went permissive. This is something I’ve been wavering on for a while now, and is the result of some developer soul-searching about why I’ve been using the GPL and what it’s done for me.Free as in mine
In the past I’ve always used the GPL or LGPL, not for philosophical reasons or because I thought software should be free (in the RMS sense), but because I was selfish. I used the GPL because I wanted to make sure nobody built something on top of my work without sharing it back to me. In my mind, using a strong copy-left license ensured I couldn’t be left out of someone else’s success with my project. And in a way it worked, I wasn’t left out, because most people never used, let alone built on, my projects. I was trying to solve a problem I didn’t actually have.You aren’t gonna need it
YAGNI (You aren’t gonna need it) is a principle of extreme programming that says you shouldn’t add features to a project until you know that it’s actually necessary. I don’t usually pay much mind to trendy programming methods, but I think this one might be applicable to the way I pick licenses. If my project aren’t being used and extended by others, why am I worried about it happening enough that I want to put restrictions on it? Maybe I don’t need the GPL’s protections afterall.A new direction
So from now on I’m going to prefer the BSD for new projects, and I’ll work on converting old ones to this license when I’ve been the only contributor. The worst that can happen is that somebody benefits from my code more than me, but that wouldn’t be much different to me than having nobody benefit from it more than me. I won’t actually lose anything. Nor will I be restricting my future options, on the contrary I can always go from a BSD to a GPL, but going the other direction is quite a bit harder once you accept contributions.
As mentioned in my earlier blog, I'm visiting several events in the US and Canada in October and November. The first of these, the talk about WebRTC in CRM at xTupleCon, has moved from the previously advertised timeslot to Wednesday, 15 October at 14:15.WebRTC meeting, Norfolk, VA
This will be a hands on event for developers and other IT professionals, especially those in web development, network administration and IP telephony. Please bring laptops and mobile devices with the latest versions of both Firefox and Chrome to experience WebRTC.Free software developers at xTupleCon
If you do want to attend xTupleCon itself, please contact xTuple directly through this form for details about the promotional tickets for free software developers.
- Final beta freeze is 9/25
- The one bug that is >= high in importance and not fixed is bug 1350810 in byobu, reminder sent to kirkland
- Everyone reminded to review assigned blueprints for any features that need to be postponed for 14.10 release, since we’re beyond feature freeze
- no updates
- no updates
- coreycb added arges to agenda
- arges reported to kickinz1 that bcache bug is fixed upstream, so that should trickle down soon
- There are a few sprints going on at the moment.
- no updates
Release Metrics and Incoming Bugs
Release metrics and incoming bug data can be reviewed at the following link:
Status: Utopic Development Kernel
The Utopic kernel has been rebased to the v3.16.2 upstream stable kernel
and uploaded to the archive, ie. linux-3.16.0-14.20. Please test
and let us know your results.
I’d also like to point out that our Utopic kernel freeze date is about 4
weeks away on Thurs Oct 9. Please don’t wait until the last minute to
submit patches needing to ship in the Utopic 14.10 release.
Important upcoming dates:
Mon Sep 22 – Utopic Final Beta Freeze (~2 weeks away)
Thurs Sep 25 – Utopic Final Beta (~2 weeks away)
Thurs Oct 9 – Utopic Kernel Freeze (~4 weeks away)
Thurs Oct 16 – Utopic Final Freeze (~5 weeks away)
Thurs Oct 23 – Utopic 14.10 Release (~6 weeks away)
The current CVE status can be reviewed at the following link:
Status: Stable, Security, and Bugfix Kernel Updates – Trusty/Precise/Lucid
Status for the main kernels, until today (Sept. 9):
- Lucid – verification & testing
- Precise – verification & testing
Trusty – verification & testing
Current opened tracking bugs details:
For SRUs, SRU report is a good source of information:
cycle: 29-Aug through 20-Sep
29-Aug Last day for kernel commits for this cycle
31-Aug – 06-Sep Kernel prep week.
07-Sep – 13-Sep Bug verification & Regression testing.
14-Sep – 20-Sep Regression testing & Release to -updates.
Open Discussion or Questions? Raise your hand to be recognized
No open discussion.
One thing we’d like to see is to bring these capabilities to our users. So I’ve been working on bundling together some of our ElasticSearch resources in Ubuntu so we can bring them to the cloud, it looks like this:
This is a standalone ElasticSearch cluster. I’ve added a few things:
- A preconfigured Kibana dashboard
- A script that preloads the cluster with the works of Shakespeare, so you can start the 10 minute introduction right away and get to work.
- Paramedic and Bigdesk so you can monitor your cluster.
One of the nice things about this bundle is it uses our ElasticSearch charm. Right off the bat you’re getting a charm that we’re using in production today. That means it’s tested (see the included tests, and it also uses many of the modern techniques for writing a charm. In this case, Michael Nelson leveraged Ansible to do most of the heavy lifting. Our ability to consume multiple tools to get the job done is one of the nice things that we can support in charms, so if you prefer a certain tool, then by all means use it! It also just consumes upstream packages, so you’ll always have a fresh version.Why ElasticSearch?
The major use of ElasticSearch is within Ubuntu’s Software Store for Unity 8. On Ubuntu Touch anytime a user is searching for and navigating the store they’re using ElasticSearch. ElasticSearch was chosen for a few reasons.
- It allowed us to design the store where every category is basically a search term. This allows the team to dynamically generate categories based on certain criteria. For example a list of “Top 10 apps” might be different depending whether you are in the US or in China.
- Since everything is designed around search, it lets the team “future proof” the Software Store for future categories and queries.
- ElasticSearch was designed to scale much more than other solutions we looked at. ElasticSearch can be horizontally scaled by just juju add-unit with no extra configuration.
- Since the team didn’t have to worry about learning how to make search it let them concentrate on the store itself and let ElasticSearch do the heavy lifting.
- Since ElasticSearch is driving the backend, this will enable Ubuntu Phone partners to offer customized views on top of the existing store without having to do major engineering work around building a branded store.
- Our team found the ElasticSearch documentation to be excellent.
Ok so let’s deploy this badboy. Assuming you’re brand new:sudo apt-get install juju juju-quickstart juju quickstart bundle:elasticsearch/cluster
At this point follow the ncurses menus to pick which cloud you want to deploy to and add your credentials and then Juju will bootstrap and start deploying ES.
Total deployment time will depend on where you’re deploying to, but on AWS US East 1 I can go from zero to cluster in about 10 minutes. By default I give you one Kibana node and one ElasticSearch node. For ElasticSearch we ensure you’re node has at least 4 CPU cores and 16GB of RAM. You can follow the instructions to load up the sample data and the other sample plugins I’ve included. Just go to the ip address of the Kibana unit in your browser and start searching:
Now you’re ready to horizontally scale:juju add-unit elasticsearch
To add a new node.And that’s it
You now have an ElasticSearch cluster. Using the same best practices that we’re doing in production. Amir Sanjar and I are prototyping bundling the ElasticSearch Hadoop plugin in a bundle as well, though that’s not quite ready (testing and help wanted!).
As you can see, we’ve barely scratched the surface. Chuck Butler’s been reworking the Logstash charm for Trusty, we expect that to land soon. We plan to make the charm a subordinate, you can just plop it onto any unit. The idea is to enable people to put logstash’s indexer on every unit they can shove all they care about into ElasticSearch.
“An idea is resilient. Highly contagious. Once an idea has taken hold of the brain it's almost impossible to eradicate.”
“Now, before you bother telling me it's impossible…”
“No, it's perfectly possible. It's just bloody difficult.”
Perhaps something like this...
“How could I ever acquire enough detail to make them think this is reality?”
“Don’t you want to take a leap of faith???”Sure, let's take a look!
Okay, this looks kinda neat, what is it?
This is an open source Java Spring web application, called Spring-Music, deployed as an app, running inside of Linux containers in CloudFoundry.
CloudFoundry is an open source Platform-as-a-Service (PAAS) cloud, deployed into Linux virtual machine instances in OpenStack, by Juju.
OpenStack is an open source Infrastructure-as-a-Service (IAAS) cloud, deployed by Juju and Landscape on top of MAAS.
Juju is an open source Orchestration System that deploys and scales complex services across many public clouds, private clouds, and bare metal servers.
Landscape is a systems management tool that automates software installation, updates, and maintenance in both physical and virtual machines. Oh, and it too is deployed by Juju.
MAAS is an open source bare metal provisioning system, providing a cloud-like API to physical servers. Juju can deploy services to MAAS, as well as public and private clouds.
"Ready for the kick?"
If you recall these concepts of nesting cloud technologies...
These are real technologies, which exist today!
These are Software-as-a-Service (SaaS) web apps served by an open source Platform-as-a-Service (PaaS) framework, running on top of an open source Infrastructure-as-a-Service (IaaS) cloud, deployed on an open source Metal-as-a-Service provisioning system, managed by an open source Orchestration-Service.
Spring Music, served by CloudFoundry, running on top of OpenStack, deployed on MAAS, managed by Juju and Landscape!
“The smallest seed of an idea can grow…”
Oh, and I won't leave you hanging...you're not dreaming!
Ubuntu Themes with support to GNOME >= 3.12
Install:sudo add-apt-repository ppa:l3on/ubuntu-themes-gnome-shell sudo apt-get update sudo apt-get install light-themes
For more info, check out lp:~l3on/ubuntu-themes/gnome-shell-fixes.
Improvements didn't happen overnight. But by the time we finished A Bug's Life, the production managers were no longer seen as impediments to creative process, but as peers--as first-class citizens. We had become better. This was success in itself, but it came with an added and unexpected benefit: The act of thinking about the problem and responding to it was invigorating and rewarding. We realized that our purpose was not merely to build a studio that made hit films but to foster a creative culture that would continually ask questions. Questions like: If we had done some things right to achieve success how could we ensure that we understood what those things were? Could we replicate them on our next projects? Perhaps as important, was replication of success even the right thing to do? How many serious, potentially disastrous problems were lurking just out of sight and threatening to undo us? What, if anything, could we do to bring the to light? How much of our success was luck? What would happen to our egos if we continued to succeed? Would they grow so large they could hurt us, and if so, what could we do to address that overconfidence? What dynamics would arise now that we were bringing new people into a successful enterprise as opposed to a struggling startup?
What had drawn me to science, all those years ago, was the search for understanding. Human interaction is far more complex than relativity or string theory, of course, but that only made it more interesting and important; it constantly challenged my presumptions.... Figuring out how to build a sustainable creative culture--one that didn't just pay lip service to the importance of things like honesty, excellence, communication, originality, and self-assessment but really *committed* to them, no matter how uncomfortable that became--wasn't a singular assignment....
As I saw it, our mandate was to foster a culture that would seek to keep our sightlines clear, even as we accepted that we were often trying to engage with and fix what we could not see. My hope was to make this culture so vigorous that it would survive when Pixar's founding members were long gone. [p. 64-5]Again, I see an almost perfect match between their task and ours, where ours=KDE e.V.. In the Community Working Group (CWG) in particular, I see my task as essentially gardening. This includes improving the soil, weeding, but never removing valuable little shoots which can grow into exciting new directions for the community. Of course I can't carry the metaphor too far, since others do the planting. But we can keep the conditions for growth optimal with our work.
In the documentation workshop yesterday, we explored the current state of the KDE documentation, how we can improve access, and grow the documentation team again. We also found some large choke points, which includes KDE.org. We really need a web team! KDE.org is valuable real estate on the web, which has been neglected for too long. More about that later.....
For now, looking forward to another day of hard work and fun in Brno!
Welcome to the Ubuntu Weekly Newsletter. This is issue #382 for the week September 1 – 7, 2014, and the full version is available here.
In this issue we cover:
- Welcome New Members and Developers
- Ubuntu Stats
- OpenStack Austin Meetup, with an Orange Box and Home Brew Beer!
- Arizona: Installfest schedule and locations
- Didier Roche: Ubuntu loves Developers
- Daniel Holbach: ubuntu-community-team list: Hang out, discuss new ideas
- Nicholas Skaggs: Autopilot Test Runners
- Lubuntu Blog: [Poll] Community wallpaper contest
- Unity8 & Mir update Sept 2, 2014
- Canonical News
- YES, I have ridden the UNICORN: The Ubuntu Utopic unicorn
- In The Blogosphere
- Ubuntu Podcast from the UK LoCo: S07E23 – The One with the Nap Partners
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04 and 14.04
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Elizabeth K. Joseph
- Jose Antonio Rey
- And many others
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License
I do a podcast called Bad Voltage with a bunch of my pals. In it we cover Open Source and technology, we do interviews, reviews, and more. It is a lot of fun.
We started a contest recently in which the presenters have to take part in a debate, but with a viewpoint that is actually the opposite of what we actually think.
In the first episode of this three part series, Bryan Lunduke and Stuart Langridge duked it out. Lunduke won (seriously).
In the most recent episode, Jeremy Garcia and I went up against each other.
Sadly, my tiny opponent is beating me right now.
Thus, I ask for a favor. Go here and vote for Bacon. Doing so will make you feel great about your life, save a puppy, and potentially get you that promotion you have been wanting.
Also, for my Ubuntu friends…a vote for Bacon…is a vote for Ubuntu.
UPDATE: The stakes have been increased. Want to see me donate $300 to charity, have an awkward avatar, and pour a bucket of ice/ketchup/BBQ sauce/waste vegetables on me? Read more and then vote.
Due to changes in NGINX, there are now changes done to the default configurations which will break fastcgi sites.
NGINX in Debian, and as such, the PPAs, were previously shipping different configuration files which differed from NGINX itself. The Debian package has now synced with the nginx configurations upstream, and as such, certain very different changes have happened.
This is the massively-detailed NEWS entry in Debian for these changes:
nginx-common (1.6.1-2) unstable; urgency=medium
As of nginx-1.6.1-2 we have synced all configuration files with upstream and
we plan to keep them in sync from now on.
Unfortunately that might break existing configuration for some users. Please
check the matrix below for more information:
mime-types whitespace, changed js/rss mime type,
minor other changes & additions
scgi_params whitespace, added HTTPS
uwsgi_params whitespace, added HTTPS, removed UWSGI_SCHEME
fastcgi_params whitespace, removed SCRIPT_FILENAME
fastcgi.conf new upstream configuration file
Fastcgi configuration issues
nginx shipped a modified `fastcgi_params`, which declared `SCRIPT_FILENAME`
fastcgi_param. This line has now been removed. From now on we are also
shipping fastcgi.conf from the upstream repository, which includes a sane
`SCRIPT_FILENAME` parameter value.
So, if you are using fastcgi_params, you can try switching to fastcgi.conf
or manually set the relevant params.
You might also want to read the documentation section before proceeding.
section: $fastcgi_script_name variable.
You will need to change fastcgi_params to the fastcgi.conf file, or manually set the relevant parameters in your site configs, in order to make things work again.
(This is introduced in the PPAs as 1.6.1-2+precise0 +trusty0 and +utopic0. This is also introduced in the PPAs as 1.7.4-1+precise0 +trusty0 and +utopic0. THis will also be in Ubuntu in versions after 1.6.1-2)
Yesterday the stream of talks at KDE’s conference Akademy finished with the Akademy Awards and Sponsors’ Presentations. Thanks to kind sponsorship by Blue Systems we got to give the first presentation. Rather than talk about how much we loved KDE we decided to show our love by giving away our smart range of polo shirts and shirts to the many good looking members of KDE.
IFA 2014 offered many surprises for those who are interested in Chromebooks. The biggest surprise and the one deserving your attention is the Toshiba Chromebook 2 with the FHD IPS display.
Apparently while other manufactures continue to guess the market Toshiba was listening to what folks were saying they want.Optional blue cover
I will be the first to admit building products from polycarbonate can be challenging but it looks like Toshiba got it right with a style which is contemporary and Ultrabook in appearance. Polycarbonate is extensively used in the mobile space for the following reasons.
2. Light weight
3. Does not interfere with reception
Polycarbonate is a poor conductor of heat which means with today’s thermally constrained devices manufacturer often add a metal strip of aluminum or magnesium to firm up the design and assist with heat dissipation. A tear down of this device would probably reveal the same as the Toshiba Chromebook 2 is fan less.
Trimmed to .76 inches thin and reduced to 2.87lbs/1.3kg in weight, the design is travel friendly and easy in hand. For comparison the 13″ Macbook Air weighs 2.96lbs/1.35kg and is .68 inches thick. A close inspection of the surface reveals a micro dimple texture which enhances the grip and helps to obscure finger prints.
One of the most requested Chromebook features is an IPS display and Toshiba is the only manufacturer to offer it in this size. Everyone who had an opportunity to see this unit at IFA have favorably commented on the quality of the display. On the down side a full 1080p user experience on a 13 inch display renders very small artifacts. We will have to see if the IPS panel off sets this liability.
Keyboard – Track pad – Sound – Essentials
No major complaints with the keyboard and the track pad so we will have to wait for evaluation units to be shipped to confirm. I am not expecting great fidelity from the speakers but Skullcandy earbuds and headphones are often favorably reviewed. In addition to the above this Chromebook is equipped with an HD webcam, a USB 3.0 port, a USB 2.0 port, full size HDMI® port, a standard SD Card slot, and 802.11ac wireless connectivity.
Intel N2840 SoC
The only area of concern voiced to date is the use of the Intel N2840 Bay Trail-M SoC. This is a dual core two thread CPU which runs at 2.16 GHz and peaks at 2.58 GHz in turbo mode. On paper it looks like this SoC will compete with the Hawell 1.4 GHz 2955u which ships in the entry level Chromebox. The N2840 also includes the Intel® HD Graphics GPU clocked at 311 MHz supporting bursts of 792 MHz.
The Toshiba Chromebook 2 has a good mix of design choices which include a quality build, excellent display, good performance, and promises to deliver all this on a battery rated for more than 8 hours of use. I am already a satisfied Chromebook owner but at a retail price $330 for the 4GB of RAM model, this one has certainly grabbed my attention. US availability is expected in early October.
Other sites of interest.
- Chromebook Comparison Chart
- CNET Toshiba Chromebook 2 Preview
- Chromebooks Google+
- Toshiba Press Release
Most of the community manger jobs in the Open Source (and Open *) world require the persons in the position to know how to develop, as in to code rather to develop a new non-coding project, if that made sense. But my thought is there is any Open * communities that are not based on development but on other things. If so, may I have some examples? I’m looking for mainly Open Science ones but any can do.
I would like to have insight here also for the non-members of that forum. You can post your answer in the comments section in instead of joining the forum and answering there.
I was glad to hear that once she found the KDE-doc-english mail list, that she was encouraged to stick around, get onto IRC, and guided every step of the way. I was also happy to hear that Yuri, Sune and Jonathan Riddell all made her feel welcome, and showed her where to find the information she needed to make her contributions high quality. When Scarlett showed up in #kubuntu-devel offering to learn to package, I was over the moon with happiness. I really love to see more women involved in free and open source, and especially in KDE and Kubuntu, my Linux home.
I was a bit sad that the Debian community was not welcoming to her, with Sune the one bright spot. Yeah SUNE! (By the way, hire him!) I think she will find a nice home there as well, however, if our plans to do some common packaging between Kubuntu and Debian works out in the future. It was interesting to see the blog by the developers of systemd discussing the same issue we've been considering; the waste of time packaging the same applications and other stuff over and over again. So much wasted work, when we could really be using our time more productively. Rather than working harder, let's work smarter! Check out their blog for their take on the issue: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
Welcome to Scarlett, who is planning to get her blog up and running again, and on the planets. She'll be saying more about these subjects in the future. Scarlett, and all you other first-time Akademy attendees, a hearty hug of greeting. Have a wonderful time! See me in person for a real hug!
PS: I couldn't post this until now, Sunday morning. The Debian folks here, especially Pinotree have been great! I look forward to our meeting with them on Thursday morning.
Some of the Kubuntu Devs
Talking and hacking in the corridor
Sebas celebrates the release of Plasma 5
David Explains Frameworks 5
Morning exercises led by President Lydia
Konqi and family
Cast your vote by choosing 5 wallpapers that you'd like to see in Lubuntu 14.10.
As we are a bit short on time this time around, we will have to close the poll on the 10th of September.
Please feel free to share the word and good luck to all contestants!
I really enjoy couscous and while it's often best in warm dishes, it makes a great pasta salad too; pasta salad it needn't always be some mayo-dressing + macaroni. Couscous mixed with a bunch of chopped vegetables & herbs in a vinagrette and served cold makes a great meal (or side dish).
You can make this salad with almost any crisp vegetable you like (or combinations of vegetables), you don't have to use all the ones I list in this recipe.
- 2 cups water
- 1 teaspoon salt
- 1 cup couscous
- 2 tablespoons olive oil
- 1 red pepper, chopped
- 1 tomato, chopped
- 1 celery stick, chopped
- 1/2 cucumber, chopped
- 1/2 red onion, chopped
- 1/3 cup black (or kalamata) olives, sliced
- 4 tablespoons feta cheese chopped/crumbled
- handful of parsely, chopped
- 2 tablespoons red wine vinegar
- salt & pepper, to taste
Makes about 4 cups
- Bring the water to a boil, add the salt.
- Remove from heat and add the couscous, stir amd let set until the couscous has absorbed the water.
- Transfer cooked couscous to a large bowl and toss thoroughly with olive oil to keep from sticking.
- Add the chopped red pepper, tomato, celery, cucumber, red onion, black olives, parsley & feta and toss to combine.
- Season with the vinegar, salt & pepper.
- Cover and chill in a refridgerator for at least 2 hours before serving.
Aunque hay (bastante escondido en su web) un manual oficial, lo hacen de un modo un poco raro. Lo fácil es el método de conexión normal:
- Pulsamos en la WIFI de Telecable:
- Dejamos estos campos como se ven en la captura (el firstname.lastname@example.org será tu NIF en minúscula en el modo email@example.com; la clave la que te asignen, que puedes cambiar desde aquí):
- E ignoramos el warning de certificado y marcamos que no nos avise de nuevo:
My book to read for this trip finally arrived from the library last week, and I could hardly wait to dip into it. I see a profound parallel between the work we do in KDE, and the experiences Catmull recounts in his book. He's structures it as "lessons learned" as he lead one of the most creative teams in both entertainment and in technology. His dream was always to marry the two fields, which he has done brilliantly at Pixar. He tried to make a place where you don't have to ask permission to take responsibility. [p. 51]
Always take a chance on better, even if it seems threatening Catmull says on p. 23. When he hired a person he deemed more qualified for his job than he was, the risk paid off both creatively and personally. Playing it safe is what humans tend to do far too often, especially after they have become successful. Our stone age brains hate to lose, more than they like to win big. Knowing this about ourselves sometimes gives us the courage to 'go big' rather than 'go home.' I have seen us follow this advice in the past year or two, and I hope we have the courage to continue on our brave course.
However, experience showed Catmull that being confident about the value of innovation was not enough. We needed buy-in from the community we were trying to serve.[p 31] My observation is that the leaders in the KDE community have learned this lesson very well. The collaborative way we develop new ideas, new products, new processes helps get that buy in. However, we're not perfect. We often lack knowledge of our "end users" -- not our fellow community members, but some of the millions of students, tech workers and just plain computer users. How often do teams schedule testing sessions where they watch users as they try to accomplish tasks using our software? I know we do it, and we need to do it more often.
Some sources rate us as the largest FOSS community. This can be seen as success. This achievement can have hidden dangers, however. When Catmull ran into trouble, in spite of his 'open door' management style, he found that the good stuff was hiding the bad stuff.... When downsides coexist with upsides, as they often do, people are reluctant to explore what's bugging them for fear of being labeled complainers.[p. 63] This is really dangerous. Those downsides are poison, and they must be exposed to the light, dealt with, fixed, or they will destroy a community or a part of a community. On the upside, the KDE community created the Community Working Group (CWG), and empowered us to do our job properly. On the downside, often people hide their misgivings, their irritations, their fears, until they explode. Not only does such an explosion shock the people surrounding the damage, but it shocks the person exploding as well. And afterwards, the most we can do is often damage control, rather than helping the team grow healthier, and find more creative ways to deal with those downsides.
Another danger is that even the smartest people can form an ineffective team if they are mis-matched. Focus on how a team is performing, not on the talents of the individuals within it.... Getting the right people and the right chemistry is more important than getting the right idea.[p. 74] One of the important strengths of FOSS teams, and KDE teams in particular, is that people feel free to come and go. If anyone feels walled out, or trapped in, we need to remove those barriers. When people are working with those who feed their energy and they in turn can pass it along. When the current stops flowing, it's time to do something different. Of course this prevents burnout, but more important, it keeps teams feeling alive, energetic, and fun. Find, develop, and support good people, and they will find, develop, and own good ideas."[p. 76] I think we instinctively know in KDE that good ideas are common. What is unusual is someone else stepping up to make those "good ideas" we are often given, to make them happen. Instead, the great stuff happens when someone has an itch, and decides to scratch it, and draws others to help her make that vision become reality.
The final idea I want to present in this post is directed to all the leaders in KDE. This doesn't mean just the board of the e.V., by the way. The leaders in KDE are those who have volunteered to maintain packages, mentor students, moderate the mail lists and forums, become channel ops in IRC, write the promo articles, release notes and announcements, do the artwork, write the documentation, keeps the wikis accurate, helpful and free of spam, organize sprints and other meetings such as Akademy, translate our docs and internationalize our software, design and build-in accessibility, staff booths, and many other responsibilities such as serving on working groups and other committees. This is a shared responsibility we carry to one another, and what keeps our community healthy.
It is management's job to take the long view, to intervene and protect our people from their willingness to pursue excellence at all costs. Not to do so would be irresponsible.... If we are in this for the long haul, we have to take care of ourselves, support healthy habits and encourage our employees to have fullfilling lives outside of work. [p. 77] This is the major task of the e.V. and especially the Board, in my opinion, and of course the task of the CWG as well.
Isn't this stuff great!? I'll be writing more blog posts inspired by this book as I get further into it.