Fossil SCM
Minor additions to gsoc-ideas.md.
Commit
8b453eb20740e8383bc6fec4c38c9157111783b9568e439a3d3ef48b2b54f535
Parent
d095066ea3db068…
1 file changed
+7
-3
+7
-3
| --- www/gsoc-ideas.md | ||
| +++ www/gsoc-ideas.md | ||
| @@ -1,6 +1,6 @@ | ||
| 1 | -# Project Ideas for Google Summer of Code | |
| 1 | +# Project Ideas for Google Summer of Code 2021 | |
| 2 | 2 | |
| 3 | 3 | This list was made for the Fossil project's application for [Google Summer of |
| 4 | 4 | Code](https://summerofcode.withgoogle.com/) in 2021. GSoC pays students to |
| 5 | 5 | contribute to free software projects during the Northern Hemiphere summer. If |
| 6 | 6 | you are a student, you will be able to apply for GSoC starting March 29th 2021. |
| @@ -14,11 +14,11 @@ | ||
| 14 | 14 | |
| 15 | 15 | * Complete per-feature CSS facilities in [the Inskinerator](https://tangentsoft.com/inskinerator/dir) and add features to the Inskinerator |
| 16 | 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 | 17 | * Allow diffing of Forum posts |
| 18 | 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 analysis | |
| 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 | 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 |
| 21 | 21 | * Create a [Pandoc](https://pandoc.org) filter that handles Fossil-style Markdown |
| 22 | 22 | * Create a [Pandoc filter that handles Pikchr](https://groups.google.com/g/pandoc-discuss/c/zZSspnHHsg0?pli=1) (Pikchr can be used with many kinds of layout, not just Markdown) |
| 23 | 23 | * Editor integration: [improve the Fossil VSCode plugin](https://marketplace.visualstudio.com/items?itemName=koog1000.fossil) or [create a Fossil plugin for Eclipse](https://marketplace.eclipse.org/taxonomy/term/26%2C31) |
| 24 | 24 | |
| @@ -43,11 +43,15 @@ | ||
| 43 | 43 | The Fossil data model concepts are simple, but the implications are quite subtle and impressive. The data model |
| 44 | 44 | is designed to [endure for centuries](./fileformat.wiki), |
| 45 | 45 | be [easily accessible](./fossil-v-git.wiki#durable), and is [non-relational](./fossil-is-not-relational.md). |
| 46 | 46 | You will need to understand the data model to work on the following tasks: |
| 47 | 47 | |
| 48 | -* Add the ability tag non-checkin artifacts, something the CLI and UIs do not although the data model does. One suggestion is that this is how xattrs could apply to file blobs. This could also relate to the RBAC system. | |
| 48 | +* Add the ability to tag non-checkin artifacts, something supported by | |
| 49 | + the data model but not the current CLI and UIs. This would open the | |
| 50 | + door to numerous new features, such as "sticky" forum posts and | |
| 51 | + per-file extended attributes. This could also relate to the RBAC | |
| 52 | + system. | |
| 49 | 53 | * Implement "merge" and "stash" in libfossil |
| 50 | 54 | * Analyse the different kinds of [split/export/shallow clone](https://fossil-scm.org/forum/forumpost/1aa4f8ea8c6f96) use cases for Fossil including [complete bifurcation](https://fossil-scm.org/forum/forumpost/6434a06871). There are many proposals, relating to many different use cases, and a good analysis would help us to work out what should be implemented, and what should be implemented in Fossil and what is instead a libfossil wrapper |
| 51 | 55 | |
| 52 | 56 | # Fossil is cool |
| 53 | 57 | |
| 54 | 58 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -1,6 +1,6 @@ | |
| 1 | # Project Ideas for Google Summer of Code |
| 2 | |
| 3 | This list was made for the Fossil project's application for [Google Summer of |
| 4 | Code](https://summerofcode.withgoogle.com/) in 2021. GSoC pays students to |
| 5 | contribute to free software projects during the Northern Hemiphere summer. If |
| 6 | you are a student, you will be able to apply for GSoC starting March 29th 2021. |
| @@ -14,11 +14,11 @@ | |
| 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 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 |
| 21 | * Create a [Pandoc](https://pandoc.org) filter that handles Fossil-style Markdown |
| 22 | * Create a [Pandoc filter that handles Pikchr](https://groups.google.com/g/pandoc-discuss/c/zZSspnHHsg0?pli=1) (Pikchr can be used with many kinds of layout, not just Markdown) |
| 23 | * Editor integration: [improve the Fossil VSCode plugin](https://marketplace.visualstudio.com/items?itemName=koog1000.fossil) or [create a Fossil plugin for Eclipse](https://marketplace.eclipse.org/taxonomy/term/26%2C31) |
| 24 | |
| @@ -43,11 +43,15 @@ | |
| 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 | You will need to understand the data model to work on the following tasks: |
| 47 | |
| 48 | * Add the ability tag non-checkin artifacts, something the CLI and UIs do not although the data model does. One suggestion is that this is how xattrs could apply to file blobs. This could also relate to the RBAC system. |
| 49 | * Implement "merge" and "stash" in libfossil |
| 50 | * Analyse the different kinds of [split/export/shallow clone](https://fossil-scm.org/forum/forumpost/1aa4f8ea8c6f96) use cases for Fossil including [complete bifurcation](https://fossil-scm.org/forum/forumpost/6434a06871). There are many proposals, relating to many different use cases, and a good analysis would help us to work out what should be implemented, and what should be implemented in Fossil and what is instead a libfossil wrapper |
| 51 | |
| 52 | # Fossil is cool |
| 53 | |
| 54 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -1,6 +1,6 @@ | |
| 1 | # Project Ideas for Google Summer of Code 2021 |
| 2 | |
| 3 | This list was made for the Fossil project's application for [Google Summer of |
| 4 | Code](https://summerofcode.withgoogle.com/) in 2021. GSoC pays students to |
| 5 | contribute to free software projects during the Northern Hemiphere summer. If |
| 6 | you are a student, you will be able to apply for GSoC starting March 29th 2021. |
| @@ -14,11 +14,11 @@ | |
| 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 |
| 21 | * Create a [Pandoc](https://pandoc.org) filter that handles Fossil-style Markdown |
| 22 | * Create a [Pandoc filter that handles Pikchr](https://groups.google.com/g/pandoc-discuss/c/zZSspnHHsg0?pli=1) (Pikchr can be used with many kinds of layout, not just Markdown) |
| 23 | * Editor integration: [improve the Fossil VSCode plugin](https://marketplace.visualstudio.com/items?itemName=koog1000.fossil) or [create a Fossil plugin for Eclipse](https://marketplace.eclipse.org/taxonomy/term/26%2C31) |
| 24 | |
| @@ -43,11 +43,15 @@ | |
| 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 | You will need to understand the data model to work on the following tasks: |
| 47 | |
| 48 | * Add the ability to tag non-checkin artifacts, something supported by |
| 49 | the data model but not the current CLI and UIs. This would open the |
| 50 | door to numerous new features, such as "sticky" forum posts and |
| 51 | per-file extended attributes. This could also relate to the RBAC |
| 52 | system. |
| 53 | * Implement "merge" and "stash" in libfossil |
| 54 | * Analyse the different kinds of [split/export/shallow clone](https://fossil-scm.org/forum/forumpost/1aa4f8ea8c6f96) use cases for Fossil including [complete bifurcation](https://fossil-scm.org/forum/forumpost/6434a06871). There are many proposals, relating to many different use cases, and a good analysis would help us to work out what should be implemented, and what should be implemented in Fossil and what is instead a libfossil wrapper |
| 55 | |
| 56 | # Fossil is cool |
| 57 | |
| 58 |