Closed waghanza closed 5 years ago
OK, I accept the migration.
Then we have to find a name
For me, the main idea behind that performance
battle :stuck_out_tongue_closed_eyes: is some king of promotion, so name could be about that
Specifically?
late take some time to think about that ;-)
at least I would have some ideas in 2 days ;-)
@OvermindDL1 any ideas ?
How about which-is
/the-fastest
? lol
Hah, I like @tbrand's suggestion, leaves it open for more repo's with more tests later too. ^.^
So why not a more generalistic word like agon
, then it could be agon
/backend
@waghanza Sorry I can't agree the name.
For me, who don't have enolugh vocabulary, dont' understand what it means without googling.
which_is_the_fastest
is verfy simple, understandable and catchy for every users on Github.
Even we drop the name of which_is_the_fastest
, it have to be simple, understandable and catchy
at least.
@tbrand which_is_the_fastest
is surely understandable, by whom have some technical skills
what I mean is that :
fastest
IS subjective (depending on use case) -> a telecommunication app and a web app are not considered fastest the same wayis
COULD be restraining for some people, according that anyone has enough knowledge to say that he has the solutionIn short :
I don't say we have to keep the name(which_is_the_fastest
) but I just disagree with the suggestion.
So pointing out the wrongs of the name mean nothing here. (I would like to put which is the fastest
on somewhere since I attached it personally. š)
How about naming org as which_is_the_fastest
? Repository names are whatever you want.
Like which_is_the_fastest/web_server
.
You might also want a which_is_the_highest_throughput
or which_is_the_most_concurrent
or something, that's why I like the which_is
personally. Optimally I'd choose which
, then you could make the name of each project better like which/http2_server_is_the_fastest
and which/html5_client_is_the_fastest
or so.
Uh huh.
like your shared ideas and the concern
about non-executive word
I personally find which
is a little bit too restraining for me
That's already taken.
I see, which
and concern
are already taken, we have to be imaginative
Purely an example name, just showing that more generic is better.
I already took which-is
and which-is-the-fastest
org since they are candidates. which
is not taken by me anyway.
@OvermindDL1 Specifically?
@OvermindDL1 Specifically?
Hmm? About what?
I have this organisation https://github.com/TheBenchmarker Would be happy to grant you guys access to it so you can use it for this project. Trying to keep it nice and generic.
@aichholzer Would be :heart: to collaborate. However, the name TheBenchmarker
is making me feal uncomfortable.
For me the idea is to gather communities, by make one project for a transparent competition, using the
suppose that we have the
knowledge on what to do
@tbrand What do you think about strugglerr
(struggle
is already taken) ?
I think it is revealing what we want to do, some effort to reveal some unknown but great frameworks :tada:
It COULD also be struggler-io
so as we can also take domain name
strugglerr
is not directory meaning the org I think. Then what is the repos will be?
We'll let people know what we are doing at there by org and repo name.
You might guess what I was doing on this repository which_is_the_fastest
right?
@tbrand in fact the idea behind creating an org, is also to create a community
The name struggler-io
(to match a domain name stugglerr.io) will be to describe a community struggling for performance :stuck_out_tongue:
For us, web frameworks with a focus on backend
I fail to understand how TheBenchmarker
can be uncomfortable. This project is about benchmarking something, in this case HTTP frameworks. I do not think this project has anything to do with performance struggles.
Why would I look at benchmarks if I am having problems with my performance?
And using your words; create a community
-Yes, a community around creating good and trustworthy benchmarks.
Anyway...
@aichholzer My suggestion was not about benchmarker
, but about using the
=> for me the
is too implying a supperior knowledge (very diffucult to be clear, so I hope you'd understand)
I like following the amber
philosophy => https://github.com/amberframework/amber/blob/master/.github/AMBER_PHILOSOPHY.md
I follow your second point. The project is NOT about solving any performance issue ;-)
Yes, the decision will be long to take, but it's for the best :stuck_out_tongue:
To me The
implies a reference, like the person who does benchmarks. When you are sick you go to The doctor
, when your car is broken you go to The mechanic
... When you need to get solid information about a benchmark, you go to The benchmarker
.
Anyway, my two cents... Checking out.
@aichholzer Personally, when I get sick, I go ot a
doctor (at least any doctor available) :stuck_out_tongue:
I think the repo name of āwhich_is_the_fastestā is super clear and effective. I think keeping it as-is is a great idea. For the org name, Iām not sure but I think TheBenchmarker makes a lot of sense
Sure āTheā implies itās the only one but I think people know thatās just a name and isnāt really the only benchmarker :)
@aichholzer ok for the name of the group
We have then to choose the projet name
I suggest using a name related to backend
I think the repo name of āwhich_is_the_fastestā is super clear and effective.
Agree. That's what I'm saying in this issue. I could change the name but the next name have the same features.(super clear and effective)
Sure.
@tbrand The purpose of migration is to enable external service
btw, it can be the same on personal repos (but will less services)
Did you guys want to use my org TheBenchmarker
?
-I will make you all part of it.
@aichholzer For me it is OK to choose a project name like TheBenchmarker/backend
:heart: (as I am more skilled in backend things). I will be hapier :tada: if you can collaborate as you seems to be more skills in server-side frontend.
@tbrand Is it OK for you ?
@waghanza -No problem. And no, I am not front-end. Not at all. I have been writing back-end services since 1998. I can do front-end, but I rather dislike it.
Let me know when to move forward and if you all agree, then I will add you all (the involved parties) to TheBenchmaker
organisation.
@aichholzer sorry for the mis-understanding, I just show a majority of javascript
app on your repos
I get paid to write Node.js software, hence the mostly JS repos. And no need to be sorry.
@aichholzer interesting ... can I make a short cut by saying rayo
will be used in production in your company ?
Rayo
is already used in production at a couple of companies. ;)
ā”ļø
Hi all! Thanks for the many suggestions and discussions!!
Finally I decided to migrate this repo into which-is
org. And the name of this repo gonna be the-fastest
at first. (It would be changed)
The reason is that it is the only way to keep the effective name and it also has flexibility for the future.
I'll close the issue. If you have other comments, please open new issues or ping me on gitter.
Regards.
@waghanza deny to my proposal on Gitter. Please continue the discussion.
@tbrand sure
for me this decision will be long and puprose is promotion ...
I think there is 2 main ideas here :
Summarizing our discussion, we agree about migrating to org TheBenchmarker
.
The next step is too choose the project name (according to what use case we want to deal about)
Did we? I've never agreed the org name. (Thanks for the proposal anyway.) Who did agree and when?
@tbrand I've noticed it, but the way we will succeed it to let a majority of developers decide.
Are you agree ?
It it's snake case, I'll accept.
Oh no snake cases since it cannot contain underbars. I've took the-benchmarker
.
@tbrand I do not understand, your concern is about the letter design ?
Yup
I just prefer the-benchmarker/which-is-the-fastest
to TheBenchmarker/WhichIsTheFastest
since former is readable for me.
@tbrand is this a problem of keyboard layout
, or something like that ?
honestly, it equal for me (camel case, snake case), I just prefer to have several developers.
if @aichholzer @OvermindDL1 @paulcsmith are OK for this naming convention, it's ok for me :heart:
I mean readability.
Hi @tbrand,
Some services (which are in the marketplace) are more usable (due to github permissions) to use / enable on some group project.
For example, using https://dependabot.com (to manage dependency) COULD only be done either on my fork or on a group project.
Do you mind if I create a group in order to migrate this project ?
It will be very helpful for maintainers.
Regards,