-
Notifications
You must be signed in to change notification settings - Fork 77
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
Planning Issue : Extend leaflet environmental layers #173
Comments
@jywarren @sagarpreet-chadha @gauravano , here is the planning issue for my project, taken from the discussions here #168 |
Hi @ananyaarun, sure we'll extend your authority. Also, you can create a project - https://github.com/publiclab/leaflet-environmental-layers/projects/new to manage the workflow once you get permissions. @jywarren also add this repo to https://github.com/orgs/publiclab/teams/soc/repositories. For now, I am adding labels. Not creating a project as you may be interested in doing that yourself (it's cool and easy way to manage 😄) . Thanks! |
Agreed with Gaurav +1 |
Noting @jywarren comment on revamping architecture #168 (comment) 😄 ! |
@gauravano , I shall create the project myself 😃 |
Yes it requires permission , lets wait for @jywarren to assign these permissions . Thanks ! |
OK, i added @ananyaarun -- exciting! Thank you! |
Hey @ananyaarun , You can update the checklist above so that i can track your progress 😄 . |
Yes, Even I wanted to start working on standardization of layers. Actually I have a few questions in this regard. Would it be convenient to discuss them with you sometime on gitter before I get started ? Thanks 😃 |
Yes sure, |
Sure, I'll open an issue shortly including the key points to take care of while going about with the standardization. We can discuss there !! |
Hi all! I'm closing this as many items are done and the others have been nicely broken out into issues. I'll add one issue for |
Planning issue for Outreachy project "Extend Leaflet Environmental Layers with new layer menu and layer addition workflow "
1) Layer display and UI based issues
(static template being developed)
2) Standardizing Layer code
(common function which could be used to reduce redundant code in layers)
3) Documentation
4) Testing
The text was updated successfully, but these errors were encountered: