My firm and I have been working with Drupal for the last year and have built a couple of modules that we use internally. Some of these modules have matured and we want to offer them back to the Drupal community. These modules are:
- Node histogram. This module is a Views plugin that allows you to select a particular field through a view and provides histogram statistics on the frequency of occurrence of all values within the field. It also allows you to separate out multiple values in the same field separated by some separation character (for example: "Apple, Orange" could be counted as Apple and Orange separately).
- Extended phone (CCK field). Similar to http://drupal.org/project/phone but allows to provide a label (main, mobile, fax etc.). Something the original module maintainers did not want to add. It's also more forgiving on the validation to allow for vanity numbers etc. 1-800-APPLE12
- A few other small CCK field modules. We need to evaluate for each whether it is worth contributing them and check if similar modules have appeared in the mean time. They circle around CCK type combinations (for example, have two text fields with customizable labels that can be used in multiple value arrangements - something CCK does not allow).
- Adulmec bar - this is a bit like the Wunderbar project that just got released. We started working on it before we knew about Wunderbar. Our goals are a bit different with the project (more flexibility, different use case, support for caching, better performance over eye candy). We will see if we can combine efforts with the project maintainers on things before we would contribute a separate project.
- OpenForis - A universal login system that allows people to share the same user name and password across multiple sites (not necessarily Drupal multisite or on the same server even). It's a bit like OpenID but more Drupal-like and allows to use regular usernames or email addresses to login.
- A few others are in the works as well.
In general, we share the goal of wanting to avoid project duplication over minor feature differences - nothing is more frustrating for users including us. We have also modified several existing projects internally and tried to contribute the improvements back to the projects. Not every maintainer was cooperative and some modules appear to have been abandoned. We would be willing to take over a few of these projects if that turns out to be indeed the case. We are also very excited about Drupal 7 and will release Drupal 7 versions of our modules in a timely fashion.
We have read the rules and will submit everything conforming to the coding standards (using Coder module and manual review). One of our employees is a long standing Drupal user (http://drupal.org/user/8662) and will be contributing OpenForis under his CVS account but the other projects are being maintained by other employees and we want to give them a separate CVS access.
Thank you very much for your time and consideration.
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | linkbar (March 14).zip | 55.6 KB | kerberos |
| #13 | linkbar.zip | 16.49 KB | kerberos |
| #3 | views_histogram.zip | 6.4 KB | kerberos |
| #1 | linkbar.zip | 16.49 KB | kerberos |
Comments
Comment #1
kerberos commentedComment #2
avpadernoComment #3
kerberos commentedHere's one of the other modules we have been working on.
Comment #4
avpaderno@kerberos: We just review a module / theme per applicant.
Comment #5
kerberos commentedUnderstood. My apologies. Please disregard. :)
-Daniel
Comment #6
avpadernoThere is already a module with such functionality: http://drupal.org/project/appbar.
Comment #7
kerberos commentedWell, their approach is somewhat different. As they state on their project page:
"Note: Neither anonymous users nor users with JavaScript disabled in their browser will see the Appbar."
Ours is visible for all users (assuming they have the permission) and does not require JavaScript and aimed at providing a simple and highly theme-able way to link to your external links (although it can be used for internal links as well).
Lastly, our module just focuses on adding the links in a highly scalable way to the bottom bar. Appbar is aimed at internal site links and notifications and integrates with Views, Activity, Menu Icons, Rules, and the core Trigger module, so it's a fairly heavy-weight module for a simple task. It fits a very different need and I am not sure those needs can be reconciled.
Comment #8
avpadernoThe comment refers to the second function, not the one directly below it. It would also be better to separate the functions with an empty line.
The indentation of the code is not correct; check also that you are using two spaces, and not a tab character.
Schema descriptions should not be passed to
t()anymore. See system_schema() for an example of what done by Drupal core code.The update function is not executed when the module is first installed. As the module is not still hosted on drupal.org, you can remove that function.
The comment should say (as other hooks as well).
Comment #9
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .
Comment #10
kerberos commentedMy apologies, I was gone for the holidays and still catching up with backlog from then. Can we reopen this or should we reapply?
Thanks.
Comment #11
avpadernoComment #12
kerberos commentedPlease give us 7 days to respond. Thank you!
Comment #13
kerberos commentedI think we fixed everything. Let me know if there are any other issues. Many thanks.
-Daniel
Comment #14
avpadernoRemember to change the status, when you upload new code.
Comment #15
kerberos commentedMy bad, thanks.
-Daniel
Comment #16
kerberos commentedWe have a few other (probably more important) modules we'd love to contribute as well. Should we create new issues for these or wait for the review of this one?
-Daniel
Comment #17
avpadernoDatabase schema descriptions should not be passed to
t(); see what done from Drupal core modules.As the function is just returning a record, the code should use
db_query_range().Comment #18
kerberos commentedOk, I hope we fixed everything this time. Sorry for the many reviews. :(
-Daniel
Comment #19
kerberos commentedAnything we can do to help out with this?
Thanks.
Best,
-Daniel
Comment #20
kerberos commentedJust checking in...
We have 3 other projects (probably more needed by the community than this one) to contribute - but since we are not supposed to submit more than one, this is sort of holding everything up. :(
-Daniel
Comment #21
avpadernoComment #23
jcisio commentedWhy the status changed to "fixed"? Was the applicant granted CVS permission?
Comment #24
avpadernoYes, he did.
I change the status to fixed right before to approve a CVS account.
Comment #25
jcisio commentedOk thanks, I just wanted to verify, as he hasn't any project or commit.
Comment #26
kerberos commentedHi. Sorry, we have a few things almost ready to commit, but we are still coming up to speed with D7 and git.
Thanks.
-Daniel
Comment #28
avpadernoPlease don't use the CVS application issue to report issues with existing modules. The purpose of this queue is to document the process of approving a CVS account.
Comment #28.0
avpadernoSet the comments to read only.