search

dwyl / contributing

:clipboard: Guidelines & Workflow for people contributing to our project(s) on GitHub. Please :star: to confirm you've read & understood! :white_check_mark:
86 stars 9 forks source link

Forking repositories into dwyl - why it's not a great idea without very good reason #30

Closed iteles closed 7 years ago

iteles commented 7 years ago

There is no way to add issues to forked repositories, which means they render our contributing guidelines pretty much useless.

screen shot 2016-10-19 at 00 57 03

We need to add a guideline to this repo on when forking a repo into dwyl is acceptable (I foresee very few situations where this would be the optimal solution) and what the process for that conversation is (open an issue on the dwyl repo that requires a fork of another repo or if there is no dwyl repo, do so on start-here).

nelsonic commented 7 years ago

Really the only reason to Fork something into dwyl is where we are going to improve on the project and send a patch/PR back up-stream. this does not appear to be the case here...

iteles commented 7 years ago

Agreed. I've emailed the person in question. If it sits for a fortnight with no changes I will delete the fork and it can be re-forked as necessary.

nelsonic commented 7 years ago

Is it hurting us to have the fork...? (I agree that it's clutter...)

iteles commented 7 years ago

It's clutter. We have too many repos for people to navigate easily so the second they hit one that is 'useless', it affects their interest in the others

nelsonic commented 7 years ago

Agreed. Don't know if this issue belongs in "contributing" tho...

iteles commented 7 years ago

I would argue that people who fork repos into dwyl rather than into their person GitHub accounts would do it because they feel they are contributing to dwyl in some way (otherwise they would fork to their own accounts).

nelsonic commented 7 years ago

Sure, maybe. :+1: