Community
Participate
Working Groups
We need an API that provides a list of specification projects for a particular working group. The input would be the identity of the working group (e.g. "jakartaee"). The output should include: * The project name; * The project id; * URL to the project landing (PMI) page; * The scope statement; and * List of Git repository URLs. Output in JSON would be fine. I don't think that we need to add any authentication or authorization around the use of this API.
How about we create a "projects" endpoint? We would need to implement two filters to meet your requirements: 1. spec_project 2. working_group For example: projects.eclipse.org/api/projects?spec_project=1&working_group=jakartaee Thanks for the requirements!
I think that this could work. I assume that you're thinking of the two ways in which we associate working groups with projects. * field_working_group which indicates an informal relationship between a project and zero or more working groups; and * field_project_spec_working_group which describes a very formal relationship between a project and at most one working group for the purposes of doing specification work.
Marking this as a P2 since it's a Q3 MBO for my team.
*** Bug 434494 has been marked as a duplicate of this bug. ***
Hi Wayne, There is now an endpoint on the Projects website to get a list of projects. It is also possible to filter the ones that are a spec project and to which working group it is associated to: https://projects.php55.dev.docker/api/projects?spec_project=1&working_group=jakarta-ee Please reopen this bug if there's an issue with this new endpoint. Thanks!
That endpoint returns an error. This one works, however (is this what you meant?): https://projects.eclipse.org/api/projects?spec_project=1&working_group=jakarta-ee The list is incomplete. It does not, for example, include "Jakarta Server Pages" (it does include "Jakarta Server Faces", which is a different project). I also expect to see, for example, Jakarta Transactions (ee4j.jta) and Jakarta NoSQL (ee4j.nosql) in the output.
(In reply to Wayne Beaton from comment #6) > That endpoint returns an error. > > This one works, however (is this what you meant?): > > https://projects.eclipse.org/api/ > projects?spec_project=1&working_group=jakarta-ee > > The list is incomplete. It does not, for example, include "Jakarta Server > Pages" (it does include "Jakarta Server Faces", which is a different > project). I also expect to see, for example, Jakarta Transactions (ee4j.jta) > and Jakarta NoSQL (ee4j.nosql) in the output. One thing I forgot to mention is that I implemented pagination in this endpoint. For example, ee4j.jsp is visible on the 2nd page: https://projects.eclipse.org/api/projects?spec_project=1&working_group=jakarta-ee&page=2 It is also possible to change the page size by using the pagesize parameter like so: https://projects.eclipse.org/api/projects?spec_project=1&working_group=jakarta-ee&page=2&pagesize=40 The default pagesize is 20 items.
Ah. Okay. Thanks.
After discussion with Chris we decided to make the following changes: The "working_group" filter will now be called "spec_project_working_group" to reflect the information that is being shown. I will create a new filter called "working_group" that will fetch the projects that are associated to a working group and not necessarily a spec project.
(In reply to Eric Poirier from comment #9) > After discussion with Chris we decided to make the following changes: > > The "working_group" filter will now be called "spec_project_working_group" > to reflect the information that is being shown. > > I will create a new filter called "working_group" that will fetch the > projects that are associated to a working group and not necessarily a spec > project. +1 and we will also: 1. include the logo with each project 2. Remove some redundancy in the attribute names. For example, project_project_id will become project_id.
(In reply to Christopher Guindon from comment #10) > (In reply to Eric Poirier from comment #9) > > After discussion with Chris we decided to make the following changes: > > > > The "working_group" filter will now be called "spec_project_working_group" > > to reflect the information that is being shown. > > > > I will create a new filter called "working_group" that will fetch the > > projects that are associated to a working group and not necessarily a spec > > project. > > +1 and we will also: > > 1. include the logo with each project > 2. Remove some redundancy in the attribute names. For example, > project_project_id will become project_id. I merged my patch to production and those changes have been applied. https://projects.php55.dev.docker/api/projects
(In reply to Eric Poirier from comment #11) > > I merged my patch to production and those changes have been applied. > > https://projects.php55.dev.docker/api/projects This is the url I meant to post in my comment: https://projects.eclipse.org/api/projects
(In reply to Eric Poirier from comment #12) > (In reply to Eric Poirier from comment #11) > > > > I merged my patch to production and those changes have been applied. > > > > https://projects.php55.dev.docker/api/projects > > This is the url I meant to post in my comment: > > https://projects.eclipse.org/api/projects There is a few duplicates under "spec_project_working_group".
New Gerrit change created: https://git.eclipse.org/r/149913
New Gerrit change created: https://git.eclipse.org/r/149914
(In reply to Christopher Guindon from comment #13) > (In reply to Eric Poirier from comment #12) > > (In reply to Eric Poirier from comment #11) > > > > > > I merged my patch to production and those changes have been applied. > > > > > > https://projects.php55.dev.docker/api/projects > > > > This is the url I meant to post in my comment: > > > > https://projects.eclipse.org/api/projects > > There is a few duplicates under "spec_project_working_group". It is now fixed on production: https://projects.eclipse.org/api/projects
