Knowledge Base discussions

What should we focus on for SUMO Day?

  1. SUMO Day is coming up on July 23rd. While there are a million things we can work on, we don't have time to squeeze them all into one day. What should we focus on next? Please limit your ideas to content-related projects, as we can't squeeze in code or software changes during SUMO Day.

    Help us decide by filling out this survey.

    Are you interested in joining a SUMO Day task force? We are looking for a group of 5-10 contributors who can take the lead in setting up "themes" or priorities for upcoming KB SUMO days. If you're interested, enter your SUMO name in the form above. You don't have to be present for every SUMO day (that's why we're looking for several contributors).

    SUMO Day is coming up on July 23rd. While there are a million things we can work on, we don't have time to squeeze them all into one day. What should we focus on next? Please limit your ideas to content-related projects, as we can't squeeze in code or software changes during SUMO Day. Help us decide by filling out [http://goo.gl/forms/pE5Vo2bXEA this survey]. '''Are you interested in joining a SUMO Day task force?''' We are looking for a group of 5-10 contributors who can take the lead in setting up "themes" or priorities for upcoming KB SUMO days. If you're interested, enter your SUMO name in the form above. You don't have to be present for every SUMO day (that's why we're looking for several contributors).

    Modified by Joni on

  2. Joni said

    SUMO Day is coming up on July 23rd. While there are a million things we can work on, we don't have time to squeeze them all into one day. What should we focus on next? Please limit your ideas to content-related projects, as we can't squeeze in code or software changes during SUMO Day. Help us decide by filling out this survey. Are you interested in joining a SUMO Day task force? We are looking for a group of 5-10 contributors who can take the lead in setting up "themes" or priorities for upcoming KB SUMO days. If you're interested, enter your SUMO name in the form above. You don't have to be present for every SUMO day (that's why we're looking for several contributors).

    Hi Joni

    The form above has some restriction. Please advice

    Michael.

    ''Joni [[#post-66017|said]]'' <blockquote> SUMO Day is coming up on July 23rd. While there are a million things we can work on, we don't have time to squeeze them all into one day. What should we focus on next? Please limit your ideas to content-related projects, as we can't squeeze in code or software changes during SUMO Day. Help us decide by filling out [https://docs.google.com/a/mozilla.com/forms/d/1uKdLhLnlFxPCwKm5JY_3g7Z8xer61ObMEUvcyVPaWHU/viewform?usp=send_form this survey]. '''Are you interested in joining a SUMO Day task force?''' We are looking for a group of 5-10 contributors who can take the lead in setting up "themes" or priorities for upcoming KB SUMO days. If you're interested, enter your SUMO name in the form above. You don't have to be present for every SUMO day (that's why we're looking for several contributors). </blockquote> Hi Joni The form above has some restriction. Please advice Michael.
  3. Joni said

    Help us decide by filling out this survey.

    The survey link gives me this message:

    You need permission This form can only be viewed by users in the owner's organization.

    ''Joni [[#post-66017|said]]'' <blockquote> Help us decide by filling out [https://docs.google.com/a/mozilla.com/forms/d/1uKdLhLnlFxPCwKm5JY_3g7Z8xer61ObMEUvcyVPaWHU/viewform?usp=send_form this survey]. </blockquote> The survey link gives me this message: ''You need permission'' ''This form can only be viewed by users in the owner's organization. ''
  4. AliceWyman said

    Joni said
    Help us decide by filling out this survey.

    The survey link gives me this message:

    You need permission This form can only be viewed by users in the owner's organization.

    +1

    Michael

    ''AliceWyman [[#post-66034|said]]'' <blockquote> ''Joni [[#post-66017|said]]'' <blockquote> Help us decide by filling out [https://docs.google.com/a/mozilla.com/forms/d/1uKdLhLnlFxPCwKm5JY_3g7Z8xer61ObMEUvcyVPaWHU/viewform?usp=send_form this survey]. </blockquote> The survey link gives me this message: ''You need permission'' ''This form can only be viewed by users in the owner's organization. '' </blockquote> +1 Michael
  5. Sorry about that. I didn't realize forms were restricted by default. I'll update the link. You should be able to access it now.

    Sorry about that. I didn't realize forms were restricted by default. I'll update the link. You should be able to access it now.
  6. It may help to have a primary and secondary task each sumo day so that as many users as possible, with differing experience levels my be included.

    Beginners may not be happy with or have the rights to review, but may find some needs changes easy enough to do.

    Fx OS will require use of the device or an emulator, and it would probably be good to have prior experience with FxOS so again it restricts the catchment of participants.

    Anyone could do the updating screenshots. But if not now then after a first Sumo day on screenshots the majority of requirements may be for Mac or Linux screenshots. Again that limits the contributors who would join in. We could add a thread in this forum, the off topic or other section to mention and assist with Linux installs given that Linux will run from a memory stick, CD ? etc

    My activity levels on Sumo vary widely, I don't mind throwing a few ideas into the ring, but others will be more active and able to commit the time and energy required.


    Off topic but what is the idea behind the stale & expiry columns and when and how will that be used  ?


    The first Sumo Day kb project should be learn to help with the KB. Link to the contributors help articles invite people to read them and try the KB. Maybe do practice writing, and edits, in allizom (stage). Try to ensure the importance of discussion and cooperation is understood and the L10n process is not overlooked.

    Otherwise people make changes but others undo them, or articles that do not need localisation are marked as such. Conversely urgent articles like maybe Pocket or FlashPlayer issues miss getting localised but are time sensitive for localisation if they are to be effective.

    It may help to have a primary and secondary task each sumo day so that as many users as possible, with differing experience levels my be included. Beginners may not be happy with or have the rights to review, but may find some needs changes easy enough to do. Fx OS will require use of the device or an emulator, and it would probably be good to have prior experience with FxOS so again it restricts the catchment of participants. Anyone could do the updating screenshots. But if not now then after a first Sumo day on screenshots the majority of requirements may be for Mac or Linux screenshots. Again that limits the contributors who would join in. We could add a thread in this forum, the off topic or other section to mention and assist with Linux installs given that Linux will run from a memory stick, CD ? etc My activity levels on Sumo vary widely, I don't mind throwing a few ideas into the ring, but others will be more active and able to commit the time and energy required. ------- Off topic but what is the idea behind the stale & expiry columns and when and how will that be used ? ----- The first Sumo Day kb project should be learn to help with the KB. Link to the contributors help articles invite people to read them and try the KB. Maybe do practice writing, and edits, in allizom (stage). Try to ensure the importance of discussion and cooperation is understood and the L10n process is not overlooked. Otherwise people make changes but others undo them, or articles that do not need localisation are marked as such. Conversely urgent articles like maybe Pocket or FlashPlayer issues miss getting localised but are time sensitive for localisation if they are to be effective.
  7. My 2 cents:

    For everyone, the focus should be the Need changes list. Reviewers should go through the Article discussion threads and look for anything that still may still need an update (like threads titled "Need screenshots" "Needs update", or "Inaccurate info") and edit the description of those articles to add them to the Need Changes list.

    For KB reviewers, another focus area should be the Unreviewed Changes list, sorted by Most Recent, and work from the bottom to clear out the old pending revisions (many are over 6 months old some are over a year old). By the way, the Article review guidelines article still needs review and update by Joni.

    My 2 cents: For everyone, the focus should be the [https://support.mozilla.org/en-US/contributors/need-changes Need changes] list. Reviewers should go through the [https://support.mozilla.org/en-US/kb/all/discussions Article discussion threads] and look for anything that still may still need an update (like threads titled "Need screenshots" "Needs update", or "Inaccurate info") and edit the description of those articles to add them to the Need Changes list. For KB reviewers, another focus area should be the [https://support.mozilla.org/en-US/contributors/unreviewed Unreviewed Changes] list, sorted by Most Recent, and work from the bottom to clear out the old pending revisions (many are over 6 months old some are over a year old). By the way, the [[Article review guidelines]] article still needs review and update by Joni.

    Modified by AliceWyman on

  8. Thanks for the feedback, John99 and Alice.

    We'll definitely have a SUMO day for newcomers, but at this point, I'm trying to figure out how to make our training materials easier to digest. I'm working with two new contributors right now and they're still giving me feedback. We'll also work with technical writing instructors later this quarter to develop quick reference materials.

    Yes, we can set multiple projects for SUMO Day, but we should limit them to 2 or 3, depending on the complexity. The past two or three SUMO days, we set out with several different projects, and that got a bit overwhelming for both contributors and moderators.

    There's a tie in the survey results right now, so please encourage others to put in their feedback.

    As for the SUMO Day task force (maybe we should call it a "Planning Team"), you don't have to be present during SUMO Day, but you'd help prepare the community for SUMO day. I'm leaving this vague because I want to empower the planning team to define its roles, processes and even a team name.

    Thanks for the feedback, John99 and Alice. We'll definitely have a SUMO day for newcomers, but at this point, I'm trying to figure out how to make our training materials easier to digest. I'm working with two new contributors right now and they're still giving me feedback. We'll also work with technical writing instructors later this quarter to develop quick reference materials. Yes, we can set multiple projects for SUMO Day, but we should limit them to 2 or 3, depending on the complexity. The past two or three SUMO days, we set out with several different projects, and that got a bit overwhelming for both contributors and moderators. There's a tie in the survey results right now, so please encourage others to put in their feedback. As for the SUMO Day task force (maybe we should call it a "Planning Team"), you don't have to be present during SUMO Day, but you'd help prepare the community for SUMO day. I'm leaving this vague because I want to empower the planning team to define its roles, processes and even a team name.
  9. I agree on the need to focus on Need changes as there so many that are pending. Can i help with this? for the en-US.AliceWyman said

    My 2 cents: For everyone, the focus should be the Need changes list. Reviewers should go through the Article discussion threads and look for anything that still may still need an update (like threads titled "Need screenshots" "Needs update", or "Inaccurate info") and edit the description of those articles to add them to the Need Changes list. For KB reviewers, another focus area should be the Unreviewed Changes list, sorted by Most Recent, and work from the bottom to clear out the old pending revisions (many are over 6 months old some are over a year old). By the way, the Article review guidelines article still needs review and update by Joni.

    I agree on the need to focus on Need changes as there so many that are pending. Can i help with this? for the en-US.

    I agree on the need to focus on [https://support.mozilla.org/en-US/contributors/need-changes Need changes] as there so many that are pending. Can i help with this? for the en-US.''AliceWyman [[#post-66049|said]]'' <blockquote> My 2 cents: For everyone, the focus should be the [https://support.mozilla.org/en-US/contributors/need-changes Need changes] list. Reviewers should go through the [https://support.mozilla.org/en-US/kb/all/discussions Article discussion threads] and look for anything that still may still need an update (like threads titled "Need screenshots" "Needs update", or "Inaccurate info") and edit the description of those articles to add them to the Need Changes list. For KB reviewers, another focus area should be the [https://support.mozilla.org/en-US/contributors/unreviewed Unreviewed Changes] list, sorted by Most Recent, and work from the bottom to clear out the old pending revisions (many are over 6 months old some are over a year old). By the way, the [[Article review guidelines]] article still needs review and update by Joni. </blockquote> I agree on the need to focus on [https://support.mozilla.org/en-US/contributors/need-changes Need changes] as there so many that are pending. Can i help with this? for the en-US.
  10. Please Jump in wherever you can help it will be welcome, although with all your other Sumo task I don't know where you get the time from !

    There is always going to be work to do. A lot of the work is in maintaining and updating current KB articles. The changes then sometimes need localisation.


    At one time a few years ago we had to archive some of the less helpful articles because the cost of maintining so many Articles was unsustainable.

    I wonder if we are heading in that direction again if we continue with a policy of more and more short articles. It strikes me that by deliberately having very many short articles that makes our maintenance tasks harder.

    We are probably updating only some of the articles and not even identifying some of the others in need of an update. Any single change or update requirement will relate to more articles. I have mentioned before using templates more often could help streamline updating, but template control and use is not simple itself.

    It is already hard to understand what we have, and which of our hundreds of articles are in need of update.

    I must of course mention we have had the "What links here" feature for a while now. It is mentioned in the little known Article Research upcoming changes to Firefox written as recently as 2013 and notably that article is not linked from other contributors articles.

    Please Jump in wherever you can help it will be welcome, although with all your other Sumo task I don't know where you get the time from ! There is always going to be work to do. A lot of the work is in maintaining and updating current KB articles. The changes then sometimes need localisation. --------- At one time a few years ago we had to archive some of the less helpful articles because the cost of maintining so many Articles was unsustainable. I wonder if we are heading in that direction again if we continue with a policy of more and more short articles. It strikes me that by deliberately having very many short articles that makes our maintenance tasks harder. We are probably updating only some of the articles and not even identifying some of the others in need of an update. Any single change or update requirement will relate to more articles. I have mentioned before using templates more often could help streamline updating, but template control and use is not simple itself. It is already hard to understand what we have, and which of our hundreds of articles are in need of update. I must of course mention we have had the ''"What links here"'' feature for a while now. It is mentioned in the little known Article [[Research upcoming changes to Firefox]] written as recently as 2013 and notably that article is not linked from other contributors articles.