microcks / microcks/community

[Thomas/BNP] Application to join Microcks Steering Committee

Open
#121 7 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

steering
Dominant language
No language data
Stars
11
Forks
9
Avg merge
5h 15m
Merged PRs (30d)
10

Description

Hello Microcks community !

I would like to apply to the Microcks Steering Committee, as discussed with [@yada](https://github.com/yada) (cf https://github.com/microcks/community/issues/120)

**About me**
* Name: Thomas KOHL
* Organization: BNP Paribas (already in adopters.md)
* Role: Maintenance and administration of our self hosted Microcks/Keycloak instance
* GitHub Profile: https://github.com/tkohl-d
* Linkedin : www.linkedin.com/in/thomas-kohl-5321675a

**Background & involvement**
BNP uses Microcks since 2022 to mock our legacy core banking systems and mainframe APIs in order to increase agility, accelerate development, and reduce costs.

Microcks is also integrated into our API-first strategy for building and delivering new cloud-native services.

I have been involved in :
- Microck/keycloak upgrades
- User administration
- Incident management (investigation, analysis, communication etc.)

And I would be happy to share with you how Bnp Paribas users are using Microcks and what they hope to see happen in the future 😀

Feel free to ask for any further information !

Best regards,
Thomas

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading community issue #120 and the seven comments on this application, then review any documented Steering Committee process in the repository. Done means the community reaches, records, and communicates a decision on Thomas's application; no code file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.