The open source article has been "BP" by the training institution again, this time I can't bear it

Hello everyone, I'm Glacier~~

Here's the thing. Recently, I made some articles open source. I didn't expect to open source them for a few days, and they were directly used as courseware by a shameless training institution. I didn't know about this at the beginning, but a reader told me of.

Originally, I wanted to open source these articles, and I wanted to open source them to share useful knowledge and skills with everyone. I also hope that everyone can build and maintain them together. After all, my power is always limited.

I have open sourced some of the technical articles, workplace insights, and personal experiences that I have written, hoping to bring substantial help to everyone, and everyone can also participate in the maintenance.

Unexpectedly, there are always some shameless people who will directly use it for commercial use. This is not the first time.

At present, I have warned the training institution to withdraw the paid courseware for directly prostituting my articles within 2 days, and reserve the right to sue.

At the same time, I changed the open source agreement used by the open source warehouse. The original whole warehouse is licensed under the Apache 2.0 agreement, and the document part is licensed under the Creative Commons Attribution 4.0 international license agreement, and the code part is licensed under the Apache 2.0 agreement.

Article open source

Let's talk about why the article is open source.

Over time, I have written a lot of articles, and more and more documents are stored on the computer disk. If the computer disk breaks down one day, these documents may be lost.

If I want to store these documents in a unified place, I have tried Baidu network disk before, but the effect is really bad.

Put Github and Gitee as open source project maintenance, and can also manage the submitted version of the document. If something is not well written, just resubmit it after modification. Github and Gitee can keep the history of each submission, so that each time can be traced back 's submission.

Open source Github and Gitee, and let everyone build and maintain together. Any small partner can submit their own Pr. My knowledge and ability are limited. If I write something wrong, everyone can help me correct it. .

After this analysis, I started to work on the open source matters of the article. First, create a new repository on Github.

https://github.com/binghe001/BingheGuide

https://gitee.com/binghe001/BingheGuide

After a few days of sorting, I open sourced some of the articles I wrote before. After the open source, I found that the pictures on Github could not be loaded, and I began to spend time dealing with the problem that the pictures could not be loaded.

I also use GitHub's Pages function to publish the article as a static page for everyone to read, which is more convenient to read. The link address is as follows:

https://binghe001.github.io/

insert image description here

Follow-up planning

This warehouse will be updated and maintained for a long time in the follow-up, and articles on other topics will be open sourced slowly. I hope that more small partners can participate in the update and maintenance together.

Finally, let's take a look at the articles that have not been open-sourced yet. In the end, these articles will be open-sourced.

picture

picture

As I write this article, I'm too sleepy to open my eyes, and these shameless training institutions are really annoying. Finally, don't forget to give Glacier a Star on Github and Gitee .

Okay, let's stop here today, I'm Glacier, see you next time~~

write at the end

If you want to enter a big factory, want to get a promotion and a salary increase, or are confused about your current job, you can privately message me to communicate, I hope some of my experiences can help you~~

Recommended reading:

Okay, let's stop here today, friends, like, favorite, comment, and start walking with one click, I'm Glacier, see you in the next issue~~

Guess you like

Origin blog.csdn.net/l1028386804/article/details/124092917