Before opening a new issue, please check that no existing issue covers the same topic.
Hi guys. I am an aspiring full stack developer with knowledge in HTML, CSS, js, java, SQL. I would like to contribute my skills to an open source project and i found this TEAMMATES project. Someone help me start my first contribution here.

Corresponds to TEAMMATES/teammates#11736

• Fix links to the devGuide in the docs in this repository
• Fix the CONTRIBUTING_GUIDELINES parameter in the deployment config of the teammates doc to point to the correct link.

As part of TEAMMATES/teammates#12048, documentation to use Liquibase to migrate production schema.

Related to this TEAMMATES/teammates#12930 which is the teammates dev process for liquibase

As part of https://github.com/TEAMMATES/teammates/projects/8

Reference: TEAMMATES/teammates#4748

StatisticsPerInstitute is run at the end of every month to collect stats. This month, it is failing with this error:

------------------ iterations count:18000 ------------------------
------------------ iterations count:19000 ------------------------
------------------ iterations count:20000 ------------------------
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

Did we do something to the backend during last month which could have caused this error?

As per Slack discussion.

GitHub tags contributors in release notes if usernames are used. Arguably we should also move away from including user's actual names as it is an unnecessary addition to developers.json

https://developer.github.com/v3/users/

After recent migration to Cloud SDK, Cloud Scheduler API and Cloud Tasks API need to be manually enabled on Google Cloud Platform console before deploying ./gradlew appengineDeployAll.

From TEAMMATES/teammates#9074:

*********************************
Configuration Warning : <application>/<version> XML elements and --application/--version should not be specified when staging

The following parameters will be scrubbed from app.yaml
application : teammatesv4
version : 6-10-1

Future versions of staging will fail if application or version is specified.
*********************************

Changes to be made to community.md:

• Area leads as concurrent appointments
• Expand sample list of potential areas to lead (reference labels)
• Invite to slack channel threshold

Noticed there while following the dev docs when deploying the new V8. To be considered for tweaking the dev docs, if necessary (I could be wrong). Posting here for the record.

1. Mention that npm install should be run after pulling major changes from upstream?
2. config.ts should be mentioned here?
   
3. Dev environment: Change the JDK requirement 8 -> 11?
4. Should npm run build be run before deployment?
5. Mention that an 'Automatic' VPC network should be created before creating the solr VM, and the VM should be created in that network.
6. Update the solr version in https://github.com/TEAMMATES/teammates-ops/blob/master/scripts/solr-setup.sh

The platform-guide.md doesn't specify that the gradle deployAll task does not build the front-end files from Angular. Might be a useful reminder for new developers who want to set up their own staging server.

We no longer use the bot, instead GitHub Actions is used for the same duty.

Following PR #11891 in teammates, as Firebase Authentication is used, its corresponding setup should be documented.

More info can be found on the wiki at https://github.com/TEAMMATES/teammates/wiki/Authentication-Plus.

From TEAMMATES/teammates#8583:

The current backup cron job uses the Cloud Datastore Admin module, which is set to be decommissioned. Let's investigate the new managed export and import feature: https://cloudplatform.googleblog.com/2018/02/fully-managed-export-and-import-with-Cloud-Datastore-now-generally-available.html

Before opening a new issue, please check that no existing issue covers the same topic.

As part of teammate's v9 , documentation to create SQL instances and connect them on staging is necessary.

https://github.com/TEAMMATES/teammates-ops/blob/master/maintainer-guide.md#using-a-long-lived-feature-branch