Brainstorming ideas for Front End and structure of the project

[TG1999]

Points finalized for now
1)Login Signup form for org maintainers.
2)Dashboard with the name of the contributors and color of their badge and also the following details written above in the idea.
3)A notification board (a link will be provided on the dashboard) that will update every week and will save the contributor’s name whose badge is faded.
4)The name selected from the notification board will open an email dashboard panel where admin can select the predefined email template for asking the contributor. We can use MailChimp to create email templates which can be later on exported as HTML and CSS for further use in our app.
5)We can have cards dedicated to each contributor. Upon clicking on the card, further details like their contribution history and period of inactivity (leading to fading of cards) will appear.

[sarthak77]

History of badges as in at what point the badge changed.
Many on the channel thought it to be a good point

[TG1999]

@sarthak77 Please can you describe this idea in detail as it was discussed on the channel it will be a great help for others.

[atharva3010]

Suggestions for point number 4:

We can use MailChimp to create email templates which can be later on exported as HTML and CSS for further use in our app.

[sarthak77]

For history of badges:
Make a card for each contributor. Then, on clicking the card, his whole contributions will be shown and period of inactivity, which leads to fading of badges
This will be similar to a person's rating like in coding sites

[sarthak77]

Can we have a notification system in which a person who is not active for very long time receives a notification and if the person posts after a long time then admin gets a notification that 'X posted for the first time in a while'

[TG1999]

@sarthak77 thanks for the idea, but since this is project is only for maintainers to look inside the community not for the contributors so notification system for in activeness won't work. And for second idea of 'X posted for the first time in a while' lets look the response of the community .

[jaskiratsingh2000]

@sarthak77 I am not sure about 4th point that we should really go for it or not, because sending emails to contributor ( who maybe don't want to contribute any more) can be a spam, so it should be like notifying on the same admin dashboard about contributors added, disappeared. Maybe it can be like a survey analysis on the board it self.

And do you have any ideas that once I shared like adding integration, for instance adding user to some trello board , etc try adding this

[TG1999]

https://docs.google.com/document/d/1zKKVIV93OfrkOVU1lGj4X4oju1_8b45QeEgqRwOLTOc/edit?usp=drivesdk but in this doc, it was given already that we need to provide email to the admin @jaskirat2000 . Please resolve this query.

[jaskiratsingh2000]

Thanks for it, I think I also mentioned that this doc is just for idea, if things don't fit accurately we should not proceed, what do you say ?

…

On Fri, 12 Apr 2019, 8:34 pm Tushar Goel ***@***.*** wrote: https://docs.google.com/document/d/1zKKVIV93OfrkOVU1lGj4X4oju1_8b45QeEgqRwOLTOc/edit?usp=drivesdk but in this doc, it was given already that we need to provide email to the admin @jaskirat2000 <https://github.com/jaskirat2000> . Please resolve this query. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJwTq0YGJuslltz-v_78exWqN7Ylm-qhks5vgKB7gaJpZM4csH99> .

[TG1999]

I think then how will this product help in sustenance if maintainers cannot ask contributors about their disappearance at least one mail should be sent so they can know is the contributor interested or not or he/she is busy with something else.

[TG1999]

Without this feature, it will be just a community tracker which is very common.

[jaskiratsingh2000]

I agree with that, but do you think really that once the maintainer or admin sends an email and if contributor is bot interested to contribute any more will reply ? We need to think this in both way

…

On Fri, 12 Apr 2019, 8:39 pm Tushar Goel ***@***.*** wrote: I think then how will this product help in sustenance if maintainers cannot ask contributors about their disappearance at least one mail should be sent so they can know is the contributor interested or not or he/she is busy with something else. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJwTq9R20KqYZD8OEhxftJcUGjiLaykKks5vgKGqgaJpZM4csH99> .

[jaskiratsingh2000]

I want others to comment on this

…

On Fri, 12 Apr 2019, 8:42 pm Tushar Goel ***@***.*** wrote: Without this feature, it will be just a community tracker which is very common. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJwTq8jB9ltkFxK-RnMhvgHP_AD8boyDks5vgKJLgaJpZM4csH99> .

[TG1999]

Fine @jaskirat2000 I am getting your point, let's see what other's has to say.

[sarthak77]

@sarthak77 I am not sure about 4th point that we should really go for it or not, because sending emails to contributor ( who maybe don't want to contribute any more) can be a spam, so it should be like notifying on the same admin dashboard about contributors added, disappeared. Maybe it can be like a survey analysis on the board it self.

And do you have any ideas that once I shared like adding integration, for instance adding user to some trello board , etc try adding this

Maybe if someone wanted to contribute and was busy at that time could use this mail and inform the mentors about his willingness to contribute