Why You Should Send Flowers To Open Source Developers

IMG_1182

You are probably thinking flowers are dumb: they die and they don’t do anything; they are for dates, weddings and funerals. Besides, open source developers do not need flowers, they need money. But nobody wants to pay for software, let alone open source software. Even though today open source software is as vital as roads and bridges, nobody wants to pay to maintain it.

So by all means let’s figure out a way to get more money for open source developers. But in the meantime, here’s why you should still send flowers.

  1. Flowers show appreciation

Taskwarrior share some great lessons learnt for open source maintainers. This includes cautionary tales like: “People will pick a fight with you about all your incidental choices. Your issue tracker, your branching strategy, your version numbers, the text editor you use, and so on.” Open source developers are a tough bunch, but are still likely to suffer from burnout. Sending flowers is the ultimate gesture of positivity and understanding. Plus there is all sorts of research out there that suggests flowers & plants improve mood and promote creativity in the workplace.

  1. People think you are more capable & emotionally intelligent

If altruistic reasons are not enough, then consider this. The act of giving flowers has benefits for the giver. The act of giving makes people happy. There is also research that says people who send flower are perceived as having higher emotional intelligence, capable and courageous.

  1. You will be a better leader

Small things can make all the difference. This idea is partly inspired by my favourite blogger, who wrote about the effect receiving flowers from Marc Benioff, CEO of Salesforce had on her. Basically really good leaders are always thinking of thoughtful ways to get the best out of everybody.

OK so now I have a confession to make. Maybe I am telling you this because Kichwa Coders have recently joined the realm of open source maintainers, heading up and contributing to the January project  (numpy & datastructures for Java). And we are gearing up, together with the rest of the Eclipse Science Working Group, for our first major science release. It is an amazing project that will provide tool infrastructure for countless scientific projects. So it will be awesome, but there is still some trepidation when you cross the threshold from open source user to open source maintainer. It is a little bit like how when you have your own kids, you finally really appreciate your parents and wonder how they did it. Right now I am in awe of open source leads and maintainers everywhere. So just do it. Send flowers to open source developers. And while you’re at it, send some to your parents too.

Whose job is it promote diversity in the Eclipse community?

IMG_20160511_184220-002

I received an email inviting me to join a group to help improve diversity at an upcoming EclipseCon. I was surprised at how reluctant I was to help.  My first reaction was ‘I do my bit and it’s just not my job‘. Maybe it hadn’t help I had just been reading research suggesting women and minorities are the ones most penalized for promoting diversity. Nevertheless, the request had come from Alex Schladebeck, someone I have a lot of respect and admiration for and I simply could not say no to her. And I’m really glad I did say yes. One meeting had us all thinking, raised a lot of questions and generated useful suggestions. It also inspired me to look into the topic more thoroughly and I was surprised where the research led me and what the solutions should be. Continue reading “Whose job is it promote diversity in the Eclipse community?”

Eclipse: Open Technology for Everything and Nothing in Particular

Eclipse is so much, much more than an IDE these days. For starters, there are many exciting technologies being developed by the Internet of Things, Science and LocationTech groups. We really need to showcase these to the wider world. This was the excuse to have an event in London bringing together these different technologies and communities for a night of tech and merriment.

The event Eclipse Converge: blending LocationTech, IoT & Science was very generously hosted by Geovation, the Innovation Hub from the Ordnance Survey. We were very grateful for all the team there for help with organising and ensuring this event went off without a hitch. They have a terrific space and laid out quite a spread of food and drink, which set the scene well for our six speakers. Here is the story of the evening, partly-told by the lovely tweets from the community. Continue reading “Eclipse: Open Technology for Everything and Nothing in Particular”

Kichwa Coders Join Eclipse Science Working Group Steering Committee

Kichwa Coders is pleased to announce that we have become a member of the Steering Committee of the Eclipse Science Working Group. Kichwa has been an active member of the Science Working Group from the beginning and its involvement includes:

  • Leading projects related to Python scripting in Eclipse EASE
  • Organizing Eclipse community meetups in London (join us for our next one!)
  • Jonah Graham is project co-lead for the January Project for common data structures.
  • Tracy Miranda is on the Program Committee promoting the Science track for Eclipsecon France

Tracy Miranda will represent Kichwa Coders as the Steering Committee participant. The current Steering Committee is made up of members from IBM, Diamond Light Source, Oakridge National Labs and Itema. Kichwa Coders look forward to working closely with other Steering Committee members to shape the future direction of the group and encourage other organizations to participate in this vibrant ecosystem where advancing open-source software advances science.

3 Reasons I Love Eclipse

I love Eclipse. Not just the IDE, but the whole community and philosophy of it. There are no shortage of folks who will tell you how they hate Eclipse.  For a change I’d like to tell you why I love Eclipse.

  1. Polyglot IDE – Eclipse IDE is really great because you can use the same open environment for multiple languages. Java, Python and C are three of our staple languages and I often end up using them in combinations. Eclipse understands each of these really, really well and allows for some powerful integrations. There’s no place I’d rather run some Python on a target processor while debugging a Linux kernel.
  2. Determined developers – with all its functionality and extensibility maximising the power of Eclipse is pretty hard. The people in the community who do use Eclipse and master its complexity are full of grit; problem-solvers who won’t give up on their end goals easily. As a result, it’s a great community to be part of.
  3. Continuous evolution – early on in my career I worked with hardware, then I switched to software and today work involves keeping up with several different technologies. Likewise, over the years Eclipse has evolved a lot. Early on it was just an IDE, then a rich-client framework and today it features many thriving working groups growing in areas like IoT. Adapting and learning can be quite a journey, so it’s great to have a community along for the ride.