~qeef

Trackers

~qeef/damn-project

Last active a month ago

#5 Finished areas a month ago

Comment by ~qeef on ~qeef/damn-project

This is deployed now at https://finished.damn-project.org/

REPORTED RESOLVED IMPLEMENTED

#5 Finished areas a month ago

Comment by ~qeef on ~qeef/damn-project

The link above does not work anymore, the script has been merged: https://git.sr.ht/~qeef/damn-deploy/commit/ee526ee4a5ef39bd1b4401ff8773fa59b447e45c

#5 Finished areas a month ago

Comment by ~qeef on ~qeef/damn-project

#6 i18n for the manager and client (JavaScript ones) 3 months ago

Ticket created by ~qeef on ~qeef/damn-project

In the static directory of the manager and the client, there is i18n.js file with the inclomplete translations.

There are few things to do:

  • check and refactor/simplify the strings,
  • add the missing strings & update related code,
  • think about how to translate the strings.

The first two points are clear. There are some points about the third one:

  • It would be beneficial to use some 3rd party platform that is already used by translators. If used, the platform SHOULD be FOSS, open, etc.
  • There MUST be no 3rd party JavaScript library to import/include into the manager nor client.
  • The translated strings MUST be available for the offline usage. (To keep the download client functionality.)
  • The translated strings MUST be available under some compatible license.
  • It would be beneficial to allow translations by sending an email to the mailing list, either as a patch or an attached file. (The proposed workflow is: 1. Check the mailing list archive if the translation already exists. 2. Send an email to the mailing list about your intention to work on some language with the subject of I will work on cs translation, where cs is the language code. 3. After the translation is finished, reply to the mailing list thread with the updated i18n.js file attached, or send the related patch to the mailing list.)

#5 Finished areas 5 months ago

Ticket created by ~qeef on ~qeef/damn-project

Since the beginning of the damn project, it is ready for two kinds of areas -- current and finished. The original idea was to have the "clones" of current_areas, current_squares, and current_commits tables and store the finished read-only areas (and squares and commits) in them. The database is ready for this, see 70_damndb.sql of the damn-deploy repo.

However, there are two main disadvantages of this approach: (1) There must be an API to retrieve the data from the database basically duplicating and/or complicating the code of the damn-server repo; (2) the database has to serve static, read-only data. Both are against the damn project philosophy, particularly the simplicity (1) and the performance (2).

The proposed solution is to create new service (or even better--update upkeep service) similar to rss_gen of the damn-deploy repository that would (1) create static file containing finished area, it's squares, and commits, (2) delete the finished area, it's squares, and commits from the database, (3) serve the static file at some subdomain.

#2 Put the locust.io to the server repo 5 months ago

Comment by ~qeef on ~qeef/damn-project

REPORTED RESOLVED IMPLEMENTED

#4 RSS feeds 7 months ago

Comment by ~qeef on ~qeef/damn-project

REPORTED RESOLVED FIXED

#4 RSS feeds 8 months ago

Ticket created by ~qeef on ~qeef/damn-project

Create service that loads all (new) commits for all (new) areas and provides filtered RSS feeds.

The feeds are:

  • Area change commits of all the areas.
  • Area change commits of one area.
  • Some square related commits of one area.

In future versions, support filtering by area tags, priority, description language, and area location.

NOTE: The list of the feeds is intentionally limited (but extendable!) RSS is for human. If some script needs all the information, it's better to use API directly.

#1 damn-client.py 8 months ago

Comment by ~qeef on ~qeef/damn-project

REPORTED RESOLVED FIXED

#3 Create new service generating JWT tokens 8 months ago

Ticket created by ~qeef on ~qeef/damn-project

The idea is to remove the authentication functionality from the server. The reason is to keep the server being the API to the database only. The server will still use the JWT for authorization.

This change creates opportunity for custom, independent authentication process.