search

rabblerouser / core

Pluggable, extensible membership database for community organising
GNU Affero General Public License v3.0
17 stars 10 forks source link

Ultimate bikeshed - project naming convention #136

Closed camjackson closed 7 years ago

camjackson commented 7 years ago

Right now most of our projects are in the form rabblerouser/rabblerouser-something. However, at least one is just rabblerouser/event-archiver, without the extra RR in the name. This came up on slack, with comments from @akjones, @phazel, and @yearofthedan, but there was no consensus. It would be good to figure this out before we start migrating away from Snap, just in case repo renaming causes issues there (we know it confused Snap in the past).

screen shot 2017-02-13 at 11 00 06 pm

:bike: :bike: :bike: :bike: :bike:

camjackson commented 7 years ago

Just want to point out that the repo names don't necessarily need to exactly match published names. E.g. on github we might have rabblerouser/stream-client, which we could publish to npm as rabblerouser-stream-client so that the context is clear. Although now I think about it, npm supports namespaced packages too, so we could equally publish as @rabblerouser/stream-client. Things that get published as docker images likewise could be rabblerouser/mailer both on github and on the docker hub.

akjones commented 7 years ago

I'm happy with relying on the github org name for repos, so rabblerouser/stream-client would be fine, as long as artifacts get stored in the public repos with rabblerouser as either a namespace, or repository name or as a prefix if the artifact repository doesn't have the concept of a namespace.

camjackson commented 7 years ago

I think that's close enough to having a consensus. I'm going to make this change now, so that we get it out of the way before potentially lots of new people join in tomorrow, only to have things shift from underneath them.