-
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
Discussion and Q&A of Outreachy + GSoC ideas 2021 #9257
Comments
This is My Proposed Idea User Interface Improvement Part of: https://github.com/publiclab/community-toolbox Description: This project is a platform dedicated to community growth and getting insights on organization-wide activities. So, we need to improve the User Interface for the whole project in order to make it more friendly for especially for
List: https://gitter.im/publiclab/publiclab Prerequisites: HTML, CSS, Bootstrap ,and JavaScript Difficulty Level: medium Potential mentors: Jeffrey Yoo Warren, ADD YOUR NAME HERE |
Hi Yogesh, we will note this idea and discuss with our @publiclab/community-reps however as @cesswairimu noted in #9283 our default policy is to consider primarily ideas from our ideas list. But I appreciate your attention to the community toolbox project which is indeed very important to our community! 🎉 |
About me -Name - Vivek SinghGithub Handle - vivek-30Email - vikky30singh@gmail.comEducation - B-Tech (Computer Engineering) [currently in 2nd Year] Project Description -As we all are aware of Image Sequencer, a very cool and efficient sequencer which works in a very constructive manner with support of many strong modules and well protected by robust tests. It has everything in it as a complete package to fire-up. Problem/issue -But!!! As this sequencer is based on plain vanilla javascript, and raw HTML we have reached a kind of saturation point of it .we are compromising with the powerful features of great Technologies out there. which not only improve its current behaviour but also leaves many aspects to be covered for future reference and also give a great Compatibility with many such Technologies. Solution/Idea -I did some research for this and some experiment on this and thought that we should
You must be wondering that why to shift it to react if we have everything with us already.But Before Diving straight to conclusion i would like put some key points like -
once converted to react we can make use of some static site generators like Gatsby which not only solves above mentioned problem but also enhance users experience.
what more -Few more Changes related to performance and for better user experience that i had in my mind.which can be done with or without react -
demo for above idea - Screen.Recording.2021-03-14.at.4.20.28.PM.mov
Contributions In PublicLab/ImageSequencer -
Why Me -Before suggesting any change mentioned in this proposal i have worked on exactly similar to them (almost all) so that i have a clear understanding of how i will be going to accomplish such task. Examples -
5 like wise i have searched and worked for other solution as well. finally -
|
@jywarren sir could you please provide a feedback for this proposal. |
Hi, @jywarren and @cesswairimu here Translation system refinements I guess the only users who have an account on Transifex those users can only translating the website into different languages using Transifex, and also only in production mode, we can see the footer? Actually, what are the parameters we need to refine here? |
Hi, @jywarren and @cesswairimu as only in production mode we can select any language but at localhost, it shows me Spanish to follow on the Twitter button how can I change it to English now? |
Since it's mentioned that the first two projects are for Outreachy applicants, so its better that a GSoC candidate doesn't choose the first two projects. Am I right? |
Hi all, i'll copy in some answers I gave in our chatroom so all can see!
Also, i just updated the Education project with:
|
Hi @YogeshSharma01 -- you can use this URL to switch: https://publiclab.org/change_locale/es where |
Hi all, just noting that @cesswairimu has posted our official GSoC call for proposals here! https://publiclab.org/notes/cess/03-24-2021/call-for-2021-gsoc-proposals |
Hey @jywarren, @cesswairimu and mentors. Dropped in my draft proposal at https://publiclab.org/notes/barun1024/03-24-2021/gsoc-2021-proposal-geographic-features-refinement. Would be glad to get feedback on it :) |
Hi, @jywarren here Translation system refinements I guess the only users who have an account on Transifex those users can only translating the website into different languages using Transifex. what are the parameters we need to refine here? |
Hi @YogeshSharma01 -- my understanding is that when you follow the prompts (also see https://publiclab.org/translation) -- you are guided to set up an account. Do you think there is more we can do to smooth this workflow? To make it easier and lower barrier? Or are you asking something more specific about parameters for Transifex API integration? Thank you! |
@jywarren I have the same query regarding the parameters we need to consider for refining the custom translation helper you mentioned above but can you also mention parameters regarding the Transifex API integration that we need to consider, and anything else I should look into regarding the translation refinements project. Also, I have posted the draft proposal here: https://publiclab.org/notes/govindgoel/03-25-2021/gsoc-proposal |
Hi, @jywarren exactly more specific about parameters for Transifex API integration? |
Hi @jywarren and @cesswairimu, I had a few questions regarding the spectral workbench integration project idea under GSoC. Pls have a look. Thanks :)
|
Hi @YogeshSharma01 @govindgoel I've added to the Translation idea:
And also adding that I believe we need an additional "guide" on the process of importing translations from Transifex, perhaps at https://publiclab.org/wiki/translation or https://github.com/publiclab/plots2#internationalization. |
Also adding more fully, i hope this helps!:
|
Hi, @jywarren when I try to translate the text by clicking on the 'Get Started' in the globe icon, I'm directed to the 404 page on transfix website. |
The Rails app should manage all user data! We should be able to "build in" the JS functionality for the capture interface similarly for how we did for the spectrum display interface, with the Rails app managing all the stateful back-end and database and even data management, and a pretty minimal "handoff" of new data from the capture interface to the "host" Rails app. See how the original JS code from long ago managed both saving new spectra (using an HTML form on the page to submit) and fetching calibration data: https://github.com/publiclab/spectral-workbench/blob/main/app/assets/javascripts/capture.js#L356-L385 You can see where the server responds to these requests on the server side in this controller: https://github.com/publiclab/spectral-workbench/blob/main/app/controllers/capture_controller.rb
Much of the new capture interface at https://publiclab.github.io/spectral-workbench.js/examples/new-capture/ is already written, but there may need to be some new code adapted from the previous version for:
This is still a pretty substantial project but it's nowhere near a rewrite of the capture interface itself! I hope this is helpful! |
@jywarren one more thing regarding the project as it is mentioned [This project may be combined with another small project]. So do I need to do any specific changes or mention in the proposal, for example, project timeline. |
Oh no! I wonder if either our account expired or if they substantially changed the API and our link no longer works? Would you be able to open this in an issue? Thank you @YogeshSharma01 for finding that. |
I think we would want to hear the order you propose and how you'd organize your time, and also why you think these two projects could be completed within the allotted time, so we know you have a full understanding of the work to be done. Thank you!!! |
Hi @jywarren and @cesswairimu |
Hi @17sushmita -- no, we accept applications for these from both programs. Yes, we would love to have your application through the GSoC program! Thank you! |
Hi @jywarren, I have a query regarding the Legacy Code deprecation project. It has been mentioned to produce archival export of the data. So I want to know which format will be desirable: .sql, csv, json, or anything else. Thank you! |
Also, another query I posted here #4072
|
Hi, Gaurav! Good questions. for the export data format, I think SQL is
probably fine.
As to drupal_content_type_map columns, I think we should assemble a
readable string from them, perhaps humanizing the column names and
assembling Markdown text from them along with their values? Thanks!
…On Fri, Apr 2, 2021 at 9:42 AM Gaurav Singh ***@***.***> wrote:
Also, another query I posted here #4072
<#4072>
Hey @jywarren <https://github.com/jywarren>. I have a doubt, I believe we
are deprecating the drupal_content_type_map model, and as mentioned in this
issue #956 <#956>, we are
merging the drupal_content_type_map model to the map node body field. Since
the body of a node is a text field, how can we merge the content_type_map
table in that as it contains several columns? Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9257 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAF6J67QOYG2X2DVYCN7NLTGXCTBANCNFSM4YPZRAPQ>
.
|
Hi all, i wanted to drop in some notes i left on @govindgoel's proposal that really applies to all proposals for the translation system!
Thanks! I hope this is helpful! |
Also, with regard to the idea of an additional guide for how to import translation files, I've added to the above description:
|
also thanks to @YogeshSharma01 for investigating the Transifex link 404 issue. Thinking about the recruitment process, i changed the title of that issue to think about how to smooth the process for first-time translators. Maybe this could be part of the plan too! #9394 |
Hi, @jywarren Just want to confirm that we want to implement i18n in js because we don't want to reload the page whenever the user selects or changes his language so that our user experience is improved and gets the page in a real-time environment. |
Hi @YogeshSharma01 actually the i18n implementation is not for preventing a page refresh, but in order to extend the ability to translate to elements which are created/generated only using JS. These include:
It also allows us to consider how to extend translations into database-backed features such as the footer. By contrast, when changing a language we probably /do/ want to refresh the page, as there will be many elements which will make use of the ruby, server-side helpers, and converting them to use JS in that one scenario probably introduces unnecessary complexity and maintenance burden. I hope this makes sense! Thanks for the excellent question! |
I wanted also to respond to @daemon1024's question about geographic scraping/caching/microservices:
I think there are a few options on this. But the main thing is that we are making arbitrary bbox (bounding box) queries to an API using 2 latitudes and 2 longitudes, so a URL-based caching system probably won't work well, since people will zoom and drag the map in unpredictable ways. However, the results are JSON, so we might think about how to store JSON objects in a geographic index for fast retrieval. Our database is actually not set up for that, as we use the more general purpose tags "lat:" and "lon:" and so we can't do as efficient database indexing on those. this is the query we get when we go to https://publiclab.org/map#6/41/-71, for example. Learn about this kind of API query here: https://publiclab.org/wiki/api So I think we can think about 2 components - the "storage/retrieval" using a query /like/ the one above, and the mechanism to "scrape and store" from the PL API into that storage system. For storage/retrieval, there seem to be many good options, i'm thinking node.js for lightweight and fast, but we can be flexible: https://duckduckgo.com/?q=efficient+nodejs+geojson+database&atb=v121-6&ia=web For the scraping, I'm not sure. Maybe we could think about whether we are constantly scanning by region, or if accessing the microservice triggers a deferred re-fetch from the original API? These are really good design/architecture questions to weigh pros/cons on. Thanks @daemon1024 !!! |
Thanks a lot @jywarren for the detailed response 😬. That does clarify a lot of things for me and given me some context for what to look into. Will get back to you in the proposal comments after some investigation ✌️ |
Also a reminder for everyone, The deadline for submitting the proposal on official GSoC website is in 2 hours. Not really sure if it's region specific but I would suggest everyone to submit the PDF immediately to be safe, you can keep modifying it till the deadline. All the Best everyone 🚀🎉 |
Hi all, i've crossed off a couple items from the first idea on Education related refinements, as @TildaDares correctly pointed out that some work has now been completed on it. Don't worry too much if this is already in your proposals, it's OK. But I did add a couple new items to try to round out the idea to compensate:
It is possible more will get completed before the session begins, and that's pretty natural for a constantly evolving project like the Public Lab website -- but we can just keep track and adjust the idea outline accordingly! Thanks, all! |
The discussion issue for GSOC/Outreachy 2022 is open in #10754. Thanks everyone! |
Hi all! We've completed our ideas list for Outreachy and Google Summer of Code 2021, and we are sharing it here for discussion. We often find that key info needs to be added or expanded upon to help people understand the projects, and are going to try discussing them all here (or in "breakout issues" if this gets too long) this year.
Remember that we have not yet been approved/confirmed for either program (as of March 2 2021) but in the interest of discussion and collaboration, we're posting this now. Thanks! 🤞
The official listing is at https://publiclab.org/wiki/gsoc-ideas#2021+Ideas and we'll leave that one as it is (as it's nice and short too, easy to browse).
By contrast, here, i'll post the full text, but we'll keep editing it and refining it as we go, based on your input.
Outreachy folks -- two of these projects -- the first two -- are posted for Outreachy. That means that if we get one or two Outreachy fellows, they will have priority to take those projects. However, it does happen that we have been able to accept more than one person per project. We hope this page will be helpful for ANYONE who wishes to build a project or proposal around these ideas. Thanks for being friendly, cooperative, and supportive to one another!
Also watch out for Welcome issues to go up in the coming days to ask folks to introduce themselves, and to otherwise offer support and info on the application and selection process.
Lastly, THANK YOU SO MUCH for your interest! We are so excited to have the chance to work with you! 🎉 🎉 🎉 🎉 🎉 🎉 🎉
Posting here so we can host a Q&A about our Summer of Code programs (Google Summer of Code and Outreachy), the project ideas for this upcoming season, and begin to refine the descriptions in more detail than we do on the formal listing at https://publiclab.org/gsoc-ideas
2021 Ideas
Education-related usability upgrades
Part of: https://github.com/publiclab/plots2
Description: Due to the growing community of educators using our PublicLab.org content management system, we are hoping to tackle a collection of systems, features, and fixes focused on educational users, and incorporating feedback from our community of educators. This project will include changes and fixes to our draft saving system, our coauthorship model, explanatory displays for complex systems like our geodata storage, modifications to our content moderation and spam filtering systems, and even changes to our username autocompletion scripts, all culminating in a smoother and more coherent system for educators across the US gulf coast who are working with students on environmental and environmental justice topics.
Tasks include:
Filter out known spam from replies to comments, as described in: Hide replies to comments that have been spammed or aren't yet moderated #8854(completed)Complete email notification opt-outs for moderators, to improve this system for educators, as described in Filter out moderators who've checked "Do you want to be notified by a email for moderation emails?" in /settings #9114(completed)/v2/dashboard
- Replace/Rename Dashboard V2 References #9278 (if not complete by start of session)List: https://gitter.im/publiclab/publiclab
Prerequisites: HTML/CSS, some JavaScript, some Ruby on Rails
Difficulty Level: easy
Potential mentors: Jeffrey Yoo Warren, Cess Wairimu, Sudipto Ghosh,ADD YOUR NAME HERE
Tag/topic system refinements
Part of: https://github.com/publiclab/plots2
Description: Our growing community has seen a major reorganization of content and activity around topic areas in the past year or two, and as this featureset has matured, we are looking to refine and improve it based on community input. This project would include the following:
locked
by a mod/administrator, only mods/administrators can add/delete tags on that page (building on existing system at https://publiclab.org/wiki/locked) (To prevent banned users from adding tags as a form of spam.)parent:____
tags (as described in https://publiclab.org/wiki/power-tags#General+power+tags)List: https://gitter.im/publiclab/publiclab, https://gitter.im/publiclab/publiclab
Prerequisites: JavaScript, Ruby on Rails
Difficulty Level: medium
Potential mentors: Jeffrey Yoo Warren, Cess Wairimu, ADD YOUR NAME HERE
Geographic features refinements
Part of: https://github.com/publiclab/plots2
Description: Public Lab community members are increasingly sharing geographic context while sharing on the PL website. We have a robust geographic metadata system and site-wide prompts to add geotags. This project will focus on key optimizations and additions which will smooth and expand geographic features, including:
List: https://gitter.im/publiclab/publiclab, https://gitter.im/publiclab/publiclab
Prerequisites: JavaScript, Node, Ruby on Rails
Difficulty Level: hard
Potential mentors: Jeffrey Yoo Warren, ADD YOUR NAME HERE
Translation system refinements
Part of: https://github.com/publiclab/plots2
Description: (This project may be combined with another small project) Our internationalization (i18n) system exists but lacks a consistent workflow for importing new translations, as well as suffering from some HTML parsing and UI shortcomings. This project will:
List: https://gitter.im/publiclab/publiclab, https://gitter.im/publiclab/publiclab
Prerequisites: JavaScript, Ruby on Rails
Difficulty Level: medium
Potential mentors: Jeffrey Yoo Warren, Cess, ADD YOUR NAME HERE
Legacy code deprecation
Part of: https://github.com/publiclab/plots2
Description: (This project may be combined with another small project) Our codebase retains a variety of old database models, code segments, and removing them is a delicate task involving correcting tests, restructuring the database, and more. This project will:
List: https://gitter.im/publiclab/publiclab, https://gitter.im/publiclab/publiclab
Prerequisites: JavaScript, Ruby on Rails
Difficulty Level: medium
Potential mentors: Jeffrey Yoo Warren, Cess, ADD YOUR NAME HERE
spectral-workbench.js JS/Rails integration
Part of: https://github.com/publiclab/spectral-workbench, https://github.com/publiclab/spectral-workbench.js
Description:
Our newly revamped and tested library at spectral-workbench.js was designed to work both on its own (https://github.com/publiclab/spectral-workbench.js/) or as a JavaScript component in a larger system, the spectralworkbench.org Rails application. Work on the standalone library is nearly complete and this project will take on the integration of the newly revamped and re-organized code into the parent Rails application, following a pattern shown at https://github.com/publiclab/inline-markdown-editor for housing a JS project within a Rails project. Parts of this project are already included for displaying saved and graphed data at pages like https://spectralworkbench.org/spectrums/205427 (see integration at https://github.com/publiclab/spectral-workbench/blob/98dbde7a881788f7bd48db59eee616d6de70054b/app/views/spectrums/show2.html.erb#L22-L29), but the new code will replace the live capture interface at https://spectralworkbench.org/capture/, and will need to be able to access the following server-side resources and routes:
The current JavaScript code at https://spectralworkbench.org/capture performs all of this, and should be saved at https://spectralworkbench.org/capture/legacy, while the new code should be launched first at https://spectralworkbench.org/capture/new and compared for feature parity with the legacy version before any legacy systems are move or modified. The project will also require some Rails full-stack system tests to confirm functionality in the new UI.
A LOT more information on this was just posted in a comment, click here to read it in full: #9257 (comment) and copied into a new issue at publiclab/spectral-workbench.js#219
List: https://gitter.im/publiclab/publiclab
Prerequisites: JavaScript, Ruby on Rails
Difficulty Level: medium
Potential mentors: Jeffrey Yoo Warren, Cess, ADD YOUR NAME HERE
The text was updated successfully, but these errors were encountered: