-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c465e39
commit 78ab885
Showing
1 changed file
with
29 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,38 +1,44 @@ | ||
| # GitProve: A Community of IT Builders | ||
| # GitProve: Where Builders Meet | ||
|
|
||
| Welcome to GitProve, where we come together to build, learn, and share. Whether you're a beginner looking to get your feet wet or an expert aiming to share your knowledge, GitProve is the place for you. | ||
| Welcome to **GitProve**! We're a vibrant community where IT enthusiasts converge to build, learn, and showcase. Whether you're a seasoned developer, a tech newbie, or someone with a passion for innovation, GitProve offers a space to collaborate, grow, and shine. | ||
|
|
||
| ## Mission | ||
| 🌐 **Website**: [https://gitprove.xyz](https://gitprove.xyz) | ||
|
|
||
| Our mission is to foster a community of IT enthusiasts who are passionate about building projects, learning from one another, and improving their skills. We believe in open collaboration, knowledge sharing, and the power of constructive feedback. | ||
| ## Our Mission | ||
|
|
||
| ## How It Works | ||
| At GitProve, our mission is to cultivate a community of IT enthusiasts who are zealous about building projects, learning collectively, and enhancing their skills. We champion the principles of open collaboration, knowledge dissemination, and the transformative power of constructive feedback. | ||
|
|
||
| - **Project Submission**: Members can submit projects as Pull Requests in a markdown file. Each project should include a roadmap plan, description, technologies used, and the team involved. | ||
| - **Review**: Projects are reviewed and, if accepted, added to our project gallery. | ||
| - **Build**: Once accepted, projects should be completed within a week. | ||
| - **Presentation**: Every week, we meet (either online or onsite) to showcase the completed projects, discuss the technologies used, and engage in a Q&A session. | ||
| ## How GitProve Operates | ||
|
|
||
| ## Guidelines | ||
| 1. **Project Submission**: Members propose projects via Pull Requests in a markdown format. Proposals should encompass a roadmap, a detailed description, the technologies to be used, and the participating team. | ||
| 2. **Review Process**: Submitted projects undergo a review. Once approved, they're showcased in our project gallery. | ||
| 3. **Building Phase**: Approved projects have a week for completion. | ||
| 4. **Presentation Day**: Every week, we convene—either virtually or in-person—to present the finalized projects, deliberate on the employed technologies, and engage in an interactive Q&A session. | ||
|
|
||
| - Projects should be open-sourced or have a portion that can be presented publicly. | ||
| - Respect the time limit. Projects are meant to be concise and achievable within a week. | ||
| - Be open to feedback and ready to provide constructive criticism. | ||
| - Collaborate, help one another, and most importantly, have fun! | ||
| ## Core Guidelines | ||
|
|
||
| ## How to Submit a Project | ||
| - **Open Source Spirit**: Projects should either be entirely open-sourced or have segments that can be publicly presented. | ||
| - **Time Respect**: Adhere to the one-week time frame. Projects should be succinct and feasible within this period. | ||
| - **Feedback Culture**: Embrace feedback and be prepared to offer constructive critiques. | ||
| - **Collaboration**: Team up, assist peers, and above all, enjoy the process! | ||
|
|
||
| 1. Fork this repository. | ||
| 2. Add your project details in a markdown file under the `projects` directory. | ||
| 3. Create a Pull Request. | ||
| 4. Wait for the review. We'll get back to you as soon as possible! | ||
| ## Proposing a Project | ||
|
|
||
| For detailed submission guidelines, please refer to [CONTRIBUTING.md](CONTRIBUTING.md). | ||
| 1. **Fork** this repository. | ||
| 2. Populate a markdown file with your project specifics and place it under the `projects` directory. | ||
| 3. Initiate a **Pull Request**. | ||
| 4. Patiently await our review. We strive to revert as swiftly as possible! | ||
|
|
||
| ## Join Us | ||
| For an in-depth understanding of the submission process, kindly refer to [CONTRIBUTING.md](CONTRIBUTING.md). | ||
|
|
||
| Interested in joining our community? Check out our [website](#) for more details or contact us directly via [email](mailto:#). | ||
| ## Engage with GitProve | ||
|
|
||
| Eager to be part of our community? Delve deeper into our [official website](https://gitprove.xyz) or directly [email us](mailto:#) for more insights. | ||
|
|
||
| ## Feedback & Suggestions | ||
|
|
||
| We're always looking to improve! If you have any feedback or suggestions, please open an issue or reach out to our team. | ||
| Your insights are our treasure! Should you have feedback or innovative ideas, please [open an issue](https://github.com/Git-Prove/GitProve-Projects/issues) or engage with our team. | ||
|
|
||
| --- | ||
|
|
||
| Thank you for being a part of GitProve! Together, we're crafting a realm where every project is a novel voyage and every collaboration a novel innovation. |