Diff for "Code/cia"

Not logged in - Log In / Register
Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2009-12-18 13:39:45 →
Size: 1384
Editor: dmitrij.ledkov
Comment:
← Revision 2 as of 2009-12-18 13:48:18 → ⇥
Size: 2132
Editor: dmitrij.ledkov
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * '''Created:''' 2009-12-18 by JulianEdwards
 * '''Contributors:''' dmitrij.ledkov		  * '''Created:''' 2009-12-18 by dmitrij.ledkov
 * '''Contributors:'''
Line 26: Line 26:
To be done.
Line 29: Line 30:
 * Replace a very manual task with an automated one
 * Better use of the infrastructure
 * Results are stored in the librarian, which is visible and managed through Launchpad.		  * bzr-cia is currently available
 * It works on local machine and relies on each developer installing and configuring it
 * Launchpad should be sending CIA notifications instead cause that's what counts
Line 35: Line 36:
 * Project developers can have a live chat about commits
 * We can subscribe UDD branches to get uploads notifications on IRC
Line 38: Line 41:
 * Cia.vc email / xml interface will be used
 * Solution is based on top of existing email commit notifications
Line 41: Line 46:
 * User subscribes "cia.vc" bot to a branch.
 * Notifications are send to cia.vc on branch updates.
 * Project owners can unsubscribe "cia.vc" bot.
Line 43: Line 52:
 * Create a new email notification format which is an implementation of CIA.vc xml notification.
 * Create a bot/user which has xml notification by default
 * When bot is subscribed to a branch it will start receiving xml notification on cia@cia.vc email address
 * CIA.vc takes it from there and does IRC notifications.

Contents

  1. Overview
    1. Overall Summary
    2. Release Note
    3. Rationale
    4. Use cases
    5. Assumptions
  2. User Interface
  3. High-level implementation points
  4. Implementation Plan
    1. Code Changes
    2. Schema Changes
    3. Estimations
    4. Migration
  5. Unresolved issues

Overview

Overall Summary

Summary: Send automatic notifications to cia.vc from launchpad without hooks or plugins.

Goal/Deliverables: Send xml branch notifications to cia@cia.vc.

We will know we have finished when anyone can subscribe any branch for cia notifications

Release Note

To be done.

Rationale

  • bzr-cia is currently available
  • It works on local machine and relies on each developer installing and configuring it
  • Launchpad should be sending CIA notifications instead cause that's what counts

Use cases

  • Project developers can have a live chat about commits
  • We can subscribe UDD branches to get uploads notifications on IRC

Assumptions

  • Cia.vc email / xml interface will be used
  • Solution is based on top of existing email commit notifications

User Interface

  • User subscribes "cia.vc" bot to a branch.
  • Notifications are send to cia.vc on branch updates.
  • Project owners can unsubscribe "cia.vc" bot.

High-level implementation points

  • Create a new email notification format which is an implementation of CIA.vc xml notification.
  • Create a bot/user which has xml notification by default

  • When bot is subscribed to a branch it will start receiving xml notification on cia@cia.vc email address

  • CIA.vc takes it from there and does IRC notifications.

Implementation Plan

Code Changes

Schema Changes

--- Variant One ---

Advantages:

Disadvantages:

Estimations

Migration

Unresolved issues

CategoryCategory CategoryProposal CategoryTemplate

Code/cia (last edited 2009-12-18 13:48:18 by dmitrij.ledkov)