If you like chaos, this is your archenemy.
If you know CUEcards, this is like CUEcards on speed.
If you like TuxCards, this is like TuxCards on speed, ecstasy, and magic mushrooms.
And if you use Linux, this shall put a broad smile on your face, broader even than when you first realized your laptop reliably wakes up from standby.

BasKet is the little assistent you always dreamed of to take care of your tidbits. It's fast, it's stylish and it collects them all: todo lists, text snippets, images, even freely choosable regions of your screen.

And it's not only the functionality that makes it stand out from the gray mass of little open source tools like the Twin Peaks tower from the fog. It's the amount of energy the French author invests into the tiny little details that make a program not only useful but fun to use. This is a guy with a plan that many larger OSS projects would and should be jealous of.

Give it a try and don't hesitate to test the current beta. It finally adds the hierarchical basket structure that we all know and love.

Looking around me, I guess my non electronic desktop could use a little basket, too ...

You know what I love about Linux? The great community! There are so many people out there who spend hours of their spare time to improve the quality of their favorite operating system. Truly amazing in a day and age where money rules the world.

Much of the discussions concerning these software projects happens in mailing lists where problems and solutions are discussed, priorities set, and the future of Linux determined. People send well-meant improvements to these lists, like this one guy who tried to fix two issues. I really like the warm and respectful response he got:

> Any problems with these two patches?
 
NACK
 
It is too late for me to write out a long email right now --
I dont know why I even opened my inbox.
 
I'll explain tomorrow.

The day after, another highly motivating e-mail from the same person, this time obviously well rested and focused on the real important problems in life:

> Any problems with these two patches?
 
First off, It isn't as bad as I made it sound in my email last night...
but I still am not very excited about this patch.  If you want this
applied, you are going to have a lot more work to do beforehand.
 
Hunk #1:
 
@@ -3957,8 +3957,9 @@ static int __devinit bttv_register_video
 	printk(KERN_INFO "bttv%d: registered device video%d\n",
 	       btv->c.nr,btv->video_dev->minor & 0x1f);
 #if LINUX_VERSION_CODE > KERNEL_VERSION(2,5,0)
-
-	video_device_create_file(btv->video_dev, &class_device_attr_card);
+	if (class_device_create_file(&btv->video_dev->class_dev,
+				      &class_device_attr_card)<0)
+		goto err;
 #endif
 
 	/* vbi */
 
^^^ ... BROKEN WHITESPACE. ...   That second line needs to line up, one
char to the right of the paren above. You should add a space surrounding
the '<'

This is definitely the way to go in order to motivate developers to contribute--the ones that write and submit patches and the ones that just follow or happen to stumble over discussions.

If some people don't learn how to treat people who generously give their time for no (material) rewards, they may just find themselves having to do a lot more work on their own. Come to think of it, that shouldn't be such a problem, after all, if you want it done right, do it yourself!