Note about gitea functionality on opendev.org
We seem to semi regularly get questions about why we don't use features like Gitea's issue tracker and wiki. Add that to the opendev.org front page FAQ. Change-Id: Ie5c4602741dcdb9cc4e87b9286a8f6b8b7ed7934
This commit is contained in:
parent
f27825d44e
commit
d679a9e197
@ -56,6 +56,9 @@
|
||||
<h2 id="what-if-i-dont-like-gerrit-and-would-prefer-insert-tool-here">What if I don’t like Gerrit and would prefer (insert tool here)?</h2>
|
||||
<p>We’ve got a fair bit of experience with the existing toolset and adding new tools for which we’ve already got an answer is currently out of scope. We think the existing tools (like Gerrit) work well, and should only get better as we update them. The system is able to scale because we do not need multiple implementations of different software that solve similar problems.</p>
|
||||
|
||||
<h2 id="why-cant-we-use-giteas-issue-tracker-and-wiki">Why can't we use Gitea's issue tracker and wiki?</h2>
|
||||
<p>For scaling and redundancy purposes we are actually running a number of independent Giteas behind a load balancer. We can keep git repos in sync from Gerrit reasonably well, but the issue tracker and wiki functionality would need another level of state syncing. Once Gitea can be run as a proper cluster this may change, but until then the functionality is limited.</p>
|
||||
|
||||
<h1 id="contact-info">Contact info</h1>
|
||||
<p>These will be updated when moved to their new OpenDev locations</p>
|
||||
<ul>
|
||||
|
Loading…
Reference in New Issue
Block a user