Welcome! - Introduce yourself

[driesvints]

👋 Hey everyone,

Welcome to the Laravel discussions section. I felt that it might be cool to kick-off this section with a thread where you can introduce yourself. I'll start off!

I'm Dries, one of the core maintainers of Laravel where I maintain most of the first party open source libraries. I also maintain Laravel.io which is the Laravel community portal website.

In my free time I work on various open source projects and tweet from my twitter.

Who are you? Let us know in a comment below 👇

[ericlbarnes]

Hi Dries,

I'm Eric Barnes and I've been using Laravel since before the dragon was removed.

[themsaid]

Issue resolved. The answer is Eric.

[IamSwap]

Hello everyone,

I am Swapnil Bhavsar, A full-stack developer from India!

I blog about Laravel, Vue.js & other development topics at swapnil.dev.

[themsaid]

Hello Swapnil 👋

[IamSwap]

Hi! Nice to see you guys around here!

[stefanbauer]

Hi,

I'm Stefan, none of the core maintainers of Laravel. I'm from Germany, more precisely Munich. I am the owner of PingPing.io. I am a huge fan of Laravel, Laracon Visitor, and work with @bobbybouwmann – the number 1 on Laracasts - on a new book called Laravel Secrets.

I blog more or less regularly on my blog and you can find me on Twitter as well.

[TheBlckbird]

oh hi, Deutscher

[awebartisan]

Hey everyone 👋

I am Zubair Mohsin, based in Pakistan 🇵🇰

Working on Laravel everyday, every night. I mostly build Shopify apps with Laravel on the Backend and React on front-end. So I guess that makes me Full-Stack 🤷🏻‍♂️

I tweet about Laravel and Shopify App Development stuff. @Zubairmohsin33

Looking forward to useful discussions here 🙏🏼

[nmokkenstorm]

Definately a useful combination for Full Stack work on Shopify apps 💪

[reinink]

Hey there! I am Jonathan Reinink, full stack developer from Canada. 👋

I've contributed to Laravel in the past, mostly stuff related to Eloquent and the query builder.

Projects of mine include Inertia.js, Tailwind CSS, Glide and recently a course on Laravel database performance called Eloquent Performance Patterns.

[Cannonb4ll]

InertiaJS 💙

[IamSwap]

Eagerly waiting for your Eloquent performance course!

[jjsquady]

Inertiajs 💚. Using it in my projects, thanks @reinink .

[mvdnbrk]

Cool! A worthy successor of the laravel/ideas repo 🎉

I am Mark, developer from The Netherlands.

Contributed to the Laravel framework itself, Nova and other packages in the eco system.
Maintaining the laravel-mix.com website.

[imliam]

Hey 👋 I'm Liam.

I've got a couple of open source Laravel packages I maintain and share some tips about Laravel I've figured out on my site and Twitter.

First picked up Laravel on the tail end of v4, and loved it ever since. I haven't really worked with Laravel in my day job for a couple of years now, but love the framework and community too much I can't get away. Still using Laravel for a bunch of side-projects at least 🎉

[ryangjchandler]

Funny seeing you here!

[imliam]

How ya doin', Ryan?!

[Cannonb4ll]

Hi there :)

[ahinkle]

Hey Liam! Thanks for all of your community help!

[ryangjchandler]

Hello, World!

I'm Ryan. I'm a Laravel and JavaScript developer who has been working with Laravel since the late days of 4.2.

I've recently started blogging and building a following in the community, alongside some of my other work on the Alpine.js team.

[m1guelpf]

Hey there!

I'm Miguel Piedrafita, I'm 18 and I make stuff, mostly with Laravel.

[Cannonb4ll]

Hey! 👏

I'm Dennis, Laravel developer from The Netherlands. I have a few awesome Laravel articles on medium

Working a lot with InertiaJS on several projects 🚀

Have contributed a few times to this repository and planning to do some more. 👀 (Especially Horizon)

[KennedyTedesco]

Hi, there! I'm Kennedy, a web developer from 🇧🇷

I've contributed to Laravel ❤️ in the past, started using it since the beginning.

[themsaid]

Hey! Man, you added whereIn() to collections. A legend.

[KennedyTedesco]

@themsaid I wish I have such a good memory like yours! :P Thank you so much for your kind words. You truly inspire all of us.

@alfaVeteran ❤️

[themsaid]

When I first started contributing to Laravel I watched your PRs closely to learn how to open a PR, add commits, etc... Thanks for everything ❤️

