Skip to content

Potential Grokers

Katie McLaughlin edited this page Dec 24, 2015 · 1 revision

GitHub isn't the only place where OSS happens. There are other grokers that can be created to help find those who are working hard and are under-recognised.

Requirements

A groker should:

  • provide a view of information not easily found via the native web interface
  • provide an input for a project name, and an output of users who have contributed
  • be simple and easy to use

Candidates

Bugzilla

  • Potential project name: insert pun name here
  • Requester: Stewart Smith via labhr/octohatrack#13.

Bugzilla is use by a few big open source projects, including the kernel and mozilla.

Technical Challenges: Bugzilla introduced a native API in version 5, but a lot of systems still run 4.4. There does exist an XML RPC, but it appears to be harder to use than a JSON API. The solution would have to be able to handle both, or allow it to be specified.

Stack Overflow

  • Potential project name: insert pun name here

Sufficiently popular projects often have technical questions asked for on the Stack Overflow platform, and be grouped by tags.

A very simple implementation would be to use the existing Top Answerers API to show the top 30 answerers for a specific tag.

More complex solutions could involve checking for all participants on questions tagged with the search term, including asker, answerers and all comments.

Non-Code Grokers

There may be systems which have sufficiently detailed listings, but may be hard to find. It stands to reason that instead of creating applications, a sufficiently detailed documentation page may suffice for these. For example, where a specific view of information on a platform might detail contributors.

More

There's probably view for more systems to have implementation or documentation. To start a discussion, create an Issue

Clone this wiki locally