Ross Barnowski

> What options are available to us? Well, it could be removed outright. Personally I'd be in favor of that - not only for this rule, but for many of...

> If you would prefer, I am happy to reword the proposed parameter descriptions. If you don't like mentioning the word edges, maybe we could just say something like (number...

Thanks for the suggestion @user27182 . Currently, the validation code is intended to validate for compliance against the numpydoc docstring format specifically. I think there's already been some scope creep,...

Indeed #7739 fixed this for `bar` so `arc3`, `angle3` and `bar` are currently supported. @dg-pb any thoughts about the remaining 2 connection styles?

I think @dschult and @Peiffap are correct that the confusion results from the data rather than a bug in `adjacency_matrix`. Therefore I will close this; however, if you believe there...

Yes, most actions triggered on push/PR run on forks. I'm not sure what the best practice is here - I had always assumed that when jobs were enabled on forks...

IMO this is more of a discussion than something that needs implementation. In particular, I'd be interested in learning: 1. How github actions handles CI jobs across forks. Particularly, when...

Thanks @bsipocz ! That does seem pretty wasteful then... Since NetworkX is pure Python, the use case of "I use my own fork to test my changes on windows before...

We looked into this a bit in the community meeting and found that it seems to be under the user's fork settings. For example, on your fork if you go...

> It may make sense to write a brief SPEC on "Unified theming" for the community. This would be great. In my experience there's been some unstructured, unofficial effort to...