[setkyar]

Hello everyone! I am Set Kyar Wa Lar which means Universe. I am a Web Developer from Myanmar.

I use Laravel since version 3. I am writing Laravel articles in Burmese at https://laravelmyanmar.com. Last time Laravel Myanmar use to translate Laravel documentation and it's stopped for a while. I hope to start back soon.

[bosunski]

Hi there!
I'm Bosun. I'm a PHP and Javascript Developer from Nigeria. I'm a fan of this community and the amazing works being done!
Though I've not contributed to Laravel before, I work with Laravel every day and one of the projects I made recently is PHPSandbox.

[alprnkeskekoglu]

Hi! 👍

I'm Alperen, I'm form Turkey. I have been using Laravel for 2 years and i have only one package. Maybe there will be more in the future.

[dillingham]

I'm Brian, freelancer. Built some Nova packages. Working on other open source projects soon to be released. Here's my twitter

[sixtusagbo]

Hi, I'm Sixtus Agbo Miracle from Nigeria. I am a Software Engineer. I've used Laravel for about 3 years now and I really like the framework.

[shaedrich]

Hey, I'm Sebastian from Germany 👋🏻

Despite the elitist contribution gatekeeping and poor communication, I love Laravel's elegance (or eloquence). Sorry for bringing down the mood, but this is how I was made feel. But that doesn't apply to the community as such 😃

But as every dark cloud has a silver lining, I started the Laravel Working Group.

[Sophist-UK]

My advice would be to:

1. Create a discussion, documenting your vision and seeing whether people agree or disagree with it or have suggested improvements. This will allow people to start to contribute and give you an idea of whether you are on the right path or not, and it will ensure that the concept is sufficiently well documented that it is easily understandable.

2. See what people think about whether these should be packages or provided as part of the core Laravel code. To some extent this will depend on whether it can realistically be provided as a package or whether it would really make more sense to be provided via a PR to core code. I know that Taylor is reluctant to merge non-core code in order to avoid code which will only be used by a minority and to avoid the code base growing too far, so a package is perhaps a preferred way forward anyway, but for example if we are considering macros where they don't exist at present, you may need to have macro support in core Laravel and specific macros in a package.

3. If the discussions suggest that there is reasonably widespread interest, then you can try to gather a team and see what people are interested in and how best to split up the work.

4. Set some technical standards - I'll throw in test-driven development as a good starter.

[shaedrich]

Thanks for your advise and even though I'm not against using Laravel's discussions per se, it drives the respective topic away from the GitLab repository it belongs to if it already has one.

See what people think about whether these should be packages or provided as part of the core Laravel code.

For Laravel, I learned the hard way, that in 99 % of the cases, it's irrelevant what "people" think in terms of it being "a package or part of the core" since Taylor will close the PR resulting from that discussion with an answer that can mean anything or nothing but sure is just copy-pasted. And this is what I initially meant by "elitist contribution gatekeeping and poor communication". It's not that I don't understand, that not everything can be part of the core and the upcoming release. It's just that Taylor doesn't bother to communicate that clearly. Sometimes, a change can't be part of the upcoming version but might come in the subsequent one. A "sorry, we aren't accepting any new changes for the upcoming version anymore. But feel free to re-submit the exact changes against the base branch 13.x and I'll be happy to review them." See? So much nicer and more transparent.

If the discussions suggest that there is reasonably widespread interest, then you can try to gather a team and see what people are interested in and how best to split up the work.

And this is exactly, why I wouldn't waste time beforehand to do all these changes to just have them rejected again without a clear explanation. If I knew beforehand what to do to make it right, it would spare both me and Taylor time and maybe I didn't need to do these changes at all since they are not wanted in the core at all.

I'll throw in test-driven development as a good starter.

Yeah, TDD is great 👍🏻 I'll see if I can fit that in.

[Sophist-UK]

I also personally wish that Taylor was more willing seriously to consider PRs and to be more forthcoming about what he will and won't accept and why, and give better feedback when he rejects PRs BUT I also understand that projects like Laravel need a decision maker, and regardless of whether I agree or disagree with his decisions, it is IMO much much better to have a strong leadership and decisive decisions than to have weak or non-existent leadership. And as you have alluded, it is this lack of information and the time people waste as a consequence that annoys me most.

That said, in the 6 months or more since you started LWG you have not gained a lot of traction. The discussions here do get a lot more visibility than GitLab, which is IMO another reason to start them off here.

I will also add that I am in the early stages of a MAJOR (and if I knew how to make that bigger and red in Markdown I would) open-source project that is so big it can only ever succeed with a team and I believe so beneficial that if I ever gather interest in it (which IMO means writing the core kernel and producing a Proof of Concept) I will get volunteers. So do understand both your challenges, and those of Taylor. I am going to try to dedicate some serious time to creating the core core kernel in the coming months, and then we will see.

[shaedrich]

Glad, we're on the same page. Took a while for me to realize that you're not making fun of me afaik, but rather that we might have a little different mindsets as you seem to be more marketing-savvy.

Yeah, that's the problem with spare time projects: I try to take some time for them, but that works sometimes better, sometimes not that good 😅 But there should be some progress in the near future, I hope.

I keep my fingers crossed for your project to be a success :)

[Sophist-UK]

I was making fun, but not making fun of you so much as making fun of the difficulties of getting help.

[discollizard]

Hello people!

I'm Álvaro. I'm a programmer from Brazil who works with a lot of PHP and Laravel on my job and my side projects. Nice to meet you all!

[murraygunn]

Hi. I'm Murray, an Australian living in Colombia. I teach technology to underprivileged kids and am dabbling in a few projects that now all use laravel.

[HOTASFFOR40]

Hi, I'm Angel from Michigan and I have no clue what I am doing~LOL

[zaghadon]

Hi Angel, you're welcome 🤗. I guess it'll help if you know that all of us don't know what we're doing too. Just keep at it and solve one problem at a time 🥂

[ghanu119]

Hi Artisans,

I am Ghanshyam Ashra. I am from India.
I made a package for Laravel, Find In Set Relation.
And also create other components for JS and useful single script file.
I use Laravel from Laravel 5.2.
I am a full stack web developer with Laravel ( PHP ) and VueJS.

[abrzzzz]

Hi, my name is Ali Barzegar, I'm from Iran
BackEnd developer specially PHP, I know a bit Front-End though,

I also built WPINT, A WordPress plugin framework based on the Laravel's core concepts which helps developers massively on their path :)

This is my LinkedIn profile

[shaedrich]

Sounds like a great idea! 👍🏻 Is there a reason, you put the "tags" in your README.md and not as topics?

[zaghadon]

Not gonna lie, this is massively nice 🔥

[abrzzzz]

Sounds like a great idea! 👍🏻 Is there a reason, you put the "tags" in your README.md and not as topics?

Thanks, There is no reason, the latest tag will be shown in the README.md file and topics will be added

[abrzzzz]

Not gonna lie, this is massively nice 🔥

Thank you

[alirezadp10]

👋Hi Deris
I'm Ali
I'm really getting into contributing to the open-source community, especially in the Laravel framework.
Hope I can help. ❤️

[CodingwithRK]

👋Hi Deris
I'm Raj Kumar (CodingwithRK)
I'm a big fan and most adducted to Laravel, I've been using it for 1 year but I am learning more.

codingwithrk.com This is my website built in Laravel, Livewire and also I am implementing the Filament Admin Panel

Thank you ❤️ for this awesome framework in the PHP environment, I am eagerly waiting for NativePHP.

[elbaable]

Hello guys

I am Trayvon from San Francisco.

I am a Laravel developer(+5 years' experience).

Great to be one of you!

[Mrbeyond]

Hi!

I am Beyond from 🇳🇬

I have been using Laravel extensively since last quarter of 2019

I am honoured to be here.

[gavinsykes]

Greetings!

Gavin here from good old Blighty 🇬🇧.

I'm a full-stack developer by trade and just feel at-home in the back-end. Relatively new to Laravel still but always keen to jump right in to see what can be built. React is my front-end jam.

Love to travel, see new places, try different foods, learn new languages - currently on 3 besides English!

[bhojkamal]

Hi and Namaste 🙏,
I am Bhoj Kamal, full-stack web developer, have been working in php and laravel application for past 6 years and in frontend js, scss, html5, tailwind css, bootstrap with modern js framework like vue, react, next.js for past 4 years and in devops for the past couple of years.

I am looking for new project to work on, if you have let's work together.

[joy2362]

Hi!!
I'm Abdullah Zahid, a back-end developer based in Bangladesh. I'm excited to jump into contributing to the Laravel community!

[tkoop]

Hi everyone. I'm Tim. I'm a full stack developer. We have been using Laravel for a few years. It's great, of course.