Ashish, > Please see my comments inline. A also very easy route would be somebody > voting me in as a committer. Don't like to ask it out, but I think I have > dedicated considerable time and my resources to the cause.
I sympathise and agree. Not very long ago I was in exactly your position. Patience and perseverance is what will get you the nomination, I was told. I didn't like it, but I stuck with it because I cared about the project and in the end I was voted in. Do not despair! >> for limitations of the CMS. > a. We can do much better. As long as design changes do not dwarf the > functionality at use, we can consider making as many changes we can > creatively think of. I'm not so sure. Although we can use every technology for building websites we want, there are limitations to what we can implement without losing the advantages of having an CMS. And I'm sure we don't want to do lose the CMS functionality as it is an important tool for the community to easily update and/or contribute content to the site. >> everyone can keep an eye on each others work. > b. Not sure what a reference design means. Is it the HTML templates > like the one I just uploaded or something else. In this context I meant reference design in the sense that it's a fully developed site, but one which isn't running of the Apache CMS. The actual project site (which does run of the CMS) tries to implement the design and content of the reference design as best as the limitations of the CMS allow for. Any features that the CMS can't handle will have to be redone in the reference design is such a manner that the implementation can match. >> effective templating will certainly help in that regard as well). > c. Completely disagree. JQuery is an enterprise standard and with the > right balance makes great products. I wasn't arguing the merits of jQuery. I know it well. And I dislike it. That's all. The point I was trying to make is that the less knowledge anybody has to bring to the table if they want to update, edit or re-design the project site, the better (hence the decision by Apache to run the project sites of an CMS, with a primary focus on the use of the MarkDown markup language). So, since jQuery adds an extra layer of complexity to the equation, I would argue against using it. And as I said, the design (IMHO) doesn't need any of the bells and whistles jQuery offers, it is very powerful without it already. I'll be using the coming days (maybe week(s)) to get a feel for your design and how we can best make it fit within the confines of the CMS. I'll share my finding with you and the list. You can decide if you are willing and able to make the changes needed in order to make it work with the Apache CMS. And I look forward to working with you to making the Apache Flex project site a showcase for an Apache project site and a great place from which to launch the the Apache Flex evangelism efforts! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
