I Fixed a 3-year-old bug in Windows Calculator and Microsoft Doesn’t care

Re:I Fixed a 3-year-old bug in Windows Calculator and Micros... by sshine on Friday August 11, 2023 @01:54PM (#37091661)

Before I put any effort into an Open Source contribution, I always check the water first:

  - Does the project have stale PRs?
  - Do they react to small fixes? (typos, broken links)

[ Parent | on HN ]

Re:I Fixed a 3-year-old bug in Windows Calculator and Micros... by veave on Friday August 11, 2023 @02:47PM (#37092333)

Do they have thousands of open issues? (I'm sitting myself on a VLC bug which I can't be arsed to report)

[ Parent | on HN ]

Re:I Fixed a 3-year-old bug in Windows Calculator and Micros... by Dhikshith12 on Friday August 11, 2023 @03:11PM (#37092641)

I'm pretty sure that's not a typo or a small fix, many people use scientific mode and type negative exponents and it gives this "2.6exp-2 == 0.6", it concerned me, so i tried to fix it, and opened a pr.

[ Parent | on HN ]

Re:I Fixed a 3-year-old bug in Windows Calculator and Micros... by sshine on Monday August 14, 2023 @10:24AM (#37121380)

I agree with you.

The point I'm making is: Before I put any real effort into a fix, I test if they are receptible to something that was easy for me to make, and should be easy for them to validate, e.g. a typo fix.

Because what you often find out is that people are not interested in being active maintainers.

[ Parent | on HN ]