|
1 | | -# Core Team \[WIP\] |
| 1 | +--- |
| 2 | +description: Who's behind Matestack? |
| 3 | +--- |
2 | 4 |
|
3 | | -## Who's behind Matestack? |
| 5 | +# Core Team |
4 | 6 |
|
5 | | -Currently it's basically just me: [Jonas](https://twitter.com/jonasjabari) I'm a passionated Ruby developer commited to put everything I have into creating sustainable Ruby gems simplifiy web software development for developers around the world. |
| 7 | +## Current core team members |
6 | 8 |
|
7 | | -I'm offering Rails/Vue.js/Matestack development/consulting services and at the same time creating open source Ruby gems. The revenue earned from the services is used to invest more time implementing and maintaining gems and documentation. |
| 9 | +Matestack heavily relies on a decent amount of time and energy following people invest into feature implementation, testing, documentation and communication without getting paid for it. Feel like [sponsoring](https://github.com/sponsors/matestack)? |
8 | 10 |
|
9 | | -## Why I do what I do |
| 11 | +### Jonas Jabari |
10 | 12 |
|
11 | | -I'm a passionated Ruby developer. In specific: I love to create web applications based on Ruby On Rails. In order to create dynamic, app-like web applications, I started to create fullblown JavaScript applications and reduced Rails to a pure JSON API. Using this common approach, compared to the classic single-repo MVC structure, I increased the complexity in my development by introducing a separate full-blown frontend framework. Implementing two separate systems \(backend-api, frontend-app\) is a pain: Two different code bases, two repositories to maintain, two different deployment schedules, two test environments, two everything...! And then add native app development for iOS and Android on top of that! Always working in a small dev team, I decided not to adopt this modern web development complexity and decided to create... `matestack-ui-core`! |
| 13 | +> **Role:** Creator of Matestack, **Job**: Self-employed software developer/founder @Matestack GmbH |
| 14 | +> |
| 15 | +> **Mail**: [email protected], **Twitter**: [@jonasjabari](https://twitter.com/JonasJabari), **Website**: [jonasjabari.dev](https://jonasjabari.dev) |
| 16 | +> |
| 17 | +> **Location**: Dresden, Germany, **Languages**: German/English |
| 18 | +> |
| 19 | +> For years Jonas struggled with increasing complexity of web app development caused by adding a JS frontend application instead of using the UI layer of Rails. He decided to fight against this complexity and created Matestack back in 2018 enabling Rails developers to implement reactive UIs in pure Ruby while enjoying highest developer happiness. |
12 | 20 |
|
13 | | -`matestack-ui-core` enables a Rails developer to create sophisticated web UIs in pure Ruby without touching JavaScript and HTML/ERB. You end up writing 50% less code while increasing productivity, maintainability and developer happiness. I love it and want to share that gift with other Ruby developers around the world. |
| 21 | +### Keith Rowell |
| 22 | + |
| 23 | +> **Role:** Core team member since 2021, **Job**: Self-employed software developer/founder @Sunstone Solutions |
| 24 | +> |
| 25 | +> **Location**: Brisbane, Australia, **Languages**: English/German |
| 26 | +> |
| 27 | +> **Twitter**: [@rowellkeith](https://twitter.com/rowellkeith) |
| 28 | +> |
| 29 | +> Early 2021 Keith discovered Matestack and was kind of hooked right away. Having created reusable UI components composed on the serverside in PHP at some point 20 years ago, the concepts and goals of Matestack felt familiar. That's the way Keith want to build software for his clients \(again\). One mail and one video call later, Keith and Jonas decided to closely work together pushing Matestack forward. |
| 30 | +
|
| 31 | +## Former core team members |
| 32 | + |
| 33 | +Following awesome people have been a very important member of the Matestack core team in the past. Thank you! |
| 34 | + |
| 35 | +### Nils Henning |
| 36 | + |
| 37 | +> **Role:** Core contributor since 2020, **Job**: Software developer @Otto Group Solution Provider \(OSP\) GmbH |
| 38 | +> |
| 39 | +> **Location**: Dresden, Germany, **Languages**: German/English |
| 40 | +> |
| 41 | +> Nils was employed at Matestack as a part-time working student from 2019 to 2020. He helped to finalize the 1.0 release and massively shaped the core rewrite leading to the 2.0 release. Additionally he wrote his master's thesis about performance optimizations of server-centric web applications \(e.g. built with Matestack\) which will result in an addition to Matestack in the future. We're grateful that Nils was part of the team! |
| 42 | +
|
| 43 | +### Pascal Wengerter |
| 44 | + |
| 45 | +> **Role:** Core contributor since 2018, **Job**: Software developer @ownCloud GmbH |
| 46 | +> |
| 47 | +> **Twitter**: [@pascalwengerter](https://twitter.com/pascalwengerter), **Website**: [pascal.rocks](https://pascal.rocks) |
| 48 | +> |
| 49 | +> **Location**: Lisbon, Portugal, **Languages**: German/English |
| 50 | +> |
| 51 | +> Pascal co-founded Basemate, a software service agency together with Jonas Jabari back in 2018. He handled clients and operations as well as maintaining and raising the community around the first versions of Matestack, which was born at Basemate back then. Without him taking care of all the small details and pushing Jonas speaking at conferences about Matestack, the project might never been able to grow until today. Thank you for being a supporter of the project until today! |
| 52 | +
|
| 53 | +## Important contributors |
| 54 | + |
| 55 | +Matestack would not be where it is right now if these mates have not helped making it better: |
| 56 | + |
| 57 | +### Sebastian Fiedlschuster & Tobias Pfeiffer |
| 58 | + |
| 59 | +> Back in 2020, Tobias and Sebastian were hired as external freelancers to help Jonas refactor the early 0.7 version of Matestack. They designed and implemented a new core architecture building the foundation of the 1.0 release. It was a pleasure to work with them and we're happy that we had a chance to use their expertise around Ruby! Hopefully our paths might cross in future again! |
14 | 60 |
|
15 | | -The main goals are: |
16 | 61 |
|
17 | | -* Reduction of complexity of modern web development, moving front and backend closer together |
18 | | -* More maintainable UI code, using a component-based structure written in Ruby |
19 | | -* Increased development speed and happiness, offering prebuilt UI-Components for typical requirements |
20 | | -* Modern, dynamic UI feeling without the need to implement a separate JavaScript Application |
21 | 62 |
|
0 commit comments