[vmchecker-request] Intalnire cu Bogdan Sandulescu + uberVU

Razvan Deaconescu razvan.deaconescu at cs.pub.ro
Thu Jan 31 07:23:39 EET 2013


Razvan Deaconescu <razvan.deaconescu at cs.pub.ro> writes:
> Razvan Deaconescu <razvan.deaconescu at cs.pub.ro> writes:
>> Cosmin Didii <cosmin.didii at gmail.com> writes:
>>> Salut,
>>> Imi cer scuze ca am raspuns asa greu, dar am fost prins cu examenele.
>>> Eu pot sa vin saptamana viitoare oricand, in afara de marti.
>>
>> Cool. O să discut cu Bogdan și vă anunț.
>
> Rămâne joi, 31 ianuarie 2013, de la ora 16:30 la sediul uberVU, strada
> Alexandru Câmpeanu, nr 24[1].
>
> [1] https://maps.google.com/maps/place?ftid=0x40b2021d4e8d3667:0xab649548e027672f&q=campeanu+alexandru,+bucharest&hl=en&ie=UTF8&ll=44.456277,26.075771&spn=0.01089,0.026157&t=m&z=16&vpsrc=0

Am adăugat în descrierea întâlnirii agenda de mai jos.

Răzvan

---
1. Unify repository and simplify deployment [Puppet, Vagrant]. Achieve a
replicable production environment

Get rid of "This module depends on pyinotify:
http://pyinotify.sourceforge.net/"

2. High level documentation to get you started. Current documentation found
on github is not geared towards contributors.

3. Does it have a test suite to ensure any changes don't break the whole
system? This will allow for easier on-boarding for contributors and for an
move fast, break things approach (if core systems are tested)

4. Unified API over current vmchecker ops (like adding assignments, etc)
... Django for managing objects within the system

5. vmchecker + CDL improvements

6. Deployment. Push to master deploys code. How important is for the system
to be up?
---


More information about the vmchecker-request mailing list