I was digging into it in order to learn why the <pre> tags are mysteriously only 720px wide (the answer seems to be the display:grid on the body; unchecking it widens things as expected)
while pasting that link I noticed that the URLs do not have any "as of this commit" information in them, making it hard to place the sender and the receiver on the same view
I do appreciate this is your project for your needs, but wanted to bring them to your attention only as "for your consideration"
Thanks for your questions. Yes the project is "for my needs" but I want to move it to "our needs".
the CSS you look at is the CSS that will be used for the project you create in the forge by default. I use https://simplecss.org/ it is not here to be changed only to be added in the GitRoot binary at build time. But in gitroot you can use any CSS you want for your project https://gitroot.dev/doc/how-tos/customize_web.html
yes you are not the first to say that to me, but it's linked to first point: I use a CSS predefined. Maybe in future or if a contributor want to, a special GitRoot CSS can be made.
yes, GitRoot is young and lot of features are missing. But GitRoot is not made to be viewed on web. Web is just a plugin. GitRoot make git forge viewable and configurable through git. So you don't have files for every commit in web, but you have issues, boards, grafts (contributions/PR/Mr) in git. That is the true power of GitRoot.
Pretty cool! I've been toying with writing my own git forge too, and this is giving me some ideas.
GitHub has long been not only the biggest player, but also the most influential forge. You can feel its influence in the design of other forges like Forgejo and Gitlab. With GitHub's fall, I'm very excited to see how people stray from GitHub's model and forge their own paths. I think there's a lot of room for innovation in this space!
No there is no policy today. Because I haven't contributors (2 one time contributors), 99,999% of the code is done by me.
I personnaly don't use llm for code and I'm against them. But, to be honest, if someone make a graft reasonably small even if llm was used, I'm not sure I'll refuse it.
It really breaks my heart to have to use them. But between that and doing nothing, I’ve chosen to use them as little as possible. In future, with a community, i hope to be able to banish them (even if I think economic will do the job before me 🤣). I have a lot of article in my todo list to explain the philosophie, security, future... And what stop me writing them is to know that an llm will resentence/fix typo or translate them.
Thanks so much and I appreciate your approach. Sorry no one's responded about proofreading help. I've done technical proof reading in the past. Feel free to contact me for future posts. If I have time, I'd be happy to help.
I also encourage you to write down those ideas, or even codify them into a policy, before it would be difficult or controversial to add them. Either way, excited to see where your project goes 🙂
manland | 8 hours ago
Hi here! I'm the creator of GitRoot, if you have any questions, please feel free to ask ;)
mdaniel | 5 hours ago
I have 3 related questions:
<pre>tags are mysteriously only 720px wide (the answer seems to be thedisplay:gridon the body; unchecking it widens things as expected)I do appreciate this is your project for your needs, but wanted to bring them to your attention only as "for your consideration"
manland | 4 hours ago
Thanks for your questions. Yes the project is "for my needs" but I want to move it to "our needs".
nick4 | 10 hours ago
Pretty cool! I've been toying with writing my own git forge too, and this is giving me some ideas.
GitHub has long been not only the biggest player, but also the most influential forge. You can feel its influence in the design of other forges like Forgejo and Gitlab. With GitHub's fall, I'm very excited to see how people stray from GitHub's model and forge their own paths. I think there's a lot of room for innovation in this space!
heavyrain266 | 9 hours ago
Gitea used to be almost 1:1 clone of GitHub’s old frontend that Forgejo simply inherited when they forked Gitea.
edwardloveall | 7 hours ago
@manland do you have an LLM policy or guidance on whether or not you allow/disallow contributions created with an LLM?
manland | 6 hours ago
No there is no policy today. Because I haven't contributors (2 one time contributors), 99,999% of the code is done by me.
I personnaly don't use llm for code and I'm against them. But, to be honest, if someone make a graft reasonably small even if llm was used, I'm not sure I'll refuse it.
If you look carefully you will find trace of llm in my communication. English is not my mother tongue and it's hard for me to explain GitRoot without them. I have asked for help in the past https://gts.gitroot.dev/@forge/statuses/01KFNWDKSZBEHTC16N5G02HJZ6 or https://gts.gitroot.dev/@forge/statuses/01KTP30NTY9FK91Q9B5Z9B4M52 but nobody come.
It really breaks my heart to have to use them. But between that and doing nothing, I’ve chosen to use them as little as possible. In future, with a community, i hope to be able to banish them (even if I think economic will do the job before me 🤣). I have a lot of article in my todo list to explain the philosophie, security, future... And what stop me writing them is to know that an llm will resentence/fix typo or translate them.
// TODO this comment should be a blog article!
edwardloveall | 4 hours ago
Thanks so much and I appreciate your approach. Sorry no one's responded about proofreading help. I've done technical proof reading in the past. Feel free to contact me for future posts. If I have time, I'd be happy to help.
I also encourage you to write down those ideas, or even codify them into a policy, before it would be difficult or controversial to add them. Either way, excited to see where your project goes 🙂
rrampage | 8 hours ago
Love the use of Tinygo for compiling go plugins to WASM!
manland | 8 hours ago
Yes tinygo is amazing, there is also SDK for AssemblyScript and rust. I'm developing the zig one https://gts.gitroot.dev/@forge/statuses/01KXRJ1GE0CNEQHVQ0R41D7V06