CONTRIBUTING_HOWTO.txt and some basic questions
My team has been working with nfs-ganesha for some time. This week I started sending patches and paying more attention to CONTRIBUTING_HOWTO.txt First of all, the home page says the community maintains an active, open IRC channel on Libera #ganesha. Most of our developers keep in touch on this channel. I recently posted messages there but have not seen any replied (*). Is that channel actively used? It that the best way to ask questions? or is it this mailing list? Also, every time I connect to that IRC channel I get the message "NFS-Ganesha V5-dev.5 released! V4.4.1 is the current stable branch!". As I understand it, https://github.com/nfs-ganesha/nfs-ganesha/wiki/Release-Cycle#current-stable... says V5.5 is the current stable release. The IRC message seems outdated and is causing confusion. And now a question about CONTRIBUTING_HOWTO.txt: It says "Establish from the other developers which branch of whose repository is the best to work in. Create an account on github.com, login and view that developers repository. Click "Fork" on the top right to create a copy of that repository. Let's say your name is "Paul Sheer" (replace "paul", "p_sheer" and "paulsheer" with your own name below), and say the developer who owns the repository is named Code Leader and his github.com login is "codeleader". Now let's say the code branch is "new-unstable-dev-project". Then it gives an example: "git clone https://github.com/codeleader/nfs-ganesha.git --branch new-branch ...... The current (as of 2019-02-07) branch for development is: git clone https://github.com/nfs-ganesha/nfs-ganesha.git --branch next". And the question is: Do I really need to clone from some developer's repository? (*) I hope I'm not coming across as super impatient. I just want to make sure I understand how to work with the nfs-ganesha community.
Frank, I think I fixed the issue that caused your replies earlier today to only go to me and not to the mailing list. Would you be so kind to re-reply here? .... for the benefit of other readers.
participants (1)
-
David Rieber