From lpsolit at gmail.com  Sun Aug 19 01:14:36 2012
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Sun, 19 Aug 2012 03:14:36 +0200
Subject: YUI2, YUI3, jQuery, something else? What to choose?
Message-ID: <50303DFC.8060306@gmail.com>

Hi everybody,

You probably know that Bugzilla currently uses YUI2 as its JS library,
but shiny new features are now only implemented in YUI3, which looks
like a very different library compared to YUI2. This means that if we
want to use new features implemented in YUI3, we basically have to
rewrite everything from scratch. As jQuery is a very popular library, I
wondered if it wouldn't be a better alternative than moving to YUI3.
More popular = potentially more contributors. Either that, or we could
stay on YUI2, but this means it would be a bigger pain to migrate in the
future once YUI2 is declared dead.

I talked with dkl and glob on IRC this week, and we plan to branch for
Bugzilla 4.4 soon, and open the new development cycle for Bugzilla 4.6.
The main focus for 4.4 was to improve WebServices, but I would like the
main focus for 4.6 to be the User Interface. More and more people are
complaining that Bugzilla looks old and is slow, while for instance
GitHub looks great, cleaner, faster, modern, easier to use, etc... The
question is not whether they are true or not (not everybody agree on
this point, and I don't want a debate here as we are all biased), but
the question is what can we do to improve the User Experience.

Nobody can object that the UI almost didn't change since the Bugzilla
2.x era, modulo some improvements here and there. The UI was built with
no JavaScript in mind, and I think this was a good thing. But now
finding the right threshold seems important in 2012, and AJAX and our
JSON-RPC interface could help us improve things now.


So, what's your opinion on the choice of the JS library? The tracking
bug on bmo is: https://bugzilla.mozilla.org/show_bug.cgi?id=453268


LpSolit


From dmarshal at yahoo-inc.com  Sun Aug 19 01:32:03 2012
From: dmarshal at yahoo-inc.com (David Marshall)
Date: Sat, 18 Aug 2012 18:32:03 -0700
Subject: YUI2, YUI3, jQuery, something else? What to choose?
In-Reply-To: <50303DFC.8060306@gmail.com>
Message-ID: <CC558E36.500F0%dmarshal@yahoo-inc.com>



On 8/18/12 6:14 PM, "Fr?d?ric Buclin" <lpsolit at gmail.com> wrote:
>
>
>So, what's your opinion on the choice of the JS library? The tracking
>bug on bmo is: https://bugzilla.mozilla.org/show_bug.cgi?id=453268
>

To whatever extent I can speak for Yahoo!, I can say that we'd like
bugzilla.org to stay with YUI. I think it's been a mutually beneficial
relationship to date, and we'd like it to continue.

Bugzilla (through the filter of our own internal instance) has played a
big role in YUI's development. If my recollections are correct, the
DataTable widget was created so that we could use it.

I've taken bug 453268, and I've just sent email to both the YUI teams and
our open-source group about how we can best help you.



From dmarshal at yahoo-inc.com  Sun Aug 19 21:05:59 2012
From: dmarshal at yahoo-inc.com (David Marshall)
Date: Sun, 19 Aug 2012 14:05:59 -0700
Subject: Launchpad Branch for YUI3
Message-ID: <CC56A347.501C6%dmarshal@yahoo-inc.com>

Hi all,

See https://bugzilla.mozilla.org/show_bug.cgi?id=453268 for the full
details.

I've created a branch on launchpad.net for work on migrating Bugzilla from
YUI 2 to YUI 3. I have the blessing of Yahoo!'s open-source folks, and
I'll be trying to interest other folks at Yahoo! in helping out.

https://code.launchpad.net/~dmarshal/bugzilla/yui3


Unfortunately, I don't have any timetable for this. We've been doing a lot
of reorganizing (that is mostly orthogonal to the arrival of Marissa Mayer
as our CEO), so I am busier than ever with working on new code and new
bugs.

If a sufficient number of folks show interest in collaborating on this, I
will try to set up a workshop (or similar) with the YUI team at our
fabulous Sunnyvale HQ.

Shameless plug:

I'm new to Javascript libraries overall all, thus I have almost no
experience with doing any of the sorts of things that YUI3 helps anyone
do. Therefore, it's a good thing I have a copy "YUI 3 Cookbook," written
by my colleague Evan Goer!

http://goer.org/YUI/



From jochen.wiedmann at gmail.com  Tue Aug 21 13:22:04 2012
From: jochen.wiedmann at gmail.com (Jochen Wiedmann)
Date: Tue, 21 Aug 2012 15:22:04 +0200
Subject: YUI2, YUI3, jQuery, something else? What to choose?
In-Reply-To: <50303DFC.8060306@gmail.com>
References: <50303DFC.8060306@gmail.com>
Message-ID: <CAF8HOZL+m6qMvzUYQSt1yPF-i58nW+Ksa7qnn7ZU04dVsOasxA@mail.gmail.com>

Given your questions background, I'd like to reformulate the question:
- Which project can be expected to have the more stable API?
- Which project has the more fitting license? So that we can easily
distribute the related files?

Jochen


On Sun, Aug 19, 2012 at 3:14 AM, Fr?d?ric Buclin <lpsolit at gmail.com> wrote:
> Hi everybody,
>
> You probably know that Bugzilla currently uses YUI2 as its JS library,
> but shiny new features are now only implemented in YUI3, which looks
> like a very different library compared to YUI2. This means that if we
> want to use new features implemented in YUI3, we basically have to
> rewrite everything from scratch. As jQuery is a very popular library, I
> wondered if it wouldn't be a better alternative than moving to YUI3.
> More popular = potentially more contributors. Either that, or we could
> stay on YUI2, but this means it would be a bigger pain to migrate in the
> future once YUI2 is declared dead.
>
> I talked with dkl and glob on IRC this week, and we plan to branch for
> Bugzilla 4.4 soon, and open the new development cycle for Bugzilla 4.6.
> The main focus for 4.4 was to improve WebServices, but I would like the
> main focus for 4.6 to be the User Interface. More and more people are
> complaining that Bugzilla looks old and is slow, while for instance
> GitHub looks great, cleaner, faster, modern, easier to use, etc... The
> question is not whether they are true or not (not everybody agree on
> this point, and I don't want a debate here as we are all biased), but
> the question is what can we do to improve the User Experience.
>
> Nobody can object that the UI almost didn't change since the Bugzilla
> 2.x era, modulo some improvements here and there. The UI was built with
> no JavaScript in mind, and I think this was a good thing. But now
> finding the right threshold seems important in 2012, and AJAX and our
> JSON-RPC interface could help us improve things now.
>
>
> So, what's your opinion on the choice of the JS library? The tracking
> bug on bmo is: https://bugzilla.mozilla.org/show_bug.cgi?id=453268
>
>
> LpSolit
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=jochen.wiedmann at gmail.com>



-- 
In other words: what could be seen as a socially debilitating failure
of character can certainly work to your advantage too. (Linus
Torvalds, but the use in the signature tells something about me as
well.)


From lpsolit at gmail.com  Thu Aug 30 22:38:53 2012
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Fri, 31 Aug 2012 00:38:53 +0200
Subject: Bugzilla trunk is now 4.5. Branch for 4.4 created
Message-ID: <503FEB7D.4050707@gmail.com>

Hi all,

Now that we released Bugzilla 4.3.3, I have created a branch for
Bugzilla 4.4:

 bzr://bzr.mozilla.org/bugzilla/4.4

We are going to stabilize the code on this branch to release 4.4rc1,
hopefully in October. If you find regressions or bugs, please report
them to us before we release 4.4rc1 (ideally). I will also start QA
testing for this branch soon.

This means that the trunk is now 4.5 (which will become 4.6 or 5.0 next
time we branch again):

 bzr://bzr.mozilla.org/bugzilla/trunk

One major change in 4.5 is that Bugzilla now requires Perl 5.10.1 or
newer. Perl 5.8.x is no longer supported. If you have major changes you
would like to see in Bugzilla (front-end, backend, API), now is a good
time as we are very early in the new development cycle. Patches and new
contributors are welcome! ;)


LpSolit