Differences between revisions 1 and 2
Revision 1 as of 2011-08-11 10:37:04
Size: 394
Editor: ?MichaelGrisuBramer
Comment:
Revision 2 as of 2011-08-11 12:46:00
Size: 1356
Editor: ?MichaelGrisuBramer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * anonymous contributions allowed or not (maybe this is a DDTSS-only
feature)
 * anonymous contributions allowed or not (maybe this is a DDTSS-only feature)
Line 17: Line 16:
=== Milestone System ===

We should manage a set of descriptions as collection. Ex. all description in the task XXX, all description with the Tag YYY, etc.

With this collections we can make contests ('translate all descriptions of the desktop task')

The Debian Description Tracking System (DDTS) make this collections on a daily basis:
 * priorities (required, important, standard, optional, extra) (prio:XXX)
 * sections (games, ...) (sect:XXX)
 * tasks from the packages-files (task:XXX)
 * Tags from the packages-files (tags:XXX)
Maybe we can add collection per hand:
 * a custom package selection per language (defined from the lang coordinator) (lang:XXX)
 * maybe a custom package selection per user, defined from himself (user:XXX)

The sql-table for this is:

{{{
CREATE TABLE description_milestone_tb (
    description_milestone_id serial PRIMARY KEY,
    description_id integer NOT NULL,
    milestone text NOT NULL
);
}}}

Config

Per language:

  • number of reviewers
  • the above feature (delay without review counts as a review)
  • the delay in the above feature
  • anonymous contributions allowed or not (maybe this is a DDTSS-only feature)

Messages System

  • "general" messages
  • Team Messages
  • Messages to users
  • Comments to descriptions

Milestone System

We should manage a set of descriptions as collection. Ex. all description in the task XXX, all description with the Tag YYY, etc.

With this collections we can make contests ('translate all descriptions of the desktop task')

The Debian Description Tracking System (DDTS) make this collections on a daily basis:

  • priorities (required, important, standard, optional, extra) (prio:XXX)
  • sections (games, ...) (sect:XXX)
  • tasks from the packages-files (task:XXX)
  • Tags from the packages-files (tags:XXX)

Maybe we can add collection per hand:

  • a custom package selection per language (defined from the lang coordinator) (lang:XXX)
  • maybe a custom package selection per user, defined from himself (user:XXX)

The sql-table for this is:

CREATE TABLE description_milestone_tb (
    description_milestone_id serial PRIMARY KEY,
    description_id integer NOT NULL,
    milestone text NOT NULL
);

proposed Database layout