-
Notifications
You must be signed in to change notification settings - Fork 45
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
Add pages showing the org teams #12
Comments
can i take up this issue? @jayvdb |
@chetanya-shrimali do you have a proposal solving this? This requires some design and we'd rather you discuss your ideas with us first before implementing them right away. |
In this we need to create the model first or is it that the model is already there we just have to fetch the data? @adtac |
@chetanya-shrimali , look in the repository for your answers |
@jayvdb, @adtac, Once #32 will be solved, and we will be having all the contributor's data into a data model then we can fetch any of the contributor's data according to our need. Suppose that we have to make a page for coala maintainers, then we can scrape all the coala maintainer's usernames from https://github.com/orgs/coala/teams/coala-maintainers/members into a list and then we can make a query for each username with the contributor model(with the login field) and get all the data of that particular contributor and then we can show it to the page. |
@sks444 can't we utilize the contributor team list that is currently being popped out from the structure, at line 35 , because scrapping the webpage using |
I think want at least the coala maintainers, coala developers and coala newcomer teams to have a page, with a list of team members similar to https://coala.io/#/getinvolved .
I think it is OK to have a page about all teams in https://github.com/orgs/coala/teams .
However we also need a way to name our temporary teams so that they do not appear on the website.
e.g. @adtac created a team to help him manage inactive newcomers at coala/meta#74 , so they could be removed. Maybe we dont want a team like that appearing on the website ;-)
The text was updated successfully, but these errors were encountered: