-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
134 changed files
with
2,561 additions
and
10,993 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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
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,50 @@ | ||
# -*- coding: utf-8 -*- | ||
# | ||
# This file is part of Invenio. | ||
# Copyright (C) 2016 CERN. | ||
# | ||
# Invenio is free software; you can redistribute it | ||
# and/or modify it under the terms of the GNU General Public License as | ||
# published by the Free Software Foundation; either version 2 of the | ||
# License, or (at your option) any later version. | ||
# | ||
# Invenio is distributed in the hope that it will be | ||
# useful, but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | ||
# General Public License for more details. | ||
# | ||
# You should have received a copy of the GNU General Public License | ||
# along with Invenio; if not, write to the | ||
# Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, | ||
# MA 02111-1307, USA. | ||
# | ||
# In applying this license, CERN does not | ||
# waive the privileges and immunities granted to it by virtue of its status | ||
# as an Intergovernmental Organization or submit itself to any jurisdiction. | ||
|
||
|
||
# TODO: Transifex integration | ||
# | ||
# 1) Create message catalog: | ||
# $ python setup.py extract_messages | ||
# $ python setup.py init_catalog -l <lang> | ||
# $ python setup.py compile_catalog | ||
# 2) Ensure project has been created on Transifex under the inveniosoftware | ||
# organisation. | ||
# 3) Install the transifex-client | ||
# $ pip install transifex-client | ||
# 4) Push source (.pot) and translations (.po) to Transifex | ||
# $ tx push -s -t | ||
# 5) Pull translations for a single language from Transifex | ||
# $ tx pull -l <lang> | ||
# 6) Pull translations for all languages from Transifex | ||
# $ tx pull -a | ||
|
||
[main] | ||
host = https://www.transifex.com | ||
|
||
[invenio-workflows.messagespot] | ||
file_filter = invenio_workflows/translations/<lang>/LC_MESSAGES/messages.po | ||
source_file = invenio_workflows/translations/messages.pot | ||
source_lang = en | ||
type = PO |
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,113 @@ | ||
Contributing | ||
============ | ||
|
||
Contributions are welcome, and they are greatly appreciated! Every | ||
little bit helps, and credit will always be given. | ||
|
||
Types of Contributions | ||
---------------------- | ||
|
||
Report Bugs | ||
~~~~~~~~~~~ | ||
|
||
Report bugs at https://github.com/inveniosoftware/invenio-workflows/issues. | ||
|
||
If you are reporting a bug, please include: | ||
|
||
* Your operating system name and version. | ||
* Any details about your local setup that might be helpful in troubleshooting. | ||
* Detailed steps to reproduce the bug. | ||
|
||
Fix Bugs | ||
~~~~~~~~ | ||
|
||
Look through the GitHub issues for bugs. Anything tagged with "bug" | ||
is open to whoever wants to implement it. | ||
|
||
Implement Features | ||
~~~~~~~~~~~~~~~~~~ | ||
|
||
Look through the GitHub issues for features. Anything tagged with "feature" | ||
is open to whoever wants to implement it. | ||
|
||
Write Documentation | ||
~~~~~~~~~~~~~~~~~~~ | ||
|
||
invenio-workflows could always use more documentation, whether as part of the | ||
official invenio-workflows docs, in docstrings, or even on the web in blog posts, | ||
articles, and such. | ||
|
||
Submit Feedback | ||
~~~~~~~~~~~~~~~ | ||
|
||
The best way to send feedback is to file an issue at | ||
https://github.com/inveniosoftware/invenio-workflows/issues. | ||
|
||
If you are proposing a feature: | ||
|
||
* Explain in detail how it would work. | ||
* Keep the scope as narrow as possible, to make it easier to implement. | ||
* Remember that this is a volunteer-driven project, and that contributions | ||
are welcome :) | ||
|
||
Get Started! | ||
------------ | ||
|
||
Ready to contribute? Here's how to set up `invenio` for local development. | ||
|
||
1. Fork the `invenio` repo on GitHub. | ||
2. Clone your fork locally: | ||
|
||
.. code-block:: console | ||
$ git clone git@github.com:your_name_here/invenio-workflows.git | ||
3. Install your local copy into a virtualenv. Assuming you have | ||
virtualenvwrapper installed, this is how you set up your fork for local | ||
development: | ||
|
||
.. code-block:: console | ||
$ mkvirtualenv invenio-workflows | ||
$ cd invenio-workflows/ | ||
$ pip install -e .[all] | ||
4. Create a branch for local development: | ||
|
||
.. code-block:: console | ||
$ git checkout -b name-of-your-bugfix-or-feature | ||
Now you can make your changes locally. | ||
|
||
5. When you're done making changes, check that your changes pass tests: | ||
|
||
.. code-block:: console | ||
$ ./run-tests.sh | ||
The tests will provide you with test coverage and also check PEP8 | ||
(code style), PEP257 (documentation), flake8 as well as build the Sphinx | ||
documentation and run doctests. | ||
|
||
6. Commit your changes and push your branch to GitHub: | ||
|
||
.. code-block:: console | ||
$ git add . | ||
$ git commit -s -m "Your detailed description of your changes." | ||
$ git push origin name-of-your-bugfix-or-feature | ||
7. Submit a pull request through the GitHub website. | ||
|
||
Pull Request Guidelines | ||
----------------------- | ||
|
||
Before you submit a pull request, check that it meets these guidelines: | ||
|
||
1. The pull request should include tests and must not decrease test coverage. | ||
2. If the pull request adds functionality, the docs should be updated. Put | ||
your new functionality into a function with a docstring. | ||
3. The pull request should work for Python 2.7, 3.3, 3.4 and 3.5. Check | ||
https://travis-ci.com/inveniosoftware/invenio-workflows/pull_requests | ||
and make sure that the tests pass for all supported Python versions. |
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,8 @@ | ||
Installation | ||
============ | ||
|
||
You can install ``invenio-workflows`` from PyPI: | ||
|
||
.. code-block:: console | ||
pip install invenio-workflows --pre |
Oops, something went wrong.