From gerv at mozilla.org Tue Mar 11 11:44:55 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 11 Mar 2014 11:44:55 +0000 Subject: Tests using SQLite Message-ID: <6JydnRXK7JeqaoPOnZ2dnUVZ_sadnZ2d@mozilla.org> This idea has been running around my head for a bit... Now that Bugzilla has SQLite support, can we use it for writing tests which require a database? We could make a simple-ish test database as an SQLite file, and then it would be possible to run read and even write tests without damaging the user's real installation. The DB could be reset after each test using source control commands. This wouldn't have been nearly so easy with e.g. MySQL, but is with SQLite. Is this a good idea? 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 Mar 11 16:20:32 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 11 Mar 2014 12:20:32 -0400 Subject: Git migration today at 17:00 UTC Message-ID: As scheduled, the migration of Bugzilla and related repositories from Bazaar on bzr.mozilla.org to git on git.mozilla.org will start at 17:00 UTC today, that is, approximately 40 minutes from now. Expected duration is around 2 hours. See https://wiki.mozilla.org/Bugzilla:Migrating_to_git for more, including a detailed plan. Feel free to join #bteam on irc.mozilla.org to follow along. I will send a follow-up message after the migration, when write access is enabled on the git repositories. 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 Tue Mar 11 16:48:51 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 11 Mar 2014 12:48:51 -0400 Subject: Git migration today at 17:00 UTC In-Reply-To: References: Message-ID: Correction: we'll use #bugzilla to discuss/monitor the migration. Mark On 2014-03-11, 12:20 PM, Mark C?t? wrote: > As scheduled, the migration of Bugzilla and related repositories from > Bazaar on bzr.mozilla.org to git on git.mozilla.org will start at 17:00 > UTC today, that is, approximately 40 minutes from now. Expected duration > is around 2 hours. > > See https://wiki.mozilla.org/Bugzilla:Migrating_to_git for more, > including a detailed plan. Feel free to join #bteam on irc.mozilla.org > to follow along. > > I will send a follow-up message after the migration, when write access > is enabled on the git repositories. > > 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 Tue Mar 11 20:36:32 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 11 Mar 2014 16:36:32 -0400 Subject: Git migration successful! Message-ID: And we're up! There were a few slight delays due to minor issues, but git.mozilla.org/bugzilla/bugzilla.git and related repositories are now available; write access has been enabled on git for those who had write access on bzr.mozilla.org. The first commit to the Bugzilla git repository was successfully mirrored to bzr: http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=commit;h=d51abfd7e3e1fcc3eea37e72ab0f49f3e28950a2 http://bzr.mozilla.org/bugzilla/trunk/revision/8957 Thanks to all involved! Stay tuned for the post migration steps in the coming weeks, including a mirroring to GitHub and moving from Tinderbox to travis-ci. 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 Mar 12 02:08:08 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 11 Mar 2014 22:08:08 -0400 Subject: Git migration successful! In-Reply-To: References: Message-ID: It appears that tags weren't migrated from bzr to git. I'll have that fixed tomorrow. Mark On 2014-03-11, 4:36 PM, Mark C?t? wrote: > And we're up! There were a few slight delays due to minor issues, but > git.mozilla.org/bugzilla/bugzilla.git and related repositories are now > available; write access has been enabled on git for those who had write > access on bzr.mozilla.org. > > The first commit to the Bugzilla git repository was successfully > mirrored to bzr: > > http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=commit;h=d51abfd7e3e1fcc3eea37e72ab0f49f3e28950a2 > > http://bzr.mozilla.org/bugzilla/trunk/revision/8957 > > Thanks to all involved! Stay tuned for the post migration steps in the > coming weeks, including a mirroring to GitHub and moving from Tinderbox > to travis-ci. > > 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 Mar 12 02:52:25 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 11 Mar 2014 22:52:25 -0400 Subject: Git migration successful! In-Reply-To: References: Message-ID: Fixed; was a simple omission of push --tags. There were some errors in the tag migration, however. Tags in git are shared amongst all branches. Thus, the same tag can only exist only once in a given repository. The only affected tag in Bugzilla core was bugzilla-stable, which was found in most branches; I moved it to the latest occurrence (as it was tagged in bzr's bugzilla/4.4). There were a few other similar cases in bmo and testopia, which I am also resolving by moving them to the occurrence in the repo's most recent branch. A couple other tags were applied to bzr branches where earlier branches went their own ways (e.g. bugzilla-3.3.4 applied to bugzilla/3.6 where bugzilla/3.4 branched off). I've left those tags as their *original* branch occurrence, e.g. bugzilla-3.3.4 stayed where it was tagged in bzr's bugzilla/3.4. Mark On 2014-03-11, 10:08 PM, Mark C?t? wrote: > It appears that tags weren't migrated from bzr to git. I'll have that > fixed tomorrow. > > Mark > > > On 2014-03-11, 4:36 PM, Mark C?t? wrote: >> And we're up! There were a few slight delays due to minor issues, but >> git.mozilla.org/bugzilla/bugzilla.git and related repositories are now >> available; write access has been enabled on git for those who had write >> access on bzr.mozilla.org. >> >> The first commit to the Bugzilla git repository was successfully >> mirrored to bzr: >> >> http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=commit;h=d51abfd7e3e1fcc3eea37e72ab0f49f3e28950a2 >> >> http://bzr.mozilla.org/bugzilla/trunk/revision/8957 >> >> Thanks to all involved! Stay tuned for the post migration steps in the >> coming weeks, including a mirroring to GitHub and moving from Tinderbox >> to travis-ci. >> >> 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 Mar 12 13:52:13 2014 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Wed, 12 Mar 2014 09:52:13 -0400 Subject: Git migration successful! In-Reply-To: References: Message-ID: That's true. Going forward, that's probably what we should do for moveable "tags" like bugzilla-stable, although there are better ways to do this kind of thing in git. For past history, I could go back and add the old bugzilla-stable tags as notes, but I suspect they are no longer useful. I believe they always point to the latest version-tagged commit anyway. Related, I should note that the git->bzr mirroring script does *not* mirror tags. It would be quite difficult to do this, given that there's no clear mapping between git and bzr commits, and tagging is not pprt of the commit process itself, i.e. they can of course be applied at any time to any existing revision. I think we'll have to manually tag bzr when we do releases for now, and we can rethink our branching strategy for the next stable release (5.0), which won't be mirrored to bzr. Mark On 2014-03-12, 12:01 AM, Damien wrote: > w.r.t git tags being unique and not to be updated once public. > ---> you should use git notes instead to keep tabs on commits that are > stable. > > http://git-scm.com/blog/2010/08/25/notes.html > http://git-scm.com/docs/git-notes > > $0.02 - damien > > > On Tue, Mar 11, 2014 at 7:52 PM, Mark C?t? wrote: > >> Fixed; was a simple omission of push --tags. >> >> There were some errors in the tag migration, however. Tags in git are >> shared amongst all branches. Thus, the same tag can only exist only >> once in a given repository. The only affected tag in Bugzilla core was >> bugzilla-stable, which was found in most branches; I moved it to the >> latest occurrence (as it was tagged in bzr's bugzilla/4.4). >> >> There were a few other similar cases in bmo and testopia, which I am >> also resolving by moving them to the occurrence in the repo's most >> recent branch. >> >> A couple other tags were applied to bzr branches where earlier branches >> went their own ways (e.g. bugzilla-3.3.4 applied to bugzilla/3.6 where >> bugzilla/3.4 branched off). I've left those tags as their *original* >> branch occurrence, e.g. bugzilla-3.3.4 stayed where it was tagged in >> bzr's bugzilla/3.4. >> >> Mark >> >> On 2014-03-11, 10:08 PM, Mark C?t? wrote: >>> It appears that tags weren't migrated from bzr to git. I'll have that >>> fixed tomorrow. >>> >>> Mark >>> >>> >>> On 2014-03-11, 4:36 PM, Mark C?t? wrote: >>>> And we're up! There were a few slight delays due to minor issues, but >>>> git.mozilla.org/bugzilla/bugzilla.git and related repositories are now >>>> available; write access has been enabled on git for those who had write >>>> access on bzr.mozilla.org. >>>> >>>> The first commit to the Bugzilla git repository was successfully >>>> mirrored to bzr: >>>> >>>> >> http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=commit;h=d51abfd7e3e1fcc3eea37e72ab0f49f3e28950a2 >>>> >>>> http://bzr.mozilla.org/bugzilla/trunk/revision/8957 >>>> >>>> Thanks to all involved! Stay tuned for the post migration steps in the >>>> coming weeks, including a mirroring to GitHub and moving from Tinderbox >>>> to travis-ci. >>>> >>>> Mark >>>> >>> >> >> _______________________________________________ >> 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: >> >> _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Wed Mar 12 14:45:34 2014 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Wed, 12 Mar 2014 15:45:34 +0100 Subject: Git migration successful! In-Reply-To: References: Message-ID: <5320730E.8020001@gmail.com> Le 12. 03. 14 14:52, Mark C?t? a ?crit : > For past history, I could go back and add the old bugzilla-stable tags > as notes, but I suspect they are no longer useful. I believe they > always point to the latest version-tagged commit anyway. We have one bugzilla-stable tag per branch on purpose. They shouldn't be removed. It points to the latest release available on a given branch. LpSolit From mcote at mozilla.com Wed Mar 12 15:37:53 2014 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Wed, 12 Mar 2014 11:37:53 -0400 Subject: Git migration successful! In-Reply-To: References: Message-ID: <45OdnRB4ipvN4r3OnZ2dnUVZ_s-dnZ2d@mozilla.org> On 2014-03-12, 10:45 AM, Fr?d?ric Buclin wrote: > Le 12. 03. 14 14:52, Mark C?t? a ?crit : >> For past history, I could go back and add the old bugzilla-stable tags >> as notes, but I suspect they are no longer useful. I believe they >> always point to the latest version-tagged commit anyway. > > We have one bugzilla-stable tag per branch on purpose. They shouldn't be > removed. It points to the latest release available on a given branch. To reiterate, it isn't possible as a tag in git. This kind of thing would probably normally be done as branches (every minor version would have its own branch, since they're cheap in git, and you could have a stable-latest branch pointing to the latest branch, or whatever). The latest release is easy to determine from the list of tags, but I'll add git notes if you want. Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From luckyk1592 at gmail.com Thu Mar 13 09:23:25 2014 From: luckyk1592 at gmail.com (Lalit Khattar) Date: Thu, 13 Mar 2014 14:53:25 +0530 Subject: GSoC proposal: Migrate from YUI2 to YUI3 Message-ID: Hi all, I have prepared a draft for GSoC project- 'Migrate from YUI2 to YUI3'. Kindly review it. Any suggestions are welcomed. Thanks, Lalit *Personal Details* - Name: Lalit Khattar - Email: luckyk1592 at gmail.com - IRC nick on irc.mozilla.org: dne0 - Telephone: +918979890064 - Other contact methods: gtalk - Country of residence: India - Timezone: India Time Zone(UTC+05:30) - Primary language: English and Hindi *Project Proposal*To migrate from YUI2 to YUI3. *Why is migration required?* Bugzilla JS code uses an external library(YUI2) for DOM manipulation and other client side interactions. In September 2009, YUI3 was released which is completely different from YUI2. Also, YUI2 version is no longer maintained so the code is now kind of obsolete. Yahoo started the work in 2012 however the progress has stalled. Therefore, migration to YUI3 is a high priority issue. *Why not use jQuery instead of YUI3?* - As stated by Evan, jQuery is great for DOM manipulation, AJAX etc, but it does not factor code into modules like YUI3 does. - Also, I have looked into the previous work done by Evan and I believe that it can still be used without any major changes in his code and will give a head start on the project. *Code Analysis* A simple grep showed which directories/files uses YUI2 code:- - js/ - template/ - extensions/Voting/template Obviously, majority of YUI2 code lies in js directory. Next on the target is Template directory code and last is Voting extension template code. *JS code* As mentioned earlier, I looked into Evan's code and found following JS files(plus, some inline JS) were already migrated into new modules:- 1. global.js => bz-base/js/login.js, bz-base/js/intl.js 2. comments.js => bz-comments/js/comments.js 3. attachments.js => bz-attachments/js/attachments.js (Partial migration done) 4. change-columns.js => bz-columns/js/columns.js, bz-select/js/select.js 5. params.js => bz-parms/js/params.js 6. productform.js => bz-products/js/products.js 7. custom-search.js => bz-search/js/search.js (Partial migration done) YUI3 version used by Evan is 3.7.3(found here). It should be upgraded to 3.14(or whatever newer version is available). Things might break due to this, therefore manual testing will be required. So, my first task will be to upgrade YUI 3.7.3 to >=3.14, test the migrated code and complete the migration of attachments.js and custom-search.js. Now, the following js files will be left to migrate and below I have proposed to which module each file might go:- 1. comment-tagging.js => bz-comments/js/comment-tagging.js 2. expanding-tree.js => bz-tree/js/expanding-tree.js 3. flag.js => bz-flag/js/flag.js 4. bug.js => bz-bug/js/bug.js 5. util.js => bz-util/js/util.js 6. field.js => bz-util/js/field.js 7. TUI.js => bz-util/js/TUI.js This is just my initial thought on how JS directory structure should be further extended. I will finalize the structure with mentor/community, if my proposal gets accepted. So, my next task will be to migrate the above js files. *Template Code(inline js)* I will be looking side by side into the template files that has the js files included in it that are currently being migrated and check for any YUI2 code in those template files. This approach might not cover all the templates but it will make sure that all the linked js and template files are covered. Last, I will look for any remaining YUI2 code using grep. *Voting Extension Template Code* A simple grep showed this doesn't have much YUI2 code, so this one will be the easiest to migrate. *Schedule of Deliverables* I will be able to spend full time only till mid term evaluation(approximately 7-8 hours each day). After that, I might get busy with job, so contribution will reduce to approximately 4-5 hours on weekdays. But, I am willing to spend more time on weekends, if the project is behind schedule. Average time per week = 40 hours Before 28 April - Exam period from April 21 - April 27 - Will be available on irc all the time April 29 - May 5: (1 week) - Learning YUI3, template toolkit and bzr. - Already familiar with jQuery and git. Won't take much time to learn YUI3 and bzr. May 5 - May 18: (2 weeks) - Get good idea of what each JS file does, study YUI2 code. - Talk with mentor/community about migration steps like module structure, code structure etc. - Get a head start. May 19 - June 10: (3 weeks) - Upgrade YUI 3.7.3 to >=3.14 - Manually test the migration done by Evan. - Complete the migration of custom-search.js and attachments.js. June 11 - June 25: (2 weeks) - Migrate bug.js, flag.js and related template files. - Test the migration manually. - Note: These are small files so they might take less than 2 weeks. Mid term deliverables: - 50-60% of the code(including inline js) will be migrated and tested. June 26 - July 17: (3 weeks) - Migrate field.js, util.js, TUI.js and related template files. - Test the migration manually. July 18 - Aug 3: (2 weeks) - Migrate comment-tagging.js, expanding-tree.js and related template files. - Test the migration manually. Aug 4 - Aug 18: (2 weeks) - Finishing up the work left due to unexpected delays. - Check for any unmigrated code in templates. Post GSoC or if time permits: - Move inline js to external files. - Write tests. *Open Source Development Experience* I recently started contributing to Mozilla and submitted few patches:- - Add a "Watch" button on the new inspection popup . - Large Textbox should have maxlength and wrap =>1 in buglists. - show_bug.cgi should use field-label.html.tmpl for field headers. (Not reviewed yet) I also did some benchmarking of this bug to test whether the JS performance issue in current code is still there or not. I regularly use open source libraries, frameworks for my projects. My other open source contributions can be found on my GitHub profile. I developed a chat application using AJAX polling in front-end and open sourced it on GitHub. *Work/Internship Experience* I did internship in a startup, HackerEarth and projects I worked on over the summer and winter internship period are listed below:- - The Robust Relatime Server - Continuous Deployment System - Introducing CodePlayer- Watch your code like a movie - HackerEarth.vim- A vim plugin to compile/run code *Academic Experience* I am an undergraduate student at Indian Institute of Technology(IIT), Roorkee. I am in final year and studying Metallurgical and Materials Engineering. *Why Me* I have got decent experience working with web technologies- HTML, CSS, Javascript, Python(Django) and PHP(Yii). I like playing with Javascript in my spare time. I am a part of Information Management Group(IMG), in IIT Roorkee, which is a student body responsible for developing and managing all Internet and Intranet applications in IIT Roorkee, including the institute website . I have done two projects under IMG:- - Institute Notice Board(Android App) - Content Management System of institute website. Also, I would like to mention that the CodePlayer work which I did during my internship required good knowledge of Javascript. I was able to build play, pause, forward functionality in a short span. *Why Mozilla* All Mozilla open source projects and their respective community are amazing. My first open source contribution was in Mozilla. The team has been really helpful and friendly to me. I would like to contribute to Mozilla through GSoC program and further plans to continue doing that. -------------- next part -------------- An HTML attachment was scrubbed... URL: From michiel.beijen at gmail.com Thu Mar 13 20:17:18 2014 From: michiel.beijen at gmail.com (Michiel Beijen) Date: Thu, 13 Mar 2014 21:17:18 +0100 Subject: GSoC proposal: Migrate from YUI2 to YUI3 In-Reply-To: References: Message-ID: Hi, On Thu, Mar 13, 2014 at 10:23 AM, Lalit Khattar wrote: > I have prepared a draft for GSoC project- 'Migrate from YUI2 to YUI3'. > Kindly review it. Any suggestions are welcomed. Please understand I do not have much actual experience with Bugzilla's YUI code. But I do have experience with YUI and jQuery, and I'd like to point out that YUI3 does not have a lot of traction and the last release was in june of 2013, which is kind of a long period in Internet time. So with the proposal to upgrade from YUI2 to YUI3 Bugzilla's frontend code will get a little less out of date, but in maybe one or two years you'll have a similar problem again. Have you considered how much effort it would be to port from YUI2 to jQuery, or to another framework; or even to vanilla JS? Also, I think, moving to something more popular than YUI[23] will have the added benefit of being able to use more available plugins, and maybe even making it easier for possible contributors to send patches. -- Mike From dmarshal at yahoo-inc.com Thu Mar 13 20:40:41 2014 From: dmarshal at yahoo-inc.com (David Marshall) Date: Thu, 13 Mar 2014 20:40:41 +0000 Subject: GSoC proposal: Migrate from YUI2 to YUI3 In-Reply-To: References: Message-ID: <18E9F9A5-AF04-4667-B165-911623A0E54F@yahoo-inc.com> On Mar 13, 2014, at 1:17 PM, Michiel Beijen wrote: > Hi, > > On Thu, Mar 13, 2014 at 10:23 AM, Lalit Khattar wrote: > >> I have prepared a draft for GSoC project- 'Migrate from YUI2 to YUI3'. >> Kindly review it. Any suggestions are welcomed. > > Please understand I do not have much actual experience with Bugzilla's YUI code. > But I do have experience with YUI and jQuery, and I'd like to point > out that YUI3 does not have a lot of traction and the last release was > in june of 2013, which is kind of a long period in Internet time. I don?t really understand that remark, because there was a release less than a month ago: http://www.yuiblog.com/blog/2014/02/26/yui-3-15-0-released/ > > So with the proposal to upgrade from YUI2 to YUI3 Bugzilla's frontend > code will get a little less out of date, but in maybe one or two years > you'll have a similar problem again. Have you considered how much > effort it would be to port from YUI2 to jQuery, or to another > framework; or even to vanilla JS? > When I compare the activity between YUI and jQuery: https://github.com/jquery/jquery/graphs/commit-activity https://github.com/yui/yui3/graphs/commit-activity it looks as though YUI is more active than jQuery. From michiel.beijen at gmail.com Thu Mar 13 21:51:52 2014 From: michiel.beijen at gmail.com (Michiel Beijen) Date: Thu, 13 Mar 2014 22:51:52 +0100 Subject: GSoC proposal: Migrate from YUI2 to YUI3 In-Reply-To: <18E9F9A5-AF04-4667-B165-911623A0E54F@yahoo-inc.com> References: <18E9F9A5-AF04-4667-B165-911623A0E54F@yahoo-inc.com> Message-ID: Hi David, On Thu, Mar 13, 2014 at 9:40 PM, David Marshall wrote: > > On Mar 13, 2014, at 1:17 PM, Michiel Beijen wrote: >> >> Please understand I do not have much actual experience with Bugzilla's YUI code. >> But I do have experience with YUI and jQuery, and I'd like to point >> out that YUI3 does not have a lot of traction and the last release was >> in june of 2013, which is kind of a long period in Internet time. > > I don?t really understand that remark, because there was a release less than a month ago: > > http://www.yuiblog.com/blog/2014/02/26/yui-3-15-0-released/ Ah really? I'm sorry in that case, I got the information from the YUI3 web page at http://yuilibrary.com/projects/yui3/ which is out of date then, I suppose. >> So with the proposal to upgrade from YUI2 to YUI3 Bugzilla's frontend >> code will get a little less out of date, but in maybe one or two years >> you'll have a similar problem again. Have you considered how much >> effort it would be to port from YUI2 to jQuery, or to another >> framework; or even to vanilla JS? > > When I compare the activity between YUI and jQuery: > > https://github.com/jquery/jquery/graphs/commit-activity > > https://github.com/yui/yui3/graphs/commit-activity > > it looks as though YUI is more active than jQuery.- Well, I think it is true that jQuery has not had activity very recently, but for instance, jQuery has more 'stars' in Github and there are more books for instance on the topic. But of course there are multiple ways you can measure activity. And YUI turns out to be more active than I thought it was, so that's nice. Anyway, I started responding because I wanted to ask if it had been considered moving to something else than YUI. If it has been considered and there are good reasons to make the move to YUI3, that's great. -- Mike From dmarshal at yahoo-inc.com Thu Mar 13 22:32:34 2014 From: dmarshal at yahoo-inc.com (David Marshall) Date: Thu, 13 Mar 2014 22:32:34 +0000 Subject: GSoC proposal: Migrate from YUI2 to YUI3 In-Reply-To: References: <18E9F9A5-AF04-4667-B165-911623A0E54F@yahoo-inc.com> Message-ID: <716D08D3-437B-4EB7-9916-F93623D39862@yahoo-inc.com> On Mar 13, 2014, at 2:51 PM, Michiel Beijen wrote: > > Well, I think it is true that jQuery has not had activity very > recently, but for instance, jQuery has more 'stars' in Github and > there are more books for instance on the topic. But of course there > are multiple ways you can measure activity. And YUI turns out to be > more active than I thought it was, so that's nice. > If we are counting books, wouldn?t that suggest that PHP is the greatest computer language ever? :) > Anyway, I started responding because I wanted to ask if it had been > considered moving to something else than YUI. If it has been > considered and there are good reasons to make the move to YUI3, that's > great. I think it?s very reasonable to ask whether it is sensible to move to something other than YUI. It probably all comes down to who is willing to implement what. I interested Evan Goer in upgrading from YUI 2 to YUI 3 exactly because someone had been asking about going to jQuery. Evan works at Apple now, so I doubt he?s doing much of anything in that regard anymore. If someone shows up with a patch that replaces YUI with jQuery, more power to them! I can tell you that YUI development continues, perhaps at an even greater pace than ever before. At Yahoo we have been making great strides in our productivity and innovation. I wish I could tell you more about how we are doing that, but I cannot. I myself have been doing so much node.js that maybe all the YUI stuff will become sufficiently less incomprehensible that I can offer meaningful contributions! From wurblzap at gmail.com Fri Mar 14 12:49:20 2014 From: wurblzap at gmail.com (Marc Schumann) Date: Fri, 14 Mar 2014 13:49:20 +0100 Subject: GSoC proposal: Migrate from YUI2 to YUI3 In-Reply-To: <716D08D3-437B-4EB7-9916-F93623D39862@yahoo-inc.com> References: <18E9F9A5-AF04-4667-B165-911623A0E54F@yahoo-inc.com> <716D08D3-437B-4EB7-9916-F93623D39862@yahoo-inc.com> Message-ID: Fwiw: There's a very early (read: very incomplete and buggy) Bugzilla installation at https://landfill.bugzilla.org/bootstrap/, which aims to replace YUI by JQuery Bootstrap (http://getbootstrap.com/2.3.2/). The plan was to tell of this here only as soon as index.cgi and show_bug.cgi worked agreeably, but maybe this is rather the time. Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcote at mozilla.com Fri Mar 21 15:30:16 2014 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Fri, 21 Mar 2014 11:30:16 -0400 Subject: Git migration successful! In-Reply-To: References: <45OdnRB4ipvN4r3OnZ2dnUVZ_s-dnZ2d@mozilla.org> Message-ID: On 2014-03-20, 6:52 PM, Damien wrote: > Hey Mark, > > quick question about the GIT mirroring; is there a timeline for it to be > mirrored ? There are several questions in there. :) Firstly, git.mozilla.org is now the repository of truth, meaning the mirroring happens *from* git.mozilla.org *to* bzr.mozilla.org (and soon to github). The script that mirrors from git.mozilla.org to bzr.mozilla.org runs every 5 minutes. > http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary > https://github.com/bugzilla/bugzilla > > this shows: > >> descriptionnoneownerlast changeThu, 20 Mar 2014 19:55:57 +0000URLssh:// >> gitolite3 at git.mozilla.org/bugzilla/bugzilla.git >> https://git.mozilla.org/bugzilla/bugzilla.git > > > but when I visit https://git.mozilla.org/bugzilla/bugzilla.git I get: > >> Not Found >> >> The requested URL /bugzilla/bugzilla.git was not found on this server. >> ------------------------------ >> Apache/2.2.15 (Red Hat) Server at git.mozilla.org Port 80 That's just an artifact of gitweb, which admittedly is not the greatest web UI for git (there's some talk about setting up an alternate web UI, such as cgit, since for various reasons we may not be able to take down gitweb entirely). The first URL you listed (actually only the p= part is needed, i.e. http://git.mozilla.org/?p=bugzilla/bugzilla.git) takes you to the gitweb (web UI) version for the repo, where you can poke around the repo in your browser. The second (https://git.mozilla.org/bugzilla/bugzilla.git) is the read-only git URL. It only works if you are using git to access it directly, e.g. $ git clone https://git.mozilla.org/bugzilla/bugzilla.git Cloning into 'bugzilla'... remote: Counting objects: 87446, done. remote: Compressing objects: 100% (19615/19615), done. remote: Total 87446 (delta 64056), reused 87349 (delta 64008) Receiving objects: 100% (87446/87446), 16.45 MiB | 2.65 MiB/s, done. Resolving deltas: 100% (64056/64056), done. Checking connectivity... done. The other URL (gitolite3 at git.mozilla.org/bugzilla/bugzilla.git) is for use with git if you have write privileges. > and when I visit https://github.com/bugzilla/bugzilla I get: > > >> This repository is empty. >> >> Care to check out the GitHub Channel on YouTube while >> you wait? >> Yeah that part isn't completed yet; we're waiting on https://bugzilla.mozilla.org/show_bug.cgi?id=982662. I've been told it should be a week or so away. Hope that answers your questions. Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From acho.arnold at live.com Wed Mar 26 06:27:32 2014 From: acho.arnold at live.com (Acho Arnold) Date: Wed, 26 Mar 2014 07:27:32 +0100 Subject: Add keyboard shortcuts to Bugzilla Message-ID: Good day, I would like to work on bug 414599 and It involves adding keyboard shortcuts to bugzilla. Which keyboard shortcuts would you guys want and on which pages should this keyboard shortcuts be active? Thanks. Acho Arnold Ewin Telephone: (+237) 77 84 51 63 Buea, Cameroon acho.arnold at live.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Wed Mar 26 08:56:23 2014 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 26 Mar 2014 09:56:23 +0100 Subject: Add keyboard shortcuts to Bugzilla In-Reply-To: References: Message-ID: On 26/03/14 07:27, Acho Arnold wrote: > I would like to work on bug 414599 > and It involves > adding keyboard shortcuts to bugzilla. > Which keyboard shortcuts would you guys want and on which pages should > this keyboard shortcuts be active? The question before that is: is having keyboard shortcuts actually a good idea? We used to have them for focussing various fields using the built-in browser mechanism, so the key combo was Ctrl-Shift-. Those didn't get much use, and we took them out. But if we use JS-based key capture, we could use individual keys without modifiers, and we could do more than just focus fields. I'd like one for "scroll to and focus comment field". I might use that a lot. It would be nice to have one for "don't scroll at all, but CC me, and beep to tell me you've done it". Perhaps "add attachment"? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From justdave at bugzilla.org Thu Mar 27 02:48:43 2014 From: justdave at bugzilla.org (Dave Miller) Date: Wed, 26 Mar 2014 22:48:43 -0400 Subject: (re)introducing Mark =?ISO-8859-1?Q?C=F4t=E9=2C_Bugzilla_Ass?= =?ISO-8859-1?Q?istant_Project_Lead?= Message-ID: <5333918B.5010205@bugzilla.org> I've invited Mark C?t? to step up to fill the Assistant Project Lead position vacated by Simon Green two months ago. He'll also be taking on a role as a "Community Coordinator" to try to step up efforts to make new community members feel welcome and encourage more involvement. You probably all know him most recently for his leadership in the project to move our source control from bzr to git. He's a long-time developer outside of Bugzilla, and has been heavily involved with Bugzilla the last year or so via his participation in maintaining bugzilla.mozilla.org. He's mainly been in the role of a project manager for BMO, and that's really what Bugzilla needs right now. We haven't had a really good project manager or community coordinator in a long time, and the state of the project kinda shows it. In another first (in recent history), "approval" rights aren't initially coming with the job. Any patches that need commit approval can continue to be directed towards Byron (glob) or myself (justdave). I've had a long-standing policy of trying to avoid having the entire senior leadership team being employed by Mozilla, in order to try to keep it a real community project and not feel like it was being controlled by Mozilla, but the reality is that nobody else from outside of Mozilla has been involved enough to step into this kind of role in the recent past, and it's better to have it filled and get things done than to leave it vacant and let the project stagnate even further. If he's an effective community builder, that problem will probably solve itself eventually. We're going to try to set up another real-time project meeting soon either on IRC or Air Mozilla or in Google Hangouts again (that wasn't too bad when we did it) so we can regroup on where we are and where we plan to go. Expect to be hearing from Mark on that soon. For more information about Mark, see his Mozillians profile at https://mozillians.org/en-US/u/mcote/ or his LinkedIn profile at https://www.linkedin.com/profile/view?id=27908882 or find him in the #bugzilla channel on IRC as mcote. -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mcote at mozilla.com Fri Mar 28 01:11:44 2014 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Thu, 27 Mar 2014 21:11:44 -0400 Subject: (re)introducing Mark =?ISO-8859-1?Q?C=F4t=E9=2C_Bugzilla_?= =?ISO-8859-1?Q?Assistant_Project_Lead?= In-Reply-To: References: Message-ID: Thanks for the intro, Dave! As Dave said, I've been managing the BMO (bugzilla.mozilla.org) team for a while (almost two years, actually!) and so I have a vested interest in Bugzilla's future. I also understand that BMO is not the same as Bugzilla; the BMO team has been good (long before my time) at upstreaming changes that have general benefit, creating extensions where use cases are specific but still applicable outside of Mozilla, and committing directly to BMO core where neither is the case. I don't plan on changing that. I feel that Bugzilla is at a critical point right now; while to the outside it may appear that development has slowed down, we're modernizing various bits of it in parallel, both on the front end and back end, and I think it's ripe for a renaissance. I want to get that word out and show the world that Bugzilla is still an excellent choice for issue tracking (and if you're like Mozilla, much more! ;). I want to get more people excited and build up to a critical mass. Just a few of things I want to do include * laying out our exact plan for the 5.0 release, in particular where community members can help out * developing a road map for the future * cataloging extensions * growing the community, finding space for everyone, be they testers, doc-writers, coders, graphic designers, or anything else that Bugzilla needs * getting regular feedback, coordination, and alignment through public meetings In the very short term, that means I'll be doing a bunch of updates to our website and a blog post or two to reflect Bugzilla's current situation and the work that has been done recently. That should set the stage for a good discussion at a public meeting, which I'd like to schedule for mid-April, perhaps (throwing out a date at random) some time on or around Wednesday, April 16th, perhaps at 14:00 UTC. Google Hangout seemed to work. We can always rotate the time and/or medium to maximize participation. Mark (mcote) _______________________________________________ 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 Fri Mar 28 03:59:21 2014 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Thu, 27 Mar 2014 23:59:21 -0400 Subject: (re)introducing Mark =?ISO-8859-1?Q?C=F4t=E9=2C_Bugzilla_?= =?ISO-8859-1?Q?Assistant_Project_Lead?= In-Reply-To: References: Message-ID: <77SdnYrHNYkKbqnOnZ2dnUVZ_sKdnZ2d@mozilla.org> Let me shift the proposed one week to April 23rd to accommodate some folks who can't make the week earlier. Nothing set in stone yet. Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla