-
Notifications
You must be signed in to change notification settings - Fork 5
Github Repository Research
Ömer Faruk Özdemir
https://github.com/serverless/serverless
Pros:
-Simple page
-Good explanation about installation and usage
-Good structure
-Convenient tool for developers.
-Good written ReadMe file, detailed explanation.
-Frequently used good issue management.
Cons:
-There is no wiki page.
https://github.com/chakra-ui/chakra-ui
Pros:
-Simple page
-Sufficient explanation
-Easy and modular tool for ui
Cons:
-Lack of wiki page.
-Lack of tags in the issues.
https://github.com/thedaviddias/Front-End-Checklist
Pros:
-Detailed explanation in the ReadMe.
-Great tool for front end developers.
Cons:
-Lack of structure and wiki page.
-Lack of labels in the issues.
Ezgi Gulperi Er
It contains a comprehensive list of prominent research papers and their implementations.
Pros:
- Well organized.
- Good for learning how to implement an intricate approach / algorithm
Cons:
- Not a real project repository
Salih Can Özçelik
https://github.com/numpy/numpy/wiki
NumPy is the fundamental package needed for scientific computing with Python.
Pros:
-Free
-Has lots of feature
-Open source
-Wiki page is okay
Cons:
-Code is difficult to follow.You can easily get lost in the code
https://github.com/excalidraw/excalidraw
A project that makes you able to create charts looks like hand drawn.
- Demo, and Code Sandbox links are provided
- Special thanks to contributors
- No wiki added
https://github.com/fritzing/fritzing-app
An Electronic Design Automation software. A desktop app that you can make electronic designs and simulate them.
- They ease to contribute
- Informative wiki
- "easy start" and "challenging start" labels are used for new contributors
- Creative Commons Attribution
- None
Hazer Babür
https://github.com/jhlywa/chess.js
It is a Javascript chess library that is used for chess move generation/validation, piece placement/movement, and check/checkmate/stalemate detection - basically everything but the AI. Lots of websites which provides chess game playing like licess, chess.com etc. uses chess.js
Pros:
-Well written and detailed README.md file
-Installation and other codes are explained very well.
Cons:
-Wiki page does not exist.
https://github.com/official-stockfish/Stockfish
Doğukan Kalkan
Stockfish is an open-source chess engine. It is one of the strongest chess engines in the world, and also stronger than any other human chess master. It is also embedded into chess websites to enable the users to analyze their games, find their mistakes and blunders and improve their games. Stockfish has been improved over the years and currently has the elo rating of 3300+ while the reigning world champion, Magnus Carlsen, has had his peak rating of 2882, which is the highest in the history of chess. Thus, Stockfish is an excellent tool for the chess masters to analyze their games and improve the variations of certain openings.
- Well-explained documentation and guideline for proper usage.
- Free and open-source.
- Contribution is possible.
- Not a complete chess program.
- Requires a UCI-compatible GUI.
https://github.com/electron/electron
That's a framework allowing developers to write cross-platform desktop applications using JS, HTML and CSS. It is based on Node.js and Chromium.
- Excellent documentation and labeling
- Issues have a conventional format.
- Issues section is abused by spam accounts and phishing scams.
- Might be complicated for beginners.
- Does not have a wiki page.
libGDX
Wiki of the Github Page
libGDX is a free and open-source game-development application framework written in the Java programming language with some C and C++ components for performance dependent code. It allows for the development of desktop and mobile games by using the same code base. It is cross-platform, supporting Windows, Linux, Mac OS X, Android, iOS, BlackBerry and web browsers with WebGL support.
- It helps to create app working on multiple platforms with single source code.
- It has lots of robust functionality.
- It has active user community on forums and many tutorials.
- It has no IDE like Godot or Unity.
- It requires some initial learning curve.
- It lacks a proper documentation and information.
https://gamedev.stackexchange.com/a/23693
https://www.quora.com/What-are-the-cons-of-libGDX/answer/Paruthi-Exe-1
- Repo : Google Cartographer
- Web page : Cartographer Web Page
- Cartographer is a system that provides real-time localization and mapping. It has ROS integration that makes life easier.
- It is started to be developed by Google. A few years ago, it became open-source. So that we can use it now instead of AMCL. It has better stability and reliability than AMCL. But it is harder to tune the parameters for our robots because it has more and complex parameters than AMCL.
- It has a good documentation on it's web page but it does not cover everything. Sometimes you should find the best solution for your robot by yourself that wastes your 3 days at least.
- A really bad thing about cartographer is that runs on only CPU. So you need a good CPU to run this system.
- Compiling this project is a disaster. You should follow the instructions strictly. You should be careful about versions.
- Cartographer has a huge community so people can ask questions and contribute to the project via issues.
- To write an issue to state a problem, there is a guideline.
- To contribute to the project, there is a link for good first issues.
- It has a good readme file. It explains the projects and there are some links for tutorials and questions. The readme file also has a google group link to join. So that people can learn the time of next meeting. Old meeting notes are also stated in the readme file.
- Unfortunately, it does not have a wiki page.
https://github.com/Marak/faker.js
It generates massive amounts of fake data in the browser and node.js. Such as image, commit, address, date, phone number. It is useful for testing web applications before publish them.
- Clean and useful coding
- Well-explained documentation and guideline for proper usage.
- Good demo.
- Well usage of issue system.
- Insufficient usage of issue labels.
- Current Members
- Former Members
- Project Description
- Project Requirements
- Customer Questions & Answers
- User Scenarios&Mockups
- Diagrams
- Meeting #1 (13.02.2020)
- Meeting #2 (20.02.2020)
- Meeting #3 (27.02.2020)
- Meeting #4 (05.03.2020)
- Meeting #5 (12.03.2020)
- Meeting #6 (05.04.2020)
- Meeting #7 (16.04.2020)
- Meeting #8 (23.04.2020)
- Meeting #9 (30.04.2020)
- Meeting #10 (07.05.2020)
- Meeting #11 (14.05.2020)
- Meeting #12 (21.05.2020)
- Meeting #13 (27.10.2020)
- Meeting #14 (03.11.2020)
- Meeting #15 (10.11.2020)
- Meeting #16 (17.11.2020)
- Meeting #17 (01.12.2020)
- Meeting #18 (08.12.2020)
- Meeting #19 (15.12.2020)
- Meeting #20 (22.12.2020)
- Meeting #21 (05.01.2021)
- Meeting #22 (12.01.2021)
- Meeting #23 (19.01.2021)
- CmpE 352
- CmpE 451