merge into activity? why another monitoring module? [#332983]

as drupal progresses, it would be nice to see devs with skills and awesome ideas review overlap with existing efforts - clearly this module overlaps directly with activity, which already has a number of contrib modules (for all user actions, og actions, commenting, voting and all other activities)

this sounds like the same thing witha slightly different spin, but same concept...why not considering merging ideas or at least review ideas with activity to make ONE awesome module instead of, once again, competing solutions that stand to confuse drupal users..?

just a thought. or perhaps i'm missing something, is this very unique and different from activity?

Comments

Comment #1

Flying Drupalist CreditAttribution: Flying Drupalist commented 12 November 2008 at 00:22

I think this is more similar to activity log than activity. And I think that the rules approach is better than activity, and if anything it's activity that should be merging into here rather than this merge into activity. I think you're missing the point zilla that if this module works as intended then you won't need any contrib modules, all modules would feed info into rules and rules would spit it out to this one.

Though the maintainter should check out activity log.

http://groups.drupal.org/node/15088

Comment #2

zilla CreditAttribution: zilla commented 12 November 2008 at 01:48

sounds like i missed something - is this module all rules based? that's a very smooth approach for the long haul...the fewer modules the better!!

Comment #3

Stalski CreditAttribution: Stalski commented 15 November 2008 at 18:12

Hellow,

Miraploy is fully correct. I am building this module as extension to activity log. mercmobily said I could try to do whathever i wish to take his module further.
So the only question is : why make a new module?

I need a repository (most important)
I will eventually merge my effort to the effort of activity_log (mercmobily). He did not have the time to take his module further for now so he let me try. Big difference between our thinking is that his module needs to stay simple, while i don't have an issue with that. I need a facebook thingy in my current project at work, so I have no choice
I had a long discussion (nice one) with mercmobily and others on this topic and the only problem we had, is that i need/want a lot more to happen than activity logging. user activity is based on activity log. The things i want extra is multilinguality, karma, user points system ... so in general the community approach.

Again i will go with Miraploy on the rules approach, because me too , I think this is the way of doing exactly what it can do. Even further, rules should be in the core of drupal imho.

Thus, it could be after I am done ( a month to be precise), this module disappears and I will end up working with activity again. I just want the future to decide, because that is the whole point with drupal contributes ... sometimes you have to see it before jump to conclusion.