request to take over maintainership
yettyn - October 13, 2008 - 11:15
| Project: | Blog Information |
| Version: | 7.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
As this project is abandoned and I have made it working in D6 and also have future plans to use it in D7, I request to take over maintainership, filing a bug here according to Dealing with abandoned projects instructions.
This would be my first drupal project to maintain and I find it a suitable task. I have fair knowledge and experience with CVS as well as PHP, although not considering myself a pro on either. I have been poking with Drupal since D5 beta times. I think this would be an excellent opportunity to further acquire knowledge about Drupal development.

#1
Do you have a CVS account so I can grant you access? If not, check out http://drupal.org/cvs-application. I'm glad to see someone interested in taking over this module and I'm glad to grant access.
#2
As I said, this would be my first project bing part of, so naturally there has been no need for me before to have cvs access. I will fill in the cvs-application among following the other guidelines for overtake of maintainership, like moving the issue to the webmasters queue project.
I just need to have my (late) morning coffee...
#3
You don't actually need to move this to the webmaster queue (but, you can if you like). Put in a request for CVS access, link to this issue in the request, and when you are granted access post here and I'll give you access.
#4
Ok I have applied for cvs access, now I cross my finger and hope I user the right words ;-)
If you say I don't need to move the issue then I take your word for it.
#5
CVS account approved, feel free to add yettyn.
#6
Access granted.
#7
can we have a dev D6 version now please?
#8
@CompShack Give yettyn some time. It's in progress. You can expect a D6 release soon.
#9
6.x-1.x-dev is in the package que, that script is only ran every 12 hour so just hang on.
#10
Sorry i didn't realize that access was granted on October 14 :) -
yettyn, thanks for getting this to D6, truly appreciate your time and effort on this!
#11
Hi Yettyn,
If you are not implementing changes in the older versions, I feel i may be of some help.
I am able to take time to work on the older versions and implement some of the fixes that you have had to turn down.
For now, i plan to take a look at some of the issues already posted, and can take on future issues.
I already posted my code on how to implement the token hooks, so i have already dealt with the back end code of this module.
I do not yet have a CVS account, but if you accept me as a co-maintainer, i'll apply for one.
#12
@yettyn - This call is up to you, of course. A practice is to have different maintainers for different branches. An example of this is the jQuery Update module. If you only want to work on drupal 6 someone else may be interested in taking on the drupal 5 branch.
#13
@orbface9, are you talking about D5 or D6? My main concern is that I don't have any active D5 site running and for that reason don't see much point in adding something I cannot put to the test in areal way. Also as it's on its way out I think it's a better path to invest energy into D6/D7 and for my personal view I prefare D7, but in no way am I opposing further development on D6 if someone like to contribute.
As for co-maintainership, I am not rejecting that either really but as I just have put myself in this seat I may like to wait awhile before taking next step. So what do you say about starting with patches?
I have already tarted to look at code that been submitted here in issues, but have had my focus elsewere for a few days as I also need to do work bringing in $$ :-)
Another thing is I like to look deeper into where the blog module is going in D7 core and take some kind of stand from there where to go with bloginfo. I think the token implementation can be good, but what I don't want in this phase is futher development in D6 that will be hard to bring over to D7 and specially when it comes to upgrades.
#14
@yettyn, i have D5 and D6 sites running and for now, I'll just help out where i can where patches are needed.
#15
Automatically closed -- issue fixed for two weeks with no activity.