You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

The Fedora Repository software is open source and released under an Apache License, Version 2.0. The software and associated documentation is developed collectively by a community of contributors and committers. All interested community members are encouraged to contribute to the project. Contributors who demonstrate sustained engagement with the project through quality participation in meetings, mailing lists, documentation and code updates can be nominated by existing committers to also become a committer. It should be emphasized that committers need not be limited to software developers. Community members with skills in documentation and testing, for example, can also be committers.

Rights

Committers share the following rights:

  • Write access to the codebase
  • Nomination privileges of new committers
  • Release management privileges
  • Binding votes on procedural, code modification, and release issues
  • Access to the private committers mailing list

Responsibilities

Committers share the following responsibilities:

  • Monitor and respond to project mailing lists
  • Attend project and technical meetings
  • Monitor and vet bug-tracker issues
  • Review and commit code contributions
  • Ensure code contributions are properly licensed
  • Guide and mentor new committers

Committers

The following is an alphabetized list of the current Fedora committers:

NameOrganizationEmailCode Signing Key
Ben ArmintorColumbia Universityarmintor at gmail dot com4951BD3E94F5F3EC2DA647B5DD0CF2D2FB219210
Chris BeerStanford Universitychris at cbeer dot info

B321153C2C20F1BF5E13DB0326440AE534DACA3F

Danny BernsteinDuraSpacedbernstein at duraspace dot orgDF1FCB1A586479808E855ACBD09B04567812610C
Aaron BirklandJohns Hopkins Universitybirkie at gmail dot com 
Esmé CowlesPrinceton Universityescowles at ticklefish dot org

DD5588E1ABE14EF2B4A3C67A2CB86AF398E1197E

Osman DinYale Universityosman.din at yale dot edu97329A853F2CF54134C1669D4FB9CB3EBABCE493
Mike DurbinUniversity of Virginiamd5wz at virginia dot eduEB1B407BD3985F4F4F00 E81E51AA1F4B834A6FD1
Nick RuestYork Universityruestn at yorku dot ca159493E15691C84D615B7D1B417FAF1A0E1080CD
Bethany SeegerAmherst Collegebseeger at amherst dot edu

652BC854772853D5FF89325A757863CC3D998C48

Jared WhikloUniversity of Manitobajwhiklo at gmail dot com

9F45FC2BE09F4D70DA0C7A5CA51C36E8D4F78790

Andrew WoodsDuraspaceawoods at duraspace dot org7BCE77FB75D06477C7A1D6EF04BE1CAB70B358DF

Contributor Profiles

The Fedora project depends on the engagement and contributions of community stakeholders. As noted above, contributions can take the form of:

  • Documentation review and curation
  • Application testing
  • Software development

Documentor

Documentors contribute by reviewing, correcting, updating, and enhancing the project documentation found on this wiki targeting users and administrators of Fedora.

Skills

  • Interest in technical writing

Tester

Testers contribute by performing and reporting on the outcomes of a wide range of tests, including performance, security, stress, regression, etc. on an on-going as well as release-time basis.

Skills

  • Ability to deploy and configure Fedora
  • Ability to document and communicate results
  • Bonus: Familiarity with testing frameworks, such as Grinder, JMeter, etc

Developer

Developers contribute by writing functional and test code that fixes, hardens, and extends the Fedora codebase.

Skills

  • Experience with software development practices (the codebase is primarily Java, but many of the project's contributors do not come with a Java background)
  • Experience reading and tracing multi-module codebases
  • Experience debugging issues
  • Interest in reading community standards and forming implementations around them

Contributors

This is a list of all known general contributors to post-Fedora 3 software. These people have contributed to at least one version of Fedora (as of Fedora 4.7.1)

NameOrganization
University of Michigan
University of Houston
University of Oxford
Brown University
University of North Carolina at Chapel Hill
DuraSpace
Indiana University
 
The Ohio State University
DuraSpace
Islandora Foundation
Duke University
DuraSpace
Metro New York Library Council
National Library of Medicine
 
Johns Hopkins University
Yale University
 
 
University of California, Berkeley
University of Maryland
University of Michigan
Brown University
University of Minho
Lafayette College
University of Oklahoma
Duke University
LYRASIS
University of Manitoba
University of Maryland
Stanford University
 
Carleton University
Art Institute of Chicago
 
University of California, Los Angeles
University of California, San Diego
 
Stanford University
University of North Carolina at Chapel Hill
 
University of Maryland
Princeton University
Indiana University
 
Art Institute of Chicago
University of Prince Edward Island
California Digital Library
University of Maryland
SLUB Dresden
University of Edinburgh
J. Paul Getty Trust
University of Wisconsin-Madison

Sébastien Leroux

 
Art Institute of Chicago
Northwestern University
Boston Public Library
University of North Florida
Princeton University
Centers for Disease Control
Max Planck Digital Library
Virginia Tech
discoverygarden inc.

  • No labels