Skip to content

Fedora Summer Coding organizing – halp!!!

06-Apr-10

We are trying to turn the lights on for a new program this year, Fedora Summer Coding 2010.

This is more than making lemonade out of lemons.  After we figured out that the whole idea of summer coding wasn’t kinda-sorta-good but actually pretty great when done right for your own community, it was clear we needed to do our own implementation of the summer coding model that Google first defined.

Although the plan was to test ideas during GSoC this year, we don’t get that luxury.  Instead, we get the enviable position of taking a cool brand, Fedora, and create for it our own program to meld college students, mentors, summers, code, and community.

If you are at all interested, join the SIG mailing list where we are discussing how all the structure comes together.  Use the step-by-step guide for organizers to get started.

Look forward to working with you!

(Fixed link to SIG mailing list.)

Ideas for summer coding due by 14 April (updated)

06-Apr-10

While we finish the Summer Coding 2010 page, it is past time for you all to let us know the problems you would like to see solved by summer coding/internship students.

Idea page is here:

https://fedoraproject.org/wiki/Category:Summer_Coding_2010_ideas

How-to fill out an ideas page is here:

https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding

Let’s get this filled with serious ideas you are willing to mentor for or help find the mentor.

Join the discussion list and be prepared to talk about your ideas or proposals.  If you were already a mentor and want to help with mentoring, such as proposal reviews, let us know and join the mentors list.

Tracking these ideas is a PITA and in fact the lack of an ideas page lead to us not getting in the Google Summer of Code this year.  This is all part of a larger issue around tracking smaller ideas for beginners and students, but for now this will have to do.

Anyone want to hack on OpenHatch.org, please help.  We’re hoping some of the functionality we are handling manually may be included in upcoming versions of OpenHatch.  If that direction gets us fruit, we may use OpenHatch as an ongoing way to expose projects to students and other new contributors.

(After this initial schedule, the SIG moved the deadline to 14 April. Post title updated to reflect but at same permalink.)

Seeking sponsors: universities, corporations, foundations, individuals, creative ideas

02-Apr-10

A cornerstone of our Fedora Summer Coding is connecting sponsors (those with resources to share) with students (those with time, passion, and skills to share.)  It’s not necessary as a sponsor to have ideas of how your resources should be used, that’s what the Fedora Project and JBoss.org mentors and sub-projects are prepared to do.

We’ll also sort the student ideas, generate the list of approved proposals, work with the students throughout the summer, and make sure you hear back about how things went.  You can learn more about the model we are using in this blog post, Summer Of Code Swimchart: Now With More Generic.

We need to start talking, soon.  I know it’s pretty late in your budget cycles and academic planning year.  But you would be surprised what a pool from a number of us can do.  It’s worth talking about, at the very least.

What are the resources you can supply?

  • Money to pay stipends to students for spending focused time on these FOSS projects.  This is a cross between a summer job and an internship.
  • Someone to help coordinate and to contribute as part of the Fedora Summer Coding special interest group (SIG).
  • Mentors, especially if they work actively in sub-project or area the sponsor is supporting.

What do you get out of it?

  • Positively impact FOSS projects.
  • Get your brand in front of smart students who want to work on FOSS.
  • Work on a community program that demonstrates how open source business is done.
  • See something you’d like coded be completed.
  • Other positive brand associations.

Can’t miss.  Can’t hurt to talk to us about it.  If you want to contact me directly for whatever reason, please do.

Redialed Fedora Summer Coding plan, time to help

01-Apr-10

Now that the textbook is out and in use, I’m turning my random spitball approach1 at Fedora Summer Coding.  We had a SIG meeting yesterday, and today I worked on updating the plan.  With that plan we can populate the messaging page.  What’s that?  It’s where people read what they need to know, depending on who they are:  student, mentor, sub-project, sponsor, upstream, administrator, community member, and so forth.

As it often is with good ideas, there are other FOSS projects doing similar things.  The page for Ruby Summer of Code looks really good, I’ll be mining it for ideas.  There is also the Joomla! Student Outreach Program.  They all seem to be using a model similar to what Mel described in her blog post, “Summer Of Code Swimchart: Now With More Generic.”

If you are interested in helping us create this program, now is a great time to join in and help.

  1. Cf. laser-like

Textbook released – Practical Open Source Software Exploration

01-Apr-10

After months of work and a last-weekend rush of conversion from MediaWiki to DocBook+Publican, the Teaching Open Source writing team has released version 0.8 of “Practical Open Source Software Exploration: How to Be Productively Lost the Open Source Way“.  (HTML single-page and PDF.)

This week, Dr. Tim Budd at Oregon State University (and member of the Teaching Open Source community) began using the textbook for a class introducing FOSS programming and contributing.  We’re looking forward to getting feedback from the students. More…

More on Publican

01-Apr-10

When writing about the Practical Open Source Software Exploration textbook release, I had a bunch of extra thoughts about Publican that I wanted to separate out to its own post.

My sense is that Publican is in good shape for groups to adopt and extend.1  For example, there was a recent discussion in a MeeGo developer list about what tool to use for end-user help on the device console.  The first version of this help documentation for device users is going to be written using RoboHelp, a proprietary platform that has long been used for this type of capability.  (The thread does a good job of explaining the reasoning.  From my perspective, Intel and Nokia are showing thinking that is evolved and learned from the old days, such as when Red Hat Linux became RHEL and Fedora.  It shows they are learning how to use the open source way.  I’ve met and had discussions with various community facing folks from Intel and Nokia over the last few years, and they were listening and talking the open source way.  Interesting to see how others handle the experience.)

It seems like a good extension of Publican to handle this sort of help output, and if the MeeGo community coughs up a Perl hacker it can probably create the functionality relatively quickly.  Publican has been designed by the Red Hat Engineering Services team to support a need to deliver source documents + translated strings as multiple target outputs.  I’m sure it can be made to match the i18n requirements of the MeeGo documentation folks.  (I just learned that Publican has an EPUB output format, no reason it can’t be easily extended to a ‘help’ format.)

In the MeeGo thread, Dave Neary says,

Im (sic) my dream world, there would be a web application with a wiki-like interface, which would be a view to docbook sources, where changes were sent to a submission queue rather than being immediately displayed, where a maintainer could review and modify/reject/accept proposed changes, and anyone could view the review queue to see what the status for their proposed patch was. I don’t know of any such application 🙁

Dave, I think those components exist and only need a little bit of glue to work for you.  Publican plus an SCM on the back-end with Beacon running as a WebUI wysiwyg front-end.  In the summer of 2009 Satya wrote code that extended Beacon to support a subset of DocBook that the Fedora Docs Team identified as most used inline and block tags.  You plug Beacon in to a CMS as an editor to handle a writing/editing/l10n/publishing workflow.  (I think the CMS needs to handle the check-in/check-out with the SCM on the back-end, making the XML files available for edit, and probably adding a commit button in the chain so files can be saved as they are worked on without triggering a nonsense commit.)

We’re working on implementing Zikula in some CMS roles for Fedora, and I hope to see us adopting the Beacon editor there as a choice for writers.  This is going to be a whole new effort, and I’m waiting on the first Zikula instance, Fedora Insight, to be running before rallying more support via the SIG.

  1. I have not always held this view, which is one reason for this public endorsement.

A better way to use Wikipedia in the classroom

28-Mar-10

This is an idea I’ve said in presentations and in person over and over again, about time I give it a home.

Where Wikipedia is a useful information source and starting place for deeper exploration beyond it’s reference-focused world, there is so much more that can be done with it to help teach the open source way.

In fact, you can teach all of the basics of joining a collaborative free and open source software community without ever getting more technical than how to get an account and edit a wiki page.

Here’s the process I would follow, in a US-based classroom.  You can adopt to fit in your environment.  This is applicable to all age levels – I’d encourage six-year-olds to define a good Summary log message and click the Save page button.  A good reference is the Wikipedia article on creating your first article.

More…

Observe the operating room – wiki2xml sprint for FOSS textbook

26-Mar-10

There is a work sprint you might be interested in observing or participating in if you …

  • Use MediaWiki for writing long works and want to see how it is to convert to DocBook XML.
  • Want to know more about using DocBook XML and the Publican publishing toolchain.
  • Enjoy watching people edit XML like mad.

We’ll meet Friday 26 March starting at 1400 UTC in #teachingopensource on irc.freenode.net (or WebUI at http://webchat.freenode.net/?channels=teachingopensource) and continue through the weekend until done.  Full schedule and participation details are on the Teaching Open Source wiki.

As part of the work of giving college/university-level educators the experiences and tools they need to effectively teach participation in free/open source software projects, we’ve been working on a textbook.

http://teachingopensource.org/index.php/Textbook_Roadmap

The textbook, “Practical Open Source Software Engineering”, is releasing a first functional version, 0.8, this coming Monday 29 March.  The goal is to see it in use in at least one classroom this spring, which we’ve been discussing on the Teaching Open Source mailing list.

Diversity check

25-Mar-10

Please remove your house colors for a moment and let go of your pre-judgement about the word diversity.

A diversity check is the moment when you look something over you have done, such as a presentation/talk, documentation, writing a blog post or an email, where you must think, “Did I just write this for people only like me, or does it make sense to a diverse audience?  Will a diverse audience find offense where it is not intended?  Will I turn away people I want to attract and keep around?”

