i had a fantastic time contributing some code to the ghost.org blog platform. they are incredibly well managed, fantastically transparent, and provide a great d

i had a fantastic time contributing some code to the ghost.org blog platform. they are incredibly well managed, fantastically transparent, and provide a great deal of support for people contributing to the codebase. very much an a+++++++ would contribute again situation. Probably the thing that sets any receptive project is its ability to identify areas where it needs help and setting aside well defined (and documented) projects in those areas. In many projects, there's lots of work needed to be done but the priorities aren't obvious and so lots of contributions get left on the floor because they're just not in any way priorities for the active maintainers. it takes lots of work and maturity for a project to advertise this sort of stuff which is why these situations seem few and far between. Regardless, try to invest time in filling in the current needs of projects rather than unsolicited work. some unsolicited work (bugfixes) is easily accepted, but features are often hard to incorporate especially if they're not aligned with the short term goals of the project.