> Setting up yourself to use Gerrit is a PITA, and it really assumes you > are a competent enough git user to start with, and even then it still is > pain. Gerrit is a tool for developers to use to review patches, but it > is definitely not a tool report bugs and issues with.
As maintainers with very limited resources our primary concern is to support those contributors that have patches and are willing to do the work. Gerrit has been a huge help and success in this regard. Look at the number an quality of commits we're getting compared to previously. Without Gerrit I would have abandoned OpenOCD. If you want to work with open source, then I take git is a skill that you have to teach yourself as a professional these days. There are lots of people who are unable or unwilling to do so. If we had lots more resources there are many things we could do: - run bug tracker - write better documentation - write a testsuite and add a hardware test farm that runs regression tests on all submitted patches - manage SWD effort If someone wants to do the above we would of course be delighted! -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 http://www.zylin.com/ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
