apostrophenow.com vs apostrophenow.org

[Fotis Paraskevopoulos]

Hello,

Foreword - I couldn't be more thankful for the tools you provide, under an open source license, free
for me to use and build on.

Seeing the advances in the apostrophenow.com version of the CMS I am wondering how much of
that is making its way back to trunk? As community members and developers of the open source version
can we expect some of the new features to find their way to the open source version?

What is the current policy on this, just for future reference.

Best,
Fotis

PS- keep up the good work!

[Geoff DiMasi]

Hi Fotis,

At this point, we are using apostrophenow.com as a playground to try out new ideas. Some of the experiments will definitely make it back into the trunk. In fact, the photo grid slot has already been released. (Eagle-eye Robert Speer noticed on the day we released it.) I have been telling the team that we should make announcements to the list as we release these features and updates to the trunk/plugin. There have been a few.

Basically, many things that fit within the overall mission of the plugin will make it back. As an example, we are going to continue to iterate on the batch photo/file uploader. I can see that getting released in the near future.

Also, lots of these ideas will make it into Apostrophe2.

______

On another note, we hope the Apostrophe community can make use of the apostrophenow.com. We have already started building sites for clients that don't need extended functionality on it. There is no reason that a local dance company needs a site on the plugin. They can get all of the functionality of Apostrophe and we can focus on their design and template creation. Some other design/devs are doing this as well for clients. It has the potential to be a great revenue stream for you.

Hope this helps.

Geoff

[Tom Boutell]

One point of order: the trunks of apostrophePlugin and
apostropheBlogPlugin are dead, dead, dead and contain warning files
saying so (: Anything new goes in the 1.5 branch (and we minimize
changes there, as much as possible). Just making sure everyone
understands this.

Some of the less officially stabilized plugins do have an active trunk
in svn though (these generally have no branches, so there's little
confusion in practice).

--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com

[Geoff DiMasi]

What he said!

[Fotis Paraskevopoulos]

Good Morning All,

Thank you for your replies, it reasures what I thought was the case.

@Tom: Sorry I meant the 1.5 branch

@Geoff: We are looking to take advantage of apostrophenow.com, havent gotten a good use case for this
yet, but I will make sure to post once we are able to get someone.

Best,
Fotis

[Carsten Rose Lundberg]

I have to say I'm a bit puzzled by this strategy/approach.

So the version you make people pay for (very little I know) is the
playground where you experiment? An experimental playground as the
description of a CMS hosting service does not resonate very well with
any client I can think of.

Secondly apostrophenow.com is for clients that does not need extended
functionality meaning I guess smaller less important clients yet it
has features that are not in the 1.5 branch. This puts me in a
situation where I can start off by showing a potential client
apostrophenow.com but if they need extended functionality I would have
to degrade their editor experience - e.g. no preview button and no
drag'n'image upload. Again I wouldn't know how to explain let alone
sell that to a client - how do you on your projects?

I'm completely aware that the plugin is open source and free but as
all other open source projects I'd argue that it thrives on the
community and it's following. I might be seeing this wrong but it
seems to me that apostrophenow.com gets the bigger chunk of pk love
and that means getting web designer and not programmer love back.

I'm not saying I have the solution or what you're doing is wrong. I
telling it as I see it from my end and I look forward to getting your
perspective. Please remember that if I had no love for apostrophe I
would write this :)

On Feb 1, 12:20 am, Geoff DiMasi <ge...@punkave.com> wrote:
> Hi Fotis,
>

> At this point, we are usingapostrophenow.comas a playground to try out new ideas. Some of the experiments will definitely make it back into the trunk. In fact, the photo grid slot has already been released. (Eagle-eye Robert Speer noticed on the day we released it.) I have been telling the team that we should make announcements to the list as we release these features and updates to the trunk/plugin. There have been a few.

>
> Basically, many things that fit within the overall mission of the plugin will make it back. As an example, we are going to continue to iterate on the batch photo/file uploader. I can see that getting released in the near future.
>
> Also, lots of these ideas will make it into Apostrophe2.
>
> ______
>

> On another note, we hope the Apostrophe community can make use of theapostrophenow.com. We have already started building sites for clients that don't need extended functionality on it. There is no reason that a local dance company needs a site on the plugin. They can get all of the functionality of Apostrophe and we can focus on their design and template creation. Some other design/devs are doing this as well for clients. It has the potential to be a great revenue stream for you.

>
> Hope this helps.
>
> Geoff
>
> On Jan 31, 2012, at 5:03 PM, Fotis Paraskevopoulos wrote:
>
>
>
>
>
>
>
> > Hello,
>
> > Foreword - I couldn't be more thankful for the tools you provide, under an open source license, free
> > for me to use and build on.
>

> > Seeing the advances in theapostrophenow.comversion of the CMS I am wondering how much of

[Tom Boutell]

Carsten, some of the features you mention are well-tested for the
feature set we deliver on apostrophenow.com but not necessarily ready
to support for the full range of things people can and should be able
to do with open source Apostrophe. Our frontend team is already
chomping at the bit to replace our drag and drop uploader with a
better one.

