Difference between revisions of "Gallery2:2.0 Release Blockers" - Gallery Codex
Personal tools

Difference between revisions of "Gallery2:2.0 Release Blockers"

From Gallery Codex

(/lib/tools/test/)
m (Text replacement - "codex.gallery2.org" to "codex.galleryproject.org")
 
(77 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=Final Release Blockers=
 
 
==High Priority==
 
==High Priority==
===/lib/tools/test/===
 
Remove /lib/tools/test/ and add some emergency tools in /tools/ or /emergency
 
 
* Flush the database cache
 
* Flush the derivative cache
 
 
 
===Theme Documentation===
 
===Theme Documentation===
 
The theme system needs to be documented. This already has been started on the [[Gallery2:Themes|theme page]].
 
The theme system needs to be documented. This already has been started on the [[Gallery2:Themes|theme page]].
 
+
* Update 15-Aug (mindless) - I added [[Gallery2:Themes:Reference]] (Update: I'm now done with that page.. feel free to take it over, make edits, etc)
===Lightweight release without development overhead===
+
Don't ship the final release with unneeded bloat, e.g. /lib/tools/, .po files, /modules/*/test/.
+
(be careful of some modules that need modules/*/test/data like imagemagick)
+
 
+
===Add better multisite install docs===
+
See [http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=117349&group_id=7130&group_project_id=14056 sf.net task 117349].
+
 
+
===Bug Recursive remove perms leaves data in imageblock cache===
+
See [http://sourceforge.net/tracker/index.php?func=detail&aid=1241790&group_id=7130&atid=107130 sf.net bug 1241790].
+
  
 
===Administration Manual===
 
===Administration Manual===
 
A guide to document the common administration tasks as installing, upgrading, configuring, etc.
 
A guide to document the common administration tasks as installing, upgrading, configuring, etc.
 +
* Update 8-Sep (mindless): not really admin manual, but I added [[G1-G2 Comparison]]
  
 
===User Manual===
 
===User Manual===
Line 31: Line 16:
 
===Links to required and optional binaries and packages===
 
===Links to required and optional binaries and packages===
 
Ideally, we'd have a package of all required and optional binaries for the supported platforms. Or link to the available precompiled binaries and offer a package of the missing binaries on our site.
 
Ideally, we'd have a package of all required and optional binaries for the supported platforms. Or link to the available precompiled binaries and offer a package of the missing binaries on our site.
 +
* Supported platforms: linux, WinXP, OSX, *BSD, Win2003Server, ...?
 +
* Binaries: NetPBM, ImageMagick, unzip, ffmpeg, jhead, dcraw, zip, php-cgi (with gettext, GD2, .. support)
 +
* Links to other requirements: apache, php, JRE,
  
Supported platforms: linux, WinXP, OSX, *BSD, Win2003Server, ...?
+
2005/08/08 '''update''': there's now a [[Gallery2:Installation_Requirements|Installation Requirements]] page and an improved [[Installing_an_Image_Processing_Library|Installing an Image Processing Library Howto]]. WHat's missing is: Binaries for ffmpeg on non-windows platforms, for imagemagick for linux, for zip, unzip, jhead and php-cgi.
 
+
Binaries: NetPBM, ImageMagick, unzip, ffmpeg, jhead, dcraw, zip, php-cgi (with gettext, GD2, .. support)
+
 
+
Links to other requirements: apache, php, JRE,
+
  
 
===Create a huge FAQ and knowledge base===
 
===Create a huge FAQ and knowledge base===
 
A huge FAQ and a specialized knowledge base can simplify the everyday work as a support staff member tremendously. e.g. that blank site admin -> module pages could be caused by a too small memory limit (16mb is sometimes not enough), or how to deal with data corruptions, etc.
 
A huge FAQ and a specialized knowledge base can simplify the everyday work as a support staff member tremendously. e.g. that blank site admin -> module pages could be caused by a too small memory limit (16mb is sometimes not enough), or how to deal with data corruptions, etc.
 
+
* As to the FAQ: we need to reorganize the G1 / G2 faqs. Some FAQs are common to both versions, e.g. PHP / webserver specific things like the upload maximum, memory limit etc.
===More debug information in the install core module step===
+
After Beta 4 was released, I have the impression there were more "install core module failed" issues than before. And it's very, very difficult to find the problem with the little output we get. Perhaps have much more $gallery->debug messages during the install process.  
+
 
+
Of course it would be better if we had not to debug, i.e. if the installer was even more robust than it is at the moment.
+
  
 
==Low Priority==
 
==Low Priority==
 
===Downloadable translations===
 
===Downloadable translations===
Don't ship the final release with all available languages, only with en_UK. But users that can't extract a language archive over an existing G2 install will have a hard time adding the translation files in all modules manually via FTP.
+
Don't ship the final release with all available languages, only with en_US. But users that can't extract a language archive over an existing G2 install will have a hard time adding the translation files in all modules manually via FTP.
  
 
===Better Edit Permissions UI===
 
===Better Edit Permissions UI===
 
The edit permissions UI was discussed again and again and the only conclusion was that it needs to be reworked.
 
The edit permissions UI was discussed again and again and the only conclusion was that it needs to be reworked.
See [[http://gallery.menalto.com/index.php?name=PNphpBB2&file=viewtopic&t=30214 this forum thread]] for a discussion of where this might lead.
+
See [[http://galleryproject.org/index.php?name=PNphpBB2&file=viewtopic&t=30214 this forum thread]] for a discussion of where this might lead.
  
===Bug "view comments" permission obscures "view item"===
+
===Create Embedding & Integration docs===
See [http://sourceforge.net/tracker/index.php?func=detail&aid=903975&group_id=7130&atid=107130 sf.net bug 903975].
+
<strike>See [http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=111196&group_id=7130&group_project_id=14056 sf.net task 111196].
 +
* update 2005/01/30 - See: http://codex.galleryproject.org/index.php/Gallery2:Embedding:Integration</strike>
  
===Bug Applets + G1->G2 url rewrite cause logout in IE===
+
===Codex Page for Modifications/Customizations===
See [http://sourceforge.net/tracker/index.php?func=detail&aid=1231227&group_id=7130&atid=107130 sf.net bug 1231227].
+
Create a codex page for modifications and customizations such that user can create their own Howto's, modifications, links to modules etc. and add them to this page. <strike>Don't forget to copy / import the User Contributions page from the gmc wiki</strike>(done by valiant).
 +
What's still missing is: instructions on how to contribute / how to create your own wiki page / add a link to your contribution to the contributions page. Maybe better organize the user contributions, create a single entry page and a page for each category (modules, themes, ..).
  
===Create Embedding & Integration docs===
+
===Progress Bar for Install-core===
See [http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=111196&group_id=7130&group_project_id=14056 sf.net task 111196].
+
<strike>See [http://sourceforge.net/tracker/index.php?func=detail&aid=1255320&group_id=7130&atid=107130 sf.net bug 1255320]</strike> (fixed by valiant)
  
 
===Try to lower the PHP memory limit requirement===
 
===Try to lower the PHP memory limit requirement===
 
Currently, we ask for at a memory limit of at least 16mb, else we show a warning in the installer. But even 16mb seem to be not enough for simple tasks like displaying the list of modules (site admin -> modules). 12mb seem to be not enough to delete an album.  (in some cases). Most often, the user just sees an empty page or something like that. We should track down the memory consumption, e.g. if it is the translation files or what else.
 
Currently, we ask for at a memory limit of at least 16mb, else we show a warning in the installer. But even 16mb seem to be not enough for simple tasks like displaying the list of modules (site admin -> modules). 12mb seem to be not enough to delete an album.  (in some cases). Most often, the user just sees an empty page or something like that. We should track down the memory consumption, e.g. if it is the translation files or what else.
  
=Release Candidate 2 Blockers=
+
[[Category:Gallery 2]]
 
+
=Release Candidate 1 Blockers=
+

Latest revision as of 15:22, 1 July 2013

High Priority

Theme Documentation

The theme system needs to be documented. This already has been started on the theme page.

  • Update 15-Aug (mindless) - I added Gallery2:Themes:Reference (Update: I'm now done with that page.. feel free to take it over, make edits, etc)

Administration Manual

A guide to document the common administration tasks as installing, upgrading, configuring, etc.

User Manual

A guide for common user actions as adding albums, items, document each module and feature; what it does, how to use it, etc.

Module Development Documention

A module howto and an introduction to the G2 framework, how to do common stuff, etc.

Links to required and optional binaries and packages

Ideally, we'd have a package of all required and optional binaries for the supported platforms. Or link to the available precompiled binaries and offer a package of the missing binaries on our site.

  • Supported platforms: linux, WinXP, OSX, *BSD, Win2003Server, ...?
  • Binaries: NetPBM, ImageMagick, unzip, ffmpeg, jhead, dcraw, zip, php-cgi (with gettext, GD2, .. support)
  • Links to other requirements: apache, php, JRE,

2005/08/08 update: there's now a Installation Requirements page and an improved Installing an Image Processing Library Howto. WHat's missing is: Binaries for ffmpeg on non-windows platforms, for imagemagick for linux, for zip, unzip, jhead and php-cgi.

Create a huge FAQ and knowledge base

A huge FAQ and a specialized knowledge base can simplify the everyday work as a support staff member tremendously. e.g. that blank site admin -> module pages could be caused by a too small memory limit (16mb is sometimes not enough), or how to deal with data corruptions, etc.

  • As to the FAQ: we need to reorganize the G1 / G2 faqs. Some FAQs are common to both versions, e.g. PHP / webserver specific things like the upload maximum, memory limit etc.

Low Priority

Downloadable translations

Don't ship the final release with all available languages, only with en_US. But users that can't extract a language archive over an existing G2 install will have a hard time adding the translation files in all modules manually via FTP.

Better Edit Permissions UI

The edit permissions UI was discussed again and again and the only conclusion was that it needs to be reworked. See [this forum thread] for a discussion of where this might lead.

Create Embedding & Integration docs

See sf.net task 111196.

Codex Page for Modifications/Customizations

Create a codex page for modifications and customizations such that user can create their own Howto's, modifications, links to modules etc. and add them to this page. Don't forget to copy / import the User Contributions page from the gmc wiki(done by valiant). What's still missing is: instructions on how to contribute / how to create your own wiki page / add a link to your contribution to the contributions page. Maybe better organize the user contributions, create a single entry page and a page for each category (modules, themes, ..).

Progress Bar for Install-core

See sf.net bug 1255320 (fixed by valiant)

Try to lower the PHP memory limit requirement

Currently, we ask for at a memory limit of at least 16mb, else we show a warning in the installer. But even 16mb seem to be not enough for simple tasks like displaying the list of modules (site admin -> modules). 12mb seem to be not enough to delete an album. (in some cases). Most often, the user just sees an empty page or something like that. We should track down the memory consumption, e.g. if it is the translation files or what else.

advertisements