Polis: Consider re-organizing of github org

[patcon]

Having the github org be a good landing page can be helpful. When people arrive on other repos not intended to be starting points, they will often jump back to org to see where they should be. Right now, the github org isn't particularly friendly to newcomers :)

I'll add some facts/feelings and ideas here. (Others should feel free to add their own however they'd prefer.)

Legend
:mag: Fact
:heart: Feeling
:bulb: Idea

Statements

1. :mag: GitHub org's allow "pinning" important repos
2. :heart: I feel that other github orgs, like EDGI's org, are more welcoming than polis'.
3. :heart: I feel that the "issues" implies a very limited scope.
4. :heart: I feel that repo descriptions are important to helping people orient from the org page.
5. :heart: I feel that a more encompassing top-level meta repo could be better for newcomers and future community-building.
6. :bulb: Let's rename issues repo to something wider scope like overview (or polis-hub or welcome or...)
7. :heart: I feel camelcase implies "this is code", and so prefer to avoid it in repo namespacing. (Where other sorts of contributors might be arriving in future.)
8. :bulb: Let's move polisDeployment content into overview
9. :bulb: Let's add clear descriptions to all repositories.
10. :bulb: Let's pin repos on org page in an intentional order that's helpful for exploration: overview > polisDocumentation > polisClientAdmin/polisClientParticipation > polisServer > polisMath

[patcon]

Also:

1. :heart: I feel inspired by the Hoodie project's organization of its GitHub presence.
2. :heart: I feel positively about emoji kicking off each repo description!

[colinmegill]

It's time for all this!

On Mon, Apr 2, 2018, 8:35 PM Patrick Connolly [e-mail]
wrote:

Also:

❤️ I feel inspired by the Hoodie project's organization of its GitHub
presence https://github.com/hoodiehq.
❤️ I feel positively about emoji kicking off each repo description!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pol-is/issues/issues/99#issuecomment-378118172, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABsDGfhDp4Z508E-zNQRV-G9edBYemnuks5tku4bgaJpZM4TEZYz
.

[patcon]

Demo! https://github.com/pol-is-2

[patcon]

Happy to do the leg-work if you feel like giving me admin ;)

[metasoarous]

@patcon I like your overall vision here.

Regarding polisClientParticipation specifically, that code isn't just for the Visualization but for the entire Participation view (the voting widget, etc). In some cases, the visualization might even be turned off. So I'm not in favor of this particular rename.

I'm not apposed to a bit of reorganization around issues/documentation/deployment, but would like to think through things a bit before doing any serious reorganization here.

At the very least though, we can start pinning repos, adding badges, useful descriptions and such as you suggest.

[patcon]

Cool! Feel free to steal meta content from that org, or alternatively grant me admin and I'll take a stab at just those final things you mentioned -- minus repo nenaming :)

cc: @colinmegill

[metasoarous]

@patcon How does this look?

[metasoarous]

@patcon - BTW, I'm open to changing polis-issues to polis-overview with a description like "getting started, feature requests, and bug reports". But we should wait till there's actually some more overview type content there. Happy to accept a PR on that.

[metasoarous]

A bit of cleanup:

[patcon]

This was already dealt with, so closing out :)