This is a read only archive of pad.okfn.org. See the shutdown announcement for details.

bcg15-appdev -------------------------------------------
Übersichtspad: https://pad.okfn.org/p/bcg15
-------------------------------------------


Session Dokumentation appdevcamp
================================


TAG 3
---------


SLOT 1
----------


Session owner
Who offered that session?
(For public documentation please just add the first name.)

Participants


Results
A summary of your results. You may keep this very short. “We had a very intense discussion on xyz” can be your full documentation. You don’t need results, in some cases the discussion is all you need.


SLOT 3 Static Site Generators (Jogi) 
----------

Link-list:
    - https://staticsitegenerators.net/ (Listing of static site generators) 
    - http://blog.getpelican.com/    

Search: 
    - http://www.tipue.com/ 


TAG 2
---------

SLOT 1
----------
Session
Nachhaltige Softwareentwicklung

Session Owner
Mario (@mzupzup)

Participants
no idea exactly :)

Results:
We had a great discussion about the merits of testing, pair programming and code reviews. Also lots of great practices to help people get involved in Software Craftsmanship were discussed like Coding Dojos and Coderetreats.
We also touched on the topic of how to establish a mindset for responsible software development and software quality in an organization.
It was a great sharing of experiences and resources in the space of software craftsmanship altogether.

Resources we talked about:

Tools:
    * Spock - Groovy tests for java (https://github.com/spockframework/spock)
    * Screenhero (https://screenhero.com/)
    * http://www.codewars.com/
    * http://coderetreat.org/
    
    
Books:

Practices

Blogs

Talks

Conferences (with Videos online)



If microsoft built cars.......

SLOT 2
----------
Session owner
Olaf
https://cryptoparty.at/graz

PGP für email:
    Am Anfang lange Motivation warum wichtig? Export Recht, Amerikanisches Strafrecht, wie viele stellen um einzugreifen...
    Asymetrische Verschlüsselung:
    Erklärung: Man brauch den publik key von dem an dem man eine email schickt, um sie zu verschlüsseln. Nur jemanden mit publik key kann man verschlüsselte email schicken.
    Eigenen private key braucht man zum signieren.
    Langes Gespräch über die Schwierigkeit public keys sicher auszutauschen. 
    
    Folien:
       Unter  https://www.cryptoparty.at/graz:infomaterial findet ihr die erste Präsentation: http://glt14-programm.linuxtage.at/attachments/131_GPG_fuer_Einsteiger.odp
       Die 2. gezeigte Präsentation findet ihr unter: https://github.com/CryptoPartyGraz/Vortraege sie heist Olaf_inet.odp


SLOT 3
----------

Agiles Management. 12 Punkte plan.
Ein paar nette Zahlen:
    1-5euro pro user für sales in social marketing: Target 1M: 5M sales budget
    pro 100.000 user 1 person support
    alles 8monate update von devices mit besseren features billider -> sichtbar für user, d.h. er will es...
    Studie von Cohen (a bit biased ;) ): PM 12%, Agile: 42% 
    
    lot of info
    
    another good thing: after each sprint replace formal contract: let the customer sign what you did was good, and what we will do is of interest...

Session owner
Who offered that session?
(For public documentation please just add the first name.)

Participants


Results
A summary of your results. You may keep this very short. “We had a very intense discussion on xyz” can be your full documentation. You don’t need results, in some cases the discussion is all you need.


Leben ohne Cloud

Session owner
Karl

Responsible for documentation
Who is responsible for the session documentation. This might be multiple people.
(For public documentation please just use the first names.)

Participants
(Won’t be published.)

Results
Cloud services gehen ein. Daten sind dann ev. weg oder werden verkauft.
ZB. von google div. dienste

bsp. radioshack : haben immer versprochen, dass daten nicht verkauft werden. Aber dann doch.

syncthing, btsync, unison file sync (visualisiert wann welche dateien synchronisiert wurden)

Blog: karl-voit.at

Siehe auch Bright (Session 2 im wissenscamp), persoenliches Datenmanagement ohne Cloud

Follow-up
If you agree on a follow-up please add to the documentation.

Other resources
If available please provide links to other resources online (blogposts, videos, …)








BONUS SESSION
---------

Da das Anstellen beim Mittagessen zu einigen Problemen geführt hat (Wo ist hier das Ende?!), erwies es sich als notwendig folgendes Paper zu konzipieren:
    
    http://www.docdroid.net/xr2x/paper-1713513798.pdf.html


TAG 1
---------









Session1 Cross-Plattform
------

Discussion on native and different hybrid app development frameworks:
 + Sencha Touch: https://www.sencha.com/products/touch/
 + ionic: http://ionicframework.com/
 + Apache Cordova: https://cordova.apache.org/

Slot 2: Android und Root (Show and tell)
-------------------------------------------------------------

Rooten ist wie Jailbreaken auf iOS nur sicherer ;)
multirom (like Grub, bootloader)
CustomRecovery: easy switch between ROM and Backuped Android Versions
(for different Runtimes take care that aps match)
saved as flashable image which you can store f.e. on SD card
SuperSU is really good for super user control in android
XPrivacy... fake some data the facebook app wants (or any app for that matter)
exposed framework: YouTube AdAway: removes YouTube ad
GravityBox: completely change UI components of android
Titanium Backup: backup only data of single apps

developed an App where teachers can control witch apps are on a phone, and install Apps with the app...
similar to hockeyapp/ crahslytic, but they are more for developers



Session owner
Who offered that session?
(For public documentation please just add the first name.)

Responsible for documentation
Who is responsible for the session documentation. This might be multiple people.
(For public documentation please just use the first names.)

Participants
(Won’t be published.)

Results
A summary of your results. You may keep this very short. “We had a very intense discussion on xyz” can be your full documentation. You don’t need results, in some cases the discussion is all you need.

Follow-up
If you agree on a follow-up please add to the documentation.

Other resources
If available please provide links to other resources online (blogposts, videos, …)