"This module is in the re-architecture period. All changes will happen in 2.x branch"

Why not do this in Flag Abuse or Flag Content?

I'm just researching without knowing the differences between modules in this stage, but suppose there is something to say for integrating them all? Which module is the most advanced? Maybe all developers in one team?

Comments

ClearXS’s picture

ClearXS commented

OK; I see in the statistics of these modules that module "abuse" is the most popular, although when plussing Flag Abuse and Flag Content, the difference is not that great anymore.

Maybe then the question: Why not integrate their specific module functions in "abuse"? Get it to work with Flags, Views, a.s.o.

Actually the statistics of Flag Abuse that has these features, are high and still booming without hesitation yet.

But then; why 2 modules that do the same; better have the developers work together on one?

Then the name: "Abuse" is more general than "Flag Abuse", implying that "Abuse" could have new functions beyond flagging only like spam detection, or that "Flag Abuse" should be used as name on joining the projects, if no new features follow.

ClearXS’s picture

ClearXS commented

Similar discussion on Flag_Content: How is this different from flag abuse? - http://drupal.org/node/436930

Similar discussion on Flag_Abuse: Consider working on the Abuse module - http://drupal.org/node/769050

jcisio’s picture

jcisio commented
Status: Active » Closed (duplicate)

See #408126: Abstract the way Abuse stores data to allow modules like the Flag Abuse module to become data storage for the Abuse UI (read coments).