Skip to content
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

DocPad is NOT free software! #6

Open
species opened this issue May 4, 2015 · 4 comments
Open

DocPad is NOT free software! #6

species opened this issue May 4, 2015 · 4 comments
Labels

Comments

@species
Copy link

species commented May 4, 2015

after npm install -g [email protected]; docpad run I get the following statement:

Before we continue, have you read and agree to DocPad's Terms of Service (http://bevry.me/tos) and Privacy Policy (http://bevry.me/privacy)? [Y/n]

And http://bevry.me/tos states:

By using any services, websites, projects or products ("Service") of Bevry Pty Ltd ("Bevry"), you are agreeing to be bound by the following terms and conditions ("Terms of Service")
...
Bevry reserves the right to update and change the Terms of Service from time to time without notice.

Hey, this clearly violates the Clause 0 of the Free Software definition:

The freedom to run the program as you wish, for any purpose

They can state MIT license in the docpad repo as often as they wish, but if they're requiring to sign a contract that can change without notice (and selling my soul to an unknown being) before using their software I'm not able to use it.

@pmackay
Copy link

pmackay commented Dec 17, 2015

How much of an issue is this for the project?

Also what influenced the choice of using DocPad?

@almereyda
Copy link
Member

This is not too much of an issue, as one can easily change the source code
to not ask this question before running it.

Second the choice was for its good ecosystem of plugins, integration of the
Prose editor (when fully entrenched with commit hooks) and the probable use
of the Node.js ecosystem.
But I'd also be happy to be using something customly tailored as in
https://github.com/valueflows/valueflo.ws or a system, as we will want to
have a classic backend for editors, like http://keystonejs.com/.

On 17 December 2015 at 16:00, Paul Mackay [email protected] wrote:

How much of an issue is this for the project?

Also what influenced the choice of using DocPad?


Reply to this email directly or view it on GitHub
#6 (comment)
.

@josefkreitmayer
Copy link
Member

I am interested, what is actually the role of DocPad in the TransforMap ecosystem?

Sorry for the dull question. I never heard the name before in any conversation.

@almereyda
Copy link
Member

Delivering a notion about what can be done to reMIT docpad.
Assuming it has been installed via npm install the binary will be found at

./node_modules/docpad/bin/docpad

The file in charge for displaying the ToS agreement lives at

./node_modules/docpad/out/lib/interfaces/console.js

where the following part can be removed:

https://github.com/docpad/docpad/blob/5a621b3b2a11d4823a5cc591be77b0aebb6e67c1/src/lib/interfaces/console.coffee#L466-L485

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants