module development

I am working on a site that will be selling courses on and off-line and am in the process of designing a module to handle this. I would be interested in people's opinions on the best way to go about doing this.

The requirements for courses are as follows:

Web Applications Programmer

Reply to: employment@ewg.org

The Environmental Working Group (EWG) is a national, non-partisan organization that uses the power of information to protect the environment and human health. EWG seeks a detail-oriented, creative, deadline-driven applications programmer to assist with development of ewg.org and our other web sites. This full-time position is based in our Washington, D.C. headquarters.

RESPONSIBILITIES

Well, after many hours of development, experimentation, API referencing, and good ol' fashioned beating our heads against our desks, we have finally got an initial release of the Übercart module package available for download. This is being considered an alpha release, with the official 1.0 release being many development hours away as we build on and flesh out some of the core systems. However, the module package as it stands is able to run e-commerce sites and is already being used in live sites. Everyone is welcome to showcase their Übercart site in our forums!

I just recognized that there are three modules besides phpfreechat that claim to provide chatting features for a Drupal site. After a quick look at Buddy Chat, Chat Box and Chat Room I wasn't able to understand the differences between those modules.

The revision system.

Drupal has a great feature whereby editing a node can create a revision of that node. Whenever create new revisions is checked under Publishing options, editing a node will result in a new revision. Users with the view revisions or administer nodes permissions will see a Revisions tab on node viewing pages. The Revisions tab interface allows you to view the individual revisions, revert to an earlier revision, and delete revisions.

One interesting detail of the system is the behavior of the reverting mechanism. Let's say you have revisions {1,2,3,current}. If you revert to revision #2, a copy of #2 is made and the copy is set as the current revision. Thus, after reverting you'll have {1,2,3,4,current}, where current is a clone of #2, and #4 is the previous current revision.

Has anyone successfully implemented og where each group lives on its own subdomain, but on a shared code base? We are looking at this as an alternative to a multi-site (separarate dbs w/ shared users) implementation. The wrinkle on this project is that the site could grow to a couple hundred subdomains. They don't need to be added on-the-fly via admin interface.

Any suggested approaches to this?

Is there a roadmap anyone might suggest for feature enhancements or supporting module development we might consider for the og module package itself?

(If 5.0 beta proceeds well, we'll likely be wanting to build this in 5.0 as well.)

I'm going to try and outline some notes from the Wiki session at DrupalCon. I may have missed some big ones. This is a good example of where a wiki would be nice - to make this list. Is it safe to say it is not certain whether to use Drupal modules and glue to make a wiki, or whether to integrate a wiki into Drupal? Maybe it depends on the case?

Basic and necessary

Access control

Here is the current state of affairs: there are two modules (created by Khalid Baheyeldin) that deal with the stock market: stock and stockapi. The first one deals with displaying stock pricing information in both a page format and in a block format. The second one is an API that the first one uses to get the stock information. The API uses Yahoo! Finance as it's source of stock information.

I'm thinking about a database which is storing:
- Project name
- Download file
- Module name
- Date
- MD5 and SHA1
- Module description
- Drupal Version
- README.TXT or INSTALL.TXT
and programming an interface (module) to check these against your own installation.

What I need is to download all "[PROJECT].tar.gz" files and import these into a database. This was the easy job (simple devel example).
Currently this is done with a CCK designed table, but I will switch to an own node-type cause of some CCK restrictions (e.g. search).

the next two steps are writing:

Is there anywhere a way to get data:
- Hown often are modules be downloaded?
- Which modules are installed?

Like from:
- http://drupal.org/node/46109
- http://drupal.org/node/25704
- admin/settings/drupal (Send system information)