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

Fix and update tools.md #2116

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Fix and update tools.md #2116

wants to merge 1 commit into from

Conversation

Dmole
Copy link

@Dmole Dmole commented Mar 16, 2025

No description provided.

@Dmole
Copy link
Author

Dmole commented Mar 16, 2025

@microsoft-github-policy-service agree

Copy link
Member

@dbaeumer dbaeumer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like to have the once separate that are basically not maintained anymore but I am not a fan of separating Proprietary. We don't do that anywhere else. What is the reason behind it?

@Dmole
Copy link
Author

Dmole commented Mar 17, 2025

What is the reason behind [separating proprietary]?

This is GitHub where we share code, there is no code shared from proprietary software.
Reasons for wanting code include;

  • knowing if the software is abandoned by reviewing last commit date and open issues.
  • comparing implementation details of an ambiguous or limiting API.
  • figuring out how to solve a niche issue.
  • fix a bug.
  • find a project to contribute a pet feature to.
  • security research.
  • etc

@dbaeumer
Copy link
Member

I would prefer a not available indication in the repository column than a separate section.

@Dmole
Copy link
Author

Dmole commented Mar 19, 2025

Now without a

separate section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants