|
1 | | ---- |
2 | | -title: "Google Summer of Code- Week 4th & 7th Midterm Evaluation" |
3 | | -slug: google-summer-of-code-week-4th-and-7th-midterm-evaluation |
4 | | -date: 2023-07-25 |
5 | | -authors: ["Ankit Kumar"] |
6 | | -tags: [google summer of code, gsoc, open-source open-sciencelab] |
7 | | -categories: [open-source, gsoc] |
8 | | -description: | |
9 | | - In this article, I will share the progress for Week 4th week to 7th week for my |
10 | | - contribution to Open-science labs as a part of Google Summer of Code 2023. |
11 | | -thumbnail: "/GSoC-Vertical.png" |
12 | | ---- |
| 1 | +# Google Summer of Code- Week 4th & 7th Midterm Evaluation |
| 2 | +Ankit Kumar |
| 3 | +2023-07-25 |
13 | 4 |
|
14 | 5 | ## Google Summer of Code- Week 4th & 7th Midterm Evaluation |
15 | 6 |
|
16 | | -In this article, I will share the progress for Week 4th week to 7th week for my |
17 | | -contribution to Open-science labs as a part of Google Summer of Code 2023. |
| 7 | +In this article, I will share the progress for Week 4th week to 7th week |
| 8 | +for my contribution to Open-science labs as a part of Google Summer of |
| 9 | +Code 2023. |
18 | 10 |
|
19 | | - <img src="GSoC-Vertical.png" width="400"> |
| 11 | +<img src="GSoC-Vertical.png" width="400"> |
20 | 12 |
|
21 | | -As my Google Summer of Code journey continued, I found myself faced with an |
22 | | -exciting yet daunting task: implementing a whole new build-system as an option |
23 | | -for templates in the esteemed Open-Science Lab. This endeavor demanded |
24 | | -meticulous planning, unwavering dedication, and the exploration of various |
25 | | -build-systems, including Maturin, Hatchling, Scikit-build, and `pybuild11`. |
| 13 | +As my Google Summer of Code journey continued, I found myself faced with |
| 14 | +an exciting yet daunting task: implementing a whole new build-system as |
| 15 | +an option for templates in the esteemed Open-Science Lab. This endeavor |
| 16 | +demanded meticulous planning, unwavering dedication, and the exploration |
| 17 | +of various build-systems, including Maturin, Hatchling, Scikit-build, |
| 18 | +and `pybuild11`. |
26 | 19 |
|
27 | | -In this period, I started working on to add support for `Maturin` build-system. |
| 20 | +In this period, I started working on to add support for `Maturin` |
| 21 | +build-system. |
28 | 22 |
|
29 | 23 | ### Maturin |
30 | 24 |
|
31 | | -[**Maturin**]() was the first build-system I explored. Its unique approach of |
32 | | -building Python bindings for Rust libraries intrigued me, and I wondered if it |
33 | | -could provide a novel solution to the lab's needs. The seamless blending of |
34 | | -Python and Rust offered the potential for unparalleled performance and memory |
35 | | -efficiency in research projects. However, I faced a steep learning curve to |
36 | | -master the intricacies of Rust and its integration with Python. Overcoming these |
37 | | -challenges was a significant achievement, and I managed to create a functional |
38 | | -prototype that demonstrated Maturin's potential to revolutionize the |
39 | | -Open-Science Lab's workflow. My contribution to this issue is |
| 25 | +[**Maturin**]() was the first build-system I explored. Its unique |
| 26 | +approach of building Python bindings for Rust libraries intrigued me, |
| 27 | +and I wondered if it could provide a novel solution to the lab’s needs. |
| 28 | +The seamless blending of Python and Rust offered the potential for |
| 29 | +unparalleled performance and memory efficiency in research projects. |
| 30 | +However, I faced a steep learning curve to master the intricacies of |
| 31 | +Rust and its integration with Python. Overcoming these challenges was a |
| 32 | +significant achievement, and I managed to create a functional prototype |
| 33 | +that demonstrated Maturin’s potential to revolutionize the Open-Science |
| 34 | +Lab’s workflow. My contribution to this issue is |
40 | 35 | [here](https://github.com/osl-incubator/scicookie/pull/152) |
41 | 36 |
|
42 | | -After merging this pull request, I started to add support for `Hatchling` |
43 | | -build-system. |
| 37 | +After merging this pull request, I started to add support for |
| 38 | +`Hatchling` build-system. |
44 | 39 |
|
45 | 40 | ### Hatchling |
46 | 41 |
|
47 | | -[**Hatchling**]() known for its user-friendly nature, was my next target. It |
48 | | -promised to simplify the build and deployment processes, which could be |
49 | | -particularly beneficial for newcomers to the lab and projects with |
50 | | -straightforward requirements. Integrating Hatchling into the lab's ecosystem |
51 | | -required thorough documentation and integration tests to ensure its smooth |
52 | | -adoption. Overcoming initial hurdles, I was elated to see the positive response |
53 | | -from the lab's community as they began adopting Hatchling for their projects. My |
54 | | -contribution to this issue is |
55 | | -[here](https://github.com/osl-incubator/scicookie/pull/144) |
| 42 | +[**Hatchling**]() known for its user-friendly nature, was my next |
| 43 | +target. It promised to simplify the build and deployment processes, |
| 44 | +which could be particularly beneficial for newcomers to the lab and |
| 45 | +projects with straightforward requirements. Integrating Hatchling into |
| 46 | +the lab’s ecosystem required thorough documentation and integration |
| 47 | +tests to ensure its smooth adoption. Overcoming initial hurdles, I was |
| 48 | +elated to see the positive response from the lab’s community as they |
| 49 | +began adopting Hatchling for their projects. My contribution to this |
| 50 | +issue is [here](https://github.com/osl-incubator/scicookie/pull/144) |
56 | 51 |
|
57 | 52 | After completetion of this issue, I jumped to a task to add support for |
58 | 53 | `Scikit-Build-Core`. |
59 | 54 |
|
60 | 55 | ### Scikit-build-core |
61 | 56 |
|
62 | | -[**Scikit-build-core**]() a cross-platform build-system, offered a robust option |
63 | | -for integrating CPython extensions. While challenging to implement, I recognized |
64 | | -its potential to support projects with complex native code dependencies. My |
65 | | -experience with Scikit-build exposed me to advanced build and packaging |
66 | | -concepts, and I was thrilled to see it complementing the existing build-systems |
67 | | -in the lab, catering to a broader range of projects. My contribution to this |
68 | | -issue is [here](https://github.com/osl-incubator/scicookie/pull/161) |
| 57 | +[**Scikit-build-core**]() a cross-platform build-system, offered a |
| 58 | +robust option for integrating CPython extensions. While challenging to |
| 59 | +implement, I recognized its potential to support projects with complex |
| 60 | +native code dependencies. My experience with Scikit-build exposed me to |
| 61 | +advanced build and packaging concepts, and I was thrilled to see it |
| 62 | +complementing the existing build-systems in the lab, catering to a |
| 63 | +broader range of projects. My contribution to this issue is |
| 64 | +[here](https://github.com/osl-incubator/scicookie/pull/161) |
69 | 65 |
|
70 | 66 | ### Conclusions |
71 | 67 |
|
72 | 68 | In conclusion, my Google Summer of Code experience with implementing new |
73 | | -build-systems for the Open-Science Lab was a transformative journey. Overcoming |
74 | | -hurdles with Maturin, embracing user-friendliness with Hatchling, exploring the |
75 | | -potential of Scikit-build.I realized the importance of innovation and |
76 | | -adaptability in the world of open-source development. This experience has not |
77 | | -only enriched my technical skills but also instilled in me a passion for |
78 | | -contributing to projects that drive positive change in the world of scientific |
79 | | -research. As I look to the future, I am excited to continue this journey, |
80 | | -collaborating with the open-source community to create solutions that empower |
81 | | -researchers and advance the boundaries of knowledge. |
| 69 | +build-systems for the Open-Science Lab was a transformative journey. |
| 70 | +Overcoming hurdles with Maturin, embracing user-friendliness with |
| 71 | +Hatchling, exploring the potential of Scikit-build.I realized the |
| 72 | +importance of innovation and adaptability in the world of open-source |
| 73 | +development. This experience has not only enriched my technical skills |
| 74 | +but also instilled in me a passion for contributing to projects that |
| 75 | +drive positive change in the world of scientific research. As I look to |
| 76 | +the future, I am excited to continue this journey, collaborating with |
| 77 | +the open-source community to create solutions that empower researchers |
| 78 | +and advance the boundaries of knowledge. |
82 | 79 |
|
83 | 80 | You can read my previous blog [here](https://medium.com/@ayeankit) |
84 | 81 |
|
|
0 commit comments