Relative Content

Tag Archive for etiquette

GitHub etiquette for duplicating a repo to change functionality

I’ve found a GitHub project I’d like to add some features to. After contacting the maintainer, the changes aren’t in line with the direction he’s going but he’s interested to see what I do with it. What is the GitHub etiquette for using one repo as a base for another project that almost certainly won’t ever be merged back into the original?

Zero Day Exploit Ethics/Etiquette [duplicate]

This question already has answers here: You’re hired to fix a small bug for a security-intensive site. Looking at the code, it’s filled with security holes. What do you do? [closed] (7 answers) Closed 10 years ago. What are my responsibilities, as a developer, if I stumble upon a zero day exploit in a widely […]

Fork a subset of a repo – licensing and etiquette

I’m a contributor to a large open source project. I have made heavy changes to a submodule of that project to support more functionality, but at this point further improvements will be outside the scope of the original project. As such, I have pulled only the relevant files to the submodule into their own repo, and am proceeding with a major rewrite to allow for these new features. The file structure is such that this submodule can live on it’s own, with the original as a dependency.

Fork a subset of a repo – licensing and etiquette

I’m a contributor to a large open source project. I have made heavy changes to a submodule of that project to support more functionality, but at this point further improvements will be outside the scope of the original project. As such, I have pulled only the relevant files to the submodule into their own repo, and am proceeding with a major rewrite to allow for these new features. The file structure is such that this submodule can live on it’s own, with the original as a dependency.