Confluence
  1. Confluence
  2. CONF-12001

include Calendar plugin as supported plugin

    Details

    • Last commented by user?:
      true
    • Support reference count:
      13

      Description

      The Calendar plugin is one of Confluence's most popular plugins.

      Atlassian Status as of 10/11/2010

      Hi All,
      Thank you for your patience with this plugin. We are currently looking Calendaring in Confluence and have been researching possible solutions for improving the Calendaring experience in the product.

      If you are interested in participating in some customer feedback, surveys or early access to some prototypes for Calendering please email me (smansour at atlassian dot com) so I can add you to our feedback list. Alternatively, continue to watch this issue and we will update it as we make further progress.

      The existing calendar plugin is known to work in Confluence 3.3/3.4, even though it isn't formally supported. As always, we recommend you test the plugin before using it in a production environment.

      Cheers,
      Sherif Mansour
      Confluence Product Manager

        Issue Links

          Activity

          Hide
          Igor Minar added a comment - - edited

          We had many requests for this plugin to be installed on wikis.sun.com. I refused them all because when I looked at the source code of the plugin I found several issues that I considered to be troublesome.

          I don't recall details right now (it's been a while), but I remember that there was an issue with having multiple calendar instances in one space, which was caused by a questionable implementation of the persistance layer of that plugin.

          We'd love to have a plugin like this on wikis.sun.com, but we'd like it to be a quality product that we as well as Atlassian wouldn't have too much trouble supporting.

          Show
          Igor Minar added a comment - - edited We had many requests for this plugin to be installed on wikis.sun.com. I refused them all because when I looked at the source code of the plugin I found several issues that I considered to be troublesome. I don't recall details right now (it's been a while), but I remember that there was an issue with having multiple calendar instances in one space, which was caused by a questionable implementation of the persistance layer of that plugin. We'd love to have a plugin like this on wikis.sun.com, but we'd like it to be a quality product that we as well as Atlassian wouldn't have too much trouble supporting.
          Hide
          Don Gamble added a comment -

          Our business users continue to want this functionality, but as an unsupported plugin it is a tough call to include it. We are currently trying to get to Confluence 3.1 and this plugin is marked as unsupported. This is becoming a significant issue as it is a conflict between business value and stability.

          Show
          Don Gamble added a comment - Our business users continue to want this functionality, but as an unsupported plugin it is a tough call to include it. We are currently trying to get to Confluence 3.1 and this plugin is marked as unsupported. This is becoming a significant issue as it is a conflict between business value and stability.
          Hide
          David Grierson added a comment -

          The lack of support for this plugin is a major issue for our organisation as well.

          We've already voted on this issue - however nothing seems to have moved on this in the 2 years its been open.

          Show
          David Grierson added a comment - The lack of support for this plugin is a major issue for our organisation as well. We've already voted on this issue - however nothing seems to have moved on this in the 2 years its been open.
          Hide
          Leila Tite added a comment -

          Our users love this plugin. Lack of support for Confluence 3.3 is going to be a showstopper for us to upgrade.

          Show
          Leila Tite added a comment - Our users love this plugin. Lack of support for Confluence 3.3 is going to be a showstopper for us to upgrade.
          Hide
          Sebastian Schmitz added a comment -

          Hi,
          is there a timeframe as to when supported Calendaring will be available in Confluence or when -for the time being - the Calendar Plugin will work with Confluence 3.3?
          Thanks for any response!

          Show
          Sebastian Schmitz added a comment - Hi, is there a timeframe as to when supported Calendaring will be available in Confluence or when -for the time being - the Calendar Plugin will work with Confluence 3.3? Thanks for any response!
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Hi Sebastian,
          We don't plan on supporting the existing plugin for Confluence. As the issue description says, we are looking at a new Calendaring solution, but don't have any rough dates at this stage.
          The existing Calendar plugin, however does work in Confluence 3.3, 3.4 - even though it is not formally supported.
          Sherif

          Show
          Sherif Mansour [Atlassian] added a comment - Hi Sebastian, We don't plan on supporting the existing plugin for Confluence. As the issue description says, we are looking at a new Calendaring solution, but don't have any rough dates at this stage. The existing Calendar plugin, however does work in Confluence 3.3, 3.4 - even though it is not formally supported. Sherif
          Hide
          Sebastian Schmitz added a comment -

          Thanks for your answer Sherif,
          however, on https://plugins.atlassian.com/plugin/details/153 it says there is neither compatibility with 3.3. nor 3.4.
          Additionally, I do not see the Calendar Plugin in the plugin repository of my Confluence instance.
          Would you recommend installing it from file?

          Best Regards
          Sebastian

          Show
          Sebastian Schmitz added a comment - Thanks for your answer Sherif, however, on https://plugins.atlassian.com/plugin/details/153 it says there is neither compatibility with 3.3. nor 3.4. Additionally, I do not see the Calendar Plugin in the plugin repository of my Confluence instance. Would you recommend installing it from file? Best Regards Sebastian
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Updated the status to reflect your comment.

          Show
          Sherif Mansour [Atlassian] added a comment - Updated the status to reflect your comment.
          Hide
          Royce Wong added a comment -

          Is Calendar plugin 3.0 available soon? I see the issue with Can't use Calendar in a Cluster has been resolved.

          References:
          https://plugins.atlassian.com/plugin/details/153
          https://studio.plugins.atlassian.com/wiki/display/CAL/Confluence+Calendar+Plugin

          Any updates?

          Show
          Royce Wong added a comment - Is Calendar plugin 3.0 available soon? I see the issue with Can't use Calendar in a Cluster has been resolved. References: https://plugins.atlassian.com/plugin/details/153 https://studio.plugins.atlassian.com/wiki/display/CAL/Confluence+Calendar+Plugin Any updates?
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Hi Royce,
          We are working on a new Calendar plugin (which does work in Clustered). We don't have a date for it at this stage other than the second half of this year. Please be assured, I will update this issue once we have made further progress.
          Sherif

          Show
          Sherif Mansour [Atlassian] added a comment - Hi Royce, We are working on a new Calendar plugin (which does work in Clustered). We don't have a date for it at this stage other than the second half of this year. Please be assured, I will update this issue once we have made further progress. Sherif
          Hide
          Alexander Seith added a comment -

          Hi,

          will the new Calendar Plugin support CalDAV or any other method to include remote calendars, e.g. Zimbra's calendar feature? That would be awesome.

          Best Regards

          Alex

          Show
          Alexander Seith added a comment - Hi, will the new Calendar Plugin support CalDAV or any other method to include remote calendars, e.g. Zimbra's calendar feature? That would be awesome. Best Regards Alex
          Hide
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment -

          +1 for Zimbra Support.

          Show
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment - +1 for Zimbra Support.
          Hide
          Brant Levinson added a comment -

          We would like to include a calendar plugin in our confluence solution we are building. We can't get source access to the current calendar plugin as you guys have restricted permissions to it. Could you please update us on what the status is of having a supported (with source) calendar plugin asap?

          Show
          Brant Levinson added a comment - We would like to include a calendar plugin in our confluence solution we are building. We can't get source access to the current calendar plugin as you guys have restricted permissions to it. Could you please update us on what the status is of having a supported (with source) calendar plugin asap?
          Hide
          Adam Durst added a comment -

          Update please.

          What is going on? The current version isn't compatible with 3.5...preventing us from upgrading.

          We are lined up to do a major upgrade...but this plugin is holding everything up!

          Will this new plugin be released in the near future?

          Or is it being built for 4.0?

          Calendar has become a critical component of our system and between the issues with the existing plugin and the lack of compatability with 3.5...I'm having more headaches then I should! Atlassian needs to manage the communities expecations on issues such as this one better...Just tell us what the plan is...please don't leave us in the dark.

          Show
          Adam Durst added a comment - Update please. What is going on? The current version isn't compatible with 3.5...preventing us from upgrading. We are lined up to do a major upgrade...but this plugin is holding everything up! Will this new plugin be released in the near future? Or is it being built for 4.0? Calendar has become a critical component of our system and between the issues with the existing plugin and the lack of compatability with 3.5...I'm having more headaches then I should! Atlassian needs to manage the communities expecations on issues such as this one better...Just tell us what the plan is...please don't leave us in the dark.
          Hide
          Andrew Barnes added a comment -

          Here's an screenshot example of what we'd like to see from a prospective new Calendar plugin:

          • iCal/ics support
          • Alternate/Customizable layouts
          • WebDAV/remote calendar support (Zimbra)
          • Ability to provide iCal/ics files for individual appointments in the calendar
          • Store a list of email(s), in order to mail iCal/ics appointment suggestions
          • RSS support
          Show
          Andrew Barnes added a comment - Here's an screenshot example of what we'd like to see from a prospective new Calendar plugin: iCal/ics support Alternate/Customizable layouts WebDAV/remote calendar support (Zimbra) Ability to provide iCal/ics files for individual appointments in the calendar Store a list of email(s), in order to mail iCal/ics appointment suggestions RSS support
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Hi Guys,
          I don't have any further updates than the update already provided. I can tell you that we are making progress with our prototype and looking for people to provide feedback that are running Confluence 3.5.x and (or) JIRA 4.3.x. So if you are interested, please email me (smansour at atlassian dot com).

          Trying to answer some of your questions:

          We can't get source access to the current calendar plugin as you guys have restricted permissions to it.

          As we have come to build a new calendar plugin we have realised that in order for us to support this moving forward we will charge for this plugin (the cost is yet to be determined). I've been speaking to a lot of customers about this plugin and many are more than happy to pay to get this plugin supported and furthermore, get features they would like to see into the plugin.

          Will this new plugin be released in the near future?

          We are targeting the second half of this year.

          Or is it being built for 4.0?

          The plugin will support Confluence 3.5.x and Confluence 4.x and above. At this stage the new plugin is not scoped to support anything less than 3.5.x, sorry about that. I'll update this issue if it is.

          Thanks for your patience. Hope this answers some of your questions. I will update this issue when we make further progress.
          Sherif

          Show
          Sherif Mansour [Atlassian] added a comment - Hi Guys, I don't have any further updates than the update already provided. I can tell you that we are making progress with our prototype and looking for people to provide feedback that are running Confluence 3.5.x and (or) JIRA 4.3.x. So if you are interested, please email me (smansour at atlassian dot com). Trying to answer some of your questions: We can't get source access to the current calendar plugin as you guys have restricted permissions to it. As we have come to build a new calendar plugin we have realised that in order for us to support this moving forward we will charge for this plugin (the cost is yet to be determined). I've been speaking to a lot of customers about this plugin and many are more than happy to pay to get this plugin supported and furthermore, get features they would like to see into the plugin. Will this new plugin be released in the near future? We are targeting the second half of this year. Or is it being built for 4.0? The plugin will support Confluence 3.5.x and Confluence 4.x and above. At this stage the new plugin is not scoped to support anything less than 3.5.x, sorry about that. I'll update this issue if it is. Thanks for your patience. Hope this answers some of your questions. I will update this issue when we make further progress. Sherif
          Hide
          Daniel Siegmann added a comment -

          Hi Sherif,

          As we have come to build a new calendar plugin we have realised that in order for us to support this moving forward we will charge for this plugin (the cost is yet to be determined). I've been speaking to a lot of customers about this plugin and many are more than happy to pay to get this plugin supported and furthermore, get features they would like to see into the plugin.

          The existing Calendar plugin is fine for us, we just wanted it to continue to function as-is for the latest version of Confluence. Having to pay for a plugin is a big barrier to our using it. It is always disappointing when suddenly we must pay for functionality we previously received for free. It also makes a simple upgrade of Confluence into a major headache.

          Show
          Daniel Siegmann added a comment - Hi Sherif, As we have come to build a new calendar plugin we have realised that in order for us to support this moving forward we will charge for this plugin (the cost is yet to be determined). I've been speaking to a lot of customers about this plugin and many are more than happy to pay to get this plugin supported and furthermore, get features they would like to see into the plugin. The existing Calendar plugin is fine for us, we just wanted it to continue to function as-is for the latest version of Confluence. Having to pay for a plugin is a big barrier to our using it. It is always disappointing when suddenly we must pay for functionality we previously received for free. It also makes a simple upgrade of Confluence into a major headache.
          Hide
          M. Martín added a comment -

          I agree with Daniel.

          The existing Calendar plugin is fine for us, we just wanted it to continue to function as-is for the latest version of Confluence. Having to pay for a plugin is a big barrier to our using it. It is always disappointing when suddenly we must pay for functionality we previously received for free. It also makes a simple upgrade of Confluence into a major headache.

          Show
          M. Martín added a comment - I agree with Daniel. The existing Calendar plugin is fine for us, we just wanted it to continue to function as-is for the latest version of Confluence. Having to pay for a plugin is a big barrier to our using it. It is always disappointing when suddenly we must pay for functionality we previously received for free. It also makes a simple upgrade of Confluence into a major headache.
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Daniel and Martin,
          Thanks for the feedback.

          It is always disappointing when suddenly we must pay for functionality we previously received for free.

          Being as open and honest with you guys, this was one of our concerns when building this plugin. I personally spoke to many customers about this with similar concerns. Without a doubt, the constant feedback I always heard was if it meant the plugin would be maintained and we would build requested features out - customers were more than happy to support this.

          One of the primary drivers for us charging for this plugin is on-going maintenance. The existing plugin has become the way it is because building and maintaining a calendar solution isn't easy. So much so, that a complete re-write was required to maintain this plugin. It evolved as a small open-source plugin a few developers built on the side to something that customers wanted to use extensively and wanted more features put into it. Additionally, it's always been hard to balance our maintenance effort across the hundreds of features and bundled plugins Confluence already has. Charging for this plugin will, in turn, mean we will have resources dedicated to continually build out requested features and maintain the plugin moving forward. There are many requested features for the calendar plugin that we want to start working on and delivering for our customers.

          Regarding the upgrades: "It also makes a simple upgrade of Confluence into a major headache.": The process for upgrading the new plugin will not change. It will happen through the plugin manager that is in Confluence - so no additional headaches there.

          Feel free to shoot me an email, I'd love to have a more detailed chat to you about it.
          Sherif

          Show
          Sherif Mansour [Atlassian] added a comment - Daniel and Martin, Thanks for the feedback. It is always disappointing when suddenly we must pay for functionality we previously received for free. Being as open and honest with you guys, this was one of our concerns when building this plugin. I personally spoke to many customers about this with similar concerns. Without a doubt, the constant feedback I always heard was if it meant the plugin would be maintained and we would build requested features out - customers were more than happy to support this. One of the primary drivers for us charging for this plugin is on-going maintenance. The existing plugin has become the way it is because building and maintaining a calendar solution isn't easy. So much so, that a complete re-write was required to maintain this plugin. It evolved as a small open-source plugin a few developers built on the side to something that customers wanted to use extensively and wanted more features put into it. Additionally, it's always been hard to balance our maintenance effort across the hundreds of features and bundled plugins Confluence already has. Charging for this plugin will, in turn, mean we will have resources dedicated to continually build out requested features and maintain the plugin moving forward. There are many requested features for the calendar plugin that we want to start working on and delivering for our customers. Regarding the upgrades: " It also makes a simple upgrade of Confluence into a major headache. ": The process for upgrading the new plugin will not change. It will happen through the plugin manager that is in Confluence - so no additional headaches there. Feel free to shoot me an email, I'd love to have a more detailed chat to you about it. Sherif
          Hide
          Guenther Sommer added a comment -

          Also for me the missing calendar for 3.5 is a major downside. The status of an installation is that I can either downgrade to 3.4 or wait for a 4.0 release. Just missing it for 3.5 makes the 3.5 release quite unusable.

          I'm happy for the way you want to implement it in future, still I'd like to have a quick (and also dirty) solution for 3.5 (a last chance for the old plugin to update?).

          Br, Günther.

          Show
          Guenther Sommer added a comment - Also for me the missing calendar for 3.5 is a major downside. The status of an installation is that I can either downgrade to 3.4 or wait for a 4.0 release. Just missing it for 3.5 makes the 3.5 release quite unusable. I'm happy for the way you want to implement it in future, still I'd like to have a quick (and also dirty) solution for 3.5 (a last chance for the old plugin to update?). Br, Günther.
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Guenther, I may not have been clear with my comment above:

          ...The plugin will support Confluence 3.5.x and Confluence 4.x and above.

          This does include 3.5.0, 3.5.1, 3.5.2 and so on... Sorry if that was confusing.

          Show
          Sherif Mansour [Atlassian] added a comment - Guenther, I may not have been clear with my comment above: ...The plugin will support Confluence 3.5.x and Confluence 4.x and above. This does include 3.5.0, 3.5.1, 3.5.2 and so on... Sorry if that was confusing.
          Hide
          Guenther Sommer added a comment -

          Yes, understood, but currently there is no calendar, because old one doesn't work and the new one will still take some months to come...

          Show
          Guenther Sommer added a comment - Yes, understood, but currently there is no calendar, because old one doesn't work and the new one will still take some months to come...
          Hide
          Daniel Siegmann added a comment -

          Sherif, thanks for the response. I'll shoot you an email so we can discuss in more detail, but I want to make a couple quick points here.

          Without a doubt, the constant feedback I always heard was if it meant the plugin would be maintained and we would build requested features out - customers were more than happy to support this.

          I think you are dealing with two separate sets of customers here. There are those who want robust calendar functionality and will gladly pay for such a solution, and there are those (such as myself) who are satisfied with the existing plugin exactly as it is and want it to continue functioning with new Confluence versions.

          Regarding the upgrades: "It also makes a simple upgrade of Confluence into a major headache.": The process for upgrading the new plugin will not change. It will happen through the plugin manager that is in Confluence - so no additional headaches there.

          It's not a technical issue, but a business issue. I must now discuss with our users whether we need this plugin and see if I can justify to my boss the cost of purchasing this plugin. If not, I need to figure out a migration path.

          At least it would be appreciated if you could make the existing plugin compatible with Confluence 3.5. As Guenther noted this blocks upgrading.

          Show
          Daniel Siegmann added a comment - Sherif, thanks for the response. I'll shoot you an email so we can discuss in more detail, but I want to make a couple quick points here. Without a doubt, the constant feedback I always heard was if it meant the plugin would be maintained and we would build requested features out - customers were more than happy to support this. I think you are dealing with two separate sets of customers here. There are those who want robust calendar functionality and will gladly pay for such a solution, and there are those (such as myself) who are satisfied with the existing plugin exactly as it is and want it to continue functioning with new Confluence versions. Regarding the upgrades: "It also makes a simple upgrade of Confluence into a major headache.": The process for upgrading the new plugin will not change. It will happen through the plugin manager that is in Confluence - so no additional headaches there. It's not a technical issue, but a business issue. I must now discuss with our users whether we need this plugin and see if I can justify to my boss the cost of purchasing this plugin. If not, I need to figure out a migration path. At least it would be appreciated if you could make the existing plugin compatible with Confluence 3.5. As Guenther noted this blocks upgrading.
          Hide
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment -

          In the company I work for we strongly believe that there is no such thing as a free lunch. See http://en.wikipedia.org/wiki/There_ain't_no_such_thing_as_a_free_lunch for more info on that.

          Regarding this discussion here: As an Atlassian Partner we often deal with crappy plugins and features, that once worked nicely and now are abandoned. It is not to be taken for granted, that plugins work in new versions. That maintenance comes with a cost.

          I am glad, that Atlassian now puts a price tag on this maintenance and makes sure, that the calendar plugin rocks. That's at least what I expect them to do.

          In my opinion, that is way better than trying to maintain a free version that won't do the trick in the long run.

          Show
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment - In the company I work for we strongly believe that there is no such thing as a free lunch. See http://en.wikipedia.org/wiki/There_ain't_no_such_thing_as_a_free_lunch for more info on that. Regarding this discussion here: As an Atlassian Partner we often deal with crappy plugins and features, that once worked nicely and now are abandoned. It is not to be taken for granted, that plugins work in new versions. That maintenance comes with a cost. I am glad, that Atlassian now puts a price tag on this maintenance and makes sure, that the calendar plugin rocks. That's at least what I expect them to do. In my opinion, that is way better than trying to maintain a free version that won't do the trick in the long run.
          Hide
          Andrew Barnes added a comment - - edited

          Adaptavist seems to be doing fine, providing free plugins and support forum while charging for dedicated support.

          Locking the deprecated source, lacking support for a major version release and the proposed move to a for-pay model for an unspecified release (no beta in sight) is... unsettling.

          Calendar viewing is a desired feature, but is not mission critical at this time - internal users can easily view and overlay shared calendars in Zimbra/Google Calendar/Outlook/etc. I'm glad to see an update to what is happening, and will have to pass the information on to see if management is interested in paying or willing to invest in a custom plugin/macro in light of the prospective time until release. Has the for-pay approach been determined - per version (IE 3.5.x, 4.x, etc) or to coincide with the Confluence license?

          Show
          Andrew Barnes added a comment - - edited Adaptavist seems to be doing fine, providing free plugins and support forum while charging for dedicated support. Locking the deprecated source, lacking support for a major version release and the proposed move to a for-pay model for an unspecified release (no beta in sight) is... unsettling. Calendar viewing is a desired feature, but is not mission critical at this time - internal users can easily view and overlay shared calendars in Zimbra/Google Calendar/Outlook/etc. I'm glad to see an update to what is happening, and will have to pass the information on to see if management is interested in paying or willing to invest in a custom plugin/macro in light of the prospective time until release. Has the for-pay approach been determined - per version (IE 3.5.x, 4.x, etc) or to coincide with the Confluence license?
          Hide
          Adam Durst added a comment -

          My concern is that this is a precendent setting move...what was a fixed/known cost for Confluence and the improvments and new features Atlassian developed...will change forever.

          How do I know that every new feature in the future isn't going to cost me more. New features wouldn't need to be added to the core...sell them seperate!

          This is a major change in the revenue/business model by which confluence is developed by Atlassian...and will certainly make me re-evaluate the platform.

          This isn't another company making a plugin and it isn't the historical practice of Atlassian.

          I don't have a problem paying to ensure the feture remains up to date...but strongly believe this should be incorporated into the core of Confluence.

          My belief is that all of Atlassians plug-in should be part of the core (which can be turned-off or on depending on the desired use of Confluence).

          In this model Atlassian should just recognise that their product has advanced significantly to require a small adjustment in licencing and maintinence costs, which would cover the development time.

          Show
          Adam Durst added a comment - My concern is that this is a precendent setting move...what was a fixed/known cost for Confluence and the improvments and new features Atlassian developed...will change forever. How do I know that every new feature in the future isn't going to cost me more. New features wouldn't need to be added to the core...sell them seperate! This is a major change in the revenue/business model by which confluence is developed by Atlassian...and will certainly make me re-evaluate the platform. This isn't another company making a plugin and it isn't the historical practice of Atlassian. I don't have a problem paying to ensure the feture remains up to date...but strongly believe this should be incorporated into the core of Confluence. My belief is that all of Atlassians plug-in should be part of the core (which can be turned-off or on depending on the desired use of Confluence). In this model Atlassian should just recognise that their product has advanced significantly to require a small adjustment in licencing and maintinence costs, which would cover the development time.
          Hide
          Dave Thomas added a comment -

          My belief is that all of Atlassians plug-in should be part of the core (which can be turned-off or on depending on the desired use of Confluence).

          I don't think I quite agree with that. In this case, there seems to be a plugin that's expensive to develop and maintain that's only desired by relatively small percentage of users. For the users that want it, the plugin is deemed critical functionality. But why should the rest of us have to pay for something we don't really need? In this case, I think breaking it out as a separate paid plugin makes sense.

          Show
          Dave Thomas added a comment - My belief is that all of Atlassians plug-in should be part of the core (which can be turned-off or on depending on the desired use of Confluence). I don't think I quite agree with that. In this case, there seems to be a plugin that's expensive to develop and maintain that's only desired by relatively small percentage of users. For the users that want it, the plugin is deemed critical functionality. But why should the rest of us have to pay for something we don't really need? In this case, I think breaking it out as a separate paid plugin makes sense.
          Hide
          Guenther Sommer added a comment -

          To pay or not to pay for the calendar is "currently" a minor issue for me.

          The major problem is, that for 3.5 there is no calendar solution at all, either paid or unpaid.

          Br, Günther.

          Show
          Guenther Sommer added a comment - To pay or not to pay for the calendar is "currently" a minor issue for me. The major problem is, that for 3.5 there is no calendar solution at all, either paid or unpaid. Br, Günther.
          Hide
          Semir Hasanbegovic added a comment -

          Even though the old calendar plugin is not supported, I have it running under Confluence 3.5.2 and it seems to work fine. If your policies are not stopping you from running unsupported plugins then give it a shot to see if it works for you.

          Semir

          Show
          Semir Hasanbegovic added a comment - Even though the old calendar plugin is not supported, I have it running under Confluence 3.5.2 and it seems to work fine. If your policies are not stopping you from running unsupported plugins then give it a shot to see if it works for you. Semir
          Hide
          Guenther Sommer added a comment -

          Ive tried it with 3.5.2 (running on linux & mysql) and I get an exception...

          Show
          Guenther Sommer added a comment - Ive tried it with 3.5.2 (running on linux & mysql) and I get an exception...
          Hide
          Andrew Barnes added a comment -

          I'm running 3.5.2 in our Development environment (RHEL 5, Tomcat 6.0.29, SQL Server 2005) - the old Calendar Plugin seems to work for me. The plugin isn't disabled, and my test page renders a Zimbra calendar without complaints.

          I'll be testing the new plugin later today.

          Show
          Andrew Barnes added a comment - I'm running 3.5.2 in our Development environment (RHEL 5, Tomcat 6.0.29, SQL Server 2005) - the old Calendar Plugin seems to work for me. The plugin isn't disabled, and my test page renders a Zimbra calendar without complaints. I'll be testing the new plugin later today.
          Hide
          Steffen Heinz added a comment -

          I also like to raise my voice and concerns here. For practical purposes, we require a calendar functionality to allow collaboration within a team. Loosing the existing (limited) cal functionality gives me a bit of a headache to move from 3.4.7 to 3.5.2.

          I can see Atlassian's point that implementing the calendar functionality requires more resources than available and hence the need to get more funding via additional charges. For us, we would be ok to pay a small amount to get an improved cal functionality, However, I also dislike the idea to pay for items deemed standard before and now being touted as "extra". This is not good practice in my opinion.

          However, speed up a bit, folks! You need to provide choices to your customers here!

          There have been discussions on the calendar functionality since ages and not much is coming out of your development pipeline. This is the real issue for me.

          Thanks!

          Cheers, Steffen

          Show
          Steffen Heinz added a comment - I also like to raise my voice and concerns here. For practical purposes, we require a calendar functionality to allow collaboration within a team. Loosing the existing (limited) cal functionality gives me a bit of a headache to move from 3.4.7 to 3.5.2. I can see Atlassian's point that implementing the calendar functionality requires more resources than available and hence the need to get more funding via additional charges. For us, we would be ok to pay a small amount to get an improved cal functionality, However, I also dislike the idea to pay for items deemed standard before and now being touted as "extra". This is not good practice in my opinion. However, speed up a bit, folks! You need to provide choices to your customers here! There have been discussions on the calendar functionality since ages and not much is coming out of your development pipeline. This is the real issue for me. Thanks! Cheers, Steffen
          Hide
          John Price added a comment -

          I stumbled upon this while testing my 3.3-3.5 upgrade. Is the consensus that the old plugin won't work at all on 3.5? If so this means we need to freeze on 3.3 until this is resolved. Several teams make extensive use of calendars, It's worked fine for years. Does anyone have a workaround? I seem to have it running with a manual install but I don't see my old calendar data. More info would be great.

          Show
          John Price added a comment - I stumbled upon this while testing my 3.3-3.5 upgrade. Is the consensus that the old plugin won't work at all on 3.5? If so this means we need to freeze on 3.3 until this is resolved. Several teams make extensive use of calendars, It's worked fine for years. Does anyone have a workaround? I seem to have it running with a manual install but I don't see my old calendar data. More info would be great.
          Hide
          greg mcmillan added a comment -

          Please get the Calendar Plugin to work with 3.5 as soon as possible. We'll gladly pay for it here at LinkedIn's IT support team.

          Show
          greg mcmillan added a comment - Please get the Calendar Plugin to work with 3.5 as soon as possible. We'll gladly pay for it here at LinkedIn's IT support team.
          Hide
          John Price added a comment -

          Update from me - I upgraded from 3.3 to 3.5 and the calendars seem ok. In my test upgrade they seemed to lose data but I figured out how to restore it at the SQL level from a backup, then felt good enough to try the production upgrade, and everything went fine.

          Show
          John Price added a comment - Update from me - I upgraded from 3.3 to 3.5 and the calendars seem ok. In my test upgrade they seemed to lose data but I figured out how to restore it at the SQL level from a backup, then felt good enough to try the production upgrade, and everything went fine.
          Hide
          greg mcmillan added a comment -

          Thanks for the update

          But where you able to reproduce any calendar issues with 3.5?

          Did you check the exceptions, error logs, or even the one about different subscriptions (iCal) to remote cals?

          Greg

          Show
          greg mcmillan added a comment - Thanks for the update But where you able to reproduce any calendar issues with 3.5? Did you check the exceptions, error logs, or even the one about different subscriptions (iCal) to remote cals? Greg
          Hide
          Sherif Mansour [Atlassian] added a comment -

          Hi All,
          Thanks for your patience with this issue. Today we are happy to announce the launch of Team Calendars 1.0, our new calendaring solution for Confluence. You can learn more about it here: http://atlassian.com/calendars

          You can provide plugin feedback here: https://studio.plugins.atlassian.com/browse/TEAMCAL
          Sherif

          Show
          Sherif Mansour [Atlassian] added a comment - Hi All, Thanks for your patience with this issue. Today we are happy to announce the launch of Team Calendars 1.0, our new calendaring solution for Confluence. You can learn more about it here: http://atlassian.com/calendars You can provide plugin feedback here: https://studio.plugins.atlassian.com/browse/TEAMCAL Sherif
          Hide
          greg mcmillan added a comment -

          How can I beta test it?

          My beta trial would be on behalf of LinkedIn Employees.

          Greg

          Show
          greg mcmillan added a comment - How can I beta test it? My beta trial would be on behalf of LinkedIn Employees. Greg
          Hide
          Mark Hrynczak [Atlassian] added a comment -

          Greg, just click the 'Try Now' button on this page to start an evaluation of the new plugin.

          Show
          Mark Hrynczak [Atlassian] added a comment - Greg, just click the 'Try Now' button on this page to start an evaluation of the new plugin.
          Hide
          Jeff Mitchell added a comment -

          Does it support CalDAV?

          I wasn't one of the blessed that got personal chats with anyone at Atlassian about our calendaring needs, but I can tell you that we're happy to pay for the plugin if it provides the functionality we need. We were in the process of setting up Zimbra because it supports CalDAV; I'd much rather save that headache and use Team Calendars, but can find no information about what protocols it supports, just handwavy information in the notes about it supporting subscriptions with iCal and Outlook. Give me CalDAV and you'll have a happy paying customer.

          Show
          Jeff Mitchell added a comment - Does it support CalDAV? I wasn't one of the blessed that got personal chats with anyone at Atlassian about our calendaring needs, but I can tell you that we're happy to pay for the plugin if it provides the functionality we need. We were in the process of setting up Zimbra because it supports CalDAV; I'd much rather save that headache and use Team Calendars, but can find no information about what protocols it supports, just handwavy information in the notes about it supporting subscriptions with iCal and Outlook. Give me CalDAV and you'll have a happy paying customer.
          Hide
          Jonathan added a comment -

          ...did Tom Moore delete his comment for whatever reasons or some admin? I find his statement quite true - the pricing is overwhelming considering this was a free plugin. It's half of the yearly conflunce fee and I guess you will have to renew your licence yearly as well if you want to stay compatible with confluence upgrades.

          Show
          Jonathan added a comment - ...did Tom Moore delete his comment for whatever reasons or some admin? I find his statement quite true - the pricing is overwhelming considering this was a free plugin. It's half of the yearly conflunce fee and I guess you will have to renew your licence yearly as well if you want to stay compatible with confluence upgrades.
          Hide
          Tom Moore added a comment -

          I deleted it, as I realized venting is probably not going to do anything.. But yea, $3600 for this on top of our existing 2000+ fees seems rather large.. I wish they would have done something like a stripped down calendar version without any connections (just to have simple calendar on a wiki page) and then have the full version for that price.

          Show
          Tom Moore added a comment - I deleted it, as I realized venting is probably not going to do anything.. But yea, $3600 for this on top of our existing 2000+ fees seems rather large.. I wish they would have done something like a stripped down calendar version without any connections (just to have simple calendar on a wiki page) and then have the full version for that price.
          Hide
          John Price added a comment -

          I ran this by my boss and he was also surprised at the cost. For that much it's usually something like JIRA Greenhopper that adds a ton of features throughout the product. I think it's especially tough for people who were happy with the existing free plugin. Basically he told me to wait on this one and keep limping by with the unsupported one until the price comes down in the future.

          For upgrades I assume we'd just download each calendar from the old plugin (iCal format), and then import each one. What would be really awesome is some automated upgrade from existing Calendar Plugin calendars.

          The new one does look very nice though.

          Show
          John Price added a comment - I ran this by my boss and he was also surprised at the cost. For that much it's usually something like JIRA Greenhopper that adds a ton of features throughout the product. I think it's especially tough for people who were happy with the existing free plugin. Basically he told me to wait on this one and keep limping by with the unsupported one until the price comes down in the future. For upgrades I assume we'd just download each calendar from the old plugin (iCal format), and then import each one. What would be really awesome is some automated upgrade from existing Calendar Plugin calendars. The new one does look very nice though.
          Hide
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment -

          I refuse to agree, that the price point of this piece of software is expensive. You guys keep comparing all pricing with the Confluence and JIRA basic pricing, which is not fair and will ultimately be problematic:
          1. Plugins sell less and thus have to be more expensive to be refinanced.
          2. Confluence and JIRA land in a company. A low price point is crucial for that mission. Plugins simply have to reflect the value they bring.

          I highly recommend to start comparing prices with value, that you get out of team calendars. I am pretty sure, that Atlassian is not going to reduce pricing for this one in the foreseeable future.

          Did you know, that you get a 40% discount in the first year as an introduction? You should go for that.

          Show
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment - I refuse to agree, that the price point of this piece of software is expensive. You guys keep comparing all pricing with the Confluence and JIRA basic pricing, which is not fair and will ultimately be problematic: 1. Plugins sell less and thus have to be more expensive to be refinanced. 2. Confluence and JIRA land in a company. A low price point is crucial for that mission. Plugins simply have to reflect the value they bring. I highly recommend to start comparing prices with value, that you get out of team calendars. I am pretty sure, that Atlassian is not going to reduce pricing for this one in the foreseeable future. Did you know, that you get a 40% discount in the first year as an introduction? You should go for that.
          Hide
          Jeff Mitchell added a comment -

          I generally have to agree with Martin here, although I think he meant "refined" instead of "refinanced"

          (CalDAV)

          Confluence and JIRA are priced low, IMHO, compared to the value they bring (look at the price of Confluence vs. Lotus Connections for instance). This helps growth and adoption, and it's a valid market strategy. Extra plugins on top are priced both to fund their development and because this helps offset the low price of the original software.

          (CalDAV)

          The Calendar plugin was nice when it was free, but to be honest, I discouraged users from relying on it specifically because it was a freebie and not open source. I knew that Atlassian could stop development on it at any time (not that many didn't use it anyways, which means I have an unfun manual upgrade coming up, unless an automatically-upgrading version is released soon), and I wouldn't really have any right to be angry with them for this, nor would I have recourse or an upgrade path without the source code.

          (CalDAV)

          To me, the new product looks like it brings a lot of extra, useful features. Yes, it's costly compared to Confluence, but that's comparing apples with oranges; it's not costly compared to many other group calendaring solutions (Oracle calendar, Exchange).

          Did I mention I need it to support CalDAV?

          Show
          Jeff Mitchell added a comment - I generally have to agree with Martin here, although I think he meant "refined" instead of "refinanced" (CalDAV) Confluence and JIRA are priced low, IMHO, compared to the value they bring (look at the price of Confluence vs. Lotus Connections for instance). This helps growth and adoption, and it's a valid market strategy. Extra plugins on top are priced both to fund their development and because this helps offset the low price of the original software. (CalDAV) The Calendar plugin was nice when it was free, but to be honest, I discouraged users from relying on it specifically because it was a freebie and not open source. I knew that Atlassian could stop development on it at any time (not that many didn't use it anyways, which means I have an unfun manual upgrade coming up, unless an automatically-upgrading version is released soon), and I wouldn't really have any right to be angry with them for this, nor would I have recourse or an upgrade path without the source code. (CalDAV) To me, the new product looks like it brings a lot of extra, useful features. Yes, it's costly compared to Confluence, but that's comparing apples with oranges; it's not costly compared to many other group calendaring solutions (Oracle calendar, Exchange). Did I mention I need it to support CalDAV?
          Hide
          Andrew Barnes added a comment - - edited

          Martin comes off as a shill.

          If the plugin was fully featured, I wouldn't balk at price. The lack of:

          ...to me are the reason for a 40% discount.

          Jeff: If you want CalDAV, have you created an issue for it? I can't find any when searching for CalDAV...

          Show
          Andrew Barnes added a comment - - edited Martin comes off as a shill. If the plugin was fully featured, I wouldn't balk at price. The lack of: ability to relate more than one person to an event/appointment ( TEAMCAL-86 ) RVSP functionality ( TEAMCAL-104 ) compact views ( TEAMCAL-99 ) security ( TEAMCAL-102 ) ...to me are the reason for a 40% discount. Jeff : If you want CalDAV, have you created an issue for it? I can't find any when searching for CalDAV...
          Hide
          Jeff Mitchell added a comment -

          It's a good point – there's a lot lacking. But it's a 1.0 product, and I'm hoping that by converting it to a paid product, they'll be putting resources behind those kinds of needs (I need those things too )

          I haven't put in an issue for CalDAV because I've been trying first to find out if it's already supported. The interoperability information is maddeningly abstract (OK, it interoperates with iCal and Outlook, but using what?) I guess it's easy for them to close an issue if it's already supported – thanks for the links to the appropriate project

          Show
          Jeff Mitchell added a comment - It's a good point – there's a lot lacking. But it's a 1.0 product, and I'm hoping that by converting it to a paid product, they'll be putting resources behind those kinds of needs (I need those things too ) I haven't put in an issue for CalDAV because I've been trying first to find out if it's already supported. The interoperability information is maddeningly abstract (OK, it interoperates with iCal and Outlook, but using what ?) I guess it's easy for them to close an issue if it's already supported – thanks for the links to the appropriate project
          Hide
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment -

          You may be right for this plugin. But I expect Atlassian to repeat that in the future again. It is simply an easy strategy to generate an additional revenue stream. Just like with Greenhopper.

          Show
          Martin Seibert (//SEIBERT/MEDIA, Germany) added a comment - You may be right for this plugin. But I expect Atlassian to repeat that in the future again. It is simply an easy strategy to generate an additional revenue stream. Just like with Greenhopper.

            People

            • Votes:
              91 Vote for this issue
              Watchers:
              74 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                2 years, 45 weeks, 5 days ago