The document outlines the agenda for a ManageIQ design summit, including discussions around the community status, ways to collaborate, and licensing. It provides details on community members and channels for collaboration such as Gitter, forums, and mailing lists. It also notes that ManageIQ has transitioned to using the Apache License 2.0 to be more inclusive of potential contributors and users.

1. Community
ManageIQ Design Summit June 2016

2. Agenda
People
Status of the community
Ways to collaborate
Channels for collaboration
Licensing
Where do you want it to go?

3. People
You can find a longer list of people here
https://github.com/orgs/ManageIQ/people
Carol Chen (cybette)
Community Development
Sergio Ocón (sergioocon)
Customer Driven Innovation
Oleg Barenboim (chessbyte)
Chess master

4. Status of the Community
Website (Documentation)
Community members
Events
Meetups
Social Media
Blog
TigerIQ.co

5. Ways to collaborate
Write:
Tutorials / articles
Documentation
Developer docs
Develop:
Bug triage
Rails / AngularJS
Dev environments
Design:
Artwork and designs
Usability
Use cases
Translators:
Develop
Translate
Ambassadors:
Represent
Promote / Media
Recruit
Mentoring
Web:
Blog posts
Website update
Images by Fedora Project
http://whatcanidoforfedora.org/
Package:
Policies
Workflows
Reports
Depot
QA:
Test
Rspec

6. Channels for collaboration
Gitter https://gitter.im/ManageIQ/manageiq
Talk (forum) http://talk.manageiq.org/
IRC
Google+ Communities?
https://plus.google.com/communities/115645322794739557548
Mailing lists?

7. License news
With the merging of PR 7481 and PR 7629, ManageIQ has transitioned to use the
Apache License 2.0 exclusively (http://www.apache.org/licenses/).
The Apache License 2.0 currently enjoys widest acceptance among the
businesses and organizations that we anticipate will be interested in using
and contributing to ManageIQ
Permissive open source licenses are also popular in the Ruby and Ruby on
Rails communities
Apache vs. MIT: explicitness around grants of patent rights
Permissive: All existing and potential community members enjoy equal status
from a legal perspective.
Used by other open source projects related - i.e. OpenStack

8. Where do you want it
to go?