Learn how three Java Specification

Learn how three Java Specification Requests will create opportunities and deliver benefits to the JCP community.

The Java platform grows and is maintained by the Java community through the Java Community Process (JCP) program. This effort is represented by Java Specification Requests (JSRs) through the JCP program.

Each JSR represents the persistent work of a team leader (Spec Lead) and a small group of dedicated developers (Expert Group members). The entire team is often an average of a dozen Java specialists. There are over three hundred JSRs that bring the Java platform to life.

The JCP is governed by the Executive Committee (EC) and entire process is overseen and guided by the Java Program Management Office (PMO) Chair and Staff.

JCP.next is a series of three JSRs designed to bring significant benefits to all of the above, and more.

Streamlining the Process for Maximum Progress
Patrick Curran is the Director of the PMO, Chair of the JCP, and the Spec Lead for all three JCP.next JSRs (JSR 348, JSR 355 and JSR 358). "These JSRs modify the JCP's processes - the Process Document and Java Specification Participation Agreement (JSPA) - and will apply to all new JSRs and to future Maintenance Releases of existing JSRs for all Java platforms," he says.

Curran explains that the first - JCP.next.1, known formally as JSR 348, Towards a new version of the Java Community Process - was completed and put into effect in October 2011 as JCP 2.8. It created a small number of simple but important changes to make the JCP's process more transparent and to enable broader participation. "We're already seeing the benefits of these changes as new and existing JSRs adopt the new requirements."

The second - JSR 355, Executive Committee Merge, is also Final. It contains revisions to the JCP Process Document (version 2.9) and the EC Standing Rules (version 2.2). These changes went into effect following the 2012 EC Elections in November, detailed on the Elections page.

The third - JSR 358, A major revision of the Java Community Process, was approved in July 2012 by the EC. This JSR is in its beginning stages and will modify the Java Specification Participation Agreement (JSPA) as well as the Process Document, and will address a large number of complex legal issues.

Next: Let's take a closer look at the two JCP.next JSRs that have reached Final Release before exploring the "major revision" challenges ahead.

JCP 2.8: Know What We're Doing, Get Involved, Improve the Platform and Process
The three themes of JSR 348, transparency, participation and agility, are designed to give the JCP community, Java community, and public a way to observe and be more involved with the Java platform's development and governance. At the same time, it creates a process for the JCP that both encourages and enforces rapid platform progress through agility.

Transparency Provides Visibility
JSR 348's transparency provisions require EG members and Spec Leads to conduct their work in the open and address all public comments. In years previous, an EG's process and progress was hidden, or at best difficult to find.

Now, JSR 2.8 EGs post all of their activities and decisions on a public mailing list. Their deliberations are copied to a public Observer Alias, and all of their documents (meeting agendas and minutes, task lists, and working drafts) are published in the JCP Document Archive.

They must also track the JSR's issues in a publicly available issue tracker such as JIRA, or others, such as Bugzilla.

The EC has already adopted the changes it is required to make, for example, publishing its minutes and meeting materials and providing a public mailing list for community feedback.

JCP 2.8 also requires the EC to hold semiannual public-participation teleconference meetings

Heather VanCura, manager of the PMO, confirms that they're on track: "In 2012 we had our first semiannual meetings in June and November, a one-hour teleconference with questions submitted by the community. Our live JavaOne gathering in October was the second event, and one-hour teleconference in November makes three public meetings in one year. These meetings are open to all JCP members, and anyone can suggest topics for discussion."

Finally, there are new transparency provisions that give the community more visibility into licensing, TCK testing and the election process.

Curran and his EG wanted to create an example of the new, "expected" transparency mode in developing and maintaining the JSR itself. They created a public java.net project where anyone can follow and participate in the work, now in Maintenance.

"Overall, I think these transparency changes have been received well," says VanCura. "We're seeing the vast majority of Spec Leads and EGs migrating to JCP 2.8 or above and using java.net or other collaborative sites. Most have started java.net projects, they have complied with the rules for establishing aliases for the public, and they're using online issue trackers as well."

In December 2012, the JCP introduced a new communication channel where the public can comment on the progress of any JSR's EG. In addition, the community will have a method to evaluate and provide feedback on EG and EC transparency. That information will help the JCP Program Management Office conduct transparency audits for each JSR and work with the Spec Lead to make improvements in their process. The audit results will also be available to the public.

Participation Builds Community
Active participation is encouraged, streamlined, and designed to support transparency in the JCP program.

For example, now, any JCP member can make a request to be added to an EG, and the Spec Lead must respond to the request. Both the request and the EG response are posted publicly. Similarly, Spec Leads are required to post notification of any EG member changes, and the reasons for adding, losing or removing a member. There is also an enforceable process for dealing with Spec Leads, EG members, and EC members who don't actively participate.

The EC members in particular can lose voting privileges for missing meetings. They can lose their EC seat altogether if the miss five meetings in a row, or two-thirds of the meetings in a twelve-month period. In 2012, three EC members "forfeited" their seats under the new rules of JCP 2.8: Samsung, ST Telecom and RIM.

"EC members have to take the time to be informed before they come to the table to make decisions, and it requires a large commitment on their part," says VanCura. "We don't want people holding a seat on the EC if they aren't participating advancing the platform. As the EC process has become more transparent to the community, our members have learned to see who on the EC is contributing, attending, and making progress. They now have the tools to track and evaluate JSR progress, and they are using them to voice their opinions."

In the October 2013 election, all current ratified and elected EC members will have to run for re-election, and the community at large will be watching their progress closely.

Agility Propels Progress
In 2009 the JCP instituted an informal process labeling a JSR "inactive" if it shows no activity in any 12-month period. It was simply labeled, with no consequences or means of progress enforcement. Now, JCP 2.8 introduces means of progress enforcement: Time-outs for JSRs. The time-out provisions require EGs to reach various stages of the process within a defined time period, or face the possibility of being shut down.

Learn more about JSR 348 in the JCP 2.8 Ushers in a New Era of Complete Transparency article.

One Java Platform, One JCP EC
The second JSR in JCP.next is JSR 355, Executive Committee Merge. It combined the two edition-centric ECs (ME and SE/EE) into one EC to govern the entire Java platform as one body, and all JSR ballots will be voted on by one EC.

The PMO's VanCura says, "As the previously distinct editions of Java converge to become 'one Java,' it has increasingly made sense to merge the two committees into one governance body that reflects that natural evolution."

The Initial Results Are Promising, and We Have a Long Way to Go
"It's encouraging to see so many Spec Leads embrace JCP 2.8 and 2.9," says VanCura. "Most of the in-process JSRs have migrated to the new process - only a handful haven't done so yet. And all new JSRs must follow the provisions of JCP 2.8 or JCP 2.9."

"So far, JCP 2.8 has made it easier for JCP members and the public to observe and participate in the work of the EGs," she says. "And it has made transparency the default, expected mode of operation, rather than an anomaly."

The Final Step is the Largest One: Defining the Future of JCP for the Long Term
The first two of the three JCP.next JSRs were completed in a reasonable time and efficient manner. Now, with the new unified EC in place, the community turns its focus to the third and most complex installment: JSR 358: A major revision of the Java Community Process.

It will revise long-standing agreements between the JCP and its members to shape the way the JCP is governed for the foreseeable future.

What's Involved
JSR 358 will modify both the Java Specification Participation Agreement (JSPA) and the JCP Process Document to address a large number of complex issues, many of them postponed from JSR 348.

For these reasons the EG members expect to spend a considerable amount of time working on it. Several members estimate, "at least a year, and probably more."

Patrick says, "We have to make sure JSR 358 is absolutely right, and fulfills all of the legal needs." He says, "The attorneys representing each of the stakeholders will be involved to finalize the agreements in both documents. It will take a while."

The current list of revisions to be made includes:

The role of independent implementations (those not derived from the Reference Implementation)
Licensing and open source
Implementing full transparency
Compatibility policy and TCK re

Hasil (Bahasa Indonesia) 1:

Pelajari bagaimana tiga Jawa spesifikasi permintaan akan menciptakan peluang dan memberikan manfaat kepada masyarakat JCP.Java platform tumbuh dan dikelola oleh masyarakat Jawa melalui program Java komunitas proses (JCP). Upaya ini diwakili oleh Jawa spesifikasi permintaan (JSRs) melalui JCP program.JSR masing-masing mewakili pekerjaan gigih pemimpin tim (mengarah Spec) dan sekelompok kecil berdedikasi pengembang (anggota kelompok ahli). Seluruh tim ini sering rata-rata selusin Jawa spesialis. Ada lebih dari tiga ratus JSRs yang membawa Java platform untuk hidup.JCP diatur oleh Komite Eksekutif (EC) dan seluruh proses ini diawasi dan dipandu oleh kursi Java Program manajemen kantor (PMO) dan staf.JCP.next adalah serangkaian tiga JSRs dirancang untuk membawa manfaat yang signifikan untuk semua hal di atas, dan banyak lagi. Merampingkan proses untuk kemajuan maksimumPatrick Curran adalah Direktur dari PMO, Ketua JCP, dan Spec memimpin untuk semua JSRs JCP.next tiga (JSR 348, JSR 355 dan JSR 358). "JSRs ini memodifikasi JCP proses - proses dokumen dan Perjanjian Partisipasi spesifikasi Jawa (JSPA) - dan akan berlaku untuk semua JSRs baru dan masa depan rilis pemeliharaan yang ada JSRs untuk semua platform Java," katanya.Curran menjelaskan bahwa pertama - JCP.next.1, dikenal secara resmi sebagai JSR 348, menuju sebuah versi baru dari proses masyarakat Jawa - selesai dan dimasukkan ke dalam efek pada Oktober 2011 sebagai JCP 2.8. Ini menciptakan sejumlah kecil perubahan sederhana namun penting untuk membuat proses JCP lebih transparan dan untuk memungkinkan partisipasi lebih luas. "Kita sudah melihat manfaat dari perubahan ini sebagai baru dan yang ada JSRs mengadopsi persyaratan baru."Kedua - JSR 355, menggabungkan Komite Eksekutif, juga Final. Ini berisi revisi JCP proses dokumen (versi 2.9) dan EC berdiri aturan (versi 2.2). Perubahan ini pergi ke efek setelah pemilu EC 2012 pada bulan November, rinci pada halaman pemilu.Ketiga - 358 JSR, revisi besar dari proses masyarakat Jawa, telah disetujui dalam Juli 2012 oleh EC. JSR ini dalam tahap awal akan memodifikasi Perjanjian Partisipasi spesifikasi Jawa (JSPA) serta dokumen proses dan akan alamat sejumlah isu-isu hukum yang kompleks.Next: Mari kita melihat lebih dekat pada JSRs JCP.next dua yang telah mencapai Final Release sebelum menjelajahi "revisi besar" tantangan di depan. JCP 2.8: Tahu apa kita melakukan, terlibat, meningkatkan Platform dan prosesTiga tema JSR 348, transparansi, partisipasi dan ketangkasan, dirancang untuk memberikan JCP komunitas, masyarakat Jawa, dan publik dengan cara mengamati dan menjadi lebih terlibat dengan Java platform pembangunan dan pemerintahan. Pada saat yang sama, itu menciptakan suatu proses untuk JCP yang mendorong dan memberlakukan cepat platform kemajuan melalui ketangkasan. Transparansi menyediakan visibilitasKetentuan-ketentuan transparansi JSR 348 memerlukan EG anggota dan Spec mengarah untuk melakukan pekerjaan mereka di tempat terbuka dan alamat semua komentar publik. Dalam tahun-tahun sebelumnya, EG proses dan kemajuan adalah tersembunyi, atau paling sulit untuk menemukan.Sekarang, JSR 2.8 EGs posting semua kegiatan dan keputusan pada milis umum. Pertimbangannya akan disalin ke Alias pengamat umum, dan semua dokumen mereka (Agenda Rapat dan menit, daftar tugas, dan konsep kerja) yang diterbitkan di JCP dokumen Arsip.Mereka juga harus melacak masalah-masalah JSR dalam pelacak isu yang tersedia untuk umum seperti JIRA, atau orang lain, seperti Bugzilla.EC telah sudah mengadopsi perubahan-perubahan yang dibutuhkan untuk membuat, misalnya, penerbitan yang menit dan bahan Rapat dan menyediakan daftar mailing umum untuk umpan balik masyarakat.JCP 2,8 juga memerlukan EC untuk mengadakan pertemuan semesteran umum-partisipasi teleconferenceHeather VanCura, manajer hotel PMO, menegaskan bahwa mereka berada di trek: "tahun 2012 kami memiliki pertemuan semesteran pertama kami di bulan Juni dan November, teleconference satu jam dengan pertanyaan yang diajukan oleh masyarakat. Kami JavaOne hidup yang berkumpul di Oktober adalah peristiwa kedua, dan satu jam teleconference di November membuat tiga pertemuan umum dalam satu tahun. Pertemuan ini terbuka untuk semua anggota JCP, dan siapa pun dapat menyarankan topik untuk diskusi."Akhirnya, ada ketentuan-ketentuan transparansi baru yang memberikan masyarakat visibilitas lebih perizinan, TCK pengujian dan proses pemilihan.Curran dan EG nya ingin membuat sebuah contoh dari mode baru, "diharapkan" transparansi dalam mengembangkan dan mempertahankan JSR itu sendiri. Mereka menciptakan sebuah proyek java.net umum dimana siapa saja dapat mengikuti dan berpartisipasi dalam pekerjaan, sekarang dalam pemeliharaan."Secara keseluruhan, saya pikir perubahan transparansi ini telah diterima dengan baik," kata VanCura. "Kami melihat mayoritas Spec memimpin dan EGs bermigrasi ke JCP 2.8 atau di atas dan menggunakan java.net atau situs lain kolaboratif. Sebagian sudah mulai proyek java.net, mereka mematuhi aturan untuk mendirikan alias untuk publik, dan mereka menggunakan pelacak isu online juga."Pada Desember 2012, JCP memperkenalkan saluran komunikasi baru dimana masyarakat dapat mengomentari kemajuan EG JSR apapun. Selain itu, masyarakat akan memiliki sebuah metode untuk mengevaluasi dan memberikan umpan balik mengenai EG dan EC transparansi. Informasi tersebut akan membantu JCP Program manajemen kantor melakukan audit transparansi bagi setiap JSR dan bekerja dengan Spec menyebabkan untuk membuat perbaikan dalam proses mereka. Hasil audit juga akan tersedia untuk umum. Partisipasi membangun masyarakatPartisipasi aktif mendorong, efisien, dan dirancang untuk mendukung transparansi dalam JCP program.Sebagai contoh, sekarang, setiap anggota JCP dapat membuat permintaan yang akan ditambahkan ke EG, dan memimpin Spec harus menanggapi permintaan. Permintaan dan respon EG diumumkan kepada publik. Demikian pula, Spec mengarah diminta untuk mengirim pemberitahuan perubahan anggota EG, dan alasan untuk menambahkan, kehilangan atau menghapus anggota. Ada juga sebuah proses dilaksanakan untuk berurusan dengan Spec mengarah, EG anggota dan anggota EC yang tidak aktif.Anggota EC khususnya dapat kehilangan hak suara untuk pertemuan yang hilang. Mereka bisa kehilangan kursi EC mereka sama sekali jika miss lima pertemuan di baris, atau dua-pertiga dari pertemuan di periode 12 bulan. Pada 2012, tiga anggota EC "hangus" kursi mereka di bawah aturan baru JCP 2.8: Samsung, ST Telecom dan RIM."Anggota EC harus meluangkan waktu untuk diberitahu sebelum mereka datang ke meja untuk membuat keputusan, dan itu memerlukan komitmen besar pada bagian mereka," kata VanCura. "Kami tidak ingin orang-orang yang memegang kursi di EC jika mereka tidak berpartisipasi memajukan platform. Sebagai proses EC telah menjadi lebih transparan kepada masyarakat, anggota kami telah belajar untuk melihat yang pada EC berkontribusi, hadir, dan membuat kemajuan. Mereka sekarang memiliki alat untuk melacak dan mengevaluasi kemajuan JSR, dan mereka menggunakan mereka untuk menyuarakan pendapat mereka."Dalam pemilihan Oktober 2013, Semua anggota saat ini disahkan dan dipilih EC akan harus menjalankan untuk Re-Pemilu, dan masyarakat pada umumnya akan mengawasi kemajuan mereka erat. Kelincahan mendorong kemajuanTahun 2009 JCP melembagakan proses informal pelabelan JSR "aktif" jika hal itu menunjukkan tidak ada kegiatan dalam setiap periode 12 bulan. Itu hanya dicap, tanpa konsekuensi atau berarti penegakan kemajuan. Sekarang, 2,8 JCP memperkenalkan cara penegakan kemajuan: Time-Out untuk JSRs. Ketentuan time-out memerlukan EGs untuk mencapai berbagai tahap proses dalam periode waktu yang ditetapkan, atau menghadapi kemungkinan ditutup.Pelajari lebih lanjut tentang JSR 348 di JCP 2.8 Usher dalam Era Baru transparansi lengkap artikel. Satu Platform Java, satu JCP ECJSR kedua di JCP.next adalah JSR 355, menggabungkan Komite Eksekutif. Ini digabungkan ECs edisi-sentris dua (saya dan SE EE) menjadi satu EC untuk mengatur seluruh platform Java sebagai satu tubuh, dan semua JSR pemungutan akan memberikan suara pada oleh satu EC.The PMO's VanCura says, "As the previously distinct editions of Java converge to become 'one Java,' it has increasingly made sense to merge the two committees into one governance body that reflects that natural evolution." The Initial Results Are Promising, and We Have a Long Way to Go"It's encouraging to see so many Spec Leads embrace JCP 2.8 and 2.9," says VanCura. "Most of the in-process JSRs have migrated to the new process - only a handful haven't done so yet. And all new JSRs must follow the provisions of JCP 2.8 or JCP 2.9.""So far, JCP 2.8 has made it easier for JCP members and the public to observe and participate in the work of the EGs," she says. "And it has made transparency the default, expected mode of operation, rather than an anomaly." The Final Step is the Largest One: Defining the Future of JCP for the Long TermThe first two of the three JCP.next JSRs were completed in a reasonable time and efficient manner. Now, with the new unified EC in place, the community turns its focus to the third and most complex installment: JSR 358: A major revision of the Java Community Process.It will revise long-standing agreements between the JCP and its members to shape the way the JCP is governed for the foreseeable future.What's InvolvedJSR 358 will modify both the Java Specification Participation Agreement (JSPA) and the JCP Process Document to address a large number of complex issues, many of them postponed from JSR 348.For these reasons the EG members expect to spend a considerable amount of time working on it. Several members estimate, "at least a year, and probably more."Patrick says, "We have to make sure JSR 358 is absolutely right, and fulfills all of the legal needs." He says, "The attorneys representing each of the stakeholders will be involved to finalize the agreements in both documents. It will take a while."The current list of revisions to be made includes:The role of independent implementations (those not derived from the Reference Implementation)Licensing and open sourceImplementing full transparencyCompatibility policy and TCK re