naming and github org

[paulirish]

Name

"Effeckt.css" I just randomly came up with. I'm not particularly attached to it, though it seemed pretty good. Renaming the project isn't a priority but if we want to, we certainly can.

Github org

The current github location of h5bp/Effeckt.css also need not be permanent. But if we move this to it's own org (probably inevitable) then let's do it with a final name.

[chriscoyier]

I like that it's in the h5bp group. Nice neutral ground.

[AaronLayton]

+1 for keeping it H5BP

[enjikaka]

I agree with @chriscoyier and @AaronLayton to keep it H5BP.

About the name, I think it's pretty great. I'm swedish myself and we spell "effect" with a k instead of a c. A mix of both looks fun and existing.

[KittyGiraudel]

Let's keep it H5BP. It's a token of trust for many people.

Edit: I like the name. :)

[mente]

H5BP is just great. H5BP is already like a brand

[i-like-robots]

When I think of simple animation tools I think of the old Swish/Swish Max programs that you could chuck Flash effects together with... so nothing 'Swishy' sounding is good!

However I think naming should perhaps be related to the tools if the project were to use Compass/Bourbon (the latter something like 'dashing' kinda works).

[grayghostvisuals]

Yeah I agree w/@hugogiraudel. H5BP is a brand of trust. ❤️

[sindresorhus]

I like the name. Some other suggestions: nimble.css, fluid.css, organik.css, smoothy.css.

I think an org could be beneficial. Each main module could be a repo, site could be a repo.

[jsoverson]

+1 for new org centered around a core set of values (performance, device equality, no compromises, etc).

H5BP has history attached to it and can exist with a different trajectory. The 'boilerplate' label is also a loaded term that can alienate people when this lib's goals seem to be closer to the metal while doing as little as possible.

Maybe a 'web-core-tools' org or something that invokes the reaction that the tools there exist as a de facto standard that can be included in any project, not just new projects.

[stephenway]

Keeping this in H5BP is great right now, however if this is one project in a series I would agree with establishing it's own organization.
The name is already awesome however I'd suggest removing the "c" to get "effekt.css".

[chee]

Effeckt.css and Fecked are fine with me.

[mnording]

+1 on @jsoverson idea on new org
Although the H5BP is a solid brand for solid web development there are differences in the core of it.

[mathiasbynens]

@che Probably not Fecked, though ;)

[mikefowler]

Let's just fork @daneden's project and name it AniGREAT.css, amirite?

In all seriousness, I like some of @sindresorhus's suggestions that hint at the "performant" goals of this project. Smoothly.css is rather pleasant.

I like the idea of eventually moving this repo to its own org that could work on hosting projects that have all been vetted against our 60 FPS benchmark (or whatever the applicable benchmark is, for the aims of the specific project).

[grayghostvisuals]

I changed my mind with my original statement. Give it its own org as previously mentioned by @sindresorhus.

[alilleybrinker]

As far as the name, how about "Allure.css"? It's active, enticing, and friendly. It also showcases the project's goal of creating better experiences for web users.

As far as the organization goes. I see no problem with keeping it under the helm of HTML5 Boilerplate.

[daneden]

What's wrong with Effeckt.css?

On 4 Jul 2013, at 07:27, Andrew Brinker notifications@github.com wrote:

As far as the name, how about "Allure.css"? It's active, enticing, and friendly. It also showcases the project's goal of creating better experiences for web users.

As far as the organization goes. I see no problem with keeping it under the helm of HTML5 Boilerplate.

—
Reply to this email directly or view it on GitHub.

[kahlil]

How about 60fps.css or 60.css or sixty.css or jankiller.css (the last one is more for lolz).

[kahlil]

jankfree.css

[kahlil]

I don't think anything is wrong with Effeckt.css, it works, although I don't really see the need for the 'k' in there. Why not just call it effect.css?

[AaronLayton]

I don't think there is anything wrong with Effeckt.css either but I like the idea of jank in the name / slogan, definitely relates to what we are aiming for.

Effeckt.css
Jank free animations for the masses

[AaronLayton]

#18

[yaroslavya]

Animation.css that can be shortend to ACSS. Can be treated as SASS or LESS for animation. As most of people know what is SASS and LESS can be self explaining.

[nstepien]

"Efecss", "FCSS"? Kinda like "fx" for "effects".

[craigmorrison]

I like the idea of playing on FX or some Hollywood connotation because it seems to fit the nature project, taking the flashy side of CSS and making it perform well. The current name already offers that to some extent though.

As far as the org goes, H5BP is trusted but I'm not sure if the connection could be misleading. As others said a library like this is quite different from a boilerplate, there's a much larger element of subjectivity involved in curating the best and most useful effects. H5BP on the other hand is a collection of widely accepted (and often well researched) good practice and I think this library will inevitably be more opinionated.

[grayghostvisuals]

@paulirish
Our own org please! It seems it's going in that direction plus we can also provide other projects under this org that deal with performant animations and transitions as little modules of happiness.

[benschwarz]

If you're going to split different effects into different repos (ah-la suit-css https://github.com/suitcss/suit), then I'm all for it being moved to its own org. Otherwise, probably not worth it.

[grayghostvisuals]

@benschwarz Thats the idea.

[arthurvr]

Was consensus reached in here? Personally I'm +1 on an own org. Allows us to split up stuff, and that's IMHO more maintainable. I like the current name.

[grayghostvisuals]

@arthurvr +1

[arthurvr]

There has been some noise around effeckt lately so I think we should move forward on this one. It might encourage contributions. @h5bp/effeckt-css So the consensus is an own org?

@h5bp/owners Are we all alright with this?

[drublic]

@arthurvr Yes.

[arthurvr]

Let's do it then! If everybody's alright with that I'll do all necessary work to make this happen. @h5bp/effeckt-css Thoughts on the org naming?

[wellingguzman]

I like it being part of h5bp (like it has been said brand of trust), and I also like the name as well.

[AaronLayton]

It is only 1 repo at the moment - so not much point it being in its own Repo, unless we plan on splitting this up at a later date?

If its staying as 1 repo then I would say to leave it as H5BP also, thinking again that its a name many already know. If there is some management issue with that then I guess it will have to be its own Org

[grayghostvisuals]

All due respect to everyone commenting this is a very divided convo that flip flops quite a bit. Also…I think there are more important issues at hand right now. IMO @paulirish should make the final call since his initial thoughts hint at an inevitable sep. org.

[benschwarz]

Its almost 2 years since this issue was opened — its safe to say that @chriscoyier, @paulirish and I are all reasonably checked out of this project.

I'm more than happy for it to be called effeckt (because its a 2 year old project), and see it reasonable for it to be moved to a new organisation.

• h5bp is inactive
• h5bp is no longer under active use
• effeckt isn't related to h5bp, it just ended up there because it was a community project

Motion to rename this to effeckt/effeckt.css

---

Finally:

@wellingguzman has done an incredible amount of great quality work, and I'd like to suggest that he becomes the official project lead for effeckt.

[arthurvr]

h5bp is inactive
h5bp is no longer under active use

@benschwarz What makes you think that? That's not in any way true.

effeckt isn't related to h5bp, it just ended up there because it was a community project

👍

[paulirish]

thumbs up on moving to own org.

[AaronLayton]

Motion to rename this to effeckt/effeckt.css

@benschwarz @paulirish ok lets do it - issue close

[arthurvr]

Seems like we have a consensus then. I'll do it this evening.

[alrra]

Comment removed (Reason: all the people previously mentioned in this comment apologized)

[AaronLayton]

Offtopic (can we close this issue now?)

[wellingguzman]

The decision have been made.I'm closing this issue.
I believe there's not anything else to say.