The document discusses how Java User Groups (JUGs) can get involved in the Java Community Process (JCP) by adopting Java Specification Requests (JSRs). It provides information on the JCP, JSR lifecycle, and opportunities for JUGs to participate at different levels from testing early releases to helping build reference implementations. The document encourages JUG KPI to adopt a JSR and lists several that are available including JSR 310 for Date/Time and JSR 335 for Lambdas. It also discusses other ways JUGs can grow through events like hack days and coding sessions.
2. About speakers
Olena Syrota
• Experience in software
development about 15
years
• Working at EPAM Systems
• Lecturing at NTUU KPI
Oleg Tsal-Tsalko
• Senior Java Developer in
EPAM Systems.
• Mostly working with
enterprise business
applications.
• Member of LJC and JUG KPI
communities.
11. JUG KPI (Kiev)
• Home - http://jug.ua
• Forum -
https://groups.google.com/forum/?fromgroup
s#!forum/jug-kpi
• Twitter - #jugua
12. Why should the JUGs get involved?
• To move the entire Java ecosystem forward
• To contribute your code and knowledge in
Java platform
• To be at the forefront of new technology
• To acquire new knowledge
• To be more recognizable in Java world
• Have fun!
13. How to start?
• Decide inside JUG what JSRs to support
• Contact Spec Lead / Expert Group to start
collaboration
• Set up a wiki page to co-ordinate your
activities
– e.g. http://java.net/projects/ljc-london-
jug/pages/JSR-310
– Link that into the matrix at http://adoptajsr.org
• Start work!
14. What exactly to do?
Starter
• Participate discussions in mailing list (give your thoughts,
suggest enhancements)
• Help reproduce issues
• Test the early RI builds (report bugs, suggest improvements)
Intermediate
• Give feedback on design (review code, specification)
• Help evangelise the JSR (talks, blogs, articals)
Advanced
• Help build the RI
• Help build the TCK
15. There are a lot to choose from:
• JSR 310 – Date & Time
• JSR 335 – Lambdas
• JSR 107 – JCache
• JSR 236, Concurrency Utilities for Java
• JSR 339, JAX RS 2.0
• JSR 343, JMS 2.0
• JSR 344, JSF 2.2
• JSR 345, EJB 3.2
• JSR 346, CDI 1.1
• JSR 352, Batch Application for the Java Platform
• JSR 353, Java API for JSON Processing
• JSR 356, Java API for Web Sockets
16. Who is already participating?
20 JUGs:
Campinas JUG, ceJUG, GOJava, SouJava,
PeruJUG, SV JUG, Houston JUG, Toronto JUG,
London Java Community, BeJUG, Madrid JUG,
JUG Cologne, Indonesia JUG, Hyderabad JUG,
JUG Chennai, Morocco JUG, Faso JUG, Jozi
JUG, Mbale and more…
JUG KPI could be one of them!!!
18. LJC event and meetups
• Meet a project
• Developers sessions
• HackDay
• Hack the tower
LSCC event and meetups
• Code & Coffee
• Code & Beer
• Round tables
• Coding kata
19. Hack Day
More details here -
http://www.slideshare.net/RichardWarburton/how-to-run-a-
hackday-1
• Educate
• Give feedback
• Find/fix bugs
Pick a target
• Establish time, place and agendaFind a space
• Have coordinator,
• Follow guidelines,
• Communicate with EG via mailing list
Get some help
• Talk/discuss with each other
• Consider range of experiences
• Consider exercises
• Pair/learn from each other
• Have fun!!!
Do it!
20. Glossary
• JUG - Java User Group
• JSR - Java Specification Request
• JCP - Java Community Process
• RI - Reference Implementation
• TCK - Technology Compatibility Kit
• EG - Expert Group
• EC - Executive Committee
• SL – Spec Lead