This document summarizes the Java Community Process (JCP) and how it manages the development of Java standards. It discusses why standards are important, describes the different Java specifications and platforms, and explains how the JCP works through Java Specification Requests (JSRs) that are developed by Expert Groups. It provides details on JSR stages, governance, transparency, and how to get involved. It also discusses current events like Java SE 7/8 and Java EE 7 JSRs, and opportunities for more participation from India and Asia.
The document provides information about how individuals and organizations can get involved with and participate in the Java Community Process (JCP) to help develop Java technology specifications, reference implementations, and compatibility test suites. It outlines different levels of participation including becoming a member, joining an expert group, or becoming a specification lead. It encourages participation through Java User Groups and describes how JUGs can get involved by adopting Java Specification Requests.
Drive yourself, community with adopts and jcp to professionalismMohamed Taman
This is an overview presentation about JCP organization, its roles, process, and output. With a detailed explanation of each group role and their output. In addition, to encourage community to participate in JCP, and being valuable members and experience input to the community.
Agenda:
http://egjug.org/page/java_ee_7_8_and_beyond
The document provides an overview of the Java Community Process (JCP) and how it develops standards for the Java platform. It discusses how JSRs are submitted and go through various stages of review, approval, and maintenance. It also describes ongoing efforts to evolve the JCP through a series of JSRs called JCP.next that aim to modify the legal and governance aspects of the process defined in the Java Specification Participation Agreement.
This document discusses Oracle's role as the steward of Java and the Java Community Process (JCP). It provides an overview of Java's history and widespread adoption. It describes how the JCP works, including how Java specifications are developed collaboratively through JSRs. It outlines reforms to the JCP through the JCP.next initiatives to improve participation and governance. It encourages developers to get involved in the JCP through their Java User Groups or by adopting JSRs.
This document provides an overview of Java and the Java Community Process (JCP). It notes that Java has over 9 million developers worldwide and is used extensively across many industries. It then discusses Oracle's role in acquiring Sun Microsystems in 2010 and revitalizing Java development. The document outlines the open and collaborative nature of the JCP for developing Java specifications through Java Specification Requests (JSRs). It encourages participation in the JCP through activities like commenting on draft specifications, testing implementations, and joining expert groups.
The document provides information about how individuals and organizations can get involved with and participate in the Java Community Process (JCP) to help develop Java technology specifications, reference implementations, and compatibility test suites. It outlines different levels of participation including becoming a member, joining an expert group, or becoming a specification lead. It encourages participation through Java User Groups and describes how JUGs can get involved by adopting Java Specification Requests.
Drive yourself, community with adopts and jcp to professionalismMohamed Taman
This is an overview presentation about JCP organization, its roles, process, and output. With a detailed explanation of each group role and their output. In addition, to encourage community to participate in JCP, and being valuable members and experience input to the community.
Agenda:
http://egjug.org/page/java_ee_7_8_and_beyond
The document provides an overview of the Java Community Process (JCP) and how it develops standards for the Java platform. It discusses how JSRs are submitted and go through various stages of review, approval, and maintenance. It also describes ongoing efforts to evolve the JCP through a series of JSRs called JCP.next that aim to modify the legal and governance aspects of the process defined in the Java Specification Participation Agreement.
This document discusses Oracle's role as the steward of Java and the Java Community Process (JCP). It provides an overview of Java's history and widespread adoption. It describes how the JCP works, including how Java specifications are developed collaboratively through JSRs. It outlines reforms to the JCP through the JCP.next initiatives to improve participation and governance. It encourages developers to get involved in the JCP through their Java User Groups or by adopting JSRs.
This document provides an overview of Java and the Java Community Process (JCP). It notes that Java has over 9 million developers worldwide and is used extensively across many industries. It then discusses Oracle's role in acquiring Sun Microsystems in 2010 and revitalizing Java development. The document outlines the open and collaborative nature of the JCP for developing Java specifications through Java Specification Requests (JSRs). It encourages participation in the JCP through activities like commenting on draft specifications, testing implementations, and joining expert groups.
How the JCP Works & Adopt-a-Program Update for Paraguay JUGHeather VanCura
The document discusses the Java Community Process (JCP) program, which is the open process for developing and revising Java technology specifications, reference implementations, and technology compatibility kits. It provides an overview of how the JCP works, including the roles of specification leads, expert groups, and the executive committee in developing specifications. It encourages participation in the JCP through various levels of involvement and describes benefits such as influencing technologies and gaining knowledge.
The document summarizes a presentation given at FOSDEM 2013 about the Java Community Process (JCP). It discusses improvements to transparency, participation, and agility in the JCP through a series of JSRs (JSR 348, 355, 358). It highlights the Adopt-a-JSR initiative where Java user groups work on JSRs, and over 20 JUGs have adopted 23 JSRs. The presentation encourages further community involvement in the JCP.
The document discusses the history and evolution of the Java Community Process (JCP) over the past 20 years. It notes that the JCP started in 1995 and has grown to include over 1,000 members developing over 350 Java technology specifications. It outlines ongoing efforts to further open the JCP through initiatives like JCP.Next and proposals to broaden membership classes and remove barriers to participation.
This document summarizes a presentation about the Java Community Process (JCP) and how Java User Groups (JUGs) and individuals can get involved. It discusses changes to make the JCP more transparent and participatory through three JSRs (JSR 348, 355, 358). It encourages JUGs and individuals to join the JCP, participate in expert groups, provide feedback on specifications, help with reference implementations, and adopt JSRs through the "Adopt-a-JSR" initiative.
As we celebrate 15 year anniversary of the JCP, a retrospective look at the past 15 years and a look into the future and plans being made together with the Java developer community.
The document discusses the Java Community Process (JCP) and Java Specification Requests (JSRs), describing the JCP's role in developing Java technology standards, the JSR lifecycle and artifacts, and providing details on JSR 331 which aims to define a Java constraint programming API to model and solve constraint problems. It also gives an overview of the JCP organization, executive committees, roles of spec leads and expert groups, and participation and governance processes for members.
This document discusses Oracle's role as the steward of Java and the Java Community Process (JCP). It provides background on Java's history and development. The JCP is described as an open, collaborative process for developing Java specifications through Java Specification Requests (JSRs). Key points include that Oracle recognizes Java's value comes from its open, collaborative development; Oracle's competitors actively participate in the JCP; and the JCP is working to further open participation through reforms like JCP.Next. The document encourages participation in the JCP and adopting JSRs through Java user groups.
The document summarizes the Java Community Process (JCP) and its role in the future of Java. It discusses how the JCP facilitates collaborative development of Java specifications through Java Specification Requests (JSRs). It also outlines recent JSRs and releases, as well as planned improvements to the JCP through increased transparency, membership changes, and other reforms. The presentation encourages participation in the JCP to help shape Java's future.
This document discusses ways for individuals and groups like Java User Groups (JUGs) to get involved in the Java Community Process (JCP) and help shape the future of Java standards. It outlines different levels of participation from becoming a member to leading expert groups and specifications. The Adopt-a-JSR program encourages JUGs to collaborate on JSRs by performing tasks like testing, documentation, and issue tracking. Over 20 JUGs from around the world have adopted 23 JSRs through activities like hack days and applications development. Getting involved can help advance careers and skills while contributing to Java.
This document provides an overview of the Java Community Process (JCP) and ways to get involved in developing Java standards. It discusses the history and organization of the JCP. Key points include that the JCP uses Java Specification Requests (JSRs) to develop specifications through expert groups. It encourages participation through various roles like commenting, writing documentation, or leading a JSR. The document also summarizes recent Java releases and outlines how to test code for compatibility with Java 9.
The document discusses the Java Community Process (JCP) and efforts to make it more open and inclusive to the broader Java community. Key points include:
- The JCP is the open process for developing and revising Java technology specifications, reference implementations, and test compatibility kits.
- Over 350 Java technology specifications are in development through the JCP, with two-thirds having reached a final release.
- Recent JCP.next efforts through JSRs 348, 355, 358, and 364 aimed to broaden JCP membership and make the process more transparent.
- Initiatives like Adopt-a-JSR and involvement in OpenJDK encourage greater community participation in influencing and implementing Java
This document summarizes Heather VanCura's presentation on participating in the Java Community Process (JCP) and the evolution of Java. It discusses the history of Java and the JCP since its creation by Sun Microsystems in 1995. It outlines how Oracle has infused new energy into Java since acquiring Sun in 2010, including new platform revisions and reforms to the JCP process. The presentation encourages participation in the JCP through Java User Groups, adopting Java Specification Requests, contributing to open source projects, and more. It provides resources for getting involved in the future of Java.
Advance your Career and Help Define Java’s FutureHeather VanCura
This document discusses ways for developers to get involved in shaping the future of Java through participation in the Java Community Process (JCP). It outlines the JCP's structure and processes for developing Java specifications through JSRs. It encourages developers to get involved by commenting on specifications, trying implementations, evangelizing technologies, and participating in hack days and open source projects. Participation can help developers advance their careers through skills growth, visibility, and giving back to the community.
Join the Java Evolution GIDS Bangalore & PuneHeather VanCura
The Java Community Process (JCP) is key to the evolution of Java technology. This session emphasizes the value of transparency and participation in the JCP program, through both Java User Groups (JUGs), and through the Adopt-a-JSR program, the grass roots, community led and developed program to empower Java developers around the world to make a contribution to Java technology. Find out how to become an active participant in advancing the Java platform - JSRs for Java Enterprise Edition (Java EE) 8 and Java Standard Edition (Java SE) 9 are being developed now. This session discusses the transparency that enables participation in the JCP program and how to get involved through the Adopt-a-JSR program. You will also hear about some upcoming changes to the Java Specification Request (JSR) process itself through the JCP.next effort, and learn how you can get involved. Come with your questions/suggestions, and leave with the motivation and information you need in order to become an active participant in advancing the Java platform now and in the future.
This document summarizes Heather VanCura's presentation about participating in the evolution of Java. It discusses the history and governance of Java through the Java Community Process (JCP). It encourages participation in the JCP to help shape new Java specifications through activities like Adopt-a-JSR, contributing to OpenJDK, and participating in hack days and other community events. The goal is to involve more developers globally in the open development of Java standards.
This document discusses ways for developers to get involved in shaping the future of Java through participation in the Java Community Process (JCP). It outlines how individuals and organizations can join the JCP as members and get involved in Java Specification Requests (JSRs) by adopting JSRs, providing feedback, writing sample code, and attending hack days. The JCP aims to develop Java through an open and collaborative process.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
How the JCP Works & Adopt-a-Program Update for Paraguay JUGHeather VanCura
The document discusses the Java Community Process (JCP) program, which is the open process for developing and revising Java technology specifications, reference implementations, and technology compatibility kits. It provides an overview of how the JCP works, including the roles of specification leads, expert groups, and the executive committee in developing specifications. It encourages participation in the JCP through various levels of involvement and describes benefits such as influencing technologies and gaining knowledge.
The document summarizes a presentation given at FOSDEM 2013 about the Java Community Process (JCP). It discusses improvements to transparency, participation, and agility in the JCP through a series of JSRs (JSR 348, 355, 358). It highlights the Adopt-a-JSR initiative where Java user groups work on JSRs, and over 20 JUGs have adopted 23 JSRs. The presentation encourages further community involvement in the JCP.
The document discusses the history and evolution of the Java Community Process (JCP) over the past 20 years. It notes that the JCP started in 1995 and has grown to include over 1,000 members developing over 350 Java technology specifications. It outlines ongoing efforts to further open the JCP through initiatives like JCP.Next and proposals to broaden membership classes and remove barriers to participation.
This document summarizes a presentation about the Java Community Process (JCP) and how Java User Groups (JUGs) and individuals can get involved. It discusses changes to make the JCP more transparent and participatory through three JSRs (JSR 348, 355, 358). It encourages JUGs and individuals to join the JCP, participate in expert groups, provide feedback on specifications, help with reference implementations, and adopt JSRs through the "Adopt-a-JSR" initiative.
As we celebrate 15 year anniversary of the JCP, a retrospective look at the past 15 years and a look into the future and plans being made together with the Java developer community.
The document discusses the Java Community Process (JCP) and Java Specification Requests (JSRs), describing the JCP's role in developing Java technology standards, the JSR lifecycle and artifacts, and providing details on JSR 331 which aims to define a Java constraint programming API to model and solve constraint problems. It also gives an overview of the JCP organization, executive committees, roles of spec leads and expert groups, and participation and governance processes for members.
This document discusses Oracle's role as the steward of Java and the Java Community Process (JCP). It provides background on Java's history and development. The JCP is described as an open, collaborative process for developing Java specifications through Java Specification Requests (JSRs). Key points include that Oracle recognizes Java's value comes from its open, collaborative development; Oracle's competitors actively participate in the JCP; and the JCP is working to further open participation through reforms like JCP.Next. The document encourages participation in the JCP and adopting JSRs through Java user groups.
The document summarizes the Java Community Process (JCP) and its role in the future of Java. It discusses how the JCP facilitates collaborative development of Java specifications through Java Specification Requests (JSRs). It also outlines recent JSRs and releases, as well as planned improvements to the JCP through increased transparency, membership changes, and other reforms. The presentation encourages participation in the JCP to help shape Java's future.
This document discusses ways for individuals and groups like Java User Groups (JUGs) to get involved in the Java Community Process (JCP) and help shape the future of Java standards. It outlines different levels of participation from becoming a member to leading expert groups and specifications. The Adopt-a-JSR program encourages JUGs to collaborate on JSRs by performing tasks like testing, documentation, and issue tracking. Over 20 JUGs from around the world have adopted 23 JSRs through activities like hack days and applications development. Getting involved can help advance careers and skills while contributing to Java.
This document provides an overview of the Java Community Process (JCP) and ways to get involved in developing Java standards. It discusses the history and organization of the JCP. Key points include that the JCP uses Java Specification Requests (JSRs) to develop specifications through expert groups. It encourages participation through various roles like commenting, writing documentation, or leading a JSR. The document also summarizes recent Java releases and outlines how to test code for compatibility with Java 9.
The document discusses the Java Community Process (JCP) and efforts to make it more open and inclusive to the broader Java community. Key points include:
- The JCP is the open process for developing and revising Java technology specifications, reference implementations, and test compatibility kits.
- Over 350 Java technology specifications are in development through the JCP, with two-thirds having reached a final release.
- Recent JCP.next efforts through JSRs 348, 355, 358, and 364 aimed to broaden JCP membership and make the process more transparent.
- Initiatives like Adopt-a-JSR and involvement in OpenJDK encourage greater community participation in influencing and implementing Java
This document summarizes Heather VanCura's presentation on participating in the Java Community Process (JCP) and the evolution of Java. It discusses the history of Java and the JCP since its creation by Sun Microsystems in 1995. It outlines how Oracle has infused new energy into Java since acquiring Sun in 2010, including new platform revisions and reforms to the JCP process. The presentation encourages participation in the JCP through Java User Groups, adopting Java Specification Requests, contributing to open source projects, and more. It provides resources for getting involved in the future of Java.
Advance your Career and Help Define Java’s FutureHeather VanCura
This document discusses ways for developers to get involved in shaping the future of Java through participation in the Java Community Process (JCP). It outlines the JCP's structure and processes for developing Java specifications through JSRs. It encourages developers to get involved by commenting on specifications, trying implementations, evangelizing technologies, and participating in hack days and open source projects. Participation can help developers advance their careers through skills growth, visibility, and giving back to the community.
Join the Java Evolution GIDS Bangalore & PuneHeather VanCura
The Java Community Process (JCP) is key to the evolution of Java technology. This session emphasizes the value of transparency and participation in the JCP program, through both Java User Groups (JUGs), and through the Adopt-a-JSR program, the grass roots, community led and developed program to empower Java developers around the world to make a contribution to Java technology. Find out how to become an active participant in advancing the Java platform - JSRs for Java Enterprise Edition (Java EE) 8 and Java Standard Edition (Java SE) 9 are being developed now. This session discusses the transparency that enables participation in the JCP program and how to get involved through the Adopt-a-JSR program. You will also hear about some upcoming changes to the Java Specification Request (JSR) process itself through the JCP.next effort, and learn how you can get involved. Come with your questions/suggestions, and leave with the motivation and information you need in order to become an active participant in advancing the Java platform now and in the future.
This document summarizes Heather VanCura's presentation about participating in the evolution of Java. It discusses the history and governance of Java through the Java Community Process (JCP). It encourages participation in the JCP to help shape new Java specifications through activities like Adopt-a-JSR, contributing to OpenJDK, and participating in hack days and other community events. The goal is to involve more developers globally in the open development of Java standards.
This document discusses ways for developers to get involved in shaping the future of Java through participation in the Java Community Process (JCP). It outlines how individuals and organizations can join the JCP as members and get involved in Java Specification Requests (JSRs) by adopting JSRs, providing feedback, writing sample code, and attending hack days. The JCP aims to develop Java through an open and collaborative process.
Similar to JCP: The JCP and the future of Java by Heather VanCura, Manager, JCP Program @ JavaOne Hyderabad (20)
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
16. How we do it
• Java Specification Requests (JSRs)
– A JSR is a single version of a Java specification.
– JSRs are led by a community member (the Spec Lead), with
a group of interested members (the Expert Group) helping
with the day-to-day decisions and work.
– Any community member can submit and lead a JSR.
• JSR Deliverables
– Each EG must deliver at the end of the JSR lifecycle:
• The Specification
• The Reference Implementation (RI)
• The Technology Compatibility Kit (TCK)
16 May 2011
17. The compatibility triangle
• Specification
In the specification Can you build an
unambiguous? implementation?
Technology Reference
Compatibility Kit Implementation
Is the TCK correct?
Does the RI conform?
17 May 2011
20. Governance
• Java Specification Participation Agreement (JSPA)
– A legal contract between members and Oracle.
– Addresses Intellectual Property (IP) grants and the terms
under which the spec, RI, and TCK should be licensed.
– http://www.jcp.org/aboutJava/communityprocess/JSPA2.pdf.
• JCP 2: Process Document
– Defines the governance of the organization.
– Defines the processes that are used to submit define, develop,
review, approve, and maintain specifications.
– Defines the obligations to produce an RI and TCK, and to
define a test challenge process.
– http://jcp.org/en/procedures/jcp2.
20 May 2011
22. Roles
• JCP Chair
– Leads the organization and manages the PMO.
• Program Management Office (PMO)
– Manages day-to-day operations of the organization.
• Executive Committees
– Define JCP governance, processes, and contractual terms of
membership.
– Vote on JSRs at defined stages through the process.
• Expert Groups
– Create JSRs (write the spec, develop the RI and TCK).
• Members
– Review specs, may participate in Expert Groups, vote in
Executive Committee elections.
22 May 2011
23. The Executive Committees
• Two Executive Committees:
– One for Java ME and one for Java SE and Java EE combined.
• Each EC has 16 members.
• Oracle has a permanent seat on each EC.
• 10 of the other 15 seats are ratified by Oracle.
– Oracle nominates a candidate; the entire JCP membership
approves via ballot.
• The remaining 5 seats are elected (any JCP member may
nominate themselves.)
• Yearly elections reconfirm or replace one-third of the members.
• ECs meet ~monthly by phone, 3 times a year face-to-face.
• EC meeting minutes are public.
– See http://jcp.org/en/resources/EC_summaries.
23 May 2011
24. Executive Committee responsibilities
• Review and vote on all JSRs associated with their EC.
• Evolve the JSPA and the Process Document.
– The JSPA and Process Document are modified through the
JSR process itself.
– The Executive Committees serve as the Expert Group for
JSRs that make these changes; the Chair is the Spec Lead.
– JSR 99 defined the JSPA, JSR 215 defined the Process Doc.
– Two new JSRs to evolve the JSPA and Process Doc will be
filed soon (JCP.next.)
• Represent their own interests to the JCP and the JCP to the
developer and user community.
• Advise the PMO.
24 May 2011
25. Current Executive Committee membership
• Java ME EC
– Stefano Andreani, Aplix, AT&T, CableLabs, IBM,
Nokia, Oracle, RIM, Samsung, Sean Sheedy,
Siemens, SK Telecom, T-Mobile, TOTVS,
Vodafone.
– One vacancy recently filled by a Special Election
(Alex Terrazas).
• Java SE/EE EC
– Credit Suisse, Eclipse, Ericsson, Fujitsu, Google,
HP, IBM, Intel, Werner Keil, Oracle, Red Hat, SAP,
Vmware.
– Three vacancies recently filled by a Special
Election (Goldman Sachs, SouJava, London Java
Community).
25 May 2011
26. The Spec Lead
• The individual or institutional owner and driver of a JSR.
– Recruits and organizes the activities of the Expert Group.
– Responsible for delivering the Spec, RI, and TCK.
• Intellectual Property rights to the technology
incorporated in the JSR accrue to the Spec Lead.
– Subject to obligations incurred under the JSPA.
• The Spec Lead is free to define the terms under which the
RI, and TCK will be licensed.
– Subject to obligations incurred under the JSPA.
• Oracle is the Spec Lead for the three existing Platforms:
Java ME, Java SE, and Java EE.
26 May 2011
27. The Expert Group
• The Expert Group is recruited and led by the Spec Lead.
– All members of the JCP are eligible to join.
– Participation by all interested parties is encouraged and
desirable.
– The EG works as a team to define the JSR and to develop
the Spec, RI, and TCK.
• The EG is free to define its own working style.
– When and how often it meets, how it makes decisions...
• Transparency is strongly encouraged.
– EGs must explain their transparency strategy:
• Public aliases, public issue list, Wikis, blogs...
– EGs must respond publicly to comments.
27 May 2011
28. The membership
• Anyone can join.
• Total membership is approximately 1500.
• 3700 registered users at jcp.org (not affliliated with a
member).
• Fees:
– Java Licensees: free.
– Individuals: free
– Java User Groups: free.
– Non-profit organizations: $2K/year.
– Commercial organizations: $5K/year.
28 May 2011
29. Who are the members?
• Membership distribution by type:
– 77% individual.
– 21% corporate.
– 2% non-profit.
• Membership distribution by location:
– 50% North America
– 32% Europe and the Russian Federation
– 13% Asia and the Middle East
– 5% South America
29 May 2011
31. JSR Submission
• Identify the submitters, the Specification Lead(s), and the
initial members of the Expert Group.
• Describe the proposed specification and the reasons for
developing it.
• Identify the target Platform(s).
• Estimate the development schedule.
• Describe the working model the Expert Group will adopt,
and how it will involve the community and the public.
• Identify preexisting documents, technology descriptions,
or implementations that might be used as a starting point.
• Publish the licensing terms for the Spec, RI, and TCK.
31 May 2011
32. JSR Approval Ballot
• JSR proposals are published on the JCP website.
• JCP members, the Executive Committees, and the public
review and comment.
• JCP members may request to join the Expert Group
during this period.
• The Executive Committee(s) vote on the JSR during the
final two weeks of the review period.
• If the JSR is voted down, submitters have 14 days to
revise and resubmit for a second vote; if this fails the
JSR is closed.
32 May 2011
33. Expert Group formation
• Expert Group formation begins when the JSR is approved.
• Members request to join the EG through an online form.
• No size limit; Spec Leads should ensure that all interested
parties are represented, but should keep the group small
enough that it will be able to function efficiently.
• Members may be added at any time, subject to the
agreement of the existing membership.
• EG decides its mode of operation (communication
mechanisms, meeting schedules, etc.)
– Transparency and community involvement are strongly
encouraged.
33 May 2011
34. Early Draft
• The Expert Group's first deliverable is the Early Draft.
– Provides the JCP membership and the public with a draft
that is detailed enough to generate useful feedback.
• No fixed deadline for generating the draft – EGs should
take as long as they need (but no longer!)
• Early Draft is published for review on the JCP website.
– Review period is typically 30 days but may be longer.
• No ballot at this stage – the purpose is to gather feedback.
• EGs may choose to revise the draft and resubmit if
feedback indicates that significant changes need to be
made.
– OK to iterate through several Early Draft reviews.
34 May 2011
35. Public Review
• Spec should be relatively complete before Public Review.
• Expert Group should also be developing the RI and TCK
while working on the spec.
• Spec is published for review on the JCP website.
– Review period is 30 – 90 days (the EG decides how long).
• All public comments should be considered and addressed.
• The Public Draft Specification Approval Ballot takes place
during the final 7 days of the review
• If the ballot fails, the EG has 30 days to resubmit for a
Reconsideration Ballot.
– If this ballot fails, the JSR is closed.
35 May 2011
36. Proposed Final Draft
• The EG submits a Proposed Final Draft of the spec to the
PMO.
– This should incorporate and address feedback from the Public
Review.
• Spec is posted on the website for public download.
36 May 2011
37. Final Approval and Release
• The EG prepares the Final Draft of the spec and completes
the RI and TCK.
– The TCK must meet quality and coverage goals.
– The RI must pass the TCK.
– A test appeals process must be defined.
– Final RI and TCK licensing terms must be published.
• The EC has two weeks to review these materials and to cast
their votes in the Final Approval Ballot.
• If the ballot fails the EG has 30 days to resubmit for a
Reconsideration Ballot; if that fails, the JSR is closed.
• Approved JSRs are posted for Final Release and may then be
implemented commercially.
37 May 2011
38. Maintenance
• Spec Leads are expected to make a long-term commitment
to revise and update the spec, RI, and TCK.
• Spec Lead typically takes on the role of Maintenance
Lead.
– Gathers Proposed changes, deciding which to Accept and
which to Defer, publishing these on the JCP website.
• 30-day public Maintenance Review period (no ballot
unless EC members intervene to request items be
deferred).
• RI and TCK must be synchronized with spec changes.
– Maintenance Release is final when this is completed.
• More significant changes (beyond minor clarifications of
the spec) require a new JSR.
38 May 2011
39. Summary of JSR Stages
• JAB: JSR Approval Ballot - Mandatory - 2 weeks.
• EDR: Early Draft Review - Mandatory - 30/45/60/90 days.
• PR: Public Review - Mandatory - 30/45/60/90 days.
• PRB: Public Review Ballot – Mandatory - 7 days.
• PFD: Proposed Final Draft - Mandatory - no time frame.
• FAB: Final Approval Ballot - Mandatory - 2 weeks.
• FR: Final Release - Mandatory.
• MR: Maintenance Review - Optional - 30/45/60/90 days.
• MREL: Maintenance Release - Optional.
Each stage must be completed before the Expert Group moves on
to the next.
39 May 2011
41. Open Source processes
• Half of all currently-active JSRs are developed as open
source projects.
– Java SE: OpenJDK.
• http://openjdk.java.net/
– Java EE: Project Glassfish.
• http://glassfish.java.net/
• Most Expert Groups have adopted some aspects of the
open-source development process.
41 May 2011
49. Platform updates
• Java SE 7 and Java SE 8 JSRs launched in late 2010.
– JSR 336: Java SE 7 Release Contents.
– JSR 337: Java SE 8 Release Contents.
– Plus many component JSRs.
• Java EE 7 JSRs launched in early 2011.
– JSR 342: Java EE 7 Specification.
– Plus many component JSRs.
• Watch for Java ME JSRs coming soon.
49 May 2011
50. Process updates
• Two JSRs will be filed soon to update the JCP's processes
and constitution.
– As defined in the Process Document and JSPA.
• JCP.next JSR1 will focus on simple changes that can be
implemented within about six months.
• JCP.next JSR 2 will implement more complex changes,
including any that require modifying the JSPA.
– This will take 12-18 months to complete.
• Both JSRs will operate transparently.
– We want your input.
50 May 2011
51. Special Election May 2011
• Four vacant EC seats filled:
– Two ratified seats on the SE/EE EC:
SouJava & Goldman Sachs
– One elected seat: London JUG
– One elected seat on the ME EC:
• Alex Terrazas
• For details see
http://jcp.org/en/whatsnew/elections.
• All members can vote –
– Join so you can vote next time (Fall 2011).
– Here's how: http://jcp.org/en/participation/membership
51 May 2011
53. Indian participation in the JCP
• 46 members, 129 EG participants, 1218 registered users
(includes members).
– Members include Chennai JUG, Pramati Technologies, Tata
Consultancy (and Limited), Wipro
• We need more participation from India to participate in
the evolution of Java technology!
53 May 2011
54. Asian participation in the JCP
• Korea: 21 members, 76 EG participants, 7 Spec Leads.
– Members include Aromasoft, Electronics and
Telecommunications Institute, LG Electronics, Samsung,
SK Telecom, TmaxSoft.
– Korean-lead JSRs: 278, 327, 324, 298, 278, 300, 332.
• Japan: 33 members, 132 EG participants, no Spec Leads.
– Members include Aplix, Fujitsu, Hitachi, Matsushita,
Mitsubishi, NEC, NTT, Ricoh, Sharp, Yokogawa.
• China: 14 members, 37 EG participants, no Spec Leads.
– Members include Beijing ZRRT, CMCC, TongTech,
Huawei, Peking University, Xian Jiaotong University.
54 May 2011
55. Why participate?
• As an individual:
– Altruism.
– Experience.
– Fame and fortune.
• As a corporation:
– To inf uence the technologies that drive your market.
l
– Because it's cheaper than developing everything yourself.
– To provide opportunities for your developers.
– To increase the size of your market.
– To gain a competitive advantage (ship new products faster.)
55 May 2011
56. How to participate
• As a non-member:
– Participate in OpenJDK or
Project Glassfish.
– Review specifications and
provide feedback.
• As a member:
– Vote in the elections.
– Join an Expert Group.
– Lead a JSR.
– Run for the Executive
Committee.
56 May 2011
57. Java and the JCP: providing solutions for everyone
57 May 2011