QA/QMO/QMO.next/Meeting Notes

From MozillaWiki
< QA‎ | QMO‎ | QMO.next
Jump to: navigation, search

June 1

status update:

  • Craig: videos put onto home page; tested webpage compatibility
  • Aakash: videos uploaded to webdav;

Anything left?:

  • Craig: work on author guide
  • Aakash: go live! we be done, son.

Post-Mortem: - Issues: Going back-and-forth with IT on getting set up on subversion in the beginning; video, magpie rss, upload limit. Overall, fine, but just some nits to remember for future releases.


May 28

status updates:

  • craig: icons created, browser technologies and subgroups created, favicon uploaded,
  • aakash: filed bug 568928 to get video size permissions uploaded

next steps:

  • craig: change groups to teams, commit bug fixes, hack for ie6 compatibility
  • aakash: upload ogv format video once IT has fixed bug 568928


May 18

status update:

  • craig: bug fixes completed, wrong approach to community (will get done tonight), related docs, completed two icons,
  • aakash: info set up with shyam, community feeds list finalized

things to do:

  • craig: filtering finished 5/18 evening, related docs (on groups and indiv docs pages) up 5/18 afternoon, finish up icons, tweak some styles, start testing
  • aakash: follow-up with shyam, follow-up with matt for graphic representation of qa services (and any other groups), get people ready to update content

May 13

Feedback:

  • I sent out e-mails to get feeds, still waiting on responses
  • filter twitter so only tweets with #qmo is picked up
  • extend out content when there's no content in sidebar?
  • related docs on groups?
  • Bugs
    • multiple hops on social networking icons
    • contributors on docs page
    • upcoming events on community page
    • getting started on event details

DONE:

  • Tweets and Blogposts Syndicated (COMMUNITY DONE!)
  • Figure out filtering for community page

Todo:

  • Craig: styling on sidebars, investigate social networking, put related docs widget on groups pages, bug fixes (remove sidebar widgets)
  • Aakash: talk to webdev

May 11

plan for community page:

  1. get blog posts syndicated to our community page
  2. get tweets syndicated to our community page
  3. have them both working together in a everything
  4. have community page segregate tweets,

feedback:

  • default to event list
    • easy to do as an option on the plugin
  • differentiate docs titles on each major section
  • add styling backgrounds/borders/etc. to get involved on home page and sidebar snippets in general to make them more visible
  • group titles smaller than headers in group page content


status:

  • craig: finishing up events, diving into community
    • need to do: get docs related to group working, get community working, look into feedback and work on styling and bugs
    • events plugin can't do associated events for now, will talk to developer to get it working
  • aakash:
    • look into rss feed syndication via filtering
    • need to do: remove commenting per page by default, find out how to incorporate video (i.e. flash or html 5?), get list of community members category feeds, talk to webdev about getting site setup on subversion (ala rock your firefox) (craigcook@gmail.com permissions)

notables/take-aways:

  • get community page up and running
  • timeline to staging for thurs/fri
  • set up in subversion, copy of wp-content folder. only thing that gets manage in subversion is theme and content. wordpress doesn't get changed

May 6

done: - plugin for event, recent blog posts for groups, upcoming events on home page - content for docs and groups merged - docs template done - groups template done

need to do: - recent blog posts per category basis - upcoming events snippets - remove administration links - community page - remove commenting per page by default (aakash) - look into rss feed syndication via filtering (aakash) - find out how to incorporate video (i.e. flash or html 5?) (aakash)

May 3

Facebook Page: http://www.facebook.com/pages/Mozilla-QA/122167964300 Twitter Account: http://twitter.com/mozillaqa

Here's some links for the getting started snippet:

Contact us on IRC: http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa Read our Newsgroup: http://groups.google.com/group/mozilla.dev.quality/


Here's some take-aways from our chat:

Home page: - blue links after links clicked on getting started - change sticky post to static content only for home page - accomodate flash video in static content - icons for groups

Planet QMO: - get the syndicated blog posts as a priority - getting twitter posts in is not a blocker

Groups/Docs: - both consist of pages rather than blog posts

April 13

https://wiki.mozilla.org/QA/QMO/QMO.next/ImplementationNotes

March 4

What went well and should be repeated in future versions?

  • domain destination, place to get information about our qa community,
  • communications hub to the community
    • mediums: blogs, forums
    • content: events
  • communications aggregate to planet and other places
  • documentation is valuable
  • events snippet
  • spam filters
  • navbar is concise and intuitive
  • speed improvements
  • events calendar

What went wrong and should be avoided in future versions?

  • lack of customizibility for any user
  • terribly difficult to administrate and update content quickly
  • lack of interactive content
  • community can't interact with each other
  • community interaction with the qa team
  • execution of initiatives for the website
  • dedicated resource to manage the website
  • deemed as a side project by mozQA and community, needed to be an integral part of communications and interaction with community

What are possible solutions to what went wrong?

  • more interactions: attract based on features (not milestones), try contests, task-based volunteering
  • document portal that's more in your face
    • tag cloud, categories, better hierarchy, integration with communications (blog posts, forum topics, etc.)
  • NO MORE DRUPAL
  • We should embed/incorporate a ShareThis widget
  • hierarchy: admins, write content users and interactors with content
  • community hub: twitter feed for #mozquality, Fade In/Fade Out ticker for latest feedback submitted on main home page siphoned from reporter.mozilla.org, latest bugs filed to fx and fennec products, Planet QMO, rss feed buttons/links

What would we like to add?

  • We should embed/incorporate a ShareThis widget
  • Discoverable links to our social networks
  • Proper FAQ where people can file an enhancement bug to BMO

Inspiration

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/QMO/QMO.next/Meeting_Notes&oldid=231325"