Slashdot Mirror


How Can I Contribute To Open Source?

rtobyr writes "I work for a state government agency. That means we can't donate money, because it's a 'gift of public funds.' I had the idea to put up a Web page stating that we 'use the following free software to save tax dollars,' as a way to help spread the word about open source software, but management calls this an 'endorsement.' A mirror server is a no-go as well. I'm certainly not a talented enough programmer to help with development. I've donated $10 here and there out of my own pocket, but I'm hoping you Slashdotters have some creative ideas about how my organization could give something back to the teams that create free software we benefit so much from."

3 of 332 comments (clear)

  1. Get others in Gov to use it by Faizdog · · Score: 5, Informative

    The knowledge that government agencies are using open source tools probably does a lot to legitimize such software. Even if you can't publicize it, you can probably let other government agencies/depts know what you use and how it helps you and how it helps with your budget (crucially important to every government entity) and encourage them to adopt similar practices; hell help them out with doing so and making the transition.

    Eventually, the word will get out through suppliers, vendors, potential news articles, etc and will do more to help the movement than small monetary donations. Whaddya mean that program x is unreliable, the fire dept/tax agency/welfare dept, etc uses it?

    --
    -"Those who fought today will die tommorow."-
  2. A Dichotomous Question? by eldavojohn · · Score: 5, Informative

    How Can I Contribute To Open Source?

    This question seems to be distinctly different from your paragraph. Your $10 here and there is something I've also done many times. And it's great to hear that I'm not alone. From buying Firefox swag to just realizing that FOSS Product A saved me (at least) three days of my time so the least I can do is paypal $20 to those in charge.

    So if you'd like to contribute in other ways, pick a project that has something that you know a lot about or are passionate about and try to make small improvements submitted as patches. Good with embedded C? Try to help out the Firefox team in squeezing out cycles. Good with computer vision algorithms? Hit up OpenCV or even write some more script/extensions for the Gimp. What's your passion? The most important thing to remember is to not get discouraged when your patch gets rejected or deferred or sent back. Ask for feedback from the team and keep in mind you're there to support them. Firefox might be too closely knit of a project for you to break into but just perusing sourceforge or github will open up your eyes to who's out there looking for your help. A lot of these projects have wish lists.

    But what I'm hearing from you is that you'd like to give FOSS more recognition than contributions. No one wants your management or tax payer to feel obligated to fund open source. That flies directly in the face of what open source wants to do for you.

    I had the idea to put up a Web page stating that we 'use the following free software to save tax dollars,' as a way to help spread the word about open source software, but management calls this an 'endorsement.'

    Above all, respect your management. Were I in your place, I'd take a page from the DoD and on your page post side by side both the open source products you use and the proprietary products you use with a brief explanation. Get your management to approve this (pending security concerns) and whenever a change is made or an addition of open source product is used, put it up. I think you'll find that your page--if not from the get go--will slowly start to paint a common picture: the coexistence of open source products and proprietary products not only working side by side but also supporting each other.

    I would not recommend trying to make a business case out of government funded changes to open source products unless you have someone high up in your pocket and on your side. Doing something like that could really make you look foolish if you have no clout to begin with and could injure your reputability. Just a thought, you're free to proceed as you see fit.

    --
    My work here is dung.
  3. Some ideas by booch · · Score: 5, Informative

    It's not directly aimed at your particular situation, but I created a list of ways for non-programmers to contribute:

    • Submit bug reports
    • Suggest new features and options
    • Make other comments on how to improve the the quality of the program
    • Help write good documentation
    • Translate the documentation (and program text) into another language
    • Read exisiting documentation, follow the examples, and make corrections
    • Correct spelling and grammar mistakes in documentation
    • Develop spelling and grammar style conventions for documentors
    • Build a glossary of technical terms
    • Convert documentation into more useful formats (i.e. DocBook)
    • Create templates to write documentation in a WYSIWYG word processor (AbiWord, KWord) and XSLT to transform it into DocBook
    • Create diagrams, screen-shots, and graphics for documentation
    • Submit graphics (icons, backgrounds) to use in the program
    • Help other people learn how to use the program (answer questions on mailing lists or IRC channels)
    • Write an email expressing your appreciation for the programs you use
    • Send the programmers post cards
    • Send the programmers a virtual beer
    • Write your legislators about the concerns that Open Source programmers have with recent and upcoming legislation
    • Write book reviews and critiques
    • Write a book
    • Maintain a FAQ or HOWTO document
    • Help organize LUG events, including InstallFests, BugFests, and DocFests
    • Help write articles for the LUG newsletter
    • Help update the LUG web site
    • Help maintain a web site for an Open Source project
    • Design a better user interface for your favorite program (GLADE and Qt Designer are great for mocking up a new UI)
    • Run usability studies
    • Create validation or regression test cases
    • See how a program handles streams of random data
    • Package the application for a particular Linux distro (or other OS)
    • Get the program to compile on a new platform
    • Create a Linux advocacy web site (probably not so easy to do right)
    • Provide training to new Linux users
    • Read relevant standards and make sure the program follows them
    • Convince people to chose Open Source products when possible
    • Write up case studies of successful Open Source implementations
    • Send the programmers some money

    The original list can be found here.

    --
    Software sucks. Open Source sucks less.