-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/stable-3_4_0' into stable-3_4_0
- Loading branch information
Showing
2,085 changed files
with
231,708 additions
and
150,998 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
on: | ||
push: | ||
branches: | ||
- '*' | ||
pull_request: | ||
branches: | ||
['stable-3_4_0'] | ||
|
||
name: omp | ||
jobs: | ||
omp: | ||
runs-on: ubuntu-latest | ||
strategy: | ||
fail-fast: false | ||
matrix: | ||
include: | ||
- php-version: 8.1 | ||
validate: 'validate' | ||
- php-version: 8.1 | ||
database: pgsql | ||
test: 'test' | ||
- php-version: 8.1 | ||
database: mariadb | ||
test: 'test' | ||
- php-version: 8.1 | ||
database: mysql | ||
test: 'test' | ||
upgrade: 'upgrade' | ||
upgrade_test: '3.1.0,3.1.1-2,3.1.2,stable-3_2_0,stable-3_2_1,stable-3_3_0' | ||
- php-version: 8.2 | ||
database: mysql | ||
test: 'test' | ||
- php-version: 8.2 | ||
database: pgsql | ||
test: 'test' | ||
|
||
|
||
|
||
name: omp | ||
steps: | ||
- uses: pkp/pkp-github-actions@v1 | ||
with: | ||
node_version: 16 | ||
dataset_branch: 'stable-3_4_0' | ||
DATASETS_ACCESS_KEY: ${{secrets.DATASETS_ACCESS_KEY}} | ||
DEBUG_IN_TMATE: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
<?php | ||
|
||
$finder = PhpCsFixer\Finder::create() | ||
->in(__DIR__) | ||
->name('*.php') | ||
// The next two rules are enabled by default, kept for clarity | ||
->ignoreDotFiles(true) | ||
->ignoreVCS(true) | ||
// The pattern is matched against each found filename, thus: | ||
// - The "/" is needed to avoid having "vendor" match "Newsvendor.php" | ||
// - The presence of "node_modules" here doesn't prevent the Finder from recursing on it, so we merge these paths below at the "exclude()" | ||
->notPath($ignoredDirectories = ['cypress/', 'js/', 'locale/', 'node_modules/', 'styles/', 'templates/', 'vendor/']) | ||
// Ignore root based directories | ||
->exclude(array_merge($ignoredDirectories, ['cache', 'dbscripts', 'docs', 'lib', 'public', 'registry', 'schemas'])) | ||
// Ignores Git folders | ||
->notPath((function () { | ||
$recursiveIterator = new RecursiveIteratorIterator( | ||
new RecursiveDirectoryIterator(__DIR__ . '/plugins', FilesystemIterator::SKIP_DOTS | FilesystemIterator::UNIX_PATHS | FilesystemIterator::CURRENT_AS_FILEINFO), | ||
RecursiveIteratorIterator::SELF_FIRST | ||
); | ||
$recursiveIterator->setMaxDepth(1); | ||
$gitFolders = new CallbackFilterIterator( | ||
$recursiveIterator, | ||
fn (SplFileInfo $file) => $recursiveIterator->getDepth() === $recursiveIterator->getMaxDepth() | ||
&& $file->isDir() | ||
// Covers submodules (.git file) and external repositories (.git directory) | ||
&& file_exists("{$file}/.git") | ||
); | ||
$folders = []; | ||
foreach ($gitFolders as $folder) { | ||
$folders[] = str_replace(__DIR__ . '/', '', $folder); | ||
} | ||
return $folders; | ||
})()); | ||
|
||
$rules = include './lib/pkp/.php_cs_rules'; | ||
$config = new PhpCsFixer\Config(); | ||
return $config->setRules($rules) | ||
->setFinder($finder); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,58 +1,35 @@ | ||
# Open Monograph Press | ||
|
||
> Open Monograph Press (OMP) has been developed by the Public Knowledge Project. For general information about OMP and other open research systems, visit the [PKP web site][pkp]. | ||
[![Build Status](https://app.travis-ci.com/pkp/omp.svg?branch=main)](https://app.travis-ci.com/pkp/omp) | ||
[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/pkp/omp/badges/quality-score.png?b=main)](https://scrutinizer-ci.com/g/pkp/omp/?branch=main) | ||
|
||
[![Build Status](https://travis-ci.org/pkp/omp.svg?branch=stable-3_3_0)](https://travis-ci.org/pkp/omp) | ||
Open Monograph Press (OMP) is open source software developed by the [Public Knowledge Project](https://pkp.sfu.ca/) to manage scholarly presses. [Learn More](https://pkp.sfu.ca/software/omp/) | ||
|
||
## Documentation | ||
## Usage | ||
|
||
You will find detailed guides in [docs](docs) folder. | ||
Read one of these guides to get started using OMP: | ||
|
||
## Using Git development source | ||
- Read the [Admin Guide](https://docs.pkp.sfu.ca/admin-guide/) to learn how to install and configure the application from an official release package. Use this guide to deploy to production. | ||
- Read the [Getting Started](https://docs.pkp.sfu.ca/dev/documentation/en/getting-started) guide to learn how to install the application from this source repository. Use this guide for local development. | ||
|
||
Checkout submodules and copy default configuration : | ||
Visit our [Documentation Hub](https://docs.pkp.sfu.ca/) for user guides, tutorials, and technical documentation. | ||
|
||
git submodule update --init --recursive | ||
cp config.TEMPLATE.inc.php config.inc.php | ||
## Bugs / Feature Requests | ||
|
||
Install or update dependencies via Composer (https://getcomposer.org/): | ||
> ⚠️ If you have found a security risk or vulnerability, please read our [security policy](SECURITY.md). | ||
composer --working-dir=lib/pkp install | ||
composer --working-dir=plugins/paymethod/paypal install | ||
All issues should be filed at the [pkp/pkp-lib](https://github.com/pkp/pkp-lib/issues/) repository. Feature requests can be made at our [Community Forum](https://forum.pkp.sfu.ca/). Learn more about how to [report a problem](https://docs.pkp.sfu.ca/dev/contributors/#report-a-problem). | ||
|
||
Install or update dependencies via [NPM](https://www.npmjs.com/): | ||
## Community Code of Conduct | ||
|
||
# install [nodejs](https://nodejs.org/en/) if you don't already have it | ||
npm install | ||
npm run build | ||
This repository is a PKP community space. All activities here are governed by [PKP's Code of Conduct](https://pkp.sfu.ca/code-of-conduct/). Please review the Code and help us create a welcoming environment for all participants. | ||
|
||
If your PHP version supports built-in development server : | ||
## Contributions | ||
|
||
php -S localhost:8000 | ||
|
||
See [Development documentation](https://docs.pkp.sfu.ca/dev/) for more complete development guidance. | ||
|
||
## Bugs / Issues | ||
|
||
See https://github.com/pkp/pkp-lib/#issues for information on reporting issues. | ||
|
||
## Running Tests | ||
|
||
See [Unit Tests](https://pkp.sfu.ca/wiki/index.php?title=Unit_Tests), and also [Github Documentation for PKP Contributors](https://pkp.sfu.ca/wiki/index.php?title=Github_Documentation_for_PKP_Contributors) for Travis-based continuous integration testing. | ||
Read the [Contributor's Guide](https://docs.pkp.sfu.ca/dev/contributors/) to learn how to make a pull request. This document describes our code formatting guidelines as well as information about how we organize stable branches and submodules. | ||
|
||
## License | ||
|
||
This software is released under the the [GNU General Public License][gpl-licence]. | ||
|
||
See the file [COPYING][gpl-licence] included with this distribution for the terms | ||
of this license. | ||
|
||
Third parties are welcome to modify and redistribute OJS in entirety or parts | ||
according to the terms of this license. PKP also welcomes patches for | ||
improvements or bug fixes to the software. | ||
This software is released under the the GNU General Public License. See the file `docs/COPYING` included with this distribution for the terms of this license. | ||
|
||
[pkp]: http://pkp.sfu.ca/ | ||
[readme]: docs/README | ||
[wiki-dev]: http://pkp.sfu.ca/wiki/index.php/HOW-TO_check_out_PKP_applications_from_git | ||
[php-unit]: http://phpunit.de/ | ||
[gpl-licence]: docs/COPYING | ||
Third parties are welcome to modify and redistribute OMP in entirety or parts according to the terms of this license. PKP also welcomes patches for improvements or bug fixes to the software. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
| Version | Supported | End Of Life | | ||
| ------- | ----------------------------------------------------- | ------------- | | ||
| 3.5.x | :x: Pre-release | 2026 (est) | | ||
| 3.4.x | :heavy_check_mark: Active development | 2025 (est) | | ||
| 3.3.x | :heavy_check_mark: Active maintenance | 2026 (est) | | ||
| 3.2.x | :x: Not supported | 2023 | | ||
| 3.1.x | :x: Not supported | 2022 | | ||
| 1.x | :x: Security only; upgrade recommended | 2022 | | ||
|
||
## Reporting a Vulnerability | ||
|
||
To report a vulnerability, please contact PKP privately using: [email protected] | ||
|
||
You can expect a response via email to acknowledge your report within 2 working days. | ||
|
||
PKP will then work to verify the vulnerability and assess the risk. This is typically done within the first week of a report. Once these details are known, PKP will file a Github issue entry with limited details for tracking purposes. This initial report will not include enough information to fully disclose the vulnerability but will serve as a point of reference for development and fixes once they are available. | ||
|
||
When a fix is available, PKP will contact its user community privately via mailing list with details of the fix, and leave a window of typically 2 weeks for community members to patch or upgrade before public disclosure. | ||
|
||
PKP then discloses the vulnerability publicly by updating the Github issue entry with complete details and adding a notice about the vulnerability to the software download page (e.g. https://pkp.sfu.ca/software/omp). At this point, a CVE and credit for the discovery may be added to the entry. | ||
|
||
Depending on the severity of the issue PKP may back-port fixes to releases that are beyond the formal software end-of-life. | ||
|
||
We aim to have a fix available within a week of notification. |
Oops, something went wrong.