Reorder members sensibly

[bsipocz]

Would be nice to come up with a reordering of OA members, as currently it sorely depends on the location of their entry in the yaml file.

One option is to do it alphabetically. I don't like it very much as it would put one of the big members, sunpy at the end. Same with reverse alphabetical, then astropy would be at the bottom of the page.

Keep the members participating in the actual gsoc at the top of the list, and the rest afterwards. Within the two groups alphabetical might be fine.

[dpshelio]

we could re-order them in order with how many stars they have in github... as a meaningful number of community size.

[bsipocz]

How do you deal with orgs with multiple repos? Also, with orgs that don't really participate in OA activities, but otherwise are bigger?
I certainly support to have astropy and sunpy at the top, both, but then don't know the answer (besides I can very well find issues with any suggestions ;) )

[dpshelio]

How do you deal with orgs with multiple repos?

We use the one with more stars 😁

with orgs that don't really participate in OA activities, but otherwise are bigger?

what do you mean?

[bsipocz]

with orgs that don't really participate in OA activities, but otherwise are bigger?

what do you mean?

We have members with 100+ stars that doesn't really participate in our activities, gsoc or even pyastro, so I don't think shorting based on stars is a good metric. Stars is basically not a really good metric.

But if we agree that we have two sections, one the actively GSoC/other summer of code participating in a year, and the second for everyone else, then I don't really care how we order the orgs within those (but still think, that both astropy and sunpy should be stick at the top of the list)