{"id":19184464,"url":"https://github.com/connerkt/projectprep1","last_synced_at":"2026-02-01T09:32:52.422Z","repository":{"id":159913023,"uuid":"620998322","full_name":"ConnerKT/projectprep1","owner":"ConnerKT","description":null,"archived":false,"fork":false,"pushed_at":"2023-04-03T15:44:58.000Z","size":14,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-06-30T14:08:01.163Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ConnerKT.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-03-29T19:39:10.000Z","updated_at":"2023-03-29T19:39:10.000Z","dependencies_parsed_at":null,"dependency_job_id":"a6782774-c411-4cd6-9667-88189f72365f","html_url":"https://github.com/ConnerKT/projectprep1","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/ConnerKT/projectprep1","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ConnerKT%2Fprojectprep1","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ConnerKT%2Fprojectprep1/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ConnerKT%2Fprojectprep1/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ConnerKT%2Fprojectprep1/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ConnerKT","download_url":"https://codeload.github.com/ConnerKT/projectprep1/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ConnerKT%2Fprojectprep1/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28975259,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-01T08:16:14.655Z","status":"ssl_error","status_checked_at":"2026-02-01T08:06:51.373Z","response_time":56,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-09T11:07:16.092Z","updated_at":"2026-02-01T09:32:52.400Z","avatar_url":"https://github.com/ConnerKT.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# projectprep1\n\n## Members\nConner Thompson\nGeorleshia Minter\nAlexia Hall\nKat\n\nhttps://docs.google.com/presentation/d/1OsolhblL_xh99npIAs8GhqN7WkTTRPAKHnJCG7IghRY/edit#slide=id.g2accd1c413_3_31\n\n# Cooperation Plan\n\n## Questions\n\n    What are the key strengths of each person on the team?\n    How can you best utilize these strengths in the execution of your project?\n    In which professional competencies do you each want to develop greater strength?\n    Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?\n\n ## Answers\nConner\n1. My key strengths are my persistence and knowledge.\n2. In order to succeed for this project I'm going to use persistence and knowledge to lead others and learn together.\n3. I want to develop my leadership skills and teamworking skills.\n4. Knowing that in order to get work done the people will have to be here and prepared to work.\n\nGeorleshia\n1. Some of my key strenghts include, my leadership and delegation skills, organization and planning, and strong work ethic.\n2. I will best utilize my strenghts in this project by helping my peers stay organized and provide feedback to help the group succeed. \n3. During this project I want to be more empathetic and show affective leadership abilitiles. \n4. To approach the day-to-day work, I will make sure i communicate daily any ideas presented and making sure each member highlights their part of the code to keep down confusion.\n\nAlexia\n1. My team mates shows accountability and persistance and also communicate well.\n2. For success its important to have these skills even when you are not as motivated you are surrounded by people who are and can remind you.\n3. I personally am working on being more consistant.\n4. Be prepared and communicate with others\n\nKat\n1. My key strenghts are curiosity of all things and always wanting to learn more, and being empathetic, understanding, and considerate of others, so I always am willing to hear other's ideas and feelings on things.\n2. I will give it my all at all times and try to come up with good ideas and be always open to new ones from my team.\n3. I want to be able to help the team and not hold them back from my lack of skills in certain things and be able to show my skills in others, and support them and myself in any way possible.\n4. To approach the day to day work, I will ask questions when I need help and try to give answers to those who may also need help.\n\n# Conflict Plan\n\n## Questions\n\n\n    What will be your group’s process to resolve conflict, when it arises?\n    What will your team do if one person is taking over the project and not letting the other members contribute?\n    How will you approach each other and the challenges of the project knowing that it is impossible for all members to be at the exact same place in           understanding and skill level?\n    How will you raise concerns to members who are not adequately contributing?\n    How and when will you escalate the conflict if your resolution attempts are unsuccessful?\n    \n## Answers\n\nConner\n1. To communicate efficently and help each other out.\n2. Take accountability for their work and to hold each other to that so no one is overworking.\n3. To know that this is a learning experience no matter what for anyone, because you can learn from the smallest things.\n4. To communicate with them that this is a group project, and you're responsible for your work.\n5. Contact instructors and tell them that they aren't doing their work, you should do your work if given.\n\nGeorleshia\n1. Our group will practice a team-building exercise. This can help relationships to build and small conflict to be addressed.\n2. Team members contribute more and work harder for any project if they feel like ownership in its success or failure to communicate openly and honestly.\n3. This is where communication comes in, making sure that we are available to text or slack when needed. \n4. By speaking with them concerning their part of the group and remebering they are not alone and if they need assistance its okay to ask.\n5. Speak with another instructor to try and smooth out the process.\n\nAlexia\n1. I will prefer to have a conversation that consist of the problem, how it made you feel or what you think and add a solution behind it.\n2. I will communicate the issue explain how this is a group project and ask the why behind it and collectively come up with a better solution.\n3. Keep communication open and zoom.\n4. I will have a respectful quick check-in\n5. notify the instructor if need be.\n\nKat\n1. Communicate Efficiently and help each other out, leave no man behind. We're in this together.\n2. Confront them and help them to distribute the work load so that all are being held accountable for part of the project.\n3. Being considerate and understanding and help when needed. All questions are good questions. We all have our own talents. Just because you lack some that another may have, doesn't mean you don't have talents in another area that you're good at and maybe they aren't as good at those talents themselves. Everyone is different and learns differently and there is nothing wrong with that.\n4. Communicate with them about whats going on, find out why, and fix the problem together.\n5. Speak with an instructor in a calm way. There should never be a reason for conflict in a project, all that is needed is to make sure you communicate issues, to whomever it needs to be said to. Being straightforward is key a lot of times in life.\n\n# Communication Plan\n\n##  Questions\n\n\n    What hours will you be available to communicate?\n    What platforms will you use to communicate (ie. Slack, phone …)?\n    How often will you take breaks?\n    What is your plan if you start to fall behind?\n    How will you communicate after hours and on the weekend?\n    What is your strategy for ensuring everyone’s voice is heard?\n    How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?\n\n## Answers\n\nConner\n1. I'm available every day until 6pm, and usually on the weekends I'm free unless stated otherwise.\n2. Slack is a good communicate device because we have a group chat.\n3. Take breaks whenever needed, but making sure your work is done in the process.\n4. If I fall behind I'm going to push myself to catch up and work hard.\n5. If I'm not able to communicate during those times I'm going to let the person know and hope they respect it.\n6. To give everyone a chance to voice their opinions.\n7. To welcome all ideas no matter how big or small, and to enable each other to have a safe zone.\n\nGeorleshia\n1. I have open availability. As long as you reach out before 8pm on weekdays or after 8am on weekends.\n2. I feel like using slack and group messaging will be the most effective to complete the project and communicate.\n3. I will take breaks when i feel overwhelemed or when the group is becoming stressed out.\n4.If I seem to start falling behind , I will make sure i communicate with the team that i need help or also let my instructor know i have fell behind.\n5. Understanding each other's time and respecting boundaries as far as when to communicate after the respescted time we informed each other of.\n6. To make sure everyone's voice is heard I will make sure i ask each partner their outlook on the questions and how they feel about the work so far.\n7. Be open to heaing all ideas, and taking apart of the persons suggestions.\n\nAlexia\n1. My hours are scattered so when ever you call or text I will try to get back to you.\n2. slack, whatsApp, message, FaceTime\n3. I'll take breaks as needed. I can work for long periods of time and also work in short increments to ensure Im not getting destracted.\n4. I will ask for help if needed and work it out. I chose to be here so its up to me to do the work to remain here.\n5. I will contact them on every communication app I have them on if there's no respones to the others.\n6. Ask questions\n7. Ask if they feel welcomed and give them space for them to express their ideas and reassure that this is a place with no judgement and respectfully hold others accountable.\n\nKat\n1. You can contact me anywhere at anytime. I will respond as fast as I can when I get the chance.\n2. Slack, email, phone calls, zoom, discord, text, etc. All is fine with me.\n3. As often as needed. But the work still needs to be done, but that doesn't mean overwork yourselves or stress your self out. You can't do a project if you aren't mentally and physically healthy to do so. Lean on others when needed.\n4. If I fall behind, I will let my team and instructor know, and figure out what to do to fix it and understand why it happene in the first place and avoid it happening again. \n5. Again, I don't mind being contacted at any time. Just be understanding if I can't respond back immediately.\n6. Talk to everyone and finding out their opinions and feelings on things and being open and understanding to all.\n7. Again, no question is a bad question. All questions and ideas are important and welcome at all times.\n\n# Work Plan\n\n## Questions\n\n\n    How you will identify tasks, assign tasks, know when they are complete, and manage work in general?\n    What project management tool will be used?\n\n## Answers\nConner\n1. As a group its best to split the work evenly, and work around eachothers strong suits so we can have a great project.\n2. We will communicate over text to let us contact eachother and split the work well.\n\nGeorleshia\n1. By giving the same amount of task to each person and being fair as far as completion goes.\n2. We will highlight accountability to make sure everyone knows to value the group's time.\n\n\nAlexia\n1. Base the assignments on peoples strenghts and growth areas and communicate that we will work evenly.\n2. We can be in a group chat on a platform that works best for all of us.\n\n\nKat\n1. Have open communication and assign things as fair as possible, relying on everyone's specific strong suites. \n2. Lean on each other when needed and give it your all no matter what. And always remember we're all learning, and communicate as much as possible, because we will all need each other, wether we like it or not.\n\n\n# Git Questions\n\n    What components of your project will live on GitHub?\n    How will you share the repository with your teammates?\n    What is your Git flow?\n    Will you be using a PR review workflow? If so, consider:\n        How many people must review a PR?\n        Who merges PRs?\n        How often will you merge?\n        How will you communicate that it’s time to merge?\n\n# Git Answers\n\n1. All commits of the project so you can have a good history of our work.\n2. Letting us collaborate on github will work well.\n3. Letting everyone work in different branches and leaving the main as a backup. Communicate when you push to main.\n4. In order to have a good workflow, people should communicate always when pushing, merging should be done by the main contributor, merge when possuble, and when the group agrees its a final change.\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fconnerkt%2Fprojectprep1","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fconnerkt%2Fprojectprep1","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fconnerkt%2Fprojectprep1/lists"}