-
Notifications
You must be signed in to change notification settings - Fork 207
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 #27 - Overestimated Issues #772
Comments
One of the issues I thought that would be the hardest was this one -> https://gitlab.com/klara-org/klara-api/merge_requests/4, in this case, I had to implement a distributed database with replication among the clusters. In the end it turned out to be more easier than I thought. Progress Currently I have finished with Mapknitter's Rails 5.2.3 upgrade, I have removed the deprecation warnings, fixed the remaining tests, started defining routes and removed the generic routing. Also, I have fixed the travis pipeline caching for bundle install and yarn. Upcoming goals I intend to solve the upcoming issues that will come up with the Rails 5 upgrade and in the meantime I intend to start the upgrade to 6-rc1 version. I also intend to implement the same improvements I've made on Mapknitter to Plots2, when it comes to travis, codecov, caching, refactoring and perharps the rails upgrade too. Work completed last week
What things I did collaboratively last week? I have given tips to Image Sequencer's Yarn migration and reviewed some PRs. I have also helped with Codecov's fix when generating a report. I have also reviewed some PRs but I can't remember the ones to link. |
Hi! This is a good topic - it took me a little bit of thinking. The only one that comes to mind is that I recently looked into deprecating Bower and updating to use NPM only for LDI. I thought it would be an ordeal - but the switch turned out almost as simple as 1. Delete bower.json 2. Add package-lock.json Not a GSOC student but this template is useful anyway!
|
Hey y'all, working on an open source sensor platform here: https://github.com/ProgressiveCoders/EnviroTrack-Node, currently working on the MQTT->Prometheus gateway (https://github.com/inuits/mqttgateway), then I'll work on converting the voltage readings into ppm of measured toxins |
Great progress @alaxalves! And, thanks @konolga for the help with MySQL issue 🎉 |
I think both of my PR's are basically done on my end (#5962 and #5896). Unfortunately, my life imploded yesterday and I'll be moving across the country alone with no job or any other certainty. I don't know when or if I'll be back online. I hope you can use what I have committed to finish up. Thank you for welcoming me here. I was happy to be able to help a little. |
Hey @michelelong thanks for helping with the issues and sorry to hear about the your setbacks. Hopefully you will find a job or something soon. Take care 💜 |
All the best @michelelong and thank you so much for your contributions and you're always welcome in our community. |
Thank you so much @michelelong and please take care! |
Hey all, I'm working on integrating action cable on top of the rails 5 upgrade branch on mapknitter. Will have to make certain events in Leaflet.DistortableImage to handle all realtime changes when placing images. Had a discussion with @jywarren @divyabaid16 @gauravano @jainaman224 here. Any suggestions would be really helpful!! Let us know if anyone wants to be a part of it. And yes rightly said by @sashadev-sky , I too had the MySql issue when setting up the project. Was not able to figure out at the end. So, had to setup using sqlite locally. I think a better mysql documentation would be helpful. |
Connecting publiclab/Leaflet.DistortableImage#328 here as well. Any help here would be highly appreciated. |
Hey everyone! I am doing all the integration locally and I haven't published a PR due to some reasons, but I will be doing it pretty soon. I have also started to work on creating a "Per-User data" page, where the users can see some information regarding the files they upload and have the option to delete those files etc. There's also some discussion going on about "Creating a Research Note" out of the plotted data although it's a bit complex, but I will be going about that one too soon. Have a great week everyone! cc @jywarren @namangupta01 @gauravano @IgorWilbert @Souravirus |
Anyone interested in opening new check-in? |
Also, we have Open Code Call tomorrow - http://publiclab.org/opencall [Reminder] |
@gauravano I'll do it :) |
You can open check-in by tomorrow evening and in any repo of your choice. Also, please mention people mentioned #772 (comment) and #772 (comment) we don't want to disturb others. Also, feel free to add names if you recognize a new contributor or from https://code.publiclab.org. Thank you! |
Sure @gauravano !! |
New check in up at LEL |
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. 💯
If you're new here, welcome, and please comment a Hello below, we would love to work with you. If you're looking for new issues, please try some of our first-timers-only issues.
We're SO EXCITED to have your help!
Is there anything, you would like to share with us from past week's work? What is your plan for this week?
If you have not planned yet, just leave a Hello! 👋 so that we know that you are in sync with us 🔃 and doing well!
The coming weeks will be full of code 💻 , tasks 🗒️, fun 🎉 and excitement 😃!!
As always, if you're waiting for a review, or if you're stuck, please request help here OR leave a comment with @publiclab/mentors @publiclab/reviewers for some input. 🙌
Gitter
Gitter is an active chatroom in our community and we'll be sending weekly reminders about check-ins there. Be sure to sign up there for these updates or just to join the conversation. You can also join us through http://publiclab.org/chat 💬.
This Week's Theme:
Overestimated Issues: Issues that seemed hard but turned out to be very simple.
This week I'd like to hear from all some situations that we got an issue to fix and seemed to be very complex at first, but when we started doing it, it turned out to be pretty easy.
You can find our list of previous check-ins here
Note to Summer of Code interns:
Hi, we request all the SoC students to include the below-mentioned points in their check-in comment:
It is like a weekly scrum. Be flexible.
With FTOs and PR reviews, we are seeking to develop a much more friendly and collaborative platform. We want you all will involve people in your project. You all will develop skills like leadership along the way.
Thank you!
The text was updated successfully, but these errors were encountered: