Looking forward to contribute to open source MIT App Inventor

Open Source Development
1

Good Morning,
I'm Reshma Shaik, Java Developer with experience in Java, OOPs and file and data handling in the past. After career break looking for an opportunity to re-enter the field. I have mastered Java, Spring and Hibernate certifications in IBM and still dedicated to learning.
Came across MIT App Inventor, eager to contribute to it. I am almost there to setup environment in my local. Working with cloud setup. Hope any one there will guide me if I have issues. Looking forward to working with MIT App Inventor.

Thanks
Reshma

2

Welcome Reshma,
Search for issues tagged with "help wanted" in GitHub:

Present your proposal once you have identified an issue that you are confident in working with, and it will be assigned to you.

If you require help setting up your local environment, please post it here or on GitHub.

3

Thank you. I will look into it once I finish setting up. I am trying to find 'Apple Developer Portal'. I will post it in github link.

Thanks ,
Reshma Shaik

4

You only need to worry about setting up an Apple Developer account if you plan to contribute to the iOS development. If not, you can skip that section. Based on your experience, projects targeting the web interface or the Android app seem like they would fit well.

5

I followed the instructions as per README file. My main server and local server are running. I got this warning :slight_smile: BuildServer:
[copy] Warning: Could not find file C:\MIT_appinventor-sources\appinventor-sources\appinventor\build\components-ios\PlayerApp-unsigned.ipa to copy.
I am able to see this page.

login
login1920×1020 57.5 KB

And I see in my local components tab appinventor-sources\appinventor/docs/markdown/reference/components/
.md files show M as Modified, when I did not modify any.

Want to make sure everything is fine before starting.

Thanks
Reshma

6

This is expected for everyone not working on the iOS build system, which requires a particular setup on macOS. Since you are on Windows so you can safely ignore this message.

My guess is that this could be a line ending issue. Our files are stored with Unix style line endings (\n) but Windows by default uses \r\n. I would recommend avoiding committing these changes. We can always rebuild documentation on our end.

7

Thank you for the update.

8

I see there are lot of issues but all are taken. Can you suggest me the type of issues to look into?
Additionally should the PR be from my feature branch to staging?