Re: Drupal 4.7.0 beta2 / rc
2. The number of bugs that need fixing grows steadily: http:// drupal.org/project/issues? projects=3060&versions=9728&states=1,8,13,14,2. How do we encourage more people to help fix bugs? How do we help people fix bugs?
bug report. Replying with one-liners like 'File a bug report!' or 'RTFM' is not considered helping in this context. The goal is to assist, to be helpful, to pull them on board and hopefully to make them "stick". Similarly, I think there is room for people that
Greetings, You hit the nail on the head Dries - at least for me. I have a Drupal install on one of my sites and have a strong interest in improving it. I have mid-level PHP skills meaning I still need to learn some fundamentals ... oop code being one of them. I'd like to help but I need to take small bites and learn what I need to learn with some help here and there. I don't need the manual read to me. I do occassionally need someone to say "read this" and give me a link or tell me what to look for. I like Drupal very much since I started using it this summer. I have issues with some aspects of it but I haven't gotten under the hood yet except to hack at the themes. Needless to say, I'm wet behind the ears and am slowly working to get up to speed. So all this being said, I'd like to know what - if anything - I could do to help. Gregg
You hit the nail on the head Dries - at least for me. I have a Drupal install on one of my sites and have a strong interest in improving it. I have mid-level PHP skills meaning I still need to learn some fundamentals ... oop code being one of them. I'd like to help but I need to take small bites and learn what I need to learn with some help here and there. I don't need the manual read to me. I do occassionally need someone to say "read this" and give me a link or tell me what to look for. I like Drupal very much since I started using it this summer. I have issues with some aspects of it but I haven't gotten under the hood yet except to hack at the themes. Needless to say, I'm wet behind the ears and am slowly working to get up to speed.
So all this being said, I'd like to know what - if anything - I could do to help.
Helping out in the issue tracker (analyzing bugs, reproducing bugs, fixing bugs, testing fixes) is a great way to get involved with Drupal development. Just pick the issues that look _fun_ to work on. :) -- Dries Buytaert :: http://www.buytaert.net/
On Wednesday 14 December 2005 09:15 am, Dries Buytaert wrote:
So all this being said, I'd like to know what - if anything - I could do to help.
Helping out in the issue tracker (analyzing bugs, reproducing bugs, fixing bugs, testing fixes) is a great way to get involved with Drupal development. Just pick the issues that look _fun_ to work on. :)
I know I didn't really begin to grok Drupal until I began developing modules. It still took me a few mods before I had a good understanding of what I was doing. :-) While there are tutorials in the handbooks, such as node_example, frankly none of them go far enough or deep enough. Really good deep but clear multi-pass tutorials are incredibly useful, but Drupal isn't there, yet. I believe I've the writing skills to do such a writeup, but I don't know that I truly grok Drupal well enough to get it right. My day job is also not Drupal related, sadly, so I don't have much time to devote to it. :-( At some point I want to give it a shot, though. I'll probably be trolling #Drupal when I do so to make sure I'm not saying something incredibly stupid. -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
with the beta1 release, is this mean there will be features freeze on 4.7codebase. I'm planning to track cvs head (just to give some hand in searching for bugs) and ugrade my site but not if there's still major changes esp to db schema. -- kamal, www.k4ml.com
On 12/14/05, Larry Garfield <larry@garfieldtech.com> wrote:
I know I didn't really begin to grok Drupal until I began developing modules. It still took me a few mods before I had a good understanding of what I was doing. :-) While there are tutorials in the handbooks, such as node_example, frankly none of them go far enough or deep enough. Really good deep but clear multi-pass tutorials are incredibly useful, but Drupal isn't there, yet.
I believe I've the writing skills to do such a writeup, but I don't know that I truly grok Drupal well enough to get it right.
I'm still getting up to speed on Drupal, as soon as you figure something out there's an update. I kind of feel like one of those guys in the Western movies who's on the horse chasing the train, I just hope I catch it ;) I got started contributing bug fixes to the docs. No better learning experience than following an example and having it mysteriously fail. And there's no better time to write docs than when you've just figured something out, all the questions are still fresh in your head and it hasn't started to seem obvious. Docs are a great way to give back and there's plenty of changes in 4.7 that need to be noted. If you've got some time there's plenty to be done, andrew
participants (5)
-
andrew morton -
Dries Buytaert -
Gregg Banse -
k4ml -
Larry Garfield