The Great Renaming
Tom Boutell
stone. At first we thought we’d name it Context. As a result, we wound
up naming the plugin pkContextCMSPlugin.
Unfortunately, the name Context was not available. We eventually chose
Apostrophe, a name we’re very happy with.
However this has led to a lot of confusion for users who don’t realize
that Apostrophe and pkContextCMS are one and the same.
Meanwhile we also gave PHP and CSS classes long names, unnecessarily
long in retrospect, such as (deep breath) pkContextCMSRichTextSlot.
And as Apostrophe nears the end of its first year, we’re closing in on
a stable release of the CMS.
So we all looked at each other and said “if there are
hard-but-worthwhile changes we can make to improve this thing for
everyone, now would be the time. Because it’ll only be harder after a
stable release.”
So after giving the matter a great deal of thought, we’ve decided to
systematically rename the plugins, PHP classes, CSS classes, etc. that
make up Apostrophe.
Before you groan, let me assure you that we will NOT be doing this
abruptly to the svn paths you are currently relying on. And we WILL be
supplying you with the same upgrade script that we’ll be using to
upgrade our own projects to the new naming convention without pain.
Some frequently asked questions about this transition:
1. “Do I need to do anything now?”
No.
2. “Should I stop development and wait?”
No, definitely not. The more up to date you are with our current
trunk, the better the upgrade script will work for you.
3. “What version should I use right now?”
The 1.3 branch, or the trunk. That’s where our projects are, so it’s
where our upgrade script will be tested.
4. “Will the svn path of the project be changing?”
Yes. We are moving Apostrophe to our own trac so that we can provide
better bug tracking, manage project milestones, get accurate
statistics on downloads and so on. The upgrade script will take care
of pointing your svn externals to the new project path.
5. “Will the license change?”
Absolutely not. The MIT license will remain in place after this change.
6. “What will the new naming convention be, exactly?”
We haven’t completely finalized it, so I’m not going to spell out
examples here. But class names will be dramatically shorter. For
instance, we definitely won’t be requiring you to type ‘ContextCMS’
all over the place anymore. And no, we will NOT be requiring you to
type ‘Apostrophe’ all over the place either. Although it will
definitely appear in plugin names, it will not be spelled out fully in
CSS and PHP class names.
7. “What about this Google Group?”
We’ll likely rename that as well, or start a new group and encourage a
migration, just for clarity’s sake.
* * *
Even though the Apostrophe plugins have not yet had a stable release,
we want to acknowledge the support of the community represented by
this Google Group, and we want to make sure you are well-informed
about the coming changes.
This one-time inconvenience should help us all to create a larger
Apostrophe community by providing clear branding and preventing
confusion, as well as making development more convenient. Stick with
us, there are great things to come.
Thanks again for the support you’ve offered throughout the development
of Apostrophe!
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com
Daniel Lohse
The long-winded version: I'm watching pkContextCMS, er ;-), Apostrophe closely as it will be the basis for a big project coming up for me and I have to say, your way of handling these upgrade/update/BC break things is really good.
There, I said it, now get to work! :D
Thanks for all the hard work and a Happy New Year!
Daniel
> --
>
> You received this message because you are subscribed to the Google Groups "pkcontextcms" group.
> To post to this group, send email to pkcont...@googlegroups.com.
> To unsubscribe from this group, send email to pkcontextcms...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pkcontextcms?hl=en.
>
>
Geoff DiMasi
We are trying really hard to make this a simple process for everyone.
Geoff
--
Geoff DiMasi
P'unk Avenue
215 755 1330
Lambert
Sounds great! Before I start with the existing version, when do you
think the 'great-renaming' has finished with an updated svn-repos? (so
I can start wish the fresh version right away),
Thanks, Lambert
On Jan 5, 12:14 am, Geoff DiMasi <ge...@punkave.com> wrote:
> Thanks, Daniel.
>
> We are trying really hard to make this a simple process for everyone.
>
> Geoff
>
> --
> Geoff DiMasi
> P'unk Avenue
> 215 755 1330http://punkave.com
> >> For more options, visit this group athttp://groups.google.com/group/pkcontextcms?hl=en.
Tom Boutell
Please don't wait! You can use this time to get familiar with the
software, and our upgrade script will take care of the changes for
you. We haven't fixed a date certain for the transition yet.