DialUpSupport

Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2007-10-25 03:56:57
Size: 3190
Editor: correo
Comment: just to improve this spec. This was a real case, without the proudly smile
Revision 4 as of 2007-10-27 07:04:20
Size: 3305
Editor: thuis
Comment:
Deletions are marked like this. Additions are marked like this.
Line 69: Line 69:
 * bluetooth devices as modems  * bluetooth devices as modems
 * ISDN support in ubuntu? (still pretty popular e.g. in germany)
Line 71: Line 72:
 * GPRS/3G support (directly or over bluetooth)

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

It should be easy to configure dial-up and ADSL out of the box, we should use Network Manager to at least bring the connections up and down.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

Use Cases

1. Andres is anxiously waiting for it's new ADSL Broadband service recently aquired. When the technician finally arrives , he/she starts to unpack the adsl modem, connects the telephone line and connects your desktop pc or laptop to the adsl modem. He/she stares at you and asks you. ¿Where are the dial-up networking folder? ¿Is this windows?. You proudly smile and show him/her the Network Manager, ready for an easy configuration. No more pppoeconfig!!!

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

  • driver support (winmodems, USB modems, ADSL)
  • connection management through network manager
  • integration with pppconfig, pppoeconfig, wvdial, etc.?
  • bluetooth devices as modems
  • ISDN support in ubuntu? (still pretty popular e.g. in germany)
  • KDE
  • GPRS/3G support (directly or over bluetooth)


CategorySpec

DialUpSupport (last edited 2008-08-06 17:00:05 by localhost)