I think the main idea is to discuss a feature on the mailing list and if it gets interest from enough developers then they can join and work on it together to create a working prototype. When it is ready then it can be added to JIRA for inclusion in the main project.
Haykel On 6 February 2012 10:54, David Arno <da...@davidarno.org> wrote: > > From: Rui Silva [mailto:f...@rduartes.net] > > Sent: 06 February 2012 09:33 > > > > If anyone thinks that he/she will sway the opinion of the group simply by > > speaking out his reasoning without giving actual proof of feasibility, > then they're > > thinking it wrong. At least, that's not what I see in an Apache project. > I struggle with this philosophy. The idea of spending time writing code to > then find out whether people like the idea is very alien to me. > > Take for example the idea of targeting JavaScript. I'd assumed there would > be lots of technical discussion on the theory of how we might go about it, > options available, likely pitfalls etc. Only then would I anticipate > writing > some experimental code to test these ideas. By the sounds of it though, > this > isn't the way we are supposed to do things. Instead we should throw code at > whiteboards/ JIRA and then use the email list to critique that code. It's > an > odd way of doing things IMO. > > David. > > >
