+1 Rafael "Monoman" Teixeira --------------------------------------- "To be creative means to be in love with life. You can be creative only if you love life enough that you want to enhance its beauty, you want to bring a little more music to it, a little more poetry to it, a little more dance to it." Osho
2010/8/7 Valeriu Caraulean <[email protected]>: > I think that samples and code projects have different vectors of interest: > - somebody looking at samples will not be downloading also the core > project's sources, it'll be faster and easier to start with compiled > assemblies. > - somebody working regularly with core source code will not be downloading > samples, they simply don't need it - unit test are well enough. > IMO they should be kept separately, but close enough to be visible and > discoverable. > Two repositories, two released packages. > Valeriu > On Sat, Aug 7, 2010 at 2:13 PM, John Simons <[email protected]> > wrote: >> >> Here is my opinion: >> -Keep the samples with the project that belongs too. >> -Distribute samples with project release package. >> -In doco refer to samples based on release package folder structure. >> >> Cheers, John >> >> On 07/08/2010, at 19:45, Krzysztof Koźmic <[email protected]> >> wrote: >> >> > Hi guys, >> > >> > We have a single sample app for Windsor 2.5 currently, contributed by >> > Hadi Eskanderi. Perhaps another one will join soon after the release... >> > anyway. >> > Where do we keep samples? >> > >> > I remember we planned to establish a "Samples" project, Richard being >> > the lead of that. What's the status of the project? >> > Where should I put that sample app? What do we do about our longer-term >> > strategy for maintaining samples? >> > >> > Ideas? >> > >> > Krzysztof >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Castle Project Development List" group. >> > To post to this group, send email to >> > [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/castle-project-devel?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
