-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Weekly Community Check-In #60 - Soc Community Bonding wrap up #7950
Comments
Hey guys,
My main goal for this week is to start increasing Spectral Workbench test coverage percentage (currently 68%, goal is >90%) with @gr455's help. So I can proceed with the upgrades with more confidence. Regarding the Mapknitter's exporter I intend to work on Sebastian's feedback given at publiclab/mapknitter-exporter-sinatra#47 so we can get that merged too. |
That's so awesome @alaxalves -- increased coverage will be so great for then making upgrades. It'll give us enormous confidence. Do you think that system tests which walk through the steps in the tutorials in https://publiclab.org/wiki/spectral-workbench will be possible? Fantastic! I merged your SimpleCov/CodeCov PR too. Great work! |
Hi folks via Outreachy and GSoC! I wanted to highlight a couple notes I left for @keshavsethi on:
Finally, it's a good idea to think about what would be a minimal milestone, or set of changes we could refine and get completely right before merging, in each PR you make, leaving further new ideas and projects for later PRs. This ensures we don't have a long-running branch that will be harder to review, catch bugs in, and rebase/sync in order to merge. We want to do these things in bite-sized pieces so we can be really thorough! Thanks, all! Hoping these tips help you structure your work as you begin!!! 🎉 💯 🙌 cc |
Hey @jywarren Thanks so much for the notes 🎉 And @alaxalves Awesome work 🔥 So this week I have been researching more on the codebase and how to optimise further. Have certain doubts about how we should organize the packages (yarn vs gem vs cdn) and if where should we keep the files (assets.rb or application.js/css or not a part of the asset pipeline). Need your help with these folks ✌️ Have opened some PRs that require reviews #7937 #7938 #7943 #7939 #7945 Also have started working on my blog which I am hosting on my personal blog site (found this great jekyll theme) this is an initial draft: https://tlazypanda.github.io/opensource/2020/05/09/outreachy'20-my-journey-with-publiclab/ rest is under construction 😅 Looking forward to feedback ✌️ |
Thanks, @jywarren!!. I am currently working on publiclab/PublicLab.Editor#487 . If anyone has faced Bugs related to code module please list that in the issues or if you can provide suggestions regarding already listed bugs in the issue than that would be even more beneficial. Does anyone know how to test Editor post changes locally? Like if we write something on http://localhost:3000/post and then post it . This doesn't show, how the content would look on in the actual website. Is there any way or workaround? |
Hey everyone! I've been working on publiclab/PublicLab.Editor#457. The last week was spent digging through the code, going through the various opened issues, finding the concerned code, rigorous testing to find something relevant for a bug or ways to reproduce it and trying to leave feedback wherever I could. |
Hey all, anyone would like to open this week's check-in? |
Sorry for the delay yesterday was a holiday in Kenya... New check-in here publiclab/PublicLab.Editor#523.. Thanks all |
Also noting to folks that I'm finishing up reading through and responding to your comments in this check-in as well, today! Thanks for a great week! @Shulammite-Aso @NitinBhasneria @keshavsethi perhaps we'll hear from you (even briefly) next week? I know you've been working hard in various issues and I definitely see you -- but just to get in the habit of chiming in here would be great. Thank you so much! |
Hi everyone! 👏
We all at Public Lab 🎈 - learn, grow, work, brainstorm ideas, contribute together so why not share about our weekly goals and the awesome work we have done at Public Lab with each other, so we can support and collaborate with each other better. We have a Community Check-In each week, where every community member can share something about their work from the past week and about their current week's goal 🎯 . You are also welcome to share fun-fact 😄 , new ideas 💡 , your learning goals ☑️.
We believe in collaborative efforts to support our community. We are running a learning platform which helps a newcomer to become master of tomorrow. 💯
Community Bonding wrap up
Let us know what you will be working on this week and if blocked express it below so that you can get help
To Outreachy and GSoc Interns
Hope the community bonding period has been great and you are ready to start coding the summer away next week 😃 ..if you have any further questions on the anything on the project or community feel free to leave a comment on the planning issues or here. I would like to hear how the past two weeks have been please leave a comment here on how the experience is so far. Also if you have any blogs leave the links below so that we can check them out 👍
To mentors
If you haven't had a chance to check who you will be mentoring this summer please do so within the week and say hi to them on the various projects planning issues and checkout the amazing conversations that are going on there 🎉 🎉 and maybe start being part of them. 😃
Reviewers and fellow contributors
We would love your help reviewing the interns PRs as they start coming in and also would appreciate chip-ins on discussions on various issues..Let do what we do best...collaborating 🎈
Next Check-in
If you would like to open the next check-in..Leave a comment below. We are happy to help if its your first time
Thanks everyone and have a great week 🎈
The text was updated successfully, but these errors were encountered: