= Project Name =
<!Update rootfs-- Replace "Project Name" with the actual name of the project in the line above. -->resize
== Project Description ==
<!Update rootfs-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->resize
== Project Leader ==
<!-- Name(s) of primary person working on the project. If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing what. For example: Include links to personal pages within wiki and to blog sites. -->Daniel Martino
== Project Contributor(s) ==
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. -->
== Project Details ==
<!The rootfs-- Provides more depth than resize package is used to resize the Project Descriptionpartitions in Pidora. This works with primary partitions and with a NOOBS(New Out Of Box System) system. NOOBS in a nutshell is the place for basically used to make setting up a Pi effortless and any person regardless of their technical discussions, project specs, or other detailsbackground can acheive. If this gets very long, you might consider breaking this part into multiple pages It however does not support extended and linking to themlogical partitions. -->
== Project Plan ==
=== Tracking ===
<!-- Describe the tracking mechanisms you are I will be using for your project (bugzilla, trac, github, ...) -->
=== Key contacts ===
<!-- Add links to any mentors or key participants in the community. -->
=== Goals by Release ===
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1
* Test partitioning resizing to accommodate Extended/Logical
* Test partitioning resizing on Pidora to accommodate Extended/Logical
* 0.2
* Continue and finish testing on Pidora
* Update and finalize rootfs-resize script
* Begin packaging
* Clean up any bugs
* 0.3
* Final package details * RPM package ready to distribute
== Communication ==
