Dear Saros Developers, during the last months some of you might have noticed that Saros is lacking a useful specification. Every once in a while I heard someone say something like "We need to define our intended behavior!" -- and you were right.
As discussed in yesterday's stand-up meeting I set up Wiki topic with a rough structure and a few questions to be answered [1]. We agreed on the following procedure: * The first step is a high-level specification that covers all areas of Saros. It's a Wiki page: feel free to add content and subpages! * Every time someone stumbles upon an ambiguity and feels an urgent need for specification, he/she keeps this topic in mind and we are going to discuss it after our stand-up. Afterwards we write down both the results and the decisions made on the way, put them on the Wiki page and share them on dpp-devel. * There will be no new features without a specification. The author is responsible for embedding his/her work in the existing specification. Best wishes, Franz Links: [1] https://www.inf.fu-berlin.de/w/SE/DPPSpecification ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
