Editing User:KeshaSShah/GSoC13/Priority2
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 63: | Line 63: | ||
***In this issue, except for two files, there is almost similar set of files in src/fedex_plus and src/clstepcore from which the other copy need to be kept and the first one should be removed carefully such that the build system is not broken at any point. | ***In this issue, except for two files, there is almost similar set of files in src/fedex_plus and src/clstepcore from which the other copy need to be kept and the first one should be removed carefully such that the build system is not broken at any point. | ||
***I have down the differences in that files using MELD tool. Now decission has to be taken to untangle calls, replace them, move them, delete them or refactor them in the clstepcore. | ***I have down the differences in that files using MELD tool. Now decission has to be taken to untangle calls, replace them, move them, delete them or refactor them in the clstepcore. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==IRC bot== | ==IRC bot== | ||
Line 92: | Line 86: | ||
*It is not just about 3 months of GSoC, I want to be committed with this code for years. I will keep contributing even after that as thing is an endless job-new codes are definitely going to be added and that in-turn would also require code reducing and refactoring. Moreover, by the end of 3 months, I believe, I would have hacked the entire source code so well that I can work on other projects also and contribute in making BRD-CAL more awesome! | *It is not just about 3 months of GSoC, I want to be committed with this code for years. I will keep contributing even after that as thing is an endless job-new codes are definitely going to be added and that in-turn would also require code reducing and refactoring. Moreover, by the end of 3 months, I believe, I would have hacked the entire source code so well that I can work on other projects also and contribute in making BRD-CAL more awesome! | ||
− | |||
− | |||
− | |||
=Links to any code or algorithms you intend to use= | =Links to any code or algorithms you intend to use= | ||
Line 138: | Line 129: | ||
=Time availability:= | =Time availability:= | ||
*My availability for the project would be possible for the specific GSoC period as I would be having my summer break from 1st May to last week of July. Since in August the new semester would have just begun, I would be able to spare enough time to work on the project as I am not involved in anything else which would be a hindrance. | *My availability for the project would be possible for the specific GSoC period as I would be having my summer break from 1st May to last week of July. Since in August the new semester would have just begun, I would be able to spare enough time to work on the project as I am not involved in anything else which would be a hindrance. | ||
− | |||
*I will also work on Sundays if needed needed to cope-up in-case if I am unable to meet with my development schedule due to unavoidable circumstances. | *I will also work on Sundays if needed needed to cope-up in-case if I am unable to meet with my development schedule due to unavoidable circumstances. | ||
− | + | Even after GSoC period I will get enough time to continue contributing to BRD-CAL. | |
=Development schedule:= | =Development schedule:= | ||
Line 152: | Line 142: | ||
/* GSoC period Starts */ | /* GSoC period Starts */ | ||
− | + | *May 21- June 14 : (PHASE I: Analysis and Design Period) | |
− | |||
− | |||
** Getting familiar with the code | ** Getting familiar with the code | ||
** Examine the existing STEPcode repo at https://github.com/stepcode/stepcode and create a list of tasks that need to be done. | ** Examine the existing STEPcode repo at https://github.com/stepcode/stepcode and create a list of tasks that need to be done. | ||
− | |||
** At the end of this period : A finalized plan to proceed for the development of the library. | ** At the end of this period : A finalized plan to proceed for the development of the library. | ||
− | + | *June 15 – August 15 (PHASE II: Development Phase) | |
− | + | ** June 15 – July 7 - Refactoring and Coding begins and testing it with step-g convertor. | |
− | ** June | + | ** July 7 – July 14 - bugs fixing, review to be ready for submitting. |
− | ** July | + | ** July 15 -July 21 -Organizing source code documentation in the step libraries to work well with doxygen. |
− | ** July | + | ** July 15 –24 - submitting and some more review and updating if it is necessary and making mid-term report. |
− | + | ** July 25 – August 15 - modifying other files in the source code that gets afftected due to changes in STEP library. | |
− | ** | + | ** At the end of this period : A complete library with all functionalities and all of them having been tested at unit level. |
− | |||
− | ** | ||
− | ** At the end of this period : | ||
− | + | *August 16- September 27 (PHASE III :Testing, Cleaning and Wrapping Up) | |
− | + | ** August 16 – August 20 - System Level testing for library at multiple platforms. | |
− | ** August | + | ** August 21-September 9 - bugs fixing, review to be ready for submitting the final result. |
− | ** September 9 | ||
** September 10- 22 -Pencils down ,Code clean up , Documentation (wiki pages) | ** September 10- 22 -Pencils down ,Code clean up , Documentation (wiki pages) | ||
** Sept. 23 – 27- Final evaluation and Submit code to Google | ** Sept. 23 – 27- Final evaluation and Submit code to Google | ||
** At the end of this period: Deliverable mentioned would be successfully be completed. | ** At the end of this period: Deliverable mentioned would be successfully be completed. | ||
− | |||
=My preparation for the Project:= | =My preparation for the Project:= | ||
*Joined IRC channel #brlcad | *Joined IRC channel #brlcad |