Fossil SCM
Improve explanations for prospective students in the ticketing section
Commit
0f90d0df757ab4ad8cda6db741fb7836561001832c14d2b384858a93d52ee6cb
Parent
316b55a6a6edeee…
1 file changed
+13
-9
+13
-9
| --- www/gsoc-ideas.md | ||
| +++ www/gsoc-ideas.md | ||
| @@ -63,27 +63,31 @@ | ||
| 63 | 63 | The Fossil command would reject anything that doesn't look like a bounce it is expecting. |
| 64 | 64 | |
| 65 | 65 | It is not certain that this design is the best one to address the inbound mail |
| 66 | 66 | problem. That is why the first part of this task is to find a workable design. |
| 67 | 67 | |
| 68 | -## Work relating to the ticketing system in Fossil | |
| 68 | +# Work relating to the ticketing system in Fossil | |
| 69 | 69 | |
| 70 | 70 | The Fossil SCM project uses tickets in a [somewhat unusual manner](https://fossil-scm.org/home/reportlist) |
| 71 | 71 | because the social programming |
| 72 | -model has evolved to often use the Fosum instead. Other Fossil-using projects | |
| 72 | +model has evolved to often use the Forum instead of ticketing. Other Fossil-using projects | |
| 73 | 73 | use tickets in a more traditional report-a-bug manner. So this means that the |
| 74 | -Fossil ticketing system user interface is underdeveloped. On the other hand, | |
| 75 | -pretty much every software developer uses a ticketing system at some point in | |
| 76 | -their workflow, and Fossil is intended to be usable by most developers. The | |
| 77 | -underlying technology for the Fossil ticketing system is guaranteed, so to | |
| 78 | -improve it requires only user interface changes. | |
| 74 | +Fossil ticketing system user interface is underdeveloped. | |
| 75 | + | |
| 76 | +On the other hand, pretty much every software developer uses a ticketing system | |
| 77 | +at some point in their workflow, and Fossil is intended to be usable by most | |
| 78 | +developers. That means the ticketing system really needs to be further | |
| 79 | +developed. The underlying technology for the Fossil ticketing system is | |
| 80 | +guaranteed, so to improve it requires only user interface changes. | |
| 79 | 81 | |
| 80 | 82 | Projects relating to the ticketing system include: |
| 81 | 83 | |
| 82 | -* Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. | |
| 84 | +* Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. This is still classified as a "user interface" even though it isn't graphical. | |
| 83 | 85 | * 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. |
| 84 | -* Improving the Fossil web UI for ticketing, which is clunky to say the least | |
| 86 | +* Improving the Fossil web UI for ticketing, which is clunky to say the least. Fossil tries not be a heavy user of Javascript and Javascript libraries, but the wikiedit, chat and Forum code are all more advanced than ticketing, | |
| 87 | +and have UI features that would improve ticketing | |
| 88 | +* If there is an inbound email system as per the previous section "Adding Inbound (Receiving) Email to Fossil", then implement this system for ticketing | |
| 85 | 89 | |
| 86 | 90 | # Look and Feel |
| 87 | 91 | |
| 88 | 92 | Tasks for those interested in graphic/web design: |
| 89 | 93 | |
| 90 | 94 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -63,27 +63,31 @@ | |
| 63 | The Fossil command would reject anything that doesn't look like a bounce it is expecting. |
| 64 | |
| 65 | It is not certain that this design is the best one to address the inbound mail |
| 66 | problem. That is why the first part of this task is to find a workable design. |
| 67 | |
| 68 | ## Work relating to the ticketing system in Fossil |
| 69 | |
| 70 | The Fossil SCM project uses tickets in a [somewhat unusual manner](https://fossil-scm.org/home/reportlist) |
| 71 | because the social programming |
| 72 | model has evolved to often use the Fosum instead. Other Fossil-using projects |
| 73 | use tickets in a more traditional report-a-bug manner. So this means that the |
| 74 | Fossil ticketing system user interface is underdeveloped. On the other hand, |
| 75 | pretty much every software developer uses a ticketing system at some point in |
| 76 | their workflow, and Fossil is intended to be usable by most developers. The |
| 77 | underlying technology for the Fossil ticketing system is guaranteed, so to |
| 78 | improve it requires only user interface changes. |
| 79 | |
| 80 | Projects relating to the ticketing system include: |
| 81 | |
| 82 | * Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. |
| 83 | * 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. |
| 84 | * Improving the Fossil web UI for ticketing, which is clunky to say the least |
| 85 | |
| 86 | # Look and Feel |
| 87 | |
| 88 | Tasks for those interested in graphic/web design: |
| 89 | |
| 90 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -63,27 +63,31 @@ | |
| 63 | The Fossil command would reject anything that doesn't look like a bounce it is expecting. |
| 64 | |
| 65 | It is not certain that this design is the best one to address the inbound mail |
| 66 | problem. That is why the first part of this task is to find a workable design. |
| 67 | |
| 68 | # Work relating to the ticketing system in Fossil |
| 69 | |
| 70 | The Fossil SCM project uses tickets in a [somewhat unusual manner](https://fossil-scm.org/home/reportlist) |
| 71 | because the social programming |
| 72 | model has evolved to often use the Forum instead of ticketing. Other Fossil-using projects |
| 73 | use tickets in a more traditional report-a-bug manner. So this means that the |
| 74 | Fossil ticketing system user interface is underdeveloped. |
| 75 | |
| 76 | On the other hand, pretty much every software developer uses a ticketing system |
| 77 | at some point in their workflow, and Fossil is intended to be usable by most |
| 78 | developers. That means the ticketing system really needs to be further |
| 79 | developed. The underlying technology for the Fossil ticketing system is |
| 80 | guaranteed, so to improve it requires only user interface changes. |
| 81 | |
| 82 | Projects relating to the ticketing system include: |
| 83 | |
| 84 | * Improving the [Fossil cli for tickets](https://fossil-scm.org/forum/forumpost/d8e8a1cf92) which is confusing, as pointed out in that ticket. This is still classified as a "user interface" even though it isn't graphical. |
| 85 | * 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. |
| 86 | * Improving the Fossil web UI for ticketing, which is clunky to say the least. Fossil tries not be a heavy user of Javascript and Javascript libraries, but the wikiedit, chat and Forum code are all more advanced than ticketing, |
| 87 | and have UI features that would improve ticketing |
| 88 | * If there is an inbound email system as per the previous section "Adding Inbound (Receiving) Email to Fossil", then implement this system for ticketing |
| 89 | |
| 90 | # Look and Feel |
| 91 | |
| 92 | Tasks for those interested in graphic/web design: |
| 93 | |
| 94 |