Should ArviZ have "community partners"?

[OriolAbril]

Right now, ArviZ integrates with many libraries and also coordinates with some to some extent in defining some features and roadmap. However, this happens kind of ad-hoc due to developer overlap between the different libraries. Could it make sense and be beneficial to all projects involved to try and establish "project level" relations?

Some idea(s):

• Have a yearly "consulting" roadmap meeting with 1-2 representatives from each partnered project (will probably be the same at first, but could also open the door for more varied input from projects with no developer overlap). That could serve to inform our roadmap meeting, ideas we might not have thought of, aligning priorities and grant proposals...

---

Note: I am sure we can find a better name and get to something that makes more sense. I had the idea and wanted to write it down so I don't forget

[OriolAbril]

Another potentially good option would allow "community partners" or whatever name we choose to open a couple call for a vote issues in order to accelerate decisions on areas that affect them more closely. For example, PyMC might have benefited from doing that after 2 months of opening one for arviz-devs/arviz#2155, which is quite trivial and fast to solve voting, but ended up stalled waiting for consensus.