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

More on renaming WG to Activity Area #1613

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

eduardo-rodrigues
Copy link
Member

@eduardo-rodrigues eduardo-rodrigues commented Nov 5, 2024

Let me know what you think of these follow-up changes that I noticed were missing.

In short I renamed "Working Group" to "Activity Area" and in some text where "working group" is mentioned I simply left "group", as in "group a people", which seems OK. But one could be more aggressive.

@eduardo-rodrigues eduardo-rodrigues marked this pull request as ready for review November 5, 2024 15:35
@eduardo-rodrigues eduardo-rodrigues changed the title More on renaning WG to Activity Area More on renaming WG to Activity Area Nov 6, 2024
@eduardo-rodrigues eduardo-rodrigues self-assigned this Nov 6, 2024
@graeme-a-stewart
Copy link
Member

Hi @eduardo-rodrigues - thanks a lot for doing this. I am generally favourable, but I think in many of the cases "X Activity Area" can just be "X Activity". It's a bit less of a mouthful.

e.g., The Detector Simulation Working Group considers approaches to making... -> The Detector Simulation Activity considers approaches to making...

What do you think?

@eduardo-rodrigues
Copy link
Member Author

Yes, there are places where one could be shorter and omit "Area". I was not sure. In other places "group" is the right word, because it stands for "group of people".

@graeme-a-stewart
Copy link
Member

I just added another commit that corrects the SG mandate, which still mentioned WGs a lot

These links are no longer valid, so remove them and note that
they are not available
Copy link
Member

@hegner hegner left a comment

Choose a reason for hiding this comment

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

Just two minor things and then we are ready to merge.
Further findings can go into a new PR.

with the aid of software tools such as code editors, static/dynamic code analysers, compilers, debuggers, performance analysers and so on.
The group plans to accomplish this by mainly serving as a forum where developers can share their experiences, discuss new/existing tools they utilise,
and learn from each other. To that point, contributions from the entire community are strongly encouraged.

## Packaging

The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*
The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we should talk about this area instead of a group

Copy link
Member Author

Choose a reason for hiding this comment

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

I left "group" in a few places as in "group of people", but happy with a change. I have no strong feeling here.


### Packaging Goals

The aim of this working group is to foster communication and exchange among the experiments' librarians. We have identified various topics to work on, including
The aim of this group is to foster communication and exchange among the experiments' librarians. We have identified various topics to work on, including
Copy link
Member

Choose a reason for hiding this comment

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

just remove this group

@@ -16,7 +16,7 @@ adaption of simulation techniques to modern computing hardware
(covering, e.g., multithreading, vectorisation and different accelerator
technologies) are an important area of work.

[Mandate]({{ site.baseurl }}/organization/working-group-mandates.html).
[Mandate for Working Groups from 2018]({{ site.baseurl }}/organization/working-group-mandates.html).
Copy link
Member Author

Choose a reason for hiding this comment

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

Is this the best thing to do? I only see the original mandate linked from here and the Reco & Trigger page. Should one have the link somewhere for historical purposes and remove this and the similar link in the Reco & Trigger page?

Copy link
Member Author

Choose a reason for hiding this comment

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

Any thoughts on this?

with the aid of software tools such as code editors, static/dynamic code analysers, compilers, debuggers, performance analysers and so on.
The group plans to accomplish this by mainly serving as a forum where developers can share their experiences, discuss new/existing tools they utilise,
and learn from each other. To that point, contributions from the entire community are strongly encouraged.

## Packaging

The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*
The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*.
Copy link
Member Author

Choose a reason for hiding this comment

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

I left "group" in a few places as in "group of people", but happy with a change. I have no strong feeling here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants