New name

[sagikazarmark]

The PHP HTTP client is an abstraction layer to separate general purpose libraries from concrete client implementations in order to make them move flexible. It is the successor of the Ivory HTTP adapter and we should not use Ivory anymore to keep it separate from all the other things under the Ivory name that do unrelated things.

Just calling it "php http" makes it impossible to find this thing in google, as almost website about web development has these keywords. We should have some additional name that makes it findable.

Ideas so far:

• CPHC/APHC for common php http client / abstract php http client by @dbu
• Klant by @hannesvdvreken
• Raspberry by @Zarkonnen
• Hunlet by @patkar
• Tupac by @greg0ire
• Straw by @Pierstoval
• Httplug (and variations) by @sandermarechal
• Phetch by @sandermarechal

[Zarkonnen]

"Raspberry", because that's what phphttp sounds like.

[QuingKhaos]

Hunlet 💨

[greg0ire]

The Universal Php Abstract Client or ... Tupac. Abstract like a ghost, awaited like the Messiah.

[sagikazarmark]

Wow, thanks fo the ideas. I am adding them to the list.

[sagikazarmark]

@patkar where does this name come from?

[QuingKhaos]

@sagikazarmark Clicked through a crazy name generator ^^

[sagikazarmark]

I had the feeling 😜

[Pierstoval]

Straw, because the client asks for a drink, gets one, but wants a straw. And a straw is thin, sexy, and can gets any drink in any glass.
Edit: no reason, just fun :p

[hannesvdvreken]

hahaha that's funny 😄

[dbu]

i love straw. the only worry i have is if it might fit better for an actual client than an abstraction layer.

[hannesvdvreken]

Straw could also be a helper for gulp.

[Pierstoval]

@dbu I think this can be debated, because it can be put in this order : Client asks for a Drink, but to be sure that he can drink in any kind of glass/bottle/can, he needs the Straw.
EDIT: Or we can name it "TinCan" :D

@hannesvdvreken's right, it could be a Gulp helper (actually I already made a helper for Gulp and named Gryp 😆 )

[sandermarechal]

httplug? phplug? phetch?

[Pierstoval]

I like Phetch !

[dbu]

httplug! and the logo looks like a power plug world adapter!

[sagikazarmark]

👍

BTW naming: should we name the whole organization. Or just the adapter? Or the adapter and other packages, like message-factory?

[dbu]

or httphplug but that becomes difficult to say and spell

[greg0ire]

phttplug then ?

[dbu]

i think i would use the name as sort of a nickname and keep calling the organization php-http. and the client is called httplug or phetch or whatever we chose

[sagikazarmark]

👍

[sagikazarmark]

What about the package vendor? It could also remain php-http OR have a separate vendor for the client related stuff:

• kantphp/klantphp
• httplug/httplug
• php-http/klant
• httplug/guzzle6-adapter

[sagikazarmark]

Httplug sounds good, but has no real relation to PHP. Variations with "PHP" in it are a bit complicated I think. Also, the httplug logo idea is great. 👍

[joelwurtz]

Httplug sounds good for me also.

IMO, since the vendor name is php-http, not having some sort of relation to PHP in the name is not a problem

[dbu]

i would keep the vendor name php-http and then httplug is specific enough.

[sagikazarmark]

I merged the terminology branch and started to remove implementations which are going to be part of the utility repo. The next step is to choose a name. My personal favourites are Klant, Httplug (or a variation) and Phetch. Httplug would be a wise decision with possible logo design keeping in mind. (BTW anyone want to work on that?)

Should we set up some sort of vote? Maybe on Google Docs or in a separate issue?

[dbu]

the question is who would be allowed to vote. imo we should try to find something that all with push rights to this repo are happy with. @sagikazarmark as lead should have the final say in this. maybe comments on this issue are enough to decide?

my order of preference is Httplug > Klant > Phetch.

and in my idea, the name would be more of a stick-on thing than deeply integrated. the repository or php namescapce, interfaces or class names would not change.

[sagikazarmark]

my order of preference is Httplug > Klant > Phetch.

Same here

and in my idea, the name would be more of a stick-on thing than deeply integrated. the repository or php namescapce, interfaces or class names would not change.

Should the namespace remain Http\Client then?

Actually I would like everyone to express his/her opinion, but the final decision should be made by @php-http/owners

So everyone please "vote" this week. If we can't agree on one of the currently proposed names then we postpone the alpha release.

[dbu]

Should the namespace remain |Http\Client| then?

i would say so, yes. i would just say "Httplug, the HTTP client abstraction for PHP" or something like that. and keep calling the organisation php-http. httplug is just the name to use and make people find the thing when searching the web.

[sagikazarmark]

👍

[ddeboer]

What about the package vendor? It could also remain php-http OR have a separate vendor for the client related stuff

I’d say: one vendor for both to show that the packages play well together.

Should the namespace remain Http\Client then?

Yes. Http is really the core business of all packages in the organisation.

Currently, I’d vote for Httplug as well.

[sagikazarmark]

@hannesvdvreken as the author of name Klant, your situation is not easy. 😉 What is your opinion about Httplug?

[hannesvdvreken]

I'm fine with Httplug as well. Let's vote? Set a time frame and let people comment.

[sagikazarmark]

Well, I think we already have a majority favoring Httplug, that's enough for me. The timeframe for voting is this week.

[hannesvdvreken]

👍 httplug it is!

[dbu]

Well, I think we already have a majority favoring Httplug, that's enough for me. The timeframe for voting is this week.

i think we have all active owners happy with httplug - so lets go with this! shall we tweet to ask if somebody wants to design a nice logo?

[sagikazarmark]

I will rename the repo and packagist package then.

@dbu Let's go with that tweet

[sandermarechal]

Brainfart for a logo, perhaps something where the U in httplug is a stylized electrical plug?

[sagikazarmark]

@sandermarechal Yeah, @dbu wanted something similar. He imagined an electrical plug with the Earth maybe?

I am not really a good designer, so I would leave this thing to someone else. 😉

[dbu]

@sagikazarmark but rename to client, right? i think the httplug should not be in the php namespace / github repository path. or do you want to go full out with the name?

[sagikazarmark]

I planned to rename the repo to httplug, but leave the namespace Http\Client.

[dbu]

I planned to rename the repo to httplug, but leave the namespace |Http\Client|.

okay, lets do it that way. i wait for you to do that and then ask for proposals. do we have a twitter name httplug? can you create one? actually, would be great if you can tweet from that name and we retweet

[sagikazarmark]

Will do that. Actually I haven't created an organization name before. Do I have to just register a new account?

[ddeboer]

No, you can just create the organisation from your profile page.

[sagikazarmark]

Thanks 👍

Update: @ddeboer I actually meant a Twitter orga account, not a Github one. I've created plenty of Github organizations before. (check my profile 😉 )

[dbu]

@ddeboer we are talking about twitter :-)
@sagikazarmark creating an account with a different email adress is what i did, yes

[sagikazarmark]

Yeah, already done it. Retweeted by me.