On Tue, Feb 11, 2020 at 2:42 PM Martin Morgan wrote:
>
> (sending again from / to an appropriate email address, sorry for the noise)
>
> Henrik -- I appreciate the ease with which gitea can be deployed in this
> one-off solution but cynically think that a real deployment would introduce
> signif
(sending again from / to an appropriate email address, sorry for the noise)
Henrik -- I appreciate the ease with which gitea can be deployed in this
one-off solution but cynically think that a real deployment would introduce
significant work, e.g., re-tooling our approach to new package addition
I wanna revive this old thread.
I've used Gitea for internal git/issue trackers at the UCSF for quite
a while now and it works really well. I've also looked into how easy
it would be to use it for pure code exposure and it's pretty
straightforward. Gitea even has built-in tools for automatically
There has been previous discussion about this.
https://stat.ethz.ch/pipermail/bioc-devel/2017-September/011455.html
It is not in our short-term plans to offer a full on-line solution, but
not impossible in a longer context.
Martin
On 10/26/2017 03:01 AM, Stian Lågstad wrote:
I would very
I would very much appreciate this as well. Issue tracking and communicating
with users directly in the repository would be very nice, as well as the
ability to reference source code directly.
On Thu, Oct 26, 2017 at 8:50 AM, Henrik Bengtsson <
henrik.bengts...@gmail.com> wrote:
> Are there any pl
Are there any plans for an online interface to https://git.bioconductor.org/?
I've recently looked into solutions for an open-source in-house
"GitHub/GitLab"-ish, and I've found https://gitea.io/ to be really
nice. It is very easy to install. It has support for various common
user authentication