Hello everyone,
We are a team of 7 engineering school students interested in joining the Gladys adventure. We have been following the project for almost a month, paying particular attention to feature requests! We hope to be able to contribute to the project at our level: it’s a real opportunity for us to develop our skills and, at the same time, help evolve Gladys.
We look forward to interacting with the community!
9 Likes
Hello and welcome to the community 
Any help is welcome.
I think it’s best to check with @pierre-gilles (usually available at the start of the week) to see how you can help best.
If you need help setting up your environments or understanding the architecture, don’t hesitate.
Great! I love reading that, as someone who can’t code ^^
Welcome to the forum and, as @cicoub13 wrote, it’s probably directly with Pierre
Looks like the day is off to a good start! 
Welcome to the community of users/debuggers/developers/sometimes grumblers 
but always in good spirits! 
Happy about the boost this could bring to the project! 
If you haven’t already, you’ll find the appropriate dev docs here Mettre en place un environnement de développement sous Mac/Linux | Gladys Assistant
https://www.youtube.com/watch?v=fyKHjo3Bjas
https://www.youtube.com/watch?v=vgCN8vAOI18
And indeed the master of the keys is @pierre-gilles 
Hi @Sylvain69 and welcome to Gladys 
Out of curiosity which school are you in?
Really great to see new contributors, the project is 100% open-source (both the product and the website!) and gladly welcomes external contributions
For skill development, it’s true that doing open-source early in your career is a great way to progress quickly and have a serious project to show when looking for your first jobs.
What I recommend to have an impact on Gladys:
- Start with small features and make small PRs: it’s the best way to get started / understand how it works end-to-end, without launching into projects that last 6 months which isn’t very motivating.
- Communicate well with the community about what you’re developing
it allows fast iteration. In particular, if at some point you open PRs that touch the core / the DB, it’s important to discuss it before development starts — this avoids having to throw away code if it wasn’t the right approach - Don’t hesitate to look at PRs already merged to understand the process, see the feedback given, etc…
Anyway, welcome to Gladys 
If you have any questions, don’t hesitate to create topics on the forum.
If at any point you want to talk in real time, we can even do a call — Meet/Zoom/whatever you want.
As for me, I work part-time on Gladys (2.5 days/week), usually on Monday, Thursday and Friday, but I reply to messages once a day.
2 Likes
Thanks everyone for the warm welcome!
To answer your question @pierre-gilles, we come from IMT Atlantique. We are all in the specialization: Collaborative Software Development!
For now we are indeed trying to « get our feet wet » on small features to get familiar with the development environment and to really understand how to achieve our goals. Having already scoured GitHub, we more or less see the prerequisites
However, in the long run, we plan to try to implement a bigger feature so we can truly leverage what we’ve learned about collaborative development — we had seen a request for an event log!
If we have questions and/or if we’d like to chat I’ll send you a message 
1 Like
Ok cool I didn’t know IMT Atlantique! I’m from UTC myself (I graduated in 2018)
Totally! If I can give you one piece of advice for big features, it would be to really not skimp on the « design » phase before diving into the
Welcome everyone!
What more can I say!
Welcome!
It’s a pleasure to read, indeed 
Also @pierre-gilles just did a live coding session covering the whole process of an integration, it’s available on the project’s YouTube channel. It should really help you!