git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Robin Shen <robin@onedev.io>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>, jgit-dev@eclipse.org
Subject: Re: Introducing OneDev - an open source git server with interesting features
Date: Mon, 7 Jan 2019 14:26:31 -0800	[thread overview]
Message-ID: <20190107222631.GB192553@google.com> (raw)
In-Reply-To: <SG2PR04MB3205E9C83085CFF2F426FE65B9890@SG2PR04MB3205.apcprd04.prod.outlook.com>

+jgit-dev
Hi Robin,

Robin Shen wrote:

> Dear git users,
>
> OneDev is an open source git server with interesting features such
> as language aware code search/navigation, issue workflow
> customization, free source/diff comment and discussion, etc.
>
> It is using MIT license and hope it can be useful to someone.  Learn
> more at https://onedev.io

Thanks for writing!  Looking at
https://github.com/theonedev/onedev/blob/master/core/pom.xml, it
appears this is a web interface that uses JGit for Git support.

Can you say a little about how it compares to Gitblit
<http://gitblit.com>, Phabricator, Gerrit, and other interfaces?

Also, if you have time for it, mind saying a little about what your
experience using JGit has been like?  Any thoughts about what worked
well and what didn't work as well?  This can help both the Git and
JGit projects:

- Git, since it can help us learn from JGit's successes and mistakes
- JGit, since it's not too late to make the API better :)

Sincerely,
Jonathan

  reply	other threads:[~2019-01-07 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 11:42 Introducing OneDev - an open source git server with interesting features Robin Shen
2019-01-07 22:26 ` Jonathan Nieder [this message]
     [not found]   ` <SG2PR04MB320586447FF738E008C373FFB9840@SG2PR04MB3205.apcprd04.prod.outlook.com>
2019-01-10  7:34     ` Robin Shen
2019-01-10 21:30     ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190107222631.GB192553@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jgit-dev@eclipse.org \
    --cc=robin@onedev.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).