open-sTeam is a platform for cooperative work and cooperative learning developed at the university of paderborn in germany. the platform is being used at http://societyserver.org/ and is being developed further.

one of the new features is a RESTful api to allow building modern websites with sTeam as a backend.

thanks to FOSSASIA this year we have several students working on sTeam: https://github.com/societyserver/sTeam/wiki/GSOC-2016-Work-Distribution

the goal for hackweek 15 is to merge new contributions and describe tasks and projects for new contributors.

sTeam code can be found at: https://github.com/societyserver/sTeam and install instructions at http://societyserver.org/how-to-install-sTeam---quick-notes

Join this project Leave this project

Looking for hackers with the skills:

documentation testing

This project is part of:

Hack Week 12 Hack Week 14 Hack Week 13 Hack Week 15

Activity

over 9 years ago: eMBee removed keyword c from this project.

over 9 years ago: eMBee removed keyword autoconf from this project.

over 10 years ago: eMBee added keyword "documentation" to this project.

over 10 years ago: eMBee added keyword "testing" to this project.

over 10 years ago: eMBee added keyword "c" to this project.

over 10 years ago: eMBee added keyword "autoconf" to this project.

over 10 years ago: eMBee started this project.

over 10 years ago: eMBee originated this project.

Comments

Be the first to comment!

Similar Projects

documentation

Advent of Code: The Diaries by amanzini

Description

It was the Night Before Compile Time ...

Hackweek 25 (December 1-5) perfectly coincides with the first five days of Advent of Code 2025. This project will leverage this overlap to participate in the event in real-time.

To add a layer of challenge and exploration (in the true spirit of Hackweek), the puzzles will be solved using a non-mainstream, modern language like Ruby, D, Crystal, Gleam or Zig.

The primary project intent is not just simply to solve the puzzles, but to exercise result sharing and documentation. I'd create a public-facing repository documenting the process. This involves treating each day's puzzle as a mini-project: solving it, then documenting the solution with detailed write-ups, analysis of the language's performance and ergonomics, and visualizations.

                               |
                             \ ' /
                           -- (*) --
                              >*<
                             >0<@<
                            >>>@<<*
                           >@>*<0<<<
                          >*>>@<<<@<<
                         >@>>0<<<*<<@<
                        >*>>0<<@<<<@<<<
                       >@>>*<<@<>*<<0<*<
         \*/          >0>>*<<@<>0><<*<@<<
     ___\\U//___     >*>>@><0<<*>>@><*<0<<
     |\\ | | \\|    >@>>0<*<0>>@<<0<<<*<@<<
     | \\| | _(UU)_ >((*))_>0><*<0><@<<<0<*<
     |\ \| || / //||.*.*.*.|>>@<<*<<@>><0<<<
     |\\_|_|&&_// ||*.*.*.*|_\\db//_
     """"|'.'.'.|~~|.*.*.*|     ____|_
         |'.'.'.|   ^^^^^^|____|>>>>>>|
         ~~~~~~~~         '""""`------'
------------------------------------------------
This ASCII pic can be found at
https://asciiart.website/art/1831

Goals

Code, Docs, and Memes: An AoC Story

Have fun!
Involve more people, play together
Solve Days 1-5: Successfully solve both parts of the Advent of Code 2025 puzzles for Days 1-5 using the chosen non-mainstream language.
Daily Documentation & Language Review: Publish a detailed write-up for each day. This documentation will include the solution analysis, the chosen algorithm, and specific commentary on the language's ergonomics, performance, and standard library for the given task.