There is an opinion that WANdisco tries to gain market share by pretending they are the major driving force behind the open source communities that support projects like Subversion and Trac. But in case of Trac the marketing efforts can be wasted, because IIUC none of WANdisco employers have a trail of commits to Trac core. So, the best way to build up a "reputation" is to place WANdisco members name on the official page of Apache Software Foundation with Trac and Apache logos and a new project name announcement. And then include this new project name in all marketing materials.
The strategy that hurts an ecosystem. Nothing prevents WANdisco from contributing back to Trac, but they didn't and probably don't want to, so I believe the true motives are somewhat different from the goals of community. Somebody said that there is no time to review changes from Wd members. This problem can be solved without Apache projects and all that buzz. First, Wd can stash the changes much like everyone else does and just remove them from their own branch when the changes are merged. It's just a matter of coding culture and maturity of company processes to be able to do so. Second, it could speed up the review process by compensating time of Trac core developers without buying and restricting them to be a flag bearers of Wd. There is a legal entity - Edgewall Software, that's year after year supported this project (unlike Wd), so nobody would really object if you could try to cooperate with them first instead of jumping into your own public project and calling for everyone to move. -- anatoly t. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
