Documentation Mailing Lists FAQ Roadmap - Questionaire Responses for AA CAMP 2004

Add new suggestion (editors)
Add new suggestion (techies/administrators)

1. Main problems and annoyances you encounter when using ActionApps

2. Features suggested for future development versions of ActionApps
Feeding improvements - reconsider "content pooling"

This is somewhat related to the following item from the development roadmap: "feeding improvements (the change in child item will be offered for acceptance/rejection to ALL 'sharers' ")

When we first developed specs for AA, there was some debate over whether we were enabling "content sharing" or "content feeding." Feeding won, even though our marketing copy still talks about "content pooling" :)

What we have is "feeding" because it's hierarchical. Even in the most complex feeding structure, every item has a parent-owner and a child-recipient.

A new step would be to enable full *collaboration* between slice owners in editing and updating items. In most feeding relationships I have ever set up, this would have been the desired behaviour.

For instance, we have several groups of organizations that maintain overlapping contact lists. These organizations trust each other. Each would like to have the benefit of updates performed by *any* of them on contact records they share. Same goes for groups with overlapping events calendars.

In other words: no *item* would have a definitive parent.

The capacity for this kind of collaboration -- true content pooling -- could be one of the most unique and NGO-aware features of AA.

By *also* deploying some accept/reject option for fed changes, we would make this content pooling SAFE for participants in a pooling group.

3. Comments About Usablility

4. General future development suggestions

Submited by:
John Hall

Jun 3 2025

APC ActionApps is a free software content management system initiated by the Association for Progressive Communications (APC) APC - Internet and ICTs for social justice and development