Start using Ditz the distributed bug tracker.

diff --git a/.ditz-plugins b/.ditz-plugins
new file mode 100644 (file)
index 0000000..2756e1e
--- /dev/null
+++ b/.ditz-plugins
@@ -0,0 +1 @@
+- git

diff --git a/.gitignore b/.gitignore
index e42ea3424f483ba29e5bb7f3a57b84bda8ed3039..df6652b0e97dfcd2c175d84d3dbddc9e02b305ae 100644 (file)
--- a/.gitignore
+++ b/.gitignore
@@ -8,6 +8,8 @@ configure
 Setup
 dist/
 
+.ditz-config
+
 Rakka/Resource/JavaScript.hs
 js/packed.js
 js/yuicompressor-*.jar

diff --git a/bugs/issue-0b925fc6286aa2d52ebd379b4c4283b14dfec865.yaml b/bugs/issue-0b925fc6286aa2d52ebd379b4c4283b14dfec865.yaml
new file mode 100644 (file)
index 0000000..f7d68f0
--- /dev/null
+++ b/bugs/issue-0b925fc6286aa2d52ebd379b4c4283b14dfec865.yaml
@@ -0,0 +1,21 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Allow guests to leave their comments on pages.
+desc: |-
+  Such data should be stored as page attachments.
+  There should be a global flag to disallow comments.
+type: :feature
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 13:03:04.294484 Z
+references: []
+
+id: 0b925fc6286aa2d52ebd379b4c4283b14dfec865
+log_events: 
+- - 2010-03-02 13:03:05.766604 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-227c3bdad879b5f85aae08563b932f99b3f95cec.yaml b/bugs/issue-227c3bdad879b5f85aae08563b932f99b3f95cec.yaml
new file mode 100644 (file)
index 0000000..573c7f5
--- /dev/null
+++ b/bugs/issue-227c3bdad879b5f85aae08563b932f99b3f95cec.yaml
@@ -0,0 +1,24 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Wouldn't it be cool if Rakka was totally pure-Haskell?
+desc: |-
+  We currently use the following impure packages:
+  - HsHyperEstraier
+  - HsSVN
+  - HsOpenSSL
+  - magic
+type: :task
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 13:28:59.008922 Z
+references: []
+
+id: 227c3bdad879b5f85aae08563b932f99b3f95cec
+log_events: 
+- - 2010-03-02 13:29:00.177175 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-5731bf94f62b6eaf8af7e1dff0da117a5ca2a0d7.yaml b/bugs/issue-5731bf94f62b6eaf8af7e1dff0da117a5ca2a0d7.yaml
new file mode 100644 (file)
index 0000000..7a79396
--- /dev/null
+++ b/bugs/issue-5731bf94f62b6eaf8af7e1dff0da117a5ca2a0d7.yaml
@@ -0,0 +1,21 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Make browsers' Back and Forward buttons usable
+desc: |-
+  We should find a way to make browsers' Back and Forward buttons usable.
+  URI fragments may help us, but how about internal state changes, like modified textarea?
+type: :task
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 12:57:47.325591 Z
+references: []
+
+id: 5731bf94f62b6eaf8af7e1dff0da117a5ca2a0d7
+log_events: 
+- - 2010-03-02 12:57:48.765873 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-6e437d5ba59c9e6e45a171d38a8a3e00dde0daac.yaml b/bugs/issue-6e437d5ba59c9e6e45a171d38a8a3e00dde0daac.yaml
new file mode 100644 (file)
index 0000000..5196810
--- /dev/null
+++ b/bugs/issue-6e437d5ba59c9e6e45a171d38a8a3e00dde0daac.yaml
@@ -0,0 +1,21 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Write logs into localstatedir
+desc: |-
+  The logger should send logs into localstatedir.
+  File rotation should be up to users.
+type: :feature
+component: Rakka
+release: "0.1"
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 12:48:35.732250 Z
+references: []
+
+id: 6e437d5ba59c9e6e45a171d38a8a3e00dde0daac
+log_events: 
+- - 2010-03-02 12:48:36.530186 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-a4c1df68e9bc332385b9c9e425738e59a029fb69.yaml b/bugs/issue-a4c1df68e9bc332385b9c9e425738e59a029fb69.yaml
new file mode 100644 (file)
index 0000000..8a23b9c
--- /dev/null
+++ b/bugs/issue-a4c1df68e9bc332385b9c9e425738e59a029fb69.yaml
@@ -0,0 +1,19 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Implement account manipulation
+desc: systemConfig has a missing feature to create or drop user accounts.
+type: :feature
+component: Rakka
+release: "0.1"
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 12:45:47.445331 Z
+references: []
+
+id: a4c1df68e9bc332385b9c9e425738e59a029fb69
+log_events: 
+- - 2010-03-02 12:45:51.399236 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-d411223c56973e94b7c7754eaf81039a03bb0b4c.yaml b/bugs/issue-d411223c56973e94b7c7754eaf81039a03bb0b4c.yaml
new file mode 100644 (file)
index 0000000..cae2c7f
--- /dev/null
+++ b/bugs/issue-d411223c56973e94b7c7754eaf81039a03bb0b4c.yaml
@@ -0,0 +1,19 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: Page templates
+desc: There should be a way to load templates at the beginning of page creation.
+type: :feature
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 13:13:26.600190 Z
+references: []
+
+id: d411223c56973e94b7c7754eaf81039a03bb0b4c
+log_events: 
+- - 2010-03-02 13:13:31.370116 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-d96e069d2394c7a1de663af67888efe61f938c89.yaml b/bugs/issue-d96e069d2394c7a1de663af67888efe61f938c89.yaml
new file mode 100644 (file)
index 0000000..f545c82
--- /dev/null
+++ b/bugs/issue-d96e069d2394c7a1de663af67888efe61f938c89.yaml
@@ -0,0 +1,22 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: "There should be a way to escape from data: scheme to http: scheme."
+desc: |-
+  When we open an image page in Rakka, we can't easilly get out of html+data: to just an image.
+  We can't easily save it to the disk.
+  We can't easily scale it (especially when the image is large).
+type: :task
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 13:25:59.810753 Z
+references: []
+
+id: d96e069d2394c7a1de663af67888efe61f938c89
+log_events: 
+- - 2010-03-02 13:26:01.442864 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - ""
+git_branch: 

diff --git a/bugs/issue-fb986d0c30569e0026e9d14f887823a372d4f6c5.yaml b/bugs/issue-fb986d0c30569e0026e9d14f887823a372d4f6c5.yaml
new file mode 100644 (file)
index 0000000..c6266e5
--- /dev/null
+++ b/bugs/issue-fb986d0c30569e0026e9d14f887823a372d4f6c5.yaml
@@ -0,0 +1,24 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: IP address blacklisting
+desc: There should be a way to disallow some people to make any changes.
+type: :feature
+component: Rakka
+release: 
+reporter: PHO <pho@cielonegro.org>
+status: :unstarted
+disposition: 
+creation_time: 2010-03-02 13:06:23.750179 Z
+references: []
+
+id: fb986d0c30569e0026e9d14f887823a372d4f6c5
+log_events: 
+- - 2010-03-02 13:10:13.576295 Z
+  - PHO <pho@cielonegro.org>
+  - created
+  - |-
+    Shouldn't Lucu have a feature like this:
+    - Disallow POST, DELETE, PUT by 1.2.3.4/24
+    - Disallow All by 10.11.12.13/30
+    
+    Such banlist shall be configured dynamically by Lucu resources...
+git_branch: 

diff --git a/bugs/project.yaml b/bugs/project.yaml
new file mode 100644 (file)
index 0000000..deeeb23
--- /dev/null
+++ b/bugs/project.yaml
@@ -0,0 +1,16 @@
+--- !ditz.rubyforge.org,2008-03-06/project 
+name: Rakka
+version: "0.5"
+components: 
+- !ditz.rubyforge.org,2008-03-06/component 
+  name: Rakka
+releases: 
+- !ditz.rubyforge.org,2008-03-06/release 
+  name: "0.1"
+  status: :unreleased
+  release_time: 
+  log_events: 
+  - - 2010-03-02 12:42:25.957028 Z
+    - PHO <pho@cielonegro.org>
+    - created
+    - This will be the first public release without complete documentations and features.