Cambridge is moving to github with a new project name

18 views
Skip to first unread message

Erdinc Yilmazel

unread,
Dec 14, 2011, 11:04:04 PM12/14/11
to cambridge...@googlegroups.com
Hi all,

I am happy to announce that I have started transitioning the project to github. Another big announcement is that I have decided to rename the library to htmlplus. Renaming the project requires me to do a lot of refactoring in the codebase as well, so I will probably rename modules, packages and classes so the next release will be incompatible with the old code. However the transition should be as easy as just renaming "cambridge" to "htmlplus". 

Here is the url for the new github project page: https://github.com/htmlplus/htmlplus

I also checked in Janino support and Playframework 1.2.4 integration, thanks to patches submitted by Tom Carchrae. Thanks again for the contribution Tom!.

Stay tuned for the updates. The next release will be in January with Spring integration support and I am hoping to implement the play framework support as a module.

PS: My immediate goal is to come up with a better documentation. I really would appreciate if anyone can recommend me some tools to write a nicely structured documentation for the library. 

Thanks,

Erdinc

Jon Stevens

unread,
Dec 14, 2011, 11:22:06 PM12/14/11
to cambridge...@googlegroups.com
I gotta say, I think that htmlplus is a terrible name.

I think that we've made some good suggestions to you in private. 

It is too bad you are choosing to go with this name without consulting the community you are trying to foster.

Gp P

unread,
Dec 14, 2011, 11:24:34 PM12/14/11
to cambridge...@googlegroups.com

Htmlplus sounds more like html editor product

-- Sent from my phone

Jeff Schnitzer

unread,
Dec 14, 2011, 11:29:19 PM12/14/11
to cambridge...@googlegroups.com
FWIW, my take is:

+1 on github
-1 on the name (sorry)

I don't hate it as much as Jon does, but... I don't think PG would approve :-)

http://messymatters.com/pgnames.html

That said, we'll keep using the software no matter what it's called.

Jeff

--
We are the 20%

Jon Stevens

unread,
Dec 14, 2011, 11:36:05 PM12/14/11
to cambridge...@googlegroups.com
This product renders more than just html email. We are using it to filter the txt body of an email (as well as the html body).

The code is amazing. The name is terrible.

jon

Erdinc Yilmazel

unread,
Dec 14, 2011, 11:40:20 PM12/14/11
to cambridge...@googlegroups.com
Hey, nothing is carved in stone yet! :) If you really don't like the name, I sure will re-think about it. It looks like I just am not good with naming things. I have been really thinking hard for quite a time but couldn't come up with anything good yet. There was the quick hawk suggestion that I remember now. Would everyone think that is a better name?

Thanks,

Erdinc

Jeff Schnitzer

unread,
Dec 15, 2011, 12:08:38 AM12/15/11
to cambridge...@googlegroups.com
Your interesting-sounding name seems to present some options. "Yilm
Templates" sounds cool and 'yilm' doesn't seem to have a significant
google presence. Or "Erd Templates", although googleability of 'erd'
is poor.

I don't think "Rapido" has been used in the context of a template language.

I rather like "Timpani", like the drum. Timpani Templates has nice
alliteration... kinda silly. I like silly.

Jeff

Gp P

unread,
Dec 15, 2011, 12:59:21 AM12/15/11
to cambridge...@googlegroups.com
+ for Timpani

Jon Stevens

unread,
Dec 15, 2011, 2:52:58 AM12/15/11
to cambridge...@googlegroups.com
+1 for Timpani!

jon

Tom Carchrae

unread,
Dec 15, 2011, 5:53:11 AM12/15/11
to cambridge...@googlegroups.com
I hate html+ as well. But I can see your rationale in the name. :)

Personally, I didn't mind Cambridge at all. I'm actually opposed to
changing it at all, but more in an indifferent sort of way. I must be
getting old.

That said, I think you'd do wonders if you changed the picture to not
show the other Cambridge. It adds confusion in a big way. What would
be more appropriate is just a nice short example of what cambridge is
(code) and why that is so awesome. I came for the code, not the
toffs. ;)

Tom

Jeff Schnitzer

unread,
Dec 15, 2011, 11:24:58 AM12/15/11
to cambridge...@googlegroups.com
FWIW, I'm pretty fine with Cambridge as well. Guess I've gotten used
to it. Googleability sucks but it's going to suck for most words we
come up with.

Jeff

Rakesh Waghela

unread,
Dec 15, 2011, 11:55:29 AM12/15/11
to cambridge...@googlegroups.com
+1 for "cambridge template engine" , I believe changing the name would rebrand the offering and will require more effort to get accustomed to the name etc.. !
We should be aware that Play ! community which by far seems the largest use group of Cambridge Template Engine , has gotten used to with the name and posibbly it would have been referred at many instances with same name all over the Internet where Play ! templating would have been discussed. ( frequently on  mailing list )!

Google search for "cambridge template engine" works well now ! I don't see any advantage in renaming it.

Erdinc Yilmazel

unread,
Dec 16, 2011, 12:16:07 AM12/16/11
to cambridge...@googlegroups.com
I guess best will be sticking with Cambridge name. Looking at the code now, renaming everything will require a lot of effort as well :) This name will never get the SEO juice that other names would get but I don't think that is really important. 

Still moving to git-hub though. I am debating if I should create a separate git-hub account for the project. I created the following repo but the url has my name in it:  https://github.com/erdincyilmazel/Cambridge. Cambridge username is taken on git-hub, but I can take something like cambridgetemplates ... Any thoughts?

Erdinc

Jeff Schnitzer

unread,
Dec 16, 2011, 12:34:00 AM12/16/11
to cambridge...@googlegroups.com
I suggest keeping it under your personal account. It's the github
way. Git makes it trivially easy to migrate the "official" repository
anywhere so it really doesn't matter.

That said, if I had a name that is hard to spell (which I do), I would
pick an alias for my personal account at github (which I did). Don't
name it after the project, however, because then you'll end up with a
zillion github accounts...

Jeff

--
We are the 20%

Reply all
Reply to author
Forward
0 new messages