Pelagicore / dlt

Temporary fork of http://git.projects.genivi.org/dlt-daemon.git
Other
7 stars 7 forks source link

Forks are usually a bad idea #1

Closed jeremiah closed 9 years ago

jeremiah commented 9 years ago

I don't think we should fork DLT. When one forks a project, all the evidence and studies show that you reduce the overall contribution which is never what one wants. A fork also creates a lot more work for us. I can understand if we have some patches that may be specific to us, or that upstream might not care about, but forking a project is not the answer to this particular problem. Instead we should keep our patches in a layer we use when building an image or in a quilt repo somewhere.

e8johan commented 9 years ago

If we use a pull-request workflow, this is ok, but I agree, we should not fork.

jacky405 commented 9 years ago

The intention is definitely to get those patches upstreamed ASAP. The corresponding bug entries in GENIVI's bugzilla are already submitted. They contain links to our fork. Hopefully, that fork repository can be deleted soon.

On 16 December 2014 at 13:49, Jeremiah C. Foster notifications@github.com wrote:

I don't think we should fork DLT. When one forks a project, all the evidence and studies show that you reduce the overall contribution which is never what one wants. A fork also creates a lot more work for us. I can understand if we have some patches that may be specific to us, or that upstream might not care about, but forking a project is not the answer to this particular problem. Instead we should keep our patches in a layer we use when building an image or in a quilt repo somewhere.

— Reply to this email directly or view it on GitHub https://github.com/Pelagicore/dlt/issues/1.

e8johan commented 9 years ago

Great to hear!

jeremiah commented 9 years ago

Yay!