Skip to content

Another sharing PR - #696

Merged
evert merged 77 commits into
masterfrom
sharing-take-2
Mar 30, 2016
Merged

evert merged 77 commits into
masterfrom
sharing-take-2

Conversation

@evert

@evert evert commented Jul 28, 2015

Copy link
Copy Markdown
Member

Work in progress.

TODO:

  • Right now we pick a 'default scheduling calendar' that might be a shared calendar. This should always be an owned calendar instead.
  • Decouple notification system from sharing system.
  • Implement getInvites and updateInvites in PDO backend.
  • Test iCal
  • Test BusyCal
  • Re-read old caldav sharing spec and see what we're missing
  • Re-read dav-notifications spec and validate implementation
  • Re-read dav-resource-sharing spec and validate implementation
  • Attain 100% coverage of new code
  • Re-read caldav-sharing spec and validate implementation
  • update new sql table names to not have underscore

Fixes #803

@evert evert self-assigned this Jul 28, 2015
@evert evert added this to the 3.1 milestone Jul 28, 2015
@phaidros7

Copy link
Copy Markdown

Oh it is great so see progress on this! Thanks alot @evert !!
Do you have any ETA for the sharing features?

Reason I am asking: alot of projects and groups demand not-googlish online calendars, including sharing features. owncloud is the only stack with a useable admin interface, but alot of people refuse to setup the whole owncloud heap for security, speed and maintainability reasons. the other alternative is projects like radicale, altho missing a end-user suitable admin interface (or better: using LDAP as backend will never attract endusers ..%) )!

Hence I believe baikal is the stack alot of people are waiting for. I'd even be willing to donate a for the feature!

@evert

evert commented Mar 24, 2016

Copy link
Copy Markdown
Member Author

Hi @phaidros7 ,

Glad you like the feature. I think this is fairly close to a release, but it will take a bit longer before it's also in baikal. If you are interested in sponsoring, I recently setup Bountysource.

https://www.bountysource.com/teams/fruux

Here you can either sponsor the team as a whole or post bounties on specific features. If you want to post a bounty on this feature specifically, you can do that via #803.

@evert

evert commented Mar 30, 2016

Copy link
Copy Markdown
Member Author

This is now ready for review / testing.

@evert

evert commented Mar 30, 2016

Copy link
Copy Markdown
Member Author

If travis passes my tests, I'm landing this. Finally!

@evert
evert merged commit 1c8a998 into master Mar 30, 2016
@prism69

prism69 commented May 4, 2016

Copy link
Copy Markdown

Forgive my noobiness but im trying to figure out how to share a calendar on Baikal...or is this not yet a feature?

@evert

evert commented May 4, 2016

Copy link
Copy Markdown
Member Author

It's not.

@evert
evert deleted the sharing-take-2 branch May 4, 2016 10:58
@prism69

prism69 commented May 4, 2016

Copy link
Copy Markdown

Thanks Evert, would you know if such a feature is imminent and, if not, what other open source calendar server I should be looking that has sharing?

@phsc84

phsc84 commented May 4, 2016

Copy link
Copy Markdown

You could try Owncloud 9.

@evert

evert commented May 4, 2016

Copy link
Copy Markdown
Member Author

The feature is going to be part of sabre/dav 3.2, which is a few weeks out. The plan is to then release baikal a few weeks after that. So this should be somewhere in June/July.

@prism69

prism69 commented May 4, 2016

Copy link
Copy Markdown

thanks, I guess I will wait.

@barnumbirr

Copy link
Copy Markdown

@evert Any news on calendar sharing landing in Baïkal?

@evert

evert commented Jul 29, 2016

Copy link
Copy Markdown
Member Author

This will happen later in the year. Baikal deseparately needs a re-architecture for this to work somewhat sanely. So we will first launch with silex support, and then sharing will come too.

You can track progress here: sabre-io/Baikal#568
any help is appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants