We use Trac, but it’s a heavily customized version — and the dashboard is the result of a collaboration between our program manager George Puckett and YUILibrary.com’s lead developer, Dav Glass.

Dav has put this work up on his GitHub account, so you can download it and try it out of you’d like:

http://github.com/davglass

-Eric

The project dashboard page at http://yuilibrary.com is very impressive. What project management system is the site built on?

I should have mentioned, also: Yes, YUI2 and YUI3 live happily together. Check out this example for more details:

http://developer.yahoo.com/yui/3/examples/yui/yui-compat.html

-Eric

The widget framework will go GA in 3.1.0, which should be out in Q4, and that’s when you’ll see widgets starting to appear in earnest. It will probably take two additional release cycles to get all of the most important widgets ported over, but we’ll go as fast as we can. See the project page for roadmap details:

http://yuilibrary.com/projects/yui3/roadmap
http://yuilibrary.com/projects/yui3/dashboard

-Eric

My apps tend to be fairly widget-heavy, using YUI widgets like TabView and Carousel extensively – when can we expect to see the bulk of YUI2 widgets ported over?

Thanks!

On the topic of skins, I agree with Kamil. The Sam skin is good to get started, but for commercial projects, more wow is required. However, may I suggest some kind of skin configuration tool, or at least better documentation for the skin and the files. After all, even if YUI came with a Wow-skin (!), in all likelihood one would want to modify the skin such as adapt to the client’s corporate design etc. In a RAD scenario, fumbling with the Sam CSS files (or a future Wow…) is a bit of a pain for developers who are not HTML wizards.

That’s my 2 cents…

And maybe I was to quick to judge, because I also feel that Sam is great for regular websites – very susceptible to small customizations, accessible and optimized (and neither is true for Ext JS), but still… it doesn’t have this wow effect that’s so useful when developing a prototype / demo app. In my opinion non technical people (not only) tend to think: simple skin (like Sam) => simple application; attractive/eye-catching, so different than websites out there skin => advanced application.

And don’t get me wrong – I still believe in “less is more”, KISS and stuff, but “attractive/eye-catching” doesn’t necessary equal to bloated (especially Ext JS skin is not bloated imo (although generated DOM tree is)).

Don’t you think?