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

Project proposal: Improve the projects website for use by other GSoC orgs #394

Open
jayvdb opened this issue Nov 1, 2017 · 7 comments
Open

Comments

@jayvdb
Copy link
Member

jayvdb commented Nov 1, 2017

https://projects.coala.io/ should be easily usable by other GSoC orgs, and potentially other GCI orgs by the end of this GCI.

However, the needs of other orgs hasnt been taken into account when build it.

A reasonable project proposal was put together in 2017, at #226 , but has been closed as the project hadnt finished being defined. As this type of project will tend to be 'easy' by default, a significant amount of analysis of other orgs requirements should be done before proposing the idea, in order to find challenges that make this project significant enough for GSoC.

@jayvdb
Copy link
Member Author

jayvdb commented Mar 27, 2018

Probably also worth considering including making this repo better designed for GCI (#299)

@jayvdb
Copy link
Member Author

jayvdb commented Mar 30, 2018

We have an applicant for this project, so it needs to be on the website.

@pydevsg
Copy link
Member

pydevsg commented Nov 7, 2018

Hi @jayvdb , I'm willing to work on this issue. Can I work on it?

@KVGarg
Copy link
Contributor

KVGarg commented Nov 16, 2018

Hi @jayvdb , I would like to work on this project and also I'm having some few ideas that how other orgs can use our projects website will share these ideas in a new project proposal.

@dshahid380
Copy link

Is this issue open ? Can i work on it ?

@KVGarg
Copy link
Contributor

KVGarg commented Feb 28, 2019

@dshahid380 Yes, it’s still open 😇

@KVGarg
Copy link
Contributor

KVGarg commented Mar 3, 2019

@jayvdb can some information be shared regarding #226, i.e. what was being decided to cover-up in this project ? because the file changes done by @arnab1896 in this PR doesn't give that much useful information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants