opensource-management-portal
repo-templates
| opensource-management-portal | repo-templates | |
|---|---|---|
| 2 | 1 | |
| 478 | 54 | |
| 0.4% | - | |
| 8.8 | 5.7 | |
| 7 days ago | 9 days ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opensource-management-portal
-
Tell HN: Microsoft forks MIT licensed repo, and changes the copyright to them
FYI: when linking to a line of code, simply press Y on your keyboard to have Github switch from the _branchname/path/to/file.xyz_ URL to the _sha1/path/to/file.xyz_ URL. The former can result in your URL pointing to unrelated code if lines are added or removed in future commits on the referenced branch.
https://github.com/microsoft/opensource-management-portal/bl...
repo-templates
-
Tell HN: Microsoft forks MIT licensed repo, and changes the copyright to them
I lead the Microsoft Open Source Programs Office team. I'm sorry this happened.
We have merged a pull request that restored the correct LICENSE file and copyright, and are in touch with the upstream author Leśny Rumcajs who emailed us this morning. We'll look to revert the entire commit that our bot made, too, since it updated the README with a boilerplate getting started guide.
The bug was caused by a bot that was designed to commit template files in new repositories. It's code that I wrote to try to prevent other problems we have had with releasing projects in the past. It's not supposed to run on forks.
I'm going to make sure that we sit down and audit all of our forked repositories and revert similar changes to any other projects.
We have a lot of process around forking, and have had to put controls in place to make sure that people are aware of that guidance. Starting a few years ago, we even "lock" forks to enforce our process. We prefer that people fork projects into their individual GitHub accounts, instead of our organization, to encourage that they participate with the upstream project. In this situation, a team got approval to fork the repository, but hasn't yet gotten started.
To be as open as I can, I'd like to point out:
- The templates we apply on new repositories live at https://github.com/microsoft/repo-templates
What are some alternatives?
jiq - jid on jq - interactive JSON query tool using jq expressions
azuredatastudio - Azure Data Studio is a data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server. Browse the extension library for more database support options including MySQL, PostgreSQL, and MongoDB.
cups - OpenPrinting CUPS Sources
cups - OpenPrinting CUPS Sources
xnu
grpc_bench - Various gRPC benchmarks
rushstack - Monorepo for tools developed by the Rush Stack community
vscode-python - Python extension for Visual Studio Code
STL - MSVC's implementation of the C++ Standard Library.
huggingface-transformers - 🤗Transformers: State-of-the-art Natural Language Processing for Pytorch and TensorFlow 2.0.
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
ippsample - IPP sample implementations.