On 10/31/2016 08:44 AM, Gustaf Neumann wrote: > many of us use naviserver since many years, so we get blind to > things, which pop up immediately to the eye of a new user.
I understand and agree; observing a new user's responses can be very informative. > Also keep in mind, that the code and documentation was written > by people with many mother tongues. Whatever languages are used, natural and synthetic (programming), it seems like a reasonable goal to strive to compose expressions in those languages in a way that is semantically meaningful, grammatically coherent, and syntactically well-formed. While I am reading the Naviserver documentation and source code (that's the expensive part), I can keep notes and then try to provide some form of useful feedback. > But contributing is easy: in case someone finds something to improve > (from wording of README files to docs and code), just clone the project > on bitbucket, improve the issues in your clone and issue a pull request. I am somewhat new to Mercurial and Bitbucket but I've set up an account and cloned the repository. Does anyone know of a tutorial or blog that describes a work-flow, process, or development methodology that fits this situation? There is the canonical Bitbucket repository: https://bitbucket.org/naviserver/naviserver/ And my clone of that repository: https://bitbucket.org/hanzer/nsclone At this point, do I 'hg pull' from /naviserver, then modify and 'hg push' to /nsclone? Any clarification or useful references will be much appreciated! ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
