[FR] Add GitHub sponsor button

[juliohm]

I think the JuliaPlots organization should be able to apply for a GitHub sponsor button. How can we sponsor the maintenance of Plots.jl? https://discourse.julialang.org/t/paying-a-freelancer-to-maintain-plots-jl/61162

[BeastyBlacksmith]

The things we lack to apply to become a NUMFocus member

• A transparent, publicly visible governance model
• A roadmap outlining high priority work areas
• A code of conduct as well as someone who is responsible for resolving CoC complaints
  One might argue about scientific orientation

[juliohm]

Isn't NumFocus sponsorship a different issue? GitHub sponsors is a feature of GitHub given to organizations so that any GitHub user can directly sponsor the project. I currently sponsor the Julia project for example, see the sponsor button at the top right of the repo: https://github.com/JuliaLang/julia

[juliohm]

https://github.com/sponsors

[daschw]

Speaking for me personally, sponsoring won't get me more time for Plots.
However, I think it's a good idea if it can motivate more contributors. Do you have more insights on how this sponsoring works? Can the sponsor decide what the money is used for, like linking it to the fix of a specific issue or to a specific contributor or does this all go to a JuliaPlots organization account that someone has to manage? I would not want to be the one deciding what happens with the sponsoring.

[BeastyBlacksmith]

As far as I know All JuliaLang sponsor Buttons go to NumFocus.

[isentropic]

Our bigger issue is I believe:

The things we lack to apply to become a NUMFocus member

* [ ]  A transparent, publicly visible governance model

* [ ]  A roadmap outlining high priority work areas

* [ ]  A code of conduct as well as someone who is responsible for resolving CoC complaints
  One might argue about scientific orientation

not the absence of a sponsor right now. It's a chicken and egg problem.

However, we could though drawout a development roadmap and choose a direction. And then perhaps think about sponsorship, leadership

[isentropic]

On top of my head, some of the things that could be rethought from the bottom up:

1. Easier backend installation/robustness. Too many GR build issues even today. Perhaps another default backend that would be more reliable. Perhaps create a low-level Cairo.jl like simple backend for quick plots.
2. New plotting defaults. Perhaps a large scale community vote
3. Legends overhaul. Legends could be generated in Plots, and backends would just need to place a white box with some text inside. Also, it would allow shared legends and more flexible legend positioning around the figure. Perhaps same with colorbars.
4. A better interactive backend, though plotly is good, it is funky and a little inconsistent. (maybe just my experience)

[BeastyBlacksmith]

Donations are now possible via open collective. I added a link to the README in 1b822b9 and applied for integration with github sponsors.
I'd be happy if someone will join the administration of that, just send me a message.