Most popular (and unpopular, for that matter) open source projects would probably appreciate someone who wants to write high quality documentation.<p>A good approach might be to find some projects you're interested in on Github, and contact them to ask if they'd be interested in someone adding to/improving their documentation and project wiki. I suspect you'll find projects interested in this rather quickly. Then, contributing will be as easy as making a pull request. And that way, any potential employers or clients can easily verify that you've actually done the work you claim you've done by looking at your Github commit history.
The MISP project[1] which is an open source project around threat intelligence sharing is actively looking for contributions and supports to write documentation. There is already a git book[2] which needs some love and support especially on the aspect of using the platform for analysts or security operators.<p>[1] <a href="https://github.com/MISP/" rel="nofollow">https://github.com/MISP/</a>
[2] <a href="https://github.com/MISP/misp-book" rel="nofollow">https://github.com/MISP/misp-book</a>
I'm one of the maintainers for Redux ( <a href="https://github.com/reactjs/redux" rel="nofollow">https://github.com/reactjs/redux</a> ), and added a couple major sections to the docs. I'm always interested in more ways to improve the docs, whether it be new information, improving the writing, or something else.<p>If you're interested in helping out, file an issue and we'll see what you might be able to do.
Hi Philipp, the FreedomBox project could use your help improving the manual. Anything added up until the 22nd of Jan can still be included in the offline manual delivered with the project. It is a Debian Pure project, aiming to give non-technical users the possibility to run their own decentralized infrastructure on low-cost SBC's. We will do our own sprint the coming days, and all help would be appreciated :)<p>The manual can be found here: <a href="https://wiki.debian.org/FreedomBox/Manual" rel="nofollow">https://wiki.debian.org/FreedomBox/Manual</a><p>After that date we would still be interested in improvements to the online manual, the landing page, and anything else you would want to help out with!<p>If there are any questions, we are willing to provide all the answers we can on OFTC #freedombox
Freeplane - a mind map open source project<p>The freeplane community is craaaving for better documentation that can shed light to the multiple features of the program. The current docs/wiki are outdated/desorganized, and this has multiple times been recognized in the freeplane community as the #1 to priority to make freeplane easy for new users - new users just have a hard time going onboard because there are no good docs explaining the simplest things!<p>And the program is not hard, it's just missing good documentation!
The docs are sometimes called the "missing killer feature" of freeplane. So, If anyone with experience feels like joining in, it will be a joy for everyone :)<p><a href="http://freeplane.sourceforge.net/" rel="nofollow">http://freeplane.sourceforge.net/</a><p><a href="https://sourceforge.net/p/freeplane/discussion/docwriters/" rel="nofollow">https://sourceforge.net/p/freeplane/discussion/docwriters/</a>
I hope you don't mind me hitching a ride on this question, but what is a 'technical writer'? Can someone with excellent composition, grammar, spelling, and proof-reading skills become a 'technical writer' or does the writer need to have specific technical domain knowledge?
We, at the Open Bank Project, could do with some help. We are an open source API for banks <a href="https://github.com/OpenBankProject" rel="nofollow">https://github.com/OpenBankProject</a> - ping me if you want to get involved
We are also looking to hire a technical writer for NXLog. If you or anyone else is interested, feel free to reach out. <a href="https://nxlog.org/contact-us" rel="nofollow">https://nxlog.org/contact-us</a>
Hi,<p>Osmocom is an open source project that is searching for technical writers. You can check it out here: <a href="https://osmocom.org/" rel="nofollow">https://osmocom.org/</a><p>PS. They are offering a free femtocell for contributions.
Yes! I was just thinking about this, actually. We're building scalable tools for analyzing genetic data on Spark:<p><a href="https://hail.is" rel="nofollow">https://hail.is</a> <a href="https://github.com/hail-is/hail" rel="nofollow">https://github.com/hail-is/hail</a><p>It's tricky because we need someone who can write, has technical knowledge (python, Apache big data stack) and some knowledge of bioinformatics and statistical genetics. There might be an option for some paid work. What's the going rate for technical writing?
If possible, choose a large/well organised Open Source project which already has good documentation and people working on it.<p>That way you get involved with a team of people who should (in theory) already be following good practises, should have a sensible tool chain, and have habits you can learn from. And you'll make good contacts/references/potentially be hired.<p>(if you're looking to get hired as a potential result, choose a project that has backers with $$$ that hire from the Community :>)
Libreoffice is a great community and we'd welcome that kind of contribution. Come visit the documentation@global.libreoffice.org mailing list or #libreoffice-doc on irc
The real question is are there any who don't need one?<p>Your contributions would be more than welcome in my Open-Source project, CAMotics. It's a CNC simulation software.
The folks at docs.openstack.org are always looking for contributors :) As rpeden said, it's important to find a project you're interested in and think you can contribute to. It takes some time to get the vocabulary down for various projects, so choose carefully and spend some time making yourself known to the community and offering to help / learn.
Absolutely, we're actively looking for one for <a href="https://deepstream.io" rel="nofollow">https://deepstream.io</a>, please find more details here <a href="https://deepstreamhub.com/careers/technical-writer/" rel="nofollow">https://deepstreamhub.com/careers/technical-writer/</a>
<a href="https://github.com/begriffs/postgrest" rel="nofollow">https://github.com/begriffs/postgrest</a> could use a technical writer and would welcome one
Just applauding your effort here, not only for being proactive about getting into the field you want, but also for finding ways to contribute to open source without having to submit code. Keep it up!
The webpack 2 docs are ripe for improvement - I've been making minor contributions myself but there's still plenty to do. Checkout WebPack.js.org