As an example, imagine if you were trying to build morale in a group and you wrote, “Cheer up!  Put a smile on your face!  We’ll make it through these tough times together.”  As the optimistic extrovert I am painting you as in this example, this advice makes sense to you.  You find that putting good cheer on your face helps you be brave for tough experiences.  You consider it important to simply trust that we’ll survive and thrive.  But do you know how many of your audience feel the same way as you do?  Do you know how your words are affecting them?

What is your goal, in this example?  Are you trying to bring up the group’s morale or trying to make the world be like you?  Uh, what did I just ask?

If you want to raise morale, you need to address all of your audience.  Some people are tired of being told to put a smile on their face they don’t feel in their heart.  Some feel treated as if they were children or idiots or as if their experiences and feelings are being ignored.  Some people only feel comfort when they have updated and accurate facts.  Some raise their morale with their circle of friends by sharing and recounting negative experiences.

The phrase catching me recently, one where I’ve been writing around and around it, is the admonition, “Be bold,” as in this paragraph from the page telling how to write on the Fedora Project wiki:

Be bold while editing changes. Wiki changes are tracked and can be reverted when necessary. This doesn’t mean you should be reckless, especially when making large changes to key documents.

Concentrate on how “be bold” makes you feel.

If you feel emboldened to edit the wiki, then the message works for you.

But for some of you, that instruction is going to make you feel uncomfortable.  Or it will frighten you instead of inspire you.

The point isn’t for you to understand how different views feel from the inside.

The point is to understand that there are different views and check your words and methods. Seek to be inclusive. Don’t try to create a bond by forging Us against an Other Them.

Sometimes the most important thing to do is to simply recognize there are other experiences and you don’t fully understand them.

So …

“When I feel discouraged, I put a smile on my face to give me courage and hope in the face of adversity.  Whatever I can do to help you feel better during these adverse times, please reach out to me.”

… and …

“We encourage you to be bold when editing the wiki because wiki changes are tracked and can be reverted when necessary.  We would rather you do something than wait for permission.  Our culture doesn’t run on permission, it runs on people recognizing something needs doing, then doing it.  If you feel you have found something worth doing, please go ahead and do it.  And encourage others to be bold while you are at it.”

Confused aka not entirely an Ada Lovelace Day tribute but thanks anyway Lana

24-Mar-10

As soon as I decided to write an Ada Lovelace Day tribute to a woman in computing, I almost immediately stumbled across Lana Brindley’s post on computer engineer Barbie.  It was a nice serendipity.  This week Lana’s posts on technical writing were both inspiring and directly helpful in terms of supplying content to a textbook we are working on.  (Honestly, I’m also hoping she is interested enough to help us make that chapter the canonical upstream for practical textbook-like instructions on how to technical write for FOSS projects.)

So I thought about doing a post on Lana, even though our paths have barely crossed.  She’s a great writer, she brings passion and dedication to technical writing, and is an excellent advocate for FOSS documentation.  Aside from being one of the writers on the stellar Red Hat content team, Lana has been recognized as a top FOSS writer.

She also wrote a post today that was sort of an Ada Lovelace Day tribute.  It was about the Unicorn Law.

From Ada Lovelace Day 2010: Unicorns

Often, when a woman joins an all-male technical environment, they will look at her strangely. They might try and pretend that she’s a bloke, that she’s just ‘one of the boys’. They might ignore her. They might make a few distasteful jokes and then get on with the job. But mostly, what happens is that a woman is noticed.

Had my own cross with the Unicorn Law recently.  The law states, “If you are a woman in Open Source, you will eventually give a talk about being a woman in Open Source.”  I didn’t learn about this law until after I had agreed to have my daughters talk at SCALE 8x about … being girls in open source.  *sigh*  It was a great experience for them, and I’m sure mainly good will come from it, but the whole realization that I had pointed them out as unicorns without even realizing it was disturbing.

Today I’m feeling that same way about writing this post.  I wanted to write something, I decided I wanted to write about Lana Brindley because she is a woman in FOSS computing and works in a field near and dear to me.  She seems to have come to her writer’s passion honestly and serendipitously.  Reading about her life, I realize in many cases I could substitute myself in to her story, it has so many similarities, all the way up to seeing pictures of her plans to build a chook shed in her backyard where she gardens, grows, and consumes slow food.  (Hey!  Just like us! We have a chook shed, too, although we Yanks call it a chicken coop, and some of our hens prefer to lay outdoors. We have an urban farm with underground restaurants and pop-up events.  Small world.)

I’m not sure if Lana meant the irony in writing about unicorns today, most likely she did.  It has made my writing experience today all the more ironic.  It’s nearly Midnight here in California, my last chance to either finish this post or throw it away.  I set out wanting to give tribute to a colleague whose work has helped and inspired me, and now I’m feeling as if I’m also calling out her as an Other in just writing this!

Anyway, I’m confused, but that’s just me, I’m a newbie geekfeminist, this is not entirely an Ada Lovelace Day tribute, and thanks Lana for the words and wisdom.