DRAFT: Fedeproxy is written in Go to share code with Gitea

Yes, this was poorly phrased of me, and was the way I understood. Good to mention explicitly that it happens in parallel wrt building other forge (Gitlab) interoperability.

Yeah, we meant to say the same, once again I could have expressed it better. You might say that Gitea after “independence stage” is in a slightly different role. They go from tight participants to the role of client / consumer of FedeProxy (though can still contribute as actively as before).


Good title, good text. I don’t know where you intend to publish (blog?). There are some slight improvement suggestions in terms of structure and language use…

You might add H2 paragraphs, and restructure with essence / TL;DR summary first e.g.:

  • Intro text (no header needed): “We have made some important decisions on the FedeProxy project direction. Instead of bootstrapping an entirely new codebase, we decided […]” and follow with the bullet list.
  • H2 par “How we got there”. First four paragraphs + first bullet list here.
  • H2 par “Where Gitea fits in”. “A large part of the Gitea codebase […] A concrete example […]”
  • H2 par “Impact and way forward”. Last paragraph here.

I would strongly advice to turn “I”'s into “we” and refer in 3rd person to yourself. You already sought consent on these decisions, so you can talk in narrative voice representing the entire community. You can also sign off that way “FedeProxy Community, Loïc Dachary”. That will make feel the project more inclusive, collectively owned.

1 Like