robinshen

GitLab tries to include all tools in a single package, while this tool emphasizes on code management. It provides some tools making code browsing and navigation much easier for daily review purpose.

I often end up asking questions in GitHub issues, not a good place for discussions though. Finally someone offered this service. Nice!

We do that in backend with a hand written, simple parser just to pick up information we needed. And it is fast (can index all JDK8 source symbols in seconds).

I checked Gerrit before and like its philosophy of enforcing atomic commits and linear history, but I do not like its way of adding special change id in commit message and push to refs/for/master. That makes new users confusing and makes it difficult to follow. So I build a gerrit gatekeeper in GitPlex to enforce same rule in pull request, that is: when you need to update a pull request, you must amend your previous commit followed by a force push. No special change-id or the magic refs/for/master will be necessary.

This is convenient. Thanks for the effort!

We also try to keep things simple. Without gatekeepers, the pull request workflow is quite the same as GitHub. Advanced users can explore gatekeepers to achieve much flexible workflows. Hackers may also write plugins to add their own gatekeepers in future releases. 8)

We are a Java shop and created the tool to manage our own code initially. Our next priority is to make it supporting more languages.

Thanks for the ideas. While I agree with you that desktop IDE is a good place for design and architecture level reviews, having a lightweight web "IDE" will be beneficial as it does not require you to switch your local workspace to particular revisions for review.

Also I often find myself need to copy code from some old revisions, in that case, I just visit our web "IDE", find desired revisions with revision search helper, and open desired symbols to copy relevant code out.

Sticky comment is actually another form of git blame, and will be available in future versions of GitPlex.

Missed description of the integration preview part, now get it added: https://www.pmease.com/gitplex#preview-integration

Thanks for pointing this out. Will get that fixed. Not a human language expert, but hope I can do better in computer languages, :)

Thanks for the link, bookmarked it for studying, :)

GitPlex can show history of any path (a file or directory) quickly via history button, and from there you can even refine the history (search for certain tags, commits made by certain people, etc) of the file, and once you get to the point, you can either view content of the file, or hit the compare button to compare with your previous browsed copy. An example here: http://gitplex.pmease.com/demo/android-framework-base/commit...

The next step is to support major languages, and C# is definitely on our road map.

Yes that is true. We build this tool with easy deployment in mind. And we've devoted a lot of our effort to performance. Just check the linux repository for instance (http://gitplex.pmease.com/demo/linux), GitPlex is able to calculate latest commits of many sub folders quickly, compared to decades needed by other tools, :) If your repository is not as large as linux, a 1 cpu machine with 1G memory allocated to GitPlex will be more than enough.

Looks like many GitPlex downloads are going on... And this happens since two hours ago when I posted this news. The first time I've experienced with HN death hug, 8) Another thing in my agenda now (to optimize the web site and download).

Is it something like this? http://gitplex.pmease.com/demo/android-framework-base/files?...

You may also put annotations on any diffs: http://gitplex.pmease.com/demo/android-framework-base/commit...

We solve this via gatekeeper rules (repository administrator defines rules such as who needs to review which part of code, or whose code needs to be reviewed (intern team for instance needs to be reviewed by core team etc), or what commit message rule should be followed etc.

A typical review process suggested by GitPlex can be found here: http://wiki.pmease.com/display/GP10/Iterative+Review+with+Pu...

I think GitPlex meets most of the requirement here if you are writing Java code (and more languages are being added). Unlike other tooks, it does not place any requirements on project build system (Maven, Gradle, etc) and can work on any project containing supported languages.

Checkout android code base for instance: http://gitplex.pmease.com/demo/android-framework-base/files?...

I actually created this tool to suffice my own needs when browsing history of QuickBuild source code.