Skip to content

added install instruction with apt #6206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

added install instruction with apt #6206

wants to merge 1 commit into from

Conversation

mef
Copy link

@mef mef commented May 16, 2014

No description provided.

@clintongormley clintongormley self-assigned this May 16, 2014
@clintongormley
Copy link
Contributor

Hi @mef

Thanks for the fix. Please could I ask you to sign the CLA so that we can get your commit merged in? http://www.elasticsearch.org/contributor-agreement

thanks

@mef
Copy link
Author

mef commented May 16, 2014

Hi @clintongormley,

I have some issues with your CLA. Why was it created on the first place, and has there ever been a need for such process? Or was it created just by mimetism of some other open source projects without an actual reflexion?

CLAs are generally common and accepted in most Open Source software projects

No, they are not. There is an ongoing controversy about it, cf. Contributor Agreements Considered Harmful

to ensure we have the agreement of our contributors to use their work

You have the agreement, it's called a Github pull request between your open source project and one of its github forks. You should probably talk to legal people specialized in the topic.

The CLA help us achieve that goal

Doesn't the CLA reduce the number of contributions, by adding un-necessary administrative tasks?
Please take into account that in addition of signing the CLA, you're asking us to:

  1. Provide our personal information to Adobe Echosign for the electronic signature. Adobe, personal data, leaks...
  2. Agree to a customer disclosure agreement
  3. Agree to Adove Echosign's terms and services.

The next step is for you to select the appropriate agreement below, (...)

How about we do the following instead:

  • option 1: "The next step is for you (Elasticsearch) to get informed and debate internally about the necessity of having CLAs. You realize it's not necessary and get more lean, great !"'. I'm sure you can push people and have this done in 2 weeks.
  • option 2: "The next step is for you (Elasticsearch) to accept and merge my pull request, by considering that this message is an explicit approval of your CLAs terms (cf. above: "You have the agreement").
  • option 3: "The next step is for you (Elasticsearch) to discard my pull request, re-do the changes I have made on your own repository, commit, and end of story"

That's about it. I hope one of the solutions offered above will let us move on. I hope option 1 will be chosen. Sorry for the rant. I don't mean to troll, but to be constructive.

@clintongormley
Copy link
Contributor

Sorry that you feel that way. We as a company have debated this before and as an employee I need to stick to our established policy. I'll be treating this as a bug report rather than as a PR.

clintongormley added a commit that referenced this pull request May 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants