GithubHelp home page GithubHelp logo

sumo's Introduction

Mozilla Sumo

This repository is used to track anything related to the platform that powers SuMo and any other projects the team might be working on. Kitsune is the platform that powers SuMo (support.mozilla.org).

Engineering Board

We are working mostly with projects. A project signifies the team's focus for a period of time. Usually there are one or two active projects at a time. A project is defined as a standalone chunk of work for a specific property. Recent examples of projects were the redesign of the SUMO site, integrating Firefox Accounts etc.

As a rule of thumb, a project is defined as work that requires more than one tasks to be completed and takes more than 3 working days. Anything that doesn't fall in the project category is a standalone issue. In most of the cases, these issues are bugs.

The board will only display either standalone issues or the issues of the active project(s) in order to avoid clutter.

GitHub Milestones

We are using milestones to better organize the work that a project needs in order to be completed. A milestone is a concrete chunk of work and each project can have more than one milestones.

An example of the above structure is:

  • Site Redesign - project
    • create designs - Milestone1
      • GH issue
      • GH issue
      • GH issue
    • implement designs - Milestone2
      • GH issue
      • GH issue
      • GH issue

Not active projects may have a placeholder milestone in the form of a Inbox if there are already existing issues in board. This is purely for organization reasons.

Labels

Labels are used to easily distinguish cards that have them attached. We should keep them to the minimum in order for the cards that hold them to easily stand out. We are not using priority labels. Priority is determined by the position of a card in the board.

We have the following labels to highlight an issue:

  • Bug: Something is not working properly.

    Any issue that has the bug label should also be assigned to the KTLO GitHub milestone regardless of the severity of the bug.

  • Pr-welcome: Tasks friendly to new contributors. These tasks are only closed when they are done.

  • Project specific labels:

    • oidc
    • other

    If an issue does not have a label then it belongs to kitsune.

Columns

Triage

Default column for incoming issues. Only holds issues that have not been proccessed yet.

Backlog column

Our Parking Lot. Issues that are valid but not yet an immediate priority.

Next Items

Hold the tasks of individual active milestone(s) or standalone tickets that will be worked on within a few weeks.

Projects, Epics and Blocked Items

This column holds all the tasks that require collaboration with project stakeholders or are blocked for any reason. It is also a placeholder for Project/Epic cards. Single cards that hold all the information relevant to a project, links to documentation and its milestones.

In Progress column

Specific tasks that are actively worked on by the team.

A card is moved to the next column only when a PR is opened.

Review column

Anything that waits for a review. An issue is moved to the next column only when merged.

QA column

Everything that is already released to the testing environment and is ready to go under QA.

If an issue passes the QA process, it will be moved to the next column. Otherwise it will be moved back to the In Progress column.

If new issues are opened from the QA processes, they should go under the Next Items column without anyone assigned.

Ready for Release column

Acts as a parking lot. This column is suitable for anything that successfully passed QA but is not yet released to production.

An effort should be put to keep this column short.

Done column

That's all!

Release notes

After each release, we are posting a summary of what happened in Discourse.

sumo's People

Contributors

akatsoulas avatar emilghittasv avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

sumo's Issues

[Epic] Issues in user experience from paid products to Support.mozilla.org

Today:

User open VPN
-> settings
-> get Help
-> Help & Support --> Links to https://support.mozilla.org/en-US/products/firefox-private-network-vpn
-> User can't see contact us as user is not logged in
-> User goes to log in, is then sent to profile page instead of back to page where user logged in from.

Interim solution:
User open VPN
-> settings
-> get Help
-> Help & Support --> Links to https://support.mozilla.org/en-US/products/firefox-private-network-vpn
-> user logs in
-> User stays on https://support.mozilla.org/en-US/products/firefox-private-network-vpn

Ideal solution:
User open VPN
-> settings
-> get Help
-> Help & Support --> Links to https://support.mozilla.org/en-US/products/firefox-private-network-vpn
User is logged automaticallu and can see Contact Us.

cc @akatsoulas @jess-cook03 @madasan

The "Download Firefox" button appears even though the Firefox browser is used, on iPad device

STR:

Prerequisites:
Open the Firefox browser in RDM mode. Menu -> Web Developer -> select Responsive Desing Mode -> select iPad device

STR:

  1. Go to Support Mozilla page
  2. Pick a product from the "Pick your product" section
  3. Click on "Home" button

ER: You are redirected on the Mozilla Support homepage and you don't see any "Download Firefox" button
AR: You are redirected on the Mozilla Support homepage and you see the "Download Firefox" button even though you are using the Firefox browser.

Please see the screen recording: https://streamable.com/ohj88

NOTE: It doesn't meeter what product you choose to form the "Pick your product" section

Remove gulp dependency

Currently we are trying to refactor our tooling towards a direction that npm will take care all the static assets building.

