-
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 #63 - Stay Updated! #8040
Comments
@moliver4, @justinelai, @Snouzy, @stevenalila, @Digiox, @yandu31, @milosv1, @jamescapps, @Nevenem, @chirag-wadhwa, @yogeshjdeshmukh, @omizrahi99, @theOpetunde, @sailahonkanen, @robin-natale, @avidler, @ccyccyccy |
Hey Everyone 👋 Hope you all are fine ❤️ This is my update for last week
Thanks!! |
Hey everyone 👋 This week I worked on some accessibility issues, issues fixing the icons error migration to FA v4.7, loading critical css and rest asynchronously ( #7996 review required help!! 😅 ) , opened some ftos for newcomers and started working on lazyloading images #8043 (any feedback appreciated ✌️) Also need inputs on #7991 before proceeding further 😅 Also welcoming some new contributors to Publiclab 🎈 🎉 👏 @Janitham97 @markkulube @JapneetSingh5 @imanishbarnwal Thanks everyone for your contributions to Publiclab!! |
@keshavsethi - i see you've linked all your PRs together here, so apologies for asking that in another issue! This is super. If you could also link them together to the Spam milestone that'd be great as well! Great work! @Tlazypanda you're doing great work too! I did note some oddities with asset loading paths in a few related issues and I think this is something to watch out for, although at least one may not have been related to your work -- but I'd super appreciate your input as you've been dealing with asset loading in any case! Looking at your linked-to issues as well. Thanks a ton! And WELCOME to new contributors! 🎉 🎉 🎉 You're awesome!!!! |
@keshavsethi #8038 looks really great. I LOVE system tests because they really show reviewers (and future contributors) how the code is supposed to work, and they make merging PRs much easier, as they guarantee functionality! Approved and ready to merge with your final confirmation! |
Folks in the Editor project - @Shulammite-Aso @NitinBhasneria @shreyaa-sharmaa @keshav234156 -- i see lots of great work and both you and other @publiclab/soc folks may want to look at the coordination issue @emilyashley opened at publiclab/PublicLab.Editor#532 - covering how to get changes to upstream libraries ready to be released and merged downstream all the way to PublicLab.org. One note on that is that we haven't republished PublicLab.org for a couple weeks and pending some changes to the /spam2 page (@keshavsethi) and the map icon assets (@Tlazypanda) we can do that soon and you'll see your work go live! 😅 🎉 Finally, some of you are starting to see how certain issues/tasks/sub-projects are seen as higher or lower priority by the @publiclab/community-reps team, and that's ok! I suggest making a Thanks, everyone! |
@Tlazypanda - just to clarify, i see one issue with an icon at https://stable.publiclab.org/tag/balloon-mapping -- i think probably a fontawesome version issue? |
Hey @jywarren I have resolved the icon errors here #8041 I think this should resolve all the errors 😅 can you kindly have a look ? Thanks ✌️ and again sorry for all the inconvenience caused with this issue, the migration caused unwanted changes in separate libraries and features not present in the codebase |
Done! No problem at all!!! |
Hello all, and thanks @keshavsethi for opening this issue 🎉 Also anyone willing to open next week's check-in kindly express your interest here. Thanks |
Hey everyone! |
Moved to #8059. Thanks everyone |
Hi everybody! 👏
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. 💯
Stay Updated
This week lets update and document our progress properly which will help fellow interns, mentors, and other members to review our code and give suggestions. Weekly standups and documentation by making weekly research note is a good idea. This can have some list of tasks that are completed and future plans including some major issues which we are currently facing and blocking our progress. This will also help us to be productive and updated in these times
There are three ways in which can keep our mentors updated:
To Outreachy and GSoc Interns
Thanks for the commendable work last week 🎉 🎉 Please update your progress here and let us know about issues and blockers which you are facing. It will be nice if we help each other and newcomers by reviewing and suggesting some changes. Let's work together and make Public Lab awesome 🎈
Happy coding ❤️
To Mentors, Reviewers and fellow contributors
Thanks to all the reviewers and mentors for all the efforts which you are putting in reviewing our code and helping us at every point of time 💯. Let's do our best by collaborating and helping each other 😄 🎉
Next Check-in
If you would like to open the next check-in. Leave a comment below. We are happy to help if it's your first time
Thanks everyone for making Public Lab awesome 🎈
Have a great week and year ahead all ❤️
Stay safe! 🤗
The text was updated successfully, but these errors were encountered: