Skip to content

Commit

Permalink
Merge pull request #125 from Seshat-Global-History-Databank/team
Browse files Browse the repository at this point in the history
Initial draft of team page
  • Loading branch information
edwardchalstrey1 authored Oct 15, 2024
2 parents d40cd30 + 6e04d5a commit 637bc01
Show file tree
Hide file tree
Showing 2 changed files with 55 additions and 6 deletions.
9 changes: 6 additions & 3 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
@@ -1,20 +1,23 @@
Seshat: Global History Databank
===============================

Project Documentation
---------------------

This site includes documentation for the Seshat project, such as how-to guides and technical guidance applicable to those working on, or contributing to Seshat.

The purpose is to provide a comprehensive knowledge sharing resource for all aspects of Seshat, including tools for working with the Seshat website and database, as well as reproducible research methods and code.

Project Roles
-------------

The documentation is divided into sections based on the role of the reader, which match the access level of accounts on the Seshat website. These roles are defined as follows:

1. Seshat Databank Admin: A member of the Seshat team responsible for the maintenance and development of the Seshat codebase, database and website.
2. Researcher: Any researcher contributing to, or consuming, the Seshat data as part of an ongoing Seshat affiliated project.
3. Seshat Expert: A collaborator with the necessary expertise and permission to approve or reject changes to the Seshat data.
4. Public User: An academic or other interested party who has created an account on the Seshat website to suggest data edits.

Project Documentation
---------------------

.. toctree::
:maxdepth: 2

Expand Down
52 changes: 49 additions & 3 deletions docs/source/team.rst
Original file line number Diff line number Diff line change
@@ -1,14 +1,60 @@
Team
====

A full list of people who have contributed to the project can be found on the project info website's `who we are <https://seshatdatabank.info/seshat-about-us/seshat-who-we-are>`_ page.

Contact
-------
This page intends to be a useful place to find out who is currently working on the project, how to get in touch with them and what they can help you with.

If you are new to the team, please add your details to the "Bios" section below.
To do this follow the guide on `how to update these docs <how-to-update-these-docs.rst>`_.
Follow the example of the existing bios, adding the following sections:

- **Who am I?** A brief introduction to who you are.
- **What can I help with?** A list of things you can help with.
- **Administrative privileges:** This is your access level on `seshat-db.com` which should be one of the following:

- Seshat Admin
- Research Assistant
- Seshat Expert
- Public User

Who can help me if...
.. note::
Project roles that match the above access levels are defined `here <index.rst>`_.

Bios
----

Ed Chalstrey
~~~~~~~~~~~~

**Who am I?**

- Research Software Engineer at the Alan Turing Institute
- Working on the Seshat project from November 2023 until March 2025

**What can I help with?**

- Seshat website codebase, in particular the maps pages
- Seshat API Python package
- Cliopatria shape dataset
- Software Engineering & Data Science skills

**Administrative privileges:** Seshat Admin

Contact
-------

If you need to contact someone from the team, email them or use one of the communication channels listed below.

- For emails of Complexity Science Hub staff, please refer to the `CSH staff page <https://www.csh.ac.at/people/>`_.
- Alan Turing Institute staff emails are listed here:
- Ed Chalstrey: `[email protected]`
- Pieter Francois: `[email protected]`
- Kalle Westerling: `[email protected]`
- Matilda Peruzzo: `[email protected]`

Communication channels
----------------------

- Complexity Science Hub: *TODO*
- Alan Turing Institute: On the institute's Slack workspace, request to join the `#data-culture` and `#seshat-turing` channels.

0 comments on commit 637bc01

Please sign in to comment.