Publish on Non-GNU ELPA

[hab25]

Fetching from source works for me, but I hold the opinion that this project being available in an ELPA gives me and others the following advantages:

• Users are more accustomed and typically face less immediate friction when fetching from an ELPA. This usually results in more users. More users usually means more bug reports and more feature requests. This tends to result in better software.

• If this repository becomes compromised with malware, there is an additional way of taking access to the repository down. I.e., besides reporting to GitHub, one can report to the ELPA's maintainers. Either one of these organizations taking action will likely result in the compromised version of the project no longer being available on the ELPA. A user that is fetching from ELPA gets to benefit from the faster of the two, instead of only the repository hosting provider.

Why both:

• The project will benefit from the potential quality increase that comes from going through an additional ELPA maintainer team's review(s).

• More access typically means more users; this typically results in better software, as mentioned before.

[szermatt]

I've got a pull request pending to add the package to melpa: melpa/melpa#9216

[szermatt]

This is now available from melpa:

• https://melpa.org/#/visual-replace
• https://stable.melpa.org/#/visual-replace

[szermatt]

I'm keeping this issue open to publish on Non-GNU ELPA. I changed the title to reflect that.