How Laravel Team Works

hey everyone welcome back to another episode of tech talks with santosh and today we have a really special guest stress with us and dress works as a developer at laravel and we are going to talk more into how laravel team works today so thanks a lot address for joining us thanks santosh for having me glad to be here yeah yeah so just to give you a small intro about dress uh he's an uh github star and he has been working with laravel's team so uh what i have heard that he there are just two developers as as part of laravel team and he's the one so uh over to you this i mean you can just introduce uh about yourself so please go ahead yeah uh uh i'm therese i'm uh from antwerp belgium um and i've been a member at the level team for i think like two and a half years a little bit more than that uh since now since 2018 um and back uh in the day when i was first hired taylor hired me to mainly work on the open source repositories of laravel to maintain the issues uh keep an eye on the pull requests and make sure that everything for our open source libraries and our main first party libraries uh goes well and that bugs are resolved and people are helped and stuff like that so that's my main role at laravel um we also discuss about um internally about new products uh and and such but my colleagues are mainly on our uh products uh at laravel like forge like embroider and uh and such yeah that's great uh yeah so as we said we are going to talk a little bit about how the team actually works at laravel so first let's start with how how actually uh once you get the issues right so how you address those issues uh well uh like every single day um i sort of uh try to work the same i work four days in a week for level so not on wednesdays but on mondays tuesdays thursdays and fridays and usually i start out with github notifications so that's like a big part of my daily job like going through the notifications that came in for open source repos and like tackling them one by one on my youtube channel i have a video of my own like how i do that specifically so you can always check that out if you want but what i uh mainly try to do is like for every single repo i go through the issues like look at which ones are the bugs label them as box which one are the feature requests try to label them as enhancements and then try to tackle as much of the low hanging fruit as possible so the bugs that are easily solved the ones that are a bit harder to solve um they'll move to the afternoon or to a later date maybe if like somebody else can help us out with those as well and then like usually that's in like during the mornings when i go through the notifications and usually uh we also have like our own specific tasks which we work on they could be new features for our libraries or specific projects which we work on and in the afternoons i usually work on those if time permits it there's a special day on tuesday on tuesday i do our releases or weekly releases of our software uh people will probably see my tweets every tuesday where i like announced the the new versions of the libraries and those are always done on a tuesday so people know that that's like the fixed schedule when they can expect new releases with uh bug fixes with new features and uh whatever got merged in that that week uh in the meantime well that's like mostly like the schedule i work on the we also have like a specific workflow at laravel which comes in like a work cycle and we used to do work cycles of six weeks since recently and more recently we switched over to a work cycle which starts at the beginning of each month and the end of each month and within that work cycle we have some specific tasks planned which we want to tackle so for example i'm currently working on the new cashier version 13 major release and i'm planning to wrap that up this month i'm almost nearly there and then next month starts a new cycle with new tasks and all of my colleagues also like have their specific tasks within that cycle that's like in a nutshell at uh how i work each day for later hall yeah i mean uh so uh how about the community support so for driving the issues do you also get the support from community or anyone else who is helping you or you are just all alone yeah definitely like i'm the main person at laravel like keeping an eye on the open source repositories but of course we have a very large community behind us as well which are very helpful uh we're very grateful for the community helping us out so we usually we have lots of eyes on the pull requests that are coming in so people can respond to them like give advice give feedback to people sending in those pull requests and also on issues like i try to keep a short uh tap like i refresh my notifications uh a lot during the day so i'm like fairly ahead of uh when someone comes in so i can give an answer very quickly but there's also a lot of people watching our repo so uh there's usually some specific people also per repository that's also something that we're seeing so like you for example have some people who are very involved with passport you have some people who are very involved with cashier um so we have specific uh community members helping us out on the different projects and those are very helpful uh they take out um quite a bit of work for us as well yeah that's nice yeah so uh i i just have another question from uh the chat we just said how about release cycles i mean you said every tuesday so it's like weekly releases which you do yeah so for more most of our uh open source repos we have weekly release cycles depending if we have new features or so uh before i start saying that we have a specific versioning scheme that we use it's the most common versioning scheme used in open source landscape i think it's called semantic version and depending on new features or bug fixes we do a minor release or batch release each week and sometimes when there's a new uh major update for a library we do a major release so for example we i'm now working on the new cashier version 13 release so that's probably expected soon depending how much testing time we'll need for the the final release for the framework there's a sort of a different cycle for the main level framework we also do minor and batch releases depending on there's new features or not but for the major release which probably has breaking changes and larger new features we do that every single year from now on we used to do a major release every six months but we sort of noticed that we weren't getting that much new features in the major versions anymore the framework was sort of like maturing as a whole so it wasn't really needed to do it every half year anymore so we switched to a yearly cycle now at the moment level 9 the next major release is expected in september so that's the next time we'll probably do a new major release um but for the libraries we it depends like we don't have a fixed yearly schedule or something it depends if like we have enough new stuff in a major release then it's probably wanted to do do one [Music] uh yeah about the uh feature request right so you said you have framework laravel framework and then you have which are the libraries so how what is the i mean in case someone requests for a new feature what is the process for both okay uh so it's again a little bit different between the framework and our open source libraries for the framework we have a dedicated repository for new ids for the framework because um obviously we have a large community and there's lots of people who have different kinds of ideas for the framework which is great we have had a lot of great ideas for the framework already lots of great community pull requests that have been contributed but because we want to like um keep a good overview of the bugs we still need to fix our main issue tracker for the framework repository is dedicated only for bugs and not for support or for new features so we have a different repository specifically for feature requests for the framework that's called uh laravel slash ideas and the issue tracker there it's like it's not really monitored or anything dedicatedly but we usually uh sometimes take a peek in there to see if there's like new fresh good ideas in there which we can use for the next major version uh like if there's things which have been upvoted a lot so we can sort through those issues to see if there's new new things and when that's uh done we sometimes tackle them ourselves but there's also a lot of bull requests being sent in by community members um it sometimes depends like if we want to take on the burden of maintaining the things that people send in uh for ourselves because every single line of code that goes into the framework we of course have to maintain ourselves and we don't always accept uh every single pull requests um we usually uh encourage like if it's wanted that people release packages like different libraries which integrate with the framework for the specific feature that they request but sometimes we also unfortunately have to decline some pull requests which like doesn't really like in our vision doesn't really like are wanted within the framework or simply because we don't want to maintain the code ourselves for the first party libraries it's again a little bit different so we do use the issue trackers for tracking feature requests there as well because usually there's not like much feature requests going on for the first party libraries all of our libraries um are pretty stable already so they have like lots of things in them already which make them pretty much feature complete but i usually when i have time to spare like go through the different feature quests and try to implement them either myself or encourage people to send them a pull request for those as well which happens uh a lot as well so really thankful to the community for contributing there as well yeah so do you have any rfcs in case let's say laravel team decides to as add any future so i mean is there any rfc process or it's just like okay we have decided and it's now we are implementing it how's that yeah it's pretty much that so we don't really have an rc process we do encourage a lot to first post an issue for if it's like for the laravel framework specifically to first post an issue on the ideas repo so like other community members can pitch in and like discuss the the id first because that usually leads to like other use cases as well or improvements in how the original author wanted to design the pull request or the code around the feature so that's something we definitely encourage also through the pull request templates that we have um but sometimes like it uh of course happens a lot as well that we get pull requests which don't have those uh issues at first and those are fine as well as long as they're they have like a very uh descriptive um uh description uh about what what's it about why they need it like uh how how we should review the code um and also like like i said earlier we have lots of people watching the framework repository as well so we usually get a lot of uh community members who can share their opinions on the public quest like say like hey you can do this a little bit better or did you think about this a little thing so that's uh nice for us that we have so much uh watchful eyes on the coat as well that catch might catch a few things which we might miss [Music] ourselves oh that's nice how how about uh community uh member how many how they can get involved so let's say if someone wants to come contribute to laravel framework or your first for first party frameworks which you have our us particular employees that you have so how they can get involved yeah uh well luckily for us we usually uh don't have to match uh tickets left on our issue trackers we we've been working very hard at getting them to zero um so um like there's still a few tickets left on the different repositories and like the best place you can go go to is through the issue trackers of different libraries and see if there's anything that you might want to get involved that you want to tackle like see if there's an issue that you think like okay i can get in on this or can give some advice or like how this can maybe be done it's always helpful and like if there's something specific you can fix uh send in a pull request for us and uh so to review um if you have a good idea uh for the framework of course like try to write an issue in the ids repository we don't closely monitor that repository ourselves but we uh try to go through the repository now and then to see if there's anything interesting for us to pick up in the next major release or in the current major release cycle um try to like ask around our discard channel is a very good place to share ideas as well there's a lot of people on our discord as well so if you have a good idea post it there like see if anyone wants to get involved with helping you out on working on a pull request and uh that's a good place to get started as well yeah how about uh stack overflow how i mean um so i'm sure you might be getting a lot of question on stack overflow so how is that managed uh we don't uh closely uh watch stack overflow ourselves that's something we totally leave to the community we only keep an eye on our issue trackers to mainly identify bugs and solve those we don't actively provide support on our issue trackers i sometimes try to help out people if they're stuck but usually what i do is try to direct them to a support channel which could be stack overflow or discord or our large at uh slack or our irc channel because there's just so much community members out there ready to help out ready to answer questions and um if we had to do that all ourselves because we're a very small team if we had to do those hours all ourselves we wouldn't have time anymore to work on our products or on our libraries itself so it's really um like if you have a problem first try to ask on one of those channels uh before you come to the issue tracker because like i think like a 95 percent of the time like someone can already help you out with the with the issue you have yeah so how about team i mean you mentioned that this uh it's a small team so how it is structured so can just tell us a little bit definitely uh so i have to count a little bit like i think we're like one two three i think we're like seven people uh so it's me uh who mainly does the open source uh stuff then you have taylor who of course created the laravel framework taylor's mainly involved in reviewing all of the pull requests that come in for our libraries so he wants to keep an eye on all of the code that goes into the library so he knows like what changed and when issues arise he can have it in his mind fresh so to know like what went wrong where um and he's also of course involved with our products like he usually talks to the different team members about the new features we're working on or the bugs we're trying to solve to help them out uh trying to like like get that uh done in a very good way and um he's also always like working on the next uh big thing at lare hall then we have muhammad uh muhammad is from egypt and he is mainly involved with working on vapor and forge and also like spark which is like a separate product we have uh for billing integration into your level uh application then we have uh james james is mainly working on forge itself he's done a uh like i think like everyone who's been using forge has been seeing like the impact that james has made over the past uh one and a half year well the past two years like for just like lifted to such a new level with all of the different things that james has implemented it's been a really cool uh way to see how the product has grown under him then we have nuno from portugal he's a rt member that works on vapor vapors are like aws integration for serverless uh larval applications and also like nunu has done a terrific job on on vapor like he knows the product in and out he's done such a great job at like uh investigating how all of the aws stuff works and like just like doing vapor and getting it up to running in a very very cool and great way um and we have a new team member since uh a couple of months uh claudio decker he's brought on as a front-end developer mainly and he's helping us transition our products to the next level in terms of like javascript integration so he's working on on few years a lot for forge amongst els and he's uh just helping us out like taking all of that to the next level he's also been doing a very great job lastly we have mir from malaysia and miar is the person who maintains nova which is also a separate product a standalone product and it's a sort of like a content management system that integrates very neatly into laravel amir has also been doing a great job he's currently working on the next major release of nova and i'm not sure like when it will come out but uh like he's been very busy with that as well that's about it for the team yeah so i can see nuno and claudio both are in chat so uh thanks for joining both of you hi guys yeah so i just wanted to know i mean how about money part right so if i understand correctly if laravel is open source framework so how does i mean it is making money and how it is surviving so because there are a lot of large projects which are supported by large organization i mean angular is uh google react is facebook so what about laravel definitely uh so you're correct like laravel is totally open source and all of our first party libraries are as well they're just free out there for you to use but besides those products those libraries we also have a couple of bay products the ones i just mentioned forge is our main product which is meant for server provisioning so it provisions vpss and servers with a standard setup of php of whatever you need to get your laravel application up and running uh it's very tight in with laravel as well so you have all kinds of goodies there to make sure that your laravel application is up and running on a vps we have envoyer which is our paid project for deployments uh so it tackles uh like deployments for applications where you have zero downtime so it's seamlessly when you deploy your application then we have vapor which is our aws integration i talked about earlier it's for serverless applications which need like uh which have like a lot of traffic and are just like a bit like hide more high demanding than what a forge provision server would provide and we have two separate uh products as well uh stand alone which you can buy a single time nova which i talked about earlier which is our cms integration for level and we have um spark as well which is our billing integration and we at the beginning of this year i think we released a new version of spark and it now supports both stripe and battle payment providers so you can get up and running with one of those uh very easily yeah so are they like a subscription based model or is it like a product which just liability members were forge envoyer and vapor are subscription-based models so you pay a monthly or yearly fee and nova and spark are standalone so you pay a one-time fee for those yeah [Music] that's great so let's talk about the different projects you mentioned there are several projects which we have in laravel's laravel sprint uh system so you have your first party libraries and your laravel framework so uh can you just let us l about them what they do and yeah uh do you want to do forge mainly or do you have a specific product in mind that you want to know more about i have i've seen your twitter feed so you mentioned something um i think blade related or what blade ui okay yeah more about the open source uh stuff yeah uh yeah definitely uh like i'm working a lot on uh blade release stuff myself i have a separate project uh called blade ui kit myself which is a personal project um and uh blade uikit is like a component-based library so you probably like if you're doing a lot of javascript you know uh the few i react are very component based um and in larval i don't know i think it was seven we introduced blade components so it's like sort of similar way of defining components in the blade templating language that larval uses and what i did is like built like a sort of like uh toolkit that ships with like standard components that you can use in the in your application yourself it has like an avatar component that derives your avatar from a twitter name or like a github username it has like form-based components to easily like scaffold a form in the into your application uh like all sorts of different uh kind of components i have been neglecting it a little bit over the past few months because i've been working on other stuff but i'm hoping to like get uh working on a proper major release uh soon besides blade you like it i also have a library called blade icons i've been working a lot on that lately and late icons is mainly a very easy way for you to get started with using svg icons into your application so instead of like pasting the entire svg into your source code you can very easily reference it as a component as a blade component or as a directive just a very um much nicer way of using those svgs into your in your larval application yeah so kapil had this question i'm sure you may be getting this question a lot so he says please ask him how do i shut up stupid people who say php is it well yeah i think like we get that a lot uh like us php developers my opinion about that is like as long as you're making a living with php and you're like uh having fun writing php php isn't that as long as there's like one single person left standing that's uh doing php code writing apps and uh making a living then php isn't that and i for a fact know that there's a lot of people making money off php and writing great php applications the php community is uh a great place to be uh in like uh i always love going to conferences like meeting people meeting new people meeting old friends uh it's definitely far far away from that yeah so uh how about uh you as a as a like open source project every or every open source project has some pain points so is there any pain points where community can help php uh family or ps3 framework right now uh that's a very good question actually uh i recently saw an article about uh the bus factor of the php language itself so at the moment there's uh of course a couple of people working on php the language itself and at the moment there's only two persons i think who are very directly involved with the language so that's uh low of course like if anything would have i god forbid happens to one of those people then we as a language would have quite a a problem i think um i think the best way to help php is something that a company called chatbrains did they hired nikita and uh nikita is one of the persons i mentioned who is uh on those bus factors and they uh entirely invested uh his paycheck into letting him work on the on the b2b language itself which is i in my eyes a great way of like contributing to the language um as a company uh while at the same time also having the benefit of having a dedicated score team member on on your team um like more like those kind of investments i think like for uh smaller like developers who like aren't very fluent in like the language behind php itself it's a bit hard to contribute because i think like the rc process of php itself like the way you have to contribute is still like a little bit um too difficult for newcomers to step into but i think like if you're a company i really want to invest into php the language itself the best way is to do something like that jetbrains did of course it's a big investment to have an entire paycheck for someone but it doesn't have to be that large even like you can contribute another race donate to the projects or having like developers spend uh just a little bit of time to the language or helping out uh other library authors as well there's so many open source um uh contributors out there on github who could use some sponsorships as well to help them out maintain keeping on maintaining their projects so always try to keep an eye out on that if there's anyone out there who needs some help with uh keeping their project maintained yeah yeah so there are like millions of developers who are using php to make money so i'm sure uh the people or the developers who are live right now just go ahead and support someone who is already doing great job in the php community uh github sponsor program is making it easy to actually go ahead and support your favorite developers so please do that i mean uh if you if you're making enemies which is something free actually opens this open source is not free yeah everyone knows that someone is actually putting their time yeah yeah please and yeah and definitely try to look around as well for the the people who aren't receiving that much sponsorship there's already a lot of people like getting some sponsorships like the more famous known people but definitely also keep an eye out for those who are also doing a great job on their own libraries but like still are struggling to find uh sponsors for their projects yeah okay in any any particular project you want to give a shout out uh yes uh yeah there's uh one uh i think he's um not that much uh like known or orienting but it's called danek and he's the maintainer of uh the magic library if i'm not mistaken and um like he's doing such a good job of maintaining that it's a like a an extension for php for the image magic uh library i think to for image manipulation and uh i don't think he gets enough credit for the work he does on on that library so shout out to danic for that and uh hope everything is going well with him yeah that's great is it the same library which you mentioned in a slack channel few days ago yeah it's uh it's the same person yeah exactly yeah great so uh please please go ahead and support him in case you are using his project so please please do that yes so we are done with the questions i mean now we don't have anything else to do any anything you want else you want to address um just really want to thank you for having me on uh thanks for doing this interview taking the time uh for interviewing me uh grateful for that thanks yeah thanks a lot for joining and uh so anything else you want to promote on the channel i mean um i'm currently working on a like a semi secret project i can't really talk about it too much it's gonna be something related to github itself uh which i'm hoping to show more i was working on it right before the stream so um the only thing i can say like keep an eye on my twitter and i hope to have something out about it uh very soon it's a php related and related to get up so yeah that's good so in case uh you want to follow address his twitter handle is behind in the background so you can just go ahead and follow him and have a nice whatever he is cooking next so thanks a lot dress for joining and and speaking about the uh laravel framework and how the team works apart from that we have uh this uh another stream coming up on this friday we are going to talk about aws and uh another great community member nada debit who will be joining us uh same time 10 p 10 p.m ist and uh yeah i will see uh everyone there in case you're interested to learn more about aws amplifier and thanks again address for joining us and in case just just just to know in case someone has questions what is the best place or best way to actually reach out to you best places to like uh i keep a very close eye on my twitter so if you have any questions hit me up on twitter and i'll try to reply there thanks yeah yeah thank you thanks uh thanks a lot again so uh thanks everyone for watching the stream in k and feel free to actually go ahead and follow dress he's also on github sponsor program so if you uh can support him please go ahead and do that and yep that's it for today so see you on friday see ya bye bye bye thanks for having me

Channel: Tech Talks With Santosh

Views: 171

Keywords:

Id: Lc31JliS4s4

Length: 33min 18sec (1998 seconds)

Published: Wed May 26 2021