Hacker News Reader

Comment by vortico | Hacker News Reader

I hope Microsoft knows this, but Open Source doesn't imply putting your source on GitHub (and vise-versa). If Microsoft dev teams served source tarballs along with their releases, we'd be just as happy. But perhaps they will actually use the GitHub issue trackers and other neat features, as they are pretty useful.

View on HN

Uh, publishing your source under a usable license is sorta really the definition of open source. Whether or not you like their dev style or other things is separate and trying to make new definitions. You shouldn't just throw caps on a common description then claim no one is that common thing because you've redefined it.

Uh, they have moved their entire development workflow to GitHub pull requests. Fully transparent and out in the open.

Work has commenced on getting CoreCLR (the official.NET run-time) ported and running on BSD and the following PR's were merged yesterday which add initial support for NetBSD and OpenBSD:

https://github.com/dotnet/coreclr/pull/453 https://github.com/dotnet/coreclr/pull/470

The "port team" is organzing work via the following issue:

https://github.com/dotnet/coreclr/issues/455#issuecomment-82...

We are looking for more people to help out, if this is of interest then please goto above and say Hello ;-)

They have been accepting community contributions on dotnet/coreclr, among other projects:

https://github.com/dotnet/coreclr/pulls

This is just one of many steps. For instance if you take a look at the following merge someone actually comments regarding what you're talking about: https://github.com/dotnet/coreclr/pull/485

Basically many teams are still on TFS versus GIT and will take some time to move over. But once they're moved over GitHub and their internal stuff will be treated more like separate branches and there will be good, useful history instead of simple bombs from TFS.

Reply on news.ycombinator.com