From OpenNMS

Contents 1 DJ's suggestions 1.1 Objectives 1.2 Developer Teams 1.2.1 Mike Huot's proposal for team structure 1.2.1.1 Mike Huot's Proposed topics 1.2.1.1.1 Migrate to Hibernate 1.2.1.1.2 Add functionality to web UI 1.2.1.1.3 Create DROOLS GUI 1.2.1.1.4 Open Lazlo Topo and review topo engine 1.2.1.1.5 Migrate maps to work using Open Lazlo so they work on more than IE. 1.3 Use Cases 2 Get Together for locals to meet the team 2.1 Location - TBD 2.2 Time - TBD 2.3 What is it?

DJ's suggestions

• Have people come prepared on Monday with Eclipse and being able to build and run OpenNMS and the webapp. Have a session on Sunday night for people who need help getting setup (make sure that people know about the prerequisites well ahead of time, i.e.: linux/mac os x laptop with X amount of memory, etc.).

---

Incomplete bits that were pulled from the main page:

Objectives

TBD. Much of this should get ironed out in the upcoming OGP conference call.

Developer Teams

Last year we had the following teams. This year may be slightly different.

1. Domain Model
2. WebUI - Web Layer
3. WebUI - Service Layer
4. Persistence
5. Build/Install
6. Integration/Testing

Mike Huot's proposal for team structure

We should select 2-3 core projects to be worked on by the majority of the developers during the dev-jam. Each of these projects will have a project leader. The projects should be able to be completed 100% or completed to some major milestone by the end of dev-jam. By July 1, developers should indicate if they would like to work on one of the core projects or work independently.

Those who want to work independently, free-agents, should be able to work with the core projects, on their own projects, or work on slaying bugs. The free-agents should indicate a bit about what they plan to work on before dev-jam. The should identify when they may need help and what kind of help they may need. Other developers will have their own agendas and may not have time to help out if they are not prepared for it.

The project leaders for the core projects should develop a list of tasks prior to dev-jam. This list should be posted to a wiki. The developers should be able to choose which tasks they want to work on and communicate additional ideas there.

The core projects will hopefully have a small number of people dedicated to it. They will be the people responsible for making sure the work on the project is getting done. The project leader should give a status each morning for their project. During the status meetings we can discuss how to proceed with a project if it is stalled or in danger of not completing on time.

Mike Huot's Proposed topics

Migrate to Hibernate

Add functionality to web UI

1. Modify pollers
2. capsd enable/disable services
3. enable/disable maps
4. edit topN
5. schedule reports
6. Add ability to test notification path from WebUI
7. Add 'next event' button in Event Detail screen
8. SNMP Trap Configuration Editor
9. Overall Availability section of Node page made very ugly by long ifDescription.
10. Enhancement to Outage Page
11. Add new group
12. Interface Descriptions
13. Add filtering capability to Outages web interface
14. Notification Page - Acknowledge ALL / Advanced Select
15. SSH button on node page
16. Add the ability to sort on columns in the Categories section of the webUI
17. Add a way for admins to create notification for an event
18. Add send-event functionality to the WebUI
19. Add poll on demand to node and interface pages
20. hide an interface from the display (i.e. VLANs on a switch)
21. Build a configuration file testing utility
22. Resurrect and fix the eventconf editor in the web interface
23. Outage Editor
24. Ability to set WebUI user defaults
25. Correlating events, outages, and notifications
26. Add a sound when outages occur
27. Allow users to change their own passwords

Create DROOLS GUI

Open Lazlo Topo and review topo engine

Migrate maps to work using Open Lazlo so they work on more than IE.

Use Cases

Use cases covering our objectives

Get Together for locals to meet the team

We had no attendance last year, do we want to try for it again? (mhuot - Umm...I think no) Maybe if we had it someplace with a liquor license this time?

Location - TBD

Time - TBD

What is it?

The true power of open source comes from the community around it, not from the fact that the software doesn't cost anything. That is why the annual OpenNMS Developer's Conference, DevJam, is such a big deal. It brings people from all over the world together, face-to-face, to help bring OpenNMS to the next level. While DevJam is, sadly, one of biggest social events on our developer's calendars, we are hoping that your calendar is free enough to join us on (TODO: when?) at (TODO: where?). If you're into IT, network management and/or open source, and if you are in the area, feel free to join us for food, drink and conversation.

E-mail mhuot opennms org put the @ and . in the right place, if you are planning on attending.