Help
Filature is the platform of the SliTaz developers: discussions and private messages, bug tracking, test reports, commits and news. Everything works in a plain browser, in links, on a phone, from a shell and by mail.
Report a bug | Test an ISO | Developers | Commands
Report a bug
On SliTaz, run filature-report in a terminal, or Report a bug from the menu. Give a title and say what happens; the tool adds anonymous system information (release, flavor, kernel, CPU, memory, graphics). You see the whole report before it is sent, and nothing leaves without your yes. A contact is optional: developers only use it to ask you questions, it is never published.
Reports wait until a developer reads them; then they become a public bug, which you can follow without an account.
Test an ISO with TazHelper
TazHelper runs automatic checks on a live SliTaz, walks the tester through a short checklist and sends the results. Its manual is on doc.slitaz.org. Filature receives TazHelper reports at https://filature.slitaz.org/report, the same format as bug reports; once reviewed they are listed in test reports.
No network on the tested machine? TazHelper and filature-report keep the report in a file: send it later with tazhelper send <file> or filature-report send <file>, or paste it from another computer on this page.
Developers
Account and login
Your Filature account is your Unix account on the server, as a member of the devs group: no password here, no key to add. From a shell on the server, or through the client, run fil login: it prints a link and a code valid five minutes. Open the link, or type the code on the login page of your phone. Each browser stays logged in; My devices (or fil sessions, fil revoke) lists and ends them. The Account page of the menu gathers what is yours: the bugs you took, the mail settings, your devices.
The client
Install the filature package and put your server login in ~/.config/filature/client.conf:
FIL_HOST="you@foyer.slitaz.org"
Then every fil command runs on the server over SSH, one shared connection. fil new and fil reply open your $EDITOR; a reply shows the thread below the scissors line, which is cut before sending.
Threads
fil threads (discussions; -b the threads of bugs and Filature's notes, -a all), fil read 12, fil new Title, fil reply 12, or the Threads page. A private thread is open to its members only: fil new -p alice,bob Title, then fil invite 12 carol. Messages are plain text; addresses become links.
fil mail set you@example.org (or the Mail page) sends you every message, private only your private threads. Answer from your mail client: the reply lands in the thread. fil mail shows your own address to start a thread by mail. The mail bridge is not enabled on this server yet.
Notifications
The Notifications page (or fil notify set mine) pushes a title and a link to the ntfy app of your phone or desktop: new messages in the threads you pick, new reports and the answers of reporters.
Bugs
Review what users sent with fil reports, fil report 7, then fil accept 7 (a bug opens) or fil reject 7; the web page is Reports to review; fil reports -r or its Reviewed view list the reports already dealt with. Work on a bug with fil bug take 3 (fil bugs -m or the Mine view of the Bugs page list the ones you took, closed included), fil bug close 3 note, fil bug reopen 3, or open one yourself: fil bug new Title. A bug gets its devs thread with the first message about it: fil bug talk 3 or the form of the bug page, which shows the discussion.
Reports of reprise, the repair tool, wait in the same queue: fil reports reprise or the reprise filter of the web page. They stay private and open no bug; accept the ones that count, reject the noise.
A commit pushed to the SliTaz repositories with fix #3 (or fixes, fixed, close, closes, closed) closes bug 3 and links the changeset; see #3 or refs #3 only links it.
Fixes database
reprise, the repair tool of SliTaz, detects known problems on the machines and repairs them offline with the fixes database. An entry belongs to a bug: fil fixes add 1042 < entry, then another look and fil fixes ready <fix>. fil fixes publish -n shows what would change, fil fixes publish freezes every ready entry into a new release, fixes.txt, which reprise downloads. fil fixes retire <fix> takes an entry out of the next release. The grammar (when= predicates, repair= functions) is in the reprise README; entries are listed on Fixes.
News
fil news add Title publishes on the News page, fil news edit 12 fixes its text in the editor, fil news edit 12 Title < /dev/null only its title. On the web, the author has an Edit button under the news. Up to four PNG, JPEG or WebP images go under a news, from its form or with fil news image 12 file.png (fil news image 12 del 2 removes the second); their metadata is removed.
Search
The box in the menu bar, or fil search words: bugs, news and test reports for everyone, plus the threads a dev may read. Every word must appear.
Commands
fil version- print versionfil news [<id> | add | edit | image | del | export]- read, publish or fix newsfil threads [-b|-a] [-n count]- latest discussions, -b bugs, -a allfil read [-n last] <thread>- read a threadfil new [-p user,...] <title>- start a thread, message on stdinfil reply <thread>- reply, message on stdinfil invite <thread> <user>...- add people to a private threadfil bugs [-a|-m]- list open bugs, -a all, -m the ones you tookfil bug <id> | new ...- show or act on a bugfil reports [-r] [kind]- reports to review, -r reviewedfil reports-reindex- rebuild the counted keys of the reportsfil report <id> | ask <id>- show a report, ask its senderfil accept <id> [title]- accept a reportfil reject <id>- reject a reportfil tazhelper-import <dir>- import the TazHelper reports of labfil fixes [show|add|edit|ready|retire|publish|releases]- the fixes database of reprisefil hg-in <repo>- file pushed changesets (for the hg hook)fil hg-sync <path> [name]- import or catch up a repository historyfil search <words>- search bugs, news, test reports and threadsfil mail [set <addr> [all|private] | off]- mail delivery settingsfil mail-in [recipient]- file one mail read on stdin (for the MTA)fil notify [set <all|mine|private|off> [reports|noreports] | off | test]- push notification settingsfil whoami- show who you arefil login- get a code to log in on the webfil sessions- list your web sessionsfil revoke <id>|all- revoke web sessionsfil check- check this installation, for admins