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

should it count paid books in the list or only free books? #3956

Closed
avelino opened this issue Dec 21, 2021 · 6 comments · Fixed by #4004
Closed

should it count paid books in the list or only free books? #3956

avelino opened this issue Dec 21, 2021 · 6 comments · Fixed by #4004

Comments

@avelino
Copy link
Owner

avelino commented Dec 21, 2021

A discussion arose within a pull request #3952 where I (Avelino) was not accepting paid books - without having the knowledge that there were already paid books on the list - sorry.

  • comment on your opinion about having paid books
@avelino
Copy link
Owner Author

avelino commented Dec 21, 2021

I start by apologizing for not knowing that we had paid books on awesome-go, for me there were only free books

I think it is important to have a subcategory within "books" for non-free books (ebooks can be a subcategory of books) - I am about to restructure it

I am thinking of the following structure:

## books

> here contains paid books

- abc...
- abc...

### free books

- abc...
- abc...

what is your opinion? @bitfield can you help us with the book category?

@bitfield
Copy link
Contributor

Sounds good to me! How about 'free books' versus 'books for purchase'?

@avelino
Copy link
Owner Author

avelino commented Dec 22, 2021

Sounds good to me! How about 'free books' versus 'books for purchase'?

I like the proposal of the names
Thinking about structure (groups and subgroups) I think as follows:

  • books - Does not contain even one item, serving to group the subcategories together
    • free books
    • Books for purchase

@bitfield
Copy link
Contributor

Pending a final decision on this, would it be all right for me to add my "book for purchase", per #3908? Writing Go books is literally my livelihood, and a listing here would make a big difference to me, as a one-person writing and publishing operation.

It's not just about me, either: what I make from selling ebooks covers the bills, and essentially funds me to provide free Go learning resources such as tutorials and YouTube videos.

If that's not allowed, I quite understand. But then it's hard to square that with the current inclusion of several paid-for books published by Manning, for example (see #3952). They are a large commercial publishing firm who must make many hundreds of dollars a year from people purchasing through the links here. They could probably scrape by without that revenue: I can't.

@phanirithvij
Copy link
Collaborator

phanirithvij commented Jan 22, 2022

@bitfield I am in favor of this, I believe Avelino is too, from his previous comment. I think you may go ahead and send a PR that restructures these books (if you don't mind) and following that, another PR that adds your book to the books for purchase section.

bitfield added a commit to bitfield/awesome-go that referenced this issue Jan 24, 2022
@bitfield
Copy link
Contributor

My pleasure, @phanirithvij, thank you. Please see #4004 for the restructuring PR.

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

Successfully merging a pull request may close this issue.

3 participants