This'll be a controversial answer, but this sounds like exactly the sort of thing an LLM should be able to do reasonably well, whether by the human writing the docs and the LLM updating the code accordingly or by the human writing the code and the LLM updating the docs accordingly.
I've been gradually migrating my Git repos to Fossil as I've been touching them. Been quite happy with it.
There are only a couple things that I miss:
- Grouping repos together into a combined project. I'd love to be able to have a single Fossil server/instance with a single set of users, wiki pages, tickets, etc. but multiple independent codebases. Closest I've gotten to that is to simply have multiple independent branches instead of a single trunk (example: https://fsl.yellowapple.us/avorion/home), and it's worked surprisingly well, but it's clear Fossil wasn't designed with this workflow in mind, so there are some rough edges with it (albeit minor and easy to work around).
- Compatibility with things that assume you're using Git. Being able to export to Git helps a lot here, but it's still extra steps. Ideal solution here would be for the Fossil server to be able to double as a Git forge and present repos accordingly, such that I can point things like CI/CD pipelines or Terragrunt module calls or whatever directly to the Fossil repo itself over the Git interface those things expect instead of having to setup a Git forge manually and somehow synchronize everything w.r.t. access controls.
- An equivalent to Git's submodules. This would IMO help address the “grouping repos together into a combined project” case as well.
There are login-group options which lets you have a single sign on with a group of repos, To unify the other bits it looks like it would be possible to change the main menu links to the central repo(in the web settings).
Never wanted to do what you want but it sounds possible
set up the fossil server on a directory of repos probably with --repolist to get a list
fossil server --repolist /var/fossil/
get all repos in the same login-group
change the menus in each repo to point to the core repo. Based on some quick tests I suspect a full http:// url is required.
- Forum /forum {@2 3 4 5 6}
+ Forum https://mydomain.org/core/forum {@2 3 4 5 6}
The much easier and more reasonable solution here would be for the RPi Foundation to ignore RMA requests for boards not bought from them or an authorized reseller.
Designers having that artistic taste, and clients lacking it, is exactly why I don't think generative AI is going to do much to replace (skilled) designers anytime soon. Likewise for other creative professions, and indeed for knowledge work in general.
Taste is a great solution for abundance, so I agree. Also, there's definitely a rubberband effect where products & designs need to differentiate on their design to stand out in a homogenous world, and you truly do need creative professionals having that judgment. Even using AI as a tool, you have to have the sayable vocabulary (at the very least) to agitate the aesthetic status quo.
And low-skill graphic design had already been mostly replaced by Canva, so I don't think AI is really having as much impact on the design industry as people might suppose.
I think we ALREADY at the point when AI is capable to replace like 99.7% of designers. It is only a question of market inertia and personal brands that prevent it from happening right now.
The lack of water is related to the lack of hydrogen; you'd need to find a hydrogen source to synthesize water.
Lots of oxygen in moon rocks, though, so in addition to directly importing icy asteroids, importing hydrocarbon-rich asteroids would also help (with the added bonus of carbon also being something scarce on the Moon).
reply