https://fedoraproject.org/w/api.php?action=feedcontributions&user=Mojavelinux&feedformat=atomFedora Project Wiki - User contributions [en]2024-03-28T23:18:34ZUser contributionsMediaWiki 1.39.4https://fedoraproject.org/w/index.php?title=User:Mojavelinux&diff=325124User:Mojavelinux2013-03-05T10:56:53Z<p>Mojavelinux: </p>
<hr />
<div>= Dan Allen =<br />
<br />
Email: dan.j.allen ~ gmail ~ com<br />
<br />
IRC: mojavelinux/irc.freenode.net #jbosstesting<br />
<br />
Twitter: [http://twitter.com/mojavelinux twitter.com/mojavelinux]<br />
<br />
GitHub: [http://github.com/mojavelinux github.com/mojavelinux]<br />
<br />
Timezone: US/Mountain<br />
<br />
== What I'm Working On ==<br />
<br />
* Asciidoctor RPM (RubyGem)</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=FUDCon:Lawrence_2013&diff=319313FUDCon:Lawrence 20132013-01-17T23:02:00Z<p>Mojavelinux: </p>
<hr />
<div><div style="text-align: center; padding: 15px;">[[Image:Fudcon lawrence withdate.png]]</div><br />
<center>'''Lawrence, Kansas, USA :: January 18&ndash;20, 2013''' &mdash; General event owners: [[User:Rbergero|Robyn Bergeron]], [[User:Rsuehle|Ruth Suehle]], [[User:Ianweller|Ian Weller]]</center><br />
<br />
== Pre-registration ==<br />
<br />
<big>'''[http://fudconlawrence-ianweller.rhcloud.com/ Pre-register here]'''</big><br />
<br />
== Event details ==<br />
<br />
'''The 2013 North America FUDCon will be held in Lawrence, Kansas, on January 18&ndash;20, 2013.'''<br />
<br />
[[FUDCon]] is the Fedora Users and Developers Conference, a major free software event held in various regions around the world, usually annually per region. FUDCon is a combination of sessions, talks, workshops, and hackfests in which contributors work on specific initiatives. Topics include infrastructure, feature development, community building, general management and governance, marketing, testing and QA, packaging, etc.<br />
<br />
FUDCon is always free to attend for anyone in the world.<br />
<br />
=== Dates ===<br />
<br />
January 18&ndash;20, 2013 (Friday, Saturday, Sunday)<br />
<br />
=== Lodging ===<br />
<br />
SpringHill Suites<br/><br />
One Riverfront Plaza<br/><br />
Lawrence, KS 66044<br />
<br />
<br />
$119/night<br />
<br />
We have a block of rooms with two queens and some with only a king. Both types have foldout sofa beds as well. The block is available for the nights of Wednesday, Thursday, Friday, Saturday, and Sunday. '''Please reserve your room by December 21.''' Rooms include:<br />
<br />
* pull out sofa bed<br />
* mini fridge and microwave<br />
* free wifi<br />
* breakfast buffet<br />
<br />
The hotel has an indoor pool, gym, and business center with printing and faxing services available. <br />
<br />
Check-in time is 3:00 pm. Check-out time is 12:00 noon. Hotel is non-smoking.<br />
<br />
=== Transportation ===<br />
<br />
==== To and from Lawrence via airline ====<br />
<br />
[http://www.flykci.com/ Kansas City International] (IATA: MCI) is about a 60-minute drive from Lawrence.<br />
<br />
If you are flying to Kansas City to come to FUDCon, please add your name and flight information to the [[/Flights|flights page]]. We will organize car pools through that page.<br />
<br />
'''Airport shuttles'''<br />
<br />
''NOTE: IMPORTANT CHANGE IN PICKUP LOCATION''<br />
If you requested an airport shuttle, you should have received an email with the relevant information. Shuttles will be picking you up at TERMINAL B baggage claim. Look for a person holding from Redy2Party bus service holding a FUDCon sign. If your plane is early or late, simply look for the next arriving shuttle. <br />
<br />
If you did not request a shuttle, you may see if there is room on one when you land. The 4:15 p.m. and 10:15 p.m. shuttles are quite full. There will be shuttles on Thursday at:<br />
<br />
* 11 a.m.<br />
* 2:15 p.m.<br />
* 3:15 p.m.<br />
* 4:15 p.m.<br />
* 5:15 p.m.<br />
* 7:15 p.m.<br />
* 10:15 p.m.<br />
* 11:45 p.m.<br />
<br />
Departing from the FUDCon location on campus on Sunday:<br />
<br />
* 11 a.m.<br />
* 1 p.m. <br />
* 3 p.m.<br />
* 4 p.m.<br />
<br />
Departing from the hotel on Monday: <br />
<br />
* 8 a.m.<br />
* 12 p.m.<br />
* 2 p.m.<br />
<br />
<br />
==== To and from Lawrence via private plane ====<br />
[http://hetrickairservices.com/cgi-bin/p/w66p-airportinfo.cgi?d=hetrick-air-services-inc Lawrence Municipal Airport] (IATA: LWC) is about a 10-minute drive from Lawrence.<br />
<br />
==== To and from Lawrence via train ====<br />
Amtrak has a [http://www.amtrak.com/servlet/ContentServer?c=am2Station&pagename=am%2Fam2Station%2FStation_Page&cid=1229726268821 Lawrence station (LRC)].<br />
<br />
==== To and from Lawrence via car ====<br />
Lawrence is accessible via exits 202 and 204 on the Kansas Turnpike (Interstate 70).<br />
<br />
The Kansas Turnpike is a toll road. The toll from the Topeka entrance to Lawrence exit 202 is USD $1.00. The toll from the Kansas City-side entrance to Lawrence exit 204 is USD $1.60. For more information on the Kansas Turnpike, visit [http://www.ksturnpike.com/ www.ksturnpike.com].<br />
<br />
==== Within Lawrence ====<br />
Lawrence has [http://www.lawrencetransit.org/ public transportation] with routes covering most of the city and University of Kansas campus with a [http://www.lawrencetransit.org/pages/trip-planner trip planner] also available to assist with getting around town.<br />
<br />
=== Parking ===<br />
Information about parking on the University of Kansas campus can be found on the [http://www.parking.ku.edu/ KU Parking & Transit site].<br />
<br />
=== Network access ===<br />
<br />
TBA<br />
<br />
=== Packing List ===<br />
<br />
'''Everybody:'''<br />
* '''Appropriately warm clothing &mdash; [http://en.wikipedia.org/wiki/Lawrence,_Kansas#Climate it will possibly snow] in Kansas in January'''<br />
* Laptop with 802.11g wireless<br />
** Extension cord<br />
** Ethernet cable (for hotel and/or hackfest)<br />
** Optional: Bring a [http://fedorafriendfinder.org/ Fedora Friend Finder] (power strip)<br />
* Credit card (VISA or MasterCard) or small amount of cash<br />
* Your presentation slides or anything needed for the hackfest<br />
<br />
'''International visitors:'''<br />
* Passport/visa and any other official documentation needed<br />
* Converters for power ([http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets reference link]<ref>Most consumer plugs in the USA are Type B.</ref>)<br />
<br />
'''If staying at the hotel:'''<br />
* Optional: swimsuit, gym clothes.<ref>This doesn't mean clothing is optional if you swim or exercise!</ref><br />
<br />
== Agenda ==<br />
<br />
=== Shuttles from hotel to conference ===<br />
<br />
Shuttles will be leaving the hotel Friday, Saturday, and Sunday mornings beginning at 7:15 a.m. The last shuttle will leave at 8:15 a.m.<br />
<br />
=== General schedule ===<br />
<br />
* '''Friday, January 18:''' Introductory session, BarCamp sessions, lightning talks, and hotel party<br />
* '''Saturday, January 19 and Sunday, January 20''': Hackfests, FUDPub<br />
<br />
Rooms available in Learned hall, all three conference dates: 1131, 1136, 2111, 2112, 2133, 2148, 3150, 3152, 3153, 3154. Spahr Engineering Classroom is also available on all three dates.<br />
<br />
==== Thursday, January 17 ====<br />
<br />
Thursday evening at 8 pm., there is a global Raspberry Pi meetup over Google Hangout. MAKE is the host and guests are Matt Richardson and Shawn Wallace, authors of Getting Started with Raspberry Pi. All meetup attendees will receive a free PDF download of MAKE Magazine Volume 33. The guests will talk about the projects featured in the magazine and discuss everything Pi. There's a live chat where you can ask them questions as well as share your own projects. <br />
<br />
https://plus.google.com/+MAKE/posts<br />
<br />
We'd like to gather to join the Hangout and then hang out amongst ourselves talking Pi. Please add your name here if you'd like to join us so that we're sure to have enough room:<br />
<br />
* Ruth Suehle<br />
* Tom Callaway<br />
* Jeff Ollie<br />
* Chris Tyler<br />
* Emily Dirsh<br />
* Shyam Prasad<br />
* Ben Williams<br />
* Sarah White<br />
* Zach Oglesby<br />
* Nick Bebout<br />
<br />
==== Friday, January 18 ====<br />
<br />
This schedule is subject to approval. Talks will be assigned Friday morning during BarCamp voting. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
|colspan=6 style="text-align:center"| Plenary session: welcome, BarCamp pitches and voting, FPL talk (Spahr Engineering Classroom)<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
|colspan=6 style="text-align:center"| Lightning talks (Spahr Engineering Classroom)<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || ||<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || ||<br />
|-<br />
|}<br />
<br />
=== Technical sessions (Friday) ===<br />
<br />
As with all BarCamp conferences, technical sessions will be presented, voted on and scheduled the morning of the conference. If you like, you may list your session proposal below.<br />
<br />
{|<br />
! Session name<br />
! Description<br />
! User level<br />
! Lead<br />
|-<br />
| Creating SECure Linux Containers"<br />
| A quick overview on Containers<br />
| Intermediate<br />
| [[User:dwalsh|Dan Walsh]]<br />
|-<br />
| "SELinux for Mere Mortals"<br />
| An introduction to SELinux (it's not scary at all - you'll love it!)<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 1 - Systems Management"<br />
| Tips and tricks on managing systems with Spacewalk<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 2 - Building Packages"<br />
| Tips and tricks on building packages for Fedora/RHEL - even if you don't have the source code.<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Building a Software NAS using Gluster"<br />
| An introduction to Gluster<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "HA Clustering with Fedora"<br />
| How to set up a high availability application cluster using a shared filesystem with Fedora<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "[http://fedmsg.com fedmsg] - What's in place and what's next."<br />
| A look at the past year of development and what exciting goodies are planned<br />
| Intermediate<br />
| [[User:Ralph|Ralph Bean]]<br />
|-<br />
| "An introduction to the new Anaconda"<br />
| Lots has changed about Anaconda in Fedora 18. This session is your handy guide to the new shiny.<br />
| All levels<br />
| [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| "EPEL (Extra Packages for Enterprise Linux) roundtable"<br />
| We need to hash out some proposals on handling overlaps and incompatible upgrades. <br />
| Any EPEL users/developers<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "HyperKitty, the next-generation Mailman archiver"<br />
| Learn about the new web-based user interface for mailing-list archives<br />
| All levels<br />
| [[User:Abompard|Aurélien Bompard]]<br />
|-<br />
| "Fedora Cloud Images for F19 and Beyond"<br />
| Let's plan what we're going to do to make our cloud images more useful to users.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Fedora Cloud Infrastructure Software in Fedora 19"<br />
| Develop plans and talk about OpenStack, OpenShift Origin, Eucalyptus, CloudStack, OpenNebula, and all the rest.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Everything you never wanted to know about Secure Boot and weren't afraid not to ask"<br />
| Discuss where we are with Secure Boot; Q&A.<br />
| All levels<br />
| [[User:Pjones|Peter Jones]]<br />
|-<br />
| Fedora Formulas Brainstorming session<br />
| Discuss if https://fedoraproject.org/wiki/Fedora_formulas is a viable thing to work on / make happen<br />
| All levels<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "ARM-building exercises: the new build platform for Fedora on ARM"<br />
| A demonstration of the Calxeda ECX-1000 server rapidly and reliably rebuilding FC for ARM<br />
| All levels<br />
| [[User:mlangsdorf|Mark Langsdorf]]<br />
|-<br />
| "COPRs - Fedora Ad-hoc package buildsystem"<br />
| A demonstration and technical explanation of the new copr buildsystem<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Ansible - Config Mgmt, Command/Control and RPC"<br />
| What fedora is doing with ansible and what you can be doing with it<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Micro-web-framework, unit-tests and maintainable web-application"<br />
| What's interesting about micro-web-framework with regards to continuous integration and maintainability<br />
| All levels<br />
| [[User:pingou|Pierre-Yves Chibon (pingou)]]<br />
|-<br />
| Improving the FAmA (Fedora Ambassador Administration) Mentoring Process<br />
| Discussion on how to better manage mentoring, tips and tricks, share the current process and improve it. Plus educating current and potential mentors and manatees (mentees).<br />
| All levels<br />
| [[User:Herlo|Clint Savage]]<br />
|-<br />
| State of the Kernel<br />
| Current status, plans, and aspirations of the Fedora kernel team <br />
| Intermediate <br />
|[[User:Jforbes|Justin M. Forbes]]<br />
|-<br />
| Open Compute - why you should care (emphasis on Hardware Management track)<br />
| Current status of Facebook's Open Compute Project, how you can help<br />
| Intermediate<br />
| [[User:Jstanley|Jon Stanley]]<br />
|-<br />
| Pulp 2.0 - Enterprise Repository Management<br />
| Learn how to create and host repositories (yum, Puppet module), add custom content, and push install to large numbers of machines. Promote content through dev, test, and production repos.<br />
| Intermediate<br />
| [[User:mhrivnak|Michael Hrivnak]]<br />
|-<br />
| Apache CloudStack - Open Source Cloud Computing<br />
| Learn all about Apache CloudStack: What it is, what it does, and how it can be used to create/deploy an IaaS cloud.<br />
| Intermediate<br />
| [[User:jzb|Joe Brockmeier]]<br />
|-<br />
| Fedora Ambassadors - Present and the Future<br />
| A session to discuss the current state of FAm program and its future. What FAmSCo has done, is planning.<br />
| Intermediate<br />
| [[User:eischmann|Jiri Eischmann]]<br />
|}<br />
<br />
{{anchor|lightning}}<!-- please don't remove this line --><br />
<br />
=== Lightning talks (Friday) ===<br />
<br />
We'll do lightning talks after lunch on Friday (depending on things). These talks are to be no longer than 5 minutes, at which point we will gong you out. '''Talk about what you are passionate about''', which doesn't have to necessarily be Fedora.<br />
<br />
If you're interested, list your proposed talk below. We have time for 10 talks, so please don't list your talk here if there are already 10.<br />
<br />
{|<br />
! Talk name<br />
! Talker<br />
! Comments<br />
|-<br />
| Texas Hold'em Poker for fun and profit: Learn how to play before the annual Fedora Poker Game<br />
| Robyn Bergeron<br />
| A super-quick overview of the rules of Texas Hold'em.<br />
|-<br />
| pkgwat and the Fedora Packages webapp<br />
| Ralph Bean<br />
| An introduction the Fedora Packages webapp and related tools.<br />
|-<br />
| fedocal: a calendar webapp for Fedora<br />
| Pierre-Yves Chibon<br />
| Short presentation to fedocal, a calendar web application for Fedora.<br />
|-<br />
| OpenLMI: The Open Linux Manageability Infrastructure<br />
| Stephen Gallagher<br />
| Short introduction to centralized manageability<br />
|-<br />
| Open Source Security<br />
| Eric Christensen<br />
| I'm looking for a few good hackers to help create developer training and resources.<br />
|-<br />
| Write docs without pain<br />
| Dan Allen<br />
| Intro to AsciiDoc, a lightweight alternative to writing docs without abandoning the DocBook toolchain.<br />
|-<br />
|}<br />
<br />
=== Hackfests (Saturday and Sunday) ===<br />
{|<br />
! Session name<br />
! Description<br />
! Time Needed <br />
! Lead<br />
|-<br />
| Ham Radio Test Session || Ham Radio Test Session For Attendees to get/upgrade their Licenses||3 hours ||Ben Williams<br />
|-<br />
| [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]] || Exchanging of GPG key fingerprints and identification to enable people to sign each other's keys||1 hour ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]] || ||1.5 hours ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Origin - Build Your Own PaaS]] || Build your own Open Source PaaS using Fedora and OpenShift Origin||3 hours || Troy Dawson (tdawson), Adam Miller (maxamillion)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Online - Deploy WebApps to the Cloud]] || Utilize the Hosted version of OpenShift to deploy and/or develop Applications in the Cloud for free! ||1.5 hours || Adam Miller (maxamillion), Troy Dawson (tdawson) <br />
|-<br />
| Features/scheduling revamp || Work on Feature process and release scheduling, blackboard needed ;-) || at least a few hours || Jaroslav Reznik (jreznik)<br />
|-<br />
| Meet your FESCo || Come and meet the men and women of the Fedora Engineering Steering Committee! || 30 minutes to an hour || Stephen Gallagher (sgallagh)<br />
|-<br />
| [https://github.com/herlo/ssh-gpg-smartcard-config GPG SmartCard Configuration] || Tips for setting up a gpg smartcard with Fedora. Two-factor SSH configuration, signing and encryption || 60-90 minutes (should happen before GPG Signing event) || [[User:Herlo|Clint Savage]]<br />
|-<br />
| [[FUDCon:Lawrence_2013_i18n_hackfest|i18n in Fedora]]: what's bad, what we broke in Fedora 18, how to fix it? || There's lots of badness in i18n configuration in Fedora, and it got worse between Fedora 17 and Fedora 18. Aim is to ensure everyone has a high-level understanding of what a good i18n config architecture would look like, and a low-level understanding of all the bits that are broken in Fedora 18+, and hopefully start some work on some of the low-hanging fruit. || Could run and run! || [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| Fedora Infrastructure Hackfest || will plan out specific tasks/areas saturday morning. See https://fedoraproject.org/wiki/Fedora_infrastructure_tasks_2013 for ideas container and lists. Everyone welcome to help/join in! || space both days would be nice || [[User:Kevin|Kevin Fenzi]] <br />
|-<br />
| Fedora ARM Hackfest || Board support hackfest, PA planning, ARMv[5678] direction, and growing community contributions || Space both days || Jon Masters (jonmasters), [[User:Ctyler|Chris Tyler]] (ctyler), [[User:blc|Brendan Conoboy]] (bconoboy) et al.<br />
|-<br />
| Marketing || Would like to have a group chat if there's interest. || 2-3 hours || [[User:rsuehle|Ruth Suehle]] <br />
|-<br />
| Fedora PPC Brainstorming || Topics at https://fedoraproject.org/wiki/Architectures/PowerPC/Meetings/FUDCon_Lawrence_2013 || Space both days || [[User:Karsten|Karsten Hopp]], et al.<br />
|-<br />
| Websites || Help improving the websites build scripts to avoid duplicates, human error and speed up the process! Plans [https://fedoraproject.org/wiki/Websites/workflow#The_Hot_.28comming.29_New_Websites_Arch here] − python & Makefiles hack|| both days.. || [[User:shaiton|Kévin Raymond]] <br />
|-<br />
| Static Analysis Hackfest || Let's build tools for automated [http://fedoraproject.org/wiki/StaticAnalysis static analysis of the code in Fedora] || Space both days || [[User:dmalcolm|Dave Malcolm]] <br />
|-<br />
| Fedora Cloud Image Generation and Automated Testing Hackfest || Let's get cloud image generation integrated into the releng process, and maybe automated nightly generation || Probably could use as much time as there is || [[User:mattdm|Matthew Miller]] + others from Cloud SIG and Rel Eng<br />
|-<br />
| Fedora JavaScript/Node.js Packaging Brainstorm || Now that Node.js is in Fedora, we need to set up some official packaging guidelines || Two hours either day || [[User:sgallagh|Stephen Gallagher]]<br />
|}<br />
<br />
==== Saturday, January 19 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]]<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]]<br />
|-<br />
|}<br />
<br />
==== Sunday, January 20 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || <br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || <br />
|-<br />
|}<br />
<br />
=== Social events ===<br />
<br />
==== Friday night gaming ====<br />
<br />
Bringing an awesome game? List it here so that we don't all put Carcassonne in our suitcases. <br />
<br />
* Carcassonne - [[User:Herlo|Clint Savage]]<br />
* [[FUDCon:Lawrence_2013_Poker|Poker Signup]] - Poker Cards & Chips - [[User:Herlo|Clint Savage]]<br />
* [http://boardgamegeek.com/boardgame/1234/once-upon-a-time Once Upon a Time] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/258/fluxx Fluxx] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/696/the-big-idea The Big Idea] - [[User:Sgallagh|Stephen Gallagher]]<br />
* Cards Against Humanity (+ Expansion 1) [[User:spot|Tom Callaway]] - Expansion 2 [[User:Jstanley|Jon Stanley]] - Holiday Expansion [[User:Ianweller|Ian Weller]] (if my roommate brings it back from Colorado)<br />
* Settlers of Catan - [[User:mattdm|Matthew Miller]]<br />
* [http://boardgamegeek.com/boardgame/31260/agricola Agricola] - [[User:mattdm|Matthew Miller]] (This is kind of a boardgaming commitment, so I'm only bringing it if at least one person e-mails me and says they're interested.)<br />
* Space: 1889 - [[User:jdulaney|John Dulaney]] If there is interest, let me know ahead of time so I know how many character sheets to print.<br />
* Arkham Horror with 2 expansions (king in yellow, goat in the woods)| [[User:jbwillia|Ben Williams]]<br />
* [http://www.atlas-games.com/product_tables/AG1100.php Lunch Money] with sticks and stones expansion - [[User:Tflink|Tim Flink]]<br />
<br />
==== FUDPub ====<br />
Wayne and Larry's, followed by bowling. <br />
933 Iowa St<br />
Lawrence, KS 66044<br />
785-856-7170 • 785-842-1234<br />
<br />
* There will be a pasta bar, toasted ravioli, chocolate chip cookies, and appropriate food for vegetarians. <br />
* Drinks alcoholic and non, bar is generously sponsored by Citrix from 6:30-8:30<br />
* We have the room to ourselves for buffet and bar from 6:30-8:30. At 9 p.m., there will be a band in the bar, which you're welcome to hang around for, or to go bowling next door.<br />
* Shuttles will return to the hotel from Wayne and Larry's at 8:30, 9:30 and 11:30.<br />
<br />
Want to go bowling after FUDPub? Add your name here so we can estimate lanes:<br />
<br />
* [[User:Suehle|Ruth Suehle]]<br />
* [[User:Herlo|Clint Savage]]<br />
* [[User:Adamwill|Adam Williamson]]<br />
* [[User:vicodan|Dan Mashal]]<br />
* [[User:Sgallagh|Stephen Gallagher]]<br />
* [[User:Pfrields|Paul Frields]]<br />
* [[User:jreznik|Jaroslav "The Dude" Reznik]]<br />
* [[User:eischmann|Jiri Eischmann]]<br />
* [[User:notting|Bill Nottingham]]<br />
* [[User:rdieter|Rex Dieter]]<br />
* [[User:ianweller|Ian Weller]]<br />
* [[User:graphitefriction|Sarah White]]<br />
* [[User:mojavelinux|Dan Allen]]<br />
* [[User:Jstanley|Jon Stanley]]<br />
* [[User:Baude|Brent Baude]]<br />
* [[User:hamzy|Mark Hamzy]]<br />
* [[User:Karsten|Karsten Hopp]]<br />
* [[User:pknirsch|Phil Knirsch]]<br />
* [[User:sparks|Eric Christensen]]<br />
* [[User:makfinsky|Ivan Makfinsky]]<br />
* [[User:AnnaE|Anna Eusebio]]<br />
* [[User:Zoglesby|Zach Oglesby]]<br />
* [[User:gholms|Garrett Holmstrom]]<br />
* [[User:Nb|Nick Bebout]]<br />
<br />
== Administration ==<br />
<br />
=== Planning meetings ===<br />
<br />
Meetings are currently not being held. We will start holding them again shortly before funding administration.<br />
<br />
Other useful pages:<br />
* [[/Budget]]<br />
* [[/Flights]] (when people are flying in; carpool planning)<br />
* [[/Booklet]]<br />
<br />
----<br />
<references/><br />
<br />
[[Category:FUDCon]]<br />
[[Category:Events]]<br />
[[Category:Events 2013]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=FUDCon:Lawrence_2013&diff=319312FUDCon:Lawrence 20132013-01-17T23:00:40Z<p>Mojavelinux: </p>
<hr />
<div><div style="text-align: center; padding: 15px;">[[Image:Fudcon lawrence withdate.png]]</div><br />
<center>'''Lawrence, Kansas, USA :: January 18&ndash;20, 2013''' &mdash; General event owners: [[User:Rbergero|Robyn Bergeron]], [[User:Rsuehle|Ruth Suehle]], [[User:Ianweller|Ian Weller]]</center><br />
<br />
== Pre-registration ==<br />
<br />
<big>'''[http://fudconlawrence-ianweller.rhcloud.com/ Pre-register here]'''</big><br />
<br />
== Event details ==<br />
<br />
'''The 2013 North America FUDCon will be held in Lawrence, Kansas, on January 18&ndash;20, 2013.'''<br />
<br />
[[FUDCon]] is the Fedora Users and Developers Conference, a major free software event held in various regions around the world, usually annually per region. FUDCon is a combination of sessions, talks, workshops, and hackfests in which contributors work on specific initiatives. Topics include infrastructure, feature development, community building, general management and governance, marketing, testing and QA, packaging, etc.<br />
<br />
FUDCon is always free to attend for anyone in the world.<br />
<br />
=== Dates ===<br />
<br />
January 18&ndash;20, 2013 (Friday, Saturday, Sunday)<br />
<br />
=== Lodging ===<br />
<br />
SpringHill Suites<br/><br />
One Riverfront Plaza<br/><br />
Lawrence, KS 66044<br />
<br />
<br />
$119/night<br />
<br />
We have a block of rooms with two queens and some with only a king. Both types have foldout sofa beds as well. The block is available for the nights of Wednesday, Thursday, Friday, Saturday, and Sunday. '''Please reserve your room by December 21.''' Rooms include:<br />
<br />
* pull out sofa bed<br />
* mini fridge and microwave<br />
* free wifi<br />
* breakfast buffet<br />
<br />
The hotel has an indoor pool, gym, and business center with printing and faxing services available. <br />
<br />
Check-in time is 3:00 pm. Check-out time is 12:00 noon. Hotel is non-smoking.<br />
<br />
=== Transportation ===<br />
<br />
==== To and from Lawrence via airline ====<br />
<br />
[http://www.flykci.com/ Kansas City International] (IATA: MCI) is about a 60-minute drive from Lawrence.<br />
<br />
If you are flying to Kansas City to come to FUDCon, please add your name and flight information to the [[/Flights|flights page]]. We will organize car pools through that page.<br />
<br />
'''Airport shuttles'''<br />
<br />
''NOTE: IMPORTANT CHANGE IN PICKUP LOCATION''<br />
If you requested an airport shuttle, you should have received an email with the relevant information. Shuttles will be picking you up at TERMINAL B baggage claim. Look for a person holding from Redy2Party bus service holding a FUDCon sign. If your plane is early or late, simply look for the next arriving shuttle. <br />
<br />
If you did not request a shuttle, you may see if there is room on one when you land. The 4:15 p.m. and 10:15 p.m. shuttles are quite full. There will be shuttles on Thursday at:<br />
<br />
* 11 a.m.<br />
* 2:15 p.m.<br />
* 3:15 p.m.<br />
* 4:15 p.m.<br />
* 5:15 p.m.<br />
* 7:15 p.m.<br />
* 10:15 p.m.<br />
* 11:45 p.m.<br />
<br />
Departing from the FUDCon location on campus on Sunday:<br />
<br />
* 11 a.m.<br />
* 1 p.m. <br />
* 3 p.m.<br />
* 4 p.m.<br />
<br />
Departing from the hotel on Monday: <br />
<br />
* 8 a.m.<br />
* 12 p.m.<br />
* 2 p.m.<br />
<br />
<br />
==== To and from Lawrence via private plane ====<br />
[http://hetrickairservices.com/cgi-bin/p/w66p-airportinfo.cgi?d=hetrick-air-services-inc Lawrence Municipal Airport] (IATA: LWC) is about a 10-minute drive from Lawrence.<br />
<br />
==== To and from Lawrence via train ====<br />
Amtrak has a [http://www.amtrak.com/servlet/ContentServer?c=am2Station&pagename=am%2Fam2Station%2FStation_Page&cid=1229726268821 Lawrence station (LRC)].<br />
<br />
==== To and from Lawrence via car ====<br />
Lawrence is accessible via exits 202 and 204 on the Kansas Turnpike (Interstate 70).<br />
<br />
The Kansas Turnpike is a toll road. The toll from the Topeka entrance to Lawrence exit 202 is USD $1.00. The toll from the Kansas City-side entrance to Lawrence exit 204 is USD $1.60. For more information on the Kansas Turnpike, visit [http://www.ksturnpike.com/ www.ksturnpike.com].<br />
<br />
==== Within Lawrence ====<br />
Lawrence has [http://www.lawrencetransit.org/ public transportation] with routes covering most of the city and University of Kansas campus with a [http://www.lawrencetransit.org/pages/trip-planner trip planner] also available to assist with getting around town.<br />
<br />
=== Parking ===<br />
Information about parking on the University of Kansas campus can be found on the [http://www.parking.ku.edu/ KU Parking & Transit site].<br />
<br />
=== Network access ===<br />
<br />
TBA<br />
<br />
=== Packing List ===<br />
<br />
'''Everybody:'''<br />
* '''Appropriately warm clothing &mdash; [http://en.wikipedia.org/wiki/Lawrence,_Kansas#Climate it will possibly snow] in Kansas in January'''<br />
* Laptop with 802.11g wireless<br />
** Extension cord<br />
** Ethernet cable (for hotel and/or hackfest)<br />
** Optional: Bring a [http://fedorafriendfinder.org/ Fedora Friend Finder] (power strip)<br />
* Credit card (VISA or MasterCard) or small amount of cash<br />
* Your presentation slides or anything needed for the hackfest<br />
<br />
'''International visitors:'''<br />
* Passport/visa and any other official documentation needed<br />
* Converters for power ([http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets reference link]<ref>Most consumer plugs in the USA are Type B.</ref>)<br />
<br />
'''If staying at the hotel:'''<br />
* Optional: swimsuit, gym clothes.<ref>This doesn't mean clothing is optional if you swim or exercise!</ref><br />
<br />
== Agenda ==<br />
<br />
=== Shuttles from hotel to conference ===<br />
<br />
Shuttles will be leaving the hotel Friday, Saturday, and Sunday mornings beginning at 7:15 a.m. The last shuttle will leave at 8:15 a.m.<br />
<br />
=== General schedule ===<br />
<br />
* '''Friday, January 18:''' Introductory session, BarCamp sessions, lightning talks, and hotel party<br />
* '''Saturday, January 19 and Sunday, January 20''': Hackfests, FUDPub<br />
<br />
Rooms available in Learned hall, all three conference dates: 1131, 1136, 2111, 2112, 2133, 2148, 3150, 3152, 3153, 3154. Spahr Engineering Classroom is also available on all three dates.<br />
<br />
==== Thursday, January 17 ====<br />
<br />
Thursday evening at 8 pm., there is a global Raspberry Pi meetup over Google Hangout. MAKE is the host and guests are Matt Richardson and Shawn Wallace, authors of Getting Started with Raspberry Pi. All meetup attendees will receive a free PDF download of MAKE Magazine Volume 33. The guests will talk about the projects featured in the magazine and discuss everything Pi. There's a live chat where you can ask them questions as well as share your own projects. <br />
<br />
https://plus.google.com/+MAKE/posts<br />
<br />
We'd like to gather to join the Hangout and then hang out amongst ourselves talking Pi. Please add your name here if you'd like to join us so that we're sure to have enough room:<br />
<br />
* Ruth Suehle<br />
* Tom Callaway<br />
* Jeff Ollie<br />
* Chris Tyler<br />
* Emily Dirsh<br />
* Shyam Prasad<br />
* Ben Williams<br />
* Sarah White<br />
* Zach Oglesby<br />
* Nick Bebout<br />
<br />
==== Friday, January 18 ====<br />
<br />
This schedule is subject to approval. Talks will be assigned Friday morning during BarCamp voting. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
|colspan=6 style="text-align:center"| Plenary session: welcome, BarCamp pitches and voting, FPL talk (Spahr Engineering Classroom)<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
|colspan=6 style="text-align:center"| Lightning talks (Spahr Engineering Classroom)<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || ||<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || ||<br />
|-<br />
|}<br />
<br />
=== Technical sessions (Friday) ===<br />
<br />
As with all BarCamp conferences, technical sessions will be presented, voted on and scheduled the morning of the conference. If you like, you may list your session proposal below.<br />
<br />
{|<br />
! Session name<br />
! Description<br />
! User level<br />
! Lead<br />
|-<br />
| Creating SECure Linux Containers"<br />
| A quick overview on Containers<br />
| Intermediate<br />
| [[User:dwalsh|Dan Walsh]]<br />
|-<br />
| "SELinux for Mere Mortals"<br />
| An introduction to SELinux (it's not scary at all - you'll love it!)<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 1 - Systems Management"<br />
| Tips and tricks on managing systems with Spacewalk<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 2 - Building Packages"<br />
| Tips and tricks on building packages for Fedora/RHEL - even if you don't have the source code.<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Building a Software NAS using Gluster"<br />
| An introduction to Gluster<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "HA Clustering with Fedora"<br />
| How to set up a high availability application cluster using a shared filesystem with Fedora<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "[http://fedmsg.com fedmsg] - What's in place and what's next."<br />
| A look at the past year of development and what exciting goodies are planned<br />
| Intermediate<br />
| [[User:Ralph|Ralph Bean]]<br />
|-<br />
| "An introduction to the new Anaconda"<br />
| Lots has changed about Anaconda in Fedora 18. This session is your handy guide to the new shiny.<br />
| All levels<br />
| [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| "EPEL (Extra Packages for Enterprise Linux) roundtable"<br />
| We need to hash out some proposals on handling overlaps and incompatible upgrades. <br />
| Any EPEL users/developers<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "HyperKitty, the next-generation Mailman archiver"<br />
| Learn about the new web-based user interface for mailing-list archives<br />
| All levels<br />
| [[User:Abompard|Aurélien Bompard]]<br />
|-<br />
| "Fedora Cloud Images for F19 and Beyond"<br />
| Let's plan what we're going to do to make our cloud images more useful to users.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Fedora Cloud Infrastructure Software in Fedora 19"<br />
| Develop plans and talk about OpenStack, OpenShift Origin, Eucalyptus, CloudStack, OpenNebula, and all the rest.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Everything you never wanted to know about Secure Boot and weren't afraid not to ask"<br />
| Discuss where we are with Secure Boot; Q&A.<br />
| All levels<br />
| [[User:Pjones|Peter Jones]]<br />
|-<br />
| Fedora Formulas Brainstorming session<br />
| Discuss if https://fedoraproject.org/wiki/Fedora_formulas is a viable thing to work on / make happen<br />
| All levels<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "ARM-building exercises: the new build platform for Fedora on ARM"<br />
| A demonstration of the Calxeda ECX-1000 server rapidly and reliably rebuilding FC for ARM<br />
| All levels<br />
| [[User:mlangsdorf|Mark Langsdorf]]<br />
|-<br />
| "COPRs - Fedora Ad-hoc package buildsystem"<br />
| A demonstration and technical explanation of the new copr buildsystem<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Ansible - Config Mgmt, Command/Control and RPC"<br />
| What fedora is doing with ansible and what you can be doing with it<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Micro-web-framework, unit-tests and maintainable web-application"<br />
| What's interesting about micro-web-framework with regards to continuous integration and maintainability<br />
| All levels<br />
| [[User:pingou|Pierre-Yves Chibon (pingou)]]<br />
|-<br />
| Improving the FAmA (Fedora Ambassador Administration) Mentoring Process<br />
| Discussion on how to better manage mentoring, tips and tricks, share the current process and improve it. Plus educating current and potential mentors and manatees (mentees).<br />
| All levels<br />
| [[User:Herlo|Clint Savage]]<br />
|-<br />
| State of the Kernel<br />
| Current status, plans, and aspirations of the Fedora kernel team <br />
| Intermediate <br />
|[[User:Jforbes|Justin M. Forbes]]<br />
|-<br />
| Open Compute - why you should care (emphasis on Hardware Management track)<br />
| Current status of Facebook's Open Compute Project, how you can help<br />
| Intermediate<br />
| [[User:Jstanley|Jon Stanley]]<br />
|-<br />
| Pulp 2.0 - Enterprise Repository Management<br />
| Learn how to create and host repositories (yum, Puppet module), add custom content, and push install to large numbers of machines. Promote content through dev, test, and production repos.<br />
| Intermediate<br />
| [[User:mhrivnak|Michael Hrivnak]]<br />
|-<br />
| Apache CloudStack - Open Source Cloud Computing<br />
| Learn all about Apache CloudStack: What it is, what it does, and how it can be used to create/deploy an IaaS cloud.<br />
| Intermediate<br />
| [[User:jzb|Joe Brockmeier]]<br />
|-<br />
| Fedora Ambassadors - Present and the Future<br />
| A session to discuss the current state of FAm program and its future. What FAmSCo has done, is planning.<br />
| Intermediate<br />
| [[User:eischmann|Jiri Eischmann]]<br />
|}<br />
<br />
{{anchor|lightning}}<!-- please don't remove this line --><br />
<br />
=== Lightning talks (Friday) ===<br />
<br />
We'll do lightning talks after lunch on Friday (depending on things). These talks are to be no longer than 5 minutes, at which point we will gong you out. '''Talk about what you are passionate about''', which doesn't have to necessarily be Fedora.<br />
<br />
If you're interested, list your proposed talk below. We have time for 10 talks, so please don't list your talk here if there are already 10.<br />
<br />
{|<br />
! Talk name<br />
! Talker<br />
! Comments<br />
|-<br />
| Texas Hold'em Poker for fun and profit: Learn how to play before the annual Fedora Poker Game<br />
| Robyn Bergeron<br />
| A super-quick overview of the rules of Texas Hold'em.<br />
|-<br />
| pkgwat and the Fedora Packages webapp<br />
| Ralph Bean<br />
| An introduction the Fedora Packages webapp and related tools.<br />
|-<br />
| fedocal: a calendar webapp for Fedora<br />
| Pierre-Yves Chibon<br />
| Short presentation to fedocal, a calendar web application for Fedora.<br />
|-<br />
| OpenLMI: The Open Linux Manageability Infrastructure<br />
| Stephen Gallagher<br />
| Short introduction to centralized manageability<br />
|-<br />
| Open Source Security<br />
| Eric Christensen<br />
| I'm looking for a few good hackers to help create developer training and resources.<br />
|-<br />
| Write docs without pain<br />
| Dan Allen<br />
| Intro to AsciiDoc, a lightweight alternative to writing docs without abandoning the DocBook toolchain.<br />
|-<br />
|}<br />
<br />
=== Hackfests (Saturday and Sunday) ===<br />
{|<br />
! Session name<br />
! Description<br />
! Time Needed <br />
! Lead<br />
|-<br />
| Ham Radio Test Session || Ham Radio Test Session For Attendees to get/upgrade their Licenses||3 hours ||Ben Williams<br />
|-<br />
| [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]] || Exchanging of GPG key fingerprints and identification to enable people to sign each other's keys||1 hour ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]] || ||1.5 hours ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Origin - Build Your Own PaaS]] || Build your own Open Source PaaS using Fedora and OpenShift Origin||3 hours || Troy Dawson (tdawson), Adam Miller (maxamillion)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Online - Deploy WebApps to the Cloud]] || Utilize the Hosted version of OpenShift to deploy and/or develop Applications in the Cloud for free! ||1.5 hours || Adam Miller (maxamillion), Troy Dawson (tdawson) <br />
|-<br />
| Features/scheduling revamp || Work on Feature process and release scheduling, blackboard needed ;-) || at least a few hours || Jaroslav Reznik (jreznik)<br />
|-<br />
| Meet your FESCo || Come and meet the men and women of the Fedora Engineering Steering Committee! || 30 minutes to an hour || Stephen Gallagher (sgallagh)<br />
|-<br />
| [https://github.com/herlo/ssh-gpg-smartcard-config GPG SmartCard Configuration] || Tips for setting up a gpg smartcard with Fedora. Two-factor SSH configuration, signing and encryption || 60-90 minutes (should happen before GPG Signing event) || [[User:Herlo|Clint Savage]]<br />
|-<br />
| [[FUDCon:Lawrence_2013_i18n_hackfest|i18n in Fedora]]: what's bad, what we broke in Fedora 18, how to fix it? || There's lots of badness in i18n configuration in Fedora, and it got worse between Fedora 17 and Fedora 18. Aim is to ensure everyone has a high-level understanding of what a good i18n config architecture would look like, and a low-level understanding of all the bits that are broken in Fedora 18+, and hopefully start some work on some of the low-hanging fruit. || Could run and run! || [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| Fedora Infrastructure Hackfest || will plan out specific tasks/areas saturday morning. See https://fedoraproject.org/wiki/Fedora_infrastructure_tasks_2013 for ideas container and lists. Everyone welcome to help/join in! || space both days would be nice || [[User:Kevin|Kevin Fenzi]] <br />
|-<br />
| Fedora ARM Hackfest || Board support hackfest, PA planning, ARMv[5678] direction, and growing community contributions || Space both days || Jon Masters (jonmasters), [[User:Ctyler|Chris Tyler]] (ctyler), [[User:blc|Brendan Conoboy]] (bconoboy) et al.<br />
|-<br />
| Marketing || Would like to have a group chat if there's interest. || 2-3 hours || [[User:rsuehle|Ruth Suehle]] <br />
|-<br />
| Fedora PPC Brainstorming || Topics at https://fedoraproject.org/wiki/Architectures/PowerPC/Meetings/FUDCon_Lawrence_2013 || Space both days || [[User:Karsten|Karsten Hopp]], et al.<br />
|-<br />
| Websites || Help improving the websites build scripts to avoid duplicates, human error and speed up the process! Plans [https://fedoraproject.org/wiki/Websites/workflow#The_Hot_.28comming.29_New_Websites_Arch here] − python & Makefiles hack|| both days.. || [[User:shaiton|Kévin Raymond]] <br />
|-<br />
| Static Analysis Hackfest || Let's build tools for automated [http://fedoraproject.org/wiki/StaticAnalysis static analysis of the code in Fedora] || Space both days || [[User:dmalcolm|Dave Malcolm]] <br />
|-<br />
| Fedora Cloud Image Generation and Automated Testing Hackfest || Let's get cloud image generation integrated into the releng process, and maybe automated nightly generation || Probably could use as much time as there is || [[User:mattdm|Matthew Miller]] + others from Cloud SIG and Rel Eng<br />
|-<br />
| Fedora JavaScript/Node.js Packaging Brainstorm || Now that Node.js is in Fedora, we need to set up some official packaging guidelines || Two hours either day || [[User:sgallagh|Stephen Gallagher]]<br />
|}<br />
<br />
==== Saturday, January 19 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]]<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]]<br />
|-<br />
|}<br />
<br />
==== Sunday, January 20 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || <br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || <br />
|-<br />
|}<br />
<br />
=== Social events ===<br />
<br />
==== Friday night gaming ====<br />
<br />
Bringing an awesome game? List it here so that we don't all put Carcassonne in our suitcases. <br />
<br />
* Carcassonne - [[User:Herlo|Clint Savage]]<br />
* [[FUDCon:Lawrence_2013_Poker|Poker Signup]] - Poker Cards & Chips - [[User:Herlo|Clint Savage]]<br />
* [http://boardgamegeek.com/boardgame/1234/once-upon-a-time Once Upon a Time] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/258/fluxx Fluxx] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/696/the-big-idea The Big Idea] - [[User:Sgallagh|Stephen Gallagher]]<br />
* Cards Against Humanity (+ Expansion 1) [[User:spot|Tom Callaway]] - Expansion 2 [[User:Jstanley|Jon Stanley]] - Holiday Expansion [[User:Ianweller|Ian Weller]] (if my roommate brings it back from Colorado)<br />
* Settlers of Catan - [[User:mattdm|Matthew Miller]]<br />
* [http://boardgamegeek.com/boardgame/31260/agricola Agricola] - [[User:mattdm|Matthew Miller]] (This is kind of a boardgaming commitment, so I'm only bringing it if at least one person e-mails me and says they're interested.)<br />
* Space: 1889 - [[User:jdulaney|John Dulaney]] If there is interest, let me know ahead of time so I know how many character sheets to print.<br />
* Arkham Horror with 2 expansions (king in yellow, goat in the woods)| [[User:jbwillia|Ben Williams]]<br />
* [http://www.atlas-games.com/product_tables/AG1100.php Lunch Money] with sticks and stones expansion - [[User:Tflink|Tim Flink]]<br />
<br />
==== FUDPub ====<br />
Wayne and Larry's, followed by bowling. <br />
933 Iowa St<br />
Lawrence, KS 66044<br />
785-856-7170 • 785-842-1234<br />
<br />
* There will be a pasta bar, toasted ravioli, chocolate chip cookies, and appropriate food for vegetarians. <br />
* Drinks alcoholic and non, bar is generously sponsored by Citrix from 6:30-8:30<br />
* We have the room to ourselves for buffet and bar from 6:30-8:30. At 9 p.m., there will be a band in the bar, which you're welcome to hang around for, or to go bowling next door.<br />
* Shuttles will return to the hotel from Wayne and Larry's at 8:30, 9:30 and 11:30.<br />
<br />
Want to go bowling after FUDPub? Add your name here so we can estimate lanes:<br />
<br />
* [[User:Suehle|Ruth Suehle]]<br />
* [[User:Herlo|Clint Savage]]<br />
* [[User:Adamwill|Adam Williamson]]<br />
* [[User:vicodan|Dan Mashal]]<br />
* [[User:Sgallagh|Stephen Gallagher]]<br />
* [[User:Pfrields|Paul Frields]]<br />
* [[User:jreznik|Jaroslav "The Dude" Reznik]]<br />
* [[User:eischmann|Jiri Eischmann]]<br />
* [[User:notting|Bill Nottingham]]<br />
* [[User:rdieter|Rex Dieter]]<br />
* [[User:ianweller|Ian Weller]]<br />
* [[User:graphitefriction|Sarah White]]<br />
* [[User:Jstanley|Jon Stanley]]<br />
* [[User:Baude|Brent Baude]]<br />
* [[User:hamzy|Mark Hamzy]]<br />
* [[User:Karsten|Karsten Hopp]]<br />
* [[User:pknirsch|Phil Knirsch]]<br />
* [[User:sparks|Eric Christensen]]<br />
* [[User:makfinsky|Ivan Makfinsky]]<br />
* [[User:AnnaE|Anna Eusebio]]<br />
* [[User:Zoglesby|Zach Oglesby]]<br />
* [[User:gholms|Garrett Holmstrom]]<br />
* [[User:Nb|Nick Bebout]]<br />
<br />
== Administration ==<br />
<br />
=== Planning meetings ===<br />
<br />
Meetings are currently not being held. We will start holding them again shortly before funding administration.<br />
<br />
Other useful pages:<br />
* [[/Budget]]<br />
* [[/Flights]] (when people are flying in; carpool planning)<br />
* [[/Booklet]]<br />
<br />
----<br />
<references/><br />
<br />
[[Category:FUDCon]]<br />
[[Category:Events]]<br />
[[Category:Events 2013]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=FUDCon:Lawrence_2013&diff=319311FUDCon:Lawrence 20132013-01-17T22:59:55Z<p>Mojavelinux: Added AsciiDoc lightning talk proposal</p>
<hr />
<div><div style="text-align: center; padding: 15px;">[[Image:Fudcon lawrence withdate.png]]</div><br />
<center>'''Lawrence, Kansas, USA :: January 18&ndash;20, 2013''' &mdash; General event owners: [[User:Rbergero|Robyn Bergeron]], [[User:Rsuehle|Ruth Suehle]], [[User:Ianweller|Ian Weller]]</center><br />
<br />
== Pre-registration ==<br />
<br />
<big>'''[http://fudconlawrence-ianweller.rhcloud.com/ Pre-register here]'''</big><br />
<br />
== Event details ==<br />
<br />
'''The 2013 North America FUDCon will be held in Lawrence, Kansas, on January 18&ndash;20, 2013.'''<br />
<br />
[[FUDCon]] is the Fedora Users and Developers Conference, a major free software event held in various regions around the world, usually annually per region. FUDCon is a combination of sessions, talks, workshops, and hackfests in which contributors work on specific initiatives. Topics include infrastructure, feature development, community building, general management and governance, marketing, testing and QA, packaging, etc.<br />
<br />
FUDCon is always free to attend for anyone in the world.<br />
<br />
=== Dates ===<br />
<br />
January 18&ndash;20, 2013 (Friday, Saturday, Sunday)<br />
<br />
=== Lodging ===<br />
<br />
SpringHill Suites<br/><br />
One Riverfront Plaza<br/><br />
Lawrence, KS 66044<br />
<br />
<br />
$119/night<br />
<br />
We have a block of rooms with two queens and some with only a king. Both types have foldout sofa beds as well. The block is available for the nights of Wednesday, Thursday, Friday, Saturday, and Sunday. '''Please reserve your room by December 21.''' Rooms include:<br />
<br />
* pull out sofa bed<br />
* mini fridge and microwave<br />
* free wifi<br />
* breakfast buffet<br />
<br />
The hotel has an indoor pool, gym, and business center with printing and faxing services available. <br />
<br />
Check-in time is 3:00 pm. Check-out time is 12:00 noon. Hotel is non-smoking.<br />
<br />
=== Transportation ===<br />
<br />
==== To and from Lawrence via airline ====<br />
<br />
[http://www.flykci.com/ Kansas City International] (IATA: MCI) is about a 60-minute drive from Lawrence.<br />
<br />
If you are flying to Kansas City to come to FUDCon, please add your name and flight information to the [[/Flights|flights page]]. We will organize car pools through that page.<br />
<br />
'''Airport shuttles'''<br />
<br />
''NOTE: IMPORTANT CHANGE IN PICKUP LOCATION''<br />
If you requested an airport shuttle, you should have received an email with the relevant information. Shuttles will be picking you up at TERMINAL B baggage claim. Look for a person holding from Redy2Party bus service holding a FUDCon sign. If your plane is early or late, simply look for the next arriving shuttle. <br />
<br />
If you did not request a shuttle, you may see if there is room on one when you land. The 4:15 p.m. and 10:15 p.m. shuttles are quite full. There will be shuttles on Thursday at:<br />
<br />
* 11 a.m.<br />
* 2:15 p.m.<br />
* 3:15 p.m.<br />
* 4:15 p.m.<br />
* 5:15 p.m.<br />
* 7:15 p.m.<br />
* 10:15 p.m.<br />
* 11:45 p.m.<br />
<br />
Departing from the FUDCon location on campus on Sunday:<br />
<br />
* 11 a.m.<br />
* 1 p.m. <br />
* 3 p.m.<br />
* 4 p.m.<br />
<br />
Departing from the hotel on Monday: <br />
<br />
* 8 a.m.<br />
* 12 p.m.<br />
* 2 p.m.<br />
<br />
<br />
==== To and from Lawrence via private plane ====<br />
[http://hetrickairservices.com/cgi-bin/p/w66p-airportinfo.cgi?d=hetrick-air-services-inc Lawrence Municipal Airport] (IATA: LWC) is about a 10-minute drive from Lawrence.<br />
<br />
==== To and from Lawrence via train ====<br />
Amtrak has a [http://www.amtrak.com/servlet/ContentServer?c=am2Station&pagename=am%2Fam2Station%2FStation_Page&cid=1229726268821 Lawrence station (LRC)].<br />
<br />
==== To and from Lawrence via car ====<br />
Lawrence is accessible via exits 202 and 204 on the Kansas Turnpike (Interstate 70).<br />
<br />
The Kansas Turnpike is a toll road. The toll from the Topeka entrance to Lawrence exit 202 is USD $1.00. The toll from the Kansas City-side entrance to Lawrence exit 204 is USD $1.60. For more information on the Kansas Turnpike, visit [http://www.ksturnpike.com/ www.ksturnpike.com].<br />
<br />
==== Within Lawrence ====<br />
Lawrence has [http://www.lawrencetransit.org/ public transportation] with routes covering most of the city and University of Kansas campus with a [http://www.lawrencetransit.org/pages/trip-planner trip planner] also available to assist with getting around town.<br />
<br />
=== Parking ===<br />
Information about parking on the University of Kansas campus can be found on the [http://www.parking.ku.edu/ KU Parking & Transit site].<br />
<br />
=== Network access ===<br />
<br />
TBA<br />
<br />
=== Packing List ===<br />
<br />
'''Everybody:'''<br />
* '''Appropriately warm clothing &mdash; [http://en.wikipedia.org/wiki/Lawrence,_Kansas#Climate it will possibly snow] in Kansas in January'''<br />
* Laptop with 802.11g wireless<br />
** Extension cord<br />
** Ethernet cable (for hotel and/or hackfest)<br />
** Optional: Bring a [http://fedorafriendfinder.org/ Fedora Friend Finder] (power strip)<br />
* Credit card (VISA or MasterCard) or small amount of cash<br />
* Your presentation slides or anything needed for the hackfest<br />
<br />
'''International visitors:'''<br />
* Passport/visa and any other official documentation needed<br />
* Converters for power ([http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets reference link]<ref>Most consumer plugs in the USA are Type B.</ref>)<br />
<br />
'''If staying at the hotel:'''<br />
* Optional: swimsuit, gym clothes.<ref>This doesn't mean clothing is optional if you swim or exercise!</ref><br />
<br />
== Agenda ==<br />
<br />
=== Shuttles from hotel to conference ===<br />
<br />
Shuttles will be leaving the hotel Friday, Saturday, and Sunday mornings beginning at 7:15 a.m. The last shuttle will leave at 8:15 a.m.<br />
<br />
=== General schedule ===<br />
<br />
* '''Friday, January 18:''' Introductory session, BarCamp sessions, lightning talks, and hotel party<br />
* '''Saturday, January 19 and Sunday, January 20''': Hackfests, FUDPub<br />
<br />
Rooms available in Learned hall, all three conference dates: 1131, 1136, 2111, 2112, 2133, 2148, 3150, 3152, 3153, 3154. Spahr Engineering Classroom is also available on all three dates.<br />
<br />
==== Thursday, January 17 ====<br />
<br />
Thursday evening at 8 pm., there is a global Raspberry Pi meetup over Google Hangout. MAKE is the host and guests are Matt Richardson and Shawn Wallace, authors of Getting Started with Raspberry Pi. All meetup attendees will receive a free PDF download of MAKE Magazine Volume 33. The guests will talk about the projects featured in the magazine and discuss everything Pi. There's a live chat where you can ask them questions as well as share your own projects. <br />
<br />
https://plus.google.com/+MAKE/posts<br />
<br />
We'd like to gather to join the Hangout and then hang out amongst ourselves talking Pi. Please add your name here if you'd like to join us so that we're sure to have enough room:<br />
<br />
* Ruth Suehle<br />
* Tom Callaway<br />
* Jeff Ollie<br />
* Chris Tyler<br />
* Emily Dirsh<br />
* Shyam Prasad<br />
* Ben Williams<br />
* Sarah White<br />
* Zach Oglesby<br />
* Nick Bebout<br />
<br />
==== Friday, January 18 ====<br />
<br />
This schedule is subject to approval. Talks will be assigned Friday morning during BarCamp voting. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
|colspan=6 style="text-align:center"| Plenary session: welcome, BarCamp pitches and voting, FPL talk (Spahr Engineering Classroom)<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
|colspan=6 style="text-align:center"| Lightning talks (Spahr Engineering Classroom)<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || ||<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || ||<br />
|-<br />
|}<br />
<br />
=== Technical sessions (Friday) ===<br />
<br />
As with all BarCamp conferences, technical sessions will be presented, voted on and scheduled the morning of the conference. If you like, you may list your session proposal below.<br />
<br />
{|<br />
! Session name<br />
! Description<br />
! User level<br />
! Lead<br />
|-<br />
| Creating SECure Linux Containers"<br />
| A quick overview on Containers<br />
| Intermediate<br />
| [[User:dwalsh|Dan Walsh]]<br />
|-<br />
| "SELinux for Mere Mortals"<br />
| An introduction to SELinux (it's not scary at all - you'll love it!)<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 1 - Systems Management"<br />
| Tips and tricks on managing systems with Spacewalk<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Spacewalk Power User Tips and Tricks Part 2 - Building Packages"<br />
| Tips and tricks on building packages for Fedora/RHEL - even if you don't have the source code.<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "Building a Software NAS using Gluster"<br />
| An introduction to Gluster<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "HA Clustering with Fedora"<br />
| How to set up a high availability application cluster using a shared filesystem with Fedora<br />
| Intermediate<br />
| [[User:tcameron|Thomas Cameron]]<br />
|-<br />
| "[http://fedmsg.com fedmsg] - What's in place and what's next."<br />
| A look at the past year of development and what exciting goodies are planned<br />
| Intermediate<br />
| [[User:Ralph|Ralph Bean]]<br />
|-<br />
| "An introduction to the new Anaconda"<br />
| Lots has changed about Anaconda in Fedora 18. This session is your handy guide to the new shiny.<br />
| All levels<br />
| [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| "EPEL (Extra Packages for Enterprise Linux) roundtable"<br />
| We need to hash out some proposals on handling overlaps and incompatible upgrades. <br />
| Any EPEL users/developers<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "HyperKitty, the next-generation Mailman archiver"<br />
| Learn about the new web-based user interface for mailing-list archives<br />
| All levels<br />
| [[User:Abompard|Aurélien Bompard]]<br />
|-<br />
| "Fedora Cloud Images for F19 and Beyond"<br />
| Let's plan what we're going to do to make our cloud images more useful to users.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Fedora Cloud Infrastructure Software in Fedora 19"<br />
| Develop plans and talk about OpenStack, OpenShift Origin, Eucalyptus, CloudStack, OpenNebula, and all the rest.<br />
| Intermediate<br />
| [[User:mattdm|Matthew Miller]]<br />
|-<br />
| "Everything you never wanted to know about Secure Boot and weren't afraid not to ask"<br />
| Discuss where we are with Secure Boot; Q&A.<br />
| All levels<br />
| [[User:Pjones|Peter Jones]]<br />
|-<br />
| Fedora Formulas Brainstorming session<br />
| Discuss if https://fedoraproject.org/wiki/Fedora_formulas is a viable thing to work on / make happen<br />
| All levels<br />
| [[User:Kevin|Kevin Fenzi]]<br />
|-<br />
| "ARM-building exercises: the new build platform for Fedora on ARM"<br />
| A demonstration of the Calxeda ECX-1000 server rapidly and reliably rebuilding FC for ARM<br />
| All levels<br />
| [[User:mlangsdorf|Mark Langsdorf]]<br />
|-<br />
| "COPRs - Fedora Ad-hoc package buildsystem"<br />
| A demonstration and technical explanation of the new copr buildsystem<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Ansible - Config Mgmt, Command/Control and RPC"<br />
| What fedora is doing with ansible and what you can be doing with it<br />
| All levels<br />
| [[User:skvidal|Seth Vidal]]<br />
|-<br />
| "Micro-web-framework, unit-tests and maintainable web-application"<br />
| What's interesting about micro-web-framework with regards to continuous integration and maintainability<br />
| All levels<br />
| [[User:pingou|Pierre-Yves Chibon (pingou)]]<br />
|-<br />
| Improving the FAmA (Fedora Ambassador Administration) Mentoring Process<br />
| Discussion on how to better manage mentoring, tips and tricks, share the current process and improve it. Plus educating current and potential mentors and manatees (mentees).<br />
| All levels<br />
| [[User:Herlo|Clint Savage]]<br />
|-<br />
| State of the Kernel<br />
| Current status, plans, and aspirations of the Fedora kernel team <br />
| Intermediate <br />
|[[User:Jforbes|Justin M. Forbes]]<br />
|-<br />
| Open Compute - why you should care (emphasis on Hardware Management track)<br />
| Current status of Facebook's Open Compute Project, how you can help<br />
| Intermediate<br />
| [[User:Jstanley|Jon Stanley]]<br />
|-<br />
| Pulp 2.0 - Enterprise Repository Management<br />
| Learn how to create and host repositories (yum, Puppet module), add custom content, and push install to large numbers of machines. Promote content through dev, test, and production repos.<br />
| Intermediate<br />
| [[User:mhrivnak|Michael Hrivnak]]<br />
|-<br />
| Apache CloudStack - Open Source Cloud Computing<br />
| Learn all about Apache CloudStack: What it is, what it does, and how it can be used to create/deploy an IaaS cloud.<br />
| Intermediate<br />
| [[User:jzb|Joe Brockmeier]]<br />
|-<br />
| Fedora Ambassadors - Present and the Future<br />
| A session to discuss the current state of FAm program and its future. What FAmSCo has done, is planning.<br />
| Intermediate<br />
| [[User:eischmann|Jiri Eischmann]]<br />
|}<br />
<br />
{{anchor|lightning}}<!-- please don't remove this line --><br />
<br />
=== Lightning talks (Friday) ===<br />
<br />
We'll do lightning talks after lunch on Friday (depending on things). These talks are to be no longer than 5 minutes, at which point we will gong you out. '''Talk about what you are passionate about''', which doesn't have to necessarily be Fedora.<br />
<br />
If you're interested, list your proposed talk below. We have time for 10 talks, so please don't list your talk here if there are already 10.<br />
<br />
{|<br />
! Talk name<br />
! Talker<br />
! Comments<br />
|-<br />
| Texas Hold'em Poker for fun and profit: Learn how to play before the annual Fedora Poker Game<br />
| Robyn Bergeron<br />
| A super-quick overview of the rules of Texas Hold'em.<br />
|-<br />
| pkgwat and the Fedora Packages webapp<br />
| Ralph Bean<br />
| An introduction the Fedora Packages webapp and related tools.<br />
|-<br />
| fedocal: a calendar webapp for Fedora<br />
| Pierre-Yves Chibon<br />
| Short presentation to fedocal, a calendar web application for Fedora.<br />
|-<br />
| OpenLMI: The Open Linux Manageability Infrastructure<br />
| Stephen Gallagher<br />
| Short introduction to centralized manageability<br />
|-<br />
| Open Source Security<br />
| Eric Christensen<br />
| I'm looking for a few good hackers to help create developer training and resources.<br />
|-<br />
| Write docs without pain<br />
| Dan Allen<br />
| An introduction to AsciiDoc, a lightweight alternative to doc writing without abandoning the DocBook toolchain.<br />
|-<br />
|}<br />
<br />
=== Hackfests (Saturday and Sunday) ===<br />
{|<br />
! Session name<br />
! Description<br />
! Time Needed <br />
! Lead<br />
|-<br />
| Ham Radio Test Session || Ham Radio Test Session For Attendees to get/upgrade their Licenses||3 hours ||Ben Williams<br />
|-<br />
| [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]] || Exchanging of GPG key fingerprints and identification to enable people to sign each other's keys||1 hour ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]] || ||1.5 hours ||Nick Bebout (nb)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Origin - Build Your Own PaaS]] || Build your own Open Source PaaS using Fedora and OpenShift Origin||3 hours || Troy Dawson (tdawson), Adam Miller (maxamillion)<br />
|-<br />
| [[FUDCon:Lawrence_2013_OpenShift_HackFests|OpenShift Online - Deploy WebApps to the Cloud]] || Utilize the Hosted version of OpenShift to deploy and/or develop Applications in the Cloud for free! ||1.5 hours || Adam Miller (maxamillion), Troy Dawson (tdawson) <br />
|-<br />
| Features/scheduling revamp || Work on Feature process and release scheduling, blackboard needed ;-) || at least a few hours || Jaroslav Reznik (jreznik)<br />
|-<br />
| Meet your FESCo || Come and meet the men and women of the Fedora Engineering Steering Committee! || 30 minutes to an hour || Stephen Gallagher (sgallagh)<br />
|-<br />
| [https://github.com/herlo/ssh-gpg-smartcard-config GPG SmartCard Configuration] || Tips for setting up a gpg smartcard with Fedora. Two-factor SSH configuration, signing and encryption || 60-90 minutes (should happen before GPG Signing event) || [[User:Herlo|Clint Savage]]<br />
|-<br />
| [[FUDCon:Lawrence_2013_i18n_hackfest|i18n in Fedora]]: what's bad, what we broke in Fedora 18, how to fix it? || There's lots of badness in i18n configuration in Fedora, and it got worse between Fedora 17 and Fedora 18. Aim is to ensure everyone has a high-level understanding of what a good i18n config architecture would look like, and a low-level understanding of all the bits that are broken in Fedora 18+, and hopefully start some work on some of the low-hanging fruit. || Could run and run! || [[User:Adamwill|Adam Williamson]]<br />
|-<br />
| Fedora Infrastructure Hackfest || will plan out specific tasks/areas saturday morning. See https://fedoraproject.org/wiki/Fedora_infrastructure_tasks_2013 for ideas container and lists. Everyone welcome to help/join in! || space both days would be nice || [[User:Kevin|Kevin Fenzi]] <br />
|-<br />
| Fedora ARM Hackfest || Board support hackfest, PA planning, ARMv[5678] direction, and growing community contributions || Space both days || Jon Masters (jonmasters), [[User:Ctyler|Chris Tyler]] (ctyler), [[User:blc|Brendan Conoboy]] (bconoboy) et al.<br />
|-<br />
| Marketing || Would like to have a group chat if there's interest. || 2-3 hours || [[User:rsuehle|Ruth Suehle]] <br />
|-<br />
| Fedora PPC Brainstorming || Topics at https://fedoraproject.org/wiki/Architectures/PowerPC/Meetings/FUDCon_Lawrence_2013 || Space both days || [[User:Karsten|Karsten Hopp]], et al.<br />
|-<br />
| Websites || Help improving the websites build scripts to avoid duplicates, human error and speed up the process! Plans [https://fedoraproject.org/wiki/Websites/workflow#The_Hot_.28comming.29_New_Websites_Arch here] − python & Makefiles hack|| both days.. || [[User:shaiton|Kévin Raymond]] <br />
|-<br />
| Static Analysis Hackfest || Let's build tools for automated [http://fedoraproject.org/wiki/StaticAnalysis static analysis of the code in Fedora] || Space both days || [[User:dmalcolm|Dave Malcolm]] <br />
|-<br />
| Fedora Cloud Image Generation and Automated Testing Hackfest || Let's get cloud image generation integrated into the releng process, and maybe automated nightly generation || Probably could use as much time as there is || [[User:mattdm|Matthew Miller]] + others from Cloud SIG and Rel Eng<br />
|-<br />
| Fedora JavaScript/Node.js Packaging Brainstorm || Now that Node.js is in Fedora, we need to set up some official packaging guidelines || Two hours either day || [[User:sgallagh|Stephen Gallagher]]<br />
|}<br />
<br />
==== Saturday, January 19 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance Event]]<br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || [[FUDCon:Lawrence_2013_GPG_Key_Signing_Event|GPG Key Signing Event]]<br />
|-<br />
|}<br />
<br />
==== Sunday, January 20 ====<br />
<br />
This schedule is subject to approval. All times are Central Standard Time (local time for Lawrence).<br />
<br />
{|width="100%"<br />
|-<br />
! Time !! Room A !! Room B !! Room C !! Room D !! Room E !! Room F<br />
|-<br />
! 09:00&ndash;10:15<br />
| || || || || ||<br />
|-<br />
! 10:30&ndash;11:20<br />
| || || || || ||<br />
|-<br />
! 11:30&ndash;12:20<br />
| || || || || ||<br />
|-<br />
! 12:30&ndash;13:20<br />
|colspan=6 style="text-align:center"| Lunch!<br />
|-<br />
! 13:30&ndash;14:20<br />
| || || || || ||<br />
|-<br />
! 14:30&ndash;15:20<br />
| || || || || ||<br />
|-<br />
! 15:30&ndash;16:20<br />
| || || || || || <br />
|-<br />
! 16:30&ndash;17:20<br />
| || || || || || <br />
|-<br />
|}<br />
<br />
=== Social events ===<br />
<br />
==== Friday night gaming ====<br />
<br />
Bringing an awesome game? List it here so that we don't all put Carcassonne in our suitcases. <br />
<br />
* Carcassonne - [[User:Herlo|Clint Savage]]<br />
* [[FUDCon:Lawrence_2013_Poker|Poker Signup]] - Poker Cards & Chips - [[User:Herlo|Clint Savage]]<br />
* [http://boardgamegeek.com/boardgame/1234/once-upon-a-time Once Upon a Time] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/258/fluxx Fluxx] - [[User:Sgallagh|Stephen Gallagher]]<br />
* [http://boardgamegeek.com/boardgame/696/the-big-idea The Big Idea] - [[User:Sgallagh|Stephen Gallagher]]<br />
* Cards Against Humanity (+ Expansion 1) [[User:spot|Tom Callaway]] - Expansion 2 [[User:Jstanley|Jon Stanley]] - Holiday Expansion [[User:Ianweller|Ian Weller]] (if my roommate brings it back from Colorado)<br />
* Settlers of Catan - [[User:mattdm|Matthew Miller]]<br />
* [http://boardgamegeek.com/boardgame/31260/agricola Agricola] - [[User:mattdm|Matthew Miller]] (This is kind of a boardgaming commitment, so I'm only bringing it if at least one person e-mails me and says they're interested.)<br />
* Space: 1889 - [[User:jdulaney|John Dulaney]] If there is interest, let me know ahead of time so I know how many character sheets to print.<br />
* Arkham Horror with 2 expansions (king in yellow, goat in the woods)| [[User:jbwillia|Ben Williams]]<br />
* [http://www.atlas-games.com/product_tables/AG1100.php Lunch Money] with sticks and stones expansion - [[User:Tflink|Tim Flink]]<br />
<br />
==== FUDPub ====<br />
Wayne and Larry's, followed by bowling. <br />
933 Iowa St<br />
Lawrence, KS 66044<br />
785-856-7170 • 785-842-1234<br />
<br />
* There will be a pasta bar, toasted ravioli, chocolate chip cookies, and appropriate food for vegetarians. <br />
* Drinks alcoholic and non, bar is generously sponsored by Citrix from 6:30-8:30<br />
* We have the room to ourselves for buffet and bar from 6:30-8:30. At 9 p.m., there will be a band in the bar, which you're welcome to hang around for, or to go bowling next door.<br />
* Shuttles will return to the hotel from Wayne and Larry's at 8:30, 9:30 and 11:30.<br />
<br />
Want to go bowling after FUDPub? Add your name here so we can estimate lanes:<br />
<br />
* [[User:Suehle|Ruth Suehle]]<br />
* [[User:Herlo|Clint Savage]]<br />
* [[User:Adamwill|Adam Williamson]]<br />
* [[User:vicodan|Dan Mashal]]<br />
* [[User:Sgallagh|Stephen Gallagher]]<br />
* [[User:Pfrields|Paul Frields]]<br />
* [[User:jreznik|Jaroslav "The Dude" Reznik]]<br />
* [[User:eischmann|Jiri Eischmann]]<br />
* [[User:notting|Bill Nottingham]]<br />
* [[User:rdieter|Rex Dieter]]<br />
* [[User:ianweller|Ian Weller]]<br />
* [[User:graphitefriction|Sarah White]]<br />
* [[User:Jstanley|Jon Stanley]]<br />
* [[User:Baude|Brent Baude]]<br />
* [[User:hamzy|Mark Hamzy]]<br />
* [[User:Karsten|Karsten Hopp]]<br />
* [[User:pknirsch|Phil Knirsch]]<br />
* [[User:sparks|Eric Christensen]]<br />
* [[User:makfinsky|Ivan Makfinsky]]<br />
* [[User:AnnaE|Anna Eusebio]]<br />
* [[User:Zoglesby|Zach Oglesby]]<br />
* [[User:gholms|Garrett Holmstrom]]<br />
* [[User:Nb|Nick Bebout]]<br />
<br />
== Administration ==<br />
<br />
=== Planning meetings ===<br />
<br />
Meetings are currently not being held. We will start holding them again shortly before funding administration.<br />
<br />
Other useful pages:<br />
* [[/Budget]]<br />
* [[/Flights]] (when people are flying in; carpool planning)<br />
* [[/Booklet]]<br />
<br />
----<br />
<references/><br />
<br />
[[Category:FUDCon]]<br />
[[Category:Events]]<br />
[[Category:Events 2013]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/Fedora_Java_Marketing_Brief&diff=299655Java/Fedora Java Marketing Brief2012-08-28T04:21:11Z<p>Mojavelinux: </p>
<hr />
<div>This page outlines the plan to make Fedora the preferred environment of choice for Java and JVM platform development. Achieving this goal is one of the objectives of the [[SIGs/Java|Fedora Java SIG]] and is attainable thanks to the hard work done by that group and other contributors to Fedora.<br />
<br />
{{admon/important|Working Draft|This document is a working draft. The content is currently under review. If you have ideas on how to improve it, we welcome your input. Feel free to offer corrections or discuss the content on the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing mailinglist] (or on the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailinglist] if it relates to a more technical subject).}}<br />
<br />
If you are just interested in the key points, refer to the first section, TL;DR.<br />
<br />
== TL;DR ==<br />
<br />
* Java is one of the most popular languages (#2 @ Tiobe Index, #5 @ github, #1 @ sourceforge)<br />
* ~ 8 million Java developers<br />
* JVM supports many other languages, which means even more developers<br />
* < 1% of these developers use Fedora<br />
* Fedora Java SIG has made creating Java packages easy, consistent w/ packaging guidelines<br />
* Fedora has the latest and most popular stuff on the JVM platform, including Java 7 (OpenJDK), Eclipse 4.2, Maven 3, JBoss AS 7, Tomcat 7 and JBoss Tools<br />
* A Fedora Java Spin is in the works<br />
* Fedora should be the operating system of choice for JVM platform developers!<br />
<br />
== Market size ==<br />
<br />
There are roughly 8 million Java developers worldwide [http://java.dzone.com/articles/how-many-java-developers-are], a significant pool of users to target that could make Fedora their preferred development platform. But this story isn't just about the Java language. It's about what runs on the Java Virtual Machine (JVM), Java bytecode. Java bytecode is an intermediate language typically compiled from Java, but can also be compiled from other languages. The JVM supports a wide array of languages in addition to Java [http://en.wikipedia.org/wiki/List_of_JVM_languages], including Groovy, Scala, Clojure (flavor of LISP), JRuby (Ruby), Jython (Python) and Rhino (JavaScript). The Java Virtual Machine is available for all major operating systems and the same code can run anywhere, so its painless for JVM platform developers to switch to Linux.<br />
<br />
All the major JVM languages are already available in Fedora today. Several of those languages are drop-in replacements for their C-based counterparts. Groovy has become the scripting language of choice on the Java platform and there are a lot of amazing tools based on it. Now consider that JRuby can run almost all Ruby frameworks, most notably Rails, which could attract enough developers to easily dwarf Groovy. Thus, the number of "JVM platform developers" (and those that could migrate to it) extends well beyond the 8 million Java developers.<br />
<br />
== Timing ==<br />
<br />
The JVM is more than a decade old, so why is this runtime interesting now? There are two key reasons, performance and packaging support.<br />
<br />
=== Performance ===<br />
<br />
The JVM can execute code faster than any other runtime. This is particularly noticable for long-running processes like web and enterprise servers and the applications that run on them. As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is "invokedynamic".<br />
<br />
"invokedynamic" [http://jcp.org/en/jsr/detail?id=292] is a recent change that demonstrates the JVM is being optimized to better support dynamic languages such as Groovy, Ruby, Clojure and JavaScript. Not only will these languages run faster, it makes the JVM a common runtime (i.e., melting pot) for programs written in these languages to interoperate seamlessly. It allows you to chose the right language for the right task. In otherwords, the JVM is an ideal polyglot runtime.<br />
<br />
Above all, the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection facilities and multi-threading support, plus general stability, make it an absolute winner.<br />
<br />
=== Packaging ===<br />
<br />
The biggest challenge to getting Java applications packaged for Fedora is due to a culture clash. Most modern Java applications rely on pre-built binary libraries that are retrieved from one or more remote repositories. As far as the Fedora packaging guidelines are concerned, these repositories, and what they contain, cannot be trusted. Therefore, it's necessary to ensure that the dependencies are built in addition to the application.<br />
<br />
Members of the Fedora Java SIG [https://fedoraproject.org/wiki/SIGs/Java] made a breakthrough when they figured out a way to the build tools so that they would map and resolve dependencies from the system instead of reaching out to the internet to grab them. This change also drastically reduced the effort to create a package for a Java application. For Maven project, it's just a matter of using mvn-rpmbuild instead of mvn to build the project. There are complements for other build tools as well, including Gradle and Leiningin. Utilities from the JPackage Project, which defines standard file system locations and conventions for use in Java packages, handle many other tasks necessary to create a Java package. The door is wide open now to bring the Java ecosystem to Fedora.<br />
<br />
What developers dig more than language runtimes are tools. Tools to develop. Tools to compile. Tools to deploy.<br />
<br />
== Tools ==<br />
<br />
Eclipse is by far the most popular Integrated Development Environment (IDE) among Java developers, accounting for more than two-thirds of the market [http://files.zeroturnaround.com/developer-productivity-report/zeroturnaround-developer-productivity-report-2012.pdf]. Fedora was the first distribution to package Eclipse 4.2 (Juno), the latest release. Ironically, the urgency to package it was not driven by packagers with an interest in Java, but rather the Linux Tools [http://overholt.ca/wp/?p=392]. Either way, this is a force multiplier for Fedora Java. <br />
<br />
Out of the momentum to package Eclipse 4.2 spawned a Google Summer of Code (GSoC) project to prepare a Fedora Java Spin [http://blog.grdryn.me/tag/gsoc-2/]. During the course of the summer the student, Gerard Ryan, packaged a large portion of JBoss Tools, a collection of Eclipse plugins aimed at Java EE development. The momentum to get Eclipse and other JVM applications packaged wouldn't have been possible without the efforts and support of the Fedora Java SIG.<br />
<br />
The other reason the Eclipse packages are so important is because they solve a major pain point of Eclipse, getting updates. Eclipse has a built-in updated manager that is notoriously slow and error prone. As a result, most developers are running outdated versions of Eclipse, foregoing bug and security fixes. By allowing the package manager to handle updates, developers can keep their IDE updated and not even have to worry about when it happens or how long it takes.<br />
<br />
== Application Servers ==<br />
<br />
A majority of Java developers are creating web applications and middleware, which run inside application servers. They are most likely deploying it to a data center or cloud environment, but the need to be able to test it locally for rapid development. That's why it's critical to be able to easily install an application server. The most popular application servers, JBoss AS, Tomcat and Jetty, are all packaged in Fedora.<br />
<br />
JBoss AS 7 is the most promising because it is as fast and simple as Tomcat, but supports many additional enterprise features and is more efficient, especially at increased scale. It can also accomodate multiple instances (clones). Instances that are setup inside the developer's home directory can be run without elevated priviledges. These features make it well suited for both development and production. Fedora is the only distribution which has a package for JBoss AS 7.<br />
<br />
== Adoption ==<br />
<br />
Fedora has the potential to be an ideal development platform for Java developers. The packages are there, but the opportunity is virtually untapped. Max Andersen, lead of the JBoss Tools project, recently analyzed two years of statistics collected by JBoss Tools pingbacks [https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users]. The statistics show that Windows is still the dominant platform for Java development, accounting for 84% of the market. Out of the 12% of the users on Linux, only 10% run Fedora (close to 80% run Ubuntu). Java 7 only recently rose above 20% usage, with Java 6 still the most widely adopted runtime. The most surprising statistic is that there are three times as many Linux users as Mac OSX. Linux hasn't lost that battle yet.<br />
<br />
== New in F18 ==<br />
<br />
* Gradle, build automation evolved, upgraded to 1.0, repackaged and build against system Java libraries<br />
* JBoss Tools, a suite of plugins for Eclipse that cater to Java EE development and cloud deployment<br />
* JPA functionality with support for multiple providers added to JBoss AS (Hibernate 3 and OpenJPA 2.2)<br />
* Leinengen, the build tool for Clojure, built using system Java libraries<br />
* Clojure libraries and frameworks, including Korma and Noir<br />
* Clojure environemnt for Vim (VimClojure)<br />
<br />
== Recap ==<br />
<br />
'''The pool of Java developers is large.'''<br />
<br />
''Fedora has the goods to appeal to them.'' Many of the tools that Java developers already know and love are available right out of the box in Fedora, including the latest version of Java (OpenJDK 7), the latest version of Eclipse (Eclipse 4.2), all the major JVM languages and the dominant build tool (Maven 3). A developer workstation that would take hours or even days to build with Windows or Mac OS X can be installed on Fedora and running in less than an hour, thanks to yum and the great OSS software that Fedora has built and packaged. There's even a Fedora Java Spin in the works that caters to these developers [https://gitorious.org/fedora-jboss-spin/kickstart/]<br />
<br />
'''The pool of Java developers remains largely untapped.'''<br />
<br />
''It's time to let them know about it.'' Let them see how ideal it is. Let them know how much time it will save them. If they can't install it on their machine, we should encourage them to use it in a virtual machine. We just need to get them to try it to realize that '''''Fedora is an ideal environment for Java and JVM platform development.'''''</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/Fedora_Java_Marketing_Brief&diff=299654Java/Fedora Java Marketing Brief2012-08-28T04:20:00Z<p>Mojavelinux: </p>
<hr />
<div>This page outlines the plan to make Fedora the preferred environment of choice for Java and JVM platform development. Achieving this goal is one of the objectives of the [[SIGs/Java|Fedora Java SIG]] and is attainable thanks to the hard work done by that group and other contributors to Fedora.<br />
<br />
{{admon/important|Working Draft|This document is a working draft. The content is currently under review. If you have ideas on how to improve it, we welcome your input. Feel free to offer corrections or discuss the content on the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing mailinglist] (or on the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailinglist] if it relates to a more technical subject).}}<br />
<br />
If you are just interested in the key points, refer to the first section, TL;DR.<br />
<br />
== TL;DR ==<br />
<br />
* Java is one of the most popular languages (#2 @ Tiobe Index, #5 @ github, #1 @ sourceforge)<br />
* ~ 8 million Java developers<br />
* JVM supports many other languages, which means even more developers<br />
* < 1% of these developers use Fedora<br />
* Fedora Java SIG has made creating Java packages easy, consistent w/ packaging guidelines<br />
* Fedora has the latest and most popular stuff on the JVM platform, including Java 7 (OpenJDK), Eclipse 4.2, Maven 3, JBoss AS 7, Tomcat 7 and JBoss Tools<br />
* A Fedora Java Spin is in the works<br />
* Fedora should be the operating system of choice for JVM platform developers!<br />
<br />
== Market size ==<br />
<br />
There are roughly 8 million Java developers worldwide [http://java.dzone.com/articles/how-many-java-developers-are], a significant pool of users to target that could make Fedora their preferred development platform. But this story isn't just about the Java language. It's about what runs on the Java Virtual Machine (JVM), Java bytecode. Java bytecode is an intermediate language typically compiled from Java, but can also be compiled from other languages. The JVM supports a wide array of languages in addition to Java [http://en.wikipedia.org/wiki/List_of_JVM_languages], including Groovy, Scala, Clojure (flavor of LISP), JRuby (Ruby), Jython (Python) and Rhino (JavaScript). The Java Virtual Machine is available for all major operating systems and the same code can run anywhere, so its painless for JVM platform developers to switch to Linux.<br />
<br />
All the major JVM languages are already available in Fedora today. Several of those languages are drop-in replacements for their C-based counterparts. Groovy has become the scripting language of choice on the Java platform and there are a lot of amazing tools based on it. Now consider that JRuby can run almost all Ruby frameworks, most notably Rails, which could attract enough developers to easily dwarf Groovy. Thus, the number of "JVM platform developers" (and those that could migrate to it) extends well beyond the 8 million Java developers.<br />
<br />
== Timing ==<br />
<br />
The JVM is more than a decade old, so why is this runtime interesting now? There are two key reasons, performance and packaging support.<br />
<br />
=== Performance ===<br />
<br />
The JVM can execute code faster than any other runtime. This is particularly noticable for long-running processes like web and enterprise servers and the applications that run on them. As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is "invokedynamic".<br />
<br />
"invokedynamic" [http://jcp.org/en/jsr/detail?id=292] is a recent change that demonstrates the JVM is being optimized to better support dynamic languages such as Groovy, Ruby, Clojure and JavaScript. Not only will these languages run faster, it makes the JVM a common runtime (i.e., melting pot) for programs written in these languages to interoperate seamlessly. It allows you to chose the right language for the right task. In otherwords, the JVM is an ideal polyglot runtime.<br />
<br />
Above all, the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection facilities and multi-threading support, plus general stability, make it an absolute winner.<br />
<br />
=== Packaging ===<br />
<br />
The biggest challenge to getting Java applications packaged for Fedora is due to a culture clash. Most modern Java applications rely on pre-built binary libraries that are retrieved from one or more remote repositories. As far as the Fedora packaging guidelines are concerned, these repositories, and what they contain, cannot be trusted. Therefore, it's necessary to ensure that the dependencies are built in addition to the application.<br />
<br />
Members of the Fedora Java SIG [https://fedoraproject.org/wiki/SIGs/Java] made a breakthrough when they figured out a way to the build tools so that they would map and resolve dependencies from the system instead of reaching out to the internet to grab them. This change also drastically reduced the effort to create a package for a Java application. For Maven project, it's just a matter of using mvn-rpmbuild instead of mvn to build the project. There are complements for other build tools as well, including Gradle and Leiningin. Utilities from the JPackage Project, which defines standard file system locations and conventions for use in Java packages, handle many other tasks necessary to create a Java package. The door is wide open now to bring the Java ecosystem to Fedora.<br />
<br />
What developers dig more than language runtimes are tools. Tools to develop. Tools to compile. Tools to deploy.<br />
<br />
== Tools ==<br />
<br />
Eclipse is by far the most popular Integrated Development Environment (IDE) among Java developers, accounting for more than two-thirds of the market [http://files.zeroturnaround.com/developer-productivity-report/zeroturnaround-developer-productivity-report-2012.pdf]. Fedora was the first distribution to package Eclipse 4.2 (Juno), the latest release. Ironically, the urgency to package it was not driven by packagers with an interest in Java, but rather the Linux Tools [http://overholt.ca/wp/?p=392]. Either way, this is a force multiplier for Fedora Java. <br />
<br />
Out of the momentum to package Eclipse 4.2 spawned a Google Summer of Code (GSoC) project to prepare a Fedora Java Spin [http://blog.grdryn.me/tag/gsoc-2/]. During the course of the summer the student, Gerard Ryan, packaged a large portion of JBoss Tools, a collection of Eclipse plugins aimed at Java EE development. The momentum to get Eclipse and other JVM applications packaged wouldn't have been possible without the efforts and support of the Fedora Java SIG.<br />
<br />
The other reason the Eclipse packages are so important is because they solve a major pain point of Eclipse, getting updates. Eclipse has a built-in updated manager that is notoriously slow and error prone. As a result, most developers are running outdated versions of Eclipse, foregoing bug and security fixes. By allowing the package manager to handle updates, developers can keep their IDE updated and not even have to worry about when it happens or how long it takes.<br />
<br />
== Application Servers ==<br />
<br />
A majority of Java developers are creating web applications and middleware, which run inside application servers. They are most likely deploying it to a data center or cloud environment, but the need to be able to test it locally for rapid development. That's why it's critical to be able to easily install an application server. The most popular application servers, JBoss AS, Tomcat and Jetty, are all packaged in Fedora.<br />
<br />
JBoss AS 7 is the most promising because it is as fast and simple as Tomcat, but supports many additional enterprise features and is more efficient, especially at increased scale. It can also accomodate multiple instances (clones). Instances that are setup inside the developer's home directory can be run without elevated priviledges. These features make it well suited for both development and production. Fedora is the only distribution which has a package for JBoss AS 7.<br />
<br />
== Adoption ==<br />
<br />
Fedora has the potential to be an ideal development platform for Java developers. The packages are there, but the opportunity is virtually untapped. Max Andersen, lead of the JBoss Tools project, recently analyzed two years of statistics collected by JBoss Tools pingbacks [https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users]. The statistics show that Windows is still the dominant platform for Java development, accounting for 84% of the market. Out of the 12% of the users on Linux, only 10% run Fedora (close to 80% run Ubuntu). Java 7 only recently rose above 20% usage, with Java 6 still the most widely adopted runtime. The most surprising statistic is that there are three times as many Linux users as Mac OSX. Linux hasn't lost that battle yet.<br />
<br />
== New in F18 ==<br />
<br />
* Gradle, build automation evolved, upgraded to 1.0, repackaged and configured to use the system Java libraries<br />
* JBoss Tools, a suite of plugins for Eclipse that cater to Java EE development and cloud deployment<br />
* JPA functionality with support for multiple providers added to JBoss AS (Hibernate 3 and OpenJPA 2.2)<br />
* Leinengen, the build tool for Clojure, configured to use the system Java libraries<br />
* Clojure libraries and frameworks, including Korma and Noir<br />
* Clojure environemnt for Vim (VimClojure)<br />
<br />
== Recap ==<br />
<br />
'''The pool of Java developers is large.'''<br />
<br />
''Fedora has the goods to appeal to them.'' Many of the tools that Java developers already know and love are available right out of the box in Fedora, including the latest version of Java (OpenJDK 7), the latest version of Eclipse (Eclipse 4.2), all the major JVM languages and the dominant build tool (Maven 3). A developer workstation that would take hours or even days to build with Windows or Mac OS X can be installed on Fedora and running in less than an hour, thanks to yum and the great OSS software that Fedora has built and packaged. There's even a Fedora Java Spin in the works that caters to these developers [https://gitorious.org/fedora-jboss-spin/kickstart/]<br />
<br />
'''The pool of Java developers remains largely untapped.'''<br />
<br />
''It's time to let them know about it.'' Let them see how ideal it is. Let them know how much time it will save them. If they can't install it on their machine, we should encourage them to use it in a virtual machine. We just need to get them to try it to realize that '''''Fedora is an ideal environment for Java and JVM platform development.'''''</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/Fedora_Java_Marketing_Brief&diff=299653Java/Fedora Java Marketing Brief2012-08-28T04:17:01Z<p>Mojavelinux: </p>
<hr />
<div>This page outlines the plan to make Fedora the preferred environment of choice for Java and JVM platform development. Achieving this goal is one of the objectives of the [[SIGs/Java|Fedora Java SIG]] and is attainable thanks to the hard work done by that group and other contributors to Fedora.<br />
<br />
{{admon/important|Working Draft|This document is a working draft. The content is currently under review. If you have ideas on how to improve it, we welcome your input. Feel free to offer corrections or discuss the content on the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing mailinglist] (or on the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailinglist] if it relates to a more technical subject).}}<br />
<br />
If you are just interested in the key points, refer to the first section, TL;DR.<br />
<br />
== TL;DR ==<br />
<br />
* Java is one of the most popular languages (#2 @ Tiobe Index, #5 @ github, #1 @ sourceforge)<br />
* ~ 8 million Java developers<br />
* JVM supports many other languages, which means even more developers<br />
* < 1% of these developers use Fedora<br />
* Fedora Java SIG has made creating Java packages easy, consistent w/ packaging guidelines<br />
* Fedora has the latest and most popular stuff on the JVM platform, including Java 7 (OpenJDK), Eclipse 4.2, Maven 3, JBoss AS 7, Tomcat 7 and JBoss Tools<br />
* A Fedora Java Spin is in the works<br />
* Fedora should be the operating system of choice for JVM platform developers!<br />
<br />
== Market size ==<br />
<br />
There are roughly 8 million Java developers worldwide [http://java.dzone.com/articles/how-many-java-developers-are], a significant pool of users to target that could make Fedora their preferred development platform. But this story isn't just about the Java language. It's about what runs on the Java Virtual Machine (JVM), Java bytecode. Java bytecode is an intermediate language typically compiled from Java, but can also be compiled from other languages. The JVM supports a wide array of languages in addition to Java [http://en.wikipedia.org/wiki/List_of_JVM_languages], including Groovy, Scala, Clojure (flavor of LISP), JRuby (Ruby), Jython (Python) and Rhino (JavaScript). The Java Virtual Machine is available for all major operating systems and the same code can run anywhere, so its painless for JVM platform developers to switch to Linux.<br />
<br />
All the major JVM languages are already available in Fedora today. Several of those languages are drop-in replacements for their C-based counterparts. Groovy has become the scripting language of choice on the Java platform and there are a lot of amazing tools based on it. Now consider that JRuby can run almost all Ruby frameworks, most notably Rails, which could attract enough developers to easily dwarf Groovy. Thus, the number of "JVM platform developers" (and those that could migrate to it) extends well beyond the 8 million Java developers.<br />
<br />
== Timing ==<br />
<br />
The JVM is more than a decade old, so why is this runtime interesting now? There are two key reasons, performance and packaging support.<br />
<br />
=== Performance ===<br />
<br />
The JVM can execute code faster than any other runtime. This is particularly noticable for long-running processes like web and enterprise servers and the applications that run on them. As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is "invokedynamic".<br />
<br />
"invokedynamic" [http://jcp.org/en/jsr/detail?id=292] is a recent change that demonstrates the JVM is being optimized to better support dynamic languages such as Groovy, Ruby, Clojure and JavaScript. Not only will these languages run faster, it makes the JVM a common runtime (i.e., melting pot) for programs written in these languages to interoperate seamlessly. It allows you to chose the right language for the right task. In otherwords, the JVM is an ideal polyglot runtime.<br />
<br />
Above all, the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection facilities and multi-threading support, plus general stability, make it an absolute winner.<br />
<br />
=== Packaging ===<br />
<br />
The biggest challenge to getting Java applications packaged for Fedora is due to a culture clash. Most modern Java applications rely on pre-built binary libraries that are retrieved from one or more remote repositories. As far as the Fedora packaging guidelines are concerned, these repositories, and what they contain, cannot be trusted. Therefore, it's necessary to ensure that the dependencies are built in addition to the application.<br />
<br />
Members of the Fedora Java SIG [https://fedoraproject.org/wiki/SIGs/Java] made a breakthrough when they figured out a way to the build tools so that they would map and resolve dependencies from the system instead of reaching out to the internet to grab them. This change also drastically reduced the effort to create a package for a Java application. For Maven project, it's just a matter of using mvn-rpmbuild instead of mvn to build the project. There are complements for other build tools as well, including Gradle and Leiningin. Utilities from the JPackage Project, which defines standard file system locations and conventions for use in Java packages, handle many other tasks necessary to create a Java package. The door is wide open now to bring the Java ecosystem to Fedora.<br />
<br />
What developers dig more than language runtimes are tools. Tools to develop. Tools to compile. Tools to deploy.<br />
<br />
== Tools ==<br />
<br />
Eclipse is by far the most popular Integrated Development Environment (IDE) among Java developers, accounting for more than two-thirds of the market [http://files.zeroturnaround.com/developer-productivity-report/zeroturnaround-developer-productivity-report-2012.pdf]. Fedora was the first distribution to package Eclipse 4.2 (Juno), the latest release. Ironically, the urgency to package it was not driven by packagers with an interest in Java, but rather the Linux Tools [http://overholt.ca/wp/?p=392]. Either way, this is a force multiplier for Fedora Java. <br />
<br />
Out of the momentum to package Eclipse 4.2 spawned a Google Summer of Code (GSoC) project to prepare a Fedora Java Spin. During the course of the summer the student, Gerard Ryan, packaged a large portion of JBoss Tools, a collection of Eclipse plugins aimed at Java EE development. The momentum to get Eclipse and other JVM applications packaged wouldn't have been possible without the efforts and support of the Fedora Java SIG.<br />
<br />
The other reason the Eclipse packages are so important is because they solve a major pain point of Eclipse, getting updates. Eclipse has a built-in updated manager that is notoriously slow and error prone. As a result, most developers are running outdated versions of Eclipse, foregoing bug and security fixes. By allowing the package manager to handle updates, developers can keep their IDE updated and not even have to worry about when it happens or how long it takes.<br />
<br />
== Application Servers ==<br />
<br />
A majority of Java developers are creating web applications and middleware, which run inside application servers. They are most likely deploying it to a data center or cloud environment, but the need to be able to test it locally for rapid development. That's why it's critical to be able to easily install an application server. The most popular application servers, JBoss AS, Tomcat and Jetty, are all packaged in Fedora.<br />
<br />
JBoss AS 7 is the most promising because it is as fast and simple as Tomcat, but supports many additional enterprise features and is more efficient, especially at increased scale. It can also accomodate multiple instances (clones). Instances that are setup inside the developer's home directory can be run without elevated priviledges. These features make it well suited for both development and production. Fedora is the only distribution which has a package for JBoss AS 7.<br />
<br />
== Adoption ==<br />
<br />
Fedora has the potential to be an ideal development platform for Java developers. The packages are there, but the opportunity is virtually untapped. Max Andersen, lead of the JBoss Tools project, recently analyzed two years of statistics collected by JBoss Tools pingbacks [https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users]. The statistics show that Windows is still the dominant platform for Java development, accounting for 84% of the market. Out of the 12% of the users on Linux, only 10% run Fedora (close to 80% run Ubuntu). Java 7 only recently rose above 20% usage, with Java 6 still the most widely adopted runtime. The most surprising statistic is that there are three times as many Linux users as Mac OSX. Linux hasn't lost that battle yet.<br />
<br />
== New in F18 ==<br />
<br />
* Gradle, build automation evolved, upgraded to 1.0, repackaged and configured to use the system Java libraries<br />
* JBoss Tools, a suite of plugins for Eclipse that cater to Java EE development and cloud deployment<br />
* JPA functionality with support for multiple providers added to JBoss AS (Hibernate 3 and OpenJPA 2.2)<br />
* Leinengen, the build tool for Clojure, configured to use the system Java libraries<br />
* Clojure libraries and frameworks, including Korma and Noir<br />
* Clojure environemnt for Vim (VimClojure)<br />
<br />
== Recap ==<br />
<br />
'''The pool of Java developers is large.'''<br />
<br />
''Fedora has the goods to appeal to them.'' Many of the tools that Java developers already know and love are available right out of the box in Fedora, including the latest version of Java (OpenJDK 7), the latest version of Eclipse (Eclipse 4.2), all the major JVM languages and the dominant build tool (Maven 3). A developer workstation that would take hours or even days to build with Windows or Mac OS X can be installed on Fedora and running in less than an hour, thanks to yum and the great OSS software that Fedora has built and packaged. There's even a Fedora Java Spin in the works that caters to these developers.<br />
<br />
'''The pool of Java developers remains largely untapped.'''<br />
<br />
''It's time to let them know about it.'' Let them see how ideal it is. Let them know how much time it will save them. If they can't install it on their machine, we should encourage them to use it in a virtual machine. We just need to get them to try it to realize that '''''Fedora is an ideal environment for Java and JVM platform development.'''''</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/FedoraJavaMarketingBrief&diff=299652Java/FedoraJavaMarketingBrief2012-08-28T04:11:23Z<p>Mojavelinux: Mojavelinux moved page Java/FedoraJavaMarketingBrief to Java/Fedora Java Marketing Brief: Use underscores in title</p>
<hr />
<div>#REDIRECT [[Java/Fedora Java Marketing Brief]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/Fedora_Java_Marketing_Brief&diff=299651Java/Fedora Java Marketing Brief2012-08-28T04:11:20Z<p>Mojavelinux: Mojavelinux moved page Java/FedoraJavaMarketingBrief to Java/Fedora Java Marketing Brief: Use underscores in title</p>
<hr />
<div>This page outlines the plan to make Fedora the preferred environment of choice for Java and JVM platform development. Achieving this goal is one of the objectives of the [[SIGs/Java|Fedora Java SIG]] and is attainable thanks to the hard work done by that group and other contributors to Fedora.<br />
<br />
{{admon/important|Working Draft|This document is a working draft. The content is currently under review. If you have ideas on how to improve it, we welcome your input. Feel free to offer corrections or discuss the content on the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing mailinglist] (or on the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailinglist] if it relates to a more technical subject).}}<br />
<br />
If you are just interested in the key points, refer to the first section, TL;DR.<br />
<br />
== TL;DR ==<br />
<br />
* Java is one of the most popular languages (#2 @ Tiobe Index, #5 @ github, #1 @ sourceforge)<br />
* ~ 8 million Java developers<br />
* JVM supports many other languages, which means even more developers<br />
* ~ 1% use Fedora<br />
* Fedora Java SIG has made creating Java packages easy, consistent w/ packaging guidelines<br />
* Fedora has the latest and most popular stuff on the JVM platform, including Java 7 (OpenJDK), Eclipse 4.2, Maven 3, JBoss AS 7, Tomcat 7 and JBoss Tools<br />
* A Fedora Java Spin is in the works<br />
* Fedora should be the operating system of choice for JVM platform developers!<br />
<br />
== Market size ==<br />
<br />
There are roughly 8 million Java developers worldwide [http://java.dzone.com/articles/how-many-java-developers-are], a significant pool of users to target that could make Fedora their preferred development platform. But this story isn't just about the Java language. It's about what runs on the Java Virtual Machine (JVM), Java bytecode. Java bytecode is an intermediate language typically compiled from Java, but can also be compiled from other languages. The JVM supports a wide array of languages in addition to Java [http://en.wikipedia.org/wiki/List_of_JVM_languages], including Groovy, Scala, Clojure (flavor of LISP), JRuby (Ruby), Jython (Python) and Rhino (JavaScript). The Java Virtual Machine is available for all major operating systems and the same code can run anywhere, so its painless for JVM platform developers to switch to Linux.<br />
<br />
All the major JVM languages are already available in Fedora today. Several of those languages are drop-in replacements for their C-based counterparts. Groovy has become the scripting language of choice on the Java platform and there are a lot of amazing tools based on it. Now consider that JRuby can run almost all Ruby frameworks, most notably Rails, which could attract enough developers to easily dwarf Groovy. Thus, the number of "JVM platform developers" (and those that could migrate to it) extends well beyond the 8 million Java developers.<br />
<br />
== Timing ==<br />
<br />
The JVM is more than a decade old, so why is this runtime interesting now? There are two key reasons, performance and packaging support.<br />
<br />
=== Performance ===<br />
<br />
The JVM can execute code faster than any other runtime. This is particularly noticable for long-running processes like web and enterprise servers and the applications that run on them. As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is "invokedynamic".<br />
<br />
"invokedynamic" [http://jcp.org/en/jsr/detail?id=292] is a recent change that demonstrates the JVM is being optimized to better support dynamic languages such as Groovy, Ruby, Clojure and JavaScript. Not only will these languages run faster, it makes the JVM a common runtime (i.e., melting pot) for programs written in these languages to interoperate seamlessly. It allows you to chose the right language for the right task. In otherwords, the JVM is an ideal polyglot runtime.<br />
<br />
Above all, the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection facilities and multi-threading support, plus general stability, make it an absolute winner.<br />
<br />
=== Packaging ===<br />
<br />
The biggest challenge to getting Java applications packaged for Fedora is due to a culture clash. Most modern Java applications rely on pre-built binary libraries that are retrieved from one or more remote repositories. As far as the Fedora packaging guidelines are concerned, these repositories, and what they contain, cannot be trusted. Therefore, it's necessary to ensure that the dependencies are built in addition to the application.<br />
<br />
Members of the Fedora Java SIG [https://fedoraproject.org/wiki/SIGs/Java] made a breakthrough when they figured out a way to the build tools so that they would map and resolve dependencies from the system instead of reaching out to the internet to grab them. This change also drastically reduced the effort to create a package for a Java application. For Maven project, it's just a matter of using mvn-rpmbuild instead of mvn to build the project. There are complements for other build tools as well, including Gradle and Leiningin. Utilities from the JPackage Project, which defines standard file system locations and conventions for use in Java packages, handle many other tasks necessary to create a Java package. The door is wide open now to bring the Java ecosystem to Fedora.<br />
<br />
What developers dig more than language runtimes are tools. Tools to develop. Tools to compile. Tools to deploy.<br />
<br />
== Tools ==<br />
<br />
Eclipse is by far the most popular Integrated Development Environment (IDE) among Java developers, accounting for more than two-thirds of the market [http://files.zeroturnaround.com/developer-productivity-report/zeroturnaround-developer-productivity-report-2012.pdf]. Fedora was the first distribution to package Eclipse 4.2 (Juno), the latest release. Ironically, the urgency to package it was not driven by packagers with an interest in Java, but rather the Linux Tools [http://overholt.ca/wp/?p=392]. Either way, this is a force multiplier for Fedora Java. <br />
<br />
Out of the momentum to package Eclipse 4.2 spawned a Google Summer of Code (GSoC) project to prepare a Fedora Java Spin. During the course of the summer the student, Gerard Ryan, packaged a large portion of JBoss Tools, a collection of Eclipse plugins aimed at Java EE development. The momentum to get Eclipse and other JVM applications packaged wouldn't have been possible without the efforts and support of the Fedora Java SIG.<br />
<br />
The other reason the Eclipse packages are so important is because they solve a major pain point of Eclipse, getting updates. Eclipse has a built-in updated manager that is notoriously slow and error prone. As a result, most developers are running outdated versions of Eclipse, foregoing bug and security fixes. By allowing the package manager to handle updates, developers can keep their IDE updated and not even have to worry about when it happens or how long it takes.<br />
<br />
== Application Servers ==<br />
<br />
A majority of Java developers are creating web applications and middleware, which run inside application servers. They are most likely deploying it to a data center or cloud environment, but the need to be able to test it locally for rapid development. That's why it's critical to be able to easily install an application server. The most popular application servers, JBoss AS, Tomcat and Jetty, are all packaged in Fedora.<br />
<br />
JBoss AS 7 is the most promising because it is as fast and simple as Tomcat, but supports many additional enterprise features and is more efficient, especially at increased scale. It can also accomodate multiple instances (clones). Instances that are setup inside the developer's home directory can be run without elevated priviledges. These features make it well suited for both development and production. Fedora is the only distribution which has a package for JBoss AS 7.<br />
<br />
== Adoption ==<br />
<br />
Fedora has the potential to be an ideal development platform for Java developers. The packages are there, but the opportunity is virtually untapped. Max Andersen, lead of the JBoss Tools project, recently analyzed two years of statistics collected by JBoss Tools pingbacks [https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users]. The statistics show that Windows is still the dominant platform for Java development, accounting for 84% of the market. Out of the 12% of the users on Linux, only 10% run Fedora (close to 80% run Ubuntu). Java 7 only recently rose above 20% usage, with Java 6 still the most widely adopted runtime. The most surprising statistic is that there are three times as many Linux users as Mac OSX. Linux hasn't lost that battle yet.<br />
<br />
== New in F18 ==<br />
<br />
* Gradle, build automation evolved, upgraded to 1.0, repackaged and configured to use the system Java libraries<br />
* JBoss Tools, a suite of plugins for Eclipse that cater to Java EE development and cloud deployment<br />
* JPA functionality with support for multiple providers added to JBoss AS (Hibernate 3 and OpenJPA 2.2)<br />
* Leinengen, the build tool for Clojure, configured to use the system Java libraries<br />
* Clojure libraries and frameworks, including Korma and Noir<br />
* Clojure environemnt for Vim (VimClojure)<br />
<br />
== Recap ==<br />
<br />
'''The pool of Java developers is large.'''<br />
<br />
''Fedora has the goods to appeal to them.'' Many of the tools that Java developers already know and love are available right out of the box in Fedora, including the latest version of Java (OpenJDK 7), the latest version of Eclipse (Eclipse 4.2), all the major JVM languages and the dominant build tool (Maven 3). A developer workstation that would take hours or even days to build with Windows or Mac OS X can be installed on Fedora and running in less than an hour, thanks to yum and the great OSS software that Fedora has built and packaged. There's even a Fedora Java Spin in the works that caters to these developers.<br />
<br />
'''The pool of Java developers remains largely untapped.'''<br />
<br />
''It's time to let them know about it.'' Let them see how ideal it is. Let them know how much time it will save them. If they can't install it on their machine, we should encourage them to use it in a virtual machine. We just need to get them to try it to realize that '''''Fedora is an ideal environment for Java and JVM platform development.'''''</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java/Fedora_Java_Marketing_Brief&diff=299650Java/Fedora Java Marketing Brief2012-08-28T04:08:08Z<p>Mojavelinux: Initial draft of Fedora Java Marketing Brief</p>
<hr />
<div>This page outlines the plan to make Fedora the preferred environment of choice for Java and JVM platform development. Achieving this goal is one of the objectives of the [[SIGs/Java|Fedora Java SIG]] and is attainable thanks to the hard work done by that group and other contributors to Fedora.<br />
<br />
{{admon/important|Working Draft|This document is a working draft. The content is currently under review. If you have ideas on how to improve it, we welcome your input. Feel free to offer corrections or discuss the content on the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing mailinglist] (or on the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailinglist] if it relates to a more technical subject).}}<br />
<br />
If you are just interested in the key points, refer to the first section, TL;DR.<br />
<br />
== TL;DR ==<br />
<br />
* Java is one of the most popular languages (#2 @ Tiobe Index, #5 @ github, #1 @ sourceforge)<br />
* ~ 8 million Java developers<br />
* JVM supports many other languages, which means even more developers<br />
* ~ 1% use Fedora<br />
* Fedora Java SIG has made creating Java packages easy, consistent w/ packaging guidelines<br />
* Fedora has the latest and most popular stuff on the JVM platform, including Java 7 (OpenJDK), Eclipse 4.2, Maven 3, JBoss AS 7, Tomcat 7 and JBoss Tools<br />
* A Fedora Java Spin is in the works<br />
* Fedora should be the operating system of choice for JVM platform developers!<br />
<br />
== Market size ==<br />
<br />
There are roughly 8 million Java developers worldwide [http://java.dzone.com/articles/how-many-java-developers-are], a significant pool of users to target that could make Fedora their preferred development platform. But this story isn't just about the Java language. It's about what runs on the Java Virtual Machine (JVM), Java bytecode. Java bytecode is an intermediate language typically compiled from Java, but can also be compiled from other languages. The JVM supports a wide array of languages in addition to Java [http://en.wikipedia.org/wiki/List_of_JVM_languages], including Groovy, Scala, Clojure (flavor of LISP), JRuby (Ruby), Jython (Python) and Rhino (JavaScript). The Java Virtual Machine is available for all major operating systems and the same code can run anywhere, so its painless for JVM platform developers to switch to Linux.<br />
<br />
All the major JVM languages are already available in Fedora today. Several of those languages are drop-in replacements for their C-based counterparts. Groovy has become the scripting language of choice on the Java platform and there are a lot of amazing tools based on it. Now consider that JRuby can run almost all Ruby frameworks, most notably Rails, which could attract enough developers to easily dwarf Groovy. Thus, the number of "JVM platform developers" (and those that could migrate to it) extends well beyond the 8 million Java developers.<br />
<br />
== Timing ==<br />
<br />
The JVM is more than a decade old, so why is this runtime interesting now? There are two key reasons, performance and packaging support.<br />
<br />
=== Performance ===<br />
<br />
The JVM can execute code faster than any other runtime. This is particularly noticable for long-running processes like web and enterprise servers and the applications that run on them. As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is "invokedynamic".<br />
<br />
"invokedynamic" [http://jcp.org/en/jsr/detail?id=292] is a recent change that demonstrates the JVM is being optimized to better support dynamic languages such as Groovy, Ruby, Clojure and JavaScript. Not only will these languages run faster, it makes the JVM a common runtime (i.e., melting pot) for programs written in these languages to interoperate seamlessly. It allows you to chose the right language for the right task. In otherwords, the JVM is an ideal polyglot runtime.<br />
<br />
Above all, the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection facilities and multi-threading support, plus general stability, make it an absolute winner.<br />
<br />
=== Packaging ===<br />
<br />
The biggest challenge to getting Java applications packaged for Fedora is due to a culture clash. Most modern Java applications rely on pre-built binary libraries that are retrieved from one or more remote repositories. As far as the Fedora packaging guidelines are concerned, these repositories, and what they contain, cannot be trusted. Therefore, it's necessary to ensure that the dependencies are built in addition to the application.<br />
<br />
Members of the Fedora Java SIG [https://fedoraproject.org/wiki/SIGs/Java] made a breakthrough when they figured out a way to the build tools so that they would map and resolve dependencies from the system instead of reaching out to the internet to grab them. This change also drastically reduced the effort to create a package for a Java application. For Maven project, it's just a matter of using mvn-rpmbuild instead of mvn to build the project. There are complements for other build tools as well, including Gradle and Leiningin. Utilities from the JPackage Project, which defines standard file system locations and conventions for use in Java packages, handle many other tasks necessary to create a Java package. The door is wide open now to bring the Java ecosystem to Fedora.<br />
<br />
What developers dig more than language runtimes are tools. Tools to develop. Tools to compile. Tools to deploy.<br />
<br />
== Tools ==<br />
<br />
Eclipse is by far the most popular Integrated Development Environment (IDE) among Java developers, accounting for more than two-thirds of the market [http://files.zeroturnaround.com/developer-productivity-report/zeroturnaround-developer-productivity-report-2012.pdf]. Fedora was the first distribution to package Eclipse 4.2 (Juno), the latest release. Ironically, the urgency to package it was not driven by packagers with an interest in Java, but rather the Linux Tools [http://overholt.ca/wp/?p=392]. Either way, this is a force multiplier for Fedora Java. <br />
<br />
Out of the momentum to package Eclipse 4.2 spawned a Google Summer of Code (GSoC) project to prepare a Fedora Java Spin. During the course of the summer the student, Gerard Ryan, packaged a large portion of JBoss Tools, a collection of Eclipse plugins aimed at Java EE development. The momentum to get Eclipse and other JVM applications packaged wouldn't have been possible without the efforts and support of the Fedora Java SIG.<br />
<br />
The other reason the Eclipse packages are so important is because they solve a major pain point of Eclipse, getting updates. Eclipse has a built-in updated manager that is notoriously slow and error prone. As a result, most developers are running outdated versions of Eclipse, foregoing bug and security fixes. By allowing the package manager to handle updates, developers can keep their IDE updated and not even have to worry about when it happens or how long it takes.<br />
<br />
== Application Servers ==<br />
<br />
A majority of Java developers are creating web applications and middleware, which run inside application servers. They are most likely deploying it to a data center or cloud environment, but the need to be able to test it locally for rapid development. That's why it's critical to be able to easily install an application server. The most popular application servers, JBoss AS, Tomcat and Jetty, are all packaged in Fedora.<br />
<br />
JBoss AS 7 is the most promising because it is as fast and simple as Tomcat, but supports many additional enterprise features and is more efficient, especially at increased scale. It can also accomodate multiple instances (clones). Instances that are setup inside the developer's home directory can be run without elevated priviledges. These features make it well suited for both development and production. Fedora is the only distribution which has a package for JBoss AS 7.<br />
<br />
== Adoption ==<br />
<br />
Fedora has the potential to be an ideal development platform for Java developers. The packages are there, but the opportunity is virtually untapped. Max Andersen, lead of the JBoss Tools project, recently analyzed two years of statistics collected by JBoss Tools pingbacks [https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users]. The statistics show that Windows is still the dominant platform for Java development, accounting for 84% of the market. Out of the 12% of the users on Linux, only 10% run Fedora (close to 80% run Ubuntu). Java 7 only recently rose above 20% usage, with Java 6 still the most widely adopted runtime. The most surprising statistic is that there are three times as many Linux users as Mac OSX. Linux hasn't lost that battle yet.<br />
<br />
== New in F18 ==<br />
<br />
* Gradle, build automation evolved, upgraded to 1.0, repackaged and configured to use the system Java libraries<br />
* JBoss Tools, a suite of plugins for Eclipse that cater to Java EE development and cloud deployment<br />
* JPA functionality with support for multiple providers added to JBoss AS (Hibernate 3 and OpenJPA 2.2)<br />
* Leinengen, the build tool for Clojure, configured to use the system Java libraries<br />
* Clojure libraries and frameworks, including Korma and Noir<br />
* Clojure environemnt for Vim (VimClojure)<br />
<br />
== Recap ==<br />
<br />
'''The pool of Java developers is large.'''<br />
<br />
''Fedora has the goods to appeal to them.'' Many of the tools that Java developers already know and love are available right out of the box in Fedora, including the latest version of Java (OpenJDK 7), the latest version of Eclipse (Eclipse 4.2), all the major JVM languages and the dominant build tool (Maven 3). A developer workstation that would take hours or even days to build with Windows or Mac OS X can be installed on Fedora and running in less than an hour, thanks to yum and the great OSS software that Fedora has built and packaged. There's even a Fedora Java Spin in the works that caters to these developers.<br />
<br />
'''The pool of Java developers remains largely untapped.'''<br />
<br />
''It's time to let them know about it.'' Let them see how ideal it is. Let them know how much time it will save them. If they can't install it on their machine, we should encourage them to use it in a virtual machine. We just need to get them to try it to realize that '''''Fedora is an ideal environment for Java and JVM platform development.'''''</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Java&diff=299649Java2012-08-28T03:37:20Z<p>Mojavelinux: </p>
<hr />
<div>= Java on Fedora =<br />
<br />
Fedora uses a Free software stack that consists of [http://en.wikipedia.org/wiki/Openjdk OpenJDK], GNU Compiler for Java, GNU Classpath and the Eclipse Java compiler to provide Java support. See our [[Java/FAQ]] for more information on that. Note that AOT compilation using GCJ has been deprecated (made optional) and new or updated packages will be built using OpenJDK to produce regular Java bytecode.<br />
<br />
Software mentioned on this page may come in different packaging formats. Fedora's own packages (''RPM'') are easy to install (''with [[Yum]]'') and installation instructions can be found from [[Docs/Drafts/SoftwareManagementGuide]]. Third party packages may be in archive formats (.zip, tar) for which case-specific instructions should be provided.<br />
<br />
= Terminology =<br />
<br />
In Java context, terms may be a bit confusing for newcomers. '''JRE''' (''Java Runtime Environment'') stands for ''virtual machine'', which is able to run Java programs.<br />
<br />
'''JDK''' (''Java Development Kit'') or '''SDK''' (''Software Developmenet Kit'') is needed to develop Java programs. Many SDK packages these days also ship JRE, or to confuse more, no separate JRE is provided and thus terminal installations are supposed to include the development environment.<br />
<br />
Terms '''AOT''' (''[http://en.wikipedia.org/wiki/AOT_compiler Ahead of Time]]''), '''SE''', '''J2EE''' need some more explanation.<br />
<br />
<br />
= Java Runtime Environments (JRE) =<br />
<br />
Java's history is well known to consist different JRE implementations and wide variety of combinations which work together. Different implementations can be installed simultaneously to Fedora and activated one at the time. Activation is done using the [[Alternatives]] system (''also used to change some other subsystems''). Java's subsystem name is surprisingly ''java'' and typical commands include:<br />
<pre># alternatives --display java</pre><br />
<pre># alternatives --config java</pre><br />
<br />
See alternative's own documentation for more information for usage and parts involved.<br />
<br />
Should be noted that JRE implementations installed outside Fedora distribution, may not support alternatives and thus not be visible there. Then the symbolic links under directory ''/etc/alternatives'' must be manually fixed.<br />
<br />
== OpenJDK and project IcedTea ==<br />
Fedora has shipped OpenJDK as default JRE implementation since Fedora release 9. It's based on Sun Microsystem's [http://en.wikipedia.org/wiki/JavaOne JavaOne] open source release and complemented by Red Hat's [http://en.wikipedia.org/wiki/IcedTea IcedTea] project that implements the missing third party components that Sun could not release under free License.<br />
<br />
OpenJDK's '''java.library.path''', shared librarary paths for i386 are:<br />
<pre><br />
/usr/lib<br />
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/<br />
</pre><br />
<br />
and for x86_64:<br />
<pre><br />
/usr/lib64<br />
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/<br />
</pre><br />
<br />
OpenJDK package name on Fedora is ''java-1.6.0-openjdk''.<br />
<br />
== GNU GCJ+GIJ for Java ==<br />
The GNU Project's Java compiler and interpreter implementations provide a working JRE environment. [http://en.wikipedia.org/wiki/Gcj GCJ] is a Java compiler that produces bytecode for Java virtual machine [http://en.wikipedia.org/wiki/GNU_Interpreter_for_Java GIJ].<br />
<br />
GCJ JRE package on Fedora is ''java-1.5.0-gcj''.<br />
<br />
<br />
== Oracle's Java SE ==<br />
Original Oracle's Java SE (Standard Edition) can be downloaded directly from [http://www.java.com/en/download/ http://www.java.com/en/download/] and installed manually.<br />
<br />
You're, however, encouraged to try out the OpenJDK runtime first.<br />
<br />
== Apache Harmony ==<br />
<br />
''Please add your knowledge about [http://en.wikipedia.org/wiki/Apache_Harmony Harmony] and Fedora.''<br />
<br />
<br />
== Troubleshooting JRE ==<br />
<br />
Fedora's JRE in browser environment can be tested using the following test pages:<br />
* [http://www.java.com/en/download/help/testvm.xml http://www.java.com/en/download/help/testvm.xml]<br />
* [http://java.com/en/download/installed.jsp?detect=jre&try=1 http://java.com/en/download/installed.jsp?detect=jre&try=1]<br />
<br />
If these don't work, proceed with [[Java/Troubleshooting]] page.<br />
<br />
= Java Develoment Tools (SDK) =<br />
<br />
The following SDKs are listed in alphabetic order.<br />
<br />
== Eclipse ==<br />
<br />
See our [[Eclipse]] page for an integrated development environment platform that itself is written in Java and has plugin support for many programming languages.<br />
<br />
== IntelliJ IDEA ==<br />
<br />
IntelliJ IDEA is considered by many the ultimate Java development environment. A commercial project for many years, IntelliJ IDEA became open-source in 2009 by releasing<br />
the IntelliJ IDEA Community Edition. It's part of the Fedora packages and can easily the installed with yum. IntelliJ is written in Java, features a portable Swing UI and is extensible via plugins.<br />
<br />
== Maven ==<br />
<br />
Fedora includes a somewhat customized version of Maven in the distribution. The customization is purely to make Maven work well in offline mode with the rest of the system. Details on how packagers can use this customized Maven are located at [[Java/JPPMavenReadme]] . We are in the process of upgrading from maven2 2.0.4 to maven2 2.0.8 (ETA = F12). Once that is achieved we will proceed immediately to maven2 2.0.9 and then to 2.0.10. The reason for going by steps is that it is easier to bootstrap a maven2 release from the previous one. Also related to maven2, a feasibility study is being performed to change the installation of Java packages to become a valid maven2 repository. We will no longer have to modify maven2 (not even with our small patch), and it wil be easier to support parallel installation of either "legacy" or "progressive" versions of Java packages. Once some positive results are obtained, it will be discussed on the fedora-devel-java-list.<br />
<br />
== NetBeans IDE ==<br />
<br />
The "reference" Java IDE, developed for many years by Sun(now Oracle). NetBeans is written in Java, features a portable Swing UI, out of the box support for many Java tools and frameworks and it's extensible via plugins.<br />
<br />
= Java Server Side Environments = <br />
<br />
== Apache Tomcat ==<br />
Fedora ships [http://en.wikipedia.org/wiki/Apache_Tomcat Apache Tomcat] as part of standard distribution.<br />
<br />
Apache Tomcat package name on Fedora is ''tomcat6''.<br />
<br />
== JBoss AS ==<br />
<br />
The [[SIGs/Java|Java SIG]] is working on packaging [http://jboss.org/as7 JBoss AS 7], along with a minimal set of required JARs, to make this open-source Java EE application server available as a service in Fedora.<br />
<br />
You can learn more about the effort and the current progress on the [[JBossAS7|JBoss AS 7 on Fedora]] page.<br />
<br />
[[JBossAS7_in_Fedora_marketing_collateral|Talking points]] about JBoss AS 7 on Fedora 17 are available and are used to create marketing cards and information sheets.<br />
<br />
= Teaching and Learning Java =<br />
<br />
As part of planning and implementing new 100% FLOSS Java components into Fedora, this draft document has been opened to give developers a place to teach each other about best practices, patterns, etc.<br />
<br />
[[Docs/Drafts/JavaProgramming]]<br />
[[Category:Language-specific_SIGs]]<br />
<br />
<br />
= Open Issues with Java packages =<br />
* [https://bugzilla.redhat.com/buglist.cgi?component=java-1.6.0-openjdk&product=Fedora&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&order=bugs.votes,bugs.bug_id java-1.6.0-openjdk]<br />
* [https://bugzilla.redhat.com/buglist.cgi?component=java-1.5.0-gcj&product=Fedora&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&order=bugs.votes,bugs.bug_id java-1.5.0-gcj]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=azureus Azureus] <br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=erlang erlang]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=itext itext]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=jakarta-commons-cli jakarta-commons-cli]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=jogl JOGL]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=kawa kawa]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=pdftk PDFTK]<br />
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=plplot plplot]<br />
<br />
= Communicate =<br />
<br />
You can subscribe to [https://admin.fedoraproject.org/mailman/listinfo/java-devel java-devel list] or talk to us in [irc://irc.freenode.net/fedora-java #fedora-java] Freenode IRC channel. Read [[Communicate]] page for more information.<br />
<br />
= See Also = <br />
* [[Java/FAQ]]<br />
* [[Java/Troubleshooting]]<br />
* [[Java/PKIAppletCompatibility]]<br />
* [[Java/StackTraces]]<br />
* [[Java/JPPMavenReadme]]<br />
* [[Java/FedoraJavaMarketingBrief]]<br />
* [[Docs/Drafts/JavaProgramming]]<br />
* [[Packaging:Java]]<br />
* [[SIGs/Java]]<br />
<br />
= References =<br />
* [http://openjdk.java.net/ OpenJDK Home]<br />
* [https://bugs.openjdk.java.net/ OpenJDK bug tracking system]<br />
* [http://icedtea.classpath.org/ IcedTea Home page]<br />
* [http://icedtea.classpath.org/bugzilla/ IcedTea bug tracking system]<br />
* [http://tomcat.apache.org/ Apache Tomcat]<br />
* [http://java-source.net/open-source/web-servers Java web servers]<br />
* [http://en.wikipedia.org/wiki/JBoss_application_server JBoss application server]<br />
* [http://www.jboss.org/ JBoss Home page]<br />
* [http://www.redhat.com/magazine/012oct05/features/java/ Red Hat Magazine article about java from 2005]<br />
* [http://developer.classpath.org/ http://developer.classpath.org/] <br />
* [http://jpackage.org/ Jpackage.org]<br />
* [http://www.marketwire.com/press-release/Oracle-and-IBM-Collaborate-to-Accelerate-Java-Innovation-Through-OpenJDK-NASDAQ-ORCL-1332855.htm IBM joins to OpenJDK project]<br />
<br />
[[Category:Java]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Talk:How_to_create_and_use_a_Live_CD&diff=298384Talk:How to create and use a Live CD2012-08-13T03:05:57Z<p>Mojavelinux: fix links to fedora hosted git repositories</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
<noinclude><br />
[[Category:Spins]]<br />
[[Category:LiveMedia]]<br />
</noinclude><br />
<br />
== Introduction ==<br />
<br />
This page explains how to make a custom-content Live CD or DVD on Fedora-based systems including derived distributions such as RHEL, CentOS and others. <br />
<br />
If you simply want to burn a pre-made ISO to a disc, visit http://fedoraproject.org/en/get-fedora to download a LiveCD or LiveDVD, then see the [http://docs.fedoraproject.org/install-guide/ install guide] or [http://docs.fedoraproject.org/readme-burning-isos/ burning how-to] for further instructions.<br />
<br />
See the [[FedoraLiveCD | project wiki]] for more details. Discussion of this project takes places at http://admin.fedoraproject.org/mailman/listinfo/livecd.<br />
<br />
== Instructions ==<br />
<br />
The basic workflow for creating a remix is:<br />
<br />
# Create a kickstart file that specifies the packages you want installed on your remix, along with special settings you want to tweak.<br />
# Run that kickstart file through livecd-creator, which will pull in the packages and compose an .iso, which you can then burn to CD.<br />
<br />
...that's it! We will walk you through these steps below.<br />
<br />
=== Install the necessary software ===<br />
<br />
To create a live image, the '''livecd-creator''' tool is used. Super user privileges are needed. The tool is more or less self-documenting, use the ''--help'' option to see options.<br />
<br />
The '''livecd-creator''' tool is part of the <code>livecd-tools</code> package. If it is not installed on your system, add it with:<br />
<br />
su -c 'yum install livecd-tools spin-kickstarts'<br />
<br />
If you are interested in localized live cd files, install also '''l10n-kickstarts'''.<br />
<br />
su -c 'yum install l10n-kickstarts'<br />
<br />
=== Choose a kickstart file as a base for your remix ===<br />
<br />
Kickstart files are configuration files. They contain settings for tools, such as:<br />
<br />
* [https://fedorahosted.org/pungi/ pungi] (for the creation of install disks), <br />
* [http://git.fedorahosted.org/cgit/livecd/ livecd-creator] (for the creation of live images) <br />
* [[Anaconda|anaconda]] (the built-in installer)<br />
<br />
You can see examples of kickstart files in the [http://git.fedorahosted.org/cgit/spin-kickstarts.git spin-kickstart repository]. These are the kickstart files for the spins displayed at http://spins.fedoraproject.org.<br />
<br />
Since we are creating a LiveCD, we want a kickstart file for livecd-creator. Chances are good that an existing LiveCD kickstart already contains most of the things we need, like a graphical dekstop environment, drivers, and the ability to make live images persistent (for installation on a liveUSB rather than a liveCD). Therefore, in order to avoid reinventing the wheel, we're going to start by picking an existing kickstart for a LiveCD to base our remix's kickstart from.<br />
<br />
There are currently two kickstart files that provide the main configuration to setup the live images. Pick one of these two:<br />
<br />
* [http://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-live-base.ks fedora-live-base.ks]: The file used for most composes. If you don't know where to start, this is a good default choice.<br />
* [http://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-live-mini.ks fedora-live-mini.ks]: A trimmed-down edition of the first file, mostly used by the Mini SIG for size-sensitive purposes. If space-saving is a primary concern, choose this one.<br />
<br />
=== Set up your environment ===<br />
<br />
Now we'll set up the place you'll be building your remix's image file in. We assume you're running a recent version of Fedora. <br />
<br />
First, make a 'remix' folder in your home directory.<br />
<br />
cd<br />
mkdir remix<br />
cd remix<br />
<br />
Now, download the kickstart files for the Fedora Spins:<br />
<br />
su -c ‘yum install fedora-kickstarts’<br />
<br />
Set SELinux in permissive mode.<br />
<br />
su -c ‘setenforce 0’<br />
<br />
Copy the kickstart file you've chosen to the current directory.<br />
<br />
cp /usr/share/spin-kickstarts/fedora-live-base.ks .<br />
<br />
or <br />
<br />
cp /usr/share/spin-kickstarts/fedora-live-mini.ks .<br />
<br />
(depending on the one you've chosen).<br />
<br />
=== Create a kickstart file ===<br />
<br />
# Create an empty text document in the editor of your choice.<br />
# Import the base kickstart file you chose above:<br />
<br />
<code>%include fedora-live-base.ks</code><br />
<br />
# Create the package manifest section and add your favorite packages:<br />
<br />
<code><br />
%packages<br />
foo<br />
baz<br />
bar<br />
%end<br />
</code><br />
<br />
# Congrats -- you're done!<br />
<br />
=== Build the image ===<br />
<br />
You'll need the livecd-creator tool. Go and install it as root:<br />
<br />
* yum install livecd-creator<br />
<br />
The build process will take some time, as well as space and bandwidth.<br />
<br />
=== Adjust the image ===<br />
<br />
ZOMG it's too big! How to cut stuff. See [[#Release management]] for more notes. (make that section)<br />
<br />
=== Distribute the image ===<br />
<br />
Now you have an .iso. What do you do with it?<br />
<br />
== Resources ==<br />
<br />
Parts of this page were based on Rahul Sundaram's article [http://www.linuxforu.com/how-to/roll-out-a-fedora-remix/ Roll Out A Fedora Remix].</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297286Getting started with JBossAS7 in Fedora2012-07-31T21:41:43Z<p>Mojavelinux: syntax</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
From a terminal, install JBoss AS 7 using yum:<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service:<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance):<br />
sudo -u jboss-as sh -c "jboss-cli -c"<br />
''When you connect to the management console, the server will send a secret key challenge to the client. The client can only pass the challenge if it has physical direct access to the filesystem and the same permissions as the user running the server. Otherwise, you'd need to create and use a proper management user.''<br />
<br />
Stop the JBoss AS 7 system service:<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7:<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance:<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that effectively runs this command<br />
JBOSS_BASE_DIR=$HOME/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance):<br />
jboss-cli -c<br />
You don't need any special permissions to connect to the management console this time thanks to the [https://community.jboss.org/en/tools/blog/2012/02/29/excited-about-jboss-as-71-part-ii-developer-friendly-security developer friendly security policy].<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297285Getting started with JBossAS7 in Fedora2012-07-31T21:40:45Z<p>Mojavelinux: a link to writeup about management console security policy</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo -u jboss-as sh -c "jboss-cli -c"<br />
''When you connect to the management console, the server will send a secret key challenge to the client. The client can only pass the challenge if it has physical direct access to the filesystem and the same permissions as the user running the server. Otherwise, you'd need to create and use a proper management user.''<br />
<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that effectively runs this command<br />
JBOSS_BASE_DIR=$HOME/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
We don't need any special permissions to connect to the management console this time thanks to the [https://community.jboss.org/en/tools/blog/2012/02/29/excited-about-jboss-as-71-part-ii-developer-friendly-security developer friendly security policy].<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297284Getting started with JBossAS7 in Fedora2012-07-31T21:34:51Z<p>Mojavelinux: update path of JBOSS_BASE_DIR</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo -u jboss-as sh -c "jboss-cli -c"<br />
''When you connect to the management console, the server will send a secret key challenge to the client. The client can only pass the challenge if it has physical direct access to the filesystem and the same permissions as the user running the server. Otherwise, you'd need to create and use a proper management user.''<br />
<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that effectively runs this command<br />
JBOSS_BASE_DIR=$HOME/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297283Getting started with JBossAS7 in Fedora2012-07-31T21:32:14Z<p>Mojavelinux: formatting</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo -u jboss-as sh -c "jboss-cli -c"<br />
''When you connect to the management console, the server will send a secret key challenge to the client. The client can only pass the challenge if it has physical direct access to the filesystem and the same permissions as the user running the server. Otherwise, you'd need to create and use a proper management user.''<br />
<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that runs this command<br />
JBOSS_BASE_DIR=jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297282Getting started with JBossAS7 in Fedora2012-07-31T21:31:30Z<p>Mojavelinux: Note about jboss-cli usage</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo -u jboss-as sh -c "jboss-cli -c"<br />
(When you connect to the management console, the server will send a secret key challenge to the client. The client can only pass the challenge if it has physical direct access to the filesystem and the same permissions as the user running the server. Otherwise, you'd need to create and use a proper management user.)<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that runs this command<br />
JBOSS_BASE_DIR=jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297280Getting started with JBossAS7 in Fedora2012-07-31T21:02:16Z<p>Mojavelinux: remove cd command</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
$HOME/jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that runs this command<br />
JBOSS_BASE_DIR=jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297279Getting started with JBossAS7 in Fedora2012-07-31T21:00:25Z<p>Mojavelinux: document generated startup script</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (for the system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-user-instance<br />
Start the JBoss AS 7 user instance<br />
cd && jboss-as-user-instance/bin/standalone.sh<br />
standalone.sh is a script generated by jboss-as-cp that runs this command<br />
JBOSS_BASE_DIR=jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (for the user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Getting_started_with_JBossAS7_in_Fedora&diff=297276Getting started with JBossAS7 in Fedora2012-07-31T20:06:43Z<p>Mojavelinux: Add -y flag to yum commad</p>
<hr />
<div>== Getting started with JBoss AS 7 in Fedora ==<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum -y install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo systemctl start jboss-as.service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo systemctl stop jboss-as.service<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
== Learn more about the effort to package JBoss AS 7 in Fedora ==<br />
<br />
* [http://fedoraproject.org/wiki/JBossAS7 fedoraproject.org/wiki/JBossAS7]<br />
<br />
== Get involved with the Fedora Java SIG ==<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Fedora-JBoss-Spin&diff=294604Fedora-JBoss-Spin2012-07-05T17:36:19Z<p>Mojavelinux: </p>
<hr />
<div>= Fedora JBoss Spin =<br />
<br />
This aim of this page is to gather all information relevant to the creation of the JBoss spin for Fedora. I ([[User:galileo|Gerard Ryan]]) am working on this as a project under Google Summer of Code 2012, with ([[User:Goldmann|Marek Goldmann]]) as mentor. More details on the GSOC proposal can be found [[GSOC_2012/Student_Application_grdryn_JBoss_Spin|here]].<br />
<br />
<br />
== JBoss Tools ==<br />
<br />
The first chunk of the work will be to start packaging [http://www.jboss.org/tools.html JBoss Tools for Eclipse]. This may require additional parts of [http://www.eclipse.org/webtools/ Eclipse WTP] to be packaged.<br />
<br />
There may be some difficulty with using tycho in Fedora, see patches for [http://pkgs.fedoraproject.org/gitweb/?p=eclipse-cdt.git eclipse-cdt].<br />
<br />
At the moment, I'm using the following page as a reference for learning how to build: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3<br />
Also, focusing on the 3.3.0.Beta3 branch, so this also applies: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3-WorkingWithBranches<br />
<br />
Currently, I'm running all mvn-rpmbuild commands from the build/ directory. I'm not sure if this is the best way going forward, it may not be necessary but the pom.xml there includes profiles for all the other components, and bootstrap profiles for many of them too.<br />
<br />
<br />
===Proposed Structure of eclipse-jbosstools===<br />
* '''eclipse-jbosstools'''<br />
** eclipse-jbosstools-'''parent'''<br />
*** builds parent pom and target-platform pom (maybe these should be separated, parent builds target-platform anyway I think, even if it exists).<br />
*** not sure if this is necessary, it may not apply as a package. Parent and target platform need to be built for all plugins, so I figure this might be the way to do it.<br />
*** provisional package available at http://galileo.fedorapeople.org/jbosstools_srpms/jbosstools-parent-3.3.0.Beta3-1.fc17.src.rpm<br />
** eclipse-jbosstools-'''tests'''<br />
** eclipse-jbosstools-'''common'''<br />
** eclipse-jbosstools-'''usage'''<br />
** eclipse-jbosstools-'''archives'''<br />
*** needs jbosstools-usage<br />
** eclipse-jbosstools-'''jmx'''<br />
*** needs jbosstools-common, jbosstools-usage<br />
** eclipse-jbosstools-'''as'''<br />
*** needs jbosstools-common, jbosstools-archives, jbosstools-jmx<br />
<br />
===Unpackaged dependencies===<br />
Feel free to package any of these, just let me know you're doing it (grdryn on #fedora-java)! :)<br />
<br /><br />
* ant-optional<br />
** currently commented out of '''jbosstools-parent''' to make it work<br />
** may not be necessary or desired<br />
<br /><br />
* eclipse-swtbot<br />
** needed by '''eclipse-jbosstools-tests'''<br />
<br /><br />
* [https://bitbucket.org/atlassian/connector-eclipse connector-eclipse]<br />
** needed by '''org.jboss.tools.common.mylyn''' (currently patched out)<br />
<br /><br />
* [http://git.eclipse.org/c/m2e/m2e-core.git/ eclipse-m2e-core]<br />
** needed by '''eclipse-jbosstools-openshift''' (not currently being built)<br />
<br /><br />
* [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsf/?root=WebTools_Project org.eclipse.jsf]<br />
** needed by '''eclipse-jbosstools-ws''' (not currently being built)<br />
<br /><br />
* [https://developers.google.com/eclipse/ Google plugin for eclipse]<br />
** needed by '''eclipse-jbosstools-gwt''' (not currently being built)<br />
<br /><br />
* [http://www.eclipse.org/webtools/jsf/main.php eclipse-wtp-jsf]<br />
** needed by '''eclipse-jbosstools-cdi''' (not currently being built)<br />
<br />
== Current progress ==<br />
<br />
Table below shows what is officially submitted to Fedora (after creating review request).<br />
<br />
{| id="current_progress"<br />
<br />
!#<br />
!Package<br />
!Version<br />
!Review request<br />
!Packager<br />
!Status<br />
!Comments<br />
|-<br />
|1<br />
|uddi4j<br />
|2.0.5<br />
|{{bz|825890}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|2<br />
|wsil4j<br />
|1.0<br />
|{{bz|826014}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|3<br />
|geronimo-activation<br />
|1.1<br />
|{{bz|826777}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|Activation framwework is included in JDK 6+ Most probably you don't need this package, at all.<br />
|-<br />
|4<br />
|eclipse-wtp-webservices<br />
|3.4.0<br />
|{{bz|827917}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|826014}}</s>, <s>{{bz|826327}}</s>, <s>{{bz|826776}}</s><br />
|-<br />
|5<br />
|eclipse-wtp-jeetools<br />
|3.4.0<br />
|{{bz|833154}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
| Depends on <s>{{bz|834944}}</s> and <s>{{bz|834956}}</s><br />
|-<br />
|6<br />
|eclipse-wtp-jpa<br />
|3.4.0<br />
|{{bz|833641}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|Depends on <s>{{bz|833154}}</s><br />
|-<br />
|7<br />
|eclipse-wtp-jst-web<br />
|3.4.0<br />
|{{bz|835338}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|Depends on <s>{{bz|833154}}</s><br />
|-<br />
|8<br />
|jboss-common-logging-spi<br />
|2.1.2<br />
|{{bz|835716}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|This package was removed from review request queue as it shouldn't be packaged and jboss-logging RPM should be used instead<br />
|-<br />
|9<br />
|jboss-classpool-scoped<br />
|1.0.1<br />
|{{bz|836400}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|<br />
|-<br />
|10<br />
|jboss-reflect<br />
|2.2.1<br />
|{{bz|836404}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Depends on {{bz|836400}}<br />
|-<br />
|11<br />
|jbossxb<br />
|2.0.3<br />
|{{bz|836403}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Depends on {{bz|836400}}, {{bz|836404}}<br />
|-<br />
|12<br />
|schlichtherle-oss-parent<br />
|2.0.3<br />
|{{bz|836849}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|<br />
|-<br />
|13<br />
|truezip<br />
|2.0.3<br />
|{{bz|836850}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
| Depends on {{bz|836849}} and {{bz|836698}}<br />
|}<br />
<br />
<br />
=== Status legend ===<br />
<br />
{|<br />
!Status<br />
!Meaning<br />
|-<br />
|'''<span style="color:red">Issue</span>'''<br />
|Package encountered a serious issue while packaging (license, etc) - see Comments field for more info.<br />
|-<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|Package submitted by accident or not required anymore.<br />
|-<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review.<br />
|-<br />
|'''<span style="color:orange">In review</span>'''<br />
|Package is submitted for review and being reviewed by someone.<br />
|-<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Package passed review and packages is waiting for creating git repo in Fedora for this package.<br />
|-<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Package is available in Rawhide. Yay! This means also that the package was submitted to Fedora 17 as an update.<br />
|-<br />
|}<br />
<br />
==Proposed Desktop Customizations==<br />
<br />
We want to put the developer in the driver's seat to start coding as soon as they load up the Spin, rather than spending time tweaking the environment to be "just right". In particular, I've suggested keybinding overrides that create a consistent experience, which is a critical to productivity. In doing so, we will also be effectively recommending a configuration that we believe is productive. We just need to agree :)<br />
<br />
The customizations are a combination of pre-installed packages, desktop settings, keybindings, resources and branding.<br />
<br />
Here are some ideas of what we might put in the kickstart file or /etc/skel (whichever applies):<br />
<br />
* Installed packages<br />
** java-1.7.0-openjdk-devel<br />
** eclipse, eclipse-wtp (when ready), eclipse-jboss-tools (when ready)<br />
** jboss-as<br />
** maven<br />
** groovy<br />
** ant<br />
** scala<br />
** clojure<br />
** thermostat<br />
** mysql-connector-java, h2<br />
** vim-enhanced<br />
** git, gitg<br />
** gedit-plugins<br />
** pidgin<br />
** asciidoc<br />
* Custom JBoss-related desktop background (perhaps [http://www.jboss.org/coolstuff/desktopwallpapers/jbossas7 JBoss AS 7] or [http://www.jboss.org/coolstuff/desktopwallpapers/jbosstools JBoss Tools])<br />
* Custom start page in Firefox, which adds or replaces feeds from [http://planet.jboss.org/feed/all Planet JBoss] and [http://planet.jboss.org/feed/weeklyeditorial JBoss Weekly]. See this [mockup http://imagebin.org/219576] (the entries can be retrieved using JavaScript w/ jQuery + jGFeed + jsRender)<br />
* Bookmarks for key Java / JBoss resources, such as http://jboss.org/jdf, http://jboss.org/developer, Java EE 6 JavaDoc<br />
* Set JAVA_HOME (we could do this in .bash_profile, though I'm not sure why it isn't setup by default in Fedora)<br />
* [https://github.com/matthewmccullough/dotfiles/blob/master/bash_gitprompt bash git prompt]<br />
* [https://community.jboss.org/wiki/MavenGettingStarted-Users Maven settings for JBoss Community Nexus repository], named ~/.m2/settings-jboss-public.xml<br />
* [https://github.com/jboss/ide-config/tree/master/eclipse JBoss Community formatting profile loaded as default in Eclipse]<br />
* Recommended Eclipse settings<br />
** Preferences > General > Workspace > [x] Refresh using native hooks or polling (enable)<br />
** Preferences > Maven > [ ] Download repository index updates on startup (disable)<br />
** Preferences > Maven > Annotation Processing > (*) Automatically configure JDT APT (enable)<br />
** default folder for Team git integration<br />
* Consistent keybindings<br />
** Gnome Terminal: <CTRL-t> = new tab, <SHIFT-right> = next tab, <SHIFT-left> = previous tab, <SHIFT-CTRL-right = move tab right, <SHIFT-CTRL-left> = move tab left, <CTRL-w> = close tab, <CTRL-q> = quit, <CTRL-=> = increase font size, <CTRL--> = decrease font size, <CTRL-0> = normal font size<br />
** Eclipse: <SHIFT-right> = next tab, <SHIFT-left> = previous tab<br />
** Gedit: <CTRL-t> = new tab<br />
** Gnome: make Capslock and additional control (gsettings set org.gnome.libgnomekbd.keyboard options "['ctrl\tctrl:nocaps']")<br />
* General desktop settings<br />
** disable attached modal dialogs (gsettings set org.gnome.shell.overrides attach-modal-dialogs false)<br />
** tab size and expand spaces in Gedit (gsettings set org.gnome.gedit.preferences.editor insert-spaces true && gsettings set org.gnome.gedit.preferences.editor tabs-size 4)<br />
* Configure devilspie to maximize terminal when opened<br />
* [https://apps.fedoraproject.org/packages/gnome-shell-extension-gpaste GPaste and GPaste gnome shell extension] (package gnome-shell-extension-gpaste) (clipboard manager for Gnome)<br />
* IRC channels pre-configured in pidgin<br />
* sshd service enabled<br />
* rhc ruby gem for OpenShift (package rubygem-rhc)<br />
* [https://github.com/gmate/gmate/ gmate setup for gedit]<br />
* Library folder with key resources such as CDI spec, JDF tutorial, Java EE spec, etc.<br />
** auto-launch welcome PDF on first login<br />
<br />
==Related Links==<br />
[[JBossAS7 | JBoss AS7]]<br />
<br />
[[Category:Java]] [[Category:JBoss]] [[Category: Summer_coding_2012]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Fedora-JBoss-Spin&diff=294603Fedora-JBoss-Spin2012-07-05T17:35:44Z<p>Mojavelinux: Added proposal for desktop customizations</p>
<hr />
<div>= Fedora JBoss Spin =<br />
<br />
This aim of this page is to gather all information relevant to the creation of the JBoss spin for Fedora. I ([[User:galileo|Gerard Ryan]]) am working on this as a project under Google Summer of Code 2012, with ([[User:Goldmann|Marek Goldmann]]) as mentor. More details on the GSOC proposal can be found [[GSOC_2012/Student_Application_grdryn_JBoss_Spin|here]].<br />
<br />
<br />
== JBoss Tools ==<br />
<br />
The first chunk of the work will be to start packaging [http://www.jboss.org/tools.html JBoss Tools for Eclipse]. This may require additional parts of [http://www.eclipse.org/webtools/ Eclipse WTP] to be packaged.<br />
<br />
There may be some difficulty with using tycho in Fedora, see patches for [http://pkgs.fedoraproject.org/gitweb/?p=eclipse-cdt.git eclipse-cdt].<br />
<br />
At the moment, I'm using the following page as a reference for learning how to build: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3<br />
Also, focusing on the 3.3.0.Beta3 branch, so this also applies: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3-WorkingWithBranches<br />
<br />
Currently, I'm running all mvn-rpmbuild commands from the build/ directory. I'm not sure if this is the best way going forward, it may not be necessary but the pom.xml there includes profiles for all the other components, and bootstrap profiles for many of them too.<br />
<br />
<br />
===Proposed Structure of eclipse-jbosstools===<br />
* '''eclipse-jbosstools'''<br />
** eclipse-jbosstools-'''parent'''<br />
*** builds parent pom and target-platform pom (maybe these should be separated, parent builds target-platform anyway I think, even if it exists).<br />
*** not sure if this is necessary, it may not apply as a package. Parent and target platform need to be built for all plugins, so I figure this might be the way to do it.<br />
*** provisional package available at http://galileo.fedorapeople.org/jbosstools_srpms/jbosstools-parent-3.3.0.Beta3-1.fc17.src.rpm<br />
** eclipse-jbosstools-'''tests'''<br />
** eclipse-jbosstools-'''common'''<br />
** eclipse-jbosstools-'''usage'''<br />
** eclipse-jbosstools-'''archives'''<br />
*** needs jbosstools-usage<br />
** eclipse-jbosstools-'''jmx'''<br />
*** needs jbosstools-common, jbosstools-usage<br />
** eclipse-jbosstools-'''as'''<br />
*** needs jbosstools-common, jbosstools-archives, jbosstools-jmx<br />
<br />
===Unpackaged dependencies===<br />
Feel free to package any of these, just let me know you're doing it (grdryn on #fedora-java)! :)<br />
<br /><br />
* ant-optional<br />
** currently commented out of '''jbosstools-parent''' to make it work<br />
** may not be necessary or desired<br />
<br /><br />
* eclipse-swtbot<br />
** needed by '''eclipse-jbosstools-tests'''<br />
<br /><br />
* [https://bitbucket.org/atlassian/connector-eclipse connector-eclipse]<br />
** needed by '''org.jboss.tools.common.mylyn''' (currently patched out)<br />
<br /><br />
* [http://git.eclipse.org/c/m2e/m2e-core.git/ eclipse-m2e-core]<br />
** needed by '''eclipse-jbosstools-openshift''' (not currently being built)<br />
<br /><br />
* [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsf/?root=WebTools_Project org.eclipse.jsf]<br />
** needed by '''eclipse-jbosstools-ws''' (not currently being built)<br />
<br /><br />
* [https://developers.google.com/eclipse/ Google plugin for eclipse]<br />
** needed by '''eclipse-jbosstools-gwt''' (not currently being built)<br />
<br /><br />
* [http://www.eclipse.org/webtools/jsf/main.php eclipse-wtp-jsf]<br />
** needed by '''eclipse-jbosstools-cdi''' (not currently being built)<br />
<br />
== Current progress ==<br />
<br />
Table below shows what is officially submitted to Fedora (after creating review request).<br />
<br />
{| id="current_progress"<br />
<br />
!#<br />
!Package<br />
!Version<br />
!Review request<br />
!Packager<br />
!Status<br />
!Comments<br />
|-<br />
|1<br />
|uddi4j<br />
|2.0.5<br />
|{{bz|825890}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|2<br />
|wsil4j<br />
|1.0<br />
|{{bz|826014}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|3<br />
|geronimo-activation<br />
|1.1<br />
|{{bz|826777}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|Activation framwework is included in JDK 6+ Most probably you don't need this package, at all.<br />
|-<br />
|4<br />
|eclipse-wtp-webservices<br />
|3.4.0<br />
|{{bz|827917}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|826014}}</s>, <s>{{bz|826327}}</s>, <s>{{bz|826776}}</s><br />
|-<br />
|5<br />
|eclipse-wtp-jeetools<br />
|3.4.0<br />
|{{bz|833154}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
| Depends on <s>{{bz|834944}}</s> and <s>{{bz|834956}}</s><br />
|-<br />
|6<br />
|eclipse-wtp-jpa<br />
|3.4.0<br />
|{{bz|833641}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|Depends on <s>{{bz|833154}}</s><br />
|-<br />
|7<br />
|eclipse-wtp-jst-web<br />
|3.4.0<br />
|{{bz|835338}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|Depends on <s>{{bz|833154}}</s><br />
|-<br />
|8<br />
|jboss-common-logging-spi<br />
|2.1.2<br />
|{{bz|835716}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|This package was removed from review request queue as it shouldn't be packaged and jboss-logging RPM should be used instead<br />
|-<br />
|9<br />
|jboss-classpool-scoped<br />
|1.0.1<br />
|{{bz|836400}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:orange">In review</span>'''<br />
|<br />
|-<br />
|10<br />
|jboss-reflect<br />
|2.2.1<br />
|{{bz|836404}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Depends on {{bz|836400}}<br />
|-<br />
|11<br />
|jbossxb<br />
|2.0.3<br />
|{{bz|836403}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Depends on {{bz|836400}}, {{bz|836404}}<br />
|-<br />
|12<br />
|schlichtherle-oss-parent<br />
|2.0.3<br />
|{{bz|836849}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|<br />
|-<br />
|13<br />
|truezip<br />
|2.0.3<br />
|{{bz|836850}}<br />
|[[User:Galileo|galileo(grdryn)]]<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
| Depends on {{bz|836849}} and {{bz|836698}}<br />
|}<br />
<br />
<br />
=== Status legend ===<br />
<br />
{|<br />
!Status<br />
!Meaning<br />
|-<br />
|'''<span style="color:red">Issue</span>'''<br />
|Package encountered a serious issue while packaging (license, etc) - see Comments field for more info.<br />
|-<br />
|'''<span style="color:darkviolet">Skipped</span>'''<br />
|Package submitted by accident or not required anymore.<br />
|-<br />
|'''<span style="color:gray">Waiting for review</span>'''<br />
|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review.<br />
|-<br />
|'''<span style="color:orange">In review</span>'''<br />
|Package is submitted for review and being reviewed by someone.<br />
|-<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Package passed review and packages is waiting for creating git repo in Fedora for this package.<br />
|-<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Package is available in Rawhide. Yay! This means also that the package was submitted to Fedora 17 as an update.<br />
|-<br />
|}<br />
<br />
==Desktop Customizations==<br />
<br />
We want to put the developer in the driver's seat to start coding as soon as they load up the Spin, rather than spending time tweaking the environment to be "just right". In particular, I've suggested keybinding overrides that create a consistent experience, which is a critical to productivity. In doing so, we will also be effectively recommending a configuration that we believe is productive. We just need to agree :)<br />
<br />
The customizations are a combination of pre-installed packages, desktop settings, keybindings, resources and branding.<br />
<br />
Here are some ideas of what we might put in the kickstart file or /etc/skel (whichever applies):<br />
<br />
* Installed packages<br />
** java-1.7.0-openjdk-devel<br />
** eclipse, eclipse-wtp (when ready), eclipse-jboss-tools (when ready)<br />
** jboss-as<br />
** maven<br />
** groovy<br />
** ant<br />
** scala<br />
** clojure<br />
** thermostat<br />
** mysql-connector-java, h2<br />
** vim-enhanced<br />
** git, gitg<br />
** gedit-plugins<br />
** pidgin<br />
** asciidoc<br />
* Custom JBoss-related desktop background (perhaps [http://www.jboss.org/coolstuff/desktopwallpapers/jbossas7 JBoss AS 7] or [http://www.jboss.org/coolstuff/desktopwallpapers/jbosstools JBoss Tools])<br />
* Custom start page in Firefox, which adds or replaces feeds from [http://planet.jboss.org/feed/all Planet JBoss] and [http://planet.jboss.org/feed/weeklyeditorial JBoss Weekly]. See this [mockup http://imagebin.org/219576] (the entries can be retrieved using JavaScript w/ jQuery + jGFeed + jsRender)<br />
* Bookmarks for key Java / JBoss resources, such as http://jboss.org/jdf, http://jboss.org/developer, Java EE 6 JavaDoc<br />
* Set JAVA_HOME (we could do this in .bash_profile, though I'm not sure why it isn't setup by default in Fedora)<br />
* [https://github.com/matthewmccullough/dotfiles/blob/master/bash_gitprompt bash git prompt]<br />
* [https://community.jboss.org/wiki/MavenGettingStarted-Users Maven settings for JBoss Community Nexus repository], named ~/.m2/settings-jboss-public.xml<br />
* [https://github.com/jboss/ide-config/tree/master/eclipse JBoss Community formatting profile loaded as default in Eclipse]<br />
* Recommended Eclipse settings<br />
** Preferences > General > Workspace > [x] Refresh using native hooks or polling (enable)<br />
** Preferences > Maven > [ ] Download repository index updates on startup (disable)<br />
** Preferences > Maven > Annotation Processing > (*) Automatically configure JDT APT (enable)<br />
** default folder for Team git integration<br />
* Consistent keybindings<br />
** Gnome Terminal: <CTRL-t> = new tab, <SHIFT-right> = next tab, <SHIFT-left> = previous tab, <SHIFT-CTRL-right = move tab right, <SHIFT-CTRL-left> = move tab left, <CTRL-w> = close tab, <CTRL-q> = quit, <CTRL-=> = increase font size, <CTRL--> = decrease font size, <CTRL-0> = normal font size<br />
** Eclipse: <SHIFT-right> = next tab, <SHIFT-left> = previous tab<br />
** Gedit: <CTRL-t> = new tab<br />
** Gnome: make Capslock and additional control (gsettings set org.gnome.libgnomekbd.keyboard options "['ctrl\tctrl:nocaps']")<br />
* General desktop settings<br />
** disable attached modal dialogs (gsettings set org.gnome.shell.overrides attach-modal-dialogs false)<br />
** tab size and expand spaces in Gedit (gsettings set org.gnome.gedit.preferences.editor insert-spaces true && gsettings set org.gnome.gedit.preferences.editor tabs-size 4)<br />
* Configure devilspie to maximize terminal when opened<br />
* [https://apps.fedoraproject.org/packages/gnome-shell-extension-gpaste GPaste and GPaste gnome shell extension] (package gnome-shell-extension-gpaste) (clipboard manager for Gnome)<br />
* IRC channels pre-configured in pidgin<br />
* sshd service enabled<br />
* rhc ruby gem for OpenShift (package rubygem-rhc)<br />
* [https://github.com/gmate/gmate/ gmate setup for gedit]<br />
* Library folder with key resources such as CDI spec, JDF tutorial, Java EE spec, etc.<br />
** auto-launch welcome PDF on first login<br />
<br />
==Related Links==<br />
[[JBossAS7 | JBoss AS7]]<br />
<br />
[[Category:Java]] [[Category:JBoss]] [[Category: Summer_coding_2012]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=294524JBossAS7 in Fedora marketing collateral2012-07-05T00:37:21Z<p>Mojavelinux: Add JRuby</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
{{admon/important|Where did the Getting Started section go?|The text on this page is currently being used to produce a 5x7 postcard. The getting started commands were moved to a [[Getting_started_with_JBossAS7_in_Fedora|new wikipage]] and will soon be linked to other appropriate pages. Please continue to add to and edit the Getting Started with JBoss AS 7 page.}}<br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3, Apache Ant 1.8, Groovy 1.8, Scala 2.9, Clojure 1.4, JRuby 1.6 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of Java<br />
* JBoss Application Server (Web Profile minus JPA 2, standalone mode only) makes its debut as an official Fedora package (jboss-as)<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone mode instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform (in testing)<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin<br />
* Groovy (added in Fedora 16)<br />
<br />
=== Get started with JBoss AS 7 and Fedora ===<br />
<br />
* [http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora]<br />
* [http://jboss.org/as7 jboss.org/as7]<br />
* [http://fedoraproject.org fedoraproject.org]<br />
<br />
=== Get involved with the Fedora Java SIG ===<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=294523JBossAS7 in Fedora marketing collateral2012-07-05T00:36:29Z<p>Mojavelinux: Add AS7 url</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
{{admon/important|Where did the Getting Started section go?|The text on this page is currently being used to produce a 5x7 postcard. The getting started commands were moved to a [[Getting_started_with_JBossAS7_in_Fedora|new wikipage]] and will soon be linked to other appropriate pages. Please continue to add to and edit the Getting Started with JBoss AS 7 page.}}<br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3, Apache Ant 1.8, Groovy 1.8, Scala 2.9, Clojure 1.4 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of Java<br />
* JBoss Application Server (Web Profile minus JPA 2, standalone mode only) makes its debut as an official Fedora package (jboss-as)<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone mode instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform (in testing)<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin<br />
* Groovy (added in Fedora 16)<br />
<br />
=== Get started with JBoss AS 7 and Fedora ===<br />
<br />
* [http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora]<br />
* [http://jboss.org/as7 jboss.org/as7]<br />
* [http://fedoraproject.org fedoraproject.org]<br />
<br />
=== Get involved with the Fedora Java SIG ===<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=294522JBossAS7 in Fedora marketing collateral2012-07-05T00:33:48Z<p>Mojavelinux: Add scala and clojure</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
{{admon/important|Where did the Getting Started section go?|The text on this page is currently being used to produce a 5x7 postcard. The getting started commands were moved to a [[Getting_started_with_JBossAS7_in_Fedora|new wikipage]] and will soon be linked to other appropriate pages. Please continue to add to and edit the Getting Started with JBoss AS 7 page.}}<br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3, Apache Ant 1.8, Groovy 1.8, Scala 2.9, Clojure 1.4 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of Java<br />
* JBoss Application Server (Web Profile minus JPA 2, standalone mode only) makes its debut as an official Fedora package (jboss-as)<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone mode instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform (in testing)<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin<br />
* Groovy (added in Fedora 16)<br />
<br />
=== Get started with JBoss AS 7 and Fedora ===<br />
<br />
* [http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora]<br />
* [http://fedoraproject.org fedoraproject.org]<br />
<br />
=== Get involved with the Fedora Java SIG ===<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=User:Akurtakov/JavaPackagingDraftUpdate&diff=294436User:Akurtakov/JavaPackagingDraftUpdate2012-07-04T00:31:14Z<p>Mojavelinux: Added cdi-api</p>
<hr />
<div>These guidelines are laid out in order of relevance to packaging.<br />
<br />
== Introduction ==<br />
<br />
=== The Basics ===<br />
The term Java means many things to many people: a class library, a bytecode interpreter, a JIT compiler, a language specification, etc. For the vast majority of users and developers, Java is a programming language and runtime environment that is architecture- and OS-agnostic. The normal flow of code is <code>.java</code> (source file) <code>.class</code> (Java bytecode) <code>.jar</code> (a zip archive). In the majority of cases, a user executes a Java program by specifying a class name containing a main method (just like C and C++). Often, this is done by invoking the <code>java</code> binary with a list of JAR files specifying the classpath like so:<br />
<br />
<code>java [-cp <jar1:jar2:jar3>] <main-class> [<args>] </code><br />
<br />
== Java Packaging ==<br />
The [http://www.jpackage.org JPackage Project] has defined standard file system locations and conventions for use in Java packages. Many distributions have inherited these conventions and in the vast majority of cases, Fedora follows them verbatim. We include relevant sections of the JPackage guidelines here but caution that the canonical document will always reside upstream: [http://www.jpackage.org/cgi-bin/viewvc.cgi/src/jpackage-utils/doc/jpackage-1.5-policy.xhtml?revision=HEAD&root=jpackage JPackage Guidelines] . Over time, we would like to remove any divergences in these documents, but where they are different, these Fedora guidelines will take precedence for Fedora packages.<br />
<br />
TODO: Find the proper jpackage link and fix it.<br />
<br />
=== Package naming ===<br />
<br />
Packages '''MUST''' follow the standard Fedora [[Packaging/NamingGuidelines]].<br />
<br />
Java API documentation '''MUST''' be placed into a sub-package called <code>%{name}-javadoc</code>.<br />
<br />
==== Release tags ====<br />
Packages '''MUST''' follow the standard Fedora [[Packaging/NamingGuidelines#Package_Version | Package versioning guidelines]].<br />
<br />
=== JAR file installation ===<br />
<br />
The following applies to all JAR files except [[#JNI|JNI-using JAR files]], [[#GCJ|GCJ files]] and application-specific JAR files (ie. JAR files that can only reasonably be used as part of an application and therefore constitute application-private data).<br />
<br />
==== Split JAR files ====<br />
<br />
If a project offers the choice of packaging it as a single monolithic jar or several ones, the split packaging '''should''' be preferred.<br />
<br />
==== Filenames ====<br />
<br />
* If the package provides a '''single''' JAR and the filename provided by the build is <code>%{name}.jar</code> or <code>%{name}-%{version}.jar</code> then filename <code>%{name}.jar</code> '''MUST''' be used.<br />
* If the package provides a '''single''' JAR and the filename provided by the build is neither <code>%{name}-%{version}.jar</code> nor <code>%{name}.jar</code> then this file '''MUST''' be installed as <code>%{name}.jar</code> and a symbolic link with the usual name must be provided.<br />
* If the package provides more than '''one''' JAR file, the filenames assigned by the build '''MUST''' be used (without versions).<br />
* If the project usually provides alternative JAR file names by installing symbolic links then such symlinks '''MAY''' be installed in the same directory as the JAR files.<br />
<br />
{{admon/note|Note|Here %{name} refers either to package name, or name of subpackage where the jar is installed.}}<br />
<br />
==== Installation directory ====<br />
<br />
* All architecture-independent JAR files '''MUST''' go into <code>%{_javadir}</code> or a Java-version specific directory <code>%{_javadir}-<i>*</i></code> as appropriate[http://lists.fedoraproject.org/pipermail/packaging/2010-January/006792.html]. Packages '''CAN''' place JAR files into subdirectories.<br />
<br />
* For installation of architecture dependent jar files, see [[#Packaging_JAR_files_that_use_JNI|Packaging JAR files that use JNI]]<br />
<br />
=== Compatibility packages ===<br />
In certain cases it might be necessary to create compatibility packages that provide older API/ABI level of the same library. However creating these compatibility packages is strongly discouraged. To standardize and simplify packaging of such compatibility packages following rules apply:<br />
<br />
* Compatibility packages are named in the same way as original except addition of version to package name<br />
* Jar and pom files '''MUST''' be versioned<br />
* Base name of jar and pom files '''MUST''' be the same as original package jar and pom filenames and they '''MUST''' be placed alongside original files<br />
* Package '''SHOULD NOT''' provide maven fragments (%add_maven_depmap calls)<br />
<br />
{{admon/note|Ant and Maven compatibility|build-classpath and related tools will resolve versioned jar files if versioned jar is asked for. Maven will use dependency information from main package and will return versioned jar if it matches the version asked for in the pom file.}}<br />
<br />
==== Compatibility package example ====<br />
<br />
* Original package: plexus-container-2.0.0<br />
<pre><br />
Name: plexus-container<br />
Version: 2.0.0<br />
...<br />
<br />
%files<br />
...<br />
%{_javadir}/plexus/container.jar<br />
%{_mavenpomdir}/JPP.plexus-container.pom<br />
%{_mavendepmapfragdir}/%{name}<br />
...<br />
</pre><br />
<br />
* Compat package: plexus-container1-1.5.0<br />
<pre><br />
Name: plexus-container15<br />
Version: 1.5.0<br />
...<br />
<br />
%files<br />
...<br />
%{_javadir}/plexus/container-1.5.0.jar<br />
%{_mavenpomdir}/JPP.plexus-container-1.5.0.pom<br />
...<br />
</pre><br />
<br />
=== Javadoc installation ===<br />
<br />
* Java API documentation uses a system known as javadoc. All javadocs '''MUST''' be created and installed into a directory of <code>%{_javadocdir}/%{name}</code>. <br />
* Directory or symlink <code>%{_javadocdir}/%{name}-%{version}</code> '''SHOULD NOT''' exist.<br />
* The javadoc subpackage '''MUST''' be declared <code>noarch</code> even if main package is architecture specific.<br />
<br />
=== BuildRequires and Requires ===<br />
At a minimum, Java packages '''MUST''':<br />
<br />
<pre>BuildRequires: java-devel [>= specific_version] <br />
BuildRequires: jpackage-utils<br />
<br />
Requires: java [>= specific_version]<br />
Requires: jpackage-utils</pre><br />
<br />
For historical reasons, when specifying versions 1.6.0 or greater, an epoch of 1 must be included. Example:<br />
<br />
<pre>Requires: java >= 1:1.6.0<br />
</pre><br />
<br />
=== build-classpath ===<br />
<code>build-classpath</code> is a script that can be used to generate classpaths from generic names of JAR files. Example:<br />
<br />
<pre>export CLASSPATH=$(build-classpath commons-logging commons-net xbean/xbean-reflect)<br />
</pre><br />
{{admon/note|Additional information|You can use either jar filename or directory name relative to %{_javadir}, %{_jnidir} or %{_javajnidir} (all jar files will be included).}}<br />
<br />
=== build-jar-repository ===<br />
<code>build-jar-repository</code> is similar to <code>build-classpath</code> but instead of producing a classpath entry, it creates symlinks in a given directory. Example:<br />
<pre>$ mkdir lib<br />
$ build-jar-repository -s -p lib commons-logging commons-net<br />
$ ls -l lib<br />
commons-logging.jar -> /usr/share/java/commons-logging.jar<br />
commons-net.jar -> /usr/share/java/commons-net.jar<br />
</pre><br />
<br />
=== ant ===<br />
<code>ant</code> is a build tool used by many Java packages. Packages built using <code>ant</code> ship with <code>build.xml</code> files which contain build targets similar to <code>Makefiles</code>. Packages built using <code>ant</code> must:<br />
<br />
<pre>BuildRequires: ant<br />
...<br />
%build<br />
...<br />
ant<br />
</pre><br />
<br />
=== maven3 ===<br />
In Fedora 15 and newer, maven 3 is used and the package is called <code>maven</code>. Packages built using <code>maven</code> ship with <code>pom.xml</code> files. They '''SHOULD''' contain common sections such as the following:<br />
<br />
<pre><br />
...<br />
%build<br />
mvn-rpmbuild package javadoc:aggregate <br />
...<br />
<br />
%install<br />
install -d -m 755 $RPM_BUILD_ROOT%{_javadir}<br />
install -d -m 755 $RPM_BUILD_ROOT%{_mavenpomdir}<br />
install -pm 644 pom.xml $RPM_BUILD_ROOT/%{_mavenpomdir}/JPP-%{name}.pom<br />
install -pm 644 target/%{name}-%{version}.jar $RPM_BUILD_ROOT/%{_javadir}/%{name}.jar<br />
<br />
# second argument is optional (parent poms have no jars)<br />
%add_maven_depmap JPP-%{name}.pom %{name}.jar<br />
...<br />
%files<br />
%{_mavendepmapfragdir}/%{name}<br />
%{_mavenpomdir}/JPP-%{name}.pom<br />
</pre><br />
<br />
Useful mvn-rpmbuild customisations: <br />
* -Dmaven.local.depmap.file=FILE.xml - xml file that defines alternative dependency maps <br />
* -Dmaven.local.debug=true makes custom resolver output more debugging information <br />
<br />
{{admon/important|Important|For detailed instructions on use of add_maven_depmap macro see [[#depmap_macro|macro documentation]]}}<br />
<br />
=== add_maven_depmap macro ===<br />
{{Anchor|depmap_macro}}<br />
<br />
Maven identifies jar files by a set of strings: groupId, artifactId and version (mostly). To let mvn-rpmbuild know what groupId:artifactId corresponds to which pom or jar file, we use the <code>%add_maven_depmap</code> macro. <code>%add_maven_depmap</code> reads the groupId and artifactId from the pom file and creates a file in <code>%{_mavendepmapfragdir}</code> that maps groupId:artifactId pairs to jar files under <code>%{_javadir}</code>. All fragments in this directory are read by mvn-rpmbuild during startup, allowing the locally installed jar files and poms to be used as a maven repository.<br />
<br />
Note that -- unless you use the <code>-f</code> option as shown below -- all depmap fragments for a given package are written to the same file, <code>%{_mavendepmapfragdir}/%{name}</code>. You should be sure to include this file in the <code>%files</code> section of your RPM.<br />
<br />
For the macro to work properly, all jar files must be copied into <code>%{_javadir}</code> (see [[#JAR_file_installation|JAR file installation]]), and all pom files must be copied into <code>%{_mavenpomdir}</code> and given file names of the following form, where <code>jarname</code> is the name of the jar without the .jar suffix:<br />
<pre>%{_mavenpomdir}/JPP[.subdirectory]-jarname.pom</pre><br />
Note that the subdirectory is only necessary if the jar file is put into a subdirectory of <code>%{_javadir}</code>. For example:<br />
* For junit, the jar is <code>%{_javadir}/junit.jar</code>, so the pom would be <code>%{_mavenpomdir}/JPP-junit.pom</code>.<br />
* For plexus-ant-factory, the jar is <code>%{_javadir}/plexus/ant-factory.jar</code>, so the pom would named <code>%{_mavenpomdir}/JPP.plexus-ant-factory.pom</code>.<br />
If a pom is installed with no corresponding jar file -- for example, for parent poms -- the same convention should be followed:<br />
* The Apache commons parent pom is installed in <code>%{_mavenpomdir}/JPP-commons-parent.pom</code>.<br />
<br />
In its simplest form (a pom without a jar file), <code>%add_maven_depmap</code> looks like this:<br />
<pre>%add_maven_depmap JPP-%{name}.pom</pre><br />
This will read the pom file in question and provide a mapping between the groupId and artifactId inside the pom file and the pom file placed into <code>%{_mavenpomdir}</code>.<br />
<br />
For a pom that maps directly to a jar file, the following is the correct form:<br />
<pre>%add_maven_depmap JPP-%{name}.pom %{name}.jar</pre><br />
In addition to creating the pom mapping, this will also ensure that the correct jar is associated with the groupId and artifactId from the pom.<br />
<br />
<pre>%add_maven_depmap JPP-%{name}.pom %{name}.jar -a "org.apache.commons:commons-lang"</pre><br />
This form also adds additional mappings for given pom/jar file. For example, if the pom file indicates that it contains groupId commons-lang, artifactId commons-lang, this form ensures that we also add a mapping between groupId org.apache.commons and the installed jar/pom files. This is necessary in cases where the groupId or artifactId may have changed, and other packages might require different IDs than those reflected in the installed pom.<br />
<br />
<pre>%add_maven_depmap JPP-%{name}.pom %{name}.jar -f "XXX"</pre><br />
This form stores dependency mapping inside <code>%{_mavendepmapfragdir}/%{name}-XXX</code> instead of standard location. This is useful for packages with multiple subpackages where each has its own jar files.<br />
<br />
<pre>%add_maven_depmap JPP.%{name}-sub.pom %{name}/sub.jar</pre><br />
This form should be used when a package consists of multiple jar files that are installed into a subdirectory of <code>%{_javadir}</code>. Note that in this case, the pom file name includes the optional subdirectory field.<br />
<br />
=== Maven pom.xml files and depmaps ===<br />
If upstream project is shipping Maven pom.xml files, these '''MUST''' be installed with the corresponding %add_maven_depmap calls.<br />
<br />
If upstream project does not ship pom.xml file [[http://repo1.maven.org/maven2/ official maven repo]] should be checked and if there are pom.xml files they '''SHOULD''' be installed.<br />
<br />
{{admon/tip|Tip|[http://mvnrepository.com/ Mvnrepository site] can be used to ease}}<br />
<br />
<br />
=== Patching Maven <code>pom.xml</code> files ===<br />
<br />
Sometimes Maven <code>pom.xml</code> files need to be patched before they are used to build packages. One could use traditional patches to maintain changes, but package maintainers '''SHOULD''' use <code>%pom_*</code> macros developed specially to ease this task.<br />
<br />
These macros are designed to be called from <code>%prep</code> section of spec files. There are documented in <code>/etc/rpm/macros.fjava</code> configuration file, which is also [http://git.fedorahosted.org/git/?p=javapackages.git;a=blob_plain;f=macros.fjava available online]. See the documentation for technical details how to use these macros. Below are some examples added for convenience.<br />
<br />
Often dependencies specified in Maven <code>pom.xml</code> files need to be removed because of different reasons. <code>%pom_remove_dep</code> macro can be used to ease this task:<br />
<br />
<pre><br />
# Removes dependency on groupId:artifactId from ./pom.xml<br />
%pom_remove_dep groupId:artifactId<br />
<br />
# Removes dependency on groupId:artifactId from ./submodule/pom.xml<br />
%pom_remove_dep groupId:artifactId submodule<br />
<br />
# Removes dependency on groupId:artifactId from ./full/path/to/file.pom<br />
%pom_remove_dep groupId:artifactId full/path/to/file.pom<br />
<br />
# Removes dependency on all artifacts in group groupId from ./pom.xml<br />
%pom_remove_dep groupId:<br />
<br />
# Removes all dependencies from ./pom.xml<br />
%pom_remove_dep :<br />
</pre><br />
<br />
<code>%pom_remove_plugin</code> macro works exactly as <code>%pom_remove_dep</code>, except it removes Maven plugin invocations. Some examples:<br />
<br />
<pre><br />
# Disables maven-jar-plugin so that classpath isn't included in manifests<br />
%pom_remove_plugin :maven-jar-plugin<br />
<br />
# Disable a proprietary plugin that isn't packaged for Fedora<br />
%pom_remove_plugin com.example.mammon:useless-proprietary-plugin submodule<br />
</pre><br />
<br />
Sometimes some submodules of upstream project cannot be built for various reasons and there is a need to disable them. This can be achieved by using <code>%pom_disable_module</code>, for example:<br />
<br />
<pre><br />
# Disables child-module-1, a submodule of the main pom.xml file<br />
%pom_disable_module child-module-1<br />
<br />
# Disables grandchild-module, a submodule of child-module-2/pom.xml<br />
%pom_disable_module grandchild-module child-module-2<br />
</pre><br />
<br />
The above macros cover the most common cases of modifying <code>pom.xml</code> files, however if there is a need to apply some less-common patches there are also two generic macros for modifying <code>pom.xml</code> files. <code>%pom_xpath_remove</code> can be used to remove arbitrary XML nodes, described by [http://www.w3.org/TR/xpath/ XPath] expressions. <code>%pom_xpath_inject</code> macro is capable of injecting arbitrary [http://www.w3.org/TR/xml/ XML] code to any <code>pom.xml</code> file.<br />
<br />
Using <code>%pom_*</code> macros not only increases readability of the spec file, but also improves maintainability of the package as there are no patches that would need to be rebased with each upstream release.<br />
<br />
=== Wrapper Scripts ===<br />
Applications wishing to provide a convenient method of execution '''SHOULD''' provide a wrapper script in <code>%{_bindir}</code>. <br />
<br />
The jpackage-utils package contains a convenience <code>%jpackage_script</code> macro that can be used to create scripts that work for the majority of packages. See its definition and documentation in <code>/etc/rpm/macros.jpackage</code>. One thing to pay attention to is the 6th argument to it - whether to prefer a JRE over a full SDK when looking up a JVM to invoke - most packages that don't require the full Java SDK will want to set that to <code>true</code> to avoid unexpected results when looking up a JVM when some of the installed JRE's don't have the corresponding SDK (*-devel package) installed. <br />
<br />
<pre><br />
%install<br />
...<br />
%jpackage_script com.sun.msv.driver.textui.Driver "" "" msv-msv:msv-xsdlib:relaxngDatatype:isorelax msv true <br />
...<br />
</pre><br />
The previous example installs the "msv" script (5th argument) with main class being com.sun.msv.driver.textui.Driver (1st argument). No optional flags (2nd argument) or options (3rd argument) are used. This script will add several libraries to classpath before executing main class (4th argument, jars separated with ":"). <code>build-classpath</code> is run on every part of 4th argument to create full classpaths. <br />
<br />
=== GCJ ===<br />
Building GCJ AOT bits is discouraged unless you have a very strong reason to include them in the packages.<br />
Even when AOT bits are built and included in packages it is recommended to not require java-1.5.0-gcj because this will force every single user to install it even if one wants to use another JVM.<br />
<br />
Please refer to [[Packaging/GCJGuidelines]] for GCJ-specific guidelines.<br />
<br />
=== -devel packages ===<br />
<code>-devel</code> packages don't really make sense for Java packages. Header files do not exist for Java packages.<br />
<br />
== Specfile Template ==<br />
=== ant ===<br />
<br />
<pre><br />
Name: # see normal package guidelines<br />
Version: # see normal package guidelines<br />
Release: 1%{?dist}<br />
Summary: # see normal package guidelines<br />
<br />
Group: # see normal package guidelines<br />
License: # see normal package guidelines<br />
URL: # see normal package guidelines<br />
Source0: # see normal package guidelines<br />
BuildArch: noarch<br />
<br />
BuildRequires: jpackage-utils<br />
<br />
BuildRequires: java-devel<br />
<br />
BuildRequires: ant<br />
<br />
Requires: jpackage-utils<br />
<br />
Requires: java<br />
<br />
%description<br />
<br />
%package javadoc<br />
Summary: Javadocs for %{name}<br />
Group: Documentation<br />
Requires: jpackage-utils<br />
<br />
%description javadoc<br />
This package contains the API documentation for %{name}.<br />
<br />
%prep<br />
%setup -q<br />
<br />
find -name '*.class' -exec rm -f '{}' \;<br />
find -name '*.jar' -exec rm -f '{}' \;<br />
<br />
%build<br />
ant<br />
<br />
%install<br />
<br />
mkdir -p $RPM_BUILD_ROOT%{_javadir}<br />
cp -p [build path to jar] $RPM_BUILD_ROOT%{_javadir}/%{name}.jar<br />
<br />
mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name}<br />
cp -rp [javadoc directory] $RPM_BUILD_ROOT%{_javadocdir}/%{name}<br />
<br />
%files<br />
%{_javadir}/*<br />
%doc<br />
<br />
%files javadoc<br />
%{_javadocdir}/%{name}<br />
<br />
<br />
%changelog<br />
</pre><br />
<br />
<br />
<br />
=== maven 3 ===<br />
<pre><br />
Name: # see normal package guidelines<br />
Version: # see normal package guidelines<br />
Release: 1%{?dist}<br />
Summary: # see normal package guidelines<br />
<br />
Group: # see normal package guidelines<br />
License: # see normal package guidelines<br />
URL: # see normal package guidelines<br />
Source0: # see normal package guidelines<br />
<br />
BuildArch: noarch<br />
<br />
BuildRequires: jpackage-utils<br />
<br />
BuildRequires: java-devel<br />
<br />
BuildRequires: maven<br />
<br />
BuildRequires: maven-compiler-plugin<br />
BuildRequires: maven-install-plugin<br />
BuildRequires: maven-jar-plugin<br />
BuildRequires: maven-javadoc-plugin<br />
BuildRequires: maven-release-plugin<br />
BuildRequires: maven-resources-plugin<br />
BuildRequires: maven-surefire-plugin<br />
<br />
Requires: jpackage-utils<br />
Requires: java<br />
<br />
%description<br />
some smart and long description.<br />
<br />
%package javadoc<br />
Summary: Javadocs for %{name}<br />
Group: Documentation<br />
Requires: jpackage-utils<br />
<br />
%description javadoc<br />
This package contains the API documentation for %{name}.<br />
<br />
%prep<br />
%setup -q<br />
<br />
%build<br />
mvn-rpmbuild package javadoc:aggregate<br />
<br />
%install<br />
<br />
mkdir -p $RPM_BUILD_ROOT%{_javadir}<br />
cp -p [build path to jar] $RPM_BUILD_ROOT%{_javadir}/%{name}.jar<br />
<br />
mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name}<br />
cp -rp [javadoc directory] $RPM_BUILD_ROOT%{_javadocdir}/%{name}<br />
<br />
install -d -m 755 $RPM_BUILD_ROOT%{_mavenpomdir}<br />
install -pm 644 [path to pom] \<br />
$RPM_BUILD_ROOT%{_mavenpomdir}/JPP-%{name}.pom<br />
<br />
%add_maven_depmap JPP-%{name}.pom %{name}.jar<br />
<br />
<br />
%files<br />
%{_mavenpomdir}/JPP-%{name}.pom<br />
%{_mavendepmapfragdir}/%{name}<br />
%{_javadir}/%{name}.jar<br />
%doc<br />
<br />
%files javadoc<br />
%{_javadocdir}/%{name}<br />
<br />
%changelog<br />
<br />
</pre><br />
<br />
{{admon/important|Important|For detailed instructions on use of add_maven_depmap macro see [[#depmap_macro|macro documentation]]}}<br />
<br />
== Packaging and using EE APIs ==<br />
There are a number of various project providing implementations for Java EE APIs. To simplify packaging and use of these APIs certain standardization is necessary. <br />
<br />
=== EE API List ===<br />
Following is a list of EE APIs as of Java EE 6[http://docs.oracle.com/javaee/6/api/] with chosen packages that provide implementations:<br />
* javax.activation - JDK<br />
* javax.annotation - JDK<br />
* javax.el - tomcat-el-2.2-api<br />
* javax.enterprise.inject - cdi-api<br />
* javax.inject - atinject<br />
* javax.jws - JDK<br />
* javax.mail - javamail <br />
* javax.management - JDK<br />
* javax.management.remote - JDK<br />
* javax.persistence - geronimo-jpa<br />
* javax.security.auth.message - geronimo-jaspic-spec <br />
* javax.servlet - tomcat-servlet-3.0-api <br />
* javax.servlet.jsp - glassfish-jsp/glassfish-jsp-api<br />
* javax.servlet.jsp.jstl - jakarta-taglibs-standard<br />
* javax.transaction - JDK<br />
* javax.ws.rs - jsr-311<br />
* javax.wsdl - wsdl4j<br />
* javax.xml - JDK<br />
* javax.xml.bind - JDK <br />
* javax.xml.rpc - axis<br />
* javax.xml.soap - JDK<br />
* javax.xml.stream - JDK <br />
* javax.xml.ws - JDK<br />
<br />
=== Packages providing APIs ===<br />
In addition to following generic guidelines they '''MUST''':<br />
* Add '''Provides: javax.XXX''' from the [[#EE_API_List|EE API list]]<br />
* Add directory %{_javadir}/javax.XXX that will contain symlinks to all implementation jar files and their dependencies<br />
<br />
At one time there '''MUST''' be at most one package providing given API.<br />
<br />
=== Packages using APIs ===<br />
Packages that need to use EE API '''SHOULD''' use:<br />
* '''Requires: javax.XXX''' from the [[#EE_API_List|EE API list]]<br />
* '''build-classpath javax.XXX''' or equivalent instead of relying on package-specific jar name.<br />
<br />
<br />
== Packaging JAR files that use JNI ==<br />
{{Anchor|JNI}}<br />
=== Applicability ===<br />
<br />
Java programs that wish to make calls into native libraries do so via the Java Native Interface (JNI). A Java package uses JNI if it contains a .so file. Note that this file can be embedded within JAR files themselves. <br />
<br />
{{Template:Warning}} Note that GCJ packages contain <code>.so</code>s in <code>%{_libdir}/gcj/%{name}</code> but they are not JNI .sos.<br />
<br />
=== Guideline ===<br />
<br />
JAR files that require JNI shared objects '''MUST''' be installed in <code>%{_libdir}/%{name}</code>. The JNI shared objects themselves must also be installed in <code>%{_libdir}/%{name}</code>. If the JNI-using code calls <code>System.loadLibrary</code> you'll have to patch it to use <code>System.load</code>, passing it the full path to the dynamic shared object. If the package installs a wrapper script you'll need to manually add <code>%{_libdir}/%{name}/<jar filename></code> to <code>CLASSPATH</code>. If you are depending on a JNI-using JAR file, you'll need to add it manually -- <code>build-classpath</code> will not find it.<br />
<br />
=== Rationale ===<br />
<br />
This is less convenient, but cleaner from a packaging point-of-view, than putting the JAR file in <code>%{_javadir}</code>, and putting the JNI shared object in <code>%{_libdir}</code> to be loaded from the default library path. First, JNI shared objects are <code>dlopen</code>'d, and <code>dlopen</code>'d shared objects should not be placed directly in <code>%{_libdir}</code> since they are application-private data, and not libraries meant to be linked to directly -- that is, not meant to be shared. Second, placing the JAR file in <code>%{_javadir}</code> causes the build-classpath script to always load it, even when running on a runtime environment of the wrong arch, meaning that the <code>System.loadLibrary</code> line would fail.<br />
<br />
The plan is to eventually eliminate patching of the <code>System.loadLibrary</code> line and wrapper script by making <code>jpackage-utils</code> multilib aware. This involves the following changes: creating <code>%{_libdir}/java</code> and <code>%{_libdir}/jni</code> directories; giving JNI-containing packages the ability to require an architecture-specific runtime environment; adding support for specifying the required runtime architecture in a wrapper script; modifying <code>jpackage-utils</code>'s runtime scripts to search <code>%{_libdir}/java</code>; modifying IcedTea to look for JNI shared objects in <code>%{_libdir}/jni</code>.<br />
<br />
The <code>%{_jnidir}</code> rpm macro defines the main JNI jar repository. Like <code>%{_javadir}</code> it is declined in <code>-ext</code> and <code>-x.y.z</code> variants. It follows exactly the same rules as the <code>%{_javadir}</code>-derived tree structure, except that it hosts JAR files that use JNI.<br />
<br />
<code>%{_jnidir}</code> usually expands into <code>/usr/lib/java</code>.<br />
<br />
== Things to avoid ==<br />
=== Pre-built JAR files / Other bundled software ===<br />
Many Java projects re-ship their dependencies in their own releases. This is unacceptable in Fedora. All packages '''MUST''' be built from source and '''MUST''' enumerate their dependencies with <code>Requires</code>. They '''MUST NOT''' build against or re-ship the pre-included JAR files but instead symlink out to the JAR files provided by dependencies. There may arise rare cases that an upstream project is distributing JAR files that are actually not re-distributable<br />
by Fedora. In this situation, the JAR files themselves should not be redistributed -- even in the source zip. A modified source zip should be created with some sort of modifier in the name (ex. -CLEAN) along with instructions for reproducing. It is a good idea to have something similar to the following at the end of <code>%prep</code> (courtesy David Walluck):<br />
<br />
<pre><br />
JAR files=""<br />
for j in $(find -name \*.jar); do<br />
if [ ! -L $j ] ; then<br />
JAR files="$JAR files $j"<br />
fi<br />
done<br />
if [ ! -z "$JAR files" ] ; then<br />
echo "These JAR files should be deleted and symlinked to system JAR files: $JAR files"<br />
exit 1<br />
fi<br />
</pre><br />
<br />
=== Javadoc scriptlets ===<br />
Older JPackage packages contained <code>%post</code> scriptlets creating <code>%ghost</code> symlinks. These '''MUST''' not appear in Fedora Java packages and are actively being removed at JPackage.<br />
<br />
=== Selected rpmlint issues ===<br />
==== class-path-in-manifest ====<br />
Use <code>sed</code> to remove <code>class-path</code> elements in <code>MANIFEST.MF</code> (or whatever file is being used as the JAR manifest) prior to JAR creation. Example:<br />
<br />
<pre><br />
sed -i '/class-path/I d' META-INF/MANIFEST.MF<br />
</pre><br />
<br />
<br />
[[Category:Java]]<br />
[[Category:Packaging guidelines drafts]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=294362JBossAS7 in Fedora marketing collateral2012-07-03T06:28:47Z<p>Mojavelinux: Added Groovy and Ant</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
{{admon/important|Where did the Getting Started section go?|The text on this page is currently being used to produce a 5x7 postcard. The getting started commands were moved to a [[Getting_started_with_JBossAS7_in_Fedora|new wikipage]] and will soon be linked to other appropriate pages. Please continue to add to and edit the Getting Started with JBoss AS 7 page.}}<br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3, Ant, Groovy and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of Java<br />
* JBoss Application Server (Web Profile minus JPA 2, standalone mode only) makes its debut as an official Fedora package (jboss-as)<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone mode instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform (in testing)<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin<br />
* Groovy (added in Fedora 16)<br />
<br />
=== Get started with JBoss AS 7 and Fedora ===<br />
<br />
* [http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora]<br />
* [http://fedoraproject.org fedoraproject.org]<br />
<br />
=== Get involved with the Fedora Java SIG ===<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292867JBossAS7 in Fedora marketing collateral2012-06-19T18:27:23Z<p>Mojavelinux: Consolidated bullet points about JBoss AS package</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
{{admon/important|Where did the Getting Started section go?|The text on this page is currently being used to produce a 5x7 postcard. The getting started commands were moved to a [[Getting_started_with_JBossAS7_in_Fedora|new wikipage]] and will soon be linked to other appropriate pages. Please continue to add to and edit the Getting Started with JBoss AS 7 page.}}<br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of Java<br />
* JBoss Application Server (Web Profile minus JPA 2, standalone mode only) makes its debut as an official Fedora package (jboss-as)<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone mode instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform (in testing)<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin.<br />
<br />
=== Get started with JBoss AS 7 and Fedora ===<br />
<br />
* [http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora]<br />
* [http://fedoraproject.org fedoraproject.org]<br />
<br />
=== Get involved with the Fedora Java SIG ===<br />
<br />
* [http://fedoraproject.org/wiki/SIGs/Java fedoraproject.org/wiki/SIGs/Java]<br />
* [http://fedoraproject.org/wiki/Fedora-JBoss-Spin fedoraproject.org/wiki/Fedora-JBoss-Spin]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292287JBossAS7 in Fedora marketing collateral2012-06-16T17:54:22Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Eclipse 4, Apache Maven 3 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server (Web Profile in standalone mode) makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* Early release of the Eclipse 4.2 (Juno) Platform and Java IDE<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
* Additional JBoss development tools being packaged for the GSoC project to create a Fedora JBoss Spin.<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java<br />
fedoraproject.org/wiki/Fedora-JBoss-Spin</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292284JBossAS7 in Fedora marketing collateral2012-06-16T17:39:24Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Java and JBoss AS 7 on Fedora ===<br />
<br />
Fedora 17 provides a comprehensive Java application development suite featuring Java 7, JBoss Application Server (AS) 7, Apache Maven 3 and Thermostat.<br />
<br />
JBoss AS 7 is a fast and lightweight Java EE 6 application server and OSGi runtime. JBoss AS is the most widely adopted open source Java EE implementation.<br />
<br />
* Composed of best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up attributed to a highly optimized boot process, concurrent classloading and concurrent service coordinator.<br />
* Classloading done right. Showcases a preview of Java modularity to attain true application isolation. Hides server implementation classes from the application and only loads classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
* Java EE 6 (Web and Full Profile) and OSGi compliant (Fedora packages not yet certified)<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server (Web Profile in standalone mode) makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292283JBossAS7 in Fedora marketing collateral2012-06-16T17:21:32Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Composed with best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up times, attributed to a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. An early preview of Java modularity for true application isolation. Hides server implementation classes from the application and only loads the classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Thoroughly tested with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292280JBossAS7 in Fedora marketing collateral2012-06-16T16:51:41Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Composed with best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up times, attributed to a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. An early preview of Java modularity for true application isolation. Hides server implementation classes from the application and only loads the classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Tested thoroughly with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292279JBossAS7 in Fedora marketing collateral2012-06-16T16:50:26Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Composed with best of breed open source components, including Hibernate, Infinispan, JGroups, JBoss Modules and Weld.<br />
* Blazing fast start up times, attributed to a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. An early preview of Java modularity for true application isolation. Hides server implementation classes from the application and only loads the classes your application needs.<br />
* Lightweight and scalable as a result of an aggressive memory management policy.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Tested thoroughly with Arquillian, a component model for creating robust tests that execute inside the server runtime.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
* Thermostat monitoring and instrumentation tool for the Hotspot JVM, with support for monitoring multiple JVMs on multiple hosts<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292278JBossAS7 in Fedora marketing collateral2012-06-16T16:39:11Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as an official package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292277JBossAS7 in Fedora marketing collateral2012-06-16T16:38:25Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as a package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service (jboss-as) to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292276JBossAS7 in Fedora marketing collateral2012-06-16T16:37:35Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as a package in Fedora (jboss-as)<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292275JBossAS7 in Fedora marketing collateral2012-06-16T16:36:51Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (mvn), with optional resolution of system jar files (mvn-local), and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292274JBossAS7 in Fedora marketing collateral2012-06-16T16:34:50Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* Apache Maven 3 (with optional resolution of system jar files) and an integration of Maven with rpmbuild (mvn-rpmbuild)<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292273JBossAS7 in Fedora marketing collateral2012-06-16T16:31:20Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive memory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292272JBossAS7 in Fedora marketing collateral2012-06-16T16:30:58Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292271JBossAS7 in Fedora marketing collateral2012-06-16T16:29:00Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 as provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292270JBossAS7 in Fedora marketing collateral2012-06-16T16:28:23Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server making its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 as provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Stop the JBoss AS 7 system service<br />
sudo service jboss-as stop<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292269JBossAS7 in Fedora marketing collateral2012-06-16T16:27:19Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server making its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 as provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp -l $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292268JBossAS7 in Fedora marketing collateral2012-06-16T16:26:51Z<p>Mojavelinux: </p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) provided by OpenJDK 1.7.0, the open-source reference implementation of the Java Platform<br />
* JBoss Application Server making its debut as a package in Fedora<br />
* Effort underway to package the fully-compliant Java EE 6 Web Profile (JPA 2 as provided by Hibernate expected soon) and compliant OSGi runtime<br />
* Add-ons to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
* JBoss AS container adapters and a JMX-based test protocol for the Arquillian testing platform<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 system service<br />
sudo service jboss-as service<br />
Connect to the JBoss AS 7 management console (system instance)<br />
sudo jboss-cli -c<br />
Create a user instance of JBoss AS 7<br />
jboss-as-cp $HOME/jboss-as-instance<br />
Start the JBoss AS 7 user instance<br />
JBOSS_BASE_DIR=$HOME/jboss-as-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml<br />
Connect to the JBoss AS 7 management console (user instance)<br />
jboss-cli -c<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292266JBossAS7 in Fedora marketing collateral2012-06-16T16:16:07Z<p>Mojavelinux: More new features</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== Fedora and JBoss AS 7 ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers. <br />
<br />
JBoss AS 7 is a fast, lightweight, open source application server. <br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) as provided by OpenJDK 1.7.0, the open-source reference implementation of Java Platform<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort in progress to provide a fully-compliant Java EE 6 Web Profile (JPA 2 provided by Hibernate expected soon)<br />
* Includes additions to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A commandline interface (jboss-cli) to the JBoss AS management console<br />
* A script (jboss-add-user) to create management and application users for JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 service<br />
sudo service jboss-as service<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=JBossAS7_in_Fedora_marketing_collateral&diff=292264JBossAS7 in Fedora marketing collateral2012-06-16T16:01:21Z<p>Mojavelinux: undo bullet</p>
<hr />
<div>=== JBoss AS 7 in Fedora Marketing Flyer ===<br />
<br />
This is the brainstorming area for text for a flyer focused on AS 7 in F17. <br />
<br />
=== JBoss AS 7 in Fedora ===<br />
<br />
Fedora 17 provides a robust Java application development environment and JBoss AS 7, one of the most popular Java application servers.<br />
<br />
JBoss AS 7 is a fast, lightweight open source application server. Fedora 17 currently supports the web profile of AS 7 and plans to implement the full profile soon.<br />
<br />
=== JBoss AS 7 ===<br />
<br />
* Blazing fast start up times, courtesy of a highly optimized boot process, concurrent class loading and concurrent service coordinator.<br />
* Classloading done right. AS 7 provides an early preview of Java modularity for true application isolation. It hides server implementation classes from the application and only loads the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module.<br />
* Lightweight and scalable due to aggressive menory management.<br />
* User-focused, centralized administration. Manage a multi-server topology (domain mode) or an independent, development server (standalone mode) from a single control point.<br />
* Test applications with ease. AS 7 is integrated with Arquillian. Arquillian, a component model for integration tests that execute inside the real runtime environment, enables you to write tests for just about any use case your application encounters.<br />
<br />
=== New in Fedora 17 ===<br />
<br />
* Java 7 runtime (JRE) and development tools (JDK) as provided by OpenJDK 1.7.0, the open-source reference implementation of Java Platform<br />
* JBoss Application Server makes its debut as a package in Fedora<br />
* Effort underway to provide a compliant Java EE 6 Web Profile<br />
* Includes additions to the Web Profile such as the Java Messaging Service (JMS) provided by HornetQ and REST web services provided by RESTEasy<br />
* A systemd system service to control a standalone instance of JBoss AS<br />
* A script (jboss-as-cp) to create a unique instance (i.e., server configuration) of JBoss AS in userspace<br />
<br />
=== Get started with AS 7 in Fedora ===<br />
<br />
In a terminal, install JBoss AS 7 using yum<br />
sudo yum install jboss-as<br />
Start the JBoss AS 7 service<br />
sudo service jboss-as service<br />
<br />
===Learn more about Fedora===<br />
<br />
join.fedoraproject.org<br />
<br />
===Get involved with the Fedora Java SIG===<br />
<br />
fedoraproject.org/wiki/SIGs/Java</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=SIGs/Java&diff=288979SIGs/Java2012-05-23T03:07:28Z<p>Mojavelinux: Add JBoss Forge</p>
<hr />
<div>= Java Special Interest Group =<br />
[[File:DukeWithHelmet.png|frameless|200px]]<br />
<br />
<br />
A SIG for people who are interested in improving the state of Java in Fedora. This includes packaging Java libraries and applications, setting and improving standards for packaging them as RPM's and collaboratively managing bigger changes related to Java in Fedora.<br />
<br />
If you want to take the attention of the SIG members. Please open a bug report and make it block [https://bugzilla.redhat.com/show_bug.cgi?id=652183 FE-JAVASIG] <br />
<br />
== Meetings ==<br />
<br />
There will be informal [[SIGs/Java/Meetings| Java SIG meetings]] in the [[Fedora meeting channel | #fedora-meeting channel]] every other<br />
* Wednesday at 13:00 UTC.<br />
<br />
For more information about the past and upcoming meetings please see the meetings subpage: [[SIGs/Java/Meetings| Java/Meetings]]<br />
<br />
== IRC Channel ==<br />
<br />
Besides the [[SIGs/Java/Meetings| Java SIG meetings]] there is also existing a freenode channel for developers and users of java in Fedora: {{fpchat|#fedora-java}}<br />
<br />
== Mailing list ==<br />
There's a mailing list here named {{fplist|java-devel}} which you can join to ask questions.<br />
<br />
== Ongoing projects ==<br />
* [https://fedoraproject.org/wiki/JBossAS7 JBossAS7 packaging effort]<br />
* [https://fedoraproject.org/wiki/Eucalyptus Eucalyptus packaging effort] - includes Spring 3, GWT, Apache Axis 2, and eventually JasperReports<br />
* [https://bugzilla.redhat.com/showdependencytree.cgi?id=784596 JabRef packaging effort] (BibTeX editor written in Java)<br />
* [https://fedoraproject.org/wiki/OVirtPackaging oVirt packaging effort]<br />
<br />
== State of Affairs ==<br />
<br />
There have been few big updates and changes to core Java packages recently. Most notably [[MavenUpdate| update of Maven]] to version 2.2.1, rename of [[JakartaCommonsRename| jakarta-commons]] packages to apache-commons (still underway) and most recently update of ant to 1.8.x. All of these changes were mostly organized through bugzilla and wiki pages. This worked out mostly OK, but this could be good place for all tasks related to Java so that everyone can quickly see what is going on.<br />
<br />
Current state of Java [[Packaging:Java|packaging guidelines]] is not ideal. They are somewhat outdated and missing few things. See [[#Tasks| Tasks]] section for current state of this.<br />
<br />
If you would like to help us with packaging Java software, read how to [[PackageMaintainers/Join | join]] Fedora packagers or get in touch with us directly and we will guide you through the process.<br />
<br />
''Guidelines'' for building Java packages can be found on a [[Packaging/Java| separate page]].<br />
<br />
See [[Java_packaging_common_problems| Java packaging common problems]] page for help with common problems while building java packages and how to solve them.<br />
<br />
== Tasks ==<br />
* Look after Java and Eclipse release notes: https://fedoraproject.org/wiki/Documentation_Beats<br />
* Update [[Java]] page. Some parts are quite outdated (for example maven part)<br />
* Discuss strategies for completing Java packaging requirements for the ''AutoQA'' project (see [[User:Jlaska/autoqa_package_dependencies]]) - 2 packages ready for package review (htmlunit, htmlunit-core-js)<br />
<br />
== Currently Open Java Package Review Bugs==<br />
We generally like to get new Java packages into Fedora as long as they follow our packaging guidelines. Currently there is no simple way to query bugzilla for Java-only package reviews so people interested in java reviews have it a bit harder. Just go through [http://fedoraproject.org/PackageReviewStatus/NEW.html all open package reviews] or [http://bugzilla.redhat.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&longdesc=java&component=Package%20Review&longdesc_type=allwordssubstr&product=Fedora&classification=Fedora Java package reviews]. The second link can be incomplete, but should contain mosly Java packages.<br />
<br />
== Members ==<br />
<br />
''If you are interested in joining the SIG, please hang out at #fedora-java. If you have provenpackager or sponsor status, please tell us so we might use your help in critical situations :-) ''<br />
<br />
# [[User:Sochotni| Stanislav Ochotnicky]] (provenpackager)<br />
# [[User:Akurtakov| Alexander Kurtakov]] (provenpackager, sponsor)<br />
# [[User:Frankly3d| Frank Murphy]]<br />
# [[User:Lfarkas| Levente Farkas]]<br />
# [[User:Mbooth| Mat Booth]] (provenpackager, sponsor)<br />
# [[User:Adimania| Aditya Patawari]]<br />
# [[User:ldimaggi| Len DiMaggio]]<br />
# [[User:Orion| Orion Poplawski]] (provenpackager, sponsor)<br />
# [[User:Nushio| Juan Rodriguez]]<br />
# [[User:Zencyl | Eric Deering]]<br />
# [[User:gbraad | Gerard Braad]]<br />
# [[User:bozhidar | Bozhidar Batsov]]<br />
# [[User:Spike | Chris Spike]]<br />
# [[User:Guidograzioli | Guido Grazioli]]<br />
# [[User:hannes | Johannes Lips]]<br />
# [[User:mef | Mary Ellen Foster]] (provenpackager)<br />
# [[User:ke4qqq | David Nalley]] (provenpackager, sponsor)<br />
# [[User:Arg | Andy Grimm]] (provenpackager)<br />
# [[User:Goldmann | Marek Goldmann]] (provenpackager, sponsor)<br />
<br />
== Package Wishlist ==<br />
* clirr-maven-plugin (needed for apache-commons-math 2.1)<br />
* Eclipse WTP<br />
* JMesa <br />
* Stripes<br />
* Ibatis<br />
* Shiro<br />
* Apache Directory Studio for Eclipse - http://directory.apache.org/studio/<br />
* Memory Analyzer Tool - http://www.eclipse.org/mat/<br />
* Eclipse NSIS - http://eclipsensis.sourceforge.net/index.shtml<br />
* Ant Pack200 tasks - https://deployment.dev.java.net/<br />
* [http://retrotranslator.sourceforge.net/ retrotranslator-runtime] (Needed for commons-email tests)<br />
* [http://code.google.com/p/subethasmtp/ subethasmtp] (Needed for commons-email tests)<br />
* [http://code.google.com/p/gerrit/ Gerrit]<br />
* [http://gradle.org/ Gradle]<br />
* [http://tomee.apache.org/ Apache TomEE]<br />
* [http://jboss.org/forge JBoss Forge]<br />
<br />
== Useful links ==<br />
* [[Java_review_template| Template for doing Java package reviews]]<br />
* [[Java_packaging_common_problems| Tips & tricks for packaging java]]<br />
* [[Java| Java in Fedora]]<br />
* [[Java/FAQ| Java FAQ]]<br />
* [http://bugzilla.redhat.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&longdesc=java&component=Package%20Review&longdesc_type=allwordssubstr&product=Fedora&classification=Fedora Open Java package reviews]<br />
<br />
[[Category:SIGs]]<br />
[[Category:Language-specific SIGs]]<br />
[[Category:Packaging SIGs]]<br />
[[Category:Fedora special-interest groups|Java]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Summer_coding_ideas_for_2012&diff=276629Summer coding ideas for 20122012-03-10T00:03:05Z<p>Mojavelinux: add notes to gitlab proposal</p>
<hr />
<div>{{Admon/tip | Please feel free to add your idea here.}}<br />
<br />
{{Admon/tip |If you are a student and willing to suggest an idea please use the [[Summer_coding_ideas_for_2012/Students_Idea|Students Idea wiki page]]. Interested mentors can check the Students Idea page and undertake any interested idea those students are suggesting.}}<br />
<br />
Find an idea you like? Want to propose your own? See the Getting Started Guide with GSoC:<br />
<br />
https://fedoraproject.org/wiki/GSOC_2012<br />
<br />
You may be interested in ideas from [[Summer_coding_ideas_for_2011|2011]], [[Summer_coding_ideas_for_2010|2010]], [[Summer_coding_ideas_for_2009|2009]] and [[Summer_coding_ideas_for_2008|2008]].<br />
<br />
Further, last year accepted ideas from the Fedora Project can be found at [http://www.google-melange.com/gsoc/org/google/gsoc2011/fedora GSoC 2011 web site]<br />
<br />
== Students Welcome ==<br />
<br />
If you are a student looking forward to participate the GSoC 2012 with Fedora, please feel free to browse the idea list which is still growing. Do not hesitate to contact the mentors/ contributors as indicated in this page for any related clarification. If you are new to The Fedora project, following material would help you to get started. Further please sign-up with the [https://fedoraproject.org/wiki/FAS Fedora Account System(FAS)] if you are willing to continue with the Fedora project. <code>#fedora-devel</code>, IRC channel can be used to get instant support.<br />
<br />
# [https://fedoraproject.org/wiki/Foundation The Foundation]<br />
# [http://docs.fedoraproject.org/en-US/index.html Fedora Documentation (Users/ Contributors)]<br />
# [http://fedoraproject.org/wiki/Communicate/IRCHowTo How to work with IRC?]<br />
# [https://fedoraproject.org/wiki/FAS Fedora Account System] <br />
# [http://fedoraproject.org/wiki/Development Development]<br />
<br />
== Supporting Mentors ==<br />
<br />
Following contributors are also willing to support the GSoC 2012 program. (please feel free to add your self, attach the user page). Sometimes there should be some backing up mentors to mentor if the original mentor get busy with something for a short time period. In such case we need help.<br />
<br />
#[[User:Bckurera|Buddhike Kurera(Bckurera)]]<br />
#[[User:Quaid|Karsten Wade(Quaid)]]<br />
#[[User:Susmit|Susmit Shannigrahi(Susmit)]]<br />
# [[User:Duffy | Mo Duffy (Duffy)]]<br />
#[[User:Mmorsi | Mo Morsi]]<br />
<br />
==Draft of an idea==<br />
Please add your idea as follows.<br />
<br />
=== Project name ===<br />
<br />
''Status:'' <br />
<br />
''Summary of idea:''<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' <br />
<br />
''Mentor(s):''<br />
<br />
''Notes:''<br />
<br />
'''!!!The draft was changed slightly, please add required field as required!!!'''<br />
<br />
== Idea list for GSoC 2012==<br />
<br />
===Applications for desktop end users===<br />
These are coding projects that benefit end users of the Linux desktop.<br />
<br />
==== Integrate Proxy Settings and Network Connections(Locations) ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' The system should use an appropriate networking profile (e.g. Proxy settings) for each network connection.<br />
<br />
Gnome 2 had a concept of network locations in its Network Proxy configuration window. However, user should selected the appropriate location whenever he moves between networks. This idea is about providing an integration between NetworkManager and Desktop environments so that a user can create network profiles for each network location(connection) providing appropriate settings like proxy settings which is the main proposed setting here. NetworkManager can have a "Network Location" concept: for wireless networks, usually the name of the network (ESSID) is usually enough. For wired connections, DHCP servers can and usually do provide network's domain name, which can be used as the name of the location. It is nice if a user can associate each network location with a network settings profile which will be used whenever the user is connected to that network automatically. So, when you connect to a network, a corresponding network settings profile is activated automatically. <br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User:Hedayat|Hedayat Vatankhah]]<br />
<br />
''Mentor(s):''<br />
<br />
''Notes:'' There is an entry with some description in [http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/TODO NetworkManager TODO] which should be considered for the implementation<br />
<br />
==== Bringing the Fedora Desktop to the Cloud====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
[http://www.aeolusproject.org Aeolus] is an umbrella project that provides an open source API which to control any number of backend proprietary cloud providers. It allows us to write tooling that is able to deploy, monitor, and manager instances to any cloud provider such as EC2 or OpenStack in a Free and Open Manner. We need more tooling to interface with the various Aeolus components from the Fedora desktop (or any other) in novel ways such as command-line and gtk-based applications to deploy instances to the cheapest cloud provider or the one with the fastest response time, to monitor running instances using various visualizations, and more closely integrate local data and code w/ that on the cloud.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info about the Aeolus project. All the components which to build images for the cloud and control instances is in place and ready to go, just drop various bits (they are interoperable and interchangable) into an environment to be able to interact with the cloud, avoiding proprietary interfaces and vendor lockin.<br />
<br />
==== Web hosting control panel ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:''<br />
develop a free alternative of cpanel / plesk control panels, 100% compatible with fedora, and redhat enterprise Linux.<br />
written in python.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' itamarjp [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Ausil | Dennis Gilmore]] [[User: toshio | Toshio kuratomi]] <br />
<br />
''Notes:''<br />
<br />
==== Assemble a toolchain for recording screencasts easily ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Creating screencasts on Fedora and post-processing them for upload should be easy and fool proof.<br />
<br />
The [[Videos|Fedora Videos]] project has been launched to bring together a collection of screencasts that help people learn how to use Fedora. There's only one major hurdle, though. Capturing really good screencasts on Fedora, post-processing them to include an intro and outro and other effects, and finally exporting them to an open format is challenging. There are lots of different tools, but each one only gets you part of the way there and you have to be the glue to make it all work. And then there are the bugs.<br />
<br />
The goal of this project is to assemble a toolchain (a recommended collection of software available in the Fedora repositories) and write a comprehensive tutorial for how to create an professional-looking screencast. That may included chasing down & fixing bugs in the existing tools, discovering new tools and getting them packaged and learning about techniques in the environment around the computer, such as how to select & setup a microphone or how to draft a good speaking script. One possible task in the project is to add sound recording support to the Gnome 3 desktop recorder. Currently, the desktop recorder only grabs the video of the screen.<br />
<br />
The student will get support and advice from the Fedora Videos team since they are trying to learn how to create these screencasts.<br />
<br />
''Knowledge prerequisite:'' gstreamer, video and sound editing, blender<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[Videos|Fedora Videos Team]]<br />
<br />
''Mentor(s):'' ???<br />
<br />
''Notes:'' <br />
<br />
===Applications for programmers===<br />
<br />
==== Implement a Socket API for GlusterFS ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' In transporting data across networks, in the case of writing and reading replicated and distributed data on GlusterFS, programmers could use a better method to send large amounts of data with lower latency and less overhead in comparison to standard methods, such as HTTP. This project would implement a socket API for GlusterFS so that programmers, using any language, could create low-latency applications that utilize GlusterFS for distributed storage.<br />
<br />
''Knowledge prerequisite:'' C, GlusterFS internals<br />
<br />
''Skill level:'' High<br />
<br />
''Contacts:'' johnmark [AT]redhat [DOT] com , abperiasamy [AT] gmail [DOT] com<br />
<br />
''Mentor(s):'' Anand Avati - Mentor, AB Periasamy - Co-mentor, [[User:johnmark|John Mark Walker]] - Co-mentor<br />
<br />
===Infrastructure for Fedora contributors and users===<br />
==== Implement a survey infrastructure for the Fedora Project====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Surveys are important to increase the quality of a service, and it is true for the Fedora project as well.(discussions [http://meetbot.fedoraproject.org/fedora-meeting/2011-12-24/apac.2011-12-24-04.00.log.html#l-310]) In this project it is supposed to implement a survey infrastructure facility so that the contributors can use for various activities as per the need.<br />
<br />
The concern is to develop a simple web base survey system OR implement a existing survey project and customized as required, so that contributors can easily create surveys and dig for results as well. Linking with the [FAS|FAS] is required. Further it should be compatible with anonymous and open ID so that if the creator set for those authentication the survey should allow those authentications. Statistics and other required reports can be obtained. So that it is easy to analyse.<br />
<br />
''Knowledge prerequisite:'' PHP, Python, Ruby are preferred, MySQL (database handling), experience with Lime Survey would be an advantage <br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' kevin [AT]scrye [DOT] com , bckurera [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Kevin|Kevin Fenzi]] - Mentor, [[User:Bckurera|Buddhike Kurera]] Co-mentor.<br />
<br />
''Notes:'' This idea is improving, please contact for upto-date details.<br />
<br />
==== Design Hub: FLOSS Collaboration for FLOSS Designers ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Free software designers don't have a great set of tools to work with to collaborate with each other and with the community on their design work. With this project, we'd like to make progress towards fixing that. We have some disparate ideas / tools that we'd like to be integrated:<br />
<br />
* [http://sparkleshare.org Sparkleshare] - a git-backed, Dropbox like system that will automatically check in and push files in project directly to a shared git repo<br />
* [https://github.com/garrett/magicmockup Magic Mockup] - a coffeescript/javascript you can insert into an SVG of mockups to enable interactive, click-through mockups ([http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/ see a demo here]<br />
* [http://blog.linuxgrrl.com/category/design-hub/ Design Hub] - an idea and a ruby on rails prototype of a web front end that could potentially serve as a front end to git repos with design assets *and* serve as well as a front end to magic mockup mockups in said repos<br />
* [http://inkscape.org Inkscape] is our preferred design tool of choice; it would be great if it had some GUI integration with Magic Mockup, Sparkleshare, and Design Hub<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' duffy at fedoraproject [dot] org<br />
<br />
''Mentor(s):'' [[User:Duffy | Mo Duffy]], [[User:Emichan | Emily Dirsh]]<br />
<br />
''Notes:'' We can provide a development platform for the web UI at openshift.redhat.com. Also, note this project doesn't just benefit Fedora designers, but it benefits all FLOSS designers.<br />
<br />
==== Implement a unit test framework for fedpkg and rpkg ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Unit tests are good. Testing is good. fedpkg and it's backend rpkg is a growing code base, gaining more and more contributors. It lacks a unit test framework which would be very beneficial to the code base for making sure contributions don't break the code in subtle ways.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' jkeating [AT]redhat [DOT] com<br />
<br />
''Mentor(s):'' [[User:jkeating]] - Mentor<br />
<br />
''Notes:'' This project is in python.<br />
<br />
==== Insight use cases for calendar ====<br />
<br />
Status: Proposed - Draft<br />
<br />
Insight project requirement to be implemented. More details can be found at the wiki, [[Insight_use_cases_for_calendar]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on PHP and Drupal would be essential <br />
<br />
''Skill level:'' Medium<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]], [[User:Herlo|Clint Savage]] & [[Insight|Insight Team]]<br />
<br />
Mentor(s): [[User:Tatica|María "tatica"]], [[User:Asrob|Peter Tibor Borsa]] and [[User:Bckurera|Buddhika Kurera]] <br />
<br />
Notes: -<br />
<br />
==== Insight use cases for status and microblogging ====<br />
<br />
Status: Proposed - Draft<br />
<br />
These are use cases for status and microblogging services that we might want to provide through Insight. More details can be found at the wiki, [[Insight_use_cases_for_status_and_microblogging]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on Drupal would be essential.<br />
<br />
''Skill level:'' High<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]]<br />
<br />
Mentor(s): -<br />
<br />
Notes: Students who are interested on this topic is highly requested to contact the mentors as the first step. Knowledge on Drupal would be essential.<br />
<br />
====isitfedoraruby.com====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
Right now most Ruby programmers make use of the [http://rubygems.org/ gem] package management system to install Ruby libraries on their system. The [http://fedoraproject.org/wiki/Ruby_SIG Fedora/Ruby] community works hard to convert these gems into rpms for inclusion in the Fedora stack, making use of various tooling such as [https://github.com/lutter/gem2rpm gem2rpm]. We are looking for more tools and capabilities around Ruby / Fedora integration, namely to reduce the overhead in supporting Ruby on Fedora and to promote Fedora as the de-facto platform for Ruby development.<br />
<br />
As part of this, we would like to develop a isitfedoraruby.com website (similar to [http://isitruby19.com/ isitruby19] and other sites like it) to promote the ruby stack on Fedora and the Fedora/Ruby development effort, highlighting success stories, use cases, ways contributors can help, etc<br />
<br />
''Knowledge prerequisite:'' <br />
<br />
''Skill level:'' <br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info. This project should be written in Ruby<br />
<br />
==== Setup Gitlab as a front end for Fedora Hosted git repositories ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' To setup [http://gitlabhq.com/ Gitlab] as a front end for git repositories at [fedorahosted.org].<br />
<br />
Git has fundamentally improved the way that developers share code. The barrier to sharing code has virtually been eliminated. We are also seeing the emergence of a new dynamic called "Social Coding". There's no better example of this than Github.<br />
<br />
Creating an environment to foster social coding, and a low barrier to sharing code, requires more than just git, though. A lot of what makes Github successful with git is the web-based front end. That explains why there is such a dramatic difference between Github and fedorahosted.org, and why many projects are moving to Github instead.<br />
<br />
Fortunately, there is an open source application named Gitlab that provides much of the interactive functionality and usability that is found at Github. The goal of this project is to bring that experience to fedorahosted.org by setting up Gitlab.<br />
<br />
This project will require working with the infrastructure team to get the necessary prerequisites installed, find a server to host the application and configure the existing projects to be wired to this interface.<br />
<br />
''Knowledge prerequisite:'' Ruby, git, Linux system administration (web servers, authentication)<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[User:mojavelinux|Dan Allen]] (general), [[User:Vondruch|Vít Ondruch]] (packaging)<br />
<br />
''Mentor(s):'' Ranjib Dey (tentative), Seth Vidal (tentative)<br />
<br />
''Notes:'' This idea is definitely something the Fedora project is interested in pursuing. The work in this project will be carried on after the project, and is an opportunity for a longer-term involvement in Fedora.<br />
<br />
See the discussion on the Fedora Infrastructure list about implementation details: http://lists.fedoraproject.org/pipermail/infrastructure/2012-March/011463.html<br />
<br />
A demo of Gitlab can be found here: http://gitlabhq.com/demo.html<br />
<br />
===Linux system services===<br />
===Improving Fedora packaging===<br />
<br />
==== Java API/ABI changes checker ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Libraries written in Java add, remove and modify their public interfaces from time to time. This is normal, but currently it is very hard to guess effect an update of library to new version will have on rest of the system. What is needed is a tool that would be able to tell us that "With update of package java-library to version 2.0, function X(b) has been removed. This function is used in package java-app". There are already a few open-source projects that can do some of the analysis needed. This would be of interest to whole Java world I believe and would enable safer and easier updates. To get an idea of similar projects see [http://linuxtesting.org/upstream-tracker/java/ Java API compliance checker] and [https://sites.google.com/site/obriencj/projects/java-classfile-python-module Python Javaclass project]<br />
<br />
''Knowledge prerequisite:'' Knowledge of Java (inheritance rules, generics, etc.) and probably some scripting language(s)<br />
<br />
''Skill level:'' Fairly high<br />
<br />
''Contacts:'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Mentor(s):'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Notes:'' Don't hesitate to get in touch via IRC (sochotni@FreeNode) or email (contact on my user page).<br />
<br />
==== Maven FOSS Repository Extension ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' With the inception of Maven we have a means to standardize the building of Java projects. However it has also resulted in the usage of a very wide dependency set by these Java projects. This makes it very hard to integrate those projects on a single platform (be it Fedora or JBoss Application Server (or the combination)). In essence during packaging all these dependencies must be lined up to form a single consistent component set. Thus each project will only have those components available which are actually available on the target platform. This is very hard to enforce using standard Maven setup.<br />
For Fedora I'm envisioning a Maven extension that makes sure only sanctioned components are used during the build (without putting a burden on the packager). This will allow developers who are not on Fedora to also build with this extension and thus verify (and fix) issues which are the result of "Fedora packaging".<br />
A prototype can be viewed at [https://github.com/wolfc/fedora-maven Fedora Maven Extension].<br />
<br />
''Knowledge prerequisite:'' Knowledge of Maven<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Mentor(s):'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Notes:'' You can find me at irc.freenode.net #fedora-java wolfc<br />
<br />
===Fedora Spins and remixes===<br />
<br />
==== Fedora Audio Creation Spin ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' To create a Fedora Audio spin showcasing the rich and diverse landscape of Linux Audio production.<br />
<br />
The [https://fedoraproject.org/wiki/Audio_Creation Fedora Audio Creation SIG] is a collection of enthusiastic Fedora users driven by the common desire to make the best Linux distribution also the best for Music creation and Audio Production. <br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source audio projects and integrating many of the packages from the PlanetCCRMA repository into Fedora. Other tasks may include the testing of kickstart files and developing small applications to better integrate with the Fedora Desktop. <br />
<br />
Ideally, interested candidates will have a passion for Music/Audio Production. Basic scripting knowledge and the ability to compile projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus. <br />
<br />
Interested? Why wait, submit an audio package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join_the_package_collection_maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (bash/python)<br />
<br />
''Skill level:'' Rudimentry<br />
<br />
''Contacts:'' [[User:bsjones|Brendan Jones]]<br />
<br />
''Mentor(s):'' [[User:bsjones|Brendan Jones]]<br />
<br />
==== Fedora JBoss Spin ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' To create a Fedora JBoss spin that helps Java developers get started quickly using JBoss software.<br />
<br />
The [https://fedoraproject.org/wiki/SIGs/Java Java SIG] and the [https://fedoraproject.org/wiki/JBossAS7 JBoss AS 7 on Fedora Initiative] is a cross-section of enthusiastic Fedora users driven by the common desire to make the Fedora the best OS for developing with JBoss software.<br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source Java and JBoss projects and integrating many of the packages from the JBoss Community into Fedora. Packages in particular include JBoss AS 7, JBoss Tools and JBoss Forge. Other tasks may include the testing of kickstart files and developing configurations to better integrate with the Fedora Desktop. <br />
<br />
There could be two variants of this spin (feel free to choose). One is on the developer needing a good desktop to create JBoss-based applications (things like Eclipse + JBoss Tools, AS 7, Forge, a database, and so on). The other focus is on getting a server setup so that it can run the application. That would also be where the upcoming OpenShift toolset will come into play.<br />
<br />
Ideally, interested candidates will have a passion for Java development using JBoss software. Basic scripting knowledge and the ability to compile Java projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus, but not required.<br />
<br />
Interested? Why wait, submit a Java package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join the package collection maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (Java, shell)<br />
<br />
''Skill level:'' Rudimentary<br />
<br />
''Contacts:'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf], [http://community.jboss.org/people/alrubinger Andrew Rubinger], [Max Andersen https://community.jboss.org/people/maxandersen]<br />
<br />
''Mentor(s):'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
==== Educational Application for Fedora Robotics Suite ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of Idea:'' Create an educational app introducing software from Fedora Robotics Suite<br />
<br />
The [[SIGs/Robotics|Fedora Robotics SIG]] is creating a [[Features/RoboticsSuite|Robotics Suite]] consisting of many packages useful in robotics. We want to develop a demonstration application introducing new users step by step to core packages like [http://www.fawkesrobotics.org Fawkes] and [http://playerstage.sourceforge.net Player/Stage]. It would feature multiple game-like levels with increasing complexity. The general task would be to instruct the robot to fulfill a specific task in a simulation environment.<br />
<br />
<br />
''Knowledge prerequisite:'' Developing this requires a strong background in C++, a background in robotics is preferred but not necessary. You should be able to familiarize yourself with new software quickly. User visible parts will require GUI programming using Gtkmm.<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' [[User:Timn|Tim Niemueller]]<br />
<br />
''Mentor(s):'' [[User:Timn|Tim Niemueller]]<br />
<br />
=== Applications for systems administrators ===<br />
<br />
==== RHQ-agent to interface with Matahari ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Write a RHQ-agent in Python and make it interface with Matahari to pick up metrics that are provided by Matahari from Fedora or RHEL systems. The agent would talk to the RHQ server via the REST api and push metrics to RHQ etc. This agent will not implement the full functionality of the RHQ java agent.<br />
<br />
While RHQ is written in Java, this project does not need any Java knowledge.<br />
<br />
''Knowledge prerequisite:'' Python, Linux system administration, qpid, principles of REST<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' Heiko Rupp <pilhuhn><br />
<br />
''Mentor(s):'' Heiko Rupp <pilhuhn><br />
<br />
''Notes:'' RHQ wiki is at http://rhq-project.org/<br />
<br />
<br />
[[Category:Summer coding 2012]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Summer_coding_ideas_for_2012&diff=276628Summer coding ideas for 20122012-03-09T23:59:56Z<p>Mojavelinux: mentors</p>
<hr />
<div>{{Admon/tip | Please feel free to add your idea here.}}<br />
<br />
{{Admon/tip |If you are a student and willing to suggest an idea please use the [[Summer_coding_ideas_for_2012/Students_Idea|Students Idea wiki page]]. Interested mentors can check the Students Idea page and undertake any interested idea those students are suggesting.}}<br />
<br />
Find an idea you like? Want to propose your own? See the Getting Started Guide with GSoC:<br />
<br />
https://fedoraproject.org/wiki/GSOC_2012<br />
<br />
You may be interested in ideas from [[Summer_coding_ideas_for_2011|2011]], [[Summer_coding_ideas_for_2010|2010]], [[Summer_coding_ideas_for_2009|2009]] and [[Summer_coding_ideas_for_2008|2008]].<br />
<br />
Further, last year accepted ideas from the Fedora Project can be found at [http://www.google-melange.com/gsoc/org/google/gsoc2011/fedora GSoC 2011 web site]<br />
<br />
== Students Welcome ==<br />
<br />
If you are a student looking forward to participate the GSoC 2012 with Fedora, please feel free to browse the idea list which is still growing. Do not hesitate to contact the mentors/ contributors as indicated in this page for any related clarification. If you are new to The Fedora project, following material would help you to get started. Further please sign-up with the [https://fedoraproject.org/wiki/FAS Fedora Account System(FAS)] if you are willing to continue with the Fedora project. <code>#fedora-devel</code>, IRC channel can be used to get instant support.<br />
<br />
# [https://fedoraproject.org/wiki/Foundation The Foundation]<br />
# [http://docs.fedoraproject.org/en-US/index.html Fedora Documentation (Users/ Contributors)]<br />
# [http://fedoraproject.org/wiki/Communicate/IRCHowTo How to work with IRC?]<br />
# [https://fedoraproject.org/wiki/FAS Fedora Account System] <br />
# [http://fedoraproject.org/wiki/Development Development]<br />
<br />
== Supporting Mentors ==<br />
<br />
Following contributors are also willing to support the GSoC 2012 program. (please feel free to add your self, attach the user page). Sometimes there should be some backing up mentors to mentor if the original mentor get busy with something for a short time period. In such case we need help.<br />
<br />
#[[User:Bckurera|Buddhike Kurera(Bckurera)]]<br />
#[[User:Quaid|Karsten Wade(Quaid)]]<br />
#[[User:Susmit|Susmit Shannigrahi(Susmit)]]<br />
# [[User:Duffy | Mo Duffy (Duffy)]]<br />
#[[User:Mmorsi | Mo Morsi]]<br />
<br />
==Draft of an idea==<br />
Please add your idea as follows.<br />
<br />
=== Project name ===<br />
<br />
''Status:'' <br />
<br />
''Summary of idea:''<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' <br />
<br />
''Mentor(s):''<br />
<br />
''Notes:''<br />
<br />
'''!!!The draft was changed slightly, please add required field as required!!!'''<br />
<br />
== Idea list for GSoC 2012==<br />
<br />
===Applications for desktop end users===<br />
These are coding projects that benefit end users of the Linux desktop.<br />
<br />
==== Integrate Proxy Settings and Network Connections(Locations) ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' The system should use an appropriate networking profile (e.g. Proxy settings) for each network connection.<br />
<br />
Gnome 2 had a concept of network locations in its Network Proxy configuration window. However, user should selected the appropriate location whenever he moves between networks. This idea is about providing an integration between NetworkManager and Desktop environments so that a user can create network profiles for each network location(connection) providing appropriate settings like proxy settings which is the main proposed setting here. NetworkManager can have a "Network Location" concept: for wireless networks, usually the name of the network (ESSID) is usually enough. For wired connections, DHCP servers can and usually do provide network's domain name, which can be used as the name of the location. It is nice if a user can associate each network location with a network settings profile which will be used whenever the user is connected to that network automatically. So, when you connect to a network, a corresponding network settings profile is activated automatically. <br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User:Hedayat|Hedayat Vatankhah]]<br />
<br />
''Mentor(s):''<br />
<br />
''Notes:'' There is an entry with some description in [http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/TODO NetworkManager TODO] which should be considered for the implementation<br />
<br />
==== Bringing the Fedora Desktop to the Cloud====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
[http://www.aeolusproject.org Aeolus] is an umbrella project that provides an open source API which to control any number of backend proprietary cloud providers. It allows us to write tooling that is able to deploy, monitor, and manager instances to any cloud provider such as EC2 or OpenStack in a Free and Open Manner. We need more tooling to interface with the various Aeolus components from the Fedora desktop (or any other) in novel ways such as command-line and gtk-based applications to deploy instances to the cheapest cloud provider or the one with the fastest response time, to monitor running instances using various visualizations, and more closely integrate local data and code w/ that on the cloud.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info about the Aeolus project. All the components which to build images for the cloud and control instances is in place and ready to go, just drop various bits (they are interoperable and interchangable) into an environment to be able to interact with the cloud, avoiding proprietary interfaces and vendor lockin.<br />
<br />
==== Web hosting control panel ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:''<br />
develop a free alternative of cpanel / plesk control panels, 100% compatible with fedora, and redhat enterprise Linux.<br />
written in python.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' itamarjp [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Ausil | Dennis Gilmore]] [[User: toshio | Toshio kuratomi]] <br />
<br />
''Notes:''<br />
<br />
==== Assemble a toolchain for recording screencasts easily ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Creating screencasts on Fedora and post-processing them for upload should be easy and fool proof.<br />
<br />
The [[Videos|Fedora Videos]] project has been launched to bring together a collection of screencasts that help people learn how to use Fedora. There's only one major hurdle, though. Capturing really good screencasts on Fedora, post-processing them to include an intro and outro and other effects, and finally exporting them to an open format is challenging. There are lots of different tools, but each one only gets you part of the way there and you have to be the glue to make it all work. And then there are the bugs.<br />
<br />
The goal of this project is to assemble a toolchain (a recommended collection of software available in the Fedora repositories) and write a comprehensive tutorial for how to create an professional-looking screencast. That may included chasing down & fixing bugs in the existing tools, discovering new tools and getting them packaged and learning about techniques in the environment around the computer, such as how to select & setup a microphone or how to draft a good speaking script. One possible task in the project is to add sound recording support to the Gnome 3 desktop recorder. Currently, the desktop recorder only grabs the video of the screen.<br />
<br />
The student will get support and advice from the Fedora Videos team since they are trying to learn how to create these screencasts.<br />
<br />
''Knowledge prerequisite:'' gstreamer, video and sound editing, blender<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[Videos|Fedora Videos Team]]<br />
<br />
''Mentor(s):'' ???<br />
<br />
''Notes:'' <br />
<br />
===Applications for programmers===<br />
<br />
==== Implement a Socket API for GlusterFS ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' In transporting data across networks, in the case of writing and reading replicated and distributed data on GlusterFS, programmers could use a better method to send large amounts of data with lower latency and less overhead in comparison to standard methods, such as HTTP. This project would implement a socket API for GlusterFS so that programmers, using any language, could create low-latency applications that utilize GlusterFS for distributed storage.<br />
<br />
''Knowledge prerequisite:'' C, GlusterFS internals<br />
<br />
''Skill level:'' High<br />
<br />
''Contacts:'' johnmark [AT]redhat [DOT] com , abperiasamy [AT] gmail [DOT] com<br />
<br />
''Mentor(s):'' Anand Avati - Mentor, AB Periasamy - Co-mentor, [[User:johnmark|John Mark Walker]] - Co-mentor<br />
<br />
===Infrastructure for Fedora contributors and users===<br />
==== Implement a survey infrastructure for the Fedora Project====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Surveys are important to increase the quality of a service, and it is true for the Fedora project as well.(discussions [http://meetbot.fedoraproject.org/fedora-meeting/2011-12-24/apac.2011-12-24-04.00.log.html#l-310]) In this project it is supposed to implement a survey infrastructure facility so that the contributors can use for various activities as per the need.<br />
<br />
The concern is to develop a simple web base survey system OR implement a existing survey project and customized as required, so that contributors can easily create surveys and dig for results as well. Linking with the [FAS|FAS] is required. Further it should be compatible with anonymous and open ID so that if the creator set for those authentication the survey should allow those authentications. Statistics and other required reports can be obtained. So that it is easy to analyse.<br />
<br />
''Knowledge prerequisite:'' PHP, Python, Ruby are preferred, MySQL (database handling), experience with Lime Survey would be an advantage <br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' kevin [AT]scrye [DOT] com , bckurera [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Kevin|Kevin Fenzi]] - Mentor, [[User:Bckurera|Buddhike Kurera]] Co-mentor.<br />
<br />
''Notes:'' This idea is improving, please contact for upto-date details.<br />
<br />
==== Design Hub: FLOSS Collaboration for FLOSS Designers ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Free software designers don't have a great set of tools to work with to collaborate with each other and with the community on their design work. With this project, we'd like to make progress towards fixing that. We have some disparate ideas / tools that we'd like to be integrated:<br />
<br />
* [http://sparkleshare.org Sparkleshare] - a git-backed, Dropbox like system that will automatically check in and push files in project directly to a shared git repo<br />
* [https://github.com/garrett/magicmockup Magic Mockup] - a coffeescript/javascript you can insert into an SVG of mockups to enable interactive, click-through mockups ([http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/ see a demo here]<br />
* [http://blog.linuxgrrl.com/category/design-hub/ Design Hub] - an idea and a ruby on rails prototype of a web front end that could potentially serve as a front end to git repos with design assets *and* serve as well as a front end to magic mockup mockups in said repos<br />
* [http://inkscape.org Inkscape] is our preferred design tool of choice; it would be great if it had some GUI integration with Magic Mockup, Sparkleshare, and Design Hub<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' duffy at fedoraproject [dot] org<br />
<br />
''Mentor(s):'' [[User:Duffy | Mo Duffy]], [[User:Emichan | Emily Dirsh]]<br />
<br />
''Notes:'' We can provide a development platform for the web UI at openshift.redhat.com. Also, note this project doesn't just benefit Fedora designers, but it benefits all FLOSS designers.<br />
<br />
==== Implement a unit test framework for fedpkg and rpkg ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Unit tests are good. Testing is good. fedpkg and it's backend rpkg is a growing code base, gaining more and more contributors. It lacks a unit test framework which would be very beneficial to the code base for making sure contributions don't break the code in subtle ways.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' jkeating [AT]redhat [DOT] com<br />
<br />
''Mentor(s):'' [[User:jkeating]] - Mentor<br />
<br />
''Notes:'' This project is in python.<br />
<br />
==== Insight use cases for calendar ====<br />
<br />
Status: Proposed - Draft<br />
<br />
Insight project requirement to be implemented. More details can be found at the wiki, [[Insight_use_cases_for_calendar]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on PHP and Drupal would be essential <br />
<br />
''Skill level:'' Medium<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]], [[User:Herlo|Clint Savage]] & [[Insight|Insight Team]]<br />
<br />
Mentor(s): [[User:Tatica|María "tatica"]], [[User:Asrob|Peter Tibor Borsa]] and [[User:Bckurera|Buddhika Kurera]] <br />
<br />
Notes: -<br />
<br />
==== Insight use cases for status and microblogging ====<br />
<br />
Status: Proposed - Draft<br />
<br />
These are use cases for status and microblogging services that we might want to provide through Insight. More details can be found at the wiki, [[Insight_use_cases_for_status_and_microblogging]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on Drupal would be essential.<br />
<br />
''Skill level:'' High<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]]<br />
<br />
Mentor(s): -<br />
<br />
Notes: Students who are interested on this topic is highly requested to contact the mentors as the first step. Knowledge on Drupal would be essential.<br />
<br />
====isitfedoraruby.com====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
Right now most Ruby programmers make use of the [http://rubygems.org/ gem] package management system to install Ruby libraries on their system. The [http://fedoraproject.org/wiki/Ruby_SIG Fedora/Ruby] community works hard to convert these gems into rpms for inclusion in the Fedora stack, making use of various tooling such as [https://github.com/lutter/gem2rpm gem2rpm]. We are looking for more tools and capabilities around Ruby / Fedora integration, namely to reduce the overhead in supporting Ruby on Fedora and to promote Fedora as the de-facto platform for Ruby development.<br />
<br />
As part of this, we would like to develop a isitfedoraruby.com website (similar to [http://isitruby19.com/ isitruby19] and other sites like it) to promote the ruby stack on Fedora and the Fedora/Ruby development effort, highlighting success stories, use cases, ways contributors can help, etc<br />
<br />
''Knowledge prerequisite:'' <br />
<br />
''Skill level:'' <br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info. This project should be written in Ruby<br />
<br />
==== Setup Gitlab as a front end for Fedora Hosted git repositories ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' To setup [http://gitlabhq.com/ Gitlab] as a front end for git repositories at [fedorahosted.org].<br />
<br />
Git has fundamentally improved the way that developers share code. The barrier to sharing code has virtually been eliminated. We are also seeing the emergence of a new dynamic called "Social Coding". There's no better example of this than Github.<br />
<br />
Creating an environment to foster social coding, and a low barrier to sharing code, requires more than just git, though. A lot of what makes Github successful with git is the web-based front end. That explains why there is such a dramatic difference between Github and fedorahosted.org, and why many projects are moving to Github instead.<br />
<br />
Fortunately, there is an open source application named Gitlab that provides much of the interactive functionality and usability that is found at Github. The goal of this project is to bring that experience to fedorahosted.org by setting up Gitlab.<br />
<br />
This project will require working with the infrastructure team to get the necessary prerequisites installed, find a server to host the application and configure the existing projects to be wired to this interface.<br />
<br />
''Knowledge prerequisite:'' Ruby, git, Linux system administration (web servers, authentication)<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[User:mojavelinux|Dan Allen]] (general), [[User:Vondruch|Vít Ondruch]] (packaging)<br />
<br />
''Mentor(s):'' Ranjib Dey (tentative), Seth Vidal (tentative)<br />
<br />
''Notes:'' This idea is something we need, but we don't yet have a driver for it. A demo of Gitlab can be found here: http://gitlabhq.com/demo.html<br />
<br />
===Linux system services===<br />
===Improving Fedora packaging===<br />
<br />
==== Java API/ABI changes checker ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Libraries written in Java add, remove and modify their public interfaces from time to time. This is normal, but currently it is very hard to guess effect an update of library to new version will have on rest of the system. What is needed is a tool that would be able to tell us that "With update of package java-library to version 2.0, function X(b) has been removed. This function is used in package java-app". There are already a few open-source projects that can do some of the analysis needed. This would be of interest to whole Java world I believe and would enable safer and easier updates. To get an idea of similar projects see [http://linuxtesting.org/upstream-tracker/java/ Java API compliance checker] and [https://sites.google.com/site/obriencj/projects/java-classfile-python-module Python Javaclass project]<br />
<br />
''Knowledge prerequisite:'' Knowledge of Java (inheritance rules, generics, etc.) and probably some scripting language(s)<br />
<br />
''Skill level:'' Fairly high<br />
<br />
''Contacts:'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Mentor(s):'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Notes:'' Don't hesitate to get in touch via IRC (sochotni@FreeNode) or email (contact on my user page).<br />
<br />
==== Maven FOSS Repository Extension ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' With the inception of Maven we have a means to standardize the building of Java projects. However it has also resulted in the usage of a very wide dependency set by these Java projects. This makes it very hard to integrate those projects on a single platform (be it Fedora or JBoss Application Server (or the combination)). In essence during packaging all these dependencies must be lined up to form a single consistent component set. Thus each project will only have those components available which are actually available on the target platform. This is very hard to enforce using standard Maven setup.<br />
For Fedora I'm envisioning a Maven extension that makes sure only sanctioned components are used during the build (without putting a burden on the packager). This will allow developers who are not on Fedora to also build with this extension and thus verify (and fix) issues which are the result of "Fedora packaging".<br />
A prototype can be viewed at [https://github.com/wolfc/fedora-maven Fedora Maven Extension].<br />
<br />
''Knowledge prerequisite:'' Knowledge of Maven<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Mentor(s):'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Notes:'' You can find me at irc.freenode.net #fedora-java wolfc<br />
<br />
===Fedora Spins and remixes===<br />
<br />
==== Fedora Audio Creation Spin ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' To create a Fedora Audio spin showcasing the rich and diverse landscape of Linux Audio production.<br />
<br />
The [https://fedoraproject.org/wiki/Audio_Creation Fedora Audio Creation SIG] is a collection of enthusiastic Fedora users driven by the common desire to make the best Linux distribution also the best for Music creation and Audio Production. <br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source audio projects and integrating many of the packages from the PlanetCCRMA repository into Fedora. Other tasks may include the testing of kickstart files and developing small applications to better integrate with the Fedora Desktop. <br />
<br />
Ideally, interested candidates will have a passion for Music/Audio Production. Basic scripting knowledge and the ability to compile projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus. <br />
<br />
Interested? Why wait, submit an audio package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join_the_package_collection_maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (bash/python)<br />
<br />
''Skill level:'' Rudimentry<br />
<br />
''Contacts:'' [[User:bsjones|Brendan Jones]]<br />
<br />
''Mentor(s):'' [[User:bsjones|Brendan Jones]]<br />
<br />
==== Fedora JBoss Spin ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' To create a Fedora JBoss spin that helps Java developers get started quickly using JBoss software.<br />
<br />
The [https://fedoraproject.org/wiki/SIGs/Java Java SIG] and the [https://fedoraproject.org/wiki/JBossAS7 JBoss AS 7 on Fedora Initiative] is a cross-section of enthusiastic Fedora users driven by the common desire to make the Fedora the best OS for developing with JBoss software.<br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source Java and JBoss projects and integrating many of the packages from the JBoss Community into Fedora. Packages in particular include JBoss AS 7, JBoss Tools and JBoss Forge. Other tasks may include the testing of kickstart files and developing configurations to better integrate with the Fedora Desktop. <br />
<br />
There could be two variants of this spin (feel free to choose). One is on the developer needing a good desktop to create JBoss-based applications (things like Eclipse + JBoss Tools, AS 7, Forge, a database, and so on). The other focus is on getting a server setup so that it can run the application. That would also be where the upcoming OpenShift toolset will come into play.<br />
<br />
Ideally, interested candidates will have a passion for Java development using JBoss software. Basic scripting knowledge and the ability to compile Java projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus, but not required.<br />
<br />
Interested? Why wait, submit a Java package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join the package collection maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (Java, shell)<br />
<br />
''Skill level:'' Rudimentary<br />
<br />
''Contacts:'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf], [http://community.jboss.org/people/alrubinger Andrew Rubinger], [Max Andersen https://community.jboss.org/people/maxandersen]<br />
<br />
''Mentor(s):'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
==== Educational Application for Fedora Robotics Suite ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of Idea:'' Create an educational app introducing software from Fedora Robotics Suite<br />
<br />
The [[SIGs/Robotics|Fedora Robotics SIG]] is creating a [[Features/RoboticsSuite|Robotics Suite]] consisting of many packages useful in robotics. We want to develop a demonstration application introducing new users step by step to core packages like [http://www.fawkesrobotics.org Fawkes] and [http://playerstage.sourceforge.net Player/Stage]. It would feature multiple game-like levels with increasing complexity. The general task would be to instruct the robot to fulfill a specific task in a simulation environment.<br />
<br />
<br />
''Knowledge prerequisite:'' Developing this requires a strong background in C++, a background in robotics is preferred but not necessary. You should be able to familiarize yourself with new software quickly. User visible parts will require GUI programming using Gtkmm.<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' [[User:Timn|Tim Niemueller]]<br />
<br />
''Mentor(s):'' [[User:Timn|Tim Niemueller]]<br />
<br />
=== Applications for systems administrators ===<br />
<br />
==== RHQ-agent to interface with Matahari ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Write a RHQ-agent in Python and make it interface with Matahari to pick up metrics that are provided by Matahari from Fedora or RHEL systems. The agent would talk to the RHQ server via the REST api and push metrics to RHQ etc. This agent will not implement the full functionality of the RHQ java agent.<br />
<br />
While RHQ is written in Java, this project does not need any Java knowledge.<br />
<br />
''Knowledge prerequisite:'' Python, Linux system administration, qpid, principles of REST<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' Heiko Rupp <pilhuhn><br />
<br />
''Mentor(s):'' Heiko Rupp <pilhuhn><br />
<br />
''Notes:'' RHQ wiki is at http://rhq-project.org/<br />
<br />
<br />
[[Category:Summer coding 2012]]</div>Mojavelinuxhttps://fedoraproject.org/w/index.php?title=Summer_coding_ideas_for_2012&diff=276627Summer coding ideas for 20122012-03-09T23:27:34Z<p>Mojavelinux: add vit</p>
<hr />
<div>{{Admon/tip | Please feel free to add your idea here.}}<br />
<br />
{{Admon/tip |If you are a student and willing to suggest an idea please use the [[Summer_coding_ideas_for_2012/Students_Idea|Students Idea wiki page]]. Interested mentors can check the Students Idea page and undertake any interested idea those students are suggesting.}}<br />
<br />
Find an idea you like? Want to propose your own? See the Getting Started Guide with GSoC:<br />
<br />
https://fedoraproject.org/wiki/GSOC_2012<br />
<br />
You may be interested in ideas from [[Summer_coding_ideas_for_2011|2011]], [[Summer_coding_ideas_for_2010|2010]], [[Summer_coding_ideas_for_2009|2009]] and [[Summer_coding_ideas_for_2008|2008]].<br />
<br />
Further, last year accepted ideas from the Fedora Project can be found at [http://www.google-melange.com/gsoc/org/google/gsoc2011/fedora GSoC 2011 web site]<br />
<br />
== Students Welcome ==<br />
<br />
If you are a student looking forward to participate the GSoC 2012 with Fedora, please feel free to browse the idea list which is still growing. Do not hesitate to contact the mentors/ contributors as indicated in this page for any related clarification. If you are new to The Fedora project, following material would help you to get started. Further please sign-up with the [https://fedoraproject.org/wiki/FAS Fedora Account System(FAS)] if you are willing to continue with the Fedora project. <code>#fedora-devel</code>, IRC channel can be used to get instant support.<br />
<br />
# [https://fedoraproject.org/wiki/Foundation The Foundation]<br />
# [http://docs.fedoraproject.org/en-US/index.html Fedora Documentation (Users/ Contributors)]<br />
# [http://fedoraproject.org/wiki/Communicate/IRCHowTo How to work with IRC?]<br />
# [https://fedoraproject.org/wiki/FAS Fedora Account System] <br />
# [http://fedoraproject.org/wiki/Development Development]<br />
<br />
== Supporting Mentors ==<br />
<br />
Following contributors are also willing to support the GSoC 2012 program. (please feel free to add your self, attach the user page). Sometimes there should be some backing up mentors to mentor if the original mentor get busy with something for a short time period. In such case we need help.<br />
<br />
#[[User:Bckurera|Buddhike Kurera(Bckurera)]]<br />
#[[User:Quaid|Karsten Wade(Quaid)]]<br />
#[[User:Susmit|Susmit Shannigrahi(Susmit)]]<br />
# [[User:Duffy | Mo Duffy (Duffy)]]<br />
#[[User:Mmorsi | Mo Morsi]]<br />
<br />
==Draft of an idea==<br />
Please add your idea as follows.<br />
<br />
=== Project name ===<br />
<br />
''Status:'' <br />
<br />
''Summary of idea:''<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' <br />
<br />
''Mentor(s):''<br />
<br />
''Notes:''<br />
<br />
'''!!!The draft was changed slightly, please add required field as required!!!'''<br />
<br />
== Idea list for GSoC 2012==<br />
<br />
===Applications for desktop end users===<br />
These are coding projects that benefit end users of the Linux desktop.<br />
<br />
==== Integrate Proxy Settings and Network Connections(Locations) ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' The system should use an appropriate networking profile (e.g. Proxy settings) for each network connection.<br />
<br />
Gnome 2 had a concept of network locations in its Network Proxy configuration window. However, user should selected the appropriate location whenever he moves between networks. This idea is about providing an integration between NetworkManager and Desktop environments so that a user can create network profiles for each network location(connection) providing appropriate settings like proxy settings which is the main proposed setting here. NetworkManager can have a "Network Location" concept: for wireless networks, usually the name of the network (ESSID) is usually enough. For wired connections, DHCP servers can and usually do provide network's domain name, which can be used as the name of the location. It is nice if a user can associate each network location with a network settings profile which will be used whenever the user is connected to that network automatically. So, when you connect to a network, a corresponding network settings profile is activated automatically. <br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User:Hedayat|Hedayat Vatankhah]]<br />
<br />
''Mentor(s):''<br />
<br />
''Notes:'' There is an entry with some description in [http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/TODO NetworkManager TODO] which should be considered for the implementation<br />
<br />
==== Bringing the Fedora Desktop to the Cloud====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
[http://www.aeolusproject.org Aeolus] is an umbrella project that provides an open source API which to control any number of backend proprietary cloud providers. It allows us to write tooling that is able to deploy, monitor, and manager instances to any cloud provider such as EC2 or OpenStack in a Free and Open Manner. We need more tooling to interface with the various Aeolus components from the Fedora desktop (or any other) in novel ways such as command-line and gtk-based applications to deploy instances to the cheapest cloud provider or the one with the fastest response time, to monitor running instances using various visualizations, and more closely integrate local data and code w/ that on the cloud.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info about the Aeolus project. All the components which to build images for the cloud and control instances is in place and ready to go, just drop various bits (they are interoperable and interchangable) into an environment to be able to interact with the cloud, avoiding proprietary interfaces and vendor lockin.<br />
<br />
==== Web hosting control panel ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:''<br />
develop a free alternative of cpanel / plesk control panels, 100% compatible with fedora, and redhat enterprise Linux.<br />
written in python.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' itamarjp [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Ausil | Dennis Gilmore]] [[User: toshio | Toshio kuratomi]] <br />
<br />
''Notes:''<br />
<br />
==== Assemble a toolchain for recording screencasts easily ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Creating screencasts on Fedora and post-processing them for upload should be easy and fool proof.<br />
<br />
The [[Videos|Fedora Videos]] project has been launched to bring together a collection of screencasts that help people learn how to use Fedora. There's only one major hurdle, though. Capturing really good screencasts on Fedora, post-processing them to include an intro and outro and other effects, and finally exporting them to an open format is challenging. There are lots of different tools, but each one only gets you part of the way there and you have to be the glue to make it all work. And then there are the bugs.<br />
<br />
The goal of this project is to assemble a toolchain (a recommended collection of software available in the Fedora repositories) and write a comprehensive tutorial for how to create an professional-looking screencast. That may included chasing down & fixing bugs in the existing tools, discovering new tools and getting them packaged and learning about techniques in the environment around the computer, such as how to select & setup a microphone or how to draft a good speaking script. One possible task in the project is to add sound recording support to the Gnome 3 desktop recorder. Currently, the desktop recorder only grabs the video of the screen.<br />
<br />
The student will get support and advice from the Fedora Videos team since they are trying to learn how to create these screencasts.<br />
<br />
''Knowledge prerequisite:'' gstreamer, video and sound editing, blender<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[Videos|Fedora Videos Team]]<br />
<br />
''Mentor(s):'' ???<br />
<br />
''Notes:'' <br />
<br />
===Applications for programmers===<br />
<br />
==== Implement a Socket API for GlusterFS ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' In transporting data across networks, in the case of writing and reading replicated and distributed data on GlusterFS, programmers could use a better method to send large amounts of data with lower latency and less overhead in comparison to standard methods, such as HTTP. This project would implement a socket API for GlusterFS so that programmers, using any language, could create low-latency applications that utilize GlusterFS for distributed storage.<br />
<br />
''Knowledge prerequisite:'' C, GlusterFS internals<br />
<br />
''Skill level:'' High<br />
<br />
''Contacts:'' johnmark [AT]redhat [DOT] com , abperiasamy [AT] gmail [DOT] com<br />
<br />
''Mentor(s):'' Anand Avati - Mentor, AB Periasamy - Co-mentor, [[User:johnmark|John Mark Walker]] - Co-mentor<br />
<br />
===Infrastructure for Fedora contributors and users===<br />
==== Implement a survey infrastructure for the Fedora Project====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Surveys are important to increase the quality of a service, and it is true for the Fedora project as well.(discussions [http://meetbot.fedoraproject.org/fedora-meeting/2011-12-24/apac.2011-12-24-04.00.log.html#l-310]) In this project it is supposed to implement a survey infrastructure facility so that the contributors can use for various activities as per the need.<br />
<br />
The concern is to develop a simple web base survey system OR implement a existing survey project and customized as required, so that contributors can easily create surveys and dig for results as well. Linking with the [FAS|FAS] is required. Further it should be compatible with anonymous and open ID so that if the creator set for those authentication the survey should allow those authentications. Statistics and other required reports can be obtained. So that it is easy to analyse.<br />
<br />
''Knowledge prerequisite:'' PHP, Python, Ruby are preferred, MySQL (database handling), experience with Lime Survey would be an advantage <br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' kevin [AT]scrye [DOT] com , bckurera [AT] fedoraproject [DOT] org<br />
<br />
''Mentor(s):'' [[User:Kevin|Kevin Fenzi]] - Mentor, [[User:Bckurera|Buddhike Kurera]] Co-mentor.<br />
<br />
''Notes:'' This idea is improving, please contact for upto-date details.<br />
<br />
==== Design Hub: FLOSS Collaboration for FLOSS Designers ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Free software designers don't have a great set of tools to work with to collaborate with each other and with the community on their design work. With this project, we'd like to make progress towards fixing that. We have some disparate ideas / tools that we'd like to be integrated:<br />
<br />
* [http://sparkleshare.org Sparkleshare] - a git-backed, Dropbox like system that will automatically check in and push files in project directly to a shared git repo<br />
* [https://github.com/garrett/magicmockup Magic Mockup] - a coffeescript/javascript you can insert into an SVG of mockups to enable interactive, click-through mockups ([http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/ see a demo here]<br />
* [http://blog.linuxgrrl.com/category/design-hub/ Design Hub] - an idea and a ruby on rails prototype of a web front end that could potentially serve as a front end to git repos with design assets *and* serve as well as a front end to magic mockup mockups in said repos<br />
* [http://inkscape.org Inkscape] is our preferred design tool of choice; it would be great if it had some GUI integration with Magic Mockup, Sparkleshare, and Design Hub<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' duffy at fedoraproject [dot] org<br />
<br />
''Mentor(s):'' [[User:Duffy | Mo Duffy]], [[User:Emichan | Emily Dirsh]]<br />
<br />
''Notes:'' We can provide a development platform for the web UI at openshift.redhat.com. Also, note this project doesn't just benefit Fedora designers, but it benefits all FLOSS designers.<br />
<br />
==== Implement a unit test framework for fedpkg and rpkg ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' Unit tests are good. Testing is good. fedpkg and it's backend rpkg is a growing code base, gaining more and more contributors. It lacks a unit test framework which would be very beneficial to the code base for making sure contributions don't break the code in subtle ways.<br />
<br />
''Knowledge prerequisite:''<br />
<br />
''Skill level:''<br />
<br />
''Contacts:'' jkeating [AT]redhat [DOT] com<br />
<br />
''Mentor(s):'' [[User:jkeating]] - Mentor<br />
<br />
''Notes:'' This project is in python.<br />
<br />
==== Insight use cases for calendar ====<br />
<br />
Status: Proposed - Draft<br />
<br />
Insight project requirement to be implemented. More details can be found at the wiki, [[Insight_use_cases_for_calendar]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on PHP and Drupal would be essential <br />
<br />
''Skill level:'' Medium<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]], [[User:Herlo|Clint Savage]] & [[Insight|Insight Team]]<br />
<br />
Mentor(s): [[User:Tatica|María "tatica"]], [[User:Asrob|Peter Tibor Borsa]] and [[User:Bckurera|Buddhika Kurera]] <br />
<br />
Notes: -<br />
<br />
==== Insight use cases for status and microblogging ====<br />
<br />
Status: Proposed - Draft<br />
<br />
These are use cases for status and microblogging services that we might want to provide through Insight. More details can be found at the wiki, [[Insight_use_cases_for_status_and_microblogging]]<br />
<br />
''Knowledge prerequisite:'' Knowledge on Drupal would be essential.<br />
<br />
''Skill level:'' High<br />
<br />
Contacts: [[User:Pfrields|Paul W. Frields]]<br />
<br />
Mentor(s): -<br />
<br />
Notes: Students who are interested on this topic is highly requested to contact the mentors as the first step. Knowledge on Drupal would be essential.<br />
<br />
====isitfedoraruby.com====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:''<br />
Right now most Ruby programmers make use of the [http://rubygems.org/ gem] package management system to install Ruby libraries on their system. The [http://fedoraproject.org/wiki/Ruby_SIG Fedora/Ruby] community works hard to convert these gems into rpms for inclusion in the Fedora stack, making use of various tooling such as [https://github.com/lutter/gem2rpm gem2rpm]. We are looking for more tools and capabilities around Ruby / Fedora integration, namely to reduce the overhead in supporting Ruby on Fedora and to promote Fedora as the de-facto platform for Ruby development.<br />
<br />
As part of this, we would like to develop a isitfedoraruby.com website (similar to [http://isitruby19.com/ isitruby19] and other sites like it) to promote the ruby stack on Fedora and the Fedora/Ruby development effort, highlighting success stories, use cases, ways contributors can help, etc<br />
<br />
''Knowledge prerequisite:'' <br />
<br />
''Skill level:'' <br />
<br />
''Contacts:'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Mentor(s):'' [[User: Mmorsi|Mo Morsi]]<br />
<br />
''Notes:'' Ping me (mmorsi on freenode) for more info. This project should be written in Ruby<br />
<br />
==== Setup Gitlab as a front end for Fedora Hosted git repositories ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' To setup [http://gitlabhq.com/ Gitlab] as a front end for git repositories at [fedorahosted.org].<br />
<br />
Git has fundamentally improved the way that developers share code. The barrier to sharing code has virtually been eliminated. We are also seeing the emergence of a new dynamic called "Social Coding". There's no better example of this than Github.<br />
<br />
Creating an environment to foster social coding, and a low barrier to sharing code, requires more than just git, though. A lot of what makes Github successful with git is the web-based front end. That explains why there is such a dramatic difference between Github and fedorahosted.org, and why many projects are moving to Github instead.<br />
<br />
Fortunately, there is an open source application named Gitlab that provides much of the interactive functionality and usability that is found at Github. The goal of this project is to bring that experience to fedorahosted.org by setting up Gitlab.<br />
<br />
This project will require working with the infrastructure team to get the necessary prerequisites installed, find a server to host the application and configure the existing projects to be wired to this interface.<br />
<br />
''Knowledge prerequisite:'' Ruby, git, Linux system administration (web servers, authentication)<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [[User:mojavelinux|Dan Allen]] (general), [[User:Vondruch|Vít Ondruch]] (packaging)<br />
<br />
''Mentor(s):'' None yet.<br />
<br />
''Notes:'' This idea is something we need, but we don't yet have a driver for it. A demo of Gitlab can be found here: http://gitlabhq.com/demo.html<br />
<br />
===Linux system services===<br />
===Improving Fedora packaging===<br />
<br />
==== Java API/ABI changes checker ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Libraries written in Java add, remove and modify their public interfaces from time to time. This is normal, but currently it is very hard to guess effect an update of library to new version will have on rest of the system. What is needed is a tool that would be able to tell us that "With update of package java-library to version 2.0, function X(b) has been removed. This function is used in package java-app". There are already a few open-source projects that can do some of the analysis needed. This would be of interest to whole Java world I believe and would enable safer and easier updates. To get an idea of similar projects see [http://linuxtesting.org/upstream-tracker/java/ Java API compliance checker] and [https://sites.google.com/site/obriencj/projects/java-classfile-python-module Python Javaclass project]<br />
<br />
''Knowledge prerequisite:'' Knowledge of Java (inheritance rules, generics, etc.) and probably some scripting language(s)<br />
<br />
''Skill level:'' Fairly high<br />
<br />
''Contacts:'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Mentor(s):'' [[User:Sochotni|Stanislav Ochotnický]]<br />
<br />
''Notes:'' Don't hesitate to get in touch via IRC (sochotni@FreeNode) or email (contact on my user page).<br />
<br />
==== Maven FOSS Repository Extension ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' With the inception of Maven we have a means to standardize the building of Java projects. However it has also resulted in the usage of a very wide dependency set by these Java projects. This makes it very hard to integrate those projects on a single platform (be it Fedora or JBoss Application Server (or the combination)). In essence during packaging all these dependencies must be lined up to form a single consistent component set. Thus each project will only have those components available which are actually available on the target platform. This is very hard to enforce using standard Maven setup.<br />
For Fedora I'm envisioning a Maven extension that makes sure only sanctioned components are used during the build (without putting a burden on the packager). This will allow developers who are not on Fedora to also build with this extension and thus verify (and fix) issues which are the result of "Fedora packaging".<br />
A prototype can be viewed at [https://github.com/wolfc/fedora-maven Fedora Maven Extension].<br />
<br />
''Knowledge prerequisite:'' Knowledge of Maven<br />
<br />
''Skill level:'' Medium<br />
<br />
''Contacts:'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Mentor(s):'' [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
''Notes:'' You can find me at irc.freenode.net #fedora-java wolfc<br />
<br />
===Fedora Spins and remixes===<br />
<br />
==== Fedora Audio Creation Spin ====<br />
<br />
''Status:'' Proposed - Draft<br />
<br />
''Summary of idea:'' To create a Fedora Audio spin showcasing the rich and diverse landscape of Linux Audio production.<br />
<br />
The [https://fedoraproject.org/wiki/Audio_Creation Fedora Audio Creation SIG] is a collection of enthusiastic Fedora users driven by the common desire to make the best Linux distribution also the best for Music creation and Audio Production. <br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source audio projects and integrating many of the packages from the PlanetCCRMA repository into Fedora. Other tasks may include the testing of kickstart files and developing small applications to better integrate with the Fedora Desktop. <br />
<br />
Ideally, interested candidates will have a passion for Music/Audio Production. Basic scripting knowledge and the ability to compile projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus. <br />
<br />
Interested? Why wait, submit an audio package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join_the_package_collection_maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (bash/python)<br />
<br />
''Skill level:'' Rudimentry<br />
<br />
''Contacts:'' [[User:bsjones|Brendan Jones]]<br />
<br />
''Mentor(s):'' [[User:bsjones|Brendan Jones]]<br />
<br />
==== Fedora JBoss Spin ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' To create a Fedora JBoss spin that helps Java developers get started quickly using JBoss software.<br />
<br />
The [https://fedoraproject.org/wiki/SIGs/Java Java SIG] and the [https://fedoraproject.org/wiki/JBossAS7 JBoss AS 7 on Fedora Initiative] is a cross-section of enthusiastic Fedora users driven by the common desire to make the Fedora the best OS for developing with JBoss software.<br />
<br />
We are looking for one or two candidates to assist us in the complete development cycle of this project. The bulk of the effort lies in packaging open source Java and JBoss projects and integrating many of the packages from the JBoss Community into Fedora. Packages in particular include JBoss AS 7, JBoss Tools and JBoss Forge. Other tasks may include the testing of kickstart files and developing configurations to better integrate with the Fedora Desktop. <br />
<br />
There could be two variants of this spin (feel free to choose). One is on the developer needing a good desktop to create JBoss-based applications (things like Eclipse + JBoss Tools, AS 7, Forge, a database, and so on). The other focus is on getting a server setup so that it can run the application. That would also be where the upcoming OpenShift toolset will come into play.<br />
<br />
Ideally, interested candidates will have a passion for Java development using JBoss software. Basic scripting knowledge and the ability to compile Java projects from source is a must. Sponsored packagers / knowledge of the Fedora Packaging Guidelines and/or the desire to continuing maintaining the packaged software post-project considered a plus, but not required.<br />
<br />
Interested? Why wait, submit a Java package for review and get sponsored ([https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Join the package collection maintainers]).<br />
<br />
''Knowledge prerequisite:'' Scripting/programming (Java, shell)<br />
<br />
''Skill level:'' Rudimentary<br />
<br />
''Contacts:'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf], [http://community.jboss.org/people/alrubinger Andrew Rubinger], [Max Andersen https://community.jboss.org/people/maxandersen]<br />
<br />
''Mentor(s):'' [[User:Goldmann|Marek Goldmann]], [http://community.jboss.org/people/wolfc Carlo de Wolf]<br />
<br />
==== Educational Application for Fedora Robotics Suite ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of Idea:'' Create an educational app introducing software from Fedora Robotics Suite<br />
<br />
The [[SIGs/Robotics|Fedora Robotics SIG]] is creating a [[Features/RoboticsSuite|Robotics Suite]] consisting of many packages useful in robotics. We want to develop a demonstration application introducing new users step by step to core packages like [http://www.fawkesrobotics.org Fawkes] and [http://playerstage.sourceforge.net Player/Stage]. It would feature multiple game-like levels with increasing complexity. The general task would be to instruct the robot to fulfill a specific task in a simulation environment.<br />
<br />
<br />
''Knowledge prerequisite:'' Developing this requires a strong background in C++, a background in robotics is preferred but not necessary. You should be able to familiarize yourself with new software quickly. User visible parts will require GUI programming using Gtkmm.<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' [[User:Timn|Tim Niemueller]]<br />
<br />
''Mentor(s):'' [[User:Timn|Tim Niemueller]]<br />
<br />
=== Applications for systems administrators ===<br />
<br />
==== RHQ-agent to interface with Matahari ====<br />
<br />
''Status:'' Proposed<br />
<br />
''Summary of idea:'' Write a RHQ-agent in Python and make it interface with Matahari to pick up metrics that are provided by Matahari from Fedora or RHEL systems. The agent would talk to the RHQ server via the REST api and push metrics to RHQ etc. This agent will not implement the full functionality of the RHQ java agent.<br />
<br />
While RHQ is written in Java, this project does not need any Java knowledge.<br />
<br />
''Knowledge prerequisite:'' Python, Linux system administration, qpid, principles of REST<br />
<br />
''Skill level:'' Medium to High<br />
<br />
''Contacts:'' Heiko Rupp <pilhuhn><br />
<br />
''Mentor(s):'' Heiko Rupp <pilhuhn><br />
<br />
''Notes:'' RHQ wiki is at http://rhq-project.org/<br />
<br />
<br />
[[Category:Summer coding 2012]]</div>Mojavelinux