search

coala / projects

A website that showcases interesting projects, using Angular JS.
https://projects.coala.io/
GNU Affero General Public License v3.0
116 stars 223 forks source link

Update the mentors page with 2019 people #777

Closed abhishalya closed 4 years ago

abhishalya commented 4 years ago

We should update the page with 2019 mentors instead of 2018.

faraz16iqbal commented 4 years ago

Hi, is it possible for me to work on this update?

abhishalya commented 4 years ago

Yes! Why not. Assigned

faraz16iqbal commented 4 years ago

Can you please guide me as to how to access the information?

abhishalya commented 4 years ago

Wouldn't it be nice if you could figure it out ;)

chttrjeankr commented 4 years ago

@faraz16iqbal, are you still working on this?

abhishalya commented 4 years ago

@chttrjeankr Do you want to take up this issue?

chttrjeankr commented 4 years ago

@chttrjeankr Do you want to take up this issue?

Sure! I'd have to go through the newcomers' procedure first. I can then start working on it.

abhishalya commented 4 years ago

Assigned to @chttrjeankr due to inactivity of previous assignee.

chttrjeankr commented 4 years ago

Thanks for assigning. :rocket:

I think you mean this Mentors Page.

The trace led me to realize the resources/js/directives/mentors.js file fetches data from data/projects.liquid which in turn fetches data from site.projects.

And since the site already has projects listed, I don't understand why it isn't automatically updating. I'm a bit new to JS so maybe I'm missing something? Could you help @abhishalya?

chttrjeankr commented 4 years ago

Figured out what to change. Discussing an appropriate solution would be needed.

The current code makes a list of all mentors who are in a project that has a status of NOT completed. I don't think we want that to happen. (though #491 says we do(?))

So we have multiple options for the mentors page:

  1. To list all mentors from all projects that are complete.
  2. To list ALL mentors disregarding the project's status.
  3. To list only mentors from GSoC19 of projects that are complete.
  4. To list mentors from all GSoC19 projects.
  5. To make a dynamic mentors page to have mentors of GSoC for the present year. (not very suitable as coala is not in GSoC every year) (this has been tried earlier #709)

The choice would depend on what exactly do we want the Mentors page to portray. Waiting for your views on the above. @abhishalya

abhishalya commented 4 years ago

@chttrjeankr Right, good research around this. So we want to change the existing implementation a bit, what we need is to get all mentors for the completed projects in latest program year (right now its 2019). In other words we need to list all mentors for all official (completed) projects for the latest GSoC coala participated in.

Now this might be a bit tricky with the existing data, you can have a look at https://github.com/coala/projects/pull/729 for reference. You can checkout webservices https://gitlab.com/coala/landing and see doing this is better with or without webservices involved. (webserivices might not be in good shape right now)

chttrjeankr commented 4 years ago

So we want to change the existing implementation a bit, what we need is to get all mentors for the completed projects in latest program year (right now its 2019). In other words we need to list all mentors for all official (completed) projects for the latest GSoC coala participated in.

@abhishalya The best solution to this would be if each project has a date/year attached to it. We can then filter by year(latest program year), initiative(GSoC) and status(completeness) and get the required projects and their mentors.

Or, having the initiatives be different. Rather than using GSoC, we may introduce GSoC19 initiatives, and similarly for RGSoC and other annual programs too, to maintain uniformity. This would need some manual updating to the project structures (I'm not sure where site.projects is fetching data from)

Now this might be a bit tricky with the existing data, you can have a look at #729 for reference. You can checkout webservices https://gitlab.com/coala/landing and see doing this is better with or without webservices involved. (webserivices might not be in good shape right now)

As far as this is concerned, the way to fetch results in #729 doesn't seem to work anymore. And yeah, webservices are in a pretty bad shape right now, with the last commit over a year ago. So, maybe involving that wouldn't be the best idea.