Re: [xwiki-devs] [GSoC] Responsive Skin

Hi Jonathan, On Sat, May 12, 2012 at 12:33 PM, Jonathan Solichin <jssolichin(a)gmail.com> wrote: OK, I didn't understood that at first. Couple of comments on the timeline : - I think you underestimate time for both design and implementation. Remember that in addition to the work it represents by itself, which in my opinion is already underestimated, you will have to present it and discuss it with the community, refine accordingly, etc. This takes more time that you imagine. - I don't know what you exactly mean under "typography check", but a priori one week sounds way too much for this - what do you mean by "bumper" ? - I think what you have as refinements in week 10 "color variations, inverse for night time" etc. you can just forget about that. That's not really important, and it's not likely we can go this far during the time of the GSoC. Also please add the calendar week number as Caty suggests so that we have a better view of when things happen. How much creativity ? A lot :) As much as you can afford ! While there are some good ideas in your skin proposal, to be honest it still does feel too much as "dressing up [the] product with a last-minute garment" as Dieter Rams put it in this great text "Good Design As A Key Business Advantage" [1]. What we want you to do is to take ownership of the product. Caty is definitely right when she says you don't consider enough how XWiki works. You should download XWiki on your computer, install it, plays with it, get to know its feature, its *purpose*, and then start afresh on a white (I mean transparent) sheet. Right now your design has "colibri" written all over it. We can tell from the links at the top and from the block in the footer. We can tell from the way you've placed the "annotations" feature, etc. you get the point. I hope you can make it as if you would never had seen colibri. I want to emphasis on the fact that, at least for me, at the end of the GSoC, the design you can come up with will likely have more value than the code you can deliver. Don't get me wrong, I'm not saying you shouldn't implement it ;) What I mean is that if you bring us a great design and a working proof-of-concept implementation - that might not be perfect - then we can certainly do something with that as a community with quite some developers. It's more likely someone interested will take over after you. While if the design feels flawed to begin with, I think no matter how good the implementation is, it's probably going to take the dust in the attic ;) Hope that nourishes your reflexion, and looking forward your work. Thanks Jerome [1] http://www.fastcodesign.com/1669725/dieter-rams-on-good-design-as-a-key-bus… -- Jérôme Velociter Winesquare http://www.winesquare.net/