-
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
Discussion: integrating or merging Mapknitter into plots2/PublicLab.org #302
Comments
I'm interested but would like to brainstorm out how that would work! |
One idea would be to make it embeddable? Or allow people to start a map from PL.org but still have a separate app? |
I am in favour of embedded like the chatroom is embedded on chat.publiclab.org |
Let's continue thinking about this a bit, and discussing, without committing to a course of action yet. This will really only be possible after we make the export system external, as in #298, i think. |
I'd like to also consider that if we separate the Exporter code, there is relatively much less code remaining in MapKnitter. I'm already starting to clean up and remove unused code. We could simplify and reduce the size of the MK codebase so that the rest of the upgrades are not too bad -- mostly handling image uploading. Then the idea of merging vs. integrating could be simpler. |
Agreed. |
Roughly it will turn the exporting task (a huge resource use) into an
external cloud service. 😄
|
Got it thanks
On Sun, Jan 27, 2019, 8:17 PM Jeffrey Warren <notifications@github.com
wrote:
… Roughly it will turn the exporting task (a huge resource use) into an
external cloud service. 😄
On Jan 27, 2019 11:36 AM, "Sidharth Bansal" ***@***.***>
wrote:
Agreed.
Can you please tell what Exporter code does in brief. I am new to MK.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#302 (comment)
>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AABfJ8IZ2KpNPIfrmWFOzkn9a1W2TH4eks5vHbkxgaJpZM4aTgah
>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#302 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQxhLH_fm9GBVucGN-9iDDVB-mx1oks5vHbvogaJpZM4aTgah>
.
|
Also just to list out pros and cons to consider: Pros
Cons or issues to consider
This all leads me to think that making MK more modular and from reusable pieces with some kind of standardized integration with PL might be better than just merging it in completely, but it bears more discussion and thought. Thanks!!! |
I guess if we can integrate MK to plots2 using minimal lines of code , that would be ideal , so that we have modular and first-timer friendly code in both repos . |
Some notes on this that relate to other parts of the system:
@SidharthBansal what do you think of these ideas? |
We need to think of the data we will need at mapknitter from the plots.
One thing we want to import to plots2 is the mapknitter maps to /maps.
What do you say?
…On Sat, Feb 9, 2019, 3:18 AM Jeffrey Warren ***@***.*** wrote:
Some notes on this that relate to other parts of the system:
- see if we can read roles from plots2 user records, ideally through a
User.role call that somehow grabs the data from plots2
- see if we can send email notifications using plots2 ? Or use
commenting/notification system from there, to simplify MapKnitter? What are
the pros/cons?
@SidharthBansal <https://github.com/SidharthBansal> what do you think of
these ideas?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#302 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQ_k286rgjLiXFjMOdj95SKWN-h_Yks5vLfCUgaJpZM4aTgah>
.
|
We can discuss this in #301 |
Can we merge Mapknitter to the pl.org/maps?
Similar workflow with mapmiller can be obtained.
Thanks
The text was updated successfully, but these errors were encountered: