More Kopete Webcam Love and Yahoo! patches!
First up, Michael Cole came in with some fixes earlier in the week on the Yahoo! protocol side for being able to better use webcams. Now Frank Schaefer has come through with the some fixes on the low level side of the webcam stuff. Frank's patches fix a number of issues, including:
- loading and saving of the video settings
- device registering, unregistering, and switching
- some problems with the GUI (bug# 188177)
Not one to lag behind, Michael also came through with some other fixes to Kopete's Yahoo! support, so from those we've got fixes for:
- Downloading avatars when a person comes online while you were online.
- Email notifications (you now get an unread count when there's more than one, and a notification with a subject when you receieve a single email while online)
- Webcam announcements are now sent to the other user, meaning that they'll get a notice saying that you are sharing your webcam with them.
- A login fix that allows people to see the notice that they typed their password wrong or are locked out.
Both the webcam and Yahoo! patches are in 4.4 and trunk (or will be shortly). Awesome work guys! Keep those patches coming in!
Yahoo Webcam Fixes for Kopete
So i just committed a rather nice patch from new contributor Michael Cole that fixes a few things in Yahoo with regard to webcams and avatars.
You can now accept webcams from Yahoo users and send your webcam to other users. Avatars that are now also downloaded and stored properly.
Michael mentions that the other user doesn't see an notification when you send your webcam to somebody (IOW, they have to request it still) and that avatars only download when they're changed while online.
Either way, it's nice to see some webcam love come our way. Thanks Michael!
kde bugzilla ui changes: feedback wanted
If you've been reading the kde-core-devel mailing list, there's been some talk recently about bugzilla, how much it sucks, whether we should switch, and alternative tools to switch to. However, only one person told me about something that could be improved. So, in order to get feedback on whether or not our customizations that are currently live on bugs.kde.org are hindering vs. helping, I've changed the layout on bugstest.kde.org back to the standard default bugzilla layout.
Please, if you use kde's bugzilla currently, take some time to test out bugstest.kde.org. When you do this, please send feedback. The feedback should be something that we're doing on the live site that is done better by the test site. It can be good or bad!This can be in the form of a bug report in bugs.kde.org against the bugs.kde.org product, or sending me a simple email. Please include changes that you want made, or specific issues with the site so that I can at least look at fixing them.
I get that a lot of KDE folks are not happy with our current Bugzilla. I'm glad that you want to have good tools to work with. So far, I haven't really seen anything that's better. I've only seen systems that do things differently, which means that we can emulate that with Bugzilla, most likely. That's after using Jira, Mantis, Flyspray, Bugzilla, and Redmine, and an old version of RT. Why not work on improving our current tool? If you think that Bugzilla has fundamental problems that require switching, I want to know what those are too.
Patch Friday!
I've deemed Fridays to be "Patch Fridays". This means that I will be doing various things with patches. I review patches, test patches, commit patches, etc. So, if you've sent me a patch, or stuck one on review board, or I've seen one from you on bugs.kde.org, then if I haven't done anything with it before a Friday, it'll most likely be handled on a Friday.
For this Patch Friday, I've (so far) got four patches to commit: two gadu gadu patches and two chatwindow patches.
Why Friday?
Because I had a lot of patches that I knew I needed to take care of, and today just happened to be the first day I could get to them. So I've decided that I'm going to stick with it.
Can I send you just any patch?
Well, not really. I'd prefer it if they were areas that I spent a lot of time on. For now, that would be:
- Kopete
- bugs.kde.org
- Basket
- Anything for the kdesdk module
- KatePart
- KDevelop
The last two areas are only areas that I'm marginally involved in, and so I'll be passing patches for those two pieces of code through the proper channels before committing them. Basket patches will go through my git repository of basket on GitHub before going into Basket's master repository that Kelvie Wong, the Basket maintainer, has.
Every Friday?
Yeah, pretty much, unless I'm travelling or otherwise indisposed.
Got Patches?
Friday's not over yet! Send me your patches! 