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.
This is a specification for a word completion and word prediction software. It comes into the form of a library with an appropriate API/demon, so that other software developer can use it in their applications. However, it will come directly with an application that watches what the user types so that its fonctionality can be used independently from other applications.
Moreover, it will sport intelligent behaviour, like typing a space and activating a software shift after a colon...
Finally the user will be able to define keywords that will automatically be replaced by determined text specified by the user.
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.
Some users, especially those that need assistive technology like an onscreen keyboard, are relatively slow to type on the computer. A software that reduces the number of keystrokes they have to type by suggesting and automatically typing letters and text would improve their efficiency.
You can have subsections that better describe specific parts of the issue.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
- 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.
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.
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.