[Basu/Amadeus] Application to join Microcks Steering Committee
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- content
Research direction
No files, tests, or entry points are mentioned. This issue is an application to join the Steering Committee, so it has no implementation target or repository-based done condition; the next step depends on a community decision.
Written by the indexing model from the issue text.
Description
Hello Microcks community 👋,
I would like to submit my application to join the Microcks Steering Committee, as discussed with @yada.
About me
- Name: Basappa(Basu) Dapalapur
- Organization: Amadeus
- Role: Microcks Technology Owner at Amadeus
- GitHub Profile: https://github.com/Basuchi
Background & involvement
Amadeus is an active adopter of Microcks, and I am responsible for Microcks usage and strategy within Amadeus.
I have been involved in:
- Driving Microcks adoption internally at Amadeus
- Supporting open-source alignment and governance discussions
- Acting as a point of contact between Amadeus and the Microcks community
Thank you for considering my application.
I am happy to provide any additional information if needed.
Best regards,
Basappa (Basu)
- 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 4/5 3-5 days Newbie friendliness 35/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
-
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
-
good first issue translation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TanbirRamim/open-source-radar#408 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
BeeStation/BeeStation-Hornet#14886 ·
Maintainers usually reply within 1 day
-
[Bug] Announcements category archive lists only 1 of 5 postsPossibly taken @simransingh7396-dev claimed this today. Openhelp wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
meshery/meshery.io#3136 · 1 comment ·
Maintainers usually reply within 1 day