Nominating wolfflow for site maintainer
Michelle - September 14, 2008 - 01:15
| Project: | Drupal.org webmasters |
| Component: | User account problem |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I'd like to suggest making wolfflow a site maintainer. He's very active in the forums and has been cleaning up handbook pages. It would be simpler for him to be able to just delete the comments he's rolling in himself rather than having to file issues.
Michelle
#1
Oh , that's will be an Honor ;-)
Edit: Sorry for having this first and only reaction, please allow me to add some more words:
First thank You Michelle for proposing me as Site maintainer. I really appreciate your trust and believe in me.
Second: I want also to thank @Dman and @add1sun to have find the patience and time to help me out so as
@sepek for his great engagement to the Handbook and Documentation on Drupal.org.
I' very proud to have here the opportunity to help Drupal and the Drupal Community in this way.
My Drupal experience is very much focused as an User and in the Documentation-Team I'm sure I will some time
also grow my PHP knowledge in Drupal and in future try to support also in more technical forums fields.
Thanks
#2
+1
I think he is all i've been seeing in the docs queue since quite a while now :D
#3
++
#4
@Gerhard - If you approve, can you make it so? I don't have the magic powers. :)
Thanks,
Michelle
#5
This is obviously yes'd already but just wanted to give my +1 as well, for the record. ;-)
#6
#7
Thank You for approving. Thank @Gerhard @add1sun @lut4rp @Michelle
:-))
#8
whoops, you accidentally switched the status ;)
#9
Just commenting on the same time - rechange to fixed.
#10
+1 Really positive efforts happening here.
wolfflows work on the comment merging has been great. It's a needed bit of housekeeping.
I'd like to suggest he gets in the habit of asking an English-native speaker to proof-read any large lumps of original content though ;-) ... y'know what I mean.
#11
Automatically closed -- issue fixed for two weeks with no activity.