Derek, Thanks!
1. Any conventions as far as forking/branch names? 2. Got it - I just use my local repo as my sandbox. Are there any conventions in the PF community as far the IDE to use, the ways to setup test scenarios, etc? 3. Self-explainatory. I guess git pull in this case is the accepted merge mechanism, right? Cheers, Boris. On Fri, May 29, 2015 at 9:32 AM, Derek Wuelfrath <[email protected]> wrote: > Boris, > > 1. Fork the PacketFence repo from Github. ( > https://github.com/inverse-inc/packetfence#fork-destination-box) > 2. Do the changes in your forked repo of PacketFence > 3. Submit a pull-request ! > > Cheers! > dw. > > -- > Derek Wuelfrath > [email protected] :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110) > Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and > PacketFence (www.packetfence.org) > > On May 28, 2015 at 17:28:05, Boris Epstein ([email protected]) wrote: > > Hello all, > > I am considering going over the PF code and trying to fix some issues I am > encountering. So I am wondering what the procedures are for introducing the > changes - i.e., git labeling/branching conventions, etc. > > Thanks. > > Boris. > > ------------------------------------------------------------------------------ > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > >
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
