I have tried to check some of the available tickets, but they seem conplicated for a beginner like me, are there simpler tickets for starters?
I have added more intro tickets. Can you take a second look?
2 Likes
kindly look at this and post you doubts if you have any… https://wiki.openmrs.org/display/docs/Getting+Started+as+a+Developer
@karolskolasinski Take a look at instruction number 6 under this https://wiki.openmrs.org/display/docs/Getting+Started+as+a+Developer.
To add on @emiriga suggestion,You dont need to download openmrs sdk , AM seeing you are trying to work on your ticket, it depends on which ticket that your working on here . Feel free to ask more questions to get more ideas
To be able to work on a ticket of your choice, kindly select a ticket from this jira site https://issues.openmrs.org/secure/Dashboard.jspa. Since its an introductory ticket, its complexity should be low and in a ready to work state more tips can be found on his link https://wiki.openmrs.org/display/docs/Tickets
Hopefully you are following every step outlined on the link @rishabh997 and @emiriga shared
before. Though you can run a standalone instance instead of SDK as stated by @sharif but still you have to ensure you have all the required soft wares in their correct versions for you will need them to build a successful project after making changes. That can be solved by following this link https://wiki.openmrs.org/display/docs/OpenMRS+SDK. As an individual I feel it will be better to download the SDK. Interact with the UI, create your first module, watch, play around with the app to get familiar with it by doing that when you work on tickets it will give you a clear picture on where to make the changes.
Thanks.
4 Likes
This might be something to incorporate into volunteer onboarding docs! Having a link to a maintained Wiki page with good tasks for someone just starting out. Tagging @jennifer for when she gets back from her hopefully restful vacation!
@madhens, yes! I think that page is a great place for developers to get started and maybe that is a part of the set of volunteer onboarding docs? I also like that it includes community priorities to pick from - and ask myself if those priorities could have its own stand alone page so that it’s easy for anyone in the community to find?
1 Like