NetNewsWire Theme "uni" Updated
A very quick note to let those who use my “uni” theme for NetNewsWire — one of my 10 must-have apps — know that I gave it a point update today, which addresses the use of the “pre” and “code” html tags in articles. Click to download the updated skin if you use it. To install, simply double-click the theme in the Finder & NNW does the rest.
Bogart v0.7 Released
A quick note to let readers know that my Bogart WordPress theme has been updated to 0.7. This new version properly adds tagging for the new 2.3 version of WP, while maintaining backwards compatibility with earlier versions (see my last post). I also fixed an issue with missing code related to preloading theme images.
Thoughts on Derivations of WordPress Themes
Today I came across this post (nofollowed) by an individual who uses Bogart for the theme of their site. In his post, the author shares how to add a single line of code in two pages of the theme which will make the new tagging feature of the soon to be released WordPress 2.3 available.
While I applaud the author for taking the time to provide his tutorial to the WP community, I’m a bit disturbed by the fact that this person feels he now has the right to (a) re-brand the theme as “Bogart 0.6 Taged” [sic], (b) redistribute the theme from his own forums (which require registration), and (c) place a credit link back to his site in the footer of the re-distributed theme essentially giving himself credit as a “co-author” of Bogart. All without making any attempt to contact me.
Yes, I’m aware I released Bogart under a GPL (General Public License) — perhaps a mistake on my part — and that the license essentially allows this individual to modify and redistribute the theme as he likes with minimal restrictions. But I have to wonder — does this person ethically have the right to claim contribution (authorship) by simply reading how to do something on another blog (as his post claims), and then adding (perhaps copying and pasting?) one line of code into two different files of the theme? Does that really seem right? Does the GPL honestly allow for those kind of derivations?
Not only that, but since this individual made his changes without any kind of error checking, the theme will break should it be used with a WordPress install prior to 2.3. Could his actions potentially taint my reputation as the original author? Should I be responsible for helping someone who has issues with the modified theme?
I wrote Bogart from from scratch starting at line one. I’ve put many hours into making the design what it is. Josh Cook was kind enough to offer to widgetize the theme at a time when my schedule wouldn’t allow for it. As a thank you, I chose to list him as a co-author. He made a solid contribution to the project and earned credit for it. Now someone comes along, adds two lines of code (well, one line really), and says “Look — I’m part of this too!” Should I honor the GPL license and allow him to take credit for the “change” he made or not?
I think there are bigger questions that need to be addressed here as well; Where should the line be drawn on derivitave works under the GPL? What honestly constitues genuine change or contribution to a GPL’d project? Should the originating author be informed of changes before or after they’re made to a GPL project? Should they be informed at all? Am I just being a whiny sissy and overreacting to the whole thing? To me, it just doesn’t feel right. I’d love to hear what others think about the limitations — or freedoms — of the GPL, and whether the actions of this individual seem appropriate to them.
Technorati Tags: WordPress, General Public License, GPL
We're Back Online…
Well, it appears we’re back online after being “suspended” for nearly a day. For those wondering, the problem wasn’t with my site. Instead it had something to do with the company who hosts me, which is a hosting reseller — as in they get their hosting from someone else further up the ladder and charge me a little bit more than what they’re charged in order to make some cash.
I have no idea what their problem was, but I think I might need to start looking for a new solution. I’ve yet to hear from anyone after sending support emails and leaving voicemails. That kind of customer service worries me. It’s almost the same thing that happened when my previous host decided to call it quits all of a sudden.
Thanks for bearing with me through this unexpected surprise. More info to follow if there’s anything worth reporting.
Yasu 2.1 Released
As promised, the latest version of Yasu (2.1) is available for download. This version fixes some speed issues, Firefox cache paths, and enhances reliability when tasks start and finish. There’s a whole bunch of other tweaks under the hood too.
There you have it — now go get yours while it’s piping hot. And remember – if you have questions or issues, use the forums to communicate them so all share in the love.
Yasu Nears Release
I’m almost finished with all the updates I plan to make on Yasu. All I have to do is tweak the reboot code a little, and then do a line by line scan of the main script file to be sure I’ve not borked something along the way. I should be able to have it all wrapped up by Sunday. If things go well, I’ll be releasing Yasu 2.1 to the Mac world on Monday Tuesday or Wednesday morning.
I plan for this to be the last of the 2.x branch. Once it’s out the door, I’ll (finally) make the minor updates to Cache Out X that it needs, and release it as a final 4.8. Thanks to all the COX users who have been so patient waiting for me to get to this.
Then, I’ll be starting from scratch on a new, totally revamped version of both apps. Since Leopard is just around the corner, there probably won’t be much coding done until I can get my hands on it. In the mean time, I’ll be focusing on really mapping out what the new versions are going to be. Trust me, you’re going to dig it. Big plans for the future, big plans…
Yasu & COX Development Begins Again
Just a quick note to let readers know that Yasu and Cache Out X development is beginning to get back underway now that summer is essentially over.
I know many have been waiting for the new version of COX for quite a while. I hope you can wait just little longer. My plan is to squash a few lingering bugs in Yasu and get it out the door. And then do the same for COX.
Once that’s done, I’ll be able to begin focusing on the feature sets and specs for the new versions of each apps. I have some big plans for both of them, so keep an ear peeled for news, and an eye open for teasers.
By the way, if you’ve wanted to see some kind of feature added to either application, now’s the time to let me know about it. Drop me a line with your big idea via the contact form.
Technorati Tags: Yasu, Cache Out X
