Re: SRS document, and offer to compose 1
Apostolos Syropoulos <[email protected]>
| Newsgroups | gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <CAMgK+EQazMmQTzh5-7sJTSFML-OByak9KzGxobybuwfn6RoNwQ@mail.gmail.com> |
2013/12/13 Matijs van Zuijlen <[email protected]>: > Hi Dinos, > > Please note that most open source projects don't have an SRS, because > development on those projects just doesn't work that way: An SRS assumes all > requirements can be found and known in detail before development starts. This > assumption doesn't hold for a long term, evolving, software project, or any > software project IMHO. > I believe it is better to translate a tutorial or even to describe how to implement things in a wiki page. For example, it would be useful to write something about feature files, their syntax etc. A.S, -- Apostolos Syropoulos Xanthi, GREECE ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk