I want to contribute a achievement_entity module, which include the below functionality.
This module uses Achievement module and has its own entity UI to handle achievements as an entity. It has 3 entity types:
Badges – This entity type provides an interface to create badges. Adding fields gives it a flexible data model.
Issuer – This entity type provides UI interface for admins to define issuer information.
User Group – This entity type provides UI interface for users to manage their badges in the backpack.
This module will allow receivers to manage their earned badges by
-Maintaining their own backpack
-Setting the privacy of badges as public/private
-Grouping the badges
-Pushing the badges to Mozilla backpack
Motivation to create this module to create badges through interface which is easily add and remove by interface.
Project Page: http://drupal.org/sandbox/ebizondrupalservices/1826730
Sandbox url: ebizondrupalservices@git.drupal.org:sandbox/ebizondrupalservices/1826730.git
Comments
Comment #1
sudeepg commentedComment #1.0
sudeepg commentedIt creates badges using achievements module with achievement_entity entity type.
It creates user interface to create badges and issuer information.
Comment #2
klausiSetting priority to normal, according to http://drupal.org/node/539608
This sounds like a feature that should live in the existing achievements project as 2.x branch. Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please open an issue in the achievements issue queue to discuss what you need. You should also get in contact with the maintainer(s) to offer your help to move the project forward. If you cannot reach the maintainer(s) please follow the abandoned project process.
If that fails for whatever reason please get back to us and set this back to "needs review".
Comment #3
sudeepg commentedThis module is dependent on Achievement module but has many enhanced features over achievement, which are:
1. Badges can be created with this module using UI whereas Achievement module just provides an API to give, take and show Achievements/Badges on user's profile.
2. This module also allows user's to push their badges to backpack on site and also on Mozilla backpack whereas Achievement module requires additional module "amobb" inorder to push the badge to Mozilla Backpack.
3. User's have the option to set the privacy of their badges.
4. This module gives a Badge management interface to manage multiple assignment of badges to multiple users.
All in all this module provides a complete OBI complaint badge system and users who want an OBI complaint badging system can use this module as it is. This has also been approved by Intel and Society for Science.
We have also spoke with the owner of Achievement module and informed of the dependency of our module over Achievement. We asked if they plan to include the additional features described above in future but it was confirmed that these features are specific to our need and they dont plan to include them.
Please suggest what should be the next step?
Comment #5
morbus iff@klausi: this stuff wouldn't ever make it into the core Achievements branch (that module is fundamentally opposed to allow UI-based creation of achievements, as described on its project page), and this code also includes a lot more stuff that isn't part of the core Achievements package (such as Mozilla backpack integration, something which also already exists in http://drupal.org/project/amobb).
Comment #6
morbus iffComment #7
morbus iffI think the code in the current sandbox is not meant to all go into one Drupal project, right?
I can easily see these things being split out into their own projects though - "Achievements as Entity", for example, would be a good one (though, I've not looked at the code fully yet, so I'm not sure how points are being handled), "Achievement User Permissions" would be another one (a module that allows users to decide the privacy of their own badge), etc. I'd be happy to link to them from the Achievements project page.
As it stands, though, I don't think the sandbox, in its entirety, should be a single Drupal project - there's just
too much "stuff" in there, and it almost sounds like an install profile, not pick-and-choosable extension modules.
Comment #8
sudeepg commentedYes, Morbus. This is a single project with sub-modules in it. We would like to release this as a separate project. However, it would be good if you can link it in your module page as well.
Drupal team, can you please give us the permission to release this as a separate module? Morbus is the author of achievement module and it makes sense to not release it as achievement branch and instead have it as a separate project.
Comment #9
klausiWe are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)
Comment #10
mohs3n71 commentedhi ,
1 ) your sandbox link is invalid and you should copy your git clone link here
2 ) README.txt is missing
3 ) Remove all old CVS $Id tags, they are not needed anymore.
like this :
achievement_entity/modules/achievement_notifications/achievement_notifications.module:3:// $Id: achievement_notifications.module 108 2012-09-05 05:17:57Z vaibhav $4 ) you have many errors and warning in your code use this website http://ventral.org/pareview/
for finding and fixing your errors
Comment #10.0
mohs3n71 commentedProject page link
Comment #10.1
sudeepg commentedchange sandbox url
Comment #10.2
sudeepg commentedSandbox url
Comment #10.3
sudeepg commentedchange git url as sandbox url
Comment #10.4
sudeepg commentedgit clone url
Comment #11
sudeepg commentedThanks for valuable suggestion for our project. We have updated sandbox URL and working on other things which is explained by you.
Comment #12
sudeepg commentedThanks for the review, Mohsen.
We have fixed these errors/warnings that were showing up.
Comment #13
sudeepg commented@klausi, we would like to help with reviewing to get review bonus :) Thats a nice concept...didnt know of it. I will come back on this.
Comment #14
stborchertBack to "needs work" since there are several tasks to do:
You can find the results of the automated report at http://ventral.org/pareview/httpgitdrupalorgsandboxebizondrupalservices1....
Consider moving the contents of "achievement_entity" to the main directory. Otherwise it could be very confusing after downloading this module.
Comment #15
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #15.0
PA robot commentedupdate sandbox url