Announcement of the creation of the jQuer Standard Group

^{Preface translator. The jQuery Standards Team phrase in indirect cases will be translated by the unusual jQuer Standardization Group phrase: the jQuery group of standards is not appropriate because it’s not about any jQuery standards, but about the impact on those standards They are not related to the jQuery library itself, but to other mainstream technologies. For the name “יהודה”, the translation option “Judas” was chosen as the most traditional (in perfect agreement with the opinion of the brainplus expressed in March last year ). The word "process" is translated as "process" in order not to inadvertently encroach upon the ambiguity of the original source.}

Today, we are happy to announce that a new subgroup has been created in the jQuery development team called the jQuery Standards Team; Its goal is to give web developers the right to vote in the standardization process.

Introduction

We all know how important web standards are. They help ensure the efficiency of the code that we write in various technological environments, people with different capabilities, and most importantly - in all browsers.

But nevertheless, how often do we all feel that our voices, our proposals and ideas are heard by the groups that are responsible for adopting these standards? In fact, although many of us would like to see some changes, lack of time and long formalities prevent us from contributing to the discussion of standards, involvement in writing specifications, and participating in meetings about future features. This is what hampers the web developers' right to vote.
')
There is another problem: those who want to influence the process often feel that the impact of participating in a specific thread on the mailing list is not significant, because the Web community is very fragmented. Browser providers are very active in all of these lists, and in most of the discussion threads, a huge amount of internal basic knowledge is assumed. Browser builders usually have a place to confer and discuss problem areas of interest to them, and web developers won't do that, except for occasional meetings at conferences.

The jQuery project intends to change these circumstances: we want you to have the right to vote in choosing the form that the future of the Web takes.

The jQuery Standards Team

The jQuer Standardization Group has three main objectives:

• Be representatives of the web development community (especially jQuery consumers) on standardization committees (such as W3C and TC39) with the intention to improve existing and emerging standards to better fit their web development needs.
  
• Be representatives of the web development community (and especially jQuery consumers) in front of browser builders, with the intention of helping browser builders in choosing the standards that need to be implemented first, and in making proofs of concept.
  
• To help the jQuery project to assimilate new standards and browser innovations properly.

This is a milestone of great changes in the power of feedback and the impact of the web development community on standardization committees and on the standards themselves. By lowering the threshold of entry, which hinders proposals and objections to existing implementations of standards to be heard, we hope to encourage more developers to interact with standardizers to ensure that browser creators participate in this process.

The jQuery team will be managed by the members of the jQuery team - Judah Katz and Paul Irish. Jude and Paul have actively interacted with standardization committees and browser vendors in a given role for many years, and their personal work at SproutCore and Chrome Developer Relations provides them with additional perspectives that will prove useful in defending community opinion.



Perhaps you are wondering why our group has earned the honor to represent the interests of the wider web development community. Since jQuery is used by a significant percentage of sites ( more than 50% from 10,000 high-rating sites), we feel well about what problems and challenges one usually encounters, what difficulties of existing implementations have to be circumvented. Since jQuery is very focused on manipulating DOM, our library always serves as a good source of information about known problems in implementations and the current best ways to solve them.

Although the current group consists mainly of jQuery development participants, we would like to involve as many web developers as possible in this group with a genuine interest in standards and specifications. By the end of the day (October 24, 2011), our group intends to assist in identifying web developers who are interested in the process, and to provide all of us with a forum for the interchange of issues, ideas, areas of interest. We believe that our work together can help all of us in improving the Web.

Taking part

If you are interested in taking part in the work of the jQuer Standardization Group, the easiest way is to subscribe to a group in Google Groups . Following the example of other jQuery development teams, there will be publicly available meetings on the # jquery-meeting channel at freenode (we will inform you later) to discuss what is the most effective way for the group to work in promoting the needs of the web development community.

You may have already seen Paul's blog. “ What feature would improve the web? "; if you left a comment there, you already took part;)

You can also leave messages and comments about problems in standards and specifications using the issue-reporting tool ("Issues") in the official repository of our group on Github. In doing so, try to identify problems in those standards or specifications that either exist or are now being proposed for adoption. And here is an excellent example of one of these problems .

We wish to collect well-defined, clearly described problems of the Web ecosystem and defend the necessary improvements to standardizers and browser builders. Real-world problems will be tagged with appropriate labels (for example, “W3C”, “TC39”, browser names, etc.), and sent, wherever and as far as possible, to a suitable committee of standardizers or browser developers — so This will not have to take care.

Conclusion

By creating such a new forum, we hope to provide the right to vote to millions of web developers who wanted to participate in this process, but did not have the simplest opportunity for that. Please let us know your views on this group, as we hope to improve it to the utmost. We look forward to your comments, suggestions and ideas about both the group and the standardization process!