This website needs help. Your help?
This december, it will have been 5 years since I created the first user for this site. Since then, there's always been a notion of a webteam. Though the webteam has from time to time been contributing to parts of the contents of the site, I don't think I am being unfair to any of the current and past webteam members if I say that I have been the sole contributor to the actual working of the site. IE: from architecting and designing the site functionality to setting up and maintaining Drupal, writing custom code, moving the site from provider to provider (to provider, to provider) and trying to keep the site processes working, to even daily pruning the spam that slipped through our anti-spam measures.
Over the past one and a half year, the site has been growing beyond what I am comfortable and capable of maintaining the site on my own. I'm trained as a designer, not as a photographer, but certainly not as a web builder or programmer. I took up the task to set up the website ~5 years ago as a member-like-the-rest-of-you. I learned about 90% of what I know now about PHP, MySQL and Drupal by and for the IVRPA. And I learned a lot these past few years. Unfortunately, what I learned over the past couple of months is that it is just too much for me to handle. I need help!
It is not that I was never offered help in the past (thanks to all who did). But delegating technical tasks requires more than a bit of skill. Technical skill on the side of the person I would be delegating to, and on the other had a project management skill on my side. Both, or either skill have been largely absent to such an extend that technical help has never materialised.
Long story short: the IVRPA website needs technical help.
We need people with skills tuning and maintaining our php/mysql/apache stack.*
We need people with experience in writing Drupal modules.**
Finally, we need people with experience in setting up a mailing list package; the membership has spoken and we need to revamp both our forums and our mailinglist.
Note that people can be single persons too...
Interested in joining the inner-circle of our association? Contact me!
*: you've just built your own website on a shared host? Good for you, but we're looking at people who can manage a Linux server.
I have come to know how to find my way around on an ssh connection, but I tremble in fear when touching php.ini, httpd.conf and my.cnf. Basically, I don't know what I am doing, so we need someone who does.
**: you're great at hacking Drupal core? I hope that works out for you, but we're looking for future-proof, maintainable solutions.
There's a number of functionalities missing that need to be added through custom modules, in order not to be hacking core or contributed modules. I will make another blogpost with my current todo-list.
- Aldo Hoeben's blog
- Login or register to post comments
- Short link
-


Re: This website needs help. Your help?
Submitted by Kris Bulman on Wed, 2010-02-24 17:39.I may not be of much assistance, but I emailed you my experience. If I can help in some way, great. If not, good luck!
Hacking Drupal core: Do people still do this? lol. Literally every piece of Drupal literature I've read since 4.7 has denounced this in the first line.
Custom modules: Are they ever "future proof"? If an existing set of well maintained modules can do what you want, there is no point in re-inventing the wheel.
php.ini: There is no need to fear this, test environments & backups help.
That said, it would certainly be great to get to the bottom of your server issues and see the site become stable again, allowing it to evolve into it's potential.
Re: This website needs help. Your help?
Submitted by Aldo Hoeben on Wed, 2010-02-24 20:09.The sites were originally set up when Drupal 4.7 was brand-spanking new ;-). A long time ago, both in actual time and in Drupal maturity. Not a lot of patching of the core was necessary, but I modified quite a number of contrib modules back in the days (in hopes that the patches would make it into the contrib modules ofcourse, but still). When I finally updated from D47 to D5, I made sure to do so with as little editing of contrib code as possible.
Currently there is one core file which has been modified, and that is bootstrap.inc (to support our multisite setup and to reduce the number of mysql queries for the typical page).
Custom modules are written to tweak and/or extend existing contrib modules where necessary.