Skip to content

oxychan/submission_media_player

 
 

Repository files navigation

submission_media_player

Welcome developers! This repository provides a streamlined process for submitting your Flutter media player projects. Get your creation out there quickly and effortlessly!

Steps to Submit:

  1. Fork It Up! (🍴) Head over to the main submission_media_player repository and click the "Fork" button. This creates your own copy on GitHub

  2. Clone It Down! (⬇️) Open a terminal or command prompt and navigate to the directory where you want to work on your submission. Use the git clone command to create a local copy of your forked repository.

    • Replace <your_username> with your GitHub username:
    git clone https://github.com/<your_username>/submission_media_player.git
  3. Branch Out! (🌿) Navigate to the cloned directory. Create a new branch dedicated to your submission using git checkout -b <your_branch_name>. This keeps your changes organized.

    • Replace <your_branch_name> with your real name
  4. Show Us Your Project! (🧑‍💻) Copy all the files and folders from your Flutter media_player project. Paste them into the cloned submission_media_player directory.

  5. Stage for Glory! (️✅) Use git add to tell Git which changes you want to include in your submission:

    git add .
  6. Commit It! (💬) Capture your changes with git commit -m "<commit_message>". Replace <commit_message> with a clear description of your submission.

  7. Push It Out There! (⬆️) Now, share your work with the world! Use git push origin <your_branch_name> to upload your changes to your forked repository on GitHub.

  8. Pull Request It! (🤝) Visit your forked repository page on GitHub and click "Pull Requests." Initiate a pull request to merge your changes with the main repository.

    Pull Request Description Form:

    When creating your pull request, please fill out the following information to help me evaluate your project:

    Title: Your Full Name - Flutter Media Player Submission

    Description:

    • Tutorial Completion Time: (How long did it take you to complete the tutorials? [e.g., 2 days, 1 week])
    • Tutorial Clarity: (On a scale of 1 (Least Clear) to 5 (Most Clear), how clear and easy-to-follow were the tutorials?)
    • Project Difficulty: (On a scale of 1 (Easiest) to 5 (Hardest), how challenging did you find developing this project?)
    • Project Satisfaction: (On a scale of 1 (Least Satisfied) to 5 (Most Satisfied), how satisfied are you with your final project?)
    • Additional Feedback: (Share any additional thoughts or feedback you have about the tutorials or the project itself)

    Example Description:

    **Tutorial Completion Time:** 4 hours
    **Tutorial Clarity:** 4 (Clear and easy to follow)
    **Project Difficulty:** 3 (Moderately challenging)
    **Project Satisfaction:** 5 (Very satisfied, learned a lot!)
    **Additional Feedback:**
    The tutorials were very helpful, especially the section on building the user interface. I would love to see more tutorials on advanced features like user authentication.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Dart 77.9%
  • C++ 10.8%
  • CMake 8.6%
  • Swift 1.0%
  • HTML 0.9%
  • C 0.7%
  • Other 0.1%