BMO/Meetings/2013-07-09

From MozillaWiki
< BMO‎ | Meetings
Jump to: navigation, search
  • lpsolit stepping down from bugzilla project but says he will still do QA stuff. He doesn't want to do the product managing and approvals.
  • discussion: glob, dkl, gerv, simon, liz, mcote (andre) (justdave)
  • need daily bug triage, approvals, releases aren't a big problem but we need overall direction and resources/time
  • core codebase will diverge more and more. we need to move more frequently than upstream, BMO is limited in what we can do with extensions.
  • why? not enough hooks? improve caching? 5.0 will only have request cacheing
  • we can't do it upstream b/c we don't have time
  • there are many things specific to bmo that we can't push upstream

bugzilla development is driven currently by dkl and glob being paid to work on bmo. simon paid to work on bugzilla for redhat. not many people are submitting patches.

  • gerv suggests that mozilla should commit resources to maintain bugzilla upstream as the base code rather than effectively forking bmo. glob and mcote and dkl assert that they have to have bmo as their priority. We have a brief but lively discussion of whether Bugzilla is "a mozilla project" and what that means.
  • justdave can do more, but needs help
  • we need at least 2 people who can check each other's code.
  • let's have a big public bugzilla meeting. promote it on dev blogs, etc. inviting input into direction on the product.
  • justdave will set and announce a meeting for a couple of weeks from now maybe as a google hangout.
  • Simon is added to the bugzilla reviewers group. Huzzah!
  • discussion of wiki / documentation infrastructure. gerv describes some of the requirements.
  • justdave will be the only approver for the next 2 weeks (till the next meeting discussion)

the actual BMO meeting

  • glob talks about memcache changes.
  • dkl talks about finishing docs for his project
  • mcote working on reviewboard stuff. authentication issues. you have to log in twice for the same thing. you shoudn't have to login in again to upload a patch . Probably will use cookies. your session in bugzilla could expire while you are in reviewboard. That would be annoying. bugzillla saves your comment if you time out. Or, touch a bugzilla session every time you do something in reviewboard so it won't time out.
  • liz's goals are here: https://wiki.mozilla.org/Auto-tools/Projects/Bugmaster_2013Q3