Differences between revisions 10 and 11
Revision 10 as of 2011-08-15 10:21:34
Size: 2892
Editor: ?MichaelGrisuBramer
Comment:
Revision 11 as of 2011-08-15 10:36:50
Size: 3169
Editor: ?MichaelGrisuBramer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 72: Line 72:
The proposed sql-table for this is:

{{{
CREATE TABLE statistic_tb (
    statistic_id serial PRIMARY KEY,
    value integer NOT NULL,
    date integer NOT NULL
    stat text NOT NULL
);

# stat: the milestone-name or something like 'user:USERID:trans' etc.
}}}

user config

  • reset password
  • resent activity link

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

maybe with some notifications per mail, if you get new messages

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 (DDT) 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)
  • description from popcon (popcon)

Maybe we can add collection per hand:

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

The user/the coordinator should select a milestone for fetching new descriptions.

The it-team have a nice script (http://linguistico.svn.sourceforge.net/viewvc/linguistico/ddtp ) with this we can add milestones like:

  • retranslate (rtrn:$LANG) (done on a daily basis (in completeTranslations.pl))
  • partial translation (part:$LANG) (done on a daily basis (in ./Packages2db.pl))

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
);

Statistic / Numbers

To motivate the reviewer and translator we will collect some numbers and print some graphs in the new system.

The graphs:

  • #translate per User
  • #reviews per User
  • #translate per lang
  • #reviews per lang
  • %translated per milestone
  • #absolut per milestone
  • #translated+review (aka in the Translation-file) per Lang

add more...

The proposed sql-table for this is:

CREATE TABLE statistic_tb (
    statistic_id serial PRIMARY KEY,
    value integer NOT NULL,
    date integer NOT NULL
    stat text NOT NULL
);

# stat: the milestone-name or something like 'user:USERID:trans' etc.

proposed Database layout

proposel feature

wordlist

Hi

I miss the the former German word list. It had the nice feature listing several English variants for one word. So it could provide translation proposals even for misspelled English.

On the other hand, the list seemed to be decoupled from the German wordlist in the wiki.

Perhaps the use of two word lists and a wiki-aware documented way to enhance it would be worth thinking about. Over time, translators get more hints and the misspellings list could be used to filter new incoming translations.