FTC Engineering 883696fac2 Update README.md
2018-09-13 10:34:48 -04:00
2018-09-13 08:32:55 -04:00
2018-09-13 10:34:48 -04:00

Welcome!

This GitHub repository can be used to download the FIRST Tech Challenge Live scorekeeper software. Also, if you have a GitHub user account, you can use the "Issues" database feature to report and track issues with the software.

Downloading the software

The software is available for download under the Releases page of this repository. Click on the "releases" link towards the upper right hand corner of the main page to navigate to the Release page.

Click on "releases" link to go to the Releases page.

Browse the releases page for version you are looking forward, and click on the appropriate link to download the archived software. The software is stored on the server as an archived .zip or .tar file. Note that most users (Windows and Mac users especially) will want to download the .zip format archive file. Once you have downloaded the archive file, uncompress the file using the appropriate tool for your computer.

Click on the file that you'd like to download.

Note that you want to download the "FIRST-Tech-Challenge-Live" archive file, and not the "Source code" file. The "Source code" file does not contain any usable content.

Documentation

Currently, the user documentation exists as a living Google Drive document. You can access the document using the following link:

  User Documentation for Scorekeeping Software

Reporting Issues

Click on the "Issues" link towards the upper left hand corner of the main page of this repository to navigate to the Issue Tracking Database page. If you are logged in to your GitHub user account (which is available for free from GitHub) you can create and reply to issues in the database.

The developers of the software requested that if you encounter a bug, you copy and archive (compress into .zip form) the "db" subdirectory and then create an issue on the Issues database and attach the .zip file to the newly created issue and save the attachment with the issue. The "db" folder is located in the "lib" subfolder.

Description
Another unofficial fork
Readme 132 KiB
2024-10-16 10:50:08 -04:00