Welcoming Contributors
ritch opened this issue ยท 216 comments
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: #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
Hi @ritch looking forward to be added as LoopBack.next contributor
Hey sounds great, looking forward to participating.
Thanks; would be delighted to participate
Hi @ritch, looking forward to be part of this group!
Hi @ritch, I would like to contribute as well!
Greetings@ritch
Been working for a commercial mBaaS and strongly feel the tech should be FOSS. Excited to be part of this community!
Hey @ritch, I've been using Loopback on a project and I love it. I'm looking forward to contributing to next.
You can now @mention everyone on this list with:
@strongloop/loopback-next
Hello @ritch, I'd like to be added to the LoopBack.next contributors list.
Hi all, I am very interested in participating in the discussion and possibly do my contributions to @strongloop/loopback-next.
Hello @ritch, I'd like to be added to the LoopBack.next contributors list.
Hello, count me in as well
Hell from Ethiopia, Very eager to be in the contrbiuters list .
Dave from Ireland, Delighted to finally see you guys moving to typescript. Would be happy to help in any way i can
Count me in
GraphQL ? Typescript ? Great choices ;) I would be very pleased to help you to build this great tool :D
would love to help
I would be more than happy to participate
@ritch Thank you!
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!
Hello there! Count me in ๐
Hello @ritch, I'd like to be added to the LoopBack.next contributors list.
@ritch ๐
Hi @ritch, hv done some enterprise works with Loopback. Would like to join loopback-next.
@M-jerez
@pbouda
@onel0p3z
@ganipadela
@makara
@bostjanpisler
@herbertsg
@incubus8
welcome to the ๐๐๐!
Yes plz
Happy to be involved @ritch
Hey @ritch, I would like to join.
@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 done. Welcome on board! (Or should I say welcome back? ๐)
Would love to come aboard.
Hi can I be added to join the discussion?
Thank you for your interest in LB Next! We're now calling for contributors on LoopBack extension. Please see #647.
Hi @bajtos I would like to join as a contributor, please! Been a long time LoopBack developer (1, 2 and 3).
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.
@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.
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)
@bajtos I would be more than happy to contribute as well; please add me. Looking forward to contributing in LoopBack.next now.
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()
Hey @ritch I have few questions about code/design decisions that the project have made
Where is the best place to discus about it?
@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.
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
.
@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.
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 !
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!
@bajtos would love to help.
Hey guys! I would like to join the contributors team as well :-)
๐ @jseijas @kattsushi @yosbelms @ghulamhussain @lindoelio ๐
Invites sent! Thanks for your interest!
And welcome! :)
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/.
Hi @bajtos, I've been using loopback for months now.I would like to contribute to loopback-next as well!
Hi @bajtos I am new to loopback but would love to contribute to loopback-next. ๐
Hi @bajtos I am new to loopback too and would love to contribute in any way possible. Eagerly waiting for v4 release. Thanks.
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
If you decide to start working on one of those issues, then please leave a comment to let other potential contributors know.
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.
Invitations sent ๐ฌ
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.
Hi @ritch
I'd love to contribute to Loopback 4 thanks
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...
@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 ๐
Hi Everyone. I recently pushed my first contribution and I'm looking forward to contribute more in a more organized fashion :)
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 #110 (comment))
@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.
@bajtos same error as @joeytwiddle mentioned.
Upd.: I was able to accept the invitation on github.com/strongloop
.
@collaorodrigo7 invite sent.
@joeytwiddle @skanygin sorry for the confusion! I am glad you found the right URL where to accept the invite.
Hi,
I'd love to contribute to Loopback 4
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.
@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.
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.
@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.