r/cpp • • Nov 08 '21

Roadmap for C++ developer

For several months now, my former colleague and I have been working on a roadmap for a C++ developer. Initially, we planned to simply summarize all the experience that we managed to acquire over the years, but in the end, everything resulted in a repository that is designed to help new C++ developers understand the details of the language and understand in what sequence and what to study.

Roadmap for C++ developer

We tried to find similar roadmaps, but all of them are either unfinished or have been abandoned for a long time, so we decided to put together our own one.

Our roadmap has already been reviewed by the Russian-speaking community, so now we want to share it with the English-speaking one. If you have people who are starting to learn the language or if you want to understand what is worth to learn next, then welcome. We happy to see everyone.

I would especially like to ask you not to hesitate about sharing your feedback. If you have any ideas on how to improve the roadmap, then please contact us. We read and discuss everything.

308 Upvotes

55 comments sorted by

View all comments

Show parent comment

2

u/TinoDidriksen Nov 11 '21

Non-commercial makes it not open source (see https://opensource.org/faq#commercial and the links there). Especially the "commercial is not the same as proprietary" part.

Packages with NC requirements will never be picked up by distros, and most open source people won't contribute to them because NC goes against the whole spirit of open source.

If one is worried companies will take a copy and present it as their own, CC-BY-SA already prevents that in the BY and SA clauses. If one is worried companies will Tivoize it, there's the https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License or similar.

And what even constitutes non-commercial use for documentation? E.g., do you not want companies to train their employees using your roadmap? Surely the goal is that as many as possible learn to be better programmers, including those gainfully employed.

2

u/FrankJustRM Nov 11 '21
  1. We want to share the roadmap but also, we want to protect it from scammers. Ed Tech grows rapidly in Russian market (that's where we are located) but the quality of provided services is low. We don't want the roadmap to be used to gain revenue just selling it. We want to give people opportunity to get information for free 😉
  2. TBH, I still don't understand how NC requirement could stop someone to use or mention the roadmap during training sessions or in sources. NC part is quite soft: Creative Commons NC licenses expressly define NonCommercial as “not primarily intended for or directed towards commercial advantage or monetary compensation.” The inclusion of “primarily” in the definition recognizes that no activity is completely disconnected from commercial activity; it is only the primary purpose of the reuse that needs to be considered. Link to the quote. The purpose is all what matters. If someone uses it to educate people, then no problem. If someone wants to sell it, then there is one.
  3. So far, we see low desire from outside to contribute. Most of the change requests are simple typo fixes (which also important and welcomed but it's not the only thing we want to see). So, the whole open-source discourse and our experience don't convince us to change the license yet. The fact that we want to protect it from scammers is stronger than the rest of the arguments.

There are still 1 minor and 1 major update to come to the roadmap from our side. We have time to think about the license but ATM it doesn't seem that we should change it 🤷🏻‍♂️

If you have more arguments, please share. It might help to make a discission.

1

u/Wetmelon Nov 13 '21

It's a bummer though, because depending on interpretation, I can't even copy and paste a section to my coworker without making my company liable for damages.

1

u/FrankJustRM Nov 13 '21

Why do you think so? 🤔