proposal(lists): Merge Version Control Systems into same section

[davorpa]

I'm convinced that it would be a nice idea join all Version Control Systems into the same category. I mean: Git, SVN, Mercurial, CVS...

And if there are some resource treating Github, Gitlab, Bitbucket, Gitea, Gitpod... put it in a subsection something like As a Service/Platform SaaS/PaaS.

Also with views to cover some utility/GUI client resources about: Gitkraken, Github Desktop, SourceTree and so on.

This will give much more context than a merely listing grouped by tool/programming language.

Therefore, maybe it aims to improve :rocket::

• #5092
• #5249

But there are some doubts how to change it :worried:

1. Under which section? The most will be Language agnostic/by topic (pending to abord #5249 ??? ), or as TOC first level...
2. Is needed preserve each heading: Git, SVN... ? This next heading snippet

   ### <a name="git"></a><a name="svn"></a>... Version Control Systems
   

   could be used in some manner for backwards compatibility, but markdown TOC that GitHub provides automatically will be lost (is built using each ##)

It's already applied in some listings.

Let me know your opinion/feedback :wink: :hugs:

[eshellman]

I guess it's time to roll out a proposal for a programming-lang/subject split

[davorpa]

It's already applied to courses-es

https://github.com/EbookFoundation/free-programming-books/blob/076fca27c3baceeb7187988c0b0def0da04e70d4/courses/free-courses-es.md#L1-L10

[davorpa]

Locked at this moment by

• #5563
• #5581

[mihir1739]

How can I contribute to this issue..?Is it open..?

[davorpa]

Hey @eshellman. Can I abord this before Hacktoberfest starts?

Locales where already applied: Spanish and english

[eshellman]

"abord"?

[davorpa]

abord

Sorry spanglish!! "tackle", "board in", "start with"

[eshellman]

go for it

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity during last 60 days :sleeping:

It will be closed in 30 days if no further activity occurs. To unstale this issue, remove stale label or add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest.

Thank you for your patience :heart:

[github-actions[bot]]

This issue has been automatically closed because it has been inactive during the last 30 days since being marked as stale.

As author or maintainer, it can always be reopened if you see that carry on been useful.

Anyway, thank you for your interest in contribute :heart: