Frequently Asked Questions (Portal Edition) - FAQ

What is currently on Activate that won't be on the Portal?

99% of content will be nearly identical on the portal as it is on Activate. As part of transitioning activate to the portal we are reviewing all of the activities and will be updating ones that have out of date information, removing activities that are no longer relevant, and adding contribution activities that are missing. All of the current, upcoming and past campaigns will be present on the Portal. The mailing list will stay the same. The portal is not localizeable right now but will be by July, 2020.

Will the portal integrate with Mozillians?

This portal will integrate with Mozilla’s People Directory in H2 which will replace Mozillians.org.

Will the portal integrate with Mozilla's People Directory?

We are working to build an integration with Mozilla’s People Directory (people.mozilla.org) for H2.

Will the portal be available in other languages?

We are prioritizing localization and the site will be localizeable in Version 2 which is scheduled for July, 2020.

What is a Mozilla Community Group?

Mozilla Community Groups are groups of people who meet regularly and work collaboratively to advance mozilla’s mission. Anyone who is working to advance Mozilla’s mission can start a Community Group. Groups can meet in-person or virtually and can be organized around a region, contribution area, identity, or interest. All groups must respect and adhere to the community participation guidelines and naming guidelines below. Only groups that have been vetted by a community manager will appear as “verified” groups.

Can there be multiple groups from the same country, city or campus?

Absolutely! Everyone has the freedom to create a group that reflects their diverse set of interests and identities while promoting inclusivity and Mozilla’s mission. We welcome multiple groups from the same countries, cities and campuses assuming they meet the requirements for validity.

Mozilla encourages a multiplicity of groups to pursue our shared mission and will not acknowledge any hierarchy between groups.

When setting up a new group the creator should consider whether a group already exist with the same audience and purpose. Groups that have the exact same focus and mandate should be open to merging or revise their title or description to be more descriptive of their differences.

What if two groups want to use the same name?

The system will not allow multiple groups with the same name in the portal and where two groups wish to use the same name the following guidelines will be applied and both groups may be encouraged to find names that are informative and help new and established community members identify the groups that are most relevant to them.

Group names should strive to meet the following criteria:

  1. Reduce confusion - Names should be descriptive and accurately reflect the focus of the group. Groups that have the exact same focus and mandate may be asked to merge or revise their title or description to be more descriptive.
  2. Avoid exclusivity - Using more descriptive titles helps avoid the appearance that a particular group exclusively represents the entire topic or area throughout the movement. Groups may overlap with other groups i.e. French Localizers in Quebec City and MozFR but people are never obligated to join a group to participate within a focus area or region. Mozilla encourages names that allow a multiplicity of groups to pursue our shared mission and will not acknowledge any hierarchy between groups.
What is a “verified” group?

Anyone can add a group to the Community Portal however after 3 months, all groups will be reviewed by a Community Manager. Once a community manager has reviewed and approved a group a “verified” mark will appear by the group title (Note: we might change the word “verified”, open to suggestions!).

Groups that fail to meet the criteria at the time of the review may be asked to update their group profile, or be removed from the portal. Validated groups will be reviewed on an annual basis to ensure they continue to uphold the guidelines and criteria.

How does a group become verified

In order for a group to be verified, at the time of review (3+ months after creation) it must meet the following criteria:

  • Follow the CPG and Leadership Principles
  • Have a completed profile with all of the relevant information for the group including ways for newcomers to get involved.
  • Have at least 5 active members.
  • Have held at least 1 event registered in the portal.
  • Have 2 group contacts.

Community managers will regularly review new groups that have been active for 3+ months.

What does it mean if a group is not verified:

There are two reasons that a group may not be validated in the portal.

  1. They are new and have not yet been reviewed by a community manager. (Reviews only begin after 3 months of being in the portal).
  2. They are working with a community manager to create the changes required to become validated.
How does a group remain “verified”:

Every year groups will be re-verified by community managers. At the time of review, groups must meet all of the criteria above and also demonstrate that the group contacts have changed since the previous year.

What is a group contact?

Group contacts are the people who are responsible for maintaining the group’s page on the portal and liaising, on behalf of the group, with Mozilla staff. There must always be 2 group contacts and they must change every year.

What do group contacts do?
  • Maintain the content and activity of the group page
  • Answer questions from community managers during the “verification” process

In order to be validated, group contacts must be responsive and able to answer and address issues on the group page. We recommend that group contacts are people who feel comfortable communicating in English. And have a good understanding of what is happening inside their community.

Note that group contacts do not have to correspond to governance roles inside the community. Communities are free to create their own internal structures and governance though all leadership roles should follow the Volunteer Leadership Principles.

Updated: January 20th, 2020.

6 Likes
  • Q: Will this replace Mozillians?
  • A: No! Ultimately this platform will pull profiles from Mozillians.
3 Likes

Is there an API of any kind being planned?

2 Likes

Heya :wave:

Do you have any specific resources in mind you’d like to access / modify through an API? The general idea of this project is consolation and having a clear point of entry into contributing. Which is not to say that we won’t miss use cases and that we’re anticipating every future idea. Hence we’re curious to hear your thoughts to find out if & how we can accomodate.

Hello, will the portal be available in Spanish from the beginning?

Hey Gery!

Unfortunately the portal will launch as a V1 in English but our goal is to have the platform localizable (in pontoon) in V2.

Lucy

1 Like

Thank you very much for your response Lucy.
Do you have any tentative dates for V2?

Regards! :grinning::beers:

Probably launch a V2 in Q2 (summer), 2020.

1 Like

I understand again thank you very much,
Regards!! :grinning::beers:

If the goal of the new Community Portal is to bring everyone under one roof and limit the number of accounts that a volunteer needs to keep track of, wouldn’t it be ideal to eliminate Mozillians in favour of this new platform? Especially considering that Mozillians is a pretty outdated website. It doesn’t even use the updated Mozilla branding.

It seems like the Community Portal will have nearly the same data as Mozillians. It just seems to me like the Community Portal could simply be moved to the Mozillians domain as a move advanced version of that platform. Maybe I’m wrong though.

Hey @ComputerWhiz so one thing is Mozillians is definitely going to be updated and will contain anyone whose ever engaged with Mozilla. But it will be more of a directory of people profiles from all around Mozilla. From there, you’ll be able to opt into where there profile shows up I.e. Common Voice contributors might not want to be on the Community Portal but might want to be able to use their profile to access discourse.

Meanwhile the Community Portal will be a place for people who want to do many things to support Mozilla can find events, groups, and people.

1 Like

Hello Lucy! :wave:

Will the API be available and open for all? If no, why not?

Currently we don’t have an API, I’ll point to a previous question about this

1 Like

We were actually planning to release a Reps App but since the Community is now moving to a common Community Portal; we are inclined to make an app in Flutter from the Community, by the Community.

Which is why I asked the following question:

Thank you. :slight_smile:

Can you elaborate about this “app”?

It would be great if there is place to read more so we can understand your need.

Thanks!

Sure, yeah!

MozFam has created a Reps Mobile Application. An app that uses API from the Reps App to pull the data and anyone will be check if there are any events around them or if there is a Rep around them to help them organize an event.

Once the internal work was done, we were to open the process of Contributing and downloading for all and it almost done when the Community Portal was announced. We hadn’t seen it coming but this was something the Community Members had put a lot of effort into. We were looking forward to using the same layout of the App and access the Portal data through the API.

Here are a few screenshots:

This is what we were planning, and the initiative was by @obitodarky and Ayush Bherwani. These are our Flutter Heads, who had the idea of building this App and make it all more accessible. We all chipped in our bits to help our beloved Community members out.

If you have a list of requirements we can check with what we are planning to deliver in v1 and v2 of the portal. The mobile version of the site might solve some of your current needs.

1 Like

Suggestions: “Foxed”, “Foxified”, “Mozilla-fied”, “Activated”

1 Like

@leo @lucyeoh can the community portal use existing discourse categories which was used by the community or group before, instead of creating a new sub category in the community portal section