Day 1: 9th July 2016

Session by Haiyya – Stories of self

The session was based on stories of self as how we can inspire, motivate other Mozillians by describing our story. Some quotes :

• Great movement and great innovations need great leaders. Great leaders need great stories.
• Your story will reflect on your leadership that will strengthen your community.

Mozilla Future Goals

• Firefox / Content Graph / Test Pilot
  • Context Graph is a recommendation system for the web.
  • Searching a content in the search bar won’t just limit the results based on the browsing history but will also seek documents, links corresponding to the search.
  • Activity stream is the first Context Graph feature, currently available in Test Pilot. It will evolve into a search engine which will also help the users discover places on the web he/she has never seen. It would be available for both desktop and mobile platforms.

• Future of Platform / Servo
  • Mozilla wants to build a next generation engine which would be a tool of choice of browser and app developers outside of Mozilla.
  • - Mozilla needs a complete platform upon which a fully featured browser engine could be built and can influence the development of the future of the Open Internet.
  • Gecko needs to be solid and stable and to make it so would be a slow development down to a crawl.
  • On the other hand, Servo is under trails and it would be tremendously valuable and critical in future. It has validated many architectural changes, has innovated the web and has injected new ideas and code.
  • Completeness of an engine like Gecko + Performance and Responsiveness wins of architecture in Servo
  • Servo is written in Rust. Rust provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.
  • Rust is one of the key focus areas.

• Connected Devices
  • Mozilla wants to create open and accessible platforms that will allow individuals, businesses and others to benefit from IoT.
  • IoT leads the way to the next phase of the Internet.
  • The IoT ideas that align with Mozilla’s goals would be selected and their problem statement and solutions would be worked on. Later, the prototypes of such statements would be built and would be tested in the market. Depending on the market response, the production of such devices would begin.

• Mozilla Issue Agenda and Advocacy

Mozilla has identified 5 issues that must be tackled in the current era, to build an Open Internet:

• Mozilla Advocacy Engine:
  • Open Privacy and Security
  • Open innovation
  • Decentralization
  • Web-literacy
  • Digital inclusion

A global movement to build and protect the next wave of openness and opportunity online.

• Near-term goals:
  • Online privacy
  • Encryption
• Mid-term goals:
  • Privacy, inclusion literacy
  • Large campaign
• Long-term goals:
  • Behaviour change and policy change
• Impact:
  • Conscious choice to build and protect Open Internet
  • Products, policies and laws in support of the Open Internet

• Mozilla Leadership Network

A global community, platform and resource to support and advance the work of leaders to protect the internet.

• MLN :
  • Open practices to shape the web in new ways
  • Increase influence on privacy, digital inclusion and web literacy
  • Improve their skills and experience as leaders

• Thematic hubs :
  • Learning
  • Science
  • Internet policy and advocacy
  • Women and web literacy
  • Internet of Things

• MLN audience :
  • Champions
  • Executives
  • Professionals
  • Emerging Leaders
  • Young Leaders

• Impact:
  • Network alignment
  • Network connectivity
  • Network size
  • Member influence/reach

Discussion On Community Restructure

In this session, the attendees were divided in groups and were asked to list points/suggestions as how the Mozilla India structure should be.

Day 2: 10th July 2016

Mozilla India Community Strategies

The attendees were divided in various groups and were asked to derive strategies around the following blocks:

• Training and Workshops
• Conflict Resolution
• Team building and Recognition
• Planning and community restructure
• Communication

The motive of this session was to take into consideration a broader perspective about the functioning of the Mozilla India community and derive strategies around them.

August Meetup

• August 26-28, 2016
• Pune

Draft goals/focus areas for the meetup

• Develop a strategy, direction and plan for the future of the community
• Re-structure the Mozilla India community -- structures and processes
• Increase the leadership/mobilizing skills of the attendees (and develop strong onboarding programs for new community members)
• Improve communication processes and tools, and transparency
• Build strong teams
• Build strong recognition practices
• Create accountability systems and a code of conduct
• Build a plan for increasing diversity and inclusive practice across the community

Working groups for planning the August meetup

• Communication
  • Members:
    • Biraj, Ashish, Siddhartha, Shaguftha
  • Role :
    • Share updates about the meetup to the community
    • Work closely with the Social Media Team

• Logistics
  • Members :
    • Prathamesh, Chandrakant, Sayak
  • Role:
    • To make local logistics arrangements like booking hotel, travel, stationary.

• Regional Coordination + Invitations
  • Members:
    • Mehul, Akhil, Viswaprasath
  • Role:
    • Keep a follow-up with the regional members
    • Work closely on the invitations with the Indian Reps Council and the Participation Team

• Staff/Functional Coordination
  • Members:
    • Sayak, Anivar
  • Role:
    • To work closely with the Mozilla staff and share status updates of the meetup

• Documentation
  • Members:
    • Ankit, Kailas, Harsha
  • Role:
    • To document the entire meetup

• Content/Facilitation
  • Members:
    • Mayur, Anup, Priyanka, Meghraj, Diwanshi
  • Role:
    • Work on agenda and broadcast the content which would be facilitated for the meetup

• Strategy/Structure for Mozilla India
  • Members :
    • Deb, Vnisha, Prathamesh, Vineel, George
  • Role:
    • Draft an email which will call for proposals/suggestions
    • Make the proposals/suggestions public and open for the community to review and comment
    • Process, analyze and integrate the suggestions
    • Declare the finalized structure