Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
HackDay Landing Page
This year the HackDay is a wide open event. If you've got ideas on what kinds of projects you want to work on, add them to this page and invite people to join you. It is fine if you just want to use this year's HackDay as a way to catch up on some of your own OSS efforts, too. Feel free to add that, too.
- Triage bugs on an existing project/framework
- Organize a feature sprint
- Spend time writing docs and/or demo code for an existing project
- Finally start that new OSS project you've always wanted to create
- [add your ideas here]
HAL-FORMS Spec client Implementation Hack-up.
I'll have a Web API server up and running emitting HAL responses that also have HAL-FORMS references. I'm looking for people interested in working on sample implementations of the HAL-FORMS spec (e.g. a HAL-client app that supports HAL-FORMS, a HAL-FORMs plug-in for other frameworks, etc.) and help w/ any subsequent HAL-FORMS spec clean-up/improvements that surface while building the samples. Mike Amundsen
- HAL-FORMS Spec
- HAL-FORMS Spec Repo
- HAL Service that Emits HAL-FORMS
- HAL Client that supports HAL-FORMS
- HAL-FORMS Service and Sample Client Repo
- Suggest/Options Writeup <-- buried in another draft
The Web Annotation Protocol is a Candidate Recommendation soon to reach "Technical Recommendation" at the W3C. It's a minimal, Web Annotation moving system. It's minimal enough to have both server and clients built in a day (or less)! I'd love to have folks "stress test" the protocol by implementing it (from either end!). Whadyathink?! - Benjamin Young
The REST Fest Videos Project is currently a collection of several Vimeo channels. To find videos, you have to search all of Vimeo. Descriptions are generally basically informative (thanks videography people!), but the whole thing would be most amazing with a People, Topic, Video, Year, etc. API...dontcha think?! - Benjamin Young
Chrome extension which detects API specs used on a page
Most of API consoles and even some API documentation use some API definition format (OpenAPI, RAML, I/O docs, API Blueprint, etc.) under the hood. But in the absolute majority of the cases, no link to the API spec is provided on a page itself. The current solution is to open "Network tab" and manually inspect all suspicious files. If we have additional time we can add "Open with ..." menu with tools like: "swagger-editor", "swagger-codegen", "api-spec-converter", etc. - Ivan Goncharov
When evolving an API, breaking change is a thing to always keep in mind. But what is a "change", what is a "breaking change"? The purpose of this hackday proposal is to work both on identifying possible changes and who/what they will affect (interface contract, generated code, documentation ...) and creating some tool(s) which will detect these changes (based on API description like OpenAPI). (This proposal can bring some topics ideas for Mike's panel How do you version your API? Arnaud Lauret
API Design check
What about create a tool to check if an API specification conforms to design rules? URL formats, case, data types, naming conventions (plural names, verbes, singleton, ...). Jason Harmon started to build one mainly based on regex, could the idea be expanded/rewrite to include more intelligence (mainly on naming conventions). Arnaud Lauret
Restlet Framework NG
10 years have passed since the launch of Restlet Framework v1, the first RESTful API framework created, and thanks to our efforts and our open source community, we have gathered a lot of experience along the way. In parallel, the continuous innovation, competition and maturation in the web API space in general and in the Java space as well has created an opportunity to innovate again. The goal is to have a prototype of the v3 of the framework working, based on Netty and Reactive Streams, supporting HTTP/2 and async APIs in a RESTful way. Jerome Louvel
Web Concepts Hacking
Web Concepts is a collection of concepts that matter for the "uniform interface" of the Web. Recently, JSON versions of the Concepts and the underlying Specs were made available. This proposal is about taking those concepts and using them for any kind of webby tooling: documentation, design, discovery, and similar things. The goal is to (1) make sure the JSON is useful and maybe tweak the format before it becomes more stable, and (2) see if additional information/data would make Web Concepts more useful. - Erik Wilde
Extending JSON-LD Support in NetKernel
JSON-LD is a data serialization format intended to help connect the worlds of web development and linked data. People who want to think about interlinked graphs of information can. People who want to just shove stuff in Angular can. There are quite a few capabilities to JSON-LD, however, that allow for automatic conversion of information from one form to another, using one set of terms to another. I want to take the rare opportunity of having the time to work on something like this to extend the JSON-LD capabilities available in the NetKernel resource-oriented environment.
The RESTful blockchain
The blockchain is conceptually interesting, but difficult to penetrate technically. We should be able to combine a semantically straightforward REST/HTTP interface with some application that utilizes the blockchain to create a programmatic marketplace.