Ferdi: We need you! Help us maintain Ferdi 👩🏽‍💻

[vantezzen]

Some of you might have noticed that Ferdi's development has slowed down in the last few months. The reason for this is that we as Ferdi's core team currently don't have much time to invest into developing Ferdi due to jobs, university etc.

Regardless of this, Ferdi is still a highly used application by our community and by us.

We always saw Ferdi as a "community-developed" project, meaning that anyone is welcome to contribute to Ferdi if they want to.

There are different areas you might be able to help us with - don't worry, you won't necessarily need coding experience to contribute to Ferdi!

Help us develop new features for Ferdi 🚀

Our community constantly has awesome new feature that could be added to Ferdi. Even though we would like to see many of these ideas features being implemented into Ferdi, we often don't have the time to do so.

How about you look at open Feature requests or use your own ideas and implement them into Ferdi?

You can look at the "About Ferdi's code" section at the end of this issue to find out more about how you can get started hacking with Ferdi's code.

Help us fix bugs in Ferdi 🐞

To be honest to you: Ferdi is not bug-free 😢 (yet?).

You can help us squash those nasty bugs in Ferdi's code and recipes to make using Ferdi more pleasant for everybody.

There are plenty of issues with the "bug" label in our repositories. If you want to, you can take one or take one you found on your own and try to fix Ferdi's code.

You can look at the "About Ferdi's code" section at the end of this issue to find out more about how you can get started hacking with Ferdi's code.

Help us manage issues (no coding required, yay 🎉)

We get countless new issues every day on our GitHub repositories. So many in fact, that we often can't look at each of them in detail.

So why don't you look at new issues comming into our repositories, try finding our if they are duplicated of existing issues or if they might need additional information added?

Help us design Ferdi (also no coding required, amazing 🥳)

Do you have ideas on how Ferdi's or Ferdi's website design could be improved? Why don't you just create a new issue on one of our repositories to tell us about your ideas.

Other areas of Ferdi?

Do you have other ideas on how you want to help out with Ferdi? Go for it! We are happy to accept any contribution 😄

About Ferdi's code

Ferdi is built with this tech stack:

• Ferdi is writting in JavaScript
• Electron as our base
• React for most of the application
• MobX for managing stores

If you know these technologies or if you want to learn them, you can dive right into Ferdi's source code at https://github.com/getferdi/ferdi.

We are using GitHub to manage and collaborate on code. If you don't yet have experience with Git or GitHub, you can start learning about that on GitHub's Getting Started Guide.

If you still have any questions about helping out with Ferdi or you need help, feel free to comment on this issue!

We are happy to accept your Pull Requests and happy hacking!

[yashsaxena]

Hello everyone, I went through the entire gamut of ferdi like tools & I can tell you that ferdi is the best bet in many ways. I tried - tryshift ( too much private info shared), slapdash (Too expensive and very few apps - perhaps just nice colors if u want), getstation ( discontinued, just in), baasass (not for linux), onedock (no linux), rambox ( busy interface), mangeyum (discontinued).

ferdi is great in that sense! I will take this post and paste it around in places. Thank you ferdi team for building this. But perhaps, a very huge community from getstation is about to look for alternatives. I hope this is it!

[mahadevans87]

@vantezzen I have been really busy with work these days and couldn't contribute to Ferdi as much as I would like to. However, I am hoping that I should be able to start contributing again hopefully from next month onwards and start taking up some issues to start with.

[bittner]

As for development, I'm worried to not see any tests in the codebase. From the Travis builds, though, I see that there is "something" there, such a ESLint and Jest (triggered via npm run lint && npm run test; the related script entry points are configured in package.json).

But where is the test code? What do I overlook? And can we try to create some transparency with the code to understand where test coverage is low? I think, these would be important bits for both bug hunting and (technically successful) contributions.

[vantezzen]

@bittner Unfortunately Ferdi doesn't really contain any tests for its functionality. As you know, Ferdi is forked from Franz which doesn't have any tests itself - only the jest infrastructure - and so far there wasn't any further focus on developing tests for Ferdi.
This would definitely be something that should be added in the future!

Currently, the only test Ferdi actually has is this file: https://github.com/getferdi/ferdi/blob/develop/src/features/utils/FeatureStore.test.js

[bittner]

Just a heads-up: I can help triaging issues (and review merge requests), but currently I lack the permissions to add/remove/change labels and edit text there.

[vantezzen]

Great. I just tried adding you to a new team that has access to triaging issues - let me know if that works as I haven't worked with GitHub Team Managing before.

[bittner]

@vantezzen It works for adding the labels and closing issues. I still can't edit comments (to correct typos or markup), though.