Re: [Rainbowportal-devel] Old themes issues
Brought to you by:
danijel_kecman,
manudea
From: Charles C. <cha...@gm...> - 2004-10-25 20:32:30
|
I have done many things for the Rainbow project on many fronts, many of which will NOT involve checking in and modifying code and CSS. A good example is I recently snagged the iBuySpy creators to join the team, and they have lots of energy and skill to check in code/css/et al. While I understand you and others think a project like Rainbow is all coding and check-ins and other contributions (testing, documenting, evangelizing,UI feedback, product feedback) are less relevant, done by second class citizens, and make the contributor less credible by the tone you use and suggested course of actions demanded of them. If that is the case as Alan Cooper would say "the Inmates are Running The Asylum". This is how Rainbow's UI got the way it is and how the team has turned away (indirectly) many good non-coding contributors, who while given heart-felt feedback, were confronted with a demanding that if they identify the flaw, they must fix it. Not everything that is wrong with Rainbow and the team's decisions requires me personally to fix them. I am NOT part of team, and do not aspire to be as long as the mistakes of past continue... I am deciding which OS team to commit time and thought to, but such a team would need to would need to be open to strong criticism without attacking the messenger. Based on Ed and other's personal attacks on me, when I use strong language and brutal assesments and words to illustrate my displeasure and disaproval of certain decisons (well intentioned or not) why would I want to join a team where every opinion and decision the team makes even one with disatrous consequences for the admins must be treated with kid's gloves. Of course as a result of Ed and others, no one wants to be brutally honest here. They know honestly and without mincing words stating one's opinions about the product and team decisions can lead to personal attacks rather than frank dicussions and debates on the merits of the issues. I am ok with the old themes being broken and included in newer builds (that is to say sometimes black text on bacground creates unreadable text or a theme designer foirgota logout option, etc.) and encouraging the people who like the themes and "iron the kinks out" to check in the fixed ones. Microsoft and many vendors ship imperfect things that are loved and liked despite their imperfections. I am not "ok" and will speak clearly and strongly against removing things that people got used to in old releases without a conversion plan. From the standpoint of investing Rainbow client's trust in newer builds seem, seems like a losing battle with the way the team decides to abandon past pieces (thems/skins, modules) rather than finish them or grandfather them in their imperfect form. There is a bustling community of people besides me that know CSS 100 x better than me to fix past themes that I will get evangalized to join this group and clean up past themes so we can have the past themes in future build. DotNetNuke tapped those people and Rainbow can too. I am working on converting a lot of good CSS and DNN and other veteran UI experts, SQLserver experts and cooding gurus to the Rainbow team -- but they only will do so if they know that I call a spade a spade -- and am upfront with them about Rainbow problems and potential solutions rather than sweep them under the rug. If I was a CSS expert and could fix all the themes I certainly would. Complaining when they cut a dozen themes down to 1 theme and expressing negative thoughts about the decision process that would lead to that hardely makes me responsible for fixing it. On Mon, 25 Oct 2004 17:01:59 +0300, Mark McFarlane <mar...@ho...> wrote: > Charles said: "I think that was a bad decision....If the old themes had > problems (and yes I know a lot of them do unreadable text etc.) people > report that and we fix them or they fix them and we get the fixed theme into > next release." > > Go for it Charles. Why don't you fix the old themes and check them in? > > Mark |