> A basic ticketing system is also provided, not sure it is that far > from trac features... not a must. > It wiki is better than track as people can subscribe for changes, > hence cooperate much better than current state. A few years ago, when I started setting up the community services I discussed the option of using external, hosted services (e.g. SF.net) internally and our CEO strongly disagreed[*] with that approach. I don't think anything has changed on that front since... and there are advantages in the approach we have now, e.g. being able to use the same authentication backend for all of our random services.
That said, the code itself is hosted externally on SF.net, so we have the _option_ of using GitHub for that part. I'd first look at the big picture of how we want to enhance our development processes and then move on to the tools. I hope to have the review of the ACK system ready by next Monday, maybe sooner. That'll give us some hard data which we can use as a basis for further discussion... [*] As in "We will have the community services on our own servers. Period." -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
