• Cygwin
•    Install Cygwin
•    Update Cygwin
•    Search Packages
•    Licensing Terms

• Cygwin/X

• Community
•    Reporting Problems
•    Mailing Lists
•    Newsgroups
•    Gold Stars
•    Mirror Sites
•    Donations

• Documentation
•    FAQ
•    User's Guide
•    API Reference
•    Acronyms

• Contributing
•    Snapshots
•    Source in CVS
•    Cygwin Packages

• Related Sites
• Red Hat Cygwin Product

Who are we?*

• Christopher Faylor (cgf) is one of the project leads. Chris works for Netapp but all of his Cygwin activities occur on his own time. He is most notably responsible for the support of signal handling and fork/exec in Cygwin. He also administer's the site which hosts the cygwin web site and release.
  
  
• Corinna Vinschen (corinna) is the other project lead. Corinna is a senior Red Hat engineer. Corinna is responsible for such important subsystems as security and networking and has recently added support to Cygwin for wide characters and increased path length.
  
  
• Yaakov Selkowitz is the Cygwin/X coordinator. Jon Turney serves on the Cygwin/X team as a developer.
  
  
• The Cygwin setup project is currently maintained by the project leads and Dave Korn. Dave also provides support for GCC.
  
  
• Eric Blake (eblake) maintains bash, coreutils, and several other vitally important packags.
  
  
• Cygwin was initially developed by Cygnus Solutions (Now Red Hat, Inc.) but the majority of package maintainership and a significant percentage of Cygwin development is handled by non-Red Hat volunteers.
  
  
• Like many free software projects on sourceware.org, contributions from net people are especially important. Cygwin benefits from thousands of testers and dozens of contributors, including some incredible people like Sergey Okhapkin, Egor Duda, Chuck Wilson, David Starks-Browning, Kazuhiro Fujieda, Jason Tishler, Robert Collins, David Billinghurst, Joshua Daniel Franklin, Chris January, Conrad Scott, Pavel Tsekov, Pierre Humblet, Igor Peshansky, Brian Dessent, Brian Ford, and Jari Aalto.

* Please note that all of the people above prefer that project related communications go to the proper mailing list rather than private email.