Filter projects based on language / framework / domain

[firstcontributions]

Filter projects based on language / framework / domain

[tranlv]

This seems to be very similar to #128

[jimjja]

@Roshanjossey do you have any ideas how to do it?
I have the following ideas how to achieve this:

1. Call GitHub API for each project and get the programming language it is written on. This means a request for each project and once we get a response from all requests filter by language.
2. The other way is to set a new property e.g. language to each project object and just filter by that based on user input
   I think the second option is better if we are not getting the projects dynamically, the performance will be much better.
   What do you think?

Another idea just popped up to my mind is to have a separate search for repositories with issues tagged specifically for first contributors. You will just search by programming language and all projects with issues with specific tags will come up.

[Roshanjossey]

@jimjja: I also had the second option in mind. Instead of language, I was thinking about tags which can be associated with projects. This can be more than just languages. Like libraries used, domain, etc can be associated with projects. This can also be shown in cards. I'll write up an issue for this once I get a concrete idea about the design

[genexu]

Hey guys, i just send a PR for this issue. #1567

But you can see there have TODO at filter update handler(other feature is all done), bcz it have to modify listOfProjects.js object structure, and i think, the last step is update projectList tag array to id or value in tagList.

It is easy to implement, but i want to discuss with you for best solution without broken original design, any idea?

[j-schuster]

Hey guys,

Can we still contribute to this issue?

[Roshanjossey]

@j-schuster, could you gimme 2 days to get back to you? We do have something left on this but I have to merge another pull request for you to get started on it

[j-schuster]

Absolutely, thanks for letting me know. Johann

…

On Tue, Nov 28, 2017 at 9:15 PM Roshan Jossey ***@***.***> wrote: @j-schuster <https://github.com/j-schuster>, could you gimme 2 days to get back to you? We do have something left on this but I have to merge another pull request for you to get started on it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#129 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AY4YiXpdb7yGcrZ3FwTCX93p3wpmlyv9ks5s7Oh-gaJpZM4MwypE> .

[Roshanjossey]

@j-schuster, I'm sorry this is taking a lot of time. I'm still waiting for #1567 to be resolved. If that doesn't happen in next week, let's close that and discuss on how to take this forward.

Meanwhile do you wanna check out #1722? It could be an interesting problem for you

[j-schuster]

Sure! No worries at all. I’ll get on that in the morning and wait to hear from you. Thanks!

…

On Sat, Dec 9, 2017 at 9:36 PM Roshan Jossey ***@***.***> wrote: @j-schuster <https://github.com/j-schuster>, I'm sorry this is taking a lot of time. I'm still waiting for #1567 <#1567> to be resolved. If that doesn't happen in next week, let's close that and discuss on how to take this forward. Meanwhile do you wanna check out #1722 <#1722>? It could be an interesting problem for you — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#129 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AY4YibBwv6Qv4bBsguuqUOnFUqs6ZGEWks5s-23JgaJpZM4MwypE> .

[Roshanjossey]

Closing this as this is completed.