File: comment_1_d5adaef4712913dc0263d4ebafb79320._comment

package info (click to toggle)
git-annex 10.20250721-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 74,484 kB
  • sloc: haskell: 90,982; javascript: 9,103; sh: 1,469; makefile: 213; perl: 137; ansic: 44
file content (15 lines) | stat: -rw-r--r-- 807 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
 nickname="Richard"
 subject="comment 1"
 date="2012-09-23T21:58:08Z"
 content="""
You could try to do it similar to [RT](http://bestpractical.com/rt/):

* Implement saved statements, i.e. offer common use cases
* Allow those statements (or aliases? stanzas?) to be loaded in a relatively simple editor with a basic wizard to support the building of new rules
* Offer a free-text input for advanced users. It should be able to parse that and load it into the simple editor.
* Users should be able to save, export, and import those statements.
* Optionally, allow users to dry run the rules by showing them what git-annex needs to do to fulfill the requirements set by the statements.

"""]]