Difference between revisions of "GSoC 2017"
(Created page with "GSoC 2015 logo = How to Apply = Please see GSoC Checklist. It's important that you read about how to apply first before you talk to...")
Revision as of 16:02, 12 March 2017
How to Apply
Please see GSoC Checklist. It's important that you read about how to apply first before you talk to use so you have an idea what is going to happen.
GSoC is about getting people involved and contributing to open source over the long-term. As such, we weight our application selection process towards students that are interested in remaining involved in open source software development long after GSoC has ended.
GSoC is not a job. If you are in for easy money then this job is not for you; if you are in because you like to learn and want to participate in an open source project, the rewards are great.
We do grade submissions based on perception of the submitter's abilities to complete the task within the program timeframe, general consensus on the technical approach being proposed, and overall interest in having such modifications made to LibreCAD. Open Source is about communication; we do very much like our student's to communicate with us, hang out on the IRC channel and be active on the forum. Not only for the GSoC project but in general be actively involved in LibreCAD.
Just about every GSoC organization receives considerably more project proposals than can be accepted. Every application gets read multiple times and reviewed in detail. Of those applications, only a small subset are selected so keep in mind that the selection process is rather competitive and difficult.
Whether or not you are accepted, contributing to open source outside of GSoC is one of the main goals of the program and is the best way to be noticed and get your proposal accepted. Keep that in mind. Thanks for your interest and we look forward to working with new LibreCAD developers!
LibreCAD Project Ideas
LibreCAD is a free Open Source CAD application for Windows, Apple and Linux. Support and documentation is free from our large, dedicated community of users, contributors and developers.
REMEMBER These are ideas for GSoC, if you want to work on a other subject then any of the the below that will benefit LibreCAD, then please don't hesitate and let us know! Contact me (Ries) or Dongxu and let us know your thought's and ideas! We ar looking forward to hear how you want to improve LibreCAD!
|LibreCAD 3 UI Phase 1: After the project in 2014, LibreCAD engine is maturing, and it's reasonable to add GUI support for drawing and editing actions to start exposing it to end users. We have separated this in 2 phases
Within our current LibreCAD 3 there is a library that handles drawing of entities. This needs to be extended such that it can handle mouse/keyboard input and have the capability to create entities within our document. We require a framework that can easily be extended such that other entities can be created with or without constrains. Constrains can include must be a extendable framework
This portion doesn't require a UI with icons/buttons but a API in/around the document canvas that can handle the above such it can be included in other applications other then LibreCAD (BRL-CAD/FreeCAD etc...)
|C++,QT,UI||MEDIUM||R. van Twisk <LibreCAD@rvt.dds.nl>|
|LibreCAD 3 DXF Entities: Implement DXF entities. For LibreCAD 2 we are missing a few set of entities like Block and possible a few more. For LibreCAD 3 are looking for a person that can help implement the missing entities. Task would include
||C++||MEDIUM||R. van Twisk <LibreCAD@rvt.dds.nl>|
|LibreCAD 3 OpenGL rendering: Our current rendering engine uses Cairo to render our entities. We are looking for a person that can do a pure OpenGL implementation of it's render engine.||C++||MEDIUM||R. van Twisk <LibreCAD@rvt.dds.nl>|
HOW TO SUBMIT A PATCH?
1) To create patch first clone our repository and make a new branch
$git clone https://github.com/LibreCAD/LibreCAD.git $cd LibreCAD $git checkout -b new_branch
2) Update your code in new branch
3) Create a patch:
Assuming your changes are in new branch and didn’t yet merge it to master branch.
$git format-patch master --stdout > my_patch.patch
This will create a new file my_patch.patch with all changes from new_branch
Now, you have a patch for the fix you wrote. Send it to the maintainer of the project …
It's recommended to use github's pull requests instead of patches: Using pull requests