Skip to content

Commit

Permalink
Merge branch 'master' into add_switzerland_regional
Browse files Browse the repository at this point in the history
  • Loading branch information
bgruening authored Aug 7, 2024
2 parents 843856e + 7e3584a commit 0b72007
Show file tree
Hide file tree
Showing 123 changed files with 4,098 additions and 429 deletions.
4 changes: 2 additions & 2 deletions content/admin/get-galaxy/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,15 @@ If setting up or running a production Galaxy service or creating your own person
If you do not have a Galaxy repository yet or you do not want to update the existing instance, run:

```
$ git clone -b release_24.0 https://github.com/galaxyproject/galaxy.git
$ git clone -b release_24.1 https://github.com/galaxyproject/galaxy.git
```

### Updating existing

If you have an existing Galaxy repository and want to update it, run:

```
$ git fetch origin && git checkout release_24.0 && git pull --ff-only origin release_24.0
$ git fetch origin && git checkout release_24.1 && git pull --ff-only origin release_24.1
```


Expand Down
7 changes: 7 additions & 0 deletions content/bare/eu/usegalaxy/main/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,15 @@ title: Galaxy Europe

<slot name="/bare/eu/usegalaxy/notices" />

<!--
<Carousel />
-->

<div class="text-center mt-5">
<a href="https://galaxyproject.org/news/2024-05-29-galaxy-training-academy-call-contribution"target=”_blank”>
<img src="/images/call_for_trainers.png" alt="Galaxy Training Academy" />
</a>
</div>
<br/>
<br/>

Expand Down
11 changes: 11 additions & 0 deletions content/blog/2024-07-29-galaxy-aquainfra/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
date: '2024-07-29'
title: "The AquaINFRA Virtual Research Environment "
tease: "Design rationale for using the Galaxy platform"
authors: "Markus Konkol"
external_url: "https://blog.52north.org/2024/07/25/the-aquainfra-virtual-research-environment-design-rationale-for-using-the-galaxy-platform/"
source_blog_url: "https://blog.52north.org/"
source_blog: "52°North Blog"
tags: [esg-wp5, esg, aquainfra, eosc]
subsites: [all-eu, global]
---
2 changes: 1 addition & 1 deletion content/careers/2020-11-hopkins-biostat/index.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Research Associate in Biomedical Data Science"
date: '2020-11-24'
closes:
closes: '2021-11-24'
summary: "Data science research and education focusing on genomics ([AnVIL](https://anvilproject.org/), [Genomic Data Science Community Network](http://www.gdscn.org/)), cancer ([ITCR](https://itcr.cancer.gov/)) or pain [A2CPS](https://a2cps.org/)."
continent: NA
location:
Expand Down
Binary file added content/community/governance/gcb/gtn_hat.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
148 changes: 58 additions & 90 deletions content/community/governance/gcb/index.md
Original file line number Diff line number Diff line change
@@ -1,114 +1,82 @@
# Galaxy Community Board
# Galaxy Community Board (GCB)

**Keywords:** Special Interest Groups, Community of Practices

## Origins

The Galaxy Community Board (GCB) is proposed to take over the functions of the Global Galaxy Steering Committee.
During GCC 2023, we discussed how to empower the Galaxy community in terms of project planning, decision-making, execution, and overall governance.

## Purposes

Representation of community aspects of the ecosystem is central to long-term project sustainability. The goal is to empower community members
to participate in planning and governance, through efficient and transparent structures and processes, that can scale effectively as the Galaxy project continues to expand.

The GCB will provide a supportive virtual forum for the exchange of ideas, and a governance body representing the interests of participating communities.
It will organise and manage its own agenda and work, including arranging meetings and asynchronous discussions. The agenda might include planning new initiatives;
supporting ongoing development; identifying and advocating for user needs; managing coherent, community-owned proposals and responses in the roadmap
processes and other important project decision-making.

