MOS Mini Hackathon: Unterschied zwischen den Versionen

(13 dazwischenliegende Versionen von 4 Benutzern werden nicht angezeigt)

Zeile 1:

= MOS Mini Hackathon =

{{Veranstaltung

|name=MOS Mini Hackathon

|image=~~No-Logo~~.~~png~~

|image=Mos_hack_ii.jpg

|involved=[[User:hop]],[[User:metaz]]

|involved=[[User:hop|hop]], [[User:metaz|metaz]], [[User:simonrepp|simonrepp]]

|when=~~14.06.2013, 17:30~~

|when=irregular regular meetups!

|category=Hackathon

|~~costs~~=

|cost=

|status=active

|wtf=Metalab Operating System ~~hacking~~, ~~or at least build a~~ development ~~enviroment foreveryone to enjoy~~

|wtf=Improving the Metalab Operating System (MOS), Introducing new people to MOS development

}}~~== WTF ==~~

}}

The gears and cogs are turning slowly for the development of our Frontpage/Membership administration Software. We like to change that and give YOU the opportunity to help making an ugly duckling shine once again.

=~~= Hacking sessions ==~~

FYI: This page is partially outdated!

[[~~MOS_Mini_Hackathon/Session01~~|~~Session 01~~]] ~~-- 14 June 2013 ~~

[[~~MOS_Mini_Hackathon/Session02~~|~~Session 02~~]] -~~- 12 July 2013 ~~

The next MOS Hackathon will take place from '''2022-11-11 18:00''' to '''2022-11-13 18:00'''. If you're interested, contact [[user:ripper|ripper]] or [[User:luto|luto]].

We irregularly meet to spend an evening improving the Metalab Operation System (MOS) - the system which handles much of Metalab's internal member management and most notably the website.

== ~~install scenarios~~ ==

== Previous sessions ==

~~experience~~ / ~~guide on how to install a MOS development enviroment~~

[[MOS_Mini_Hackathon/Session03|Session 03]] -- 14 December 2013

[[MOS_Mini_Hackathon/Session02|Session 02]] -- 12 July 2013

[[MOS_Mini_Hackathon/Session01|Session 01]] -- 14 June 2013

~~http://titanpad.com/03hFho4f77~~

== Preparing for a session ==

~~== ToDo ==~~

Before coming to a session you can prepare yourself by installing Python2.7, pip and virtualenv. (no must though! it just speeds things up :))

~~here are~~ the ~~more important bits from the mailinglist because i'm too lazy~~ to ~~write~~ it ~~up properly~~:

Some people wrote down their experiences with installing the MOS development environment on different platforms, this might greatly help you to get it done yourself: http://titanpad.com/03hFho4f77

=== ~~for those who want to contribute code~~ ===

== Code-related Agenda ==

~~Leidige Arbeit, die erledigt werden sollte, bevor ich neue Features~~

~~angehen würde:~~

* ~~Dokumentation einer lokalen Installation (hg, django, pip~~,

* Improving the documentation for installation, system architecture and deployment procedures

~~virtualenv, support-libs). [teilweise fertig]~~

* Porting to Django v1.5

* ~~Portierung auf~~ Django ~~v1.4 (~~v1.5~~) fertigstellen. [teilweise fertig]~~

* Building a dummy database for testing

* ~~Eine Dummy-Datenbank aufbauen, damit wir ohne Live-Daten testen~~

* Writing tests

~~können.~~

* Setting up a deploy procedure

* ~~Tests schreiben.~~

* Clearing the backlog of old bugs

* ~~Deployment einrichten.~~

* ~~Ein Backlog an altbekannten Bugs fixen, die lästig unter der~~

~~Schmerzgrenze herumgrundeln.~~

~~Rechnet nicht damit, bei einem ersten Workshop weiter als bis zum ersten~~

~~Punkt zu kommen~~

~~Erhöht die Chancen, beim ersten Workshop den ersten Punkt erfolreich~~

~~abzuschließen, indem Ihr mit Linux-Python2.7+pip+virtualenv vorinstalliert~~

~~daherkommt!~~

~~for the last part, more information on a current README how to set up an evniroment go here: (insert that one link)~~

== Non-Code Agenda ==

==~~= for those who want to contribute other things =~~==

Quote hop:

Ein großer Batzen Arbeit, der beim Weiterentwickeln helfen wird, ist

eine Dummy-Datenbank, damit wir sinnvolle Daten haben mit denen wir

Zeile 72:

Zeile 65:

Ahja, und dann brauchen wir wahrscheinlich noch Combat-Medics, um die

diversen Nervenzusammenbrüche zu verarzten.

[[Kategorie:Metalab_OS]]