• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Roles of the Developers

The developer need not be the class owner. This role cannot be reassigned, so in mid-development of a new class that has not been versioned, another developer cannot take over and continue what the first one started. This means that copying another developer's image with editable classes in it, sharing passwords, and then concurrently working in the same class editions is a no-no. ENVY will not let either developer version the class until conflicts are resolved.

Responsibilities

The manager of an application must communicate with the managers of the contained subapplications (there can be different managers for an app and each of its subs). The app manager can be made responsible for the integration of their application and its subs. They are responsible for documenting the application (yes, there are application and subapplication comments). They should test the loading and unloading of the application.

The manager of a configuration could be responsible for overall integration and satisfactory testing. This role could/should be rotated among team members. The days of the "guru" approach are over with ENVY. (Unless that is what you really want to do.)

A class owner should never release changes made to their class without first verifying them. Hopefully, this is obvious.

A class developer should give a recognizable version name to his or her version, then inform the owner of the reason for their changes and ask the owner to integrate their changes. It is counter productive to the team effort to routinely change another's classes and never tell the owner about how you think it should be improved. This applies to the development environment tools, too. With ENVY, the "my image is my world" attitude (e. g., I can change anything I want, even base classes) is obsolete. (Unless that is the team culture you really want.)

[ prev | top | next ]