search

dtoebe / new-che-electron

Complete rewrite of https://github.com/TylerJewell/che-electron
Eclipse Public License 1.0
0 stars 0 forks source link

Licensing and Logo #1

Open dtoebe opened 8 years ago

dtoebe commented 8 years ago

Add proper licensing to whole project to get the appropriate logo and branding.

TylerJewell commented 8 years ago

The general process to get a project added into the repository itself will be: 1: You'll have to execute an Eclipse CLA if you haven't already.

2: Eclipse has some strict policies around IP policies. They check provenance on every library and line of code. So there are certain types of open source libraries that are permitted and certain kinds that are not. If the code is to be part of the /eclipse/che repository, then all of the libraries will have to be submitted for CQs and then we can only merge a pull request after they give the go ahead for everything.

3: There would then need to be some sort of maintenance policy so that the maintainers would have the skills and ability to maintain the improvements over time if you are not able to.

4: If for some reason there are components that are not acceptable to the foundation, then we have other avenues for publication. We can host the binaries on our Web servers and push users to make use of it with caveats and conditions that they understand the binaries are not IP reviewed.

5: The license will have to be EPL if you want it to go into the Eclipse Che project, though you keep the copyright. Each author of code has the copyright to what they write - it's how open source becomes ownership of commons. Even though it's licensed and distributed with Che - the copyright is yours.

dtoebe commented 8 years ago

Ok I will hop on the CLA for myself. A couple questions. First incorporating this project into the Che fold, does that mean any contributor has to sign the Eclipse CLA before I am able to commit their changes? And with that said is this project a bit premature to commit the Eclipse licensing? And If the CLA is required for every committer, I should put a note in the readme explaining of my plans to go under the Eclipse License, and become part of the Che fold?

I know for a fact that i want to make this an Eclipse project, and be included as a Che project.

TylerJewell commented 8 years ago

Well, the license is a different concept than your ability to have the code committed into an Eclipse project. The EPL license is something that anyone can use - so you can license the source code in this project with anything that you want at any time. So there is nothing premature about that.

Now, the process of getting this code into an Eclipse certified repo is quite laborious - and yes, in that case, for the code to be merged into the Eclipse core code base, every file and every commit will need to be traceable back to someone who has signed a CLA. So if you are thinking about issuing a big PR into the che repository, you'll want to think about those rules that we have to follow to get code accepted, and anticipate it before you accept code from others.

dtoebe commented 8 years ago

I signed the CLA, and verified it. I added the EPL to License file, and to the package.json. I will update the scripts headers, and create the wiki, which will outline a maintenance policy, basically I will model it similar to the eclipse/che repo.

That means anything promotional will reference promoting the Che project itself. For the short time being, I will leave out any chat support.

As the full scope of the project takes form I will add Roadmaps, milestones and so so forth.

I will spend much of my free time this week I will familiar myself with eclipse project requirements and structure.

TylerJewell commented 8 years ago

Running an open source project always seem to be more administration and very little development!

dtoebe commented 8 years ago

Ha ha ya. But code has so little to do with the software business... Just Kidding.... Well sort of.