Loopback-next: Welcoming Contributors

[ritch]

This issue is for new folks to chime in and say hello and that they'd like to be involved offline (off GitHub) discussions. I'm not expecting the working group on this project to be so large that we can't all get to know each other.

Just comment here that you'd like to be added to the LoopBack.next contributors list and I'll create a group in the StrongLoop org with all of you - so we can do things like @strongloop/loopback-next for scheduling external meetings and such.

When we invite you to join our org and you don't receive an email notification for GitHub, then you can accept the invite here: https://github.com/strongloop

Check out issues labelled as good first issue for tasks suitable for new contributors.

---

_Updated on 05/31/2019_

Hi all! First of all, thanks for your interests and support in LoopBack 4!

We have been thinking about how to grow our contributor community together with the user community. There are several ways to contribute:

• Provide your feedback
  We'd love to hear your feedback! Feel free to comment on the GitHub issues that interest you or open an issue in this repo
• Contributing code
  Please see below for details. For step-by-step instructions in submitting a PR, refer to https://loopback.io/doc/en/lb4/submitting_a_pr.html.
• Contributing docs
  From the feedback we got, there's a need to improve our docs. This PR outlines some of the enhancements we'd like to make: https://github.com/strongloop/loopback-next/pull/2925

Contributing code

Contribute what you need

We hope you are contributing to something that you need or will be using. We'd encourage you to take a backlog and see if any of our GitHub issues capture your requirement. If you're planning to implement a more complex feature, it would be helpful to submit a draft PR with minimal implementation to discuss your approach first. It would also be helpful to include your use case so that we can understand your requirements better. This is to make sure the intended implementation would align with our architecture and direction.

Contribute anything

If you don't have a particular area you want to contribute, you can look up the help wanted: https://github.com/strongloop/loopback-next/labels/help%20wanted

New Contributors?

If you're new to contributing to LoopBack or open source projects in general, don't worry. You can look at issues with good first issue. Those issues are meant for new contributors:
https://github.com/strongloop/loopback-next/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

[jonathan-casarrubias]

Hi @ritch looking forward to be added as LoopBack.next contributor

[doublemarked]

Hey sounds great, looking forward to participating.

[karthicktv]

Thanks; would be delighted to participate

[carlosroec]

Hi @ritch, looking forward to be part of this group!

[jcurlier]

Hi @ritch would love to participate

[jesperbruunhansen]

Hi @ritch, I would like to contribute as well!

[rajivramv]

Greetings@ritch
Been working for a commercial mBaaS and strongly feel the tech should be FOSS. Excited to be part of this community!

[jonathanfoster]

Hey @ritch, I've been using Loopback on a project and I love it. I'm looking forward to contributing to next.

[ritch]

Here is the list so far:

• @ritch
• @superkhau
• @raymondfeng
• @bajtos
• @deepakrkris
• @crandmck
• @mpatsute
• @rashmihunt
• @siddhipai
• @jannyHou
• @davidcheung
• @loay
• @0candy
• @kjdelisle
• @jonathan-casarrubias
• @doublemarked
• @karthicktv
• @carlosroec
• @jcurlier
• @jesperbruunhansen
• @rajivramv
• @jonathanfoster

[ritch]

You can now @mention everyone on this list with:

@strongloop/loopback-next

[jeetendra-choudhary]

Hello @ritch, I'd like to be added to the LoopBack.next contributors list.

[JonnyBGod]

Hi all, I am very interested in participating in the discussion and possibly do my contributions to @strongloop/loopback-next.

[padelagani]

Hello @ritch, I'd like to be added to the LoopBack.next contributors list.

[vishwasrao]

Hello, count me in as well

[m3hari]

Hell from Ethiopia, Very eager to be in the contrbiuters list .

[el-davo]

Dave from Ireland, Delighted to finally see you guys moving to typescript. Would be happy to help in any way i can

[rpeterson]

Count me in

[denneulin]

GraphQL ? Typescript ? Great choices ;) I would be very pleased to help you to build this great tool :D

[shairez]

would love to help

[alireza-ahmadi]

I would be more than happy to participate

[ritch]

@jeetendra-choudhary
@JonnyBGod
@padelagani
@vishwasrao
@m3hari
@el-davo
@rpeterson
@denneulin
@shairez
@alireza-ahmadi

Welcome! 👋

[jeetendra-choudhary]

@ritch Thank you!

[M-jerez]

Hi @ritch is this still open?
if you are still accepting contributors I would love to be added to the group.
I've done some work with loopback and next looks really interesting.
So please add me if it still possible!

[pbouda]

Hi @ritch, I like to contribute to loopback-next.

[onel0p3z]

Hello there! Count me in 👍

[ganipadela]

Hello @ritch, I'd like to be added to the LoopBack.next contributors list.

[makara]

Hi @ritch. Thanks for the invitation and everything; I'd love to join the group.

[BostjanPisler]

@ritch 🙌

[herbertsg]

Hi @ritch, I'd like to contribute to loopback-next.

[rhzs]

Hi @ritch, hv done some enterprise works with Loopback. Would like to join loopback-next.

[ritch]

@M-jerez
@pbouda
@onel0p3z
@ganipadela
@makara
@BostjanPisler
@herbertsg
@incubus8

welcome to the 🎉🎉🎉!

[proreact-mj]

Yes plz

[bitingedgemick]

Happy to be involved @ritch

[headwire]

Hey @ritch, would love to help.

[rahulrkr08]

Hey @ritch, I would like to join.

[haoxins]

Hi @ritch, I would like to join :)

[bajtos]

@proreact-mj
@bitingedgemick
@headwire
@rahulrkr08
@coderhaoxin

Hello and welcome onboard! 🎉 🎉 🎉

Please check your GitHub inbox for an invitation to join strongloop organization and the loopback-next team.

I apologize for the delay.

[richardpringle]

@bajtos or @ritch, can you add me on there as well?

Cheers!

[bajtos]

@richardpringle done. Welcome on board! (Or should I say welcome back? 😉)

[null4bl3]

Would love to come aboard.

[bajtos]

@null4bl3 invitation sent, welcome! 🎉

[Untel]

@ritch @bajtos
Hey guys! Would like to help :)

[bajtos]

@Untel welcome! 🎉

[mpicard]

Hi can I be added to join the discussion?

[bajtos]

@mpicard invite sent, welcome! 🎉

[phuongnl]

Hi @bajtos, i would like to join.

[darknos]

Hi @bajtos,
I'm already typescripting with loopback and I'd like to join.

[mrbatista]

Hi @bajtos, i would like to join.

[dhmlau]

Thank you for your interest in LB Next! We're now calling for contributors on LoopBack extension. Please see https://github.com/strongloop/loopback-next/issues/647.

[creativekinetix]

@bajtos @ritch would love to join as a contributor. thanks and excited about LB-Next

[mikstur]

Hi @bajtos I would like to join as a contributor, please! Been a long time LoopBack developer (1, 2 and 3).

[tuanquynet]

Hi @bajtos ,
I would like to join as a contributor, please. I have built 3 application based on loopback. One is IoT system, one is built as API endpoint for mobile app. And I am developing 1 internal social network using next-js and loopback. Thanks.

[bajtos]

@creativekinetix @mikstur @tuanquynet Awesome! I sent you an invite to join our team, check your email inbox or go to https://github.com/strongloop/loopback-next/invitations to accept.

@vishwasrao @herbertsg I see that you haven't accepted our invite yet, are you still keen to join? Please go to https://github.com/strongloop/loopback-next/invitations to review & accept the invitation.

[VMois]

Hi, @ritch! I would like to join as a contributor. Currently, I'm volunteering for the non-profit organization and we use LoopBack 3. I'm very excited about LoopBack 4 new concepts and architecture. Want to learn more and help)

[Amir-61]

@bajtos I would be more than happy to contribute as well; please add me. Looking forward to contributing in LoopBack.next now.

[sofyan-ahmad]

I've been using loopback for 2 months now, but I already deliver 2 huge applications.
I'll definitely contribute to loopback community.
looking forward to the next.now()

[Bnaya]

Hey @ritch I have few questions about code/design decisions that the project have made
Where is the best place to discus about it?

[bajtos]

@VMois @Amir-61 @sofyanhadia
That's great! I sent you an invite to join our team, check your email inbox or go to https://github.com/strongloop/loopback-next/invitations to accept.

@Bnaya

I have few questions about code/design decisions that the project have made
Where is the best place to discus about it?

Please open a new GitHub issue, preferably one per topic, and mention the following handles: @bajtos, @raymondfeng, @ritch and @kjdelisle.

[yshing]

@bajtos I would like to join the team as well.
Have been using loopback 2&3 for a few years.
Really looking forward to this.

[bajtos]

@yshing welcome on board and sorry for the delay.

[yagobski]

Thanks @bajtos looking forward to participating.

[mdartic]

Hello @ritch, I used Loopback v3 some times ago, and now I'm starting a new project with.
I'm gonna use the v4 version, maybe I can help for documentation or maybe code.
Would be happy to contribute and join the team !

[thanhlq]

Hello, I am also planning to use loopback v4 in my next project so it's really interesting for me to participate into this group. Thank you!

[raul26]

Hi @bajtos I would like to join the team and contribute. Thank you.

[bajtos]

@mdartic @thanhlq @raul26 welcome 🎉

[jseijas]

Hi @ritch, I would really love to participate!

[kattsushi]

@ritch Hello! I would like to join the team as a contributor, thx!

[yosbelms]

Hi @ritch, @bajtos, looking forward to be part of this group!

[ghulamhussain]

@bajtos would love to help.

[lindoelio]

Hey guys! I would like to join the contributors team as well :-)

[kjdelisle]

:tada: @jseijas @kattsushi @yosbelms @ghulamhussain @lindoelio :tada:
Invites sent! Thanks for your interest!

[kjdelisle]

And welcome! :)

[dhmlau]

Hi @strongloop/loopback-next , thank you all for your interests! In case you aren't aware, we are currently asking for the community to help us decide on the new logo. Please see details and survey in here: https://strongloop.com/strongblog/new-loopBack-logo/.

[ghulamhussain]

hi Diana lau i am pleased to know that you are working on your new logo and
accent color and i have provided my feedback regarding design. Thanks for
reminding me.

On Tue, Dec 12, 2017 at 6:33 PM, Diana Lau [e-mail] wrote:

Hi @strongloop/loopback-next
https://github.com/orgs/strongloop/teams/loopback-next , thank you all
for your interests! In case you aren't aware, we are currently asking for
the community to help us decide on the new logo. Please see details and
survey in here: https://strongloop.com/strongblog/new-loopBack-logo/.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/strongloop/loopback-next/issues/110#issuecomment-351052336,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP4HoQTUTH03h34CvaD2WblcKW5B_H_Sks5s_oCygaJpZM4M3F3O
.

[llissery]

Hi @bajtos, I've been using loopback for months now.I would like to contribute to loopback-next as well!

[privateOmega]

Hi @bajtos I am new to loopback but would love to contribute to loopback-next. :smile:

[rahulpsd18]

Hi @bajtos I am new to loopback too and would love to contribute in any way possible. Eagerly waiting for v4 release. Thanks.

[bajtos]

Good morning, fine folks of @strongloop/loopback-next ! As the design of LoopBack4 is stabilizing and we are getting closer to have a Walking Skeleton/MVP that will make it easier to contribute small incremental improvements, we are looking for tasks that are suitable for your first code contributions. We are using "good first issue" label in our issue tracker and there are already few such issues available for picking up, see

https://github.com/strongloop/loopback-next/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

If you decide to start working on one of those issues, then please leave a comment to let other potential contributors know.

[skanygin]

Hi @ritch! Can I join loopback-next army? I've reviewed tasks from @bajtos list and I think I can handle some of them.

[hasahmad]

Hi @ritch I'd like to join.

[perceptron007]

Hey, everyone, this is Vijay. I am junior developer and I am using Loopback 3 for our project since last June. I would really love to help in any way I can. Revert back if I can be of some use.

[bajtos]

Invitations sent 📬

[hmtai6]

Hi @ritch, I wanna would like to join. I have experience on loopback v3 and typescript with react. It will be my honour to join the next version loopback development.

[tallboy]

Hi @ritch I'd also like to contribute to the loopback-next project. Thanks!

[dhmlau]

@hmtai6 and @tallboy , thanks for your interest! Invitations sent.

[ThatDevSteve]

Hi @ritch

I'd love to contribute to Loopback 4 thanks

[joeytwiddle]

Hi, I was recommended Loopback in 2013, but I didn't get around to using it for many years. Now we're starting a new project at work, so I thought I would try out Loopback 4.

Unfortunately the boss wants a working demo by the end of the week, and I'm still stuck on authentication. Oops! (Edit: We made it, with a bit of duct tape!)

It does look pretty powerful though. TypeScript has already strong-armed me into the corner a few times. I keep getting Java flashbacks. Oh well, whatever doesn't kill you...

[ghulamhussainK]

@joeytwiddle version 4 is a work in progress . it would be suitable for production in 2019.you should start with v 3. as it is the mature and stable one :smile:

[SzymonSel]

Hi Everyone. I recently pushed my first contribution and I'm looking forward to contribute more in a more organized fashion :)

[bajtos]

We have 9 pending invitations. Could you please open the following URL and accept/reject the invite please? @vishwasrao @herbertsg @skanygin @austinfrey @GetCodePanda @ThatDevSteve @joeytwiddle @ghulamhussainK @SzymonSel

~https://github.com/strongloop/loopback-next/invitations~
https://github.com/strongloop

(EDITED based on https://github.com/strongloop/loopback-next/issues/110#issuecomment-394165930)

[joeytwiddle]

@bajtos, that links gives me a red alert:

Sorry, we couldn't find that repository invitation. It is possible that the invitation was revoked or that you are not logged into the invited account.

_Edit: skanygin's workaround below worked._

[collaorodrigo7]

@ritch, @bajtos I would really love to help. I have been using loopback 3 over a year already and testing a bit of 4, it's all pretty awesome. I think I can contribute a lot, and will also like to help writing the new documentation and examples!

[skanygin]

@bajtos same error as @joeytwiddle mentioned.

[skanygin]

@joeytwiddle @bajtos

Upd.: I was able to accept the invitation on github.com/strongloop.

[bajtos]

@collaorodrigo7 invite sent.

@joeytwiddle @skanygin sorry for the confusion! I am glad you found the right URL where to accept the invite.

[fernandobastos]

Hi,
I'd love to contribute to Loopback 4

[marioestradarosa]

Hi @bajtos I would like to contribute. Currently we are moving a loopback3 backend to loopback4 and making some training materials to our in-house developers on loopback4.

[bajtos]

@marioestradarosa Invitation sent.

I am excited to hear that people have already started migrating to LB 4.x. I would love to hear your feedback - which part of LoopBack 4 worked well for you, what are the rough areas that we need to improve, what features are you missing most. If you could write it as a blog post (e.g. on your company or personal blog, or perhaps on https://medium.com?), then we can boost your reach by sharing your post to our followers on social media.

[marioestradarosa]

Hi @bajtos , I admire all the work done so far on any LoopBack versions. Our electronic banking platform supports browser and mobile app banking software on the front-end. In the Backend, we talk to Finastra core banking SOAP Web Services, Db2 database and MongoDB for our internal _chat app._ All these communications are handled by loopback3 already.

We created our own microservice for authentication and token management. Our developers just received a training on typescript a couple of months ago, _we are coming from Java_ world and now we are excited that we can use loopback4 with typescript in our solution.

_Missing?_ . I will keep you posted :-).

One thing for now, is that _we centralized in a library our models_ (_using interfaces)_ that we use in our angular applications, those models are transformed in order to be used by the @model decorator so we keep the same centralized concept and useful for both angular and LoopBack4. The feature of transforming those interfaces used by Angular already and transformed to model definitions would be great! as some tables are very simple. something as follows, as those tables are just required to feed some combo boxes on client apps, but also are required in CRUD operations in a BackOffice application.

As a note, instead of DummyInterface we might have a 50 columns one, but we are still just requiring to pass in, just the ID, the real table name and if the ID is required or not, so the object parameter will always be simple:

@model(DummyInterface,{table:'DUMMY', id:'BBLID', required:false'})

The DummyInterface is more or less as follows:

export interface DummyInterface {
    BBLID: number;
    NAME: string;
    ... N number of columns
}

This DummyInterface is placed in a module library and is installed using npm along with other interfaces and ready to use by mobile, angular 6 and LoopBack4 applications.

In the mean time, I will work on this weekend on introductory training material that we used internally so we can evangelize consultants/developers to move forward with the adoption.

[bajtos]

@marioestradarosa thank you for an example showing how you would like to use LoopBack 4. Please open a new issue to discuss your use case, so that we don't spam everybody watching this issue.

[bhailogee]

Hi @bajtos, I would like to thank for such a nice framework, Its been 2 years now, I am working with loopback, and now I am planning to move to lb4 for my new project, this time I would like to be the part of your team, If anyway I can help that would be satisfactory for me. I am training and talking to many people here in Pakistan about loopback. Please add me in your channel if possible.

[bajtos]

@bhailogee It's great to see LoopBack spreading across the world :)

I sent you an invite to join our GitHub org/team. If you don't receive an email notification from GitHub then you can accept the invite here: https://github.com/strongloop.

[viper-md]

Hi @bajtos , I would like to contribute to loopback-next.

[peanutenthusiast]

Hi @bajtos I'm interested in contributing to loopback-next! I attended the Loopback talk at NodeSummit this year, and my team is looking into implementing Loopback 4 for our future projects.

[bajtos]

@viper-md @peanutenthusiast invites sent. If you don't receive any notification from GitHub, then you can accept the invitation and join our GH organization here: https://github.com/strongloop.

Welcome on board 🎉

[morningspace]

@bajtos I would be interested to be part of the family… and wonder how and what I could contribute… :-)

I am from IBM Connections development, where we have spent 2 years using lb3 to create our next generation product. It’s a very nice framework!

Early this year, I developed an online course on lb series in Chinese for IBM Mini Academy to share lb3 use here to our local developer communities. It covers 6 lessons and 1 offline workshop. The presentation, sample code and video record for each lesson can be found at my github repo. On lesson 6, we also invited Janny Hou from lb team to share the overview of lb4. All the materials can also be found at IBM developerWorks. I'm proud that the top most search results on developerWorks cn are all about the course:-)

Recently I started to evaluate lb4, and plan to write up something on what I learned during my evaluation and share with my readers on developerWorks and then my personal blog. I am also having some questions on the behavior of lb4 and not sure whether that's limitation of lb4 or because the work is still in progress and will be changed later when it's released, or even my misunderstanding. I will find time to raise somewhere after I know how:-)

[dhmlau]

@morningspace , hi again. :)
Thanks for putting up the online course for LB3.
If you have any questions / bug reports / feature proposals, please feel free to open an issue in this loopback-next repo. It helps us to know more about what our users are trying to do and to prioritize our work.

@bajtos will send out an invitation to join the GH team.

[morningspace]

Hi @dhmlau @bajtos Just curious whether the invitation has been sent out or I missed it :-) Thanks in advance...

[bajtos]

@morningspace sorry for the delay, I sent the invite few moments ago.

[JosueMorales]

@bajtos @ritch is it too late to join?

[bajtos]

@JosueMorales not late at all. Invitation sent.

[murphylan]

Hey, looking forward to participating.

[elv1s]

I'd like to join!

[aldaircruz]

Hi everyone, thanks for this amazing project!
I'm getting my feet wet in strongloop, and I would like to participate!

Keep up the good work!

[leezhenghui]

Hello,
I would like to participate.
BTW, I'm currently working on a personal project tsnode-proxify for AOP library for node.js w/ typescript, I was told that lookback-next may have similar feature plan. If possible, I am happy to help on that feature.

[jiwantmg]

Hello,
I would love to participate.

[RaphaelDrai]

Hi @ritch looking forward to be added as LoopBack.next contributor. Thanks

[cloudwheels]

Hi @ritch and @dhmlau I've been, er, enjoying getting to grips with loopback4 recently and trying to feedback helpfully (I hope) with issues if poss.

I really appreciate the responses from your end as I can see there's a lot going on and I think it was a brave but wise decision to put the GA out before having a chance to really do a lot of implementation to show it off.

It's all very exciting and would love to be marked as involved when you next update your contributor list and do what I can when I can, even if it's docs, as I think one consequences of the GA release is you will probably be fire-fighting more & more user implementation questions and/or risk having folk walk away frustrated (unnecessarily) unless the initial quick start/deploy is a little smoother than currently. Hopefully this can be balanced with a wider base of contributors so you can get some sleep occasionally :)

With my best wishes!

[bajtos]

Invites sent ❤️

[cloudwheels]

Many thanks for the add @bajtos - after a few days checking out lb4 itself I will be tracking the shopping sample closely looking at sticking / (generating?) an admin CRUD client interface on top of that with something Angular-ish. I'm actually having some success developing a user manager with Ionic4 beta at the moment, though not sure whether I'm opening a can of worms there! Will put up a repo if & when I get somewhere...

[gczobel-f5]

Hi @bajtos!
Looking forward to being added as LoopBack.next contributor.

[TomerSalton]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[apocaliss92]

Hi @ritch looking forward to be added as LoopBack.next contributor. Thanks

[bajtos]

Invites sent ❤️

after a few days checking out lb4 itself I will be tracking the shopping sample closely looking at sticking / (generating?) an admin CRUD client interface on top of that with something Angular-ish. I'm actually having some success developing a user manager with Ionic4 beta at the moment, though not sure whether I'm opening a can of worms there! Will put up a repo if & when I get somewhere...

@cloudwheels sounds great, I am looking forward to see what you can build.

[orshlom]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[The-Murdock]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[YaelGit]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[bajtos]

Invites sent ❤️

Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop

Right now, there are 16 pending invitations: @vishwasrao @herbertsg @austinfrey @GetCodePanda @ThatDevSteve @ghulamhussainK @murphylan @David-Mulder @leezhenghui @aldaircruz @TomerSalton @gczobel-f5 @codejamninja + the three new invites sent today.

I apologize for a possible spam 🙈

[SharonItz]

Hi @bajtos!
Looking forward to being added as LoopBack.next contributor.
Thanks
sharon

[codejamninja]

Thanks!

[oleg269]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[haotangio]

Hello @ritch @bajtos
I've been using Loopback for very long time on several projects and really enjoy it.
I'd love to contribute to Loopback 4 and be added as Loopback.next contributor.
Thanks.

[BillTuan]

Hi @ritch @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[bajtos]

Invites sent, welcome on board 🎉 Please don't forget to accept the invite.

[Dhirendra24]

Hi @ritch looking forward to be added as LoopBack.next contributor. Thanks

[iamjamilspain]

@ritch, add me to the contributor list too please

[dejibimbolaAyo]

I would love to contribute, please add to contributor list.

[bajtos]

Invites sent, welcome on board 🎉 Please don't forget to accept the invite.

[nabieebabak]

Hi @ritch & @bajtos ,
I've worked on a project on loopback 3 for the past 2 years and i'm loving it. Please add me to the list as well. Love to be able to give back and thanks for the great framework!

[marvinirwin]

@bajtos Requesting and invite an invite so I can contribute, thanks.

[milindsingh]

@bajtos I want to be part of loopback community and contribute to the framework.

[orensolo]

Hi @bajtos
Looking forward to being added as LoopBack.next contributor.
Thanks.

[luisfavila]

Would like to be added as well @bajtos
Looking forward to contribute!

[ghost]

Hi @ritch @bajtos @raymondfeng looking forward to be added as LoopBack.next contributor. Thanks

[bajtos]

Invites sent ❤️

Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop

[yanamg7]

Hi @ritch @bajtos @raymondfeng,
Looking forward to be added as LoopBack.next contributor.
Thanks

[david-sw]

Hi @ritch @bajtos @raymondfeng,
Looking forward to be added as LoopBack.next contributor.
Thanks

[ghost]

Hi @ritch @bajtos @raymondfeng,
Looking forward to be part of amazing community.
Thanks.

[bajtos]

Invites sent 📨

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[samarpanB]

Hello @ritch @bajtos

Looking forward to be part of loopback-next community and contribute.

[Whamo12]

I'd like to help out anyway I can, thanks!

[d337]

Hey @ritch @bajtos,
I would like to help out too guys. Waiting for magical mail.

[vnaveed]

Hi I have an issue on model relation. By using hasmany mapped to another table column.But while calling default crud get api I can't able to get that subtable array of values in explorer output

[bajtos]

@vnaveed please open a new issue and provide us with enough details to reproduce the problem you are experiencing. See https://loopback.io/doc/en/contrib/Reporting-issues.html

[bajtos]

@Whamo12 @deepchudasama Invites sent 📨

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[derdeka]

Hi @ritch @bajtos
Looking forward to be part of amazing community.
Thanks.

[ckoliber]

Hi dear friends: @ritch, @bajtos, and other team members
First of all, thanks a lot for the perfect version of loopback

I'd be happy to be a member of your team

Currently i'm trying to develop some extensions for loopback v4:

1. loopback-telegram-extension: Telegram bot library for loopback v4 based on Telegraf library
2. loopback-authorization-extension: General way for authorizing users in a RestApplication, depends on @loopback/authentication
3. and etc

[bajtos]

@derdeka @koliberr136a1 Invites sent 📨

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[shubhddn01]

Hi @bajtos
I'd like to be added to the LoopBack.next contributors list.
Thanks.

[iamdharmesh]

Hi @bajtos, I would like to contribute as well!
Thanks

[rodrigouz]

Hi @bajtos
I would like to be part of the contributors.
Thanks!

[bajtos]

@shubhddn01 @iamdharmesh @rodrigouz @quico14 invites sent, welcome on board!

[yagobski]

Hello @ritch https://github.com/ritch and @bajtos
https://github.com/bajtos would be possible to contribute too?
Thanks

Le ven. 24 mai 2019 à 12:38, Miroslav Bajtoš [e-mail] a
écrit :

@shubhddn01 https://github.com/shubhddn01 @iamdharmesh
https://github.com/iamdharmesh @rodrigouz https://github.com/rodrigouz
@quico14 https://github.com/quico14 invites sent, welcome on board!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/strongloop/loopback-next/issues/110?email_source=notifications&email_token=AABV6NHRXMCOEF7W75VWCILPW7ATZA5CNFSM4DG4LXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWE4DMY#issuecomment-495567283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABV6NF6DFN5MHF2MD6FW3LPW7ATZANCNFSM4DG4LXHA
.

[bajtos]

@yagobski of course! Invite sent 📨

[dhmlau]

@strongloop/loopback-next, thanks for your support in LoopBack! I've added some details on how to contribute to the original description. Hope it would be helpful for those who would like to contribute but don't know where to start. Thanks!

[aharbis]

Hi @bajtos, I'd like to be added to the contributors list. Thanks!

[sbacem]

Hi @bajtos, I would like to be part of the contributors.

[bajtos]

@aharbis @sbacem Invitations sent, welcome on board 🚢

[bhupesh-sf]

@bajtos I would like to contribute to this awesome projects. We are using it for our production applications and has delivered successfully as well. Now wish to contribute to the project itself. Thanks

[bajtos]

@bhupesh-sf invite sent, welcome on board 🚢

[julianomacielferreira]

Hi @bajtos,

I would like be a contributor to this great project, too.

Thanks!

[irineul]

Hey, @bajtos I would like to contribute to the project! We are using it and I want to make it even better! Tks!

[bajtos]

@julianomacielferreira @irineul invites sent ✉️

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[frbuceta]

@julianomacielferreira @irineul invites sent ✉️

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

Hey @bajtos you send me an invitation?

[julianomacielferreira]

Hello @bajtos ,

Thank you very much!!!

[alcmontejo]

hello, Interested here. count me in.

[jorgebarrero]

I would like to participate... thanks. Documentation is what I would like to do. Guidelines for beginners

[Sharonee]

Hi @bajtos I would like to participate
thanks

[yashmurty]

Hi @bajtos, I have contributed to the docs here before and would like to contribute more here on multiple fronts. :pray:
Thank you. :)

[yashmurty]

Hi @bajtos, waiting to hear from you! :slightly_smiling_face:

[bajtos]

@alcmontejo @frbuceta @jorgebarrero @yashmurty @Sharonee invites sent, I am looking forward to see you around in our GitHub repositories 🤗

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[frbuceta]

@alcmontejo @frbuceta @jorgebarrero @yashmurty @Sharonee invites sent, I am looking forward to see you around in our GitHub repositories 🤗

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

Thanks @bajtos 😎

[madaky]

Hi, @bajtos I would like to contribute to this awesome project.

[madaky]

HI, @bajtos Thank you :smile:

[mohanasundarR]

Hi,
@bajtos using loopback for more than a year for developing complex Api's. I am Willing to be a contributor for this awesome project.

[squiril]

Hi @bajtos
I would love to participate :)

[koriamanish]

Hi, @bajtos I would like to contribute to this project

[Hichem-elAbassi]

Hi, @bajtos ,count me in (?)

[jgwinner]

Hi @bajtos I'd definitely like to be involved.

[sila12]

Hello!!
We have been using loopback in my company for some time now! And I really love the project. I would definitely love to involved.

[spirAde]

Hi @bajtos would love to help

[n-francky]

Hello! I would like to be involved as well! To this beautiful project!
Thanks.

[HrithikMittal]

Hi, @bajtos I would like to contribute. and I am also working over the issues and working towards the improvement of docs you can check it out, please

https://github.com/HrithikMittal/Loopback4-auth
https://github.com/HrithikMittal/loopback4-authorization

[nflaig]

Hi, I am using Loopback 4 for a while now and would like to further contribute to the project.

Thanks for the great work!

[bajtos]

Invites sent 📨

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[GabrielCarneiroDeveloper]

Hi @bajtos, I have been using loopback in some personal projects and I loved it. I would like to contribute.

[alcmontejo]

@bajtos sorry its been awhile, can you please send the invitation again, thanks.

[bajtos]

Invites sent 📨

_Please note that you have to accept the invite on GitHub before you become a member of @strongloop/loopback-next. If you didn't receive an email notification from GitHub, then I think you can find the invite when visiting StrongLoop organization on GitHub: https://github.com/strongloop_

[mayank-SFIN571]

Hi @bajtos
I would like to contribute.
thanks

[bajtos]

@mayank-SFIN571 Invite sent 📨

[alexkander]

Hi guys, I would like to contribute.

Regards

[bajtos]

@arondn2 Invite sent 📨

[andrewlamyw]

Hi @bajtos I would love to contribute.

[odykyi]

Hi @bajtos I am happy to implement new feature with roles
please provide me access
many thanks

[MattiaPrimavera]

Hi @bajtos, I'd love to contribute!

Best regards,

[vishal-chhabria]

Hi, I have been using for a while now, would love to contribute !

[alma3lol]

Hi @bajtos, I'd love to be a contributor.

Thanks in advance.

[bajtos]

Invites sent 📨

We are not using the team @strongloop/loopback-next much. I think this thread is past its usefulness, I am going to close this issue.

For anybody interesting in contributing to LoopBack, feel free to help others in GitHub issues, answering questions on StackOverflow or contributing pull requests to improve the framework. We are keeping an eye on regular contributors and inviting them to become maintainers with a commit access, that's the best way how to join our team.