Free-programming-books: It would be helpful to specify access requirements

Created on 3 Dec 2014  ·  17Comments  ·  Source: EbookFoundation/free-programming-books

I have being following this repo for a few days and checked out some of the books referenced. Some links point to files stored behind subscription barriers (i.e. you must join a list a cop junk mail to read the book). These types of books are rarely 'free' per se. Maybe submitters should flag if a link points to a subscription site or has particular license constraints.

All 17 comments

yea i know what you mean, i try to avoid merging these in. @vhf can weigh in about these too.

:+1: for this issue! I think it is important to note when accounts or other requirements are necessary to obtain a book/course. It isn't truly free if you need to provide something on your end. I think we can assume account logins for sites like Coursera, because how else are you to track your progress?

@SimonChristopherCropper I would suggest opening a PR noting which links require logins, etc. We should amend (add info) to the list, at the very least, before removing helpful references.

I agree with @onebree !

@onebree @vhf Is it preferable to separate such links into their own category, or just add a note?

As my focus on documentation is with readability, my concern with notes (granting there might be numerous problem links present) is we'll bloat the existing document vertically, while adding no real value. That is, people will inherently gravitate towards easy access and truly "free" content over paywalls or the like, so it seems more apt to separate these into their own Subscription-based category within the documents.

As I said before, we should change as little of the current links as possible, until we research further. I think an "account required" category would be nice -- the word "subscription" makes me think that money is involved (and not free).

I could create a PR in a couple of days to add this section to all the English docs...

@onebree I lean towards your word choice here. "Account required" or "Signup required" is definitely less suggestive than "Subscription."

Agreed. If you have some free time, I'd gladly accept a PR annotating such links with *(account required)*

@vhf I am unable to submit a PR at this time. Hopefully another person can!

No problem @onebree! You helped this repo a lot already, and it is/was much appreciated. You certainly noticed I closed a bunch of issues today. This one is still standing though, and I won't close it until it's fixed, by any contributor or by me. :)

1746 made me realise I have not been clear about what I would prefer regarding this issue.

I suggest annotating links with *(account required)* when it applies, instead of creating a new category "Account Required" and duplicating sub-categories.

No @vhf, my bad!!! I was in a hurry and misunderstood the requirements! Sorry

@vhf I think this issue should remain open until we put somewhere (maybe these guidelines.

I am on the fence as to whether we should add an "account required" section, versus adding a note on the lines. I mean, I personally like a separate section, because I would rather avoid sites requiring a sign-up when I am looking for "free"

Slightly off-topic, the lists seem to be growing horizontally (link, filetype, author, etc). What if everything was in a table? Then you could add the column "Account Required", and add an X if it's true.

Oh I thought it was already in I'll add it.

Thank you. What are your thoughts on a table format? The raw markdown may not look as pretty, and added new columns will be a pain... I am not sure how this could be done elegantly, but just an idea.

Would something like be against this then? It requires signing up for an account before access to the book is given.

@johnaoss it's not really against this. I think although syncfusion doesn't require an actual _account_, we should still annotate all syncfusion links with _account required_. I'm open to suggestions on this matter.

@onebree I suspect that's something for another issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Tlalanne picture Tlalanne  ·  4Comments

kaleemullah360 picture kaleemullah360  ·  8Comments

kadhirash picture kadhirash  ·  4Comments

eshellman picture eshellman  ·  18Comments

VicoSilalahi picture VicoSilalahi  ·  4Comments