Notice: MediaWiki has been updated. Report any rough edges to marcan@marcan.st

Difference between revisions of "People"

From OpenKinect
Jump to: navigation, search
(csharp)
(Updated page instructions)
Line 1: Line 1:
 
This page documents the major efforts within the OpenKinect project and who the coordinator is for each effort. The purpose of this is to coordinate people with similar interests and reduce or eliminate redundant efforts. If you are interested in the status of an effort or contributing of an effort, contact the designated coordinator.
 
This page documents the major efforts within the OpenKinect project and who the coordinator is for each effort. The purpose of this is to coordinate people with similar interests and reduce or eliminate redundant efforts. If you are interested in the status of an effort or contributing of an effort, contact the designated coordinator.
 +
 +
= Coordinators and participants =
 +
 +
You can add your name as a participant in an effort if you are actively working on code or have previously contributed to the effort. If you are no longer active but still wish to be listed, your name may be moved to a "Past participants" list within the effort. The coordinator is assumed to be an active participant and does not need to be listed twice.
 +
 +
The coordinator is often, but not always, the person with the most technical experience or the person who contributes the most to an effort. More important than those factors are that the coordinator is reliable, keeps up-to-date with what is going, and responds to communication (mailing list, IRC, direct email, or other chat program). New contributors check this page and contact the coordinator for the effort he or she is interested in. Coordinators need to help new contributors get up to speed on where they can help.
 +
 +
If there is not already a coordinator listed for something you're interested in, please ask around on IRC and the mailing list to see if anyone else is working on the same thing. The people working on an effort should agree upon a single coordinator and then update this page. If no agreement can be made, contact Josh Blake and he'll work something out.
  
 
=== Page conventions ===
 
=== Page conventions ===
Names should be real name with pseudonym in parenthesis. Contact information and links for a name should be placed in a linked user page. For example, JoshB's info is located at http://openkinect.org/wiki/User:JoshB. You can add your name as a participant in an effort if you are actively working on code for the effort.
+
Names should be real name with pseudonym in parenthesis. Contact information and links for a name should be placed in a linked user page. For example, JoshB's info is located at http://openkinect.org/wiki/User:JoshB and the link would look like
 +
<nowiki>[[User:JoshB|JoshB]]</nowiki>
  
 
= Project lead =
 
= Project lead =
  
Joshua Blake (JoshB) is the OpenKinect community founder and project lead. The project lead will designate a coordinator for each effort area in the project. If you would like to coordinate a new effort not listed here, please contact Josh to discuss.
+
Joshua Blake ([[User:JoshB|JoshB]]) is the OpenKinect community founder and project lead. As such, he is the coordinator of coordinators.  
  
 
= Efforts =
 
= Efforts =
Line 14: Line 23:
  
 
Coordinator:
 
Coordinator:
* Joshua Blake (JoshB)
+
* Joshua Blake ([[User:JoshB|JoshB]])
  
Participants:
+
Active participants:
 
* Seth Sandler (cerupcat), assists with Google Group mailing list apps
 
* Seth Sandler (cerupcat), assists with Google Group mailing list apps
 
* Nink, primarily runs @openkinect on twitter
 
* Nink, primarily runs @openkinect on twitter
Line 26: Line 35:
 
* Kyle Machulis (qDot)
 
* Kyle Machulis (qDot)
  
Participants:
+
Active participants:
 
* Hector Martin (marcan)
 
* Hector Martin (marcan)
* Josh Blake (JoshB)
+
* Joshua Blake ([[User:JoshB|JoshB]])
  
 
== libfreenect ==
 
== libfreenect ==
  
libfreenect is the driver and API project that includes all code that communicates directly with the hardware. The repository is located at https://github.com/OpenKinect/libfreenect/.
+
libfreenect is the driver and API project that includes all code that communicates directly with the hardware for Windows, Linux, and OS X. The repository is located at https://github.com/OpenKinect/libfreenect/.
  
 
Coordinator:
 
Coordinator:
 
* Hector Martin (marcan)
 
* Hector Martin (marcan)
  
Participants:
+
Active participants:
 
* Arne Bernin - debian/ubuntu packaging
 
* Arne Bernin - debian/ubuntu packaging
* ofTheo - Theo Watson
+
* Theo Watson (ofTheo)
 
* stephanemagnenat - Working on ROS node which uses libfreenect, would like to push changes upstream. Our lab could help with calibration.
 
* stephanemagnenat - Working on ROS node which uses libfreenect, would like to push changes upstream. Our lab could help with calibration.
 
* zarvox - Working on camera protocol reverse engineering & documentation
 
* zarvox - Working on camera protocol reverse engineering & documentation
Line 51: Line 60:
  
 
Coordinator:
 
Coordinator:
* Joshua Blake (JoshB)
+
* Joshua Blake ([[User:JoshB|JoshB]])
  
Participants:
+
Active participants:
 
* Kyle Machulis (qDot)
 
* Kyle Machulis (qDot)
  
Line 60: Line 69:
  
 
Coordinator:
 
Coordinator:
* Joshua Blake (JoshB)
+
* Joshua Blake ([[User:JoshB|JoshB]])
  
Participants:
+
Active participants:
* AdityaGaddam (LostInCake) - Help with C# wrapper if and when Josh needs it. Or just testing if not.
+
* Aditya Gaddam (LostInCake) - Help with C# wrapper if and when Josh needs it. Or just testing if not.
  
 
=== java ===
 
=== java ===
Line 71: Line 80:
 
* Scott Byrns (scottb)
 
* Scott Byrns (scottb)
  
Participants:
+
Active participants:
  
 
=== python ===
 
=== python ===
Line 81: Line 90:
 
* ?
 
* ?
  
Participants:
+
Active participants:

Revision as of 01:25, 21 November 2010

This page documents the major efforts within the OpenKinect project and who the coordinator is for each effort. The purpose of this is to coordinate people with similar interests and reduce or eliminate redundant efforts. If you are interested in the status of an effort or contributing of an effort, contact the designated coordinator.

Coordinators and participants

You can add your name as a participant in an effort if you are actively working on code or have previously contributed to the effort. If you are no longer active but still wish to be listed, your name may be moved to a "Past participants" list within the effort. The coordinator is assumed to be an active participant and does not need to be listed twice.

The coordinator is often, but not always, the person with the most technical experience or the person who contributes the most to an effort. More important than those factors are that the coordinator is reliable, keeps up-to-date with what is going, and responds to communication (mailing list, IRC, direct email, or other chat program). New contributors check this page and contact the coordinator for the effort he or she is interested in. Coordinators need to help new contributors get up to speed on where they can help.

If there is not already a coordinator listed for something you're interested in, please ask around on IRC and the mailing list to see if anyone else is working on the same thing. The people working on an effort should agree upon a single coordinator and then update this page. If no agreement can be made, contact Josh Blake and he'll work something out.

Page conventions

Names should be real name with pseudonym in parenthesis. Contact information and links for a name should be placed in a linked user page. For example, JoshB's info is located at http://openkinect.org/wiki/User:JoshB and the link would look like [[User:JoshB|JoshB]]

Project lead

Joshua Blake (JoshB) is the OpenKinect community founder and project lead. As such, he is the coordinator of coordinators.

Efforts

Administration

This includes mailing list and PR efforts such as twitter and blogs.

Coordinator:

Active participants:

  • Seth Sandler (cerupcat), assists with Google Group mailing list apps
  • Nink, primarily runs @openkinect on twitter

Maintainers

Maintainers have commit access to the official repositories and integrate pull requests and patches. This access is only used for integration and maintainers still follow the standard fork/pull request model for bug fixes or new feature development they work on.

Coordinator:

  • Kyle Machulis (qDot)

Active participants:

  • Hector Martin (marcan)
  • Joshua Blake (JoshB)

libfreenect

libfreenect is the driver and API project that includes all code that communicates directly with the hardware for Windows, Linux, and OS X. The repository is located at https://github.com/OpenKinect/libfreenect/.

Coordinator:

  • Hector Martin (marcan)

Active participants:

  • Arne Bernin - debian/ubuntu packaging
  • Theo Watson (ofTheo)
  • stephanemagnenat - Working on ROS node which uses libfreenect, would like to push changes upstream. Our lab could help with calibration.
  • zarvox - Working on camera protocol reverse engineering & documentation
  • Kyle Machulis (qDot)
  • zephod - Working on audio protocol and Win32 C++

This project has several sub-efforts.

win32

Porting the libfreenect C code to work on Windows.

Coordinator:

Active participants:

  • Kyle Machulis (qDot)

csharp

C# wrapper and API

Coordinator:

Active participants:

  • Aditya Gaddam (LostInCake) - Help with C# wrapper if and when Josh needs it. Or just testing if not.

java

Java wrapper and API

Coordinator:

  • Scott Byrns (scottb)

Active participants:

python

Python wrapper and API

There are several people working on python. Please find each other on IRC and email and choose a coordinator. -JoshB

Coodinator:

  •  ?

Active participants: