Skip to content

guardian/scala-guild-administration

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

18 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Scala Guild

πŸŽ‰βœ¨ Maintaining shared Scala code & infrastructure at the Guardian βœ¨πŸŽ‰

Membership

See the GitHub team @scala-guild! This GitHub team is specifically for developers across the Guardian who’ve accepted the honoured responsibilities of our Scala Guild. It’s intended to draw its membership from across all Product Streams and Teams.

If you'd like to join the guild, feel free to message any of the guild members (particularly, Roberto will always be delighted to hear from you!) and they'll add you to the @scala-guild GitHub team.

Scala Guild responsibilities

The Scala Guild is focussed on making sure that shared Scala code and infrastructure at the Guardian is maintained and secure - it gives a place for responsibility to exist for security vulnerability patching, upgrading and general maintenance. Without this group, maintenance responsibility for shared libraries that are used across many Product Teams at the Guardian would be unclear.

The guild has criteria for accepting responsibility for Scala code, and is not responsible for all Scala code at the Guardian. Accepting responsibility does not happen automatically, each repo must be added by a PR reviewed by the guild.

Criteria for code being maintained by the Guild

It must:

  • Be in a public GitHub repository
  • Be consumed by more than one Product team at the Guardian - if only one Product team consumes a library, then by default, they should maintain it - though obviously the Scala Guild can be consulted for expertise.
  • Have Scala Steward enabled.
  • (if it is a library) Use a secure automated release process, ie gha-scala-library-release-workflow

There should be:

About

Maintaining shared Scala code & infrastructure at the Guardian βœ¨πŸŽ‰

Resources

Code of conduct

Stars

Watchers

Forks

Contributors 3

  •  
  •  
  •