Let's remove gulp to simplify our tooling.

[webcontent] Browser recognition is off

Site with issue and any steps to reproduce

Browse page "How to clear browsing history in Firefox Preview" https://support.mozilla.org/en-US/kb/how-clear-browsing-history-firefox-preview using Firefox Preview complains me using older mobile browser. In other words that page is not able recognize I am using Firefox preview -browser.

https://pbs.twimg.com/media/EHGJyLZWwAAEWGC?format=jpg&name=4096x4096
https://twitter.com/firefox/status/1186207598565044224

Expected behavior

Actual behavior

Does toggling Tracking Protection fix the issue? (Press the lock icon in the toolbar while on the site to see toggle)

no

Can you reproduce in Firefox for Android?

Have not tested this.

Can you reproduce in Chrome (or other non-Mozilla browser)?

Have not tested this.

Device information

Android device: Samsung S8
Fenix version: 2.1.0, build 12821601

History

Originally reported: mozilla-mobile/fenix#6175
Re-reported by @darkwing : mdn/kuma#6100

Remove django-mobility and mobile templates

Kitsune is using libraries and templates specifically targeting mobile devices. When the redesign is completely we should remove all the relevant to the mobile experience code.

Update or Remove link to Troubleshooting XPI

I think this is obsolete:

https://github.com/mozilla/kitsune/blob/master/kitsune/settings.py#L1042

It is referenced in a macro here:

https://github.com/mozilla/kitsune/blob/master/kitsune/questions/jinja2/questions/includes/aaq_macros.html#L177

The macro is referenced here:

https://github.com/mozilla/kitsune/blob/master/kitsune/questions/jinja2/questions/includes/question_editing_frame.html#L86

If a user encounters this broken link, they lose their work in the AAQ flow, so they get a terrible experience.

Odd thing is, I don't know where this would be shown because going in directly via

https://support.mozilla.org/questions/new/desktop/fix-problems

leads to a page with a "Share Data" button instead of an "Add automatically" button.

Noindex Administration article showing up in search

Steps to reproduce:

  1. Go to google.com.
  2. Perform a search for "Firefox Accounts change email"
  3. Go to the second page of search results.

Expected result:
-https://support.mozilla.org/en-US/kb/firefox-accounts-mozilla-support-faq shouldn't appear in search results because it's in the Admin category and says "noindex" in the source.

Actual result:
https://support.mozilla.org/en-US/kb/firefox-accounts-mozilla-support-faq is showing up on the second page of search.

Fix Firefox Preview detection

Summary
First reported here:

mozilla-mobile/fenix#6175

It seems kumascript (?) is incorrectly detecting Fennec instead of Firefox Preview.

Steps To Reproduce (STR)
How can we reproduce the problem?

Open Firefox Preview (repo here: https://github.com/mozilla-mobile/fenix)
Go to https://support.mozilla.org/en-US/kb/how-clear-browsing-history-firefox-preview
Actual behavior
You see a block saying that the user is using an old version of Firefox Mobile

Expected behavior
No message.

The Log in/ Sign up button label is displayed incorrectly.

STR:

Prerequisites: You don't need to be logged in.

  1. Go to Mozilla Support page
  2. Resize the browser window, shrink it.

ER: The Log in/ Sign up button label is displayed correctly.
AR: The Log in/ Sign up button label is displayed incorrectly.
Screenshot 2019-12-12 at 17 36 59

CMS/Database hookups

  • On the homepage and product pages, "Featured Articles and Threads" needs hooked up to real data
  • On the homepage and product pages, the 'need more help' and 'join our community' callouts are hard-coded HTML. Those may need to be wired to the CMS to give editors access.
  • In the footer and navigation, there are a handful of #TODO links that didn't have parallels that I could find on the live site.
  • "Popular Searches" under the search box need actual links.

Remove CSS related bundles from django pipeline

As part of moving our frontend tooling towards a direction where npm is responsible for building our static assets let's remove all the CSS bundles from the settings. That involves:

  • Cleaning up settings
  • Cleanup references to CSS files built by pipeline

The error message for fields is not descriptive enough when editing a profile.

[Precondition]:
Log in via FxA

[STR]:
1.Go to Edit my profile section
2.Fill the Facebook URL field (e.g. https://www.facebook.com/)
3.Click "Update my profile" button
4.Scroll the page up/down

[Expected result]:
The field should be marked with red and a descriptive message should be displayed
The error message should not be scrolled up/down

[Actual result]:
"Please match the requested format" message is displayed without indicating which field
The changes are not saved
The error message is scrolled up/down
https://drive.google.com/file/d/1kUbmoPN1Yvgr43F0tZrZffO1oDWsS5At/view

[Note]:
The issue is not reproducible if the field is filled with the following format: e.g. https://www.facebook.com/username

@mcranston18

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.