[Thomas/BNP] Application to join Microcks Steering Committee
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- content
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.
Description
Hello Microcks community !
I would like to apply to the Microcks Steering Committee, as discussed with @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
- Dominant language
- No language data
- Stars
- 11
- Forks
- 9
- Avg merge
- 17m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/community
-
Clarify and Formalize Steering Committee Membership Application ProcessPossibly taken @yada claimed this 6 days ago. Opensteering
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
steering
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
documentation good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
documentation good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in microcks/community
Similar issues
-
enhancement good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 66/100
AlphaaCode/Popbook#10 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
BSData/age-of-sigmar-4th#1420 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
lingdojo/kana-dojo#33508 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
broker-data page-monitor
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
markramm/data-broker-registry#173 ·
Maintainers usually reply within 1 day
-
artwork good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
arnegiacomo/fugleramme#357 · 1 comment ·
Maintainers usually reply within 1 day