Until now I was a bit concerned about this, but I think I'm completely convinced that it is the way to go.
Here are a few brief excerpts from drupal-dev
Person 1
|
|||
Don't get me wrong, I dislike many of the practices of America's police forces as much as anyone. Many laws that they enforce serve to harass the public, and generate income, but I don't quite get the latest set of outrage at the police for their actions at different riots throughout this country. So the police used tear gas on a crowd of protest/rioters that weren't listening to the police and moving on. This is not news. As much as I don't like it, it's generally a good idea to do what the police say, and some things are bound to provoke them. For instance carrying banners and trying to march through a police line. This applies to "journalists" as well. If you're carrying a palm corder through a protest/riot crowd, then you are not a journalist, and you would be advised to listen to the police as well. |
|||
First select your packages:
Then go through and configure each one: (note the expanded task list on the left side) |
|||
While I think it's a little designer centric, I like A List Apart's articles, style and I have found them very, very useful in the past, and I'm sure I will again. They are running a survey titled appropriately, "The Survey for People Who Make Websites 2008." I would recommend checking it out.
|
|||
I've been wondering for awhile now if Mollom's captcha has been cracked, and recent evidence would seem to support that. In the last few days, the amount of spam I've seen getting through has increased from none, to between 6-10 messages a day on this low traffic site. Mollom is also reporting that it is blocking about twice as much spam as it has been on average as well.
Note that all of the ham in that chart turned out to in fact be spam. Roel De Meester and Kristof De Jaeger have both blogged about massive increases in the amount of spam that Mollom is blocking. Has this increase signaled a large scale attempt to crack the captcha? I believe that is a strong possibility after seeing comment spam reappear on this site, in the past week. I am considering a switch to recaptcha, if this continues, as I've heard very little about it being compromised. It would be great if the captcha that Mollom uses could be configured to use recaptcha, however I don't think this is currently possible with the existing Mollom module, however one could certainly write another module, or a patch to the Mollom module to provide such functionality. UPDATES 1 hour after posting this, I have received 4 more comment spam, that were not blocked by Mollom. 5 hours after posting this, I have received another 14 comment spam, I have isolated about half of it to 1 IP, and while I could block it, I feel that kinda defeats the purpose of using a service like Mollom. 24 hours after posting this I have only received 4 more comment spam, all from the same IP as mentioned above. 36 hours and running...seems to have cleared up now. |
|||
So I was thinking about finding a way to help out the fine folks that maintain the project_* family of modules for drupal.org again and was chatting with the folks in IRC about the status of the drupalorg_testing profile which is designed to help one mimic the setup of drupal.org and provide sample data for testing new features. In the process aclight pointed out some patches to the profile that need to be applied (detailed below) to prepare it for use. I was surprised that these haven't been committed yet, only to find out it's due to a small issue which I have been trying to get resolved for some time now. It's truly funny how things come back around to you after awhile sometimes. Anyway, currently to test the drupalorg_testing profile, download it from here, and follow it's installation instructions on dependencies, but before installing the profile, check out the patches from here and here. Then install the profile, and let it do it's thing. If your experience was anything like mine, you may be greated by some serious whitescreen issues when trying to check out your new installation. If so, check out the patch here by webchick. |
|||
So for sometime now, I've been doing Drupal/PHP development on my local machine. I'm a Mac user, and I use Growl quite a bit to keep aware of whats going on. Honestly at times its probably a productivity killer to know that I have 22 new emails, I was pinged in IRC, and my feeds were just updated, and the latest track in iTunes is something that I probably don't want to hear. So I've been spending some time thinking about how to best put this cool tool to work for me, and I kept coming back to growlnotify, a command line tool to post notifications. My first though was, how to get this to tail some server logs for me, and how to take care of letting me know when servers had issues. But then I got to thinking that isn't really all that useful. Servers shouldn't go down, and if they do, they should notify me by email (which if I'm at the computer, Growl will pick up) and server logs? I just don't need that. The next logical conclusion was maybe to do some local tasks, like I don't know...say the PHP error log while I"m developing? That might actually be useful when I do something stupid, like get tired and call $node['body'] ( PHP Fatal error: Cannot use object of type stdClass as array). Anyway, lo and behold, someone else has already done this for me. Check out the snippets here for more info on how to make this work. It's a bit tricky since growl won't send a notify until an end of file is reached, and tail -f just sends newline characters. The solution is to use a small python script to read the stdin, and then conver that into a full growlnotify command, and execute it. Thanks to this tip I now get notifications like this:
You may need to play with your error level to keep from getting splattered with notices, but I find this quite useful (especially for catching notices with Drupal 6). |
|||
.
Did you know that you can set your email subscription for regression testing notices for patches you've committed? I didn't. At least not until today. I was off editing my subscriptions because I noticed new issues in the queues of a couple of modules I maintain, and I realized that I hadn't been notified by mail. Realizing that my subscription status to issues queues is all over the place I went to edit it at http://drupal.org/project/issues/subscribe-mail, and when I went to save the form, what did I see at the bottom? A subscription option for regression testing notices! This is going to be very important in the upcoming months as Drupal strives for 100% test coverage. After all, how are you going to know when you owe a dollar to the Drupal Association?
|
|||
So, I've been having a lot problems keeping track of the Drupal issues that I want to participate in, and help out with. It seems like everyday, I see at least one issue that I think to myself, "HEY SELF, this has GOT to be in the next version of Drupal!!" And then I never think about it again until I read the release notes for the next major Drupal release (6, 7, 14* whatever...). This is not a very effective way to help out. I need to be able to get quick access to a list of Drupal issues, categorize them, and then view and update those categories quickly. So, enter del.icio.us. Now many of you up-to-date, hooked on the next-best-thing will be expecting my to discover framsets and cgi counters for the web next. Nay, I have known of del.icio.us for many ages, but have never been much of one, for applications on the web, that work better on the desktop. I 'got' it but I didn't 'get' it for personal use until recently. What changed my mind you ask? Enter Cocoalicious UPDATE: I think I found a Windows client that is similar. If you use Windows, check out Delicer. |
|||
Time to help out where it counts. The developers of the project module from Drupal.org are in need of funding to attend This would enable them to work together in person, rally troops, and get serious-work-done™ on the module. This is critical to Drupal.org as it facilitates the development of all projects including Drupal itself and all contributed modules on Drupal.org. If you ask me they are every bit as important as the core developers of Drupal itself. They need to be, there, so Chip in what you can, and look forward to seeing them there! |
|||
