编辑“用户:Bharat”

Bharat is a Gallery developer.

[[img:10774]]

= TODO =
==2.3 Project Queue==

=== Does not require API change ===
* '''Infrastructure''': DP should provide the APIs in its requests so that the gmc_repository Drupal module can choose a repository that is compatible (probably basing this on GalleryCoreAPI version is enough).  No APIs presented means that they're on 2.2 so we can hardcode a starting point.
* '''Performance''': Move file based caching into the database
* '''Package Size''': Allow DP to download core language packs
* '''Features''': Create language pack manager 
** eg: "I only want these languages, and I want them for all plugins"
* '''Stability''': Create an event viewer module 
** Admins should be able to see a log of all errors that have occurred
* <strike>'''Package size''': Stop shipping locale hierarchy</strike>
* '''Usability''': AJAXify the progress bar
** make it a DHTML overlay instead of an interstitial page
* '''Usability''': Get rid of the g2_statusId and g2_navId from the urls.
** If this means deleting those two features, I'm totally ok with it. They're marginal at best (especially statusId) but they clutter up our urls.
* '''Usability''': Get rid of g2_ as the default form variable
** It's not necessary for standalone G2
** We will need to be backwards compatible for a long while
* '''Stability''': Overhaul the rewrite module (my require API change)
** Change the rewrite module so that it has a minimal footprint in the .htaccess file.  Just enough to delegate to the PHP code and let the PHP code interpret the url.  
** Allow each module to register urls that it wants to control, like Drupal does
* '''Features''': Rewrite the RSS module
** It's way, way, way too complicated.  Replace it with something very simple
* '''Features''': Add the notification module
** Finish this off and get it integrated.  Lots of people want it
* '''Features''': Integrate a better anti-spam solution
** Akismet would be good.  Wordpress' akismet integration is a good template to follow
** Simple is better here
* '''UI''': Give modules more template hooks
** Modules should be able to arbitrarily add code to the header and footer of the page (like to add a page counter, etc)

=== Requires API Change ===
* Move all _xxx special plugin parameters into GalleryPluginMap
** select count(*) from g2_PluginParameterMap where g_parameterName like '%_' == 701 in a full 2.2.1
* '''UI''': Standardize our status message output
** Instead of making each individual template create a status message box, make it a standard feature that the theme can put somewhere on the page
** This will let us publish messages to admins whenever we want (eg "security update available!" or "your config.php has an error!")

=== Other ===
* Make permissions 256 bits instead of 32 bits
** ''talmdal'' is working on this
* Add fulltext search support
** user ''jrmint'' added fulltext search for mysql, see [http://gallery.menalto.com/node/38404 this forum topic] -- valiant

== Reviews ==

== Code Notes ==

=== Safe Mode ===
(preliminary results from trying to install/use G2 with safe_mode on)
* Installer:
** Warning: putenv(): Safe Mode warning: Cannot set environment variable 'LANG' - it's not in the allowed list in /usr/home/bharat/public_html/gallery2/modules/core/classes/GalleryTranslator.class on line 274
** Warning: putenv(): Safe Mode warning: Cannot set environment variable 'LANGUAGE' - it's not in the allowed list in /usr/home/bharat/public_html/gallery2/modules/core/classes/GalleryTranslator.class on line 275
** disable safe mode check
* step 4:
** Warning: mkdir(): SAFE MODE Restriction in effect. The script whose uid is 1000 is not allowed to access /usr/home/bharat/public_html/g2data/locks owned by uid 80 in /usr/home/bharat/public_html/gallery2/install/index.php on line 272

= Archived Stuff (done but not forgotten) =
=== 2.2 ===
* Roll AdminThemes into AdminPlugins and make Theme configuration pages their own SiteAdmin links -- '''done'''
* Move all _xxx special plugin parameters into GalleryPluginParameterMap (saves 4M columns) -- '''roll forward'''
* Consider removing GPL boilerplate from every file -- '''done''': considered and rejected as risky: http://www.archivesat.com/gallery_developers/thread566721.htm
* Finish writing publishxp/test/phpunit/LoginControllerTest.class -- '''done'''
* Support forced module deactivation -- '''done'''
* Finish off downloadable plugins -- '''done'''
* Move file based caching into the database -- '''roll forward'''

==2.0.1 release==
* Update codebase with the patch.  Done?
** valiant: yes, mindless did that. he also updated the MANIFEST files. i've tested a 2.0 -> 2.0.1 -> HEAD upgrade path and all went fine. but mindless had to commit something after my test, so a last test would be necessary before packaging.
* Make a patch
** Patch Issues:
*** Do we want to ship DataCacheTest?  If we don't then unit tests may fail for the end user.  If we do, then they'll have a way to verify that the patch actually worked (by running the test).  Problem: the new test has the same name as the old so if the patch fails totally the test will still pass but it won't actually be patched.
*** Full releases have DataCacheTest and the corresponding line in the MANIFEST already.  Other releases will not.  We'll have to either document the fact that the patch will fail in some circumstances and that's ok, or we'll have to have 2 patches.
*** Potential decision: '''don't ship DataCacheTest changes with the patch'''?
*** Should the patch contain just a diff?  Or should it contain all the files that have changed?  Or both?
**** Valiant suggests that the way that http://www.phpbb.com/downloads.php does it is fine.  Full package, Changed files only, Patch.
* Write comprehensive patch instructions.
* Make a new release
** Update the README to be 2.0.1
*** Is this a security vulnerability?  We don't want to advertise the version of G2 that's out there, but people could easily google for the README instead of looking for the version on the main page.
*** mindless is -1 on the README update.  bharat is leaning away from making the change also.  we have to consider the implications of making that information too available.
** Update the downloads page to include the patch too
* Push the release and patch to sf.net
* Write news article for sf.net
* Write news article for gmc
* Announce on Freshmeat.net
* Write security advisory for Bugtraq