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

Publish team members #424

Open
3 tasks
Riduidel opened this issue Mar 7, 2024 · 0 comments
Open
3 tasks

Publish team members #424

Riduidel opened this issue Mar 7, 2024 · 0 comments
Labels
effort: 3 state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: obvious The situation is obvious, best practices used.

Comments

@Riduidel
Copy link
Owner

Riduidel commented Mar 7, 2024

There are at least two/three ways to get team members

  • Get the team from the maven pom
  • Get the team from the Git history (with bot exclusion)
  • Get the team by calling GitHub/GitLab API

Each of these should fill on the upmost model element a maven property (something like aadarchi.team.members which content could be some json representing the team members).
And finally, a "late" Enhancer would pull that member list and expose it as a documentation element. I think it would find its place in the constraints part.

@Riduidel Riduidel added work: obvious The situation is obvious, best practices used. effort: 3 state: approved Approved to proceed. priority: 2day type: feature Brand new functionality, features, pages, workflows, endpoints, etc. and removed difficulty-🐛🐛 priority: 2day labels Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 3 state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: obvious The situation is obvious, best practices used.
Projects
None yet
Development

No branches or pull requests

1 participant