Community toolbox for any Open Source project 🌐

[grvsachdeva]

I guess, a year ago someone, shown interest in re-using our project. And, I also saw - https://github.com/publiclab/community-toolbox/issues/208.

For sure, this project has lot of scope and can be useful for other orgs too. So, let's do our bit in making it that useful.

• [ ] Generic code structure -- No hardcoded URL, at any place
• [ ] Consistent release cycle - We are planning this with all other projects of PL too, but this is good place to start.
• [ ] Easy to use for orgs -- Orgs, user should just require to setup a single config file. Also, instructions should be added.
• [ ] Outreach -- Spread the word

@Rishabh570 you spent a lot of time on this project and so you can definitely add more points to it. And, maybe help creating issues for this. Thank you!!

cc @jywarren

[Rishabh570]

Hi @gauravano, yes, making the project flexible for any organization or user was the goal in issue #208 and #216 was opened regarding that. Getting rid of hardcoded URLs and adding a config file was the main goal of that PR.

JSON data in the config.json file solves the goal of achieving flexibility but surely we can add more points here...consistent release cycle is definitely a priority as well as outreach. I'll be opening a long term and short term roadmap where we can add relatively small milestones which will help us achieve the big ones.

Also, the config file for this can be found here. Here's the screenshot showing the contents of config.json,

Thanks! :smiley:

[jywarren]

Hi, that's awesome, thank you - maybe we can brainstorm any additional ideas here?

Just a clarification, can the Json config file be remote?

On Mon, Aug 26, 2019, 11:50 AM Rishabh Rawat notifications@github.com wrote:

Hi @gauravano https://github.com/gauravano, yes, making the project flexible for any organization or user was the goal in issue #208 https://github.com/publiclab/community-toolbox/issues/208 and #216 https://github.com/publiclab/community-toolbox/pull/216 was opened regarding that. Getting rid of hardcoded URLs and adding a config file was the main goal of that PR.

JSON data in the config.json file solves the goal of achieving flexibility but surely we can add more points here...consistent release cycle is definitely a priority as well as outreach. I'll be opening a long term and short term roadmap where we can add relatively small milestones which will help us achieve the big ones.

Also, the config file for this can be found here https://github.com/publiclab/community-toolbox/blob/main/config.json. Here's the screenshot showing the contents of config.json,

[image: config] https://user-images.githubusercontent.com/25483260/63703273-43aa2200-c846-11e9-8928-a87deabb490f.png

Thanks! 😃

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/publiclab/community-toolbox/issues/259?email_source=notifications&email_token=AAAF6J3C3BZRIZTUYVOROXLQGP3UBA5CNFSM4IPJ32R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EZDFY#issuecomment-524915095, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAF6J6YJFQZ56VI5NWGPW3QGP3UBANCNFSM4IPJ32RQ .

[Rishabh570]

As of now, the config file should reside on the project's root and cannot be hosted remotely, but that can be easily modified, we just need to update the URL of config.json in the configure.js file.

So, what if a newcomer gets an issue suggestion to work on from the pool of unclaimed FTO issues...user would be able to shuffle if the issue doesn't suites him (all the suggestions would come from unclaimed issues' pool). Also, we can make use of gitter integration to make the process seamless. Having the chat room slider on the website would make it more approachable to a newcomer and he is more likely to drop a message regarding his queries. What do you think?

(I closed it by accident :sweat_smile: )

[jywarren]

oh that shuffle idea is so cool! friendlier than a list, too! :-))))

On Mon, Aug 26, 2019 at 12:38 PM Rishabh Rawat notifications@github.com wrote:

Reopened #259 https://github.com/publiclab/community-toolbox/issues/259.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/publiclab/community-toolbox/issues/259?email_source=notifications&email_token=AAAF6J37XA3EVQYUYFOOE23QGQBGBA5CNFSM4IPJ32R2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTIEJFQA#event-2584253120, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAF6JZAVRE5U5R2ZICYO5DQGQBGBANCNFSM4IPJ32RQ .

[grvsachdeva]

Shuffle idea sounds good!!

[jywarren]

More ideas - and outreach! I'm going to give a brief talk on this and @cesswairimu and I will do a session on it on Sunday at the GSoC mentor summit. People are already asking about it - and wondering if it could be adapted to GitLab! 😅 I created #281 to follow up on this idea.

Awesome! 🚀

[jywarren]

Thinking of shuffle, we could have it show 5 random issues from a list if the list gets too long... we have a long list of FTOs right now 😅