jQuery UI Management: Please read!
Hi guys,
this email is addressed to all developers who are currently participating on the development of jQuery UI or want to. John and I decided we will need a better structural organization in the future, to handle the growth of the project.
jQuery UI 1.0 was a pretty wild release - the code is still rough, many cross-browser issues and (at least from my point of view) a lot of communication problems, that became manifest in modules that were not ready for inclusion, complete rewrites, duplicate code and code that was never requested. That's fine for a first release - but it will be stricter organized from now on to achieve a certain quality level (read: production ready).
The following will change:
<font size="4">
Management<font size="2">
The group is not enough to plan releases, tasks and team members. We have set up a new basecamp account for the management of jQuery, jQuery UI and the Evangelism team. I have invited most of the current developers (I will add more of you later). You should have received an email.
In case you're wondering, this is what a "current developer" is:
To become a active UI developer, you must have either 1.) modules written or (heavily) modified by you in a current release, or 2.) modules that are definitely planned for a next UI release in current development. John and I will decide if a module is needed / will make it into a next release (this also means all the stuff that's not in
1.0 and checked in). Please understand and accept this step - there are multiple reasons for it (read "complete rewrites, duplicate code and code that was never requested").
Basecamp is a very easy groupware solution - watch the demo videos and you will be fine.
<font size="4">Communication
<font size="2">
There was a serious lack of communication lately. I have sometimes been guilty myself not entering IRC, but what really made me wonder (read: upset) were people not using the project controlling sheet at all and people who didn't write anything about progress / problems to me/John.
In order to solve this problem, I want every UI developer to think about their issues and problems. Ask yourself the question "Could Paul need this information?", and you will be surprised how often you can answer this question with yes. So please, use the to-do tool in basecamp to track your issues (so others can see it) and write me mails (I don't bite).
<font size="4">1.1
<font size="2">
I have set up a date for the next release (the bugfix release 1.0.1 doesn't count), it's October 22th for now. This might slightly differ, but it should give you something to work with. The following aspects are important for the next release:
</font></font></font></font></font></font><ul><li>Cross-Browser compatibility in all released modules (IE 6.0+, FF 1.5+, Safari 2.0+, Opera 9.0+)</li><li>Better layout/colors in <a href="http://jquery.com">jquery.com
</a>'s wiki</li><li>Tutorials</li><li>Restructuring UI into patterns, removing effects</li></ul>Yes, we will be removing effects, read below.
<font size="4">jQuery FX</font>
In order to maintain a good structure within jQuery projects, we decided to move all effects to their own separate library, called jQuery FX. There is only this decision for now, nothing to see yet. However, the first release is also planned together with UI
1.1. I'll keep you updated.
So thank you for all your support so far, I really appreciate it. I'm looking forward to a lot of new cool modules.
More from me soon!
Paul
<font size="4"><font size="2">
<font size="4"><font size="2"><font size="4"><font size="2"></font></font></font></font></font></font>
--
--
Paul Bakaus
this email is addressed to all developers who are currently participating on the development of jQuery UI or want to. John and I decided we will need a better structural organization in the future, to handle the growth of the project.
jQuery UI 1.0 was a pretty wild release - the code is still rough, many cross-browser issues and (at least from my point of view) a lot of communication problems, that became manifest in modules that were not ready for inclusion, complete rewrites, duplicate code and code that was never requested. That's fine for a first release - but it will be stricter organized from now on to achieve a certain quality level (read: production ready).
The following will change:
<font size="4">
Management<font size="2">
The group is not enough to plan releases, tasks and team members. We have set up a new basecamp account for the management of jQuery, jQuery UI and the Evangelism team. I have invited most of the current developers (I will add more of you later). You should have received an email.
In case you're wondering, this is what a "current developer" is:
To become a active UI developer, you must have either 1.) modules written or (heavily) modified by you in a current release, or 2.) modules that are definitely planned for a next UI release in current development. John and I will decide if a module is needed / will make it into a next release (this also means all the stuff that's not in
1.0 and checked in). Please understand and accept this step - there are multiple reasons for it (read "complete rewrites, duplicate code and code that was never requested").
Basecamp is a very easy groupware solution - watch the demo videos and you will be fine.
<font size="4">Communication
<font size="2">
There was a serious lack of communication lately. I have sometimes been guilty myself not entering IRC, but what really made me wonder (read: upset) were people not using the project controlling sheet at all and people who didn't write anything about progress / problems to me/John.
In order to solve this problem, I want every UI developer to think about their issues and problems. Ask yourself the question "Could Paul need this information?", and you will be surprised how often you can answer this question with yes. So please, use the to-do tool in basecamp to track your issues (so others can see it) and write me mails (I don't bite).
<font size="4">1.1
<font size="2">
I have set up a date for the next release (the bugfix release 1.0.1 doesn't count), it's October 22th for now. This might slightly differ, but it should give you something to work with. The following aspects are important for the next release:
</font></font></font></font></font></font><ul><li>Cross-Browser compatibility in all released modules (IE 6.0+, FF 1.5+, Safari 2.0+, Opera 9.0+)</li><li>Better layout/colors in <a href="http://jquery.com">jquery.com
</a>'s wiki</li><li>Tutorials</li><li>Restructuring UI into patterns, removing effects</li></ul>Yes, we will be removing effects, read below.
<font size="4">jQuery FX</font>
In order to maintain a good structure within jQuery projects, we decided to move all effects to their own separate library, called jQuery FX. There is only this decision for now, nothing to see yet. However, the first release is also planned together with UI
1.1. I'll keep you updated.
So thank you for all your support so far, I really appreciate it. I'm looking forward to a lot of new cool modules.
More from me soon!
Paul
<font size="4"><font size="2">
<font size="4"><font size="2"><font size="4"><font size="2"></font></font></font></font></font></font>
--
--
Paul Bakaus
Topic Participants
Paul Bakaus
John Resig
digitalspaghetti
littlecooldude
rektide