Plugin by Dev /// Dev home pages #299
Replies: 6 comments 24 replies
-
|
To add to this, based on a twitter thread with @haesleinhuepf (https://twitter.com/haesleinhuepf/status/1451650535027793923?s=21), I now realize it's possible to make |
Beta Was this translation helpful? Give feedback.
-
|
So, maybe some sort of Twitter blue check could work? To indicate verified non-troll non-noob plugins? |
Beta Was this translation helpful? Give feedback.
-
|
Coming back to the original discussion :-D I think meta-plugins or plugin-collections should be maintained by others, not by plugin developers, because they have a conflict of interest. Again, Peter @psobolewskiPhD , if you think of founding a plugin-collection e.g. for quality-of-life, I would totally support you and show you how this can be achieved. |
Beta Was this translation helpful? Give feedback.
-
I recently had some discussions with @sofroniewn, @jni and others who remineded me of the first sentence on the website: "napari is a fast, interactive, multi-dimensional image viewer for Python." Thus, I have the impression non-programmers are not an important target audience of napari (anymore?). Hence, people like you @psobolewskiPhD and me, who are closer to that audience who lacks coding skills, should build the bridge between the communities. I'm suggesting: @psobolewskiPhD why don't you take care of a quality-of-life plugin collection for napari just like I maintain devbio-napari? I'm happy to help when it comes to technical difficulties. I presume you are also less biased than me when it comes to selecting plugins from other developers and thus, better suited for that job ;-) |
Beta Was this translation helpful? Give feedback.
-
I know what you mean. I just don't know how to slow down that process. Just to clarify, what I meant with acceleration. We have people from about 7 research groups here on campus who develop napari plugins at the moment. In my group it's four people including myself. In my institute, multiple research groups are founded right now and the first new postdocs arriving ask me "Shall we go for ImageJ or try napari? Shall we run our new custom microscopes with Java or Python?" What would you answer? That's what I meant with the "train". Furthermore, multiple groups ask me for "plot profile" and "cropping" tools at the same time and that's why I'm pushing out publicly available plugins such as plot-profile and napari-crop. You know, it's my responsibility to serve the needs of local scientists, especially those who can't code such plugins themselves. |
Beta Was this translation helpful? Give feedback.
-
totally get it :) and... A) I love that the answer to "Shall we run our new custom microscopes with Java or Python?" is increasingly "let's try python!". makes my heart go flutter. honestly, that really is my dominant emotion in all this. You're doing amazing stuff and I don't want to sound like I want to stop the train or anything ... just didn't know where you got the idea that non-programmers are not an important part of napari anymore, or that we're not particularly interested in the life sciences community anymore. And I hope that we don't conflate "not stopping the train" with going off and creating a parallel plugin ecosystem cause napari's not moving fast enough. You're a very visible member out there, and "with great power comes great responsibility" 😂 thanks again! |
Beta Was this translation helpful? Give feedback.
-
It was the tone in a couple of zoom meetings 2-4 weeks ago. I explicitly asked for it and got replies like "life sciences is just one thing, napari aims at a wider community" and "focus on the python community"... I misunderstood that obviously. Btw. I also know from former projects that these misunderstandings come from lack of exchange on a personal level. Remote-collaborations suffer from that. You need to meet physically from time to time and drink beer together in order to really understand each others motivations and goals. NEUBIAS was extremely successful in this context. I hope, one day that we all meet physically and clear up these kinds of misunderstandings. We should totally hava a plugin-hackathon, in Dresden for example :-) |
Beta Was this translation helpful? Give feedback.
-
i do agree with this statement very much. it is just one thing, and i wouldn't want us to make decisions that preclude the possibility of napari being useful to, for example, the astronomy or geo communities... but it's also the specific community that is very near and dear to most of the core napari dev's hearts! :) we love it too. |
Beta Was this translation helpful? Give feedback.
-
Count me in! |
Beta Was this translation helpful? Give feedback.
-
Hi @haesleinhuepf - my bad if I gave that impression - it certainly wasn't my intent. There has been no change in the mission and values of napari over the past year, and if you look at those statements they clearly indicate that we want to
see https://napari.org/community/mission_and_values.html#our-mission. As @tlambert03 said above though, this takes time to do, but we are trying to do it in a long term stable and sustainable way.
I completely agree with @tlambert03 here and now could be a good time to think about what are more of those essential features that we need to add to the core of napari, and work on contributing those to the main repo. @jni also is working on curating a list here too.
As to this @psobolewskiPhD. While it is possible, and would be of some immediate value, I'm not sure this approach is the best long term solution to sharing "starter packs". There have been some discussions with @neuromusic that one day the hub could allow people to share curated lists of plugins without having to create a new plugin, or share workflows that depend on plugins but aren't themselves plugins. We might go in the direction of meta plugins, but there could also be better alternatives that are simpler lists etc. |
Beta Was this translation helpful? Give feedback.
-
Oh great! Because I really thought the team shifted from a life-science mission to a general-python mission. Apologies for my obviously wrong interpretation. Anyway, my (teams) mission focuses on what non-coders need, as we have many of them on campus, and thus, we are going in that direction even though napari is still experimental. This train is gaining speed and we can't stop it. We are fully aware that things may break and are happy to fix them. (Did you know that Fiji breaks all the time?😉) I also hope we can contribute more to the core at some point but there are some rather political barriers to be removed first. For now, it appears to us as strategic advantage to use napari and through providing plugins make it useful for our purposes as we mostly work with 3D (+ time) data, which is hard on other platforms such as ImageJ. Thanks again everyone for the fantastic platform you're crafting and maintaining 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
Dresden plugin-hackathon Summer 2022?
…On Mon, Oct 25, 2021 at 8:43 PM Nicholas Sofroniew ***@***.***> wrote:
You need to meet physically from time to time and drink beer together in
order to really understand each others motivations and goals.
Count me in!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#299 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APFJIOZ7HUUTSYVLZXVNT2LUIYPUTANCNFSM5GRK2I5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
*Lucy Coulson Obus *(she/her)
Staff User Experience Researcher, Imaging Technology
napari.org | napari-hub.org | chanzuckerberg.com/science
|
Beta Was this translation helpful? Give feedback.
-
|
I'm in! |
Beta Was this translation helpful? Give feedback.
-
The discussion derailed a bit to broader issues, but I'd like to bump this. Having the authors be clickable on a plugin page to bring up their other plugins (even if just via search) is still something I'd really like to see. |
Beta Was this translation helpful? Give feedback.
-
It should filter as soon as you click out of the submenu... does that work? |
Beta Was this translation helpful? Give feedback.
-
|
click out? Not sure I get what you mean. |
Beta Was this translation helpful? Give feedback.
-
|
Oh! I see now! Click to select then click somewhere else. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, yes, I can see how that might not be intuitive. I've shared your feedback with the team and we'll look into it :D |
Beta Was this translation helpful? Give feedback.
-
|
Done. Check it out @psobolewskiPhD: https://www.napari-hub.org/?sort=recentlyUpdated&authors=Robert+Haase&page=1 |
Beta Was this translation helpful? Give feedback.
-
|
@neuromusic I love that the author names are clickable! Thanks! I really think this is a big improvement. Next, I would love if the author clicks went to a new landing page, not just filtered search. More like GitHub clicking on a dev? So there would be obviously all the plugins, but maybe also some copy about the dev, a picture, etc? Keep up the good work! |
Beta Was this translation helpful? Give feedback.
-
|
Great call out on the multi-dev plugin issue! |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure how it works now, because I don't have a plugin, but maybe devs of a plugin on the hub could log in, ideally using GitHub login, like image.sc, etc. and "claim" their author/dev page? Then they could provide a photo, some copy, etc. Or maybe it could be copied over from GitHub. |
Beta Was this translation helpful? Give feedback.
-
Indeed. The issue here is that PyPI's metadata only supports one author, which plugin devs get around by listing multiple in the field separated by commas or ampersands or "and". We explored parsing these and could technically do so, but not without clobbering authors like "Computational Microscopy Platform, CZ Biohub". HOWEVER! We do have a solution... If authors use the "Author" field in In the coming weeks, we're going to do some bulks PRs and will try to help plugin devs make the necessary changes to take advantage of this feature. |
Beta Was this translation helpful? Give feedback.
-
From the main page, one can search by Dev, which is nice, if you know in advance that say Robert Haase @haesleinhuepf is a superstar plugin author.
But if you're on a plugin page, like: https://www.napari-hub.org/plugins/napari-crop
you can't easily get to Robert's other plugins, as far as I can tell.
My expectation would be—at the least—that here:
Under Authors: the
Robert Haasewould be a clickable link, like all the others to the right.To go further, I think it would be a good idea to have Dev profiles/pages which would help validate plugins. I mean, as far as I can tell, anyone—even me—can make a
napari-cropplugin. in fact, I have a Gist that uses zoom for this! Derp! Obviously I'm bad, but folks like @haesleinhuepf with many plugins need to be highlighted in some way! If someone has multiple plugins that's a major form of verification, because some troll isn't going to work so hard.Beta Was this translation helpful? Give feedback.
All reactions