Due to the needs of my employer I have created a user menus module which does pretty much the same thing as both Bookmarks and Bookmarks2. The module is based on the menu code in 6.2.

There are a few features that this module has that I do plan to incorporate. At this time, the only things that I can see which are done by Bookmarks2 that are not done by User menus is rss and password reminders. Don't have a box with mcrypt so I'm not too sure what the password reminder stuff is for but if those features are being used then they would be incorporated.

Thanks.

Comments

Anonymous’s picture

deekayen’s picture

Status: Active » Postponed (maintainer needs more info)

I'm not surprised you find bookmarks and bookmarks2 similar in function, because bookmarks2 is a fork of bookmarks. The mcrypt addition was the whole point of the fork. It allows users to store login credentials alongside their bookmarks. The mcrypt part encrypts the login credentials with AES and typing your key decrypts the reminder password into memory for the next page view.

To me, titling this issue requesting to take over the project means you're looking to become maintainer, yet you didn't cite any reason other than that you have a similar module that you're already a maintainer of. Two people besides yourself have expressed interest in becoming maintainer. Is this not something that can be handled with patch submissions and/or CVS access?

Anonymous’s picture

Thank you for explaining the mcrypt part as that makes more sense now.

The goal for requesting maintainer of both this module and the original bookmarks module is to try and eliminate duplicity within the drupal project. Yes, I'm sure this could be handled with either patch or CVS. I'll also look at getting mcrypt onto a box so I can actually see how the login reminder works.

Anonymous’s picture

Double Post : Deleted

Anonymous’s picture

Assigned: » Unassigned
Status: Postponed (maintainer needs more info) » Closed (fixed)

I have reviewed the bookmarks2 module in detail and reached the conclusion that it is not in my interest nor in yours to merge the modules as they perform distinct and different actions. While these actions might be better served in a more formalized architecture in the long term they would not be at this time.