Outreachy - Round 11
Typesafe and Play Framework are proud to be participating in Outreachy, a program to help groups that are underrepresented in free and open source software get involved. For detailed information about Outreachy, including how to apply, see the main program page.
This is the landing page for Outreachy Play Framework projects.
Applications for Round 11 Play Framework projects close on the 2nd of November.
The best way to get started is to read Play's Get Involved page. From there you can find information about the project issue tracker and mailing lists, links to instructions for building Play from source.
The best place to talk about Play development is on the Play contributors Gitter channel, while the Play development mailing list can be used for deeper architectural and design style discussions. Discussion about the Play Outreachy projects can be had in the Play Outreachy Gitter channel, where Play Outreachy mentors can be found (though note that the Play team is very geographically distributed, including developers in Australia, USA, New Zealand and Europe, so don't expect to get immediate responses from any particular person.
Typesafe is sponsoring one intern for Play Framework in Outreachy in Round 11.
Play Module Directory
Mentor: James Roper
Play 1 offered a module directory for Play modules, which can still be found on the Play website here. Unlike Play 1, where a home baked dependency management system was used, Play 2 uses sbt, which is able to use any Ivy or Maven based distribution system for distributing libraries. This makes the requirements of a module directory for Play 2 quite different to Play 1, which is why the Play 1 module directory has not been reused for Play 2.
Currently an ad-hoc module directory is maintained in the markdown documentation. This quickly gets out of date, and is missing features such as the ability to search for modules, as well as listing different module versions and compatibility matrices.
The new module directory should allow a user to login using their GitHub id, and then submit new modules for approval. Once approved by an admin, the user should be able to edit and maintain their module, adding new module versions. A brief outline of requirements and discussion about the feature can be found here.
The intern ideally should have some web development experience. Play and/or Scala experience will be useful, but not required.