coreboot has grown and matured a lot in the last few years and we have many new contributors and users. This growth has been something I have been thinking about for some time. I often ask myself what makes a good community? How does our community grow and flourish? How do we get new contributors and new students for GSOC. How can I contribute to growing our community? These questions were on my mind as I attended the GSOC reunion in San Jose last fall and again later at the coreboot meetup in Prague. Discussions at both events helped shape my ideas, but GSOC reunion had some key elements to shaping a good community.
A reoccurring topic at GSOC gatherings is how to expand project communities, keeping students engaged after GSOC, and how to get new students and contributors involved with projects. Normally, these discussions are among mentors, who are well entrenched in the FLOSS culture, are experienced developers, and have developed strong relationships within their project. Unlike previous mentor summits, the GSOC reunion was open to past students and mentors to attend, which brought a different perspective. Many of the students were not involved in the projects after GSOC and we wanted to know why. This was an opportunity to hear from students about what worked for them and what didn’t work. Most of the students I met still used lots of open source software, but there were a number of reasons that they no longer developed on their GSOC project. Some students lost interest in the project, but still developed on other projects. Some students got jobs that didn’t deal with open source, but would do it again given the opportunity. Finally, there were some students (and mentors) that said that they didn’t like working in open source, that they were mistreated, forced or flamed out, or never felt welcome and appreciated. It is the last group that I wanted to make a difference in.
While most developers don’t experience something as terrible as the harassment that happened in the context of Gamergate or other terrible behavior documented at technical and open source conferences the last several years, it does indicate that there is a problem in our open source communities. This terrible behavior online and offline is unacceptable. You shouldn’t be required to have a thick skin to develop open source. It should be a collaborative, not combative environment. We can’t lose valuable contributors because they felt uncomfortable or unwanted. A few mentors of large communities have had to deal with some really ugly incidents (I’m trying to recall, but I think it was folks from Debian and Ubuntu among others) and they provided some great advice. The first was that mature communities should have some rules for behavior. The second, and maybe more important, is that community members must point out when someone is behaving poorly. I felt that these were important point and started to consider how to make coreboot a more safe and welcoming place.
Typically, harassment, trolling, flaming, etc is not a problem in the coreboot community. We have a group that is generally friendly and helpful. We try to encourage good behavior and discourage bad behavior, but we could do more. With a growing and maturing community we are going a step farther and describing what is unacceptable within our community with the coreboot Code of Conduct. It is a simple and straight forward statement about what we expect from out community members. The code of conduct is based on the Citizen Code of Conduct and similar documents in the open source community. Feel free to comment and provide feedback either publicly or privately. Please note that this isn’t directed at anyone in particular or for a specific instance. It is part of “growing up” as an active and maturing community.
Woot! A new look for coreboot.org. We have shifted the landing page from the mediawiki to WordPress. DON’T PANIC!, we are still using the wiki as the primary location for developer content. The new landing page and WordPress site is more visually appealing and is the location for news, blogs, and other basic information for those that are just discovering and learning about coreboot.
Congratulations coreboot’s GSoC students. coreboot has three students working on coreboot for GSoC 2014 .
Title: Enhance early coreboot debugging
Student: Kyösti Mälkki
Mentors: Martin Roth and Rudolf Marek
Title: Generic Interface using alternate CBFS access patterns for ARM SoCs
Student: Naman Govil
Mentors Aaron Durbin and Marc Jones
Title: The yearly flashrom maintenance and enhancement proposal
Student: Stefan Tauner
Mentors Carl-Daniel Hailfinger and David Hendricks
Each student is required to post progress to this blog. We expect first posts later this week. Stay tuned for progress!
We are excited to announce that coreboot has been selected for Google Summer of Code 2014. As with previous years, coreboot will also support flashrom and SerialICE projects.
All the information you need is on the coreboot GSOC page and the following project ideas pages:
We are in the Get Familiar period before the Application Period opens. Join the mailing list and IRC #coreboot. Start to get familiar with coreboot, our development process, and with the coreboot community. Discuss project ideas and scope with coreboot developers.
Student Application Period: March 10 – March 21
To be a mentor, you must be a coreboot contributor in good standing (review and commit rights). If you would like to be a member, please add your name to the coreboot GSoC mentors section and signup and connect with coreboot in melange.
Feel free to contact me (IRC:marcj) if you have any questions.
coreboot has been accepted to participate in Google Summer of Code, 2013.
coreboot has many Project Ideas for various firmware ability levels and the coreboot project also hosts flashrom and SerialICE projects. Please visit the wiki for additional information.
coreboot was not selected to participate in GSoC 2012. This is
disappointing new for the project. I do not know why we were not
selected this year. I will attend the post selection meeting to see
what we can do to improve our chances of selection next year.
Students, thank you for your interest in coreboot. We are happy that
you are engaging with our community. I hope that you continue
exploring your interest in coreboot. Please let us know what we can do
to assist you in your learning.
Feel free to send me questions, comments, or concerns.
Continue reading Flip Bits, Not Burgers – coreboot GSoC 2012 – Update
We are starting to see coreboot in more shipping products this summer and I expect even more in the fall. The exciting thing is that coreboot is becoming a piece of technology that vendors are starting to advertise. A recent example is the Portwell PCS-8277:
PORTWELL ANNOUNCES REVOLUTIONARY IN-VEHICLE PC
WITH THE BOOT SPEED OF AN APPLIANCE New PCS-8277 telematics system based on Coreboot® technology with HD graphics processing engine
I think that we are starting to see vendors and customers becoming more knowledgeable about what is going into their products and how coreboot is an advantage in many situations. I hope to see more announcements in the coming months.
AMD has added the Family10 G34 support to coreboot. This new support located in the AGESA vendorcode area. This AGESA code should be used for new Family 10 development. The initial development platform is the Super Micro H8QGI+-F mainboard.
Thanks to Kerry and Frank @ AMD for the submission.
A small side note, this addition put coreboot tree at over a million lines of code.