-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
On 08/01/2010 07:24 PM, Derick Rethans wrote: > On Sat, 31 Jul 2010, Tobias Schlitt wrote: >> I think that such a process is a good idea. Providing full requirements >> and design documentation up front is not always possible and indeed >> represents a quite high barrier for new contributions. > However, providing the idea and what you're trying to solve is a good > thing to have. This is exactly what the requirements document was > supposed to be. Design is of course different. I don't think we should > give up the "requirements" part. I would stick to requiring both, requirements and design documentation, before a component migrates from experimental/ to trunk/. However, for just getting started in experimental/, both documents must not be final yet. An initial component proposal should should describe the idea behind it on the ML anyway. >> We already have the experimental/ area in SVN, where such components >> may be developed. >> >> However, we need to define some requirements on how new component ideas >> might enter this experimental area, in order to avoid lots of dead code >> there. > We can always delete it :-) That is true. :) Cheers, Toby - -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxWgqwACgkQ5bO3TcRivBTprgCfTpVsVFbStTRSSlAWMncksn+p 0WMAnRzgSW9/sfjYWoKj0OXWSN1L32kp =ts+N -----END PGP SIGNATURE-----
