Opened 16 months ago

Last modified 6 weeks ago

#5474 new change

Rename "cms" to "wake"

Reported by: juliandoucette Assignee: kvas
Priority: P3 Milestone:
Module: Sitescripts Keywords:
Cc: kvas, jsonesen, wspee, juliandoucette, ire Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by kvas)

Background

Let's stop pointing this out :D

However, our CMS is not a CMS (pun intended) but rather a static site generator

What to change

Rename the "cms" to "wake", rename the folders inside accordingly and update the infrastructure to match. It might be easiest to create a new repository, push the renamed version there, then switch all infrastructure, then eventually deprecate and remove the old repo.

Change History (26)

comment:1 Changed 16 months ago by juliandoucette

I set module to Sitescripts instead of sending an email to operations@… because I didn't know if you (Sitescripts) would agree.

comment:2 Changed 16 months ago by kvas

I agree that CMS is a bad name for our static site generator and I would also like to rename it. In my opinion just renaming the repository would not be enough, I'd rather rename the "cms" module inside as well and make it a python package while we're at it. I'm also not sure about "website-generator" as a name, perhaps we could think about something more distinctive so that we could publish it on PyPI.

Anyway, I welcome the ticket.

comment:3 follow-up: Changed 16 months ago by juliandoucette

In my opinion just renaming the repository would not be enough, I'd rather rename the "cms" module inside as well and make it a python package while we're at it. I'm also not sure about "website-generator" as a name, perhaps we could think about something more distinctive so that we could publish it on ​PyPI.

  • I agree about renaming the module inside too
  • I disagree about renaming it to something more distinctive so that we could publish it on PyPI
    • Because we don't have the resources to support it as an independent open source project?
    • But this is not a strong objection

Anyway, can you take this from here?

comment:4 in reply to: ↑ 3 Changed 16 months ago by kvas

Replying to juliandoucette:

  • I disagree about renaming it to something more distinctive so that we could publish it on PyPI
    • Because we don't have the resources to support it as an independent open source project?

You're right, we don't have resources to run it as a proper open source project ( :'( ), but just publishing it on PyPI doesn't cost much (we just need to create setup.py with some metadata) and then publish it. Installing CMS would become easier: "$ pip install eyeo-magic-sauce + $ eyeo-magic-sauce my-dir" instead of "figure out dependencies and install them + hg clone ..../cms + run it in an awkward way from where we've cloned it to".

However, we might still not want to think about publishing new releases, versioning and all that stuff. At least not until we have a working CI or some other good way of automating these things. If we just make CMS a Python package, we get almost all the benefits of publishing it on PyPI anyway, so we can limit this ticket to just that. But given that we might want to publish it in the future, I would prefer to have a "more distinctive" name to avoid renaming it again.

Anyway, can you take this from here?

Yes.

comment:5 Changed 12 months ago by kvas

  • Cc juliandoucette ire added

I would like to move this ticket forward because it somewhat stands in the way of making CMS a Python package. At least we will have to do part of the work twice if we don't do this ticket first. Let's decide on a name first. I propose that we start the discussion here, decide on a list of acceptable options and then present them to Felix.

The options that I see are:

  • "website-generator" -- The original proposal from Julian,
  • "eyeoweb" or "eye/web" -- More distinctive, with "eyeo" in its name, perhaps we can think of other similar options,
  • Something related to ninjas, although I only came up with "shuriken" and "kunai" (and I'm not very happy with either and they're taken on PyPI -- the python package repository).
  • Some kind of contraction related to static generators: "statgen", "wake" (from web make), "wender" (from web render).
  • A word that is a metaphor for what a website generator does: "conjure", "evoke", dunno I guess native speakers could do better :D.
  • We can just use an animal or a plant like some others.

Do you like any of these options? Do you have better ideas?

comment:6 Changed 12 months ago by sergz

what about the following play of words? There are dynamic and static web sites and there are "statics" and "dynamics" in physics. So, one could use some distinguishable feature of statics, e.g. equilibrium, though I guess there is a huge opportunity for typos, however some words from another languages could be better and they don't overlap with English:

  • ruhen or ruhe
  • pokoi
Last edited 12 months ago by sergz (previous) (diff)

comment:7 Changed 12 months ago by juliandoucette

I like "wake". Is it available?

comment:8 Changed 12 months ago by kvas

"wake" is free. Some other ideas from #english channel (ironically enough, they all use words from other languages) were: "allesklar", "lekker", "imprimus" and "genus".

comment:9 Changed 12 months ago by ire

I vote for "wake" as well. It's simple, short, and a nice play on words.

comment:10 Changed 11 months ago by juliandoucette

I think it would be nice to have this rename completed before we launch help center using gitlab CI (soonish).

comment:11 Changed 11 months ago by jsonesen

Sounds good, I like wake as well

comment:12 Changed 11 months ago by kvas

  • Description modified (diff)
  • Summary changed from Rename "cms" to "website-generator" to Rename "cms" to "wake"

comment:13 Changed 9 months ago by juliandoucette

Looks ready to me?

comment:14 Changed 9 months ago by kvas

  • Priority changed from Unknown to P3
  • Ready set

comment:15 Changed 7 months ago by kvas

Bad news, everyone!

While this ticket was sitting in the issue tracker, someone created a Python package called wake. As annoying as it is, this means our package can't be called wake, at least not if we want to keep the ability to publish it on PyPI one day (I would like that).

Our immediate options are either keeping the name but calling the package eyeo-wake (easy, but not very forward looking) or coming up with a new name, which we can still claim (and I will claim it right away, since I started working on this ticket). Perhaps someone will have another idea.

I'm slightly leaning towards a new name, to start things right, even though we've been calling this thing "wake" for a while with Jon and I'm kind of used to the name by now. What do you guys think?

comment:16 Changed 7 months ago by ire

Oh no :(

I agree that we should come up with a new name instead of eyeo-wake. I'm not great with coming up with names, but these are the ones I like from the previous lists:

  • statgen
  • eye/web
  • genus

comment:17 Changed 7 months ago by jsonesen

statgen is pretty concise and sorta makes sense, genus sounds cool I too am bad at names :)

comment:18 Changed 7 months ago by juliandoucette

statgen is fine with me (if it's available).

comment:19 Changed 7 months ago by kvas

It seems that everyone likes "statgen" except me. It's ok objectively but sounds a bit like the name that Soviet Union bureaucrats would've come up with, so I have a bit of aversion to that :). I will try to propose a couple more names but if none of them are as liked as statgen, we'll just go with statgen. So here we go:

  • statig (sounds like "static" but means "static generator"),
  • webmaker (more or less what "wake" originally came from),
  • spinne (german for "spider", which is "web maker"),
  • spinnr (flattr-style misspelling of "spinner", which is like "spinne" but sounds nicer).

My preference is "spinnr" because it's unique and easily findable, sounds nice, has this nice ring of stuff working and happening, and it's also like "flattr", which is an extra bonus in the context of eyeo.

comment:20 follow-up: Changed 7 months ago by juliandoucette

webmaker (or webmake?)

comment:21 in reply to: ↑ 20 Changed 7 months ago by ire

Replying to juliandoucette:

webmaker (or webmake?)

I like webmake

comment:22 Changed 7 months ago by jsonesen

So as Vasily noted in IRC webmake is taken, webmaker is okay.

I do like the idea that was talked about with using conjure or evoke, like siteconjure,
"webvoke" or "woke"

comment:23 follow-up: Changed 7 months ago by kvas

I like woke probably about the same as spinnr. Maybe we can vote in IRC tomorrow evening (GMT evening)?

comment:24 in reply to: ↑ 23 Changed 7 months ago by ire

Replying to kvas:

I like woke probably about the same as spinnr. Maybe we can vote in IRC tomorrow evening (GMT evening)?

(I'm away today so may not be able to make the vote so here are my thoughts)

I don't like using woke particularly because of its cultural meaning. I don't think it's appropriate in this context.

I don't mind spinnr, but still prefer webmake.

comment:25 Changed 7 weeks ago by kvas

A new name proposal by Julian, that I quite like is liven.

comment:26 Changed 6 weeks ago by kvas

  • Owner set to kvas
Note: See TracTickets for help on using tickets.