Repository navigation
Project Aspects
#Aspects to consider
##Abstract From the wiki post, and Project Proposal, this document hopes to expand on the "Aspects to consider" section in more detail, and prove a reference to solutions that would meet the objectives in building a distributed, highly scalable information system utilising only existing Open Source technologies and libraries.
##Summary
Below is an outline of the functional dimensions of the proposed global website, incorporating specific features suggested by ZM members during the consultation process:
-
Information management
- ZM vision, principles and aims
- ZM news
- ZM media materials
- Steps to activism
- Presentation of easy-to-do immediate actions
- Educational materials
- ZM organizational structure
- Chapters
- Teams
- Projects
- Personnel
- Membership
- Map and statistics
- Online users display
- Question and answer service
- Archive
- Parallel organizations and movements
-
Project management
- Project proposal and implementation system
- Collaboration tools
- Decision-making or polling features
- Specified project development
- Town Hall meetings
- Resource bank
- Think tank
- Solutions project
-
Team management
- Chapter coordination, access and local contact
- Chapter search
- Chapter creation process
- Calendars
- Voice meetings calendar (TeamSpeak)
-
Social networking
- Reputation/trust-building
- Secure communication
- Short message service (aka tweeting)
-
Content management
- User contributions
- Forum
- Blog
- Document upload
- User personalization
- Homepage customization
- Subscription and notification management
- Recent activity
- Latest news
- Favorites menu
- Search/filter tools
- User contributions
-
Integration
- Single ZM login globally (e.g. OpenID)
- News and information aggregation
- Zeitnews
- Science, technology and innovation
- Social breakdown and protest
- Transition and resilience
- Localization and targeting
- Chapter information and contacts
- Calendar
- Translation
- Integration with other ZM websites
- Incorporation of compatible third-party tools
-
Design
- Esthetics, logos, images
- Mutable logo (as per Google) with clickable mutable info
- Interface accessibility guidelines
- Help and bubble hints
- Esthetics, logos, images
-
System tools & technical approach
- Databases
- Security and security testing
- Email management
- Hosting & server provision including use of peer-to-peer, cloud and 389 directory server (LDAP) services
- Mobile device features
-
Organizational features
- Roles and responsibilities
- Timetable for roll-out
- Schedule for maintenance
- Oversight and administration
##Information management
##Project management
##Team management
##Integration
###Groups/Permissions This deals with who can see what and needs to be self governing without the need for having to request permissions in order to do something.
###UI Interface The UI interface section has the most suggestions and it has to boil down to the fact that people are different and require different ways to access the same information. Thus the platform must be flexible, easily localizable and conform with Section 508 and WCAG. Also the content has to be organised so that it can be easily accessible within a maximum of 2-clicks.
###Communication The communication analysis can be broken down further into:
- Structure - the data must be organised and stored securely and without data loss on the physical level.
- Organisation - this deals with how we group the content, for example, calendars, files, comments
###Indexing/Search The application needs to ensure that content is able to indexed correctly so that the end user is able to find it in an efficient manner.
##References
http://admin.1synergy.org/zglobal/wiki/project-proposal
https://docs.google.com/document/d/1TO1GqqmTvREHY51JQjPVgII4vWRXtrWdKqLUWndvyZM/edit
http://admin.1synergy.org/zglobal/wiki/current-global-connect-phoenix-status