-
Notifications
You must be signed in to change notification settings - Fork 24
Code Development
johnsm21 edited this page Aug 18, 2020
·
4 revisions
The Hadatac GitHub consists of three main branches: Master, LESA, and HHEAR. The Master branch is our stable release code that is updated after a sprint. The other two are project branches used to develop new features and address bugs. Developers should never merge changes directly into Master.
Projects branches are updated frequently using Github's issue/pull request system. A user wishing to make a change to the codebase must create an issue on GitHub, fork the repository, make the desired changes to a project branch and submit a pull request for review on GitHub. These steps are detailed below.
- Goto: https://github.com/paulopinheiro1234/hadatac/issues
- Check to see if your feature or bug already has an open issue
- If not then create a new issue using the new issue button
- Add a title
- Leave a detailed description
- For bugs include a description on how to recreate the bug
- For features include a description on how Hadatac should behave if this feature is implemented
- Assign a person to work on the issue using the gear button
- Leave blank if your assigning it to yourself
- If it's not you be sure to let them know
- Assign a label using the gear button
- Features → enhancement
- Bugs → bug
- Assign a project using the gear button
- This corresponds to the project the issue will be merged into either LESA or HHEAR
- Click “Submit new issue”
- Goto:
https://github.com/paulopinheiro1234/hadatac
- Click the "Fork" button in the top right
- Choose your GitHub account
- Go to your project folder location
cd project_folder_path
- Clone your fork
git clone https://github.com/<YourUsername>/hadatac.git
- Install HADatAc
- Go to your project folder through your command line
cd hadatac
- Add Hadatac Repository
git remote add hadatac git://github.com/paulopinheiro1234/hadatac.git
- Develop tests for the new feature or bug
- Create a Java class in project_folder/test
- Denote test methods with @Test
- Make code changes
- List changed files
git status
- Add changed files to a commit
git add file1 file2
- Do not add files specific to your configuration
- Commit files
git commit -m “Description of changes”
- Backup changes to Github
git push
- Run unit tests
sbt test
- Repeat steps 3-10 until complete (Feature implemented/bug fixed and tests pass)
- Merge development branch changes
git pull hadatac
- Check for conflicts
git status
- Resolve conflicts
- Repeat steps 3-14 until complete (Feature implemented/bug fixed and tests pass)
- Goto:
https://github.com/<YourUsername>/hadatac/pulls
- Click "New Pull Request"
- Set base using the dropdown and select the development branch
- Should be HHEAR or LESA
- Set compare using the dropdown and select the branch you're developing on
- Click “Create pull request” button
- Enter a title and detailed description
- These will look very similar to the issue if the pull request is addressing only one issue
- Assign a reviewer using the gear button
- This should never be you
- Be sure to let them know
- Assign a label using the gear button
- Features → enhancement
- Bugs → bug
- Assign a project using the gear button
- This corresponds to the project the issue will be merged into either LESA or HHEAR
- Select Issue addressed using the gear button
- Double-check the pull request information
- Don’t forget the base this should be HHEAR or LESA
- If the pull request is ready (approved) select “Squash and merge”
- This will convert all commits into a single commit
- This makes exploring the git history easier to search through
- Enter a final description for git history
- Submit changes
- This will merge changes and close all linked issues
Copyright (c) 2019, HADatAc.org
-
Installation
1.1. Installing for Linux (Production)
1.2. Installing for Linux (Development)
1.3. Installing for MacOS (Development)
1.4. Deploying with Docker (Production)
1.5. Deploying with Docker (Development)
1.6. Installing for Vagrant under Windows
1.7. Upgrading
1.8. Starting HADatAc
1.9. Stopping HADatAc -
Setting Up
2.1. Software Configuration
2.2. Knowledge Graph Bootstrap
2.2.1. Knowledge Graph
2.2.2. Bootstrap without Labkey
2.2.3. Bootstrap with Labkey
2.3. Config Verification -
Using HADatAc
3.1. Initial Page
3.1.1. Home Button
3.1.2. Sandbox Mode Button
3.2. File Ingestion
3.2.1. Ingesting Study Content
3.2.2. Manual Submission of Files
3.2.3. Automatic Submission of Files
3.2.4. Data File Operations
3.3. Manage Working Files 3.3.1. [Create Empty Semantic File from Template]
3.3.2. SDD Editor
3.3.3. DD Editor
3.4. Manage Metadata
3.4.1. Manage Instrument Infrastructure
3.4.2. Manage Deployments 3.4.3. Manage Studies
3.4.4. [Manage Object Collections]
3.4.5. Manage Streams
3.4.6. Manage Semantic Data Dictionaries
3.4.7. Manage Indicators
3.5. Data Search
3.5.1. Data Faceted Search
3.5.2. Data Spatial Search
3.6. Metadata Browser and Search
3.7. Knowledge Graph Browser
3.8. API
3.9. Data Download -
Software Architecture
4.1. Software Components
4.2. The Human-Aware Science Ontology (HAScO) -
Metadata Files
5.1. Deployment Specification (DPL)
5.2. Study Specification (STD)
5.3. Semantic Study Design (SSD)
5.4. Semantic Data Dictionary (SDD)
5.5. Stream Specification (STR) -
Content Evolution
6.1. Namespace List Update
6.2. Ontology Update
6.3. [DPL Update]
6.4. [SSD Update]
6.5. SDD Update -
Data Governance
7.1. Access Network
7.2. User Status, Categories and Access Permissions
7.3. Data and Metadata Privacy - HADatAc-Supported Projects
- Derived Products and Technologies
- Glossary