Fossil SCM
Add projects relating to the ticketing system
Commit
9e9fb33caf883c40053cea67bc4289d42434cda62a6e0638dfbed6cf9ddc3934
Parent
7a985a3d2c570b1…
1 file changed
+18
+18
| --- www/gsoc-ideas.md | ||
| +++ www/gsoc-ideas.md | ||
| @@ -36,10 +36,28 @@ | ||
| 36 | 36 | ``` |
| 37 | 37 | |
| 38 | 38 | This is a non-network-aware Mail Delivery Agent, and would be called by an MTA such as Postfix, Courier or Exim. |
| 39 | 39 | This command would reject anything that doesn't look like a bounce it is expecting. |
| 40 | 40 | |
| 41 | +## Work relating to the ticketing system in Fossil | |
| 42 | + | |
| 43 | +The Fossil SCM project uses tickets in a [somewhat unusual manner](https://fossil-scm.org/home/reportlist) | |
| 44 | +because the social programming | |
| 45 | +model has evolved to often use the Fosum instead. Other Fossil-using projects | |
| 46 | +use tickets in a more traditional report-a-bug manner. So this means that the | |
| 47 | +Fossil ticketing system user interface is underdeveloped. On the other hand, | |
| 48 | +pretty much every software developer uses a ticketing system at some point in | |
| 49 | +their workflow, and Fossil is intended to be usable by most developers. The | |
| 50 | +underlying technology for the Fossil ticketing system is guaranteed, so to | |
| 51 | +improve it requires only user interface changes. | |
| 52 | + | |
| 53 | +Projects relating to the ticketing system include: | |
| 54 | + | |
| 55 | +* Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. | |
| 56 | +* Alternatively, instead of improving Fossil's cli, implement a comprehensive ticket commandline with [libfossil's primitives](https://fossil.wanderinghorse.net/r/libfossil/wiki/home), look under the f-apps/ directory. | |
| 57 | +* Improving the Fossil web UI for ticketing, which is clunky to say the least | |
| 58 | + | |
| 41 | 59 | # Tasks Requiring Fossil Data Model Knowledge |
| 42 | 60 | |
| 43 | 61 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 44 | 62 | is designed to [endure for centuries](./fileformat.wiki), |
| 45 | 63 | be [easily accessible](./fossil-v-git.wiki#durable), and is [non-relational](./fossil-is-not-relational.md). |
| 46 | 64 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -36,10 +36,28 @@ | |
| 36 | ``` |
| 37 | |
| 38 | This is a non-network-aware Mail Delivery Agent, and would be called by an MTA such as Postfix, Courier or Exim. |
| 39 | This command would reject anything that doesn't look like a bounce it is expecting. |
| 40 | |
| 41 | # Tasks Requiring Fossil Data Model Knowledge |
| 42 | |
| 43 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 44 | is designed to [endure for centuries](./fileformat.wiki), |
| 45 | be [easily accessible](./fossil-v-git.wiki#durable), and is [non-relational](./fossil-is-not-relational.md). |
| 46 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -36,10 +36,28 @@ | |
| 36 | ``` |
| 37 | |
| 38 | This is a non-network-aware Mail Delivery Agent, and would be called by an MTA such as Postfix, Courier or Exim. |
| 39 | This command would reject anything that doesn't look like a bounce it is expecting. |
| 40 | |
| 41 | ## Work relating to the ticketing system in Fossil |
| 42 | |
| 43 | The Fossil SCM project uses tickets in a [somewhat unusual manner](https://fossil-scm.org/home/reportlist) |
| 44 | because the social programming |
| 45 | model has evolved to often use the Fosum instead. Other Fossil-using projects |
| 46 | use tickets in a more traditional report-a-bug manner. So this means that the |
| 47 | Fossil ticketing system user interface is underdeveloped. On the other hand, |
| 48 | pretty much every software developer uses a ticketing system at some point in |
| 49 | their workflow, and Fossil is intended to be usable by most developers. The |
| 50 | underlying technology for the Fossil ticketing system is guaranteed, so to |
| 51 | improve it requires only user interface changes. |
| 52 | |
| 53 | Projects relating to the ticketing system include: |
| 54 | |
| 55 | * Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. |
| 56 | * Alternatively, instead of improving Fossil's cli, implement a comprehensive ticket commandline with [libfossil's primitives](https://fossil.wanderinghorse.net/r/libfossil/wiki/home), look under the f-apps/ directory. |
| 57 | * Improving the Fossil web UI for ticketing, which is clunky to say the least |
| 58 | |
| 59 | # Tasks Requiring Fossil Data Model Knowledge |
| 60 | |
| 61 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 62 | is designed to [endure for centuries](./fileformat.wiki), |
| 63 | be [easily accessible](./fossil-v-git.wiki#durable), and is [non-relational](./fossil-is-not-relational.md). |
| 64 |