Clean-up and replace outdated content

[egpbos]

For our next release, we need to remove a bunch of content that we no longer will maintain as part of the Guide itself (they were mostly moved to other places). This is a partial do-over of #286 which became a bit unwieldy. From this issue we'll create the subissues so we can work on them in parallel. This is the list of issues:

Straightforward replacements

Materials that were moved to the Turing Way that we want to map (using links to the Turing Way or RSQkit or other reputable sources) in the Best Practices chapter (see #321 and #360).

• Clean-up and replace Checklists chapter #375
• Clean-up and replace Version control chapter #376
• Clean-up and replace Code quality chapter #377
• Clean-up and replace Code reviews chapter #378
• Clean-up and replace Licensing chapter #379
• Clean-up and replace Communication chapter #380
• Clean-up and replace Testing chapter #381
• Clean-up and replace Releases chapter #382
• Clean-up and replace Teamwork chapter #383
• Clean-up and replace Intellectual property chapter #384

A bit more work + replacements

• Documentation chapter #385
• Standards chapter #386

[egpbos]

Thanks to @PabRod for convincing me to reorganize this way 🚀

[egpbos]

All issues have been addressed in some way: either it has been closed, or there are pending PRs (#407, #408, #409). For a third group (#380 and #383) there are discussion points that may require a bit more time and that I think we will not resolve before the v1.0 release. Because the actual clean-up parts of those issues are done (the questions are only about replacing the removed chapters with new material) I think we can do this in a next release. What do you think @bouweandela @c-martinez?

[c-martinez]

Yes, let's go ahead!