Efficient communication between the GCB (Community Board) and both the GEB (Executive Board) and the GTB (Technical Board) requires at least one representative
from GEB and from GTB to be also members of the GCB. Therefore, it is recommended that at least one member of each of the other two Boards are also members of the GCB.

In summary, the goals of the GCB are:

* discuss and summarize scientist (user) feedback to help guide the technical development of the Galaxy platform;
* communicate scientist (user) vision and feedback to the GTB and GEB;
* develop proposals to advance scientist (user) goals in the Galaxy community.
<slot name="/community/governance/linkbox" />

## Community Special Interest Groups (SIGs)

The GCB is a governance structure representing groups that are not primarily technical, such as the existing Proteomics and Microbial communities,
through engaging in capacity building, toolkit development, outreach and training. The term *[Special Interest Group](/community/sig)* (SIG)
refers to these dedicated scientific communities. No specific restrictions are proposed, other than making a useful contribution to the project,
no specific restrictions apply.

Active contributors are encouraged to form and govern their own [SIG](/community/sig), with a focus on specific shared interests.
Each [SIG](/community/sig) may elect one member to represent their interests on the [GCB](/community/governance/gcb/).
This is analogous to the Technical Board, consisting of representatives of the Working Groups (WG).

### Characteristics of SIGs

* Often focused on community development (distinct from the more technical issues managed by WGs)
* Self-regulated, which includes organising meetings, developing training material and tools, maintaining the Hub pages, and choosing a representative for the GCB
* Dependent on community needs, SIGs are easy to form and dissolve
for ongoing recognition, easy to create and to dissolve, can be transient
* Supported with administrative infrastructure provided by the Galaxy Project and the [GCB](/community/governance/gcb/), such as:
* mailing list
* website infrastructure and a place on the Galaxy hub to present the Community
* presentation slot at the annual GCC conference
* Chat channel/room
* Govern their own activities such as organising meetings, developing training material and tools, maintaining the Hub pages, and choosing a representative for the GCB.
* Represented in the GCB in order to articulate needs and requirements as part of the Galaxy Project roadmap and (competitive grant) processes.
**Keywords:** Special Interest Groups, Community of Practices

### Requirements for SIGs
<!-- This is the text from this GTN snippet. One day, would be good to make one central location for this and embed it https://training.galaxyproject.org/training-material/topics/community/faqs/governance_gcb.html -->

