Hi Diwaker Good questions! I think.... - At apache we have https://reviews.apache.org , but usually we discuss and review on the dev list or via JIRA issues and commit afterwards. That's fine. - Continuous Integration is important: https://hudson.apache.org/hudson/job/Thrift/ => ruby & go is currently missing:-( - We have the wiki page http://wiki.apache.org/thrift/HowToContribute describing how to contribute - We do not have a nice Logo and web site making our attitude visible: "we talk any language" and "high performance" .... do we have some artists here? - Yes, a wiki page http://wiki.apache.org/thrift/RoadMap is a great idea! - Reliability, performance and interoperability across languages (e.g. THRIFT-847) is the super important topic => Quality, Testing, CI, short Release Cycles, Refactoring , etc. - I agree with Bryan: "We don't have any "official" coding style guidelines, though I'd say pretty much every library (and the compiler) have an implicit set of guidelines they follow."
Greetings & Thank you ALL for making Thrift better! roger -----Ursprüngliche Nachricht----- Von: Diwaker Gupta [mailto:[email protected]] Gesendet: Donnerstag, 24. Februar 2011 19:59 An: [email protected] Betreff: Development process Is there a documented (or at least well understood) development process for Thrift? In particular: * How is code reviewed? I've seen people attach patches to Jira, but thats not very convenient and makes the review process cumbersome and less transparent. I noticed some people using http://codereview.appspot.com/. What do people feel about a dedicated ReviewBoard or Gerrit instance? * Is there a style/formatting guide for the code? * Most of the development seems to be driven by Jira issues. Is there any prioritization or roadmap on top of that? Diwaker
