From Fedora Project Wiki
< Changes
(→Scope) |
|||
| Line 25: | Line 25: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
- Packaging: williamjmorenot at fedoraproject.org | |||
- Review and QA: mayorga at fedoraproject.org | |||
<!-- What work do the feature owners 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?--> | <!-- What work do the feature owners 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?--> | ||
* Other developers: | * Other developers: not a System Wide Change <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other 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?--> | <!-- What work do other 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?--> | ||
* Release engineering: | * Release engineering: not a System Wide Change <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | ||
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook --> | Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook --> | ||
* Policies and guidelines: | * Policies and guidelines: not a System Wide Change <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
* Trademark approval: | * Trademark approval: not needed for this Change | ||
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | ||
Revision as of 14:35, 5 June 2015
Frappe Framework
Summary
A full-stack web framework based on Python and Javascript to help you build powerful business apps and nifty extensions.
Owner
- Name: William Moreno Reyes
- Email: williamjmorenor at fedoraproject.org
- Name: Eduardo Mayorga
- Email: mayorga at fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 23
- Last updated: 06-04-2014
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
- Frappe is a Python and JavaScript framework.
- Frappe is the Framework on top ERPNext it is builded.
- Frappe has libraries and API for everything from authentication to reports.
- Frappe is built with the philosophy make it a "battries included" framework
Benefit to Fedora
Bring to Fedora a Python Framework with active upstream community and a growing user community, please note than Fedora will become in the first distro to ship the Frappe Framework.
Scope
- Proposal owners:
- Packaging: williamjmorenot at fedoraproject.org - Review and QA: mayorga at fedoraproject.org
- Other developers: not a System Wide Change
- Release engineering: not a System Wide Change
- Policies and guidelines: not a System Wide Change
- Trademark approval: not needed for this Change
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)