* Must have 2 or more members to be viable
* Must maintain a page on the Community Hub with at least:
* A description of the focus and purposes of the SIG.
* A clear explanation of how individuals can join and maintain membership.
* Details of access to the SIG’s communication channels.
* A description of roadmap-related processes for gathering input from members.
* The current contact/email address for the nominated GCB representative, and to manage membership and internal communication for itself.
* Use at least one public Matrix channel under the Galaxy Matrix space.
The Galaxy Community Board provides a supportive virtual forum for the exchange of ideas, and a governance body to represent [**Special Interest Groups** (SIGs)](https://galaxyproject.org/community/sig/) in Galaxy.

### Creating a new SIG
The goals of the GCB are to:

We encourage everyone with an interest in contributing to Galaxy to join a SIG, WG, or to create their own SIG. The Galaxy Project Management Office (PMO)
is the first point of contact for anyone wanting to form a new SIG. To illustrate the scope of SIGs, see the community page on the
Galaxy Community Hub and the following examples:
- share resources, tips & best practices to make running **SIGs** easier;
- discuss scientist (user) feedback to help guide Galaxy platform development;
- communicate scientist (user) needs to the Galaxy Governance structure; and
- develop proposals to advance scientist (user) goals in the Galaxy community.

* Microbial (People interested in Microbial research, tool, workflow and training development)
* Industry Forum (a forum for people to exchange needs and experiences with Galaxy in Industry settings)
* Indian Galaxy Community (regional Galaxy community, interested in Galaxy community building)
* AnVIL (funded project related to Galaxy)
* BLA (Better License Annotation SIG - does not exist yet, but could bring people together to better annotate Galaxy tools and workflows with appropriate licenses, could develop License recommendations)
## Where is the GCB in the Galaxy Governance Structure?

## Why make a SIG?
<!-- This is the text from this GTN snippet. One day, would be good to make one central location for this and embed it https://training.galaxyproject.org/training-material/topics/community/faqs/governance_structure.html -->

### Prevent work duplication
Galaxy Governance consists of a [Galaxy Executive Board](https://galaxyproject.org/community/governance/geb/) that provides global direction, working with a [Galaxy Technical Board](https://galaxyproject.org/community/governance/gtb/) that represents [Working Groups](https://galaxyproject.org/community/wg/) and a [Galaxy Community Board](https://galaxyproject.org/community/governance/gcb/) that represents [Special Interest Groups](https://galaxyproject.org/community/sig/).

It’s surprisingly easy for individuals halfway across the world to need the same tool and build the same tool.
What a waste of time when there are so many cool things to do!
<p align="center">
<img src="structure.png" alt="Galaxy Executive Board is in a rectangle over top of two rectangles, the Galaxy Technical Board and Galaxy Community Board, which are themselves over top of Working Groups and Special Interest Groups, respectively. A Project Management Office rectangle spans the image across the bottom" style="width:450px">
</p>

### Highlight new resources
## Who is in the GCB?
Each Galaxy Special Interest Group (**SIG**) may elect one member to represent their interests on the [GCB](/community/governance/gcb/). In practice, this is often (but not always) the person chairing the **SIG**.
This is analogous to the [Technical Board](/community/governance/gtb/), consisting of representatives of the [Working Groups (WG)](/community/wg).

If you’re working in the same research area, for instance, it can be exciting when someone builds something new that could help your research. With so many things getting added daily, it’s easy to miss this news. SIGs can point out such highlights and give you new ideas for your research or work.
You can learn more about **SIGs** in our dedicated tutorials below, or explore our [**SIG** directory](/community/sig).

### Peer review
<div style="text-align: center;">
<div class="row">
<div class="col-md-6">
<div class="row">
<div style="border: 2px solid black; padding: 10px; margin: 5px;background-color: papayawhip">
<a href="https://training.galaxyproject.org/training-material/topics/community/tutorials/sig_define/tutorial.html">
<img src="gtn_hat.png" alt="GTN Hat" width="50">
What is a SIG?
</a>
</div>
<div style="border: 2px solid black; padding: 10px; margin: 5px;background-color: papayawhip">
<a href="https://training.galaxyproject.org/training-material/topics/community/tutorials/sig_create/tutorial.html">
<img src="gtn_hat.png" alt="GTN Hat" width="50">
Creating a SIG
</a>
</div>
</div>
</div>
</div>
</div>

Need someone to look at an issue? Want some feedback on a tutorial or tool? Your fellow SIG members are a lot more likely to help you if you help them, and, more importantly, if they know who you are. Cut through the 1.8k of issues on Github by making some work friends in your field.
## Purpose

### Building community
Representation of community aspects of the Galaxy ecosystem is central to long-term project sustainability. The goal is to empower community members
to participate in planning and governance, through efficient and transparent structures and processes, that can scale effectively as the Galaxy project continues to expand.

The bigger the community you have, the more power in developing further resources (or grant proposals!), finding collaborators, co-authoring papers, etc. Higher user counts give you more sway in decision-making and building up Galaxy further, advancing your own work. It’s a lot easier to say you need something and 100 users agree, than to ask on behalf of yourself alone.
## Practicalities

### Many hands make light work
The **GCB** organises and manages its own agenda and work, including arranging meetings and asynchronous discussions. The agenda might include planning new initiatives; supporting ongoing development; identifying and advocating for user needs; managing coherent, community-owned proposals and responses in the roadmap
processes and other important project decision-making.

When delivering training (like [Smorgasbord](https://gallantries.github.io/posts/2021/03/01/smörgåsbord/) global training events) or projects, it’s rather important that the website you point to, quite frankly, looks nice. Imagine half the training is out of date, or - as happened to this author - you send someone to a page to learn a field and they get 3.5 hours into a 7 hours tutorial that no longer works, is outdated and not relevant to the name of the page itself. You immediately lose people and waste time. Preparing training material for training events is a big task, but if you can share it amongst a SIG, you ensure sustainability and increase impact.
Efficient communication between the GCB (Community Board) and both the GEB (Executive Board) and the GTB (Technical Board) requires at least one representative
from GEB and from GTB to be also members of the GCB. Therefore, it is recommended that at least one member of each of the other two Boards are also members of the GCB.

## WG and SIGs are complimentary
SIG members, and especially the representatives, are encouraged to join WG meetings or talk to WG representatives to raise issues or request help.
For example, SIG members could request assistance from the tools and workflows WG. WGs might contact SIGs to collect feedback from the community.

WGs are distinct from SIGs in that they are:
## Origins

* focused on technical issues
* manage important project infrastructure assets, including source code, for the long term
* self-organised
* have representative(s) as a contact point
* send a representative to the Technical Board ([GTB](/community/governance/gtb/))
* contribute to the roadmap by providing technical input and requesting resources for technical and development activities
During GCC 2023, we discussed how to empower the Galaxy community in terms of project planning, decision-making, execution, and overall governance. The Galaxy Community Board (GCB) was formed to take over from the Global Galaxy Steering Committee.

SIG members, and especially the representatives, are encouraged to join WG meetings or talk to WG representatives to raise issues or request help.
For example, SIG members could request assistance from the tools and workflows WG. WGs might contact SIGs to collect feedback from the community.
## Contributors
This page is brought to you by:
- [Wendi Bacon](https://training.galaxyproject.org/training-material/hall-of-fame/nomadscientist/)

with thanks for editing and review from:

- [Saskia Hiltemann](https://training.galaxyproject.org/training-material/hall-of-fame/shiltemann/)
- [Helena Rasche](https://training.galaxyproject.org/training-material/hall-of-fame/hexylena/)
Binary file added content/community/governance/gcb/structure.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 4 additions & 6 deletions content/community/governance/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,10 @@ Read more about [Galaxy Working Groups](/community/wg/).

## Galaxy Community Board (GCB)

The [GCB](/community/governance/gcb/) is a committee representing *[Special Interest Groups](/community/sig/)* (SIGs) that are not primarily technical in nature (such as the existing
Proteomics and Microbial communities), engaging in capacity building, toolkit development and training.
The [GCB](/community/governance/gcb/) will provide a supportive virtual forum
for the exchange of ideas. It will organise and manage its own agenda and work,
including arranging meetings and asynchronous discussions. The agenda might include planning new initiatives; supporting ongoing development;
managing coherent, community owned proposals and responses in the roadmap processes and other important Project decision making.
The GCB is a committee representing *Special Interest Groups* (SIGs) that are not primarily technical in nature (such as Proteomics or Microbiome), engaging in capacity building, toolkit development and training.
The GCB provides a supportive virtual forum for the exchange of ideas. It organises and manages its own agenda and work, including arranging meetings and asynchronous discussions. Agendas include planning new initiatives; supporting ongoing development; managing coherent, community owned proposals; and collectively engaging with the roadmap processes and other important Project decision making.

<i class="fa fa-book" aria-hidden="true"></i>&nbsp; &nbsp; Read more about the [Galaxy Community Board](/community/governance/gcb/) or peruse our [Special Interest Groups](/community/sig/).

## Galaxy Executive Board (GEB)

Expand Down
Loading

0 comments on commit 0b72007

Please sign in to comment.