Skip to content

Commit bf3a4a8

Browse files
committed
Added ROADMAP to the Project
1 parent c40ce98 commit bf3a4a8

File tree

3 files changed

+89
-19
lines changed

3 files changed

+89
-19
lines changed

β€ŽREADME.mdβ€Ž

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
1-
Please read [UPGRADE-v2.0.md](/UPGRADE-v2.0.md) to learn how to upgrade to Graphene `2.0`.
1+
**We are looking for contributors**! Please check the [ROADMAP](https://github.com/graphql-python/graphene/blob/master/ROADMAP.md) to see how you can help ❀️
22

33
---
44

55
# ![Graphene Logo](http://graphene-python.org/favicon.png) [Graphene](http://graphene-python.org) [![Build Status](https://travis-ci.org/graphql-python/graphene.svg?branch=master)](https://travis-ci.org/graphql-python/graphene) [![PyPI version](https://badge.fury.io/py/graphene.svg)](https://badge.fury.io/py/graphene) [![Coverage Status](https://coveralls.io/repos/graphql-python/graphene/badge.svg?branch=master&service=github)](https://coveralls.io/github/graphql-python/graphene?branch=master)
66

7-
87
[Graphene](http://graphene-python.org) is a Python library for building GraphQL schemas/types fast and easily.
98

109
- **Easy to use:** Graphene helps you use GraphQL in Python without effort.
@@ -13,17 +12,16 @@ Please read [UPGRADE-v2.0.md](/UPGRADE-v2.0.md) to learn how to upgrade to Graph
1312
We believe that by providing a complete API you could plug Graphene anywhere your data lives and make your data available
1413
through GraphQL.
1514

16-
1715
## Integrations
1816

1917
Graphene has multiple integrations with different frameworks:
2018

21-
| integration | Package |
22-
|---------------|-------------------|
23-
| Django | [graphene-django](https://github.com/graphql-python/graphene-django/) |
24-
| SQLAlchemy | [graphene-sqlalchemy](https://github.com/graphql-python/graphene-sqlalchemy/) |
25-
| Google App Engine | [graphene-gae](https://github.com/graphql-python/graphene-gae/) |
26-
| Peewee | *In progress* ([Tracking Issue](https://github.com/graphql-python/graphene/issues/289)) |
19+
| integration | Package |
20+
| ----------------- | --------------------------------------------------------------------------------------- |
21+
| Django | [graphene-django](https://github.com/graphql-python/graphene-django/) |
22+
| SQLAlchemy | [graphene-sqlalchemy](https://github.com/graphql-python/graphene-sqlalchemy/) |
23+
| Google App Engine | [graphene-gae](https://github.com/graphql-python/graphene-gae/) |
24+
| Peewee | _In progress_ ([Tracking Issue](https://github.com/graphql-python/graphene/issues/289)) |
2725

2826
Also, Graphene is fully compatible with the GraphQL spec, working seamlessly with all GraphQL clients, such as [Relay](https://github.com/facebook/relay), [Apollo](https://github.com/apollographql/apollo-client) and [gql](https://github.com/graphql-python/gql).
2927

@@ -39,7 +37,6 @@ pip install "graphene>=2.0"
3937

4038
Please read [UPGRADE-v2.0.md](/UPGRADE-v2.0.md) to learn how to upgrade.
4139

42-
4340
## Examples
4441

4542
Here is one example for you to get started:
@@ -67,9 +64,8 @@ result = schema.execute(query)
6764

6865
If you want to learn even more, you can also check the following [examples](examples/):
6966

70-
* **Basic Schema**: [Starwars example](examples/starwars)
71-
* **Relay Schema**: [Starwars Relay example](examples/starwars_relay)
72-
67+
- **Basic Schema**: [Starwars example](examples/starwars)
68+
- **Relay Schema**: [Starwars Relay example](examples/starwars_relay)
7369

7470
## Contributing
7571

@@ -90,7 +86,7 @@ py.test PATH/TO/MY/DIR/ # All tests in directory
9086

9187
Add the `-s` flag if you have introduced breakpoints into the code for debugging.
9288
Add the `-v` ("verbose") flag to get more detailed test output. For even more detailed output, use `-vv`.
93-
Check out the [pytest documentation](https://docs.pytest.org/en/latest/) for more options and test running controls.
89+
Check out the [pytest documentation](https://docs.pytest.org/en/latest/) for more options and test running controls.
9490

9591
You can also run the benchmarks with:
9692

@@ -99,13 +95,17 @@ py.test graphene --benchmark-only
9995
```
10096

10197
Graphene supports several versions of Python. To make sure that changes do not break compatibility with any of those versions, we use `tox` to create virtualenvs for each python version and run tests with that version. To run against all python versions defined in the `tox.ini` config file, just run:
98+
10299
```sh
103100
tox
104101
```
102+
105103
If you wish to run against a specific version defined in the `tox.ini` file:
104+
106105
```sh
107106
tox -e py36
108107
```
108+
109109
Tox can only use whatever versions of python are installed on your system. When you create a pull request, Travis will also be running the same tests and report the results, so there is no need for potential contributors to try to install every single version of python on their own system ahead of time. We appreciate opening issues and pull requests to make graphene even more stable & useful!
110110

111111
### Documentation

β€ŽREADME.rstβ€Ž

Lines changed: 42 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
Please read `UPGRADE-v2.0.md </UPGRADE-v2.0.md>`__ to learn how to
2-
upgrade to Graphene ``2.0``.
1+
**We are looking for contributors**! Please check the
2+
`ROADMAP <https://github.com/graphql-python/graphene/blob/master/ROADMAP.md>`__
3+
to see how you can help ❀️
34

45
--------------
56

@@ -91,24 +92,60 @@ If you want to learn even more, you can also check the following
9192
Contributing
9293
------------
9394

94-
After cloning this repo, ensure dependencies are installed by running:
95+
After cloning this repo, create a
96+
`virtualenv <https://virtualenv.pypa.io/en/stable/>`__ and ensure
97+
dependencies are installed by running:
9598

9699
.. code:: sh
97100
101+
virtualenv venv
102+
source venv/bin/activate
98103
pip install -e ".[test]"
99104
100-
After developing, the full test suite can be evaluated by running:
105+
Well-written tests and maintaining good test coverage is important to
106+
this project. While developing, run new and existing tests with:
101107

102108
.. code:: sh
103109
104-
py.test graphene --cov=graphene --benchmark-skip # Use -v -s for verbose mode
110+
py.test PATH/TO/MY/DIR/test_test.py # Single file
111+
py.test PATH/TO/MY/DIR/ # All tests in directory
112+
113+
Add the ``-s`` flag if you have introduced breakpoints into the code for
114+
debugging. Add the ``-v`` ("verbose") flag to get more detailed test
115+
output. For even more detailed output, use ``-vv``. Check out the
116+
`pytest documentation <https://docs.pytest.org/en/latest/>`__ for more
117+
options and test running controls.
105118

106119
You can also run the benchmarks with:
107120

108121
.. code:: sh
109122
110123
py.test graphene --benchmark-only
111124
125+
Graphene supports several versions of Python. To make sure that changes
126+
do not break compatibility with any of those versions, we use ``tox`` to
127+
create virtualenvs for each python version and run tests with that
128+
version. To run against all python versions defined in the ``tox.ini``
129+
config file, just run:
130+
131+
.. code:: sh
132+
133+
tox
134+
135+
If you wish to run against a specific version defined in the ``tox.ini``
136+
file:
137+
138+
.. code:: sh
139+
140+
tox -e py36
141+
142+
Tox can only use whatever versions of python are installed on your
143+
system. When you create a pull request, Travis will also be running the
144+
same tests and report the results, so there is no need for potential
145+
contributors to try to install every single version of python on their
146+
own system ahead of time. We appreciate opening issues and pull requests
147+
to make graphene even more stable & useful!
148+
112149
Documentation
113150
~~~~~~~~~~~~~
114151

β€ŽROADMAP.mdβ€Ž

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Graphene Roadmap
2+
3+
In order to move Graphene and the GraphQL Python ecosystem forward I realized is essential to be clear with the community on next steps, so we can move uniformly.
4+
5+
There are few key points that need to happen in the short/mid term, divided into two main sections:
6+
7+
- [Community](#community)
8+
- [Graphene 3](#graphene-3)
9+
10+
_πŸ‘‹ If you have more ideas on how to move the Graphene ecosystem forward, don't hesistate to [open a PR](https://github.com/graphql-python/graphene/edit/master/ROADMAP.md)_
11+
12+
## Community
13+
14+
The goal is to improve adoption and sustainability of the project.
15+
16+
- πŸ’Ž Add Commercial Support for Graphene #813
17+
- Create Patreon page
18+
- Add /support page in Graphene website
19+
- πŸ“˜ Vastly improve documentation #823
20+
- πŸ’° Apply for [Mozilla MOSS](https://www.mozilla.org/en-US/moss/) sponsorship
21+
22+
## Graphene 3
23+
24+
The goal is to summarize the different improvements that Graphene will need to accomplish for version 3.
25+
26+
In a nushell, Graphene 3 should take the Python 3 integration one step forward while still maintaining compatibility with Python 2.
27+
28+
- πŸš€ [graphql-core-next](https://github.com/graphql-python/graphql-core-next) GraphQL engine support (almost same API as graphql-core)
29+
- πŸ”Έ GraphQL types from type annotations #729
30+
- πŸ“„ Schema creation from SDL (API TBD)
31+
- ✨ Improve connections structure
32+
- πŸ“— Improve function documentation
33+
- πŸ”€ Add support for coroutines in Connection, Mutation (abstracting out Promise requirement)

0 commit comments

Comments
Β (0)