Bountysource VS PropertyChanged

I used to use BountySource for this, but apparently they have not been honoring withdrawal requests and maybe are insolvent now. Gitcoin used to offer crypto bounties on bugfixes, but apparently they no longer do that and now only do "hackathons". I'm aware of many "bounty" sites, but they all are focused on finding security flaws not fixing specific issues.

It sounds like bountysource, but bountysource seems to have stopped paying bounties. Found these two links on the Wikipedia Article for Bountysource:

[CRITICAL] Bountysource Escrow, Complain @ dfpi.ca.gov, 18.05.2023 - https://github.com/bountysource/core/issues/1539

What is wrong with your support and cash out process?, 20.06.2021 -

Bountysource

Also obvious, and also only one way - sites where repository maintainers ask for feature implementation with a reward. There is no obvious winner here, both sites are good. - BountySource — payments in USD, seemingly more requests - Tip4Commit — payments in BTC, smaller amount of requests but payments are quite bigger.

There were a few companies that tried doing that, if I recall correctly https://www.bountysource.com/ was one of them (seems to still be active). I've been following the area and also tried to run a business in the area. My experience is that while there's some demand, it's either really small, or extremely difficult to grow.

I've pledged for fixes before. I think this is the service I used. https://www.bountysource.com/

There is a website called BountySource that I think is meant to do what you describe. I've never actually used it though.

Add [AddINotifyPropertyChangedInterface] attribute to the class for change notification.

All the weaving libraries (also called weavers or addin) using Fody need to have the .Fody suffix, so it's quite easy to recognize them. As an example, if you ever had to implement INotifyPropertyChanged manually in a class with dozens of properties you would probably welcome weaving (and Fody) with open arms. By creating all the plumbing code directly in IL, libraries like PropertyChanged.Fody allows to inject the necessary notification code without the need to modify anything in the original source code.

You can rewrite auto-props (as used this this lib https://github.com/Fody/PropertyChanged) with Fody.

If you're not familiar with Fody and specifically the PropertyChanged weaver, I highly recommend checking it out: https://github.com/Fody/PropertyChanged

Now the ugly part - you need to implement INotifyPropertyChanged. It can be done either manually, or automated with this or this

https://github.com/Fody/PropertyChanged and Android background makes WPF pretty easy. At least the surface level stuff.

If you really don't want to deal with it ever again, just add this Fody - PropertyChanged NuGet package. Any class that inherits from INotifyPropertyChanged will be updated at compile time to inject in the boilerplate code for handling the property change and you never even need to think about it again. All you need to do is just add plain old properties. The only downside that some people see is that it is not immediately transparent as the change notification code is injected in during compile and is not in source code.

And GitHub is the place where employees of billion dollar companies pester unpaid maintainers because they won’t support a 12 year old version of .NET

https://github.com/Fody/PropertyChanged/issues/270#issuecomm...

If you need more info, check the docs https://github.com/Fody/PropertyChanged