Team meeting 7/14/2011
Meeting Agenda and Notes - Special Meeting to Flesh Out Deliverables
Mike will be gone July 19 - August 2
- Jimmy/Todd: Project management UI discussion & implementation
- Noam: Polls, decisions, and surveys proposal that is generic, and a simpler version to implement this summer that is not throw-away code
- Jimmy/Todd: Document/comment viewer discussion
- Jimmy/Noam/Todd: Group collaboration discussion
- Mike: Customizable website implementation
- Noam: Fullscreen/fontsize implementation
Deliverables by 9/30/2011:
- Project management tool integrated with discussions . The platform should free users to focus on the content of the issue by managing routine tasks in an automated fashion. Users should be able to create and edit to do items without leaving the deliberation areas. - do as module
- Examples: basecamp, jira, toodledo, asana.com
- Flexible polls and decisions. Multiple, easy to use options for binding and non-binding decision making should be provided. Rules or guidelines should accompany the tools, how to vote, deadlines for voting, help resources; along with user ratings of tool performance. - do as module
- This is a narrow, one-week-implementation proposal (DONT DO THIS)
- Poll(question: String) extends Item
- PollProposition(poll: Poll, answer: String) extends Item
- PollResponse(poll: Poll, proposition: PollProposition, agent: Agent) extends Model (unique_together = [poll, agent])
- TODO: formulate a more generic proposal, find ways to only implement partially without being throw-away work (Noam)
- See Decision items and action at http://groupspace.org/deme/groups/Demo-Group/marea/?marea_id=1
- Co-visibility of in-text comments and documents. Text and comments should be visible together in the interface, with clear pointing relations and cross-linking.
- Implement dotted line pointer between located comments (in document) to comments (in side bar), only on hover/click. (Noam, 1 week)
- highlighting of current comment in text
- make comment display work better
- design an interface by Tuesday 7/19 (Todd and Jimmy)
- Multiple meeting areas per group space. The platform should provide private space for groups and sub-groups. This would mirror normal group structures, such as committees, sub-committees, task forces, specific interest or cohort groups, etc.
- Groups that are Members of a Group are subgroups (subsets) that extend the Group for permissions
- Other Groups can have their Folios as members of a Group's Folio
- UI needs to be modified so users can better interact with Groups and their Folios, including subgroups and folios of other groups with a folio (Todd, Jimmy, and Noam will come up with a design July 20-22)
- Ability to share meeting areas across groups. When different groups wish to combine or share their spaces and resources, the platform should facilitate this for any length of time needed, within the norms established for the project and by the groups.
- This will be described in "multiple meeting areas per group space" proposal
- Customizable group website, editable and configurable through the web interface. Existing Deme functionality should be enhanced so that users without programming skills can manage the look and feel, as well as the content, of a group's website.
- Create a new subclass of DjangoTemplateDocument called PremadeDjangoTemplateDocument, which has fields like "page_title" and "page_logo".
- It wlil also have a field called "skin". We will have a new skins/ directory that contains different HTML layouts, each with its own static directory.
- The body field will be synthetically generated from skin's django template, substituting these fields in.
- We may have to create a new item type called CustomDjangoTemplateDocument that allows you to edit the body, and have DjangoTemplateDocument not store state but only have a get_body() method
- Change create_initial_data.py to use the default layout, and change deme.stanford.edu to use it (leave symsys alone)
- Mike will do when he returns from china or possibly earlier
- WYSIWYG editor would be very challenging - good long term goal
- Optional sorting methods for discussion items. Discussion items should be labeled and searchable. Users should be able to search for, view and sort threads by subject, item, date, author, group affiliation; and see links to associated To Do items.
- The non-threaded view can depend on Mike doing the ajax list viewer, which will not easily support highlighting, but may be able to if we formulate exactly what is necessary
- The threaded view will be discussed in "Co-visibility of in-text comments and documents" - see http://groupspace.org/base35/deme/groups/deme-team meeting area interface (thread view of comments) - could be switched to from grid/list view
- Mike will write list viewer when he returns from china
- Expandable viewers. Viewing items should be easy and adaptable for all users. Full screen options should be easily invoked. Text size and font options should be available to make for easy reading
- Assume full screen means full browser window and/or popouts
- Fullscreen - 1 hour, search on how to do in Javascript
- Put on layout - Noam will do this
- Resize text (1 hour):
- Put on layout - Noam will do this
- Dictionary, thesaurus, and translation options would be accessible via the viewer.
- Blocking on document viewer proposal, should be part of that discussion
- Full document translation via some web service (non-html, 1 day; html, not sure)
- Dictionary/thesaurus/translation, from a highlight
- Still need to discuss where to place these options in the UI
- Look at Ben's highlighting code from v0.6
Comment Tools
Add Comment
Show Located Comments
Hide Located Comments