XS Community Edition/Features/user management framework: Difference between revisions
m (→Owner) |
mNo edit summary |
||
| Line 25: | Line 25: | ||
== Detailed Description == |
== Detailed Description == |
||
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.'' |
|||
In a school context, the Karma Learning System requires the school to create a list of all persons who have been assigned XOs. There is also a list of XOs. This information is used to recognize staff members who have special privileges and to provide appropriate lessons to students based on their grade (actually, like Moodle, the courses in which they are enrolled - which in primary school is the same thing). |
|||
This 'framework' is based on Django for convenience. It is available to any web application on the school server. |
|||
== Benefit to XSCE == |
== Benefit to XSCE == |
||
| Line 33: | Line 37: | ||
== Scope == |
== Scope == |
||
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?'' |
|||
This feature has already been implemented and needs to be moved to the codebase of XSCE. |
|||
==UI Design== |
==UI Design== |
||
Revision as of 22:06, 21 October 2013
Summary
Framework for user, and group, access control lists for web applications
Owner
- Name: Tony Anderson
- Email: tony_anderson@usa.net
Current status
- Targeted release: 0.5
- Last updated:
- Percentage of completion: 90%
Detailed Description
In a school context, the Karma Learning System requires the school to create a list of all persons who have been assigned XOs. There is also a list of XOs. This information is used to recognize staff members who have special privileges and to provide appropriate lessons to students based on their grade (actually, like Moodle, the courses in which they are enrolled - which in primary school is the same thing).
This 'framework' is based on Django for convenience. It is available to any web application on the school server.
Benefit to XSCE
What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will XSCE become a better platform or project because of this feature?
Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.
Scope
This feature has already been implemented and needs to be moved to the codebase of XSCE.
UI Design
Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.
How To Test
Testing notes go here
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Contingency Plan
If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The XSCE Release Notes inform end-users about what is new in the release. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.