[Bug 157969] GUI for Adding/Removing of Panels Missing

Aaron J.Seigo aseigo at kde.org
Tue Feb 19 13:27:27 CET 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=157969         




------- Additional Comments From aseigo kde org  2008-02-19 13:27 -------
> have to just wait and see 

good idea.

> because you cannot read their mind either

there is no need to.

> Discussing on the ml

unless you're going to be involved in the implementation, there is no need to do this either.

> changing it afterwards

don't worry, it won't be.

> If the roadmap would state what you are going to implement and what 
> not, including reasons, you would have saved yourself a lot of time and could 
> just point to the roadmap.

i *wish*. most people don't read those documents, many who do don't care and file away anyways and honestly: i could sit and write books of material but that doesn't get code written. just back off and let me work.

> it is currently a valid question, if a user asks: panel config, does 
> that include xy

no, it isn't a valid question. it's a question that may occur to you, but it's not a valid question for me. to me it's irrelevant. my point in being here is not to molly coddle you into feeling good and nice. somewhere along the line people got this impression that it's my job to do something along the lines of customer support and cooing in a soothing voice. every minute i spend doing that is five i don't spend coding. i'm trying to tell you how i work best, and you seem intent on finding a way around that. good job on helping me slow down.

> I could write down a 
> list of kde3-features for the panel in the roadmap and you simply add 
> comments to those you do not consider worth porting. 

the roadmap page is for people putting down what they are actually implementing. please don't abuse it for something else like a "wishlist area somewhere else after we were asked not to do it on b.k.o."

moreover, i don't need such a list, it's not going to get you anything sooner (or later) and i really don't get everyone's obsession with having to pester about whether Foo or Bar are going to be there today or tomorrow.

when it comes to panel config, write code or back off. if you're looking to write code, i'm happy to discuss. but i'm not going to waste my time (which is really the time you have to wait before the features land) if you aren't.

if you wonder why i'm replying to this, it's because i'm going to bookmark this BR and start offering it as my reply to people who come to me with the same questions in the future. it'll save me from having to manually re-iterate it over and over.


More information about the Panel-devel mailing list