Skip to content

Commit

Permalink
Update 2023-12-11-hacktoberfest.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ymougenel authored Apr 11, 2024
1 parent 478abd0 commit e1994fe
Showing 1 changed file with 12 additions and 7 deletions.
19 changes: 12 additions & 7 deletions _posts/2023-12-11-hacktoberfest.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ I joined the 2023 Hacktoberfest event, and managed to end up with 3 main contrib
<img src="../assets/slack.jpg" width="21%">
<img src="../assets/springboot.png" width="21%">
<br>
It has been some time since I last took part in the Hacktoberfest open-source events.
This year, I came in with a handful of goals and minimal time to spare, but here's how it all played out:
It has been some time since I last took part in the Hacktoberfest open-source events.
This year, I came in with a handful of goals and minimal time to spare, and here's how it all played out:
<!--more-->

# The event
[Hacktoberfest](https://hacktoberfest.com/) happens every year in October, it is a free event which encourages open-source contribution.
[Hacktoberfest](https://hacktoberfest.com/) happens every year in October, it is a free event which encourages open-source contribution.
I took part in the event in 2017 and wanted to give it another shot this year.

# Goals for this year
Expand All @@ -28,6 +28,8 @@ As I started a new job on September, I had limited time for this October challen


I did some preparation for the event by searching open-sourced projects on Github & Gitlab (both platforms provide Hacktoberfest Topics).


Here are the final contributions:

# Jenkins __Slack-Plugin__: a pipeline status error
Expand All @@ -41,24 +43,27 @@ I immediately got inspired: I had already worked on Jenkins plugins before, and
2. Isolate the concerned code base . Jenkins' plugins usually works through steps. The faulty steps had to identified and fixed.
3. Testing: I manually tested few scenarios, and added **unit tests** to avoid any further regressions.

| [Github MR](https://github.com/jenkinsci/slack-plugin/pull/929) | status: accepted & closed | time spent: ~4 hours |
| [Github MR](https://github.com/jenkinsci/slack-plugin/pull/929) &ensp;&ensp;&ensp; | status: accepted & closed &ensp;&ensp;&ensp; | time spent: ~4 hours |

# Spring-io initializr: Synchronizing the zip file name with the artefact ID
As I participated in an open-source coding night at my company [Takima](https://www.takima.fr/), I encountered minor issues related to the Spring Framework.
[This one issue](https://github.com/spring-io/start.spring.io/issues/163) in particular caught my eye: the zip name generated by Spring Initializr sometimes didn't match the project artefact ID.

[This one issue](https://github.com/spring-io/start.spring.io/issues/163) in particular caught my eye: the zip name generated by Spring Initializr sometimes didn't match the project artefact ID.

After compiling a huge codebase (both start.spring.io and Initializr), fixing it implied a small refactoring in order to synchronize the naming process for both the artefactId and the zip file.

| [Github MR](https://github.com/spring-io/initializr/pull/1492) | status: accepted & closed | time spent: ~2 hours |
| [Github MR](https://github.com/spring-io/initializr/pull/1492) &ensp;&ensp;&ensp; | status: accepted & closed &ensp;&ensp;&ensp; | time spent: ~2 hours |

# Text-finder Jenkins plugin, a translation contribution that became a fix
Back in the old days, I started my open-source journey by doing some Jenkins plugin French translations.
Due to the lack of time, I decided that my last MR would be i18n and found an interesting Jenkins plugin already in English and Japanese, but not in French.

However, during the translation into French, I noticed that the plugin's folder structure for translations was incorrect, resulting in most of the Japanese translations being ignored.

I reorganized the structure to ensure that all translations were properly incorporated.
It ended up taking much more time than anticipated (finding the correct structure and testing for all languages), but it ultimately proved successful.

| [Github MR](https://github.com/jenkinsci/text-finder-plugin/pull/206) | status: accepted & closed | time spent: ~3 hours |
| [Github MR](https://github.com/jenkinsci/text-finder-plugin/pull/206) &ensp;&ensp;&ensp; | status: accepted & closed &ensp;&ensp;&ensp; | time spent: ~3 hours |

# Global summary

Expand Down

0 comments on commit e1994fe

Please sign in to comment.