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

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

Closed
davorpa opened this issue Sep 8, 2021 · 10 comments
Closed

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

davorpa opened this issue Sep 8, 2021 · 10 comments
Assignees
Labels
good first issue A good starting point for newcomers help wanted Needs help solving a blocked / stucked item PR requested Issues that can be addressed with a new PR stale: closed Requests closed due to don't have recent interaction (Out-of-Date) stale Requests that have not had recent interaction (Out-of-Date)

Comments

@davorpa
Copy link
Member

davorpa commented Sep 8, 2021

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 🚀:

But there are some doubts how to change it 😟

  1. Under which section? The most will be Language agnostic/by topic (pending to abord Rename "Language Agnostic"? #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 😉 🤗

@eshellman
Copy link
Collaborator

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

@davorpa
Copy link
Member Author

davorpa commented Sep 20, 2021

It's already applied to courses-es

### Índice
* [Android](#android)
* [Arduino](#arduino)
* [Bases de Datos](#bases-de-datos)
* [Big Data](#big-data)
* [Ciencias de la Computación](#ciencias-de-la-computaci&#x00F3;n)
* [Control de Versiones](#control-de-versiones)
* [Flujos de trabajo](#flujos-de-trabajo)
* [Frameworks](#frameworks)

@davorpa davorpa added the conflicts Conflict(s) need to be resolved label Sep 29, 2021
@davorpa

This comment was marked as outdated.

@davorpa davorpa added PR requested Issues that can be addressed with a new PR and removed conflicts Conflict(s) need to be resolved labels Sep 29, 2021
@davorpa davorpa self-assigned this Oct 6, 2021
@davorpa davorpa changed the title Proposal: Merge Version Control Systems into same section proposal(lists): Merge Version Control Systems into same section Oct 6, 2021
@davorpa davorpa mentioned this issue Jan 13, 2022
5 tasks
@davorpa davorpa added good first issue A good starting point for newcomers help wanted Needs help solving a blocked / stucked item labels Feb 8, 2022
@mihir1739
Copy link

mihir1739 commented Jul 15, 2022

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

davorpa added a commit to davorpa/free-programming-books that referenced this issue Jul 16, 2022
handles proposal(lists): Merge Version Control Systems into same section EbookFoundation#5526
davorpa added a commit to davorpa/free-programming-books that referenced this issue Jul 16, 2022
handles proposal(lists): Merge Version Control Systems into same section EbookFoundation#5526
davorpa added a commit to davorpa/free-programming-books that referenced this issue Jul 16, 2022
handles proposal(lists): Merge Version Control Systems into same section EbookFoundation#5526
davorpa added a commit to davorpa/free-programming-books that referenced this issue Jul 16, 2022
handles proposal(lists): Merge Version Control Systems into same section EbookFoundation#5526
davorpa added a commit to davorpa/free-programming-books that referenced this issue Jul 16, 2022
handles proposal(lists): Merge Version Control Systems into same section EbookFoundation#5526
eshellman pushed a commit that referenced this issue Jul 18, 2022
* feat: add `vcs` section

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

* chore: move GIT resources from books to subjects

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

* chore: move Mercurial resources. books 2 subjects

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

* lint: alphabetize Mercurial resources

* chore: move Subversion resources. books 2 subjects

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

* lint: alphabetize Subversion resources

* add resource authoring

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

* format: Add archived notes to http://gitref.org/

handles #6301

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

* Update http://svnbook.red-bean.com resource

- To `https`
- Use localized `index.html`
- Add book authoring

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

* Add resource authoring

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

* format: Add archived notes to http://rypress.com/tutorials/git/index

handles #6301

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>
@davorpa
Copy link
Member Author

davorpa commented Sep 10, 2022

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

Locales where already applied: Spanish and english

@eshellman
Copy link
Collaborator

"abord"?

@davorpa
Copy link
Member Author

davorpa commented Sep 12, 2022

abord

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

@eshellman
Copy link
Collaborator

go for it

@github-actions
Copy link

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

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 ❤️

@github-actions github-actions bot added the stale Requests that have not had recent interaction (Out-of-Date) label Nov 13, 2022
@github-actions
Copy link

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 ❤️

@github-actions github-actions bot added the stale: closed Requests closed due to don't have recent interaction (Out-of-Date) label Dec 14, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue A good starting point for newcomers help wanted Needs help solving a blocked / stucked item PR requested Issues that can be addressed with a new PR stale: closed Requests closed due to don't have recent interaction (Out-of-Date) stale Requests that have not had recent interaction (Out-of-Date)
Projects
None yet
Development

No branches or pull requests

3 participants