summaryrefslogtreecommitdiff
path: root/data/docs
diff options
context:
space:
mode:
authorYorhel <git@yorhel.nl>2009-11-15 10:06:54 +0100
committerYorhel <git@yorhel.nl>2009-11-15 10:08:41 +0100
commitcd566ad416c19c81e7574491c78b81a7c609c5d2 (patch)
treec07e4e369e33ff89f16c920b8089730c69dbf3d9 /data/docs
parent42d95bdc14a887c37ec1f849d0f8224736816f11 (diff)
docs: Deleted d8 from the git repo
This page is pretty specific to the main VNDB, and each VNDB would probably have it's own d8.
Diffstat (limited to 'data/docs')
-rw-r--r--data/docs/881
1 files changed, 0 insertions, 81 deletions
diff --git a/data/docs/8 b/data/docs/8
deleted file mode 100644
index 701f5f70..00000000
--- a/data/docs/8
+++ /dev/null
@@ -1,81 +0,0 @@
-:TITLE:Development roadmap
-:INC:index
-
-
-:SUB:Some notes
-This TODO list is just a place for Yorhel to write down his plans and ideas
-for the upcoming versions of VNDB. Keep in mind that probably not everything
-written down here will actually see the light of day.<br />
-<br />
-The full source code of the site is available on a
-<a href="http://git.blicky.net/vndb.git/">git repository</a>, you can use it
-to track changes to the code or even to run your own version of VNDB.<br />
-<br />
-There is a <a href="http://beta.vndb.org/">beta version</a> of VNDB available
-for testing. New features will be implemented there and tested before getting
-uploaded to the actual website. Everyone is free to play around and use that
-beta version as a sandbox. Keep in mind, however, that all changes you make
-on the beta are not permanent, and will be reverted whenever the beta is
-synchronised with a more recent version of the database.<br /><br />
-Feel free to comment about the TODO list and to suggest new features on the
-<a href="/t/db">discussion board</a> or on <a href="irc://irc.synirc.net/vndb">
-IRC</a>.
-<br /><br />
-<b>Last update: 2009-02-12</b><br /><br />
-
-
-:SUB:Next version (2.3)
-<ol>
- <li>Catalog numbers for releases (done)</li>
- <li>Changing release statusses from VN page using AJAX (done)</li>
- <li>Random VN quotes on footer of every page (done)</li>
- <li>Platform icons on homepage (done)</li>
- <li>Tagging system (...will take a while)</li>
-</ol>
-
-
-:SUB:(Hopefully) soon
-<ol>
- <li>Advanced notification system</li>
- <li>More VNList filters &amp; stats</li>
- <li>Release calendar</li>
-</ol>
-
-
-:SUB:Later
-<ol>
- <li>Filters on /v/* to exclude blacklisted and/or VNs on a users list from the results</li>
- <li>Producer relations</li>
- <li><b style="font-weight: normal; text-decoration: line-through">VN Staff and Character database</b><br />
- <i>Probably not going to make it into VNDB, unless someone wants to be in charge of this</i></li>
- <li>Soundtrack listing<br />
- <i>Work together with <a href="http://vgmdb.net/">VGMdb</a>.</i></li>
- <li>Manga relations<br />
- <i>Looking for a good and comprehensive manga database fetch info from</i></li>
- <li>Reviews</li>
- <li>Walkthroughs/guides?<br />
- <i>Let each user maintain his own walkthrough, or just one collaboratively edited walkthough per VN?</i></li>
- <li>Image quality/resolution field to releases</li>
- <li>Some kind of minimal API for the hardcore VNDB fans (most likely using the JSON-RPC 1.0 Specification)</li>
- <li>Automatic uploading of cover images from a URL</li>
- <li>Scans of the packaging for releases</li>
- <li>Store which fields have been changed for revisions using one-character-code indicators</li>
- <li>Improved platform for fan translations (separated from releases)</li>
- <li>'currently down/offline' flag for official website links</li>
-</ol>
-
-
-:SUB:Technical things that need improvements
-<p>
- (I'm not expecting anyone to understand this, just random notes for myself)
-</p>
-<ol>
- <li>Set PostgreSQL charset to UTF-8</li>
- <li>Make use of PostgreSQL's fulltext search functionality to power the VN search</li>
- <li>Proper implementation of the 'hidden' flag for v/r/p entries</li>
- <li>Let VNDB and Multi communicate via SQL (and use schemas to separate the tables)</li>
- <li>More secure login system</li>
- <li>Use PostgreSQL stored procedures to insert revisions (using composite types, arrays, etc as arguments)</li>
- <li>Update the users.c_changes column on hiding/unhiding an item</li>
-</ol>
-