Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
as of "takeover guidelines" http://drupal.org/node/251466 i
* filed this issue
* sent a pm
* waited 10 weeks
so i suppose maintainer markus_petrux is too busy or something.
+1 for @axel.rutz. This is a critical module and @axel.rutz has picked up the baton for D7. It's very hard for new users to find his sandbox with the current. Please give him control over the project.
Hello, markus_petrux. I am writing you because axel.rutz (http://drupal.org/user/229048) is willing to maintain the project.
Please reply on http://drupal.org/node/1105850. Don't reply to this email message, as it would be wrongly marked as spam, and I could not read your reply. If you don't reply before two weeks, the project ownership could be passed to axel.rutz.
Best regards,
kiamlaluno
Drupal.org site maintainer
Drupal.org git administrator
@Axel: Apologies for the delay. Sadly, I haven't had much spare time in the past weeks. So, I have given you maintainer access to the WYSIWYG Filter project.
This is a module that is critical for a couple of projects of mine. So, please do not add more features. If you want that, then I think it would be better to fork the module. In fact, something like this would have to be included in Drupal core, I think. Keep that in mind when thinking about new features.
Related to that, there have been requests to support more tags (iframe, embed, ...), but I have refused to do that, because it'd pretty complex to do it properly, or it would open a security hole. If someone needs more features not included in WYSIWYG Filter, there are alternative modules to look at, such as HTML Purifier or htmLawed.
i read those issues and see and share your point!
and i think this point might be put on the project page in more explicit words - i'll think about that and open a doc issue for that (as i don't have access to the project page).
as for other ideas i have i think it's always a good idea to open a feature request to allow other maintainers to comment.
oh, I write that manually. Hopefully the existing history can give you an idea of the style. I think this is a format that is still used by CCK and other modules here.
Comments
Comment #1
geek-merlinas of "takeover guidelines" http://drupal.org/node/251466 i
* filed this issue
* sent a pm
* waited 10 weeks
so i suppose maintainer markus_petrux is too busy or something.
i wanna maintain
http://drupal.org/project/wysiwyg_filter
which i already do from my sandbox
http://drupal.org/sandbox/axel.rutz/1105784
and the "d7 issue"
http://drupal.org/node/865034
Comment #2
tim.plunkettI will follow up with this soon.
Comment #3
bryancasler commentedsubscribe
Comment #4
capellicLooking forward to this module moving forward.
Comment #5
Shai commented+1 for @axel.rutz. This is a critical module and @axel.rutz has picked up the baton for D7. It's very hard for new users to find his sandbox with the current. Please give him control over the project.
Thank you,
Shai Gluskin
Owner, Content2zero Web Development
Comment #6
avpadernoComment #7
markus_petrux commented@Axel: Apologies for the delay. Sadly, I haven't had much spare time in the past weeks. So, I have given you maintainer access to the WYSIWYG Filter project.
This is a module that is critical for a couple of projects of mine. So, please do not add more features. If you want that, then I think it would be better to fork the module. In fact, something like this would have to be included in Drupal core, I think. Keep that in mind when thinking about new features.
Related to that, there have been requests to support more tags (iframe, embed, ...), but I have refused to do that, because it'd pretty complex to do it properly, or it would open a security hole. If someone needs more features not included in WYSIWYG Filter, there are alternative modules to look at, such as HTML Purifier or htmLawed.
Comment #8
tim.plunkettSo... then this is fixed?
Comment #9
geek-merlinyep, fixed.
@markus,
i read those issues and see and share your point!
and i think this point might be put on the project page in more explicit words - i'll think about that and open a doc issue for that (as i don't have access to the project page).
as for other ideas i have i think it's always a good idea to open a feature request to allow other maintainers to comment.
Comment #10
geek-merlin@markus: can you provide me your changelog script so we keep unified style?
Comment #11
markus_petrux commentedoh, I write that manually. Hopefully the existing history can give you an idea of the style. I think this is a format that is still used by CCK and other modules here.