Tim Hoffmann

@story645 all names are working titles. We will find out how they are properly called while we go. That also depends on how they are eventually scoped and interplay.

@trygvrad The aspects 1 & 2 have not been on my radar. I had thought the data were part of the original Artist that ScalarMappable was added to, but makes...

I agree that a series of PRs to main is not ideal. Would it be reasonable to create a longer-lived feature branch for this, to which we would do smaller...

Won't other (scientific) libraries have the same issue? (Thinking numpy, scipy, pandas, ...) How do they solve it? Would it make sense to create an independent guide how to contribute...

I'd prefer that we don't use the tagging mechanism for internal suff. Making internal labels public is confusing, OTOH packing them behind `.. ifconfig` is extra effort (and doesn't work...

Well, I feel uncomfortable, with this duct-tape coding of internal tags via `.. ifconfig`. It's cluttered and difficult to write for tag authors. But it technically, works and could be...

Is it sufficient to create a collection issue for "example rework"? Instead of adding a `internal: needs review` tag to the code, add a line in the issue - [...

@shalul The issue is open, so not solved yet. But as linked above, it has an associated open pull request, i.e. a solution proposal. Therefore it does not make sense...

@tacaswell Sorry for being late in the process, but we need to clarify the API strategy. Fundamentally, 1. It's desireable to have naming consistency between kwargs and setters 2. We...

I'm removing the tags "good first issue" and "difficulty: easy" for now. While they are correct for the eventual implementation, we need a though API discussion and decission first. These...