Git Product home page Git Product logo

feedmereadmes's Introduction

Feedmereadmes: A README Help Exchange

This project originated during a conversation at FOSDEM 2017 between folks at RedHat and (at the time) Zalando. It's here to serve:

  • project authors looking for README feedback and help. Add the link to your project README via this repository's Issues tracker to request editing support and feedback to help you sharpen your project's "why," "how," and "what." (If you want to try doing an edit yourself first, take a look at this product analysis template—it offers guidance.)
  • writers and editors who would like to help the open source community but aren't sure where to start. Pick a project in the Issues tracker and start working your magic. GitHub's tutorial for new users will help you to find your way.
  • product specialists/managers who want to contribute to open source development. Lend your storytelling expertise to help project maintainers strengthen their project purpose and vision.

Note: Please submit only READMEs, not full sets of documentation or manuals.

Press + Quotes

Inspiration List

Go here for relevant articles, talks, and projects that we find inspiring. Add your own favorites via pull request.

Why We're Doing This

Documentation remains an overlooked part of OSS development. How this plays out:

  • No basic install/run/config instructions, which creates friction for potential users.
  • No explanation of why projects exist, how they're unique, or how they solve problems.
  • too-short or outdated READMEs.

Feedmereadmes aims to help bridge the gap between project maintainers who want to make their docs user-friendly, and people with writing and editing skills who can help them. We define "user" to include non-developers and aim to tell compelling stories. "[C]ode isn't self-documenting" is one of our mantras, as per Mike Jang's 2015 OSCON talk offering Ten Steps to Better READMEs.

Our Project Aims, in No Specific Order:

  • make READMEs clearer and more useful
  • help project creators explain the "how" and "what"
  • offer guidance that might otherwise be unavailable to individual creators
  • generate discussions and new ideas around README development
  • draw more attention to docs and doc-writing
  • provide a safe, simple, fun gateway (or gateway drug?!) for non-devs to contribute to OSS

A Note to FOSS First-Timers Who Write/Edit: Why Work for Free?

Some of us have worked as full-time writers and editors. So we understand that requests to work for free can be annoying and even insulting. Free doesn't buy dinner, or pay the rent. With that in mind, consider why you want to contribute to a project. Don't over-commit. Start with helping one project, then assess your experience. Did you like it? Did you not? What would make it better? Would you do it again?

Many of us contribute to FOSS projects at work; we are lucky. You might not have this opportunity ... yet. Many of us non-devs working in the tech industry have created our own jobs. Our writing, editing and communications skills are valuable.

One thing to keep in mind, in FOSS and in life: Go where it's warm. If a project creator treats you poorly, assert your boundaries. Seek collaborators who make you feel respected, appreciated, and "one of us." Don't settle for less.

feedmereadmes's People

Contributors

epaul avatar getconor avatar jasonnovich avatar jerodsanto avatar lappleapple avatar pbh101 avatar rektide avatar remotesynth avatar tbroadley avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

feedmereadmes's Issues

Chemfiles readme

Hi !

Thank you very much for proposing this, it will be very useful to the whole open-source world.

Could you give a look at the readme of the chemfiles library: https://github.com/chemfiles/chemfiles?

The project intended audience is scientists who are not necessary developers, put are putting together small scripts/programs for research. I'm not telling more, I hope the README can explain the rest =)

Thank you very much !

Feedback on README for Dataverse

Hi! I just stumbled upon "maker of @feedmereadmes" at https://twitter.com/LauritaApplez and think it's a great idea to encourage projects to give and receive feedback on READMEs. I'm especially interested in the README maturity model you've come up with.

From what I understand I'm supposed to create an issue and link to my project's README and ask for feedback. Please take a look at the README at https://github.com/IQSS/dataverse and let me know what you think! Thanks!

(I wish I had know about Feedmereadmes before today because I just gave a talk last week about open source and would have mentioned it!) 😄

Gaphas README

Hi, I just spent a lot of effort completely revamping the README for Gaphas. I would very much appreciate some feedback to help me further sharpen the why, how, and what, and of course any other feedback would be awesome as well. ❤️

Add page for README/docs inspiration

Takeoff Readme

I've been trying to make the documentation for my project clear but would appreciate some feedback (especially as someone commented the Readme wasn't good enough

https://github.com/takeoff-env/takeoff is the main repo (which also drives the documentation on https://takeoff.sh via github pages, but the Readme is the index and the "hook" for people). This is the main tool I'm publishing.

It also ships with blueprints which include their own documentation and the default blueprint is here https://github.com/takeoff-env/takeoff-blueprint-basic

Apache Mahout README.md review

Hi,

first of all, thanks for this initiative! I think explicitly getting feedback on project documentation is an awesome idea.

As for the actual help request: It would be lovely to get feedback for the following readme:

https://github.com/apache/mahout/blob/master/README.md

Please note that while I'm part of the group of committers listed for this project, me posting this issue here is my personal initiative. So when posting feedback it might be worthwhile to let people know that I'm the one to blame for seeking input.

As an additional note, people on our project are right now working to improve the documentation and website. So in case of time left, feedback on the progress made there, as well as on how easy it is to find that progress as a new motivated contributor would be highly appreciated.

Thanks again,
Isabel

Please review

Hi,

I would like to ask for a review of the multilanguage readmes of Spring Cloud example, a hello-world app written entirely in Kotlin. This app is for demonstrating / learning Microservices architecture.
Thanks in advance for your work!

Cheers,
Paul

Node Serialport

Node Serialport is a widely used nodejs serialport library. I have users from all languages and countries, a lot of people new to javascript development and software development as a whole. To make it even more interesting we have at least 3 versions of serialport in wide use and the very old ones have a lot of bugs.

I have a few goals;

  • Making sure non english speakers can approach the documentation.
  • Making sure people can find and understand the installation guides, as a lot of support issues are solved by linking people to the docs.

https://github.com/EmergingTechnologyAdvisors/node-serialport

Italian Digital Citizenship APIs README

Hi @LappleApple ,

one of the projects of the Italian Digital Transformation Team is to build a set of API that will be used by government agencies as the foundation for their digital services.

We're currently working on the first iteration of these APIs that will provide:

  • a communication interface for sending messages to citizens through several digital channels (initially e-mail and SMS)
  • a repository of user preferences that citizens can set and that services can read to deliver personalized experiences to the citizens

This is the main repository of the APIs code, with the README (the audience is toward contributors and service developers).

Thanks in advance for the feedback! ❤️

Hack typeface README feedback

Thanks for offering this fantastic service Lauri and gang!

We would love input, critiques, and edits of our README page (and all other documentation in the project for that matter) for the Hack project and highly encourage participation in the project by any interested technical writers out there. We are definitely open to contributions from those who have never contributed to open source projects and would like to experience the workflow/interactions with development teams and the community around a project.

https://github.com/source-foundry/Hack/blob/master/README.md

Please let us know how we can assist any writers with the contribution process beyond the documentation that you provide here. They are welcome to open new issue reports on the repository for anything that they would like to discuss (prior to or during work on the docs) and submit pull requests with their edits. Our CONTRIBUTORS.md page includes our documentation contributors and writer participation in the project will be acknowledged there irrespective of whether they commit changes or would like to work via issue reports with our team making the repository modifications (though it would be to their benefit to learn the former path if they are unfamiliar with it and intend to broaden their OS project participation).

Thanks again and let us know how we can be of help!

Explain the role of wikis, and use the wiki here

Opening a project's wiki to any registered user can open a breeding ground / incubator for catching ideas in raw form and polishing them for inclusion into the "official" documentation. It fosters collaboration much more so than the rigid time-line format of an issue thread, and potentially lowers the threshold for new contributors.

Like in this project, where you could have a page to discuss improvements of the "Inspiration" page. 😉

A README should link to the wiki, and explain what it's main purpose is (main docs, experiments / drafts, …).

Please review the readme for FlubuCore

Hi,

We would like to ask for a review of the readme of FlubuCore, a cross platform build and deployment automation system for building projects and executing deployment scripts using C# code.

Thanks in advance, and for your work.

Marble Marcher: Community Edition README review

Hi! I manage the project for the community edition of a game, the upstream of which has stopped development. I'm a bit worried about the size of the README itself, even though the building process itself is quite complex and warrants the size. If you have any suggestions, it'd be much appreciated. Thanks!

Link

Feedback for README.md of MapStruct

Hi, I just learned about this project/service -- it's a fantastic idea!

If you have the time, we'd love to have your feedback on the README of MapStruct: https://github.com/mapstruct/mapstruct. We spent quite some time on it originally, but since then it has aged a bit and I think there are a few opportunties for improvement. Any thoughts and input on that would be very much appreciated.

Gaphor README

Hi, I just spent a lot of effort completely revamping the README for Gaphor. I would very much appreciate some feedback to help me further sharpen the why, how, and what, and of course any other feedback would be awesome as well. ❤️

ffind review

Hey there!

I'm looking for feedback in the ffind README page.

Thanks a lot in advance! This is a great initiative

Cheers,
Jaime

Diesel review

Hey folks,

Thanks in advance for taking the time to look at this. I'm interested in feedback for Diesel's README. We also have a lot of stuff on our website diesel.rs, so the README Is intentionally a bit light. (Not sure if y'all are interested in reviewing websites as well)

VaporShell Readme.md Review Request

First:

Thank you so much for offering this service! It's pretty fantastic!!

Second - Here's the GitHub project Readme that I would love some help with:

https://github.com/scrthq/Vaporshell/blob/master/README.md

Third - Background:

The Readme I have there is mainly a pointer towards the documentation site I build on top of GitHub Pages w/ a custom domain. I've been building VaporShell completely solo, down to the website design (http://vaporshell.io/), all of the source code, and any associated Readme's. It's the first project I've really done on this scale and is for a tool that I feel is a huge help to SysAdmin's working in AWS with CloudFormation / Infrastructure as Code in general. VaporShell itself is a PowerShell module designed to allow easy creation of CloudFormation templates by leveraging Powershell's featureset and syntax. This allows you to do things like tab-completion of valid values for specific parameters, tab completion of resource parameters in general (there are over 600 resource types available in CloudFormation with varying property sets between each one, so remembering all of those tends to be a little overwhelming), and many other things. Another key point for the project is cross-platform compatibility, now that PowerShell Core / .netcore is becoming a bigger focal point. All development and CI tests are done on both .NetFramework (Windows/AppVeyor) AND .NetCore (Ubuntu for local dev/testing, Ubuntu/macOS in Travis CI for CI integration)

Fourth - Plans for the near future:

v2.0.0 is coming soon (within the next month). Updates are geared around including full CloudFormation stack management (i.e. deploy/update/delete/monitor -- current iteration is template building only) via the .NET / .netcore SDK's from AWS

Thanks again for helping out OSS projects!

  • Nate / SCRT HQ

Results?

Super interesting project.

I was hoping to see the before/after of some reviews somewhere, maybe links to issues or PRs created. Or to say it in the words of the maturity model:

[...] evidence of past performance in real development situations.

😄

Did I miss it or doesn't this exist (yet)?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.