-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vote: Renaming the project #664
Comments
Project Name: Gomods
|
Project Name: Gopher Collective
|
Project Name: GopherPacks
|
ProjectName: GoMods
|
Note that there is another open source Go Module Proxy under the name |
I think we should wait on renaming anything until we figure out what to do with Olympus on a technical and an architectural level. For example, if Olympus/Proxy ended up getting merged into one thing: then we can just call the server itself Athens and that's it. In other words if someone asks "what's Athens?" We'll have a simple answer: it's a GOPROXY implementation. There's only one server inside the Athens repo, and that is the Athens server. But if Olympus becomes a big thing that's totally separate from the "proxy" that we currently have, then yes, it's worth looking at better naming of things. |
good point @marwan-at-work. here's my proposal:
thoughts? |
@arschles a much easier solution is to just have the registry be the only public one and wait on Go1.12 to fix this issue: golang/go#26334 |
I'd love to suggest that our names should be unique in that it won't be confused with other Go Proxies that the open source community is building. For example: For example, GopherPacks sounds the best so far. But other people might build GopherProxies or GopherMods and I'd easily confuse them together. I'll add suggestions as other comments once my creativity kicks in, if ever :) |
As of #772, we've decided that we're not going to build a registry, so the confusion between the proxy and registry that @marwan-at-work mentioned here is no longer. So I'm adding a voting option here for the name "Athens Proxy" |
I'm putting this under v0.1.0 because I think it would be a good idea to decide on a name before releasing a beta |
At the October 18, 2018 developer meeting, we discussed #664. Since we decided in #772 that we're not gonna do a registry, we decided that the vote should change a little bit because we don't have to distinguish between the proxy and registry. I said in the meeting that I would create a new vote between "Gomods proxy" and "Athens proxy." I thought about it and decided that we should move on and call this the Athens proxy since it's what we've been doing already. I am going to close this issue now and finalize us on "Athens proxy." Let's move forward with our v0.1.0 beta release 😄 |
Suggestion: Rename the project to something that most go developers would at least recognize as being a) related to go and b) solving a problem (such as dependency mgmt, proxies, modules, etc).
I'm going to reply to this issue with suggestions that people can vote on using 👍 or 👎 . Feel free to contribute your own suggestions, but please it would really help if you formulated your replies in the same format, so that they are votable as well.
Background
At GopherCon it became painfully obvious that continuing to use the codenames "Athens" and "Olympus" is hurting understanding of our project. No one understood what "Project Athens" was, that it was even associated with: go, modules, goproxy, etc. During our workshop, explaining the difference between Athens, proxy and Olympus was difficult and confusing for our new contributors.
We chatted about this among the maintainers and during our dev meeting yesterday, and decided to vote on new names.
The text was updated successfully, but these errors were encountered: