Latest revision as of 14:21, 19 January 2015

Deprecated template!
From Fedora 20 the Feature process was replaced by the Planning Process!. Please, use the new empty template.

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.

Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler

All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed

Feature Name

Summary

Owner

Name: Your Name

Email: <your email address so we can contact you, invite you to meetings, etc.>

Current status

Targeted release: [[Releases/<number> | Fedora <number> ]]
Last updated: (DATE)
Percentage of completion: XX%

Detailed Description

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion

See Talk:Features/Your_Feature_Name

@@ Line 1: / Line 1: @@
+{{admon/caution|Deprecated template!|From Fedora 20 the Feature process was replaced by the [[Changes | Planning Process]]!. Please, use the new [[Changes/EmptyTemplate | empty template]].}}
 {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
-{{admon/important | Set a ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
+{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
 {{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
@@ Line 9: / Line 11: @@
   We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
-<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
+<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
+= Feature Name <!-- The name of your feature --> =
-= Feature Name <!-- The name of your feature --> =
-User can able to change filename/Folder name in open dialog box
 == Summary ==
 <!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
-Most of the time we have seen. If any person wants to change filename or folder name. and he just "open file" dialogue or "save file" dialogue. We should have option where we can able to change the file name. If any person used key "F2" then file/folder need to ready to change for editing.
 == Owner ==
 <!--This should link to your home wiki page so we know who you are-->
-* Name: Manish Runwal
+* Name: [[User:FASAcountName| Your Name]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
-* email: manish@runwalsoft.com
+* Email: <your email address so we can contact you, invite you to meetings, etc.>
 == Current status ==
-* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]
+* Targeted release: [[Releases/<number> | Fedora <number> ]]
 * Last updated: (DATE)
 * Percentage of completion: XX%
@@ Line 33: / Line 33: @@
 == Detailed Description ==
-Most of the people are in hurry to make changes fast. and they don't want to leave the current screen whatever they are using. Lets say e.g. I am using kate and I clicked on save. lets say I have imagined that I want to save that name with "ABC.txt" but I found that "ABC.txt" is already their. On that time if I want to change old ABC.txt with new name then I have to open dolphin/File Browser so rename the folder then I have to change to path where that "ABC.txt" file is already their. But As you can see that this is really long process. rather If we provide option on the same screen of save dialogue or File Open Dialogue then it will be easier for any person to edit the filename. and then he can proceed with rest of his work. This will be handy tools for all people
+<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 == Benefit to Fedora ==
-This will be cool features. and It will increase productivity of the person. and reduce its extra efforts.
+<!-- 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 Fedora become a better distribution or project because of this feature?-->
 == Scope ==
-I am not sure about what need to be edit/added in existing system. Might be more technical person can able to comment on this.
+<!-- 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?-->
 == How To Test ==
-This is quite simple to test.
+<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
-Hardware requirement : I don't think so their will be need of hardware requirement
+Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
-Software Requirement : Not sure.
-Where need to work : All applications, kate,kwrite, gnome, where ever save as, save , open dialogue.
-Just open editor(or even Office)
+A good "how to test" should answer these four questions:
-. write something in blank file.
-. click on file -> save
-. Next dialogue box will appear. before click on save you will see some file which are already their. just try to rename the files and folder (depending upon their rights). for renaming you need to press "F2". and see whether its really working or not.
+. What special hardware / data / etc. is needed (if any)?
+. How do I prepare my system to test this feature? What packages
+need to be installed, config files edited, etc.?
+. What specific actions do I perform to check that the feature is
+working like it's supposed to?
+. What are the expected results of those actions?
+-->
 == User Experience ==
-Whatever is renamed. it should be actually renamed.
+<!-- 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 ==
-Not sure where ever its being reflected
+<!-- 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, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 == Contingency Plan ==
-If the things are not working then we don't allow to edit file or folder.
+<!-- 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 you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 == Documentation ==
-* This is simple feature for better usability. Any one can able to edit on run.
+<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+*
 == Release Notes ==
-I expect that this feature need to added on Fedora 13
+<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+<!-- 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 documentation team and shipped with the release. -->
+*
 == Comments and Discussion ==
-Just started the page so don't know about discussion.
+* See [[Talk:Features/Your_Feature_Name]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

Search

Features/EmptyTemplate: Difference between revisions