Mike Fedyk wrote: > Ok, you want comments. I have posted three versions of my zaptel > configure fix patch and haven't received one comment on it in review. I > want faster response from the developers for possible fixes.
It's possible that few people are using zaptel hardware (or if they are, they might not consider themselves qualified to comment at a developer level). Don't worry, I face the same problem with chan_capi ;-) > As for svn, keep it and use https instead of ssh for access. svn with > https is easier to use and just as secure. svk is an option if any > developer wants a local copy of the code to do private commits on a > laptop while offline. +1 > As for trac, allow anon to create tickets, but require accounts for wiki > changes. trac accounts can be merged with other accounts but it is more > important to get new trac accounts working now, not later. +1 > Also I've never liked it where there are multiple wikis. Use the trac > wiki, it can include references to code and is more useful than a normal > wiki because of that. +1. This is a software development project, so a wiki that ties into the SCM platform is a good idea, IMHO. Other wikis are fine for non-development-related projects. > My general opinion is to do whatever it takes to allow people to work > *now* and not letting "perfect" get in the way of "good enough for now". Maybe a code freeze is in order? Stop adding new features, and spend all available resource on squashing the last remaining known bugs for a release. _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
