socialappslab / appcivist-mobilizing-groups Goto Github PK

Based on what comes out of issue #9, create a draft of:

• The list of operations needed to support the creation and management of working groups, in such a way that they can be mapped to either of the three systems selected in #9

Observations:

• On the next General Meeting, we will decide whether we follow up this thread or not
• Working Groups in AppCivist will support the flow of all other capabilities, by establishing who and how can access the different resources of the process (i.e., what members of a group can do with AppCivist issues, proposals, discussions, events, etc.)

[This is for @jamesholston]

Change settings of the repository to:

• Allow the creation of milestones
• Allow the creation of Labels
• Allow the assignment of issues to members of the @socialappslab/appcivist-team
• Assign the repository to the @socialappslab/technical-managers team

https://typesafe.com/activator/template/play-spring-data-jpa
https://github.com/socialappslab/appcivist-deliberation/tree/master/deliberationV1

Add the following github users to the team @socialappslab/appcivist-team

• frschmidt
• Mark when he creates one

Although not connected to this repo in particular, we will also need to add

• jennyfromtheweb

Follow comments from last general meeting
Concentrate on 3 screens and improve them

One screen showing:

1. The event Archive

• The whole stream of updates, integrating Twitter, Instagram, Facebook
• A list of important resources or links that resulted from the event (e.g., documents that summarize results, news mentions links, etc.)
• A list of events highlighted results

Create the following milestones, once issue #6 is closed

Semester Milestones:

1. Final version of the event organization control center Mockup (due to the end of the semester)
2. Final draft of the API operations for the event organization control center (due to the end of the semester)
3. [Optional] Final version of the working groups management API (due to the end of the semester)
4. [Optional] Initial prototype implementation of API with playframework

Current Week Milestones:

1. Event's Mockup version 2
2. Initial list of operations version 1

Based on the features that will be part of mockup v2 (issues #2, #3 and #4), create the following:

• A list of operations to support the functionalities in these screens (e.g., createEvent)
• For each operation, define what's the input and what's the output (e.g., Event Title, Event Description, Event Date, etc.)

Observation: We will decide on the next General Meeting whether we follow up this thread, or if we just focus on the event's milestones

Take the following three systems:

1. Facebook (a traditional social network)
2. Google Groups (a popular email based group)
3. Loomio (a system oriented to activists)

Identify commonalities and differences in:

1. What are the properties of the group
2. What type of operations can they perform

One screen where the event is being broadcasted:

1. Screen where event details are being broadcasted:

• Show updates coming from Twitter and Instagram (i.e., posts with the event's hashtag)
• A button to post updates (which automatically posts these updates to the Facebook page of the event, to Twitter and to Instagram - if there is a picture)

Although this was already done by the group, please link in the comments to the mockup for the sake of a history

Two screens:

1. A screen that shows the information needed to create the event (e.g., title, location, whether is face to face or online, start and end date, hashtag to identify it etc.)
2. A screen that shows the event details and its Facebook page, which was automatically created after (1), with some buttons for:

• Invite people
• Promote in other social media
• Post update (which is directly posting the update to the facebook page)