Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Dries on
We put a task list in place. So if you want to help out but don't know where to start, take a look at the task list. There are tasks for non-programmers as well so even if you have never written a line of code in your life, you can help out and become a Drupal contributor. Of course, you can also check the bugs reports, find a bug, fix it, and send a patch to the mailing list. Any help is most welcome. If, after checking the tasks and bug reports, you still want to help but don't know how or where to start, just post a comment below.
Comments
suggestion
add this topic to "primary_links". i'd suggest to change the title to "Contribute", as (to me) this describes better what it is about (who's "Task list"?). if this makes "primary_links" too long / wrap (which i wouldn't mind), move "Contact" to "secondary_links".
Certainly.
Of course, I only know enough PHP to have a vague idea what I'm looking at to read it, and while I searched bugs/features/tasks for Drupal/Contributions and Tools, I'm at a loss for how to make myself useful.
I'd be glad to help out, though, so by all means, count me in if there's anything I can do to make myself useful. You can leave me a message here, or send email to maxbell@atlasisshrugging.org -- I check the forums here at least once or twice a day.
Tasks for non-programmers
Here is an example task you can do as a non-programmer: review descriptions/help texts at the top of the administration pages. That would be a very, very useful contribution. While doing that, you could also look into this task. Or, if you are familiar with HTML (but not with PHP), there are quite a few tasks related to the maintenance of themes which requires little or no PHP knowledge.
I'm on it.
I've presently got a working 4.1.0 with a few of the add-on modules running as a production site with a shared hosting service under redhat apache.
I need to grab copies of the core CVS and get that running on a test machine, and from there I can throw a copy up on my host's machine if need be. I've been through the online help for 4.1.0 and all the admin functions several times over, and I know that end of it fairly well. Once I've got a test system running, I'll be able to find my way around without any problem. I'm already on the mailing lists so I'll throw what I come up with back on the dev list once I've got something.
I'm also fairly comfortable with HTML and wrote a tutorial for my site to cover basic HTML for my users and explain XHTML and why it's important. I know enough PHP to read it and have done themes for Nuke, but I'll go ahead and do the help sections first and start looking at usability.
Arrgh!
Just a brief update -- ran into a snag /w/ PHP 4.3.1/Apache 2 that bombs php4ts.dll, and have spent the intervening time waiting for my hosting service to restore FTP access, so I'll finally start working on this this evening.
Looking forward to your patches
Looking forward to your patches, Max. Thanks for keeping us posted about your progress.
I'm looking forward to them, too.
Spent a productive morning putting together a working copy of last night's CVS, found a diff & patch utility (Gnu diffutils for win32) that should produce patches in unified format, and then spent a fair amount of time proof-reading existing help items and trying to make sense of the module_help function.
The new CVS version looks great, particularly admin/help, and I'm hoping to have something finished enough to throw on the dev list this evening in case anybody wants to proof the result. At this point, I at least feel like I know what I'm doing (or more so than I did)...
Gratefully...
No one else actually wanted to do this. Shortly after my last post, I lost my PC (it was sold into bondage by a room-mate while I was off doing other things) and it's taken me this long to get something together besides an iMac, which I could scarcely condescend to use for retrieving email. Since I didn't know exactly how long that was going to be, I figured it wasn't worth mentioning at all.
Anyhow. Moving right along...