Skip to content

Commit 0bcb178

Browse files
committed
remove unnecessary blockquote
1 parent 07b7e7b commit 0bcb178

File tree

1 file changed

+26
-26
lines changed

1 file changed

+26
-26
lines changed

Guides/Official/OpenChain-in-Mergers-and-Acquisitions/2.0/en/Assessment-Of-OS-Practices-In-Merger-and-Acquisition.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -472,32 +472,32 @@ height="0.9791666666666666in"}
472472
***"Adaptation of Business Processes" focuses on fitting OSS compliance
473473
practices within the context of existing business processes.***
474474

475-
> - Existing business processes are modified to incorporate open source
476-
> compliance activities and considerations.
477-
>
478-
> - Compliance activities are mapped against the organization's
479-
> product development process to identify leverage points.
480-
>
481-
> - A process FMEA (failure mode effects analysis) is performed to
482-
> identify ways that compliance failures could occur and the
483-
> business processes that should be modified to prevent such
484-
> failures.
485-
>
486-
> - Supply chain's supplier selection procedures are tailored to ensure
487-
> that open source compliance requirements are considered when
488-
> performing due diligence on suppliers.
489-
>
490-
> - Process management ensures that open source compliance activities
491-
> are included early enough in the product development cycle to
492-
> enable the organization to meet its release timelines.
493-
>
494-
> - Late-cycle verification steps are used to ensure that all compliance
495-
> requirements have been met before external distribution occurs.
496-
>
497-
> - Individuals charged with managing business processes have received
498-
> training in open source compliance requirements and exhibit
499-
> sufficient understanding and experience with open source
500-
> compliance concerns.
475+
- Existing business processes are modified to incorporate open source
476+
compliance activities and considerations.
477+
478+
- Compliance activities are mapped against the organization's
479+
product development process to identify leverage points.
480+
481+
- A process FMEA (failure mode effects analysis) is performed to
482+
identify ways that compliance failures could occur and the
483+
business processes that should be modified to prevent such
484+
failures.
485+
486+
- Supply chain's supplier selection procedures are tailored to ensure
487+
that open source compliance requirements are considered when
488+
performing due diligence on suppliers.
489+
490+
- Process management ensures that open source compliance activities
491+
are included early enough in the product development cycle to
492+
enable the organization to meet its release timelines.
493+
494+
- Late-cycle verification steps are used to ensure that all compliance
495+
requirements have been met before external distribution occurs.
496+
497+
- Individuals charged with managing business processes have received
498+
training in open source compliance requirements and exhibit
499+
sufficient understanding and experience with open source
500+
compliance concerns.
501501

502502
## 8. Training
503503

0 commit comments

Comments
 (0)