From gerv at mozilla.org Wed Apr 2 15:34:55 2014 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 02 Apr 2014 16:34:55 +0100 Subject: Bugzilla Installation List Message-ID: I've been remiss at maintaining the Bugzilla Installation List: http://www.bugzilla.org/installation-list/ Part of the reason is that every time I think about doing it, my heart sinks because I have a sneaking suspicion some people don't actually use Bugzilla, they just email their site name in to get Google juice. And there's no good way of telling. I changed a few years ago to using rel=nofollow for non-public ones, and that helped, but I still suspect some of the remaining ones. And of course there's the issue that we have no idea if people are _still_ using Bugzilla who said they were 8 years ago. So my plan is to change the list to list only publicly-accessible Bugzillas. They can have "requirelogin" set, that's OK, as long as the front page can be seen over the web. Then we can verify the truthfulness of assertions. What other options are there? A ping to us from each install that gives the urlbase would be a privacy issue, and not necessarily verifiable anyway. One can imagine more complex schemes, but they'd all require setting up and maintaining. Does anyone have an alternative suggestion, or should I go ahead with the public-only plan? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From Fred.Kleindenst at isilon.com Wed Apr 2 18:29:25 2014 From: Fred.Kleindenst at isilon.com (Kleindenst, Fred) Date: Wed, 2 Apr 2014 14:29:25 -0400 Subject: Bugzilla Installation List In-Reply-To: References: Message-ID: <776691157D89DE4AA026C5D990012C01037E034F30@MX45A.corp.emc.com> I can imagine a feature in the admin section such that: * admin user: -- files out voluntary info -- clicks a "send my info to Mozilla" button * feature compiles some info from existing buzilla installation -- some type of checksum for validity checking -- maybe an anonymized hash based upon urlbase/etc/etc -- report back version info -- report back total bugs/comments/users (voluntary) * feature does a http rpc to a service at Mozilla Call it "self registration". Wrap it up with some kind of inducement if you like. Note my company uses bugzilla, but we don't have our service out in public. Cheers --Fred -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Gervase Markham Sent: Wednesday, April 02, 2014 8:35 AM To: dev-apps-bugzilla at lists.mozilla.org Subject: Bugzilla Installation List I've been remiss at maintaining the Bugzilla Installation List: http://www.bugzilla.org/installation-list/ Part of the reason is that every time I think about doing it, my heart sinks because I have a sneaking suspicion some people don't actually use Bugzilla, they just email their site name in to get Google juice. And there's no good way of telling. I changed a few years ago to using rel=nofollow for non-public ones, and that helped, but I still suspect some of the remaining ones. And of course there's the issue that we have no idea if people are _still_ using Bugzilla who said they were 8 years ago. So my plan is to change the list to list only publicly-accessible Bugzillas. They can have "requirelogin" set, that's OK, as long as the front page can be seen over the web. Then we can verify the truthfulness of assertions. What other options are there? A ping to us from each install that gives the urlbase would be a privacy issue, and not necessarily verifiable anyway. One can imagine more complex schemes, but they'd all require setting up and maintaining. Does anyone have an alternative suggestion, or should I go ahead with the public-only plan? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla - To view or change your list settings, click here: From gerv at mozilla.org Thu Apr 3 15:21:13 2014 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 03 Apr 2014 16:21:13 +0100 Subject: Bugzilla Installation List In-Reply-To: References: Message-ID: <533D7C69.5010907@mozilla.org> On 02/04/14 19:29, Kleindenst, Fred wrote: > I can imagine a feature in the admin section such that: I can imagine that feature too :-) But it would need coding. And is that really the best use of anyone's time? Genuine question. How much value is the installation list? We did originally start it in part as a way of giving a small SEO boost to Bugzilla users, but it's not useful for that any more. Is anyone going to choose Bugzilla because that list is 10000 names rather than 1000? Gerv From mcote at mozilla.com Thu Apr 3 18:26:13 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Thu, 03 Apr 2014 14:26:13 -0400 Subject: Bugzilla Installation List In-Reply-To: <533D7C69.5010907@mozilla.org> References: <533D7C69.5010907@mozilla.org> Message-ID: On 2014-04-03, 11:21 AM, Gervase Markham wrote: > On 02/04/14 19:29, Kleindenst, Fred wrote: >> I can imagine a feature in the admin section such that: > > > I can imagine that feature too :-) But it would need coding. And is that > really the best use of anyone's time? Genuine question. > > How much value is the installation list? We did originally start it in > part as a way of giving a small SEO boost to Bugzilla users, but it's > not useful for that any more. Is anyone going to choose Bugzilla because > that list is 10000 names rather than 1000? Yeah, definitely an interesting idea, but we'd need someone very interested in the idea to code it, and as Gerv says, I don't know that it provides much benefit to anyone anymore. I agree with Gerv in switching our list to just publicly accessible installs, at least until such a time as the above feature might be implemented. I've noticed at least one site that's not on there right now (LibreOffice). Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From cedric.corazza at gmail.com Thu Apr 3 23:07:06 2014 From: cedric.corazza at gmail.com (=?UTF-8?B?Q8OpZHJpYyBDb3Jhenph?=) Date: Fri, 04 Apr 2014 01:07:06 +0200 Subject: Bugzilla Installation List In-Reply-To: <533D7C69.5010907@mozilla.org> References: <533D7C69.5010907@mozilla.org> Message-ID: <__2dnTNz6pwKdKDOnZ2dnUVZ_t6dnZ2d@mozilla.org> Le 03/04/2014 17:21, Gervase Markham a ?crit : > On 02/04/14 19:29, Kleindenst, Fred wrote: >> I can imagine a feature in the admin section such that: > Unless I misunderstood, what would prevent me to setup a test machine, opt in to get referenced and not have a really used Bugzilla installation? > I can imagine that feature too :-) But it would need coding. And is that > really the best use of anyone's time? Genuine question. Agreed: there is not so much coder resources on that project to afford spending time on this (cf. next point) > How much value is the installation list? We did originally start it in > part as a way of giving a small SEO boost to Bugzilla users, but it's > not useful for that any more. Is anyone going to choose Bugzilla because > that list is 10000 names rather than 1000? Agreed again. Your proposal about referencing only public accessible Bugzilla installations seems a good compromise to me: no coding, easy checking (though it could be fake installations in case login is mandatory and moderated), etc. As you wrote, does this project need to have a long list of adopters to boost further adoptions? I don't think so. My two cents C?dric _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Apr 4 09:21:27 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 04 Apr 2014 10:21:27 +0100 Subject: Bugzilla Installation List In-Reply-To: <__2dnTNz6pwKdKDOnZ2dnUVZ_t6dnZ2d@mozilla.org> References: <533D7C69.5010907@mozilla.org> <__2dnTNz6pwKdKDOnZ2dnUVZ_t6dnZ2d@mozilla.org> Message-ID: <85-dnVzRVecK5KPOnZ2dnUVZ_vWXnZ2d@mozilla.org> On 04/04/14 00:07, C?dric Corazza wrote: > Unless I misunderstood, what would prevent me to setup a test machine, > opt in to get referenced and not have a really used Bugzilla installation? Nothing, except that I suspect that SEO-optimizers would not go to that much effort for one link. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From narenthiran88 at gmail.com Sat Apr 5 18:18:07 2014 From: narenthiran88 at gmail.com (R.Naren thiran) Date: Sat, 5 Apr 2014 23:48:07 +0530 Subject: Self-Introduction: Narenthiran Rajaram Message-ID: Hi team, I have joined bugzilla.org recently and would like to introduce myself, Name : Narenthiran Rajaram IRC name : narenthiran_rajaram Location: Chennai, Tamil nadu, India Profession: Systems Engineer Company: Tata consultancy services I would like to contribute to the development of Bugzilla . I am a perl developer with intermediate experience(3.7 years), I hereby also include my resume. I have worked on data mining scripts using perl and linux tools development for system administration tasks such as disk space monitoring. As a new member, I would like you all to guide me to entry level problems and issues which will help me in learning about the bugzilla code base. Looking forward for your support and suggestions.. Regards, R.Narenthiran -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: resume.doc Type: application/msword Size: 51200 bytes Desc: not available URL: From olav at vitters.nl Wed Apr 9 11:43:13 2014 From: olav at vitters.nl (Olav Vitters) Date: Wed, 9 Apr 2014 13:43:13 +0200 Subject: Git workflow Message-ID: <20140409114313.GA17253@bkor.dhs.org> Hi, Is there any recommended workflow people are using in the following situation: - be able to commit changes in a self hosted Bugzilla repository - use that self hosted Bugzilla repository for own installation (easy) - be able to merge changes from git.mozilla.org - be able to move from 4.2 branch to 4.4 branch, etc - be able to see the difference between local and "pristine upstream" - how to set all of this up initially? Any recommended workflow to follow? I'm pretty much an idiot with git. I've found various guides, just wondering what people use in practice. e.g. http://joshbranchaud.com/blog/2014/01/17/Updating-Forked-Git-Repository-With-Latest-Upstream-Changes.html Is that what people do? How do you set up the initial fork? -- Regards, Olav From mcote at mozilla.com Thu Apr 10 05:25:40 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Thu, 10 Apr 2014 01:25:40 -0400 Subject: Bugzilla Public Meeting: 23 April 2014 14:00 UTC Message-ID: The Bugzilla Project is holding a public meeting on 23 April 2014 at 14:00 UTC. Details are on the Bugzilla Meeting wiki page[1]. We'll video-conference either through Google Hangout or Mozilla's Vidyo system, broadcast to Youtube or Air Mozilla, respectively. There will be a follow-up post closer to the date of the meeting with the connection details. In either case, we'll have a back channel on irc.mozilla.org in #bugzilla-meeting. We will have a designated video participant act as IRC proxy. The agenda is on the wiki page[1]. I've also updated the previous meeting page[2] with a summary of the discussion. It has been a while since the last meeting, and we've accomplished many things. Development on version 5.0 is wrapping up and will have a lot of new features and a new look. I'm committed to resurrecting these meetings and holding them regularly, so please come out if you are interested in contributing to Bugzilla in any capacity: support, documentation, engagement, administration, development, design, or any area you can think of! Mark [1]: https://wiki.mozilla.org/Bugzilla:Meeting [2]: https://wiki.mozilla.org/Bugzilla:Meetings:2013-07-17 -------- Mark C?t? Assistant Project Leader, Bugzilla Manager, Automation & Tools, Mozilla http://mrcote.info/ _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Thu Apr 10 05:40:21 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Thu, 10 Apr 2014 01:40:21 -0400 Subject: Bugzilla Public Meeting: 23 April 2014 14:00 UTC In-Reply-To: References: Message-ID: Correcting a reference in the last post: [1]: https://wiki.mozilla.org/Bugzilla:Meetings _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Tue Apr 15 01:36:54 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 14 Apr 2014 21:36:54 -0400 Subject: GitHub mirrors are live Message-ID: We are now mirroring the core Bugzilla repo and the qa (integration test) repo on GitHub: https://github.com/bugzilla/bugzilla https://github.com/bugzilla/qa No other upstream-Bugzilla-related repos are being mirrored at the moment. If there are any others under git.mozilla.org/bugzilla/ that are under active development, I can add them if desired. These mirrors are *read only*. *We don't accept pull requests*. Patches should be submitted using the standard process documented at https://wiki.mozilla.org/Bugzilla:Patches. Feel free to fork the project, of course; in addition to getting free hosting and great tools via GitHub, you'll be able to easily clone our upcoming travis-ci setup (see https://bugzilla.mozilla.org/show_bug.cgi?id=983275). Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From aidenkkim at gmail.com Tue Apr 15 05:08:47 2014 From: aidenkkim at gmail.com (Aiden Kim) Date: Mon, 14 Apr 2014 22:08:47 -0700 (PDT) Subject: [Comments appreciated] Which bugs get fixed? Message-ID: <6a271bd8-14bb-48cb-b235-cfa2c4cb8d60@googlegroups.com> Hi guys, I'm not a developer like the most of you, but maybe I can contribute to the community as well---if everything goes well. For my research, I'm analyzing different aspects of the bug fix process on Bugzilla, and hopefully I can come up with some useful results that could be used to improve Bugzilla in the future. But first, I need to understand Bugzilla community better, and the process in which the bugs get fixed. My questions are: + Who would report bugs on Bugzilla? Casual users (e.g., common users of Firefox), or Mozilla employees? Maybe, employees of companies using and extending Mozilla's software products? Volunteering open-source developers? Basically, how do bugs enter the system, by who, and with what incentives (e.g., monetary, pleasure, interest, related to job, etc)? + Similar to the question above, who would fix bugs on Bugzilla? Mozilla employees? Employees of companies using and extending Mozilla's software products? Volunteering open-source developers? + How do bugs get chosen for fixing? Are they assigned by an authority (as it would happen in corporate setting)? Are they picked up voluntarily (e.g., developer picks up whichever he/she is interested in)? + Are the bugs managed in a stack (e.g., priority stack), or in a queue? Or, are the bugs taken up in a completely random fashion (i.e., people take up whichever they want)? I suppose the story might be different for every developer here, and I want to hear your story. To compress my questions, I'm interested in: + Who reports bugs, and why + Who fixes bugs, and why + How bugs get chosen for fixing, and in what order, if any. I'll be looking forward to hear from you! And, please feel free to let me know if there is another more appropriate place for my questions. Thank you for your replies and pointers in advance! Best, -Aiden _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From damien.nozay at gmail.com Wed Apr 16 04:31:01 2014 From: damien.nozay at gmail.com (Damien) Date: Tue, 15 Apr 2014 21:31:01 -0700 Subject: GitHub mirrors are live In-Reply-To: References: Message-ID: Hey Mark, maybe some changes to the readme pointing to the standard process to submit patches / report issues would be good. thanks, damien _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Wed Apr 16 16:27:10 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Wed, 16 Apr 2014 12:27:10 -0400 Subject: GitHub mirrors are live In-Reply-To: References: Message-ID: On 2014-04-16, 12:31 AM, Damien wrote: > Hey Mark, > maybe some changes to the readme pointing to the standard process to submit > patches / report issues would be good. Yes, I do want to update the README to clarify things now that it's being mirrored around. I'll try to do that soon unless someone beats me to it. :) Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gmorris at royall.com Wed Apr 16 19:23:45 2014 From: gmorris at royall.com (Morris, Gordon) Date: Wed, 16 Apr 2014 15:23:45 -0400 Subject: unsubscribe Message-ID: Gordon Morris Test Engineer Royall & Company O: 804.741.6337, Ext 1169 | M: 804.221.9529 | F: 804.741.8969 gmorris at royall.com | royall.com _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Apr 18 13:17:28 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 18 Apr 2014 14:17:28 +0100 Subject: Poor patch timing... Message-ID: <4uOdndCBs5l0uMzOnZ2dnUVZ_qadnZ2d@mozilla.org> 16:48:07 - LpSolit: gerv: we usually don't commit non-critical patches in the middle of the release process :( 16:48:57 - LpSolit: gerv: and Tinderbox is now burning Sorry everyone. Didn't realise we were in the middle of release :-( Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Tue Apr 22 02:37:51 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 21 Apr 2014 22:37:51 -0400 Subject: Reminder: Bugzilla Public Meeting: 23 April 2014 14:00 UTC Message-ID: This is a reminder that the Bugzilla project is holding a public meeting on 23 April 2014 at 14:00 UTC[1]. We will be using Mozilla's Vidyo system for interactive video, in the Bugzilla room, and it will be simultaneously broadcast and recorded on Air Mozilla. We'll use an IRC channel with a designated moderator. See the Meetings wiki page for connection details[2] as well as an agenda. Note that a discussion of the road map is listed. The Roadmap wiki page[3] has recently been updated to reflect the current situation; if you're interested, you might want to review it quickly before the meeting. Mark [1] http://arewemeetingyet.com/UTC/2014-04-23/14:00/Bugzilla%20Project%20Public%20Meeting [2] https://wiki.mozilla.org/Bugzilla:Meetings [3] https://wiki.mozilla.org/Bugzilla:Roadmap _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Apr 22 14:53:29 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 22 Apr 2014 15:53:29 +0100 Subject: The Bugzilla Guide in Bulgarian Message-ID: http://www.ajoft.com/wpaper/aj-bugzilla.html I've encouraged the translator to get in touch with the project as a whole :-) Cedric or others: how is the project going to get other translations of the Guide into a form where they can be put up on ReadTheDocs? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Tue Apr 22 20:31:22 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 22 Apr 2014 16:31:22 -0400 Subject: Reminder: Bugzilla Public Meeting: 23 April 2014 14:00 UTC In-Reply-To: References: Message-ID: Just a reminder that, if you want to participate via Vidyo (as opposed to just watching on Air Mozilla), you should install the client ahead of time. Go to https://v.mozilla.com/ to get it. I will post a guest link tomorrow ahead of the meeting. Mark On 2014-04-21, 10:37 PM, Mark C?t? wrote: > This is a reminder that the Bugzilla project is holding a public meeting > on 23 April 2014 at 14:00 UTC[1]. > > We will be using Mozilla's Vidyo system for interactive video, in the > Bugzilla room, and it will be simultaneously broadcast and recorded on > Air Mozilla. We'll use an IRC channel with a designated moderator. See > the Meetings wiki page for connection details[2] as well as an agenda. > > Note that a discussion of the road map is listed. The Roadmap wiki > page[3] has recently been updated to reflect the current situation; if > you're interested, you might want to review it quickly before the meeting. > > Mark > > [1] > http://arewemeetingyet.com/UTC/2014-04-23/14:00/Bugzilla%20Project%20Public%20Meeting > [2] https://wiki.mozilla.org/Bugzilla:Meetings > [3] https://wiki.mozilla.org/Bugzilla:Roadmap > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Mon Apr 28 15:30:39 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 28 Apr 2014 11:30:39 -0400 Subject: Triage party! Message-ID: <-KKdnZWiWbGC6cPOnZ2dnUVZ_u-dnZ2d@mozilla.org> Hi Bugzilla contributors, as discussed during our meeting last week (of which I will be posting minutes in a day or two), I'd like to hold a triage party soon. We can go through as many open bugs as possible with the goals of 1. moving feature-request bugs that are potentially useful but too far from our road map into an Extension Ideas component, 2. closing bugs that are duplicates or invalid (probably not many of those, but you never know what might have slipped by) or that are not suitable for either core or an extension, and 3. identifying good first bugs. I think the best way to do this would be to get the full list of open bugs and divide them up by the number of attendees, and then individually assess them for the above points. As I mentioned in the meeting, I think we should, as the Wikipedia says, "be bold"; there's a history of every change, and many of subscribe to all changes in bugs in the Bugzilla product so we can audit either as we go or after the meeting and revert any mistakes. Otherwise, if we go through each bug together, we won't get very far. That said, everyone should feel free to ask for clarification on any bug; that's part of the point of getting us all together (the other is to alleviate boredom :) I suggest Wednesday, May 7, at 14:00 UTC (the same time spot as our regular meetings), in the Bugzilla Vidyo room and on IRC in #bugzilla (*not* #bugzilla-meeting, since we can potentially benefit from anyone hanging around in #bugzilla!). I don't think we'll bother to broadcast to Air Mozilla for this, unless anyone desires. If there are no suggestions of a better time, see you all then! Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Apr 29 12:36:02 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 29 Apr 2014 13:36:02 +0100 Subject: Triage party! In-Reply-To: <-KKdnZWiWbGC6cPOnZ2dnUVZ_u-dnZ2d@mozilla.org> References: <-KKdnZWiWbGC6cPOnZ2dnUVZ_u-dnZ2d@mozilla.org> Message-ID: On 28/04/14 16:30, Mark C?t? wrote: > I suggest Wednesday, May 7, at 14:00 UTC (the same time spot as our > regular meetings), in the Bugzilla Vidyo room and on IRC in #bugzilla You had to pick the week I was in the USA, so this is 7am rather than 3pm... :-P Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From theycallmefish at gmail.com Tue Apr 29 14:48:25 2014 From: theycallmefish at gmail.com (Ryan Wilson) Date: Tue, 29 Apr 2014 07:48:25 -0700 (PDT) Subject: Triage party! In-Reply-To: References: <-KKdnZWiWbGC6cPOnZ2dnUVZ_u-dnZ2d@mozilla.org> Message-ID: On Tuesday, April 29, 2014 6:36:02 AM UTC-6, Gervase Markham wrote: > On 28/04/14 16:30, Mark C?t? wrote: > > > I suggest Wednesday, May 7, at 14:00 UTC (the same time spot as our > > > regular meetings), in the Bugzilla Vidyo room and on IRC in #bugzilla > > > > You had to pick the week I was in the USA, so this is 7am rather than > > 3pm... :-P > > > > Gerv I will be there, though I may have a few brief AFK moments if it runs over an hour. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Tue Apr 29 20:45:34 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 29 Apr 2014 16:45:34 -0400 Subject: Triage party! In-Reply-To: References: <-KKdnZWiWbGC6cPOnZ2dnUVZ_u-dnZ2d@mozilla.org> Message-ID: On 2014-04-29, 8:36 AM, Gervase Markham wrote: > On 28/04/14 16:30, Mark C?t? wrote: >> I suggest Wednesday, May 7, at 14:00 UTC (the same time spot as our >> regular meetings), in the Bugzilla Vidyo room and on IRC in #bugzilla > > You had to pick the week I was in the USA, so this is 7am rather than > 3pm... :-P Yeah, this time is definitely not going to be perfect for everyone. If the party works well, I think we should do another one at a different time to accommodate others, that is, if we don't triage all the bugs next week. ;) Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Wed Apr 30 14:12:03 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Wed, 30 Apr 2014 10:12:03 -0400 Subject: Minutes and next meeting Message-ID: <_NidnRj-EekvmfzOnZ2dnUVZ_tudnZ2d@mozilla.org> Minutes from the last meeting are up on https://wiki.mozilla.org/Bugzilla:Meetings:2014-04-23. There were no objections to holding these meetings on a monthly basis on the 4th Wednesday of every month at 14:00 UTC. Therefore the next meeting will be on 28 May 2014 at 14:00 UTC. You can always see details about the next meeting on the Meetings wiki page (https://wiki.mozilla.org/Bugzilla:Meetings), which is generally updated soon after the previous meeting ends. The meetings are also listed on the Air Mozilla calendar (https://air.mozilla.org/calendar/). Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla