Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add historical roles #324

Merged
merged 45 commits into from
Dec 19, 2023
Merged
Show file tree
Hide file tree
Changes from 23 commits
Commits
Show all changes
45 commits
Select commit Hold shift + click to select a range
0ca41fd
add historical roles
lilyminium Sep 23, 2023
0aab970
Update pages/team.md
lilyminium Sep 24, 2023
caabe95
Update pages/team.md
lilyminium Sep 24, 2023
ff8c831
Update pages/team.md
lilyminium Sep 24, 2023
0c0f4af
Update pages/team.md
lilyminium Sep 24, 2023
1e23b85
Update pages/team.md
lilyminium Sep 24, 2023
d80d935
update with notes on how far back and who to contact
lilyminium Sep 24, 2023
603127e
update year
lilyminium Sep 26, 2023
9d258a5
Update pages/team.md
fiona-naughton Nov 2, 2023
d7223bf
Update pages/team.md
fiona-naughton Nov 2, 2023
08224ec
Update pages/team.md
fiona-naughton Nov 2, 2023
a0d7347
Update pages/team.md
fiona-naughton Nov 2, 2023
29a21cf
Update pages/team.md
fiona-naughton Nov 2, 2023
a1981b5
Update pages/team.md
fiona-naughton Nov 2, 2023
3176e44
Update pages/team.md
fiona-naughton Nov 2, 2023
ba29021
Update pages/team.md
fiona-naughton Nov 2, 2023
1617afd
re-format table as yaml
lilyminium Nov 4, 2023
fb1df54
add readme for editing
lilyminium Nov 4, 2023
0443f64
change table headings
lilyminium Nov 4, 2023
769e12a
update text
lilyminium Nov 4, 2023
835bec7
add note about emeritus core devs
lilyminium Nov 4, 2023
56b76df
add note about current column year
lilyminium Nov 4, 2023
e177bd5
fix ci
lilyminium Nov 4, 2023
130d171
Update _data/team/roles/code_of_conduct.yml
lilyminium Nov 8, 2023
a8c4d25
Update _data/team/roles/continuous_integration.yml
lilyminium Nov 8, 2023
4c62a3b
Update _data/team/roles/outreach.yml
lilyminium Nov 8, 2023
9e608d2
change historical leads to historical members and remove from docs
lilyminium Nov 8, 2023
82f4e58
add "teaching materials" subrole
lilyminium Nov 8, 2023
7b4e72d
Apply suggestions from code review
lilyminium Nov 10, 2023
0ef6eb6
fix formatting error
lilyminium Nov 10, 2023
a385f71
fix emeritus link
lilyminium Nov 10, 2023
bded28c
rm Fiona from members
lilyminium Nov 10, 2023
46ffacc
rename file
lilyminium Nov 10, 2023
d037f79
lily leading hole2
lilyminium Nov 10, 2023
beaca73
change "leading figures" wording
lilyminium Nov 10, 2023
d11be08
Update distopia
hmacdope Nov 10, 2023
50de3e1
Update _data/team/roles/releases_and_deployment.yaml
IAlibay Nov 10, 2023
bf6c48d
Apply suggestions from code review
lilyminium Dec 14, 2023
e7ca512
remove leads and historical contributors
lilyminium Dec 14, 2023
88e8dfd
remove historical references in text and add footnote
lilyminium Dec 14, 2023
91839ab
markdownify tasks
lilyminium Dec 14, 2023
d50e270
update according to spreadsheet
lilyminium Dec 14, 2023
e14bdfe
add wording on when structure was started
lilyminium Dec 14, 2023
aecc25a
re-add wording on reaching out and emeritus core devs
lilyminium Dec 14, 2023
367869d
move invitation to join up a bit
lilyminium Dec 14, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/workflows/build_page.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -35,4 +35,5 @@ jobs:
destination: ./_site
- name: Upload artifact
uses: actions/upload-pages-artifact@v2
retention-days: "1"
with:
retention-days: "1"
2 changes: 1 addition & 1 deletion _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ author:
email: [email protected]

images: /public/images
data: /public/data
data_files: /public/data
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
js: /js
blog: /blog

Expand Down
43 changes: 43 additions & 0 deletions _data/team/roles/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# Roles

This directory contains YAML files, one per role.

## Editing

Each YAML file should contain the details of one role only.
Each role is automatically picked up by the template. To add or remove a role, simply add or remove a file. Do not add non-role documents to this directory that can be parsed by Jekyll.

Each file *must* contain the following tags at top level:

* `role`: The name of the role (e.g. Core library maintenance)

Each role can optionally have the following tags:
* `description`: text describing the role. This can be written in Markdown.
* `tasks`: a list of strings describing tasks. This is rendered as a list.

Each role can also optionally have lead/member tags, if there are no subroles. If there are subroles, the below are ignored:
* `current_leads`: a list of names who are current leads
* `current_members`: a list of names who are current members in the subgroup
* `historical_leads`: a list of names who were previously leads
* `historical_members`: a list of names who were previously members in the subgroup
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the fuzziness of historical roles, is it necessary and/or possible to distinguish between "leads" and "members"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the above comment at the very beginning of this review, but couldn't help but notice that the historical_members is always an empty list.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think I could go either way, and it definitely doesn't make too much sense at the moment! When I came up with the structure I thought we'd update the table annually or otherwise as people changed over, and shift the "current" leads/members into the historical column -- but if we head towards just maintaining a "current" column and keeping snapshots of this table around, that's not necessary either. If anyone has strong opinions about this either way they're very welcome!

As a compromise, until we nail down how we want to deal with archival or past lead/subgroups, how about just calling everyone a historical "member" (i.e. unbolding everyone), and removing the historical_leads from the documentation?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about cases where we know who the historical leads have been?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess my take here is - there have been a lot of things lately that have been concentrated on very few individuals and I think we should recognise that. But removing historical leads we're effectively saying "everyone did the same work".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current table is not the current snapshot unfortunately - if we're being honest with ourselves, a lot of this is "these folks will take on these roles", not "these folks are currently taking on these roles".

That's true that we haven't directly set when these transitions are meant to happen, thanks for pointing that out. As you said this probably requires core-dev input. Since the next meeting is so far away I'll see if I can get agreement on when the "Current" column starts asynchronously -- if it's either the end of the core-devs role-call or 2024, we can re-title the columns or add explanatory text as appropriate. If it's something else we can perhaps re-visit the idea of dropping the "Current" column in favour of publishing the historical one ASAP, and adding a new column later. Does that feel like a good compromise between getting this table out quickly but accurately to you?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My current understanding is that we largely don't have the data to specifically point out who did what when in the 2020-2023 era, and that also this organisational structure did not yet exist -- so that everyone in the "historical contributors" column is a major contributor, who in hindsight could theoretically be described to have done leadery roles. However, unless we start adding and crediting people who did less substantial work, or start drawing thresholds and declaring what amount of work qualifies as being considered a retrospective lead vs member, we don't have a proper distinction between historical "leads" and "members".

Need for clarification

I would make the time frame and intent of "historical" clearer in the table itself - it should be something along the lines of "historical leads 2020-2023". Right now it says "historical contributors" and most folks aren't going to go into the text to check this.

Dilemmas

Maintenance

One of the categories which I'm not sure about (and I don't think the intent of historical had been communicated as "2020-2023 leads" by then) is general maintance:

Here's my dilema:

Over the 2020 to today period, there were a total of 364 PRs against the core library that were labelled under maintainability. The breakdown of PRs submitted under the "maintainability" label for the top 20 submitters is as follows:

image

Now, it is fair for @jbarnoud to want to be listed under "historical contributors" for that section - @jbarnoud did an overwhelming amount of maintenance in the past (i.e. prior to 2020). However, this raw data indicates that there are other folks here who have, by measure of the number of submitted PRs, have also done a lot of contributions in the 2020 to 2023 period. What is the right way forward here?

Releases

Another area where we have strict data on "who did what" is releases.

@richardjgowers was the release manager for releases until 2.0.0. I then did all the releases mostly on lonesome since.

It would make sense here to have that distinction because we have that data on hand?

Is 2020 too far away? Should we say 2021 instead?

In retrospect, the limit of our data is really 2020, and honestly it's an odd arbitrary limit to put down (I think I may have been at fault here for setting this date for data gathering).

There are things represented in this table that don't really make sense if we say 2020-2023. For example, I was not made core developer until 2021, admittedly I did a lot of work whilst not being a coredev (I think I got to ~ 50 maintenance PRs before folks agreed to make me one...), but I don't think we can claim that I was "managing CI" back then.

May I suggest being a bit more conservative and setting the max retrospective date to 2021?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you suggesting this for the column as it stands now (representing 2020-2023) or for potential future tables when the current lead/member column gets shuffled in or put into a new yearly column?

Both - when we have good data we should do this (see my releases example).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's true that we haven't directly set when these transitions are meant to happen, thanks for pointing that out. As you said this probably requires core-dev input. Since the next meeting is so far away I'll see if I can get agreement on when the "Current" column starts asynchronously -- if it's either the end of the core-devs role-call or 2024, we can re-title the columns or add explanatory text as appropriate. If it's something else we can perhaps re-visit the idea of dropping the "Current" column in favour of publishing the historical one ASAP, and adding a new column later. Does that feel like a good compromise between getting this table out quickly but accurately to you?

I think I'd be happy with role-call being the set deadline? As far as I see them things are mostly still under the "old model", if we're saying "this will all change by Monday" then I'm looking forward to it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will say here - I do think that we need to have a clear detailed set of instructions about what it means to be a lead, how we will review this table going forward to ensure that we accurately capture who has been doing what, etc...

I am particularly worried that folks will take on positions right now and another set of unamed folks will end up doing the work and we will never end up acknowledging them.


Onto subroles: each role can optionally define `subroles`. The `subroles` tag should be a **list** where each item *must have*:

* `subrole`: The name of the subrole (e.g. Issue management)

Each subrole can *optionally have*:
* `current_leads`: a list of names who are current leads
* `current_members`: a list of names who are current members in the subgroup
* `historical_leads`: a list of names who were previously leads
* `historical_members`: a list of names who were previously members in the subgroup
RMeli marked this conversation as resolved.
Show resolved Hide resolved
* `description`: text describing the role. This can be written in Markdown.
* `tasks`: a list of strings describing tasks. This is rendered as a list.


## Parsing

The files here are read first by ``_includes/team_table.html`` and ``_includes/roles_description.html``.
Jekyll automatically reads YAML, JSON, and other formatted files in the ``_data`` directory
as objects that can be interacted with using the Liquid templating language.
For example, the ``name`` variable of the ``code_of_conduct.yml`` file is accessible as ``site.data.team.roles.code_of_conduct.name`` in HTML.

17 changes: 17 additions & 0 deletions _data/team/roles/code_of_conduct.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
role: Code of conduct committee
description: |
The [Code of conduct committee](https://www.mdanalysis.org/pages/conduct/)
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
is elected by the MDAnalysis core developers on a rolling basis.
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
tasks:
- Act as points of contact for code of conduct violations
lilyminium marked this conversation as resolved.
Show resolved Hide resolved

current_leads:
- Jenna Swarthout Goddard
- Richard Gowers
- Micaela Matta
current_members: []
historical_leads:
- Jenna Swarthout Goddard
- Richard Gowers
- Micaela Matta
historical_members: []
12 changes: 12 additions & 0 deletions _data/team/roles/community_engagement.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
role: Community engagement
tasks:
- Responding to questions on Discord and mailing lists
- Managing and triaging conversations on Discord and mailing lists
current_leads:
- Jenna Swarthout Goddard
current_members:
- All core devs
historical_leads:
- Oliver Beckstein
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
13 changes: 13 additions & 0 deletions _data/team/roles/continuous_integration.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
role: Continuous integration
tasks:
- Building and developing new CI infrastructure
- Monitoring status
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Maintenance and fixes
current_leads:
- Irfan Alibay
- Richard Gowers
current_members:
- Fiona Naughton
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
50 changes: 50 additions & 0 deletions _data/team/roles/core_library_maintenance.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
role: Core library maintenance
description: |
The core library maintenance team is responsible for the
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
managing the maintenance of the MDAnalysis library.

subroles:
- subrole: Issue management
tasks:
- Initial triage and tagging of issues
- Managing timely responses and resolving issues
current_leads:
- Rocco Meli
current_members:
- All core devs
historical_leads:
- Oliver Beckstein
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Jonathan Barnoud
historical_members: []

- subrole: Pull request management
tasks:
- Reviewing, shepherding, and merging pull requests
current_leads:
- Rocco Meli
- Oliver Beckstein
current_members:
- All core devs
historical_leads:
- Oliver Beckstein
- Richard Gowers
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Hugo MacDermott-Opeskin
- Jonathan Barnoud
historical_members: []

- subrole: General maintenance
tasks:
- Standards compliange (e.g. managing metadata such as the author list)
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Tracking new dependencies
- Emergency fixes
- Other emergency maintenance
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_leads:
- Irfan Alibay
current_members:
- All core devs
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Jonathan Barnoud
historical_members: []
18 changes: 18 additions & 0 deletions _data/team/roles/documentation.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
role: Documentation
tasks:
- Managing UserGuide repositories and main core documentation
- Managing MDAnalysis Sphinx theme
- Managing documentation-related utilities and architecture
- Managing new issues and PRs related to documentation
- Keeping documentation updated
- Responding to documentation issues in sub-projects
current_leads:
- Lily Wang
- Rocco Meli
current_members:
- Fiona Naughton
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- All core devs
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Lily Wang
historical_members: []
13 changes: 13 additions & 0 deletions _data/team/roles/external_liaison.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
role: External liaison
tasks:
- Coordinate and connect with affiliated organisations, e.g. NumFOCUS
- Coordinate participation in external projects
- Coordinate with potential industry partners

current_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@orbeckst - following on from yesterday's discussion, how do we feel about folks that aren't coredevs doing this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies, this is longer than anticipated — and sorry, you'll have to follow my typed out slow thought process:

Within our current definition of "core dev" as "project leadership" I think that's a bit problematic when viewing it from the perspective of the other side: If I were an outsider, looking to engage with the MDAnalysis Project, I'd eventually like to talk to someone in a position of obvious authority. The only way we currently obviously publicize "authority" is https://www.mdanalysis.org/about/#mdanalysis-core-developers and if I don't see the person I am negotiating with listed there then I might think that ultimately I will need to talk to someone else "who can make decisions".

From the internal side this seems like less of an issue to me. Within the current structure it would mean that the person leading this effort would not be able to vote on anything but could influence the process through discussion. If I were in this position I would probably feel not super-happy that I don't get a say in my own effort but that would depend on the person. We'd just need to be very clear up-front with them.


To come to something concrete:

I am considering

  1. Decisions should be consistent, and in the absence of clear rules, precedent should generalize without breaking everything else.
  2. Would we as a project be more successful in "external liaisons" if a CoreDev was doing it than if a non-CoreDev?

(2) is easy: Of course, the alternative may actually be "no-one does it or someone who cares does it" and then I am pretty sure the answer is that we'll do much better with someone who owns the role than someone whose name was put in to avoid a blank or who is stretched too thin. So there I think that someone who wants to do this and who has a track record of being able to work in such a role and work with the project is great. Ideally, we want both (for reasons above) but if we can't get both, then someone who wants to do it.

(1) It should be possible for "leadership" to delegate tasks. At the moment we are already doing this very successfully with our Project Manager. So I don't think that there's a problem per-se with someone leading a "role" who is not on the CoreDev list. However, the authority to do so must come from somewhere. Therefore, in these cases I'd say that "leadership" (CoreDevs) would need to vote to "appoint" and provide guidance on what the scope of authority is. This might feel mightily awkward.

In summary, I think we should be open to people who are not in the current Project Leadership (=CoreDev) to lead some of these roles and that ultimately they do this with delegated power from Leadership.


At the end of the day, it points more to the issue of rethinking our narrow governance structure.

current_members:
- Jenna Swarthout Goddard
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
18 changes: 18 additions & 0 deletions _data/team/roles/governance.yml
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
role: Governance
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
tasks:
- Managing roadmap planning and the "big picture"
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Organising meetings
- Coordinating elections of core developers
- Onboarding new core developers
- Managing other roles in the organisation and general task lists
- Gathering usage and community metrics

current_leads:
- Jenna Swarthout Goddard
current_members:
- Oliver Beckstein
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Oliver Beckstein
- Irfan Alibay
- Jenna Swarthout Goddard
historical_members: []
15 changes: 15 additions & 0 deletions _data/team/roles/mdakit_registry.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
role: MDAKits registry
tasks:
- Managing submissions to MDAKits registry
- Managing manual review process of new MDAKits
- Managing automated test and badge infrastructure of all MDAKits
- Manage helping with MDAKits who need assistance
current_leads:
- Irfan Alibay
current_members:
- Fiona Naughton
- Lily Wang
- Oliver Beckstein
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
80 changes: 80 additions & 0 deletions _data/team/roles/non_core_library_maintenance.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
role: Non-core library maintenance
description: |
The non-core library maintenance team is responsible for the
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
managing the maintenance of the all MDAnalysis packages
that are not the core MDAnalysis library.
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
tasks:
- Managing issues and pull-requests for sub-projects
- Managing new features and updates
- Managing maintenance
- Working with CI and CD team and infrastructure
subroles:

- subrole: distopia
current_leads: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_members: []
historical_leads:
- Hugo MacDermott-Opeskin
historical_members: []

- subrole: cookiecutter-mdakit
current_leads:
- Lily Wang
current_members: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Lily Wang
historical_members: []

- subrole: mda-encore
current_leads: []
current_members: []
historical_leads:
- Ian Kenney
historical_members: []

- subrole: hole2-mdakit
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_leads: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_members: []
historical_leads:
- Ian Kenney
historical_members: []

- subrole: benchmarks
current_leads:
- Oliver Beckstein
current_members: []
historical_leads:
- Oliver Beckstein
historical_members: []

- subrole: GridDataFormats
current_leads:
- Oliver Beckstein
current_members: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Oliver Beckstein
historical_members: []

- subrole: MDAnalysisData
current_leads:
- Oliver Beckstein
current_members: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Oliver Beckstein
historical_members: []

- subrole: mda-xrlib and other small utilities
current_leads:
- Irfan Alibay
current_members: []
historical_leads:
- Irfan Alibay
historical_members: []

- subrole: pyedr
current_leads: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_members: []
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
32 changes: 32 additions & 0 deletions _data/team/roles/outreach.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
role: Outreach
subroles:
- subrole: Workshops and meetings
tasks:
- Identifying workshop and event opportunities
- Organising workshops and events
- Gathering and coordinating volunteers
- Managing content, presentations and teaching at workshops
current_leads:
- Jenna Swarthout Goddard
- Rocco Meli
RMeli marked this conversation as resolved.
Show resolved Hide resolved
current_members:
- Micaela Matta
- All core devs
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
- Micaela Matta
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we've had plenty more people than this engaged here previously

historical_members: []

- subrole: Mentoring
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
tasks:
- Manage material maintenance on GitHub
- Mentoring-related administrative tasks
- Advertising opportunities for mentoring programs
- Mentoring in structured programs
current_leads:
- Jenna Swarthout Goddard
current_members: []
historical_leads:
- Jenna Swarthout Goddard
- Oliver Beckstein
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
15 changes: 15 additions & 0 deletions _data/team/roles/releases_and_deployment.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
role: Releases and deployment
tasks:
- Monitoring upstream and downstream package changes
IAlibay marked this conversation as resolved.
Show resolved Hide resolved
- Updates and fixes for upstream and downstream packages
- Managing future release plans and timing
- Carrying out releases
- Maintaining continuous deployment infrastructure
- Monitoring issues in core library and sub-projects
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
current_leads:
- Irfan Alibay
current_members:
- Fiona Naughton
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
14 changes: 14 additions & 0 deletions _data/team/roles/relicensing_coordinator.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
role: Relicensing coordinator
tasks:
- Researching the steps required to change licenses
- Coordinating the choice to a new license
- Contacting existing developers to solicit agreement
- Ensuring new developers agree to a new license
- Managing the switch to a new license

current_leads:
- Irfan Alibay
current_members: []
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_leads:
- Irfan Alibay
lilyminium marked this conversation as resolved.
Show resolved Hide resolved
historical_members: []
14 changes: 14 additions & 0 deletions _data/team/roles/social_media.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
role: Social media
tasks:
- General management and administration
- Posting announcements of new developments
- Moderating content
- Managing X and LinkedIn
- Managing new content to the MDAnalysis website and blog
current_leads:
- Jenna Swarthout Goddard
current_members: []
historical_leads:
- Oliver Beckstein
- Jenna Swarthout Goddard
historical_members: []
Loading
Loading