Hi AUT UpStage Team!
AUT UpStage Team schrieb:
> Thank you for your email (and sorry it has taken so long to get back
to you), you have obviously spent a considerable amount of time thinking
about this and we appreciate any assistance you are able to offer. Your
> email had only a broad outline of timeframe, would you please provide
some more information regarding this i.e. how much time are you able to
devout to this and an estimation of how long each task would take you?
Right now I have semester break till beginning of october, but some of
the time I have to work to get a living. Currently I am spending 1-3
days per week for UpStage. From October till February I will probably
write a diplome thesis about UpStage (subject is not clearly defined
yet, but probably "Usability" and/or "AV Streaming" - will be rock-solid
defined latest in October) and therefore will spend about a minimum of
three days per week. I hope you agree to my intent and give "permission"
Currently I thought of some personal milestones which should help myself
to determine my personal time frame. These are currently kind of loose,
and of course I am able and willing to synchronize with a global
Until beginning of September:
- Base Work: most of the ant part and dependencies to this (like install
scripts for festival, ming, swftools) to have a fundament to work with
- Time to publish my changes
Until beginning of October:
- Unifying all options and configuration
- Replacing all shell-scripts by (native) python
- Installer scripts (deb, rpm, exe, app, ...)
- Maybe some network related things (protocol, transport)
Starting from October till December:
- Bugfixes and new Features
- User Interface (webpart & flash ui)
- Network related things (protocol, transport)
December to February (or sort of open end):
All of the time I will do documentation in parallel (in code or separate
documents). Because my personal time frame can slightly differ from real
time needed, some tasks can slide one or two weeks back and forth but in
general this should be a realistic estimation.
Some additional remarks for my part for further development:
As I have also seen the SF page contains a trac site which could
probably be helpful for further development. If agile methods can take
place by using trac, I would greatly appreciate this (roadmap, tickets,
wiki, etc). IMHO the SF native functionalities are also practicable, but
lack further flexibility (e.g. linkage between each functionality). A
public dedicated project server (performance!) with trac would be really
I also noticed that the subversion repo is kind of neglected, because I
am missing a tag structure and tidy trunk and branches. Is it scheduled
to update this? Are you considering using tags?
If it is possible I would be pleased to get an own branch for my
changes. Probably you will also be setting up your own.
Another thing is, that the SF tracker seems to contain outdated
information. Are all issues in a correct current state? As noticed
before, IMHO this could probably be managed efficiently using trac.
> Our team has discussed your email and think that setting up a
protocol that all developers can follow will best manage this situation
– we’ll email you more on this later.
Ok, I am eager to hear from you and hope you agree to my planning so far
(hoping not to be too dominant and distracting or bothering the
development plans by my initiative and we are acting in concert). There
is almost surely intersection between you and me reagarding further
development and so I am curious what exactly you are planning, how roles
are handled and how your schedule looks like.
BTW: you can send me a PM for skype contact if you want