From Fedora Project Wiki
(add documentation)
(Update on dependencies and scope)
Line 4: Line 4:
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->


= OwnCloud =
= ownCloud =


== Summary ==
== Summary ==
Line 17: Line 17:


== Current status ==
== Current status ==
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Targeted release: [[Releases/18 | Fedora 18 ]]  
* Last updated: 2012-01-30
* Last updated: 2012-01-30
* Percentage of completion: 0%
* Percentage of completion: 0%
Line 30: Line 30:
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Package reviews
Package reviews. Unfortunately ownCloud bundles a lot of 3rd party code, that we need to package first:
** [http://pear.php.net/package/Crypt_Blowfish Crypt_Blowfish] already packaged as php-pear-Crypt-Blowfish
** [https://github.com/harvesthq/chosen Chosen]
** [http://arshaw.com/fullcalendar/ FullCalendar]
** [http://jquery.com/ jQuery]
** [http://code.google.com/p/sabredav/ SabreDAV]
** [https://github.com/fgelinas/timepicker Time Picker]
** [http://github.com/tplaner/When When]
** various other PEAR modules


== How To Test ==
== How To Test ==
Line 54: Line 62:
== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* php
* php-pear-Crypt-Blowfish
* php-pear-MDB2 (plus drivers for either MySQL or PostgreSQL)
* more PEAR modules (see [[#Scope]]


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
Don't ship it.


== Documentation ==
== Documentation ==

Revision as of 16:52, 26 February 2012


ownCloud

Summary

Owner

  • Email: <cwickert@fedoraproject.org>

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-01-30
  • Percentage of completion: 0%

Detailed Description

Benefit to Fedora

Scope

Package reviews. Unfortunately ownCloud bundles a lot of 3rd party code, that we need to package first:

How To Test

User Experience

  • Users should be able to easily store their data on OwnCloud
  • Provide package to easy set up and host OwnCloud on a server

Dependencies

  • php
  • php-pear-Crypt-Blowfish
  • php-pear-MDB2 (plus drivers for either MySQL or PostgreSQL)
  • more PEAR modules (see #Scope

Contingency Plan

Don't ship it.

Documentation

Release Notes

Comments and Discussion