We also needed time to work on a strategy for releasing new features
without infuriating the other half of our open source users, the ones
who are sick of changes to apostrophePlugin 1.5 and accompanying bugs
and bc breaks.

We'll probably release additional plugins that override parts of
apostrophePlugin when desired. You're not wrong that this will help
with our own quality control.

But don't forget we're turning our attention to Apostrophe 2. so we
really don't want to go down the Apostrophe 1.6 road any more than our
projects demand.

That said, we've already open sourced tons of
apostrophenow.com-related tech (pkLockServer and aS3StreamWrapper and
the Apostrophe changes that allow Apostrophe to use them come
immediately to mind) and will open source more.

--

[Carsten Rose Lundberg]

Thanks answering so fast Tom. I have to compliment you for doing a
great job of keeping the community in the loop.

I know about Apostrophe 2 and completely understand that 1.6 is not a
priority. Also I realize that there is indeed a flow of features
originating on apostrophenow.com into the 1.5 branch.

I also understand the problems relating to the constant flow of
updates to the 1.5 branch. Knowing that I'm not in your shoes could a
suggestion to a release strategy be to provide a "technology preview"
branch with the most current version of apostrophenow.com? - not the
account management part I realize that. That would allow us to cherry
pick functionality by ourselves and it wouldn't break the 1.5 branch.

On Feb 2, 9:43 pm, Tom Boutell <t...@punkave.com> wrote:
> Carsten, some of the features you mention are well-tested for the

> feature set we deliver onapostrophenow.combut not necessarily ready

> to support for the full range of things people can and should be able
> to do with open source Apostrophe. Our frontend team is already
> chomping at the bit to replace our drag and drop uploader with a
> better one.
>
> We also needed time to work on a strategy for releasing new features
> without infuriating the other half of our open source users, the ones
> who are sick of changes to apostrophePlugin 1.5 and accompanying bugs
> and bc breaks.
>
> We'll probably release additional plugins that override parts of
> apostrophePlugin when desired. You're not wrong that this will help
> with our own quality control.
>
> But don't forget we're turning our attention to Apostrophe 2. so we
> really don't want to go down the Apostrophe 1.6 road any more than our
> projects demand.
>

> That said, we've already open sourced tons ofapostrophenow.com-related tech (pkLockServer and aS3StreamWrapper and

> the Apostrophe changes that allow Apostrophe to use them come
> immediately to mind) and will open source more.
>
> On Thu, Feb 2, 2012 at 3:29 PM, Carsten Rose Lundberg
>
>
>
>
>
>
>
>
>
> <advert...@gmail.com> wrote:
> > I have to say I'm a bit puzzled by this strategy/approach.
>
> > So the version you make people pay for (very little I know) is the
> > playground where you experiment? An experimental playground as the
> > description of a CMS hosting service does not resonate very well with
> > any client I can think of.
>

> > Secondlyapostrophenow.comis for clients that does not need extended

> > functionality meaning I guess smaller less important clients yet it
> > has features that are not in the 1.5 branch. This puts me in a
> > situation where I can start off by showing a potential client

> >apostrophenow.combut if they need extended functionality I would have

> > to degrade their editor experience - e.g. no preview button and no
> > drag'n'image upload. Again I wouldn't know how to explain let alone
> > sell that to a client - how do you on your projects?
>
> > I'm completely aware that the plugin is open source and free but as
> > all other open source projects I'd argue that it thrives on the
> > community and it's following. I might be seeing this wrong but it

> > seems to me thatapostrophenow.comgets the bigger chunk of pk love

[Geoff DiMasi]

Hey Carsten,

To reiterate what Tom said, it is likely that features like preview and batch upload should be making it back to the plugin if they won't break things. I know that some clients are asking for preview, so we should be able to leverage that effort back into the plugin.

___________

If you are planning on building a client website in the plugin, I would demo another site you built in the plugin or use the plugin's demo:

http://demo.apostrophenow.org/

That will allow you to demo the complete feature set including the much more robust users/permissions.

___________

By the way, one of the best ways to accelerate development on Apostrophe 1.5 and 2 is to sign some customers up for the hosted version! :)

That will buy us more time to invest directly in the plugin.

[Giles Smith]

I second seeing the preview functionality in the plugin, we have several clients wanting to see this functionality too, and one new one who requires it :)

[Tom Boutell]

FYI, the preview functionality is now available in the plugin.

For maximum backwards compatibility, you must set app_a_preview_toggle
to true to enable this. You must also add jquery.cookie.js to
view.yml, see view.yml in the sandbox.

If you don't expressly enable this, nothing changes.

In the sandbox i squeezed the admin bar down a bit and removed the
label from the preview toggle for space reasons, however in most
production sites you won't have every possible feature enabled at once
up there (or you'll be rolling some custom dropdown menus to
accommodate it).

--

[Giles Smith]

Tom, amazing, thanks!

[Tom Boutell]

You're welcome (: