Sometime in the next month or 2, I'm going to be pulled into a non-Drupal project for a few months. As I won't have much time to spend on the modules that I've created thus far, I'm placing them up for adoption. Anyone interested in taking over the maintenance of any of these please let me know. I don't want to see them rot on the vine and would rather somebody potentially take them in a different direction then have them sit unused and neglected.
attached_node
Status: Working
Needs: Future maintenance and occasional bug fixes (currently a few to look at)
editasnew
Status: Working
Needs: Future maintenance and occasional bug fixes
relativity
Status: Functional but not quite 100%. Will be soon, though.
Needs: TLC, proper documentation/help, rethink the UI a bit (simplify it)
moblog
Status: Functional but not very robust. Relies on mime_registry. Neglected for quite a while now.
Needs: Current and future maintenance. Needs to be made stable enough to be part of a public project. This is not a simple project, so buyer beware.
mime_registry
Status: Functional based on other drupal 4.5.1 modules (image,filestore2,etc). Neglected for quite a while now.
Needs: An advocate to promote this to other module developers (so it's hooks are supported). Currently, there are dependencies on specific versions of other contrib modules. Also not a simple project.
I'll still be around for another month or two, so anyone taking over a module won't be standing out in the cold wondering why the hell I wrote something the way I did (though I might not always have an answer :P ).
Comments
Congrats!
If its a good thing - congrats on the new project!
As you know, I've been an avid fan of the relativity module. I would enjoy taking over development of it. It would be a good starting point for me to get good at working with drupal modules.
If noone else with more experience chimes up, I'll take it. :)
--
http://www.electroniclife.org/
Thanks
The upcoming project won't be too much trouble (not my choice) I hope, though nowhere near as interesting as a good Drupal project. It will take pretty much all of my time. Some of these modules (the bottom two) have been neglected for a while now and really need somebody to keep them maintained. If you're going to be doing any code contributions you should definitely apply for a CVS account.
relativity module uses the nodeapi interface for a lot of its functionality, so I'd definitely recommend studying up on that. The CVS version (currently) bends drupal a bit (and requires a patch to menu.inc to work properly). Look the code over and tell me if you're still interested :-P
Anyways, thanks!
Aye
Well, I've browsed the CVS code and have actually already done some work useing nodeapi. I've just put in a request for a CVS account. I just need to get the cvs client installed on my server. (I like subversion so much more... sigh)
So, I'm still a go for the adoption.
How/when do you envision winding down your work on the relativity module? Is there any more work you need to put in to feel like it is ready to be handed over? Before I get my hands in to it I would like it if you would post as many feature requests and bugs as come to mind so I have a bit of a guideing light until I feel situated enough to take the module on my own path.
--
http://www.electroniclife.org/
Timing
The project that I'm currently developing the relativity module for is still going and will probably involve a few minor updates to the module. I would think that I'll be done adding new features in another week or two. I'm not currently planning anymore new features, but I'm sure something will come up that I'll want to share, be it a bugfix or new feature.
The administrative interface is getting too busy for my tastes, and I might have an "advanced" tab or something similar to hide the more peculiar settings. This is low priority for me now, so I'll probably not do it. I'll submit feature requests/bug reports for all of the changes that I do so that you'll have more than just the CVS logs to go by.
if nobody else wants it..
Hi javanaut.
Am fairly new to php & drupal...and understand that the moblog.module isn't a simple one..but I think I can add some value to it and help develop it further.
Dub
DUBLIN DRUPALLER
___________________________________________________
A drupal user by chance and a dubliner by sheer luck.
Using Drupal to help build Artist & Band web communities.
Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate
Great
The moblog module is intimately tied to the mime_registry module, so for all practical purposes, you'd be adopting it as well. mime_registry is moblog module's workhorse and handles the actual creation of various nodes from mail attachment data. If attached_node is installed, this is used to represent multiple attachments in a single email. The modules you'll need to study up on for this are:
mime_registry.module
mailhandler.module
mailalias.module
attached_node.module
Additionally, to continue mime_registry's support for creating various node types, you should have a look at:
image.module (more advanced)
filestore2.module (advanced)
fscache.module (for reference)
blog.module (easy)
story.module (easy)
..as well as any other node type that you're interested in creating from a moblog post. Note that mime_registry jumps down into the bowels of these modules, sometimes faking $_POST parameters to get around security checks, etc. Not the most sustainable techniques, as contrib modules tend to change a lot as time goes on. The advocate role for you would be to convince the module owners to support the programmatic means of creating nodes for you. I never got around to this part ;)
There's been requests to support video (3gpp/quicktime format) posts and audio posts, but those are currently only handled as generic filestore2 nodes. Requests to support the creation of custom flexinode types have come my way as well, but I would wait until flexinode is finished being rewritten for 4.6 before starting on that.
Ok, I'm writing a book here. I'm glad you're interested. I would start out just by installing it and verifying that the docs that I do have are still relavent.
Thanks,
Mark
I have an enhancement I want
I have an enhancement I want to do to editasnew so if no one else wants it I will have a go. However I am NOT a PHP programmer and this is my first ever Drupal site. I really suggest you find someone better and they can get my help.
feature request
Go ahead and submit a feature request if you feel timid about PHP coding. I'm not abandoning these modules, just looking for help while I'm gone. The editasnew module is quite simple in design (relatively) and it wouldn't be much of a problem adding new features to it. I'll still be available for the next month or so, so feel free to suggest new ideas.