Fossil SCM
Move CSS task to new Look and Feel section
Commit
092a7fb796a3b37df8a7dd1e6245aa65b29a9b1dfacbaeaa8fa0471ac7a15b37
Parent
ea2f26aadc03182…
1 file changed
+1
-1
+1
-1
| --- www/gsoc-ideas.md | ||
| +++ www/gsoc-ideas.md | ||
| @@ -10,11 +10,10 @@ | ||
| 10 | 10 | have an identical implementation of the Fossil data model, are 100% compatible in terms of |
| 11 | 11 | data access since they use the same SQL, and are 100% binary compatible in terms of on-disk storage. |
| 12 | 12 | |
| 13 | 13 | ## General Features |
| 14 | 14 | |
| 15 | -* Complete per-feature CSS facilities in [the Inskinerator](https://tangentsoft.com/inskinerator/dir) and add features to the Inskinerator | |
| 16 | 15 | * Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history) |
| 17 | 16 | * Allow diffing of Forum posts |
| 18 | 17 | * Develop a test suite for the draft JSON API in libfossil. This JSON API is a way of integrating many kinds of systems with Fossil |
| 19 | 18 | * Re-implement the draft JSON API in libfossil to use the JSON capability in SQLite, now that SQLite has JSON. This is a large project and would start with feasibility analysis |
| 20 | 19 | * Fossil hooks for pipelines with CI/CD such as static analysis, Buildbot, Gerrit, Travis and Jenkins are not well-documented and may need some further development. Make this work better, with configuration examples |
| @@ -63,10 +62,11 @@ | ||
| 63 | 62 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 64 | 63 | cares to dig, require digging into C code to find, and potentially modify, how |
| 65 | 64 | the HTML is generated. |
| 66 | 65 | * Creation of one or more new skins. This does not specifically require any C |
| 67 | 66 | know-how. |
| 67 | +* Complete per-feature CSS facilities in [the Inskinerator](https://tangentsoft.com/inskinerator/dir) and add features to the Inskinerator | |
| 68 | 68 | |
| 69 | 69 | # Tasks Requiring Fossil Data Model Knowledge |
| 70 | 70 | |
| 71 | 71 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 72 | 72 | is designed to [endure for centuries](./fileformat.wiki), |
| 73 | 73 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -10,11 +10,10 @@ | |
| 10 | have an identical implementation of the Fossil data model, are 100% compatible in terms of |
| 11 | data access since they use the same SQL, and are 100% binary compatible in terms of on-disk storage. |
| 12 | |
| 13 | ## General Features |
| 14 | |
| 15 | * Complete per-feature CSS facilities in [the Inskinerator](https://tangentsoft.com/inskinerator/dir) and add features to the Inskinerator |
| 16 | * Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history) |
| 17 | * Allow diffing of Forum posts |
| 18 | * Develop a test suite for the draft JSON API in libfossil. This JSON API is a way of integrating many kinds of systems with Fossil |
| 19 | * Re-implement the draft JSON API in libfossil to use the JSON capability in SQLite, now that SQLite has JSON. This is a large project and would start with feasibility analysis |
| 20 | * Fossil hooks for pipelines with CI/CD such as static analysis, Buildbot, Gerrit, Travis and Jenkins are not well-documented and may need some further development. Make this work better, with configuration examples |
| @@ -63,10 +62,11 @@ | |
| 63 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 64 | cares to dig, require digging into C code to find, and potentially modify, how |
| 65 | the HTML is generated. |
| 66 | * Creation of one or more new skins. This does not specifically require any C |
| 67 | know-how. |
| 68 | |
| 69 | # Tasks Requiring Fossil Data Model Knowledge |
| 70 | |
| 71 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 72 | is designed to [endure for centuries](./fileformat.wiki), |
| 73 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -10,11 +10,10 @@ | |
| 10 | have an identical implementation of the Fossil data model, are 100% compatible in terms of |
| 11 | data access since they use the same SQL, and are 100% binary compatible in terms of on-disk storage. |
| 12 | |
| 13 | ## General Features |
| 14 | |
| 15 | * Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history) |
| 16 | * Allow diffing of Forum posts |
| 17 | * Develop a test suite for the draft JSON API in libfossil. This JSON API is a way of integrating many kinds of systems with Fossil |
| 18 | * Re-implement the draft JSON API in libfossil to use the JSON capability in SQLite, now that SQLite has JSON. This is a large project and would start with feasibility analysis |
| 19 | * Fossil hooks for pipelines with CI/CD such as static analysis, Buildbot, Gerrit, Travis and Jenkins are not well-documented and may need some further development. Make this work better, with configuration examples |
| @@ -63,10 +62,11 @@ | |
| 62 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 63 | cares to dig, require digging into C code to find, and potentially modify, how |
| 64 | the HTML is generated. |
| 65 | * Creation of one or more new skins. This does not specifically require any C |
| 66 | know-how. |
| 67 | * Complete per-feature CSS facilities in [the Inskinerator](https://tangentsoft.com/inskinerator/dir) and add features to the Inskinerator |
| 68 | |
| 69 | # Tasks Requiring Fossil Data Model Knowledge |
| 70 | |
| 71 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 72 | is designed to [endure for centuries](./fileformat.wiki), |
| 73 |