From dylan at mozilla.com Mon Apr 25 19:55:53 2016 From: dylan at mozilla.com (Dylan Hardison) Date: Mon, 25 Apr 2016 15:55:53 -0400 Subject: Bugzilla on GitHub and Dual-Life Extensions Message-ID: (tl;dr: Bugzilla git primary is going to be github. git.mozilla.org for bugzilla development is going away; Useful extensions are getting their own repos.) For a variety of reasons, the primary git repository for Bugzilla will be moving to github. Our code is already on github (mirrored) but in the coming weeks we'll need to update our remotes to push to it as well. As it would happen, a benefit arises from this: Currently there are several very popular extensions whose canonical home is ... the bmo repo. This is not desirable for a number of reasons: 1) If someone contributes an improvement (rather than a fix), that improvement has to be vetted both on the principal "is this what is best for the extension?" and *also* "Will this break bmo?" As a result, improvements to extensions linger with very long review times (this is but one reason reviews take a long time) 2) It points people at the bmo repo. The BMO repo is not consumable. It's possibly (and encouraged, I think) to take ideas/code from it, but anyone trying to run it that isn't Mozilla is burdening themselves with a lot of arbitrary decisions and it will almost always end in tears. 3) Sometimes the BMO team breaks compatibility in an extension, as has happened with EditComments (as I recall). 4) The commit history of the extensions is littered with the rest of the commit history in BMO Thus, since we are moving to primary git hosting to github anyway, I am going to split out (as a start) InlineHistory, EditComments, and SecureMail as git repositories under https://github.com/bugzilla. These will be history-complete with the ones on BMO, but because of the magic of git-filter-branch the history will be useful. Astute observers will note that extensively used extensions should be core'd -- included in the regular bugzilla codebase. Those observers are correct, but doing so is often a non-trivial amount of work. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Tue Apr 26 13:04:51 2016 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 26 Apr 2016 14:04:51 +0100 Subject: Bugzilla on GitHub and Dual-Life Extensions In-Reply-To: References: Message-ID: <0b587690-04ad-49af-6c24-e3f86bab4986@mozilla.org> On 25/04/16 20:55, Dylan Hardison wrote: > Thus, since we are moving to primary git hosting to github anyway, I am > going to split out (as a start) > InlineHistory, EditComments, and SecureMail as git repositories under > https://github.com/bugzilla. You know that InlineHistory and SecureMail already have their own repos, on git.mozilla.org? https://git.mozilla.org/?p=bugzilla/extensions/InlineHistory.git;a=tree https://git.mozilla.org/?p=bugzilla/extensions/SecureMail.git;a=tree Along with 12-15 other extensions? See the http://git.mozilla.org/ front page. SecureMail is fairly up-to-date with the BMO version; not sure about InlineHistory. But these seem like better starting points? Gerv From dylan at mozilla.com Tue Apr 26 13:51:00 2016 From: dylan at mozilla.com (Dylan Hardison) Date: Tue, 26 Apr 2016 09:51:00 -0400 Subject: Bugzilla on GitHub and Dual-Life Extensions In-Reply-To: <0b587690-04ad-49af-6c24-e3f86bab4986@mozilla.org> References: <0b587690-04ad-49af-6c24-e3f86bab4986@mozilla.org> Message-ID: I'd want to see what the differences between them lie. I know there was no canonical repo for EditComments. Moving all of those to github will certainly increase their visibility. As will finishing migrating the bugzilla.org site something more people can work with. On Tue, Apr 26, 2016 at 9:04 AM, Gervase Markham wrote: > On 25/04/16 20:55, Dylan Hardison wrote: > > Thus, since we are moving to primary git hosting to github anyway, I am > > going to split out (as a start) > > InlineHistory, EditComments, and SecureMail as git repositories under > > https://github.com/bugzilla. > > You know that InlineHistory and SecureMail already have their own repos, > on git.mozilla.org? > > https://git.mozilla.org/?p=bugzilla/extensions/InlineHistory.git;a=tree > https://git.mozilla.org/?p=bugzilla/extensions/SecureMail.git;a=tree > > Along with 12-15 other extensions? See the http://git.mozilla.org/ front > page. > > SecureMail is fairly up-to-date with the BMO version; not sure about > InlineHistory. But these seem like better starting points? > > Gerv > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Wed Apr 27 14:42:52 2016 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 27 Apr 2016 15:42:52 +0100 Subject: Bugzilla Meeting for April Message-ID: Hi everyone, The next Bugzilla meeting will be today, Wednesday, at 21:00 UTC: http://arewemeetingyet.com/UTC/2016-04-27/21:00/Bugzilla%20Meeting https://wiki.mozilla.org/Bugzilla:Meetings has the agenda; feel free to add items. See you there :-) Gerv _______________________________________________ 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 Wed Apr 27 17:46:54 2016 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 27 Apr 2016 18:46:54 +0100 Subject: Bugzilla Meeting for April In-Reply-To: References: Message-ID: On 27/04/16 15:42, Gervase Markham wrote: > The next Bugzilla meeting will be today, Wednesday, at 21:00 UTC: Aargh! Sorry! 21:00 UK time. We even discussed this. Doh. http://arewemeetingyet.com/London/2016-04-27/09:00/Bugzilla%20Meeting Gerv _______________________________________________ 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 Thu Apr 28 15:49:44 2016 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 28 Apr 2016 16:49:44 +0100 Subject: Meeting notes for April Message-ID: <1bKdnThYpNCFrL_KnZ2dnUU7-I3NnZ2d@mozilla.org> The notes from last night's Bugzilla Meeting are here: https://wiki.mozilla.org/Bugzilla:Meetings:2016-04-27 Gerv _______________________________________________ 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 Fri Apr 29 21:39:43 2016 From: cedric.corazza at gmail.com (=?UTF-8?Q?C=c3=a9dric_Corazza?=) Date: Fri, 29 Apr 2016 23:39:43 +0200 Subject: Meeting notes for April In-Reply-To: <1bKdnThYpNCFrL_KnZ2dnUU7-I3NnZ2d@mozilla.org> References: <1bKdnThYpNCFrL_KnZ2dnUU7-I3NnZ2d@mozilla.org> Message-ID: Le 28/04/2016 17:49, Gervase Markham a ?crit : > The notes from last night's Bugzilla Meeting are here: > https://wiki.mozilla.org/Bugzilla:Meetings:2016-04-27 > > Gerv > Hi, I could not attend this meeting. I am a bit puzzled about "the Github migration plans". Although I do not contribute to the code, I do understand the contributors' concerns about using Github. There are alternatives for it, like Gitlab: https://about.gitlab.com/ which has more or less the same features than Github, than can be hosted on Mozilla infrastructure. In fact, I had to create a gitlab instance in my enterprise because developers created a "wild" repo on github. The burden is the initial configuration setup. Then, it is all about backupping the MySQL/MariaDB dumps and upgrading when new versions are released. The Community Edition support LDAP, CAS and database (local) identification. 10 mn hacking allows to customize the homepage (this feature is included in Enterprise Edition in a more easier way). I did not check yet, but I guess there should be providers that propose this kind of hosting The Community Edition is licensed under MIT License. Voil?! 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 dkl at mozilla.com Sat Apr 30 21:18:45 2016 From: dkl at mozilla.com (David Lawrence) Date: Sat, 30 Apr 2016 17:18:45 -0400 Subject: Meeting notes for April In-Reply-To: References: <1bKdnThYpNCFrL_KnZ2dnUU7-I3NnZ2d@mozilla.org> Message-ID: <57252135.7050701@mozilla.com> The issue is that, as I understand it, Mozilla is downsizing on the amount of VCS systems it has to maintain. So IT is trying to decommission the internal git server and is not really interested in putting another one in its place and maintain that instead (gitlab). So if we move to github, we have a stable place to host the upstream Bugzilla as well as BMO itself. dkl On 04/29/2016 05:39 PM, C?dric Corazza wrote: > Le 28/04/2016 17:49, Gervase Markham a ?crit : >> The notes from last night's Bugzilla Meeting are here: >> https://wiki.mozilla.org/Bugzilla:Meetings:2016-04-27 >> >> Gerv >> > Hi, > > I could not attend this meeting. I am a bit puzzled about "the Github > migration plans". > Although I do not contribute to the code, I do understand the > contributors' concerns about using Github. > There are alternatives for it, like Gitlab: https://about.gitlab.com/ > which has more or less the same features than Github, than can be hosted > on Mozilla infrastructure. > In fact, I had to create a gitlab instance in my enterprise because > developers created a "wild" repo on github. > The burden is the initial configuration setup. Then, it is all about > backupping the MySQL/MariaDB dumps and upgrading when new versions are > released. The Community Edition support LDAP, CAS and database (local) > identification. 10 mn hacking allows to customize the homepage (this > feature is included in Enterprise Edition in a more easier way). > I did not check yet, but I guess there should be providers that propose > this kind of hosting > The Community Edition is licensed under MIT License. > Voil?! > > 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 > - > To view or change your list settings, click here: > -- David Lawrence dkl at mozilla.com