Opensource.guide: address poorly maintained projects

Created on 24 May 2018  路  9Comments  路  Source: github/opensource.guide

The guide so far doesn't address the delicate task of getting an unmaintained or poorly maintained project back on track when one isn't (yet) part of the maintainer team. There are many projects out there that have a small but significant user base and no or inadequate maintenance. Forking is unattractive as one cannot continue with the old project name, website and source code repository. A take-over attempt can easily get messy and fail. Some guidance how to best approach such situations would be useful.

Most helpful comment

@ramadankini: Please elaborate. Are you requesting a change, do you suggest that I should request a change, what change...?

All 9 comments

See #289 for some related prior discussion.

Request Change

@ramadankini: Please elaborate. Are you requesting a change, do you suggest that I should request a change, what change...?

Nothing.

..Ignore that typos

unable the device by qualxom

Good

Something support

Thanks for the issue! We're not currently creating new guides at this time. My personal advice in those situations would be forking the project and, if the fork gets enough steam, considering renaming the project.

Was this page helpful?
0 / 5 - 0 ratings