From Fedora Project Wiki

(Add link to new job)
(Greg's POSSE update)
Line 43: Line 43:
 
* Be an effective bridge between the external volunteer contributor base and the contributor community inside Red Hat, such as RHEL engineers.
 
* Be an effective bridge between the external volunteer contributor base and the contributor community inside Red Hat, such as RHEL engineers.
 
* Lower contributor barriers to the absolute minimum, and encourage others to get involved in FOSS through Fedora.
 
* Lower contributor barriers to the absolute minimum, and encourage others to get involved in FOSS through Fedora.
 +
 +
== Education Background ==
 +
 +
Jared graduated in 2001 from Utah State University with a degree in Computer Engineering.
 +
 +
His fondest memory of his USU education involves a course taught by [http://digital.cs.usu.edu/~allan/ Professor Stephen J. Allan]:
 +
 +
"The class was something like "Unix Basics" or something boring like that, but the teacher made the assignments interesting, by forcing you to work with others in the class to solve a problem. A typical assignment might go something like this: 'Joe, you write an awk script to take this file I give you and transform it to look like this -- Susie, you take that, and use grep and sed to do this to it, Jared -- you take that and write a Perl script to do this...' and so on. So not only did we learn the tools, we had to communicate our expectations and assumptions with the other members of our team."

Revision as of 15:56, 23 July 2011

Jared Smith
Jared Smith
Fedora Information
FAS name: jsmith
Fedora email: jsmith@fedoraproject.org
IRC nick: jsmith
IRC channels: #fedora-docs, #asterisk-doc, #asterisk-dev, #asterisk-bugs (and others)
Fedorapeople page: https://jsmith.fedorapeople.org
Badges (162)
F32 i18n Test Day Participant I Voted: Fedora 32 Speak Up! Junior Editor Flock 2013 Attendee Involvement Tanked! Crypto Panda You can call me "Patches" (SCM I) If you build it... (Koji Success I) Bona Fide You can call me "Patches" (SCM II) If you build it... (Koji Success II) Junior Badger (Badger I) Mugshot Ambassador Flock 2013 Speaker Like a Rock (Updates-Stable I) Like a Rock (Updates-Stable II) In Search of the Bull (Tester I) FUDCon Cusco Nuancier Is this thing on? (Updates-Testing II) Is this thing on? (Updates-Testing I) Embryo Bloggin' it! (Planet III) Bloggin' it! (Planet I) Bloggin' it! (Planet II) Baby Badger Tagger (Tagger II) Senior Tagger (Tagger III) Junior Tagger (Tagger I) Egg Tadpole Secretary General Apex Take this and call me in the morning Tadpole with Legs White Hat Vacation Novice (Wordsmith I) White Rabbit Discovery of the Footprints (Tester II) No Longer a Ronin Associate Editor Sensei Let Me Introduce Myself Proven Packager Froglet Flock 2014 Speaker The Blessing of the FPL Keepin Fedora Beautiful (F21) If you build it... (Koji Success III) Flock 2014 Attendee What goes around comes around (Karma I) Senior Badger (Badger II) Helping Hand Party Pirate Dancing with Toshio Science (Kernel Tester I) Def Keepin Fedora Beautiful (F21) Flock Paparazzi Nuancier 21 What goes around comes around (Karma II) Fedora Docs FAD 2014 Corporate Drone What goes up... (Koji Failure I) Readiness Shellshocked Perceiving the Bull (Tester III) What goes up... (Koji Failure II) Package Tagger (Package Tagger II) Flock 2015 Attendee FUDCon Pune 2015 Speaker Senior Package Tagger (Package Tagger III) You can call me "Patches" (SCM III) FUDCon Managua The Panda Is In FUDCon Pune 2015 Attendee Junior Package Tagger (Package Tagger I) Associate Badger (Badger 1.5) Macaron (Cookie I) OSCON 2015 Attendee DevConf 2015 Attendee Science (Kernel Tester II) Origin Nuancier (F22) Telegraphist (Upstream Release Monitoring I) Delivery Flock 2015 Speaker Nuancier F23 Is this thing on? (Updates-Testing III) FUDCon Cordoba 2015 Speaker Chocolate Chip (Cookie II) Nom Nom Nom Keepin Fedora Beautiful (F23) If you build it... (Koji Success IV) You can call me "Patches" (SCM IV) FUDCon Cordoba 2015 Attendee Master Badger (Badger III) Def Keepin Fedora Beautiful (F23) Building the Outer Ring (Copr Build I) Building the Outer Ring (Copr Build II) Corporate Shill Partners in Crime Building the Outer Ring (Copr Build III) Building the Outer Ring (Copr Build IV) Building the Outer Ring (Copr Build V) What goes up... (Koji Failure IV) Building the Outer Ring (Copr Build VI) Like a Rock (Updates-Stable III) Black and White (Cookie III) What goes up... (Koji Failure III) Building the Outer Ring (Copr Build VII) Senior Editor Master Editor Top 25 The Last Argument of Kings Badge Muse (Badge Ideas I) Top 100 Top 500 Nuancier F25 Patches (SCM V) Fedora 24 Change Accepted Nuancier F24 The cat came back... Community Messenger I Flock 2016 Attendee Krakow Brews! All your $arch are belong to us (Koji Success V) Security Team Adult Frog Nuancier F26 Hindenburg (Koji Failure V) Chief Editor Steampunk Arcade Binary Star Pizzelle (Cookie IV) Flock 2017 Attendee F28 i18n Test Day Participant Fedora Mindshare FAD 2018 Catching the Bull (Tester IV) Fedora Docs FAD 2018 Flock 2018 Attendee It's a Cake Thing Meeting of the Minds Fedora Podcast Interviewee Rollercoaster Restaurant I Voted: Fedora 29 Long Life to Pagure (Pagure I) Long Life to Pagure (Pagure II) Parselmouth I You’re on a boat! Badge Junkie (Badger IV) Long Life to Pagure (Pagure III) Flock 2019 Attendee Fedora Advocate I Voted: Fedora 30 I Voted: Fedora 31 Long Life to Pagure (Pagure IV) Long Life to Pagure (Pagure VI) Long Life to Pagure (Pagure V)
 

My name is Jared Smith. I'm a big Linux geek. I enjoy systems administration, relational databases, web programming, and VoIP. I eat too many donuts, and don't blog as regularly as I should. I've managed small systems and large-scale networks (over 6500 servers and 800 network devices). As a college freshman, I once stuffed 26 jumbo marshmallows in my mouth to win a contest. Oh, and I wrote a book for O'Reilly on Asterisk and the future of telephony. For all the nitty gritty details, see http://www.jaredsmith.net/about/.

Contact

Activities within Fedora

  • I work for Red Hat as the Fedora Project Leader.
  • I help out with the Fedora Docs project, and generally make a nuisance of myself. I have a lot of experiece with DocBook publication toolchains, such as Publican.
  • I've also helped out on the Fedora Infrastructure team, mostly around the Fedora Talk server. (I have *lots and lots* of experience with Asterisk and voice over IP.)
  • I do my best to report bugs when I find them, and work with those responsible to ensure the problems get solved.

Goals as the Fedora Project Leader

  • Oversee the entire Fedora Project -- if it's in Fedora, ultimately I'm accountable for it.
  • Act as a catalyst within the community to improve communications and encourage excellent behavior
  • Work with the Fedora Program Manager John Poelstra, Fedora Engineering Manager Tom "Spot" Callaway, and the Community Architecture team to make sure that Fedora is making constant, substantial progress in its mission to advance free and open source software.
  • Chair the Fedora Project Board, and ensure that the Board is effectively advising and guiding the Fedora Project where needed.
  • Be an effective bridge between the external volunteer contributor base and the contributor community inside Red Hat, such as RHEL engineers.
  • Lower contributor barriers to the absolute minimum, and encourage others to get involved in FOSS through Fedora.

Education Background

Jared graduated in 2001 from Utah State University with a degree in Computer Engineering.

His fondest memory of his USU education involves a course taught by Professor Stephen J. Allan:

"The class was something like "Unix Basics" or something boring like that, but the teacher made the assignments interesting, by forcing you to work with others in the class to solve a problem. A typical assignment might go something like this: 'Joe, you write an awk script to take this file I give you and transform it to look like this -- Susie, you take that, and use grep and sed to do this to it, Jared -- you take that and write a Perl script to do this...' and so on. So not only did we learn the tools, we had to communicate our expectations and assumptions with the other members of our team."