How to contribute to OSS without annoying maintainers?

[music] Yeah. So, I'm a first contributor for around a year now and I have been like developing an open-source volunteer and shift management plug-in for eventi. So, it all uh started as a Yeah. Let's move right. Yeah.

Can you switch to next slide?

Yeah. So, it all started as a uh discussion uh which later on became a problem. So uh every event runs on volunteers. Uh volunteers can be people like who manages the entire event. In order to make it successful event, we need a few volunteers to be have some sort of management.

So for that purpose uh event had no way actually to manage them or recruit them. So for that purpose we were using spreadsheets or some email threads and some separate tool. But there was no native way that can actually be useful. So for that uh the team shift came as a uh what we can say uh solution to the problem. Please next slide.

Yeah. So, Team Shift is a component level plug-in that is built by me which helps in getting a volunteer recruited from application stage to uh review getting it that application reviewed by organizers and once that application is approved they can see the entire schedule that list all the shifts and those shifts can also be uh claimed by the volunteers and on the day of event they show up and they check in through their assigned shifts and they get a certificate of appreciation at the end of event where uh also uh they get some perks as well through this uh teamship plug-in which we everything is managed inside event itself. Next slide. Yeah. Here uh comes the organizer side config.

Here what is called as that is called as call for team members. So here a organizer can set a call make it public or make it even a private call that can be sent to some pool of members privately without showing it to anywhere on the internet. it can be only shown to those people through a secret link. Uh it can also set deadlines and uh that deadline can be configured in this call settings as well. Uh then there are few more configurations like custom questions that can also be uh built using uh the uh eventi ticket component like we have already developed this plug-in on top of eventi.

Uh for these questions these will be publicly appearing on all the pages that these calls belong to. Next page. Yeah. Then these are few more features that are part of team shifts. For example, roles and locations.

Roles and locations make a complete shift. For example, let's say this is an event where photography can be a role. Then the location can be clsless. This particular hall then the timing can be like 5 10 or something. So these all things completely make a full shift that can be assigned to any member through organizer or even the member can see those shifts on their public schedule.

Yeah. Next slide. Last one. Yeah. So this is where volunteer side comes in picture.

Uh we have like a very beautiful looking schedule which is built by our core members. uh it is already part of like schedule editor and the public schedule where we can see all the shapes of uh those volunteers. We can remove them. We can uh maybe assign someone even we can like uh send uh emails to them from this particular uh schedule. Next slide.

Uh then there are a few more features that are part of uh team shifts. Uh email certificates and vouchers. So these all three are built on top of eventi. So, event already has a core system which handles emails, which handles uh ticket editors, which handles uh voucher claims and voucher send out. So, it is built on top of that.

We have a self-contained email system in uh team shift uh that can send email at every instance of the volunteer entire journey and life cycle. Uh then we have a certificate layout editor which can be used to generate and make some certificates uh that can be customized as per each event. For example, OTS as a event that they can have their own timings, they can have their own location, they can have their own logo, they can have their own uh what what you can say titles and so on. So that can be edited in the certificate layout editor. Uh then we have ticket vouchers.

They are also built on uh top of vouchers that are that can be generated in tickets. Those vouchers are sent out to uh volunteers. Those are part of team shifts and those vouchers are mapped to the check-in as well which will help in getting that volunteer check-in at the uh events um uh entry. Yeah. So these were uh these are few lessons I learned actually.

So event is like a very developing evolving platform. Uh like every day it keeps evolving. So uh I learned how to work in an existing codebase. Then also uh learned on how to uh turn any requirement into feature like few months back it was just an uh discussion now it is like a completely bootstrap plug-in. Uh then I also learned from code reviews from my mentors and mainteners.

So it was a great experience so far. Yeah next slide. Yeah that's all about my talk uh and all about team shift. If you want, if you are a developer and if you want to contribute, you can just scan the QR and like go to uh team shifts repository and like find uh the open issues and stuff. Uh that's all.

[music]