Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Jun 2011 at 08:00 UTC
Updated:
6 Jan 2012 at 18:38 UTC
The FAQ with easy asking functional module allow users with the 'create faq
question' permission add new FAQ node fill only question field. Users with
'create faq answer' permission can add answer on this question and publish node.
Also they can admin questions on page faq/unanswered. Module create for Drupal 7 version.
This module is have some same functional with another module FAQ_Ask. But now that module have critical bags, and it can`t used on production site.
Comments
Comment #1
sreynen commentedHi rbogdan,
As a general rule, we don't approve modules in this application review that duplicate functionality of existing modules. If the existing module, in this case FAQ_Ask, has bugs, the preferred solution to that problem is to fix those bugs. Have you tried contributing to FAQ_Ask rather than starting a new project?
I'm setting this to "needs work" awaiting your response.
Comment #2
rbogdan commentedHello sreynen.
Today i have time to try fix bugs in FAQ_Ask project. Some of them i fix, but there is many other remained in code, and to fix them need much time. And without fix all of them FAQ_Ask module can't work on Drupal 7 sites.
Also i see what differences between two projects. In FAQ_Ask work only if FAQ module use "Categorize questions" dependent on taxonomy, without this option module don't work.
In FAQ_Ask functional of create questions and answering on questions contain in blocks. In my module it contain in tabs and in add some functional in main faq page content.
Comment #3
jthorson commentedrbogdan,
I haven't looked at the code, and haven't used FAQ_Ask, so I don't really know how your module compares with the FAQ_Ask module. However, since the descriptions seem similar, and the FAQ_Ask code is not production ready, and the FAQ_Ask maintainer has posted the following quote in their own issue queue, have you considered approaching the FAQ_Ask maintainers to see if they'd consider accepting your module as a full replacement for the existing FAQ_Ask code; as an option to fixing the existing bugs?
If they are agreeable, I believe the existing owners can grant you commit access to the FAQ_Ask module themselves. While we certainly encourage contributing to an existing module rather than developing a competing module of your own, there's no rule that says your contribution can't be a complete rewrite instead of dealing with the existing bugs.
In the end, having only one working option is better than making end users choose between a "new and working" option and the "more established but broken" one ... too many of those users are going to initially assume that older means better.
Based on Stenjo's quote above (which dates back to January!), the existing maintainers may be perfectly willing to accept your code and scrap the existing -dev version. This is a perfectly valid approach ... and one which should at least be discussed with the FAQ_Ask maintainers before introducing a competing module.
Comment #4
klausiNo activity in several months. Reopen and set the status to "needs review" if you are still pursuing this application.