|
| 1 | +--- |
| 2 | +category: "london" |
| 3 | +title: "TerminusDB Documentation + Django DRF API Tracking" |
| 4 | +level: "All" |
| 5 | +time: "18:30" |
| 6 | +meetup_link: https://www.meetup.com/Python-Sprints/events/269207483/ |
| 7 | +event_link: |
| 8 | +project: terminusdb |
| 9 | +image: |
| 10 | +sponsor: decibel |
| 11 | +--- |
| 12 | + |
| 13 | +We won't let the virus stop us from contribute to open-source (actually what is better than contributing when you are stying at home)? |
| 14 | + |
| 15 | +In this sprint, we are lucky to have Decibel hosting us, we will also be **streaming the presentation** by the maintainers via Zoom ([Join here](https://zoom.us/j/882305838)) and have a **chat room** at Gitter ([Join here](https://gitter.im/py-sprints/sprint-2020-03-23)) so you can either come to join us or sprint at home. |
| 16 | + |
| 17 | +We have 2 projects at this sprint: |
| 18 | + |
| 19 | +-------------------- |
| 20 | + |
| 21 | +### TerminusDB - documentation |
| 22 | + |
| 23 | +The first one is help writing docstrings for the Python client library of TerminusDB. The library consist of an API (which uses requests a lot), a query language (yup, query language in Python) and tools to work with pandas DataFrame. |
| 24 | + |
| 25 | +They use the same format of docstrings as numpy and pandas so it will be a good practice for writing docstrings without the stress of contributing to a huge project. (I can assure you your PR will be reviewed quickly). |
| 26 | + |
| 27 | +List of methods that need documentation is listed [here](https://github.com/terminusdb/documentation-sprint). |
| 28 | + |
| 29 | +You can also have a look at their [GitHub repo](https://github.com/terminusdb/terminus-client-python) and [issues](https://github.com/terminusdb/terminus-client-python/issues). |
| 30 | + |
| 31 | +-------------------- |
| 32 | + |
| 33 | +### DRF API Tracking |
| 34 | + |
| 35 | +DRF API Tracking provides a Django model and DRF view mixin that work together to log Django Rest Framework requests to the database. You'll get these attributes for every request/response cycle to a view that uses the mixin. |
| 36 | + |
| 37 | +Have a look at their [GitHub repo](https://github.com/lingster/drf-api-tracking) and [issues](https://github.com/lingster/drf-api-tracking/issues). |
| 38 | + |
| 39 | +-------------------- |
| 40 | + |
| 41 | +You can choose either one project to work on (or both if you know what you are doing :-P) |
| 42 | + |
| 43 | +For beginners in open-source, we will have a beginners table for making your first pull request on GitHub. |
| 44 | + |
| 45 | +As usual, we will give priority to join the sprint to the people who: |
| 46 | + |
| 47 | +- Experienced open source contributors |
| 48 | +- People from underrepresented minorities in our sprints |
| 49 | + |
| 50 | +There is **no limit** on remote participation. |
| 51 | + |
| 52 | +Agenda |
| 53 | +------ |
| 54 | + |
| 55 | +- 6:30pm: Networking, drinks and food |
| 56 | +- 7:00pm: Sponsor presentation, project presentations and team creation (Zoom starts here) |
| 57 | +- 7:20pm: Coding |
| 58 | +- 8:45pm: Group presentations |
| 59 | +- 9pm: End of the event, or pub |
| 60 | + |
| 61 | + |
| 62 | +The day of the sprint |
| 63 | +--------------------- |
| 64 | + |
| 65 | +- Bring your own laptop if you can |
| 66 | +- Join the [Gitter channel](https://gitter.im/py-sprints/sprint-2020-03-23) of the sprint |
| 67 | +- Join the [Telegram group](https://t.me/py_sprints) for the update and community news of Python Sprint |
| 68 | + |
| 69 | +Code of Conduct |
| 70 | +--------------- |
| 71 | + |
| 72 | +- Please be reminded that all participants (including remote participants) are expected to follow the [NumFOCUS Code of Conduct](https://numfocus.org/code-of-conduct) |
0 commit comments