Mozilla's Community Support Software
Home Page: https://discourse.mozilla-community.org/t/iam-coss-work-week-jan-2017/13497
License: Mozilla Public License 2.0
The Community Support Software provides the tools needed for people to contribute to the issues they care about through Mozilla.
For documentation, see coss.readthedocs.io or build the docs/
Create an issue on GitHub.
Copied everything over from https://noteapp.com/hORUdAzn2l. This can help us open tickets for each item and then link them here to make sure we have everything covered.
Meeting with Lucy, Christos, Amira, and Julia. We decided to work towards a singular brand with a personalized user experience for the sub brands that allows for cross pollination. Naming/visuals will be on hold until the report from the Campus Clubs consultant comes at the end of Feb.
@alanmoo and I discussed having a list of 'things to consider when choosing a cms'. We can then quickly evaluate options against the list. Since there is no perfect option and we have a limited amount of time to make a decisions this seems like the best way to move forward. Feel free to suggest another approach. Definitely please add to this list with a comment.
Goal: Identify where we are gathering data and what we are collecting
Work with Lifecycle Marketing and Insights team to plan process to access
Front End/Admim User Feedback
Event Platform Prototype selection
Data deliverable - DEPENDENCY with LCM
CMS build out
Goals:
Getting up and running with ZenHub
*This will be a bit messy for a sprint or two as we work out how to literally do work together
Flush out initial steps for the first items in Berlin Work Week project map
Not in first steps on product roadmap but implied by work is selecting a CMS
@m-branson since you have tested an array of CMS, it would be great if you could benchmark a few. Not that we would use them, just so we can show what an ideal look would be and what type of elements we should strive for.
Probably just need to grab some screen caps and pointing out what you like about them, but open to whatever format you think works best.
Google slides would be great so that anyone can collaborate on it if they want.
mezzanine
mezzanine-cms-experiment, won't be live quite yet, env vars need to be sorted out firstfirst steps:
We have a repo and no longer have to use the Network repo! I'm making this the main ticket. Summarizing what we've done and what we still need to do.
Identify gaps between what our current structure supports and what we need
Create Wireframes for Clubs Prototype to test then build.
Overall goal of being able to tell what is working and why at the programmatic level and to provide a great UX to users.
Let's continue the conversations from last week- what are the needs of the events section of the platform, from different perspectives?
Ongoing user testing.
Lots of in process 'event' type work happening across Mozilla. First step is to gather and centralize.
Identify main community like sites and figure out what if any CMS they are using. Having a list of currently used CMSs will help us figure out if there is a choice that will aid in future scale.
I've started brainstorming some possible attributes in this spreadsheet.
@a-kilroy you have a better understanding of the purpose/goals for this so could you please add that context to this ticket?
Time activated hashtag feed
Individual club social links
Individual club social shares
Hashtag feeds
Talk to program staff who are currently using Django as a CMS. Find out what types of updates they are doing with it and identify pain points and wins.
We can identify staff based on - Mozilla current CMS inventory #24. This will help us decide if Django is a viable CMS platform for us.
I will expand on the user flow and IA work we started during the work week. This will give us a big picture view of all the moving pieces and compare what we are currently doing (and the problems with it) vs our streamlined proposed solutions.
We can then overlay a list the current technologies used (example: google spreed sheets, emails, production team...) vs proposed technologies/Strategic Domains (example: Sales Force, Content Management System, Events Platform...).
We can then see how the Strategic Domains we build for Clubs can be used on other sites (example for Advocacy events, shared CRM newsletter lists...)
User Flows
Information Architecture (IA)
Feedback
I will make all of these in Google Slides so everyone can edit. Once I've done the first pass, I will need help and feedback from @simonwex @a-kilroy @jvallera @amirad @Lucyeoh @bacharakis
Current Mozilla Clubs user flow (with current technologies and proposed Strategic Domains)
Proposed user flow
Strategic Domains Reference
Paper Wireframe Prototypes
I will start the IA by pulling key pieces from the wireframes we created. @a-kilroy can you please add photos for these to the ticket?
Ability to customize the content on a page based off location. Especially important for strategy differences in content/brand between North America and Asia.
This is the Epic to capture the TBD IAM/CoSS integration plan
As much I love missy, we gotta give her a proper name! What are we called? I have a slight preference for Community Software. Since Community Support Software is too long. Community Support sounds like we do SUMO type work. CoSS is to cryptic. Or maybe something completely different?
The readme can use our working Strategic Vision from slide deck:
The Community Support Software, CoSS for short (previously VMS or MozNet), provides the tools needed for people to contribute to the issues* they care about through Mozilla. A simple, transparent, guided and personalized User Experience ensures that work is surfaced, strategic, done with clear accountability. It will have a near seamless experience with other Mozilla communication and collaboration tools.
Additionally, the CoSS facilitates and enhances the staff/volunteer relationship, allowing for staff or Volunteer Leaders to identify, recognize, and support people at a variety of levels and contribution types.
In 2017, we will create the start of a solution through iterative prototyping with local clubs. With the goal to build key functionality to solve programmatic needs in a way that is scalable for other teams.
Github Collaboration
Working with the student program at GitHub to find ways to collaborate
Mostly activity and challenge sharing
Possible cross-promotion and sharing students
GitHub
Most of our activities are hosted on GitHub so that we can measure our students in repositories
Eventually consider moving away from teachable to see if we can use github pages (like the open source leadership group uses) or another open source tool
I know @a-kilroy wants to be very intentional about the labels we use/create so that they can be used across multiple repos.
Here's what this repo has so far:
Here are a few other ideas:
cc @hannahkane since you probably have some thoughts?
An about/landing page will be the first section of the website we tackle. We should start gathering, synthesizing and editing copy for it.
We can start by dumping everything we think could be there into this doc. This won't be final copy in any way but will be a good exercise to start figuring out how we want to talk about 'clubs' in the new expanded sense, in a safe nonpublic space. But the real goal for this is to have something to start the page layout with and then eventually start editing it down.
We created a bunch of personas during our workweek. I will digitize what we have, complete them, and narrow them down to a few key ones. Will also check in with MoCo's persona specialist Reena(?).
MLN personas: https://drive.google.com/file/d/0B3b1KWRwjxtoMkpiTUsxTDY4ZTg/view
Personas from Amira:
All the personas from the workweek are now in this doc.
Since they were sorted by name, I was able to add the Berlin workweek users stories to the personas. But the Hawaii users stories are all all taped onto the large paper personas, @a-kilroy can you please sort and add them into the doc?
I remember there were a few personas that had a lot of the same users stories, could you also point out which ones those where?
Find websites that feature multiples events. Ideally, events should be reoccurring and happen all over the world. Websites can either integrate with existing platforms or have their own.
Goals:
Start a folder to consolidate all our images that we can then pull from for the website comps.
We usually fill out this design brief before starting a new project.
We don't necessarily have to fill in everything but we should at least identify:
Team meets to review findings and select a CMS to use for the Clubs Prototype
Find popular/viable django interface bolt-ons/etc that make working with Django easier from a user/admin point of view.
Evaluate selected django interface(s) from a UX perspective. Compare django to wordpress (UI, number of steps to complete a task…)
So far, https://www.django-cms.org/en/ looks like the best option, very Wordpress like.
Enhance Content functionality for the Clubs Prototype:
Preview public view
Photo uploader
Edit Copy
Initial suggestions from @jvallera on how she can help get user feedback:
This is the Epic for our website. Some example tickets associated with this but we should all jump in to edit them and add to them. In my mind the there are two paths, production and 'design/testing' so steps in a non waterfall timeline are: Install, wireframe, test wireframes, light visual design, content upload, refine design, integrations
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.