Skip to content

Commit a5370d7

Browse files
SMartorelliSMartorelli
committed
Initial commit
1 parent cf8608c commit a5370d7

File tree

161 files changed

+9730
-2
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

161 files changed

+9730
-2
lines changed

Diff for: ‎.github/ISSUE_TEMPLATE/bug_report.md

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: "[BUG]"
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. macOS 11]
28+
- Project version [e.g. 1.0.0]
29+
30+
**Additional context**
31+
Add any other context about the problem here.

Diff for: ‎.github/ISSUE_TEMPLATE/feature_request.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: "[Feature Request]"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

Diff for: ‎.github/pull_request_template.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
*Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
2+
3+
*List which issues are fixed by this PR. You must list at least one issue.*
4+
5+
6+
## Pre-launch Checklist
7+
8+
- [ ] I read the [Code of Conduct](/CODE_OF_CONDUCT.md) and followed the process outlined there for submitting PRs.
9+
- [ ] I listed at least one issue that this PR fixes in the description above.
10+
- [ ] I updated/added relevant documentation (doc comments with `///`).
11+
- [ ] I updated [README.md](https://github.com/IBM/mac-ibm-migration-tool/blob/main/README.md) file with new version/info - if applicable.
12+
- [ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
13+
- [ ] All existing and new tests are passing.

Diff for: ‎.gitignore

+93
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
# Xcode
2+
#
3+
# gitignore contributors: remember to update Global/Xcode.gitignore, Objective-C.gitignore & Swift.gitignore
4+
5+
## User settings
6+
xcuserdata/
7+
8+
## compatibility with Xcode 8 and earlier (ignoring not required starting Xcode 9)
9+
*.xcscmblueprint
10+
*.xccheckout
11+
12+
## macOS
13+
**/.DS_Store
14+
15+
## compatibility with Xcode 3 and earlier (ignoring not required starting Xcode 4)
16+
build/
17+
DerivedData/
18+
*.moved-aside
19+
*.pbxuser
20+
!default.pbxuser
21+
*.mode1v3
22+
!default.mode1v3
23+
*.mode2v3
24+
!default.mode2v3
25+
*.perspectivev3
26+
!default.perspectivev3
27+
28+
## Obj-C/Swift specific
29+
*.hmap
30+
31+
## App packaging
32+
*.ipa
33+
*.dSYM.zip
34+
*.dSYM
35+
36+
## Playgrounds
37+
timeline.xctimeline
38+
playground.xcworkspace
39+
40+
# Swift Package Manager
41+
#
42+
# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
43+
# Packages/
44+
# Package.pins
45+
# Package.resolved
46+
# *.xcodeproj
47+
#
48+
# Xcode automatically generates this directory with a .xcworkspacedata file and xcuserdata
49+
# hence it is not needed unless you have added a package configuration file to your project
50+
# .swiftpm
51+
52+
.build/
53+
54+
# CocoaPods
55+
#
56+
# We recommend against adding the Pods directory to your .gitignore. However
57+
# you should judge for yourself, the pros and cons are mentioned at:
58+
# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
59+
#
60+
# Pods/
61+
#
62+
# Add this line if you want to avoid checking in source code from the Xcode workspace
63+
# *.xcworkspace
64+
65+
# Carthage
66+
#
67+
# Add this line if you want to avoid checking in source code from Carthage dependencies.
68+
# Carthage/Checkouts
69+
70+
Carthage/Build/
71+
72+
# Accio dependency management
73+
Dependencies/
74+
.accio/
75+
76+
# fastlane
77+
#
78+
# It is recommended to not store the screenshots in the git repo.
79+
# Instead, use fastlane to re-generate the screenshots whenever they are needed.
80+
# For more information about the recommended setup visit:
81+
# https://docs.fastlane.tools/best-practices/source-control/#source-control
82+
83+
fastlane/report.xml
84+
fastlane/Preview.html
85+
fastlane/screenshots/**/*.png
86+
fastlane/test_output
87+
88+
# Code Injection
89+
#
90+
# After new code Injection tools there's a generated folder /iOSInjectionProject
91+
# https://github.com/johnno1962/injectionforxcode
92+
93+
iOSInjectionProject/

Diff for: ‎.sonarcloud.properties

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Project Version to be used as Code Definition
2+
sonar.projectVersion=1.1.0.100
3+
# Folders excluded from the scan
4+
sonar.exclusions=**/migratorTests/**,**/migratorUITests/**

Diff for: ‎.swiftlint.yml

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
disabled_rules:
3+
- line_length
4+
- compiler_protocol_init
5+
- cyclomatic_complexity
6+
- notification_center_detachment
7+
- trailing_whitespace
8+
- colon

Diff for: ‎CODE_OF_CONDUCT.md

+128
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
the contact informations available on the MAINTAINERS.md resource.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

Diff for: ‎CONTRIBUTING.md

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
## Contributing In General
2+
Our project welcomes external contributions. If you have an itch, please feel
3+
free to scratch it.
4+
5+
To contribute code or documentation, please submit a [pull request](https://github.com/ibm/mac-ibm-migration-tool/pulls).
6+
7+
A good way to familiarize yourself with the codebase and contribution process is
8+
to look for and tackle low-hanging fruit in the [issue tracker](https://github.com/ibm/mac-ibm-migration-tool/issues).
9+
Before embarking on a more ambitious contribution, please quickly [get in touch](#communication) with us.
10+
11+
**Note: We appreciate your effort, and want to avoid a situation where a contribution
12+
requires extensive rework (by you or by us), sits in backlog for a long time, or
13+
cannot be accepted at all!**
14+
15+
### Proposing new features
16+
17+
If you would like to implement a new feature, please [raise an issue](https://github.com/ibm/mac-ibm-migration-tool/issues)
18+
before sending a pull request so the feature can be discussed. This is to avoid
19+
you wasting your valuable time working on a feature that the project developers
20+
are not interested in accepting into the code base.
21+
22+
### Fixing bugs
23+
24+
If you would like to fix a bug, please [raise an issue](https://github.com/ibm/mac-ibm-migration-tool/issues) before sending a
25+
pull request so it can be tracked.
26+
27+
### Merge approval
28+
29+
The project maintainers use LGTM (Looks Good To Me) in comments on the code
30+
review to indicate acceptance. A change requires LGTMs from two of the
31+
maintainers of each component affected.
32+
33+
For a list of the maintainers, see the [MAINTAINERS.md](MAINTAINERS.md) page.
34+
35+
## Legal
36+
37+
Each source file must include a license header for the Apache
38+
Software License 2.0. Using the SPDX format is the simplest approach.
39+
e.g.
40+
41+
```text
42+
//
43+
// © Copyright IBM Corp. 2023, 2024
44+
// SPDX-License-Identifier: Apache2.0
45+
//
46+
```
47+
48+
We have tried to make it as easy as possible to make contributions. This
49+
applies to how we handle the legal aspects of contribution. We use the
50+
same approach - the [Developer's Certificate of Origin 1.1 (DCO)](https://github.com/hyperledger/fabric/blob/master/docs/source/DCO1.1.txt) - that the Linux® Kernel [community](https://elinux.org/Developer_Certificate_Of_Origin)
51+
uses to manage code contributions.
52+
53+
We simply ask that when submitting a patch for review, the developer
54+
must include a sign-off statement in the commit message.
55+
56+
Here is an example Signed-off-by line, which indicates that the
57+
submitter accepts the DCO:
58+
59+
```
60+
Signed-off-by: John Doe <[email protected]>
61+
```
62+
63+
You can include this automatically when you commit a change to your
64+
local git repository using the following command:
65+
66+
```
67+
git commit -s
68+
```
69+
70+
## Communication
71+
Please feel free to connect with us by mail, see the [MAINTAINERS.md](MAINTAINERS.md) page.
72+
73+
## Testing
74+
Make sure that every Xcode Unit and UI test pass befor submitting any changes.
75+
76+
## Coding style guidelines
77+
Please follow the SwiftLintFramework rules.

Diff for: ‎MAINTAINERS.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# MAINTAINERS
2+
3+
Simone Martorelli - [email protected]

0 commit comments

Comments
 (0)