Ideas on Hackfest
Developer Setup in less than 10 minutes
Coordinator: Douglas
Summary: Get development environment setup quickly and reduce setup mistakes.
Description:
This idea was sparked because Douglas and George will be coming to hackfest w/o their workstations but instead laptops. Instead of not participating in hackfest, the day can be spent optimizing the steps to building a workstation. Once the goal is met, they can participate in other projects.
This project is particularly important going forward because 4.6 exposes more plugin APIs then ever before. Lowering the barrier to assembling a build system is crucial to extending sipXecs and therefore adoption of sipXecs..
Goals:
- System dependencies installed
- Full source tree compiled
- RPMs built for all distributions
- Eclipse installed with setup instructions (Eclipse is preferred IDE for Java apps)
- Easy to follow instructions.
Non-Goals:
- Not creating a "wrapper script" for system setup, but leverage standard tools and checks
- Not creating a virtual machine for setup, virtual machines get out of date fast and pain to maintain.
Sip stack trace utility in sipXconfig
Coordinator: ? (Douglas added idea but may not have time to work in it)
Summary: Embed sipXsipviewer in sipXconfig to capture stack traces with CLI
Description:
Whether you're a newbie or veteran SIP engineer, when there's a problem getting a call through the system, you need to see the call flow to all components. sipXsipViewer is a nice utility to see the call flow, but it can be cumbersome to collect the logs.
Goals:
- Find active or past calls and see visual of call flow from sipXconfig admin UI
Non-Goals:
- Be nice to capture trace in multi-cluster but probably too difficult for single day
- Flipping all the processes into INFO log mode is PITA, so see if SIP messages can be extracted from a tcpdump output that is set to run in the background.