From mohanapriya.narapareddy at emory.edu Thu Mar 7 10:56:26 2019 From: mohanapriya.narapareddy at emory.edu (Narapareddy, Mohanapriya) Date: Thu, 7 Mar 2019 15:56:26 +0000 Subject: read .scn file Message-ID: I am trying to execute the below command. vips copy myslide.scn mypyr.tif[tile,pyramid,compression=jpeg] But i am getting the openslide error. openslide2vips: opening slide: Slides with dissimilar main images are not supported I contacted the libvips developers but they asked to contact openslide support regarding this. Please resolve this issue. Mohanapriya ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments). -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.weihrauch at smartinmedia.com Sun Mar 24 15:24:55 2019 From: m.weihrauch at smartinmedia.com (Martin Weihrauch) Date: Sun, 24 Mar 2019 19:24:55 +0000 Subject: Getting the EXACT tilesize of an image Message-ID: Hi everyone: I have the following question: To quickly serve tiles out of formats, I wanted to know: is there the possibility to get the exact tilesize of an image through OpenSlide? E. g., if Aperio uses 240x240 px tiles, wouldn?t it be good that on the client side, I present also 240x240px tiles and by requesting them through OpenSlide, they don?t have to be ?processed? by OpenSlide, i. e. OpenSlide does not have to create a whole new tile, but use an existing one. What I am trying to say is: extracting an existing tile from a Tiff Pyramid should be way faster than creating a new tile (image in memory), copying regions from existing tiles onto it and returning the result. Thanks Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcupitt at gmail.com Sun Mar 24 16:27:05 2019 From: jcupitt at gmail.com (jcupitt at gmail.com) Date: Sun, 24 Mar 2019 20:27:05 +0000 Subject: Getting the EXACT tilesize of an image In-Reply-To: References: Message-ID: Hello Martin, On Sun, 24 Mar 2019 at 19:25, Martin Weihrauch wrote: > I have the following question: To quickly serve tiles out of formats, I wanted to know: is there the possibility to get the exact tilesize of an image through OpenSlide? Yes! I asked Benjamin this precise question back in 2011 and he very kindly added the feature for me. libvips uses it to size the tilecache it uses for openslide images. You can read the tilesize out of the openslide metadata like this: $ vipsheader -a CMU-1.svs | grep tile openslide.level[0].tile-height: 256 openslide.level[0].tile-width: 256 openslide.level[1].tile-height: 256 openslide.level[1].tile-width: 256 openslide.level[2].tile-height: 256 openslide.level[2].tile-width: 256 I'm not sure if this was ever documented: it went in as an experimental feature. It gives a useful speedup. John From m.weihrauch at smartinmedia.com Mon Mar 25 02:00:14 2019 From: m.weihrauch at smartinmedia.com (Martin Weihrauch) Date: Mon, 25 Mar 2019 06:00:14 +0000 Subject: AW: Getting the EXACT tilesize of an image In-Reply-To: References: Message-ID: Hi John: That's great, that there is a feature like that! Do we have a list of which OpenSlide formats have tiles at all and which don't (or which have e. g. weird overlapping tiles, which wouldn?t perform that way)? If I remember correctly, ndpi of Hamamatsu is tiled, but their VMS is some other weird stuff. Thanks for all your efforts and congratulations for 30 years of libVIPS!!!! Martin -----Urspr?ngliche Nachricht----- Von: jcupitt at gmail.com Gesendet: Sonntag, 24. M?rz 2019 21:27 An: Martin Weihrauch Cc: openslide-users at lists.andrew.cmu.edu Betreff: Re: Getting the EXACT tilesize of an image Hello Martin, On Sun, 24 Mar 2019 at 19:25, Martin Weihrauch wrote: > I have the following question: To quickly serve tiles out of formats, I wanted to know: is there the possibility to get the exact tilesize of an image through OpenSlide? Yes! I asked Benjamin this precise question back in 2011 and he very kindly added the feature for me. libvips uses it to size the tilecache it uses for openslide images. You can read the tilesize out of the openslide metadata like this: $ vipsheader -a CMU-1.svs | grep tile openslide.level[0].tile-height: 256 openslide.level[0].tile-width: 256 openslide.level[1].tile-height: 256 openslide.level[1].tile-width: 256 openslide.level[2].tile-height: 256 openslide.level[2].tile-width: 256 I'm not sure if this was ever documented: it went in as an experimental feature. It gives a useful speedup. John From m.weihrauch at smartinmedia.com Mon Mar 25 02:06:39 2019 From: m.weihrauch at smartinmedia.com (Martin Weihrauch) Date: Mon, 25 Mar 2019 06:06:39 +0000 Subject: Status of OpenSlide support Message-ID: Dear Benjamin: I wanted to inquire, what the status of OpenSlide is. The last commit is almost 1 year old and there are some important pull requests (problem with bif, Motic and introduction of VMIC) waiting to be introduced. I guess that you may have not the time to maintain it currently, which would be sad and a problem for so many of us, who rely on it. Maybe some of the community here (me included) could throw in some money and we could pay you or someone else e. g. a quarter or a half of his/her salary to further maintain and expand this important library, which you created. Looking forward to hearing from you. Martin From jcupitt at gmail.com Mon Mar 25 03:06:25 2019 From: jcupitt at gmail.com (jcupitt at gmail.com) Date: Mon, 25 Mar 2019 07:06:25 +0000 Subject: Getting the EXACT tilesize of an image In-Reply-To: References: Message-ID: On Mon, 25 Mar 2019 at 06:00, Martin Weihrauch wrote: > Do we have a list of which OpenSlide formats have tiles at all and which don't (or which have e. g. weird overlapping tiles, which wouldn?t perform that way)? If I remember correctly, ndpi of Hamamatsu is tiled, but their VMS is some other weird stuff. Yes, I think that some slide formats are rather complex internally. I believe openslide keeps a small tile cache for all formats, and that the _properties just reads out the tile size for that cache. As a user of the library, you can (effectively) treat all formats as tiled. John From adam at spicenitz.org Mon Mar 25 10:23:15 2019 From: adam at spicenitz.org (Adam Goode) Date: Mon, 25 Mar 2019 10:23:15 -0400 Subject: Status of OpenSlide support In-Reply-To: References: Message-ID: Hi Martin, Benjamin and I are are both quite busy with other things. I cannot speak for Benjamin, but in my case I am not able to take money to work on side projects like this. It is likely that Benjamin has a similar situation. Given this information, how should you move forward? The typical advice I give to organizations interested in OpenSlide is this: 1. Please identify someone in your organization to work on OpenSlide. This can be someone in your development group or research group, or possibly even a grad student in some circumstances. 2. Explicitly allocate some amount of time for this person to work on OpenSlide (perhaps 15-20%, possibly more while getting started). 3. Introduce this person to the list and me. 4. I will provide some of my time to answer questions and give some help getting started. 5. Depending on the circumstances, we may be able to grant permissions to this person to let them approve pull requests and do other things. This would be a good outcome, though I would have to discuss with Benjamin and the CMU folks exactly what criteria we would use for granting this. Note that, completely independently, you can fork the project and make whatever changes you like. I encourage this! But please try to publish your changes as we have done, and do so under the same license so that we could eventually merge changes back someday. Forking may still be the correct thing to do even if we do steps #1-4 above, since I can't currently say what the criteria for #5 would be. Thanks, Adam On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < m.weihrauch at smartinmedia.com> wrote: > Dear Benjamin: > > I wanted to inquire, what the status of OpenSlide is. The last commit is > almost 1 year old and there are some important pull requests (problem with > bif, Motic and introduction of VMIC) waiting to be introduced. > > I guess that you may have not the time to maintain it currently, which > would be sad and a problem for so many of us, who rely on it. > > Maybe some of the community here (me included) could throw in some money > and we could pay you or someone else e. g. a quarter or a half of his/her > salary to further maintain and expand this important library, which you > created. > > Looking forward to hearing from you. > > Martin > _______________________________________________ > openslide-users mailing list > openslide-users at lists.andrew.cmu.edu > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satya at cs.cmu.edu Mon Mar 25 10:49:43 2019 From: satya at cs.cmu.edu (Mahadev Satyanarayanan) Date: Mon, 25 Mar 2019 10:49:43 -0400 Subject: Status of OpenSlide support In-Reply-To: References: Message-ID: <201903251049.43799.satya@cs.cmu.edu> Hi Adam and Martin, Is #5 (inability to do commit changes without the help of one of the original developers) really the showstopper at present? I don't have that impression, but if that's the case it is easily fixed by us granting permission to specific, carefully-vetted individuals. We don't have a community-developed process in place, but for a small number of individuals it shouldn't be a big deal. If you can convince Adam Goode, Benjamin Gilbert, and Jan Harkes that you can be trusted with this role (and they tell me so), I can work out the mechanism. There is no need to create a fork just to be able to commit changes to the OpenSlide code base. My understanding is that it is #1 and #2 (lack of time and expertise) that is the limiting factor to OpenSlide evolution at the moment. Adam's advice on #1 to #4 are right on target for addressing that. Cheers -- Satya On Monday 25 March 2019 10:23:15 Adam Goode wrote: > Hi Martin, > > Benjamin and I are are both quite busy with other things. I cannot speak > for Benjamin, but in my case I am not able to take money to work on side > projects like this. It is likely that Benjamin has a similar situation. > > Given this information, how should you move forward? The typical advice I > give to organizations interested in OpenSlide is this: > > 1. Please identify someone in your organization to work on OpenSlide. This > can be someone in your development group or research group, or possibly > even a grad student in some circumstances. > 2. Explicitly allocate some amount of time for this person to work on > OpenSlide (perhaps 15-20%, possibly more while getting started). > 3. Introduce this person to the list and me. > 4. I will provide some of my time to answer questions and give some help > getting started. > 5. Depending on the circumstances, we may be able to grant permissions to > this person to let them approve pull requests and do other things. This > would be a good outcome, though I would have to discuss with Benjamin and > the CMU folks exactly what criteria we would use for granting this. > > Note that, completely independently, you can fork the project and make > whatever changes you like. I encourage this! But please try to publish your > changes as we have done, and do so under the same license so that we could > eventually merge changes back someday. Forking may still be the correct > thing to do even if we do steps #1-4 above, since I can't currently say > what the criteria for #5 would be. > > > Thanks, > > Adam > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > m.weihrauch at smartinmedia.com> wrote: > > > Dear Benjamin: > > > > I wanted to inquire, what the status of OpenSlide is. The last commit is > > almost 1 year old and there are some important pull requests (problem with > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > I guess that you may have not the time to maintain it currently, which > > would be sad and a problem for so many of us, who rely on it. > > > > Maybe some of the community here (me included) could throw in some money > > and we could pay you or someone else e. g. a quarter or a half of his/her > > salary to further maintain and expand this important library, which you > > created. > > > > Looking forward to hearing from you. > > > > Martin > > _______________________________________________ > > openslide-users mailing list > > openslide-users at lists.andrew.cmu.edu > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > From m.weihrauch at smartinmedia.com Mon Mar 25 11:26:59 2019 From: m.weihrauch at smartinmedia.com (Martin Weihrauch) Date: Mon, 25 Mar 2019 15:26:59 +0000 Subject: AW: Status of OpenSlide support In-Reply-To: <201903251049.43799.satya@cs.cmu.edu> References: <201903251049.43799.satya@cs.cmu.edu> Message-ID: Thank you very much for your insights! I think that it should be possible on this list to collect some money, especially from the companies to make 1-5 work for all of us. So, first of all, we need to secure funds to go either: a) My company Smart In Media could hire a full time developer for OpenSlide to drive the library forward with the clear goal to keep it open source under LGPL. b) There is someone here on the list, who would be able to work x% of his time as a paid developer. My company could provide ?5,000 / year. Who else can add to the pot? Martin -----Urspr?ngliche Nachricht----- Von: Mahadev Satyanarayanan Gesendet: Montag, 25. M?rz 2019 15:50 An: Adam Goode ; Martin Weihrauch Cc: openslide-users at lists.andrew.cmu.edu Betreff: Re: Status of OpenSlide support Hi Adam and Martin, Is #5 (inability to do commit changes without the help of one of the original developers) really the showstopper at present? I don't have that impression, but if that's the case it is easily fixed by us granting permission to specific, carefully-vetted individuals. We don't have a community-developed process in place, but for a small number of individuals it shouldn't be a big deal. If you can convince Adam Goode, Benjamin Gilbert, and Jan Harkes that you can be trusted with this role (and they tell me so), I can work out the mechanism. There is no need to create a fork just to be able to commit changes to the OpenSlide code base. My understanding is that it is #1 and #2 (lack of time and expertise) that is the limiting factor to OpenSlide evolution at the moment. Adam's advice on #1 to #4 are right on target for addressing that. Cheers -- Satya On Monday 25 March 2019 10:23:15 Adam Goode wrote: > Hi Martin, > > Benjamin and I are are both quite busy with other things. I cannot > speak for Benjamin, but in my case I am not able to take money to work > on side projects like this. It is likely that Benjamin has a similar situation. > > Given this information, how should you move forward? The typical > advice I give to organizations interested in OpenSlide is this: > > 1. Please identify someone in your organization to work on OpenSlide. > This can be someone in your development group or research group, or > possibly even a grad student in some circumstances. > 2. Explicitly allocate some amount of time for this person to work on > OpenSlide (perhaps 15-20%, possibly more while getting started). > 3. Introduce this person to the list and me. > 4. I will provide some of my time to answer questions and give some > help getting started. > 5. Depending on the circumstances, we may be able to grant permissions > to this person to let them approve pull requests and do other things. > This would be a good outcome, though I would have to discuss with > Benjamin and the CMU folks exactly what criteria we would use for granting this. > > Note that, completely independently, you can fork the project and make > whatever changes you like. I encourage this! But please try to publish > your changes as we have done, and do so under the same license so that > we could eventually merge changes back someday. Forking may still be > the correct thing to do even if we do steps #1-4 above, since I can't > currently say what the criteria for #5 would be. > > > Thanks, > > Adam > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > m.weihrauch at smartinmedia.com> wrote: > > > Dear Benjamin: > > > > I wanted to inquire, what the status of OpenSlide is. The last > > commit is almost 1 year old and there are some important pull > > requests (problem with bif, Motic and introduction of VMIC) waiting to be introduced. > > > > I guess that you may have not the time to maintain it currently, > > which would be sad and a problem for so many of us, who rely on it. > > > > Maybe some of the community here (me included) could throw in some > > money and we could pay you or someone else e. g. a quarter or a half > > of his/her salary to further maintain and expand this important > > library, which you created. > > > > Looking forward to hearing from you. > > > > Martin > > _______________________________________________ > > openslide-users mailing list > > openslide-users at lists.andrew.cmu.edu > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > From adam at spicenitz.org Mon Mar 25 11:28:09 2019 From: adam at spicenitz.org (Adam Goode) Date: Mon, 25 Mar 2019 11:28:09 -0400 Subject: Status of OpenSlide support In-Reply-To: <201903251049.43799.satya@cs.cmu.edu> References: <201903251049.43799.satya@cs.cmu.edu> Message-ID: Hi Satya, I agree it's best to always have a plan to bring forked changes into the main openslide project. GitHub is a little unusual in the sense that nearly all proposed changes start out as a "fork": https://github.com/openslide/openslide/pulls is a list of forks whose authors have proposed them to be merged. https://github.com/openslide/openslide/network/members is a list of some forks (folks who are doing some sort of development). It takes a good amount of time to review code and help get code into a high quality, merge-ready state. I think it is to the benefit of anyone using OpenSlide to help contribute to this. Thanks, Adam On Mon, Mar 25, 2019 at 10:50 Mahadev Satyanarayanan wrote: > Hi Adam and Martin, > Is #5 (inability to do commit changes without the help of one of the > original > developers) really the showstopper at present? I don't have that > impression, but > if that's the case it is easily fixed by us granting permission to > specific, > carefully-vetted individuals. We don't have a community-developed > process in place, but for a small number of individuals it shouldn't be a > big deal. If you can convince Adam Goode, Benjamin Gilbert, and Jan Harkes > that you can be trusted with this role (and they tell me so), > I can work out the mechanism. There is no need to create a fork just to > be able to commit changes to the OpenSlide code base. > > My understanding is that it is #1 and #2 (lack of time and expertise) that > is > the limiting factor to OpenSlide evolution at the moment. Adam's advice > on #1 to #4 are right on target for addressing that. > > Cheers > -- Satya > > On Monday 25 March 2019 10:23:15 Adam Goode wrote: > > Hi Martin, > > > > Benjamin and I are are both quite busy with other things. I cannot speak > > for Benjamin, but in my case I am not able to take money to work on side > > projects like this. It is likely that Benjamin has a similar situation. > > > > Given this information, how should you move forward? The typical advice I > > give to organizations interested in OpenSlide is this: > > > > 1. Please identify someone in your organization to work on OpenSlide. > This > > can be someone in your development group or research group, or possibly > > even a grad student in some circumstances. > > 2. Explicitly allocate some amount of time for this person to work on > > OpenSlide (perhaps 15-20%, possibly more while getting started). > > 3. Introduce this person to the list and me. > > 4. I will provide some of my time to answer questions and give some help > > getting started. > > 5. Depending on the circumstances, we may be able to grant permissions to > > this person to let them approve pull requests and do other things. This > > would be a good outcome, though I would have to discuss with Benjamin and > > the CMU folks exactly what criteria we would use for granting this. > > > > Note that, completely independently, you can fork the project and make > > whatever changes you like. I encourage this! But please try to publish > your > > changes as we have done, and do so under the same license so that we > could > > eventually merge changes back someday. Forking may still be the correct > > thing to do even if we do steps #1-4 above, since I can't currently say > > what the criteria for #5 would be. > > > > > > Thanks, > > > > Adam > > > > > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > > m.weihrauch at smartinmedia.com> wrote: > > > > > Dear Benjamin: > > > > > > I wanted to inquire, what the status of OpenSlide is. The last commit > is > > > almost 1 year old and there are some important pull requests (problem > with > > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > > > I guess that you may have not the time to maintain it currently, which > > > would be sad and a problem for so many of us, who rely on it. > > > > > > Maybe some of the community here (me included) could throw in some > money > > > and we could pay you or someone else e. g. a quarter or a half of > his/her > > > salary to further maintain and expand this important library, which you > > > created. > > > > > > Looking forward to hearing from you. > > > > > > Martin > > > _______________________________________________ > > > openslide-users mailing list > > > openslide-users at lists.andrew.cmu.edu > > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satya at cs.cmu.edu Mon Mar 25 11:42:19 2019 From: satya at cs.cmu.edu (Mahadev Satyanarayanan) Date: Mon, 25 Mar 2019 11:42:19 -0400 Subject: Status of OpenSlide support In-Reply-To: References: <201903251049.43799.satya@cs.cmu.edu> Message-ID: <201903251142.19679.satya@cs.cmu.edu> Ah! Thank you for the clarification, Adam. I thought you meant a completely new fork with permanent independent life (e.g. OpenOffice and LibreOffice). -- Satya On Monday 25 March 2019 11:28:09 Adam Goode wrote: > Hi Satya, > > I agree it's best to always have a plan to bring forked changes into the > main openslide project. > GitHub is a little unusual in the sense that nearly all proposed changes > start out as a "fork": https://github.com/openslide/openslide/pulls is a > list of forks whose authors have proposed them to be merged. > https://github.com/openslide/openslide/network/members is a list of some > forks (folks who are doing some sort of development). > > It takes a good amount of time to review code and help get code into a high > quality, merge-ready state. I think it is to the benefit of anyone using > OpenSlide to help contribute to this. > > > Thanks, > > Adam > > > On Mon, Mar 25, 2019 at 10:50 Mahadev Satyanarayanan > wrote: > > > Hi Adam and Martin, > > Is #5 (inability to do commit changes without the help of one of the > > original > > developers) really the showstopper at present? I don't have that > > impression, but > > if that's the case it is easily fixed by us granting permission to > > specific, > > carefully-vetted individuals. We don't have a community-developed > > process in place, but for a small number of individuals it shouldn't be a > > big deal. If you can convince Adam Goode, Benjamin Gilbert, and Jan Harkes > > that you can be trusted with this role (and they tell me so), > > I can work out the mechanism. There is no need to create a fork just to > > be able to commit changes to the OpenSlide code base. > > > > My understanding is that it is #1 and #2 (lack of time and expertise) that > > is > > the limiting factor to OpenSlide evolution at the moment. Adam's advice > > on #1 to #4 are right on target for addressing that. > > > > Cheers > > -- Satya > > > > On Monday 25 March 2019 10:23:15 Adam Goode wrote: > > > Hi Martin, > > > > > > Benjamin and I are are both quite busy with other things. I cannot speak > > > for Benjamin, but in my case I am not able to take money to work on side > > > projects like this. It is likely that Benjamin has a similar situation. > > > > > > Given this information, how should you move forward? The typical advice I > > > give to organizations interested in OpenSlide is this: > > > > > > 1. Please identify someone in your organization to work on OpenSlide. > > This > > > can be someone in your development group or research group, or possibly > > > even a grad student in some circumstances. > > > 2. Explicitly allocate some amount of time for this person to work on > > > OpenSlide (perhaps 15-20%, possibly more while getting started). > > > 3. Introduce this person to the list and me. > > > 4. I will provide some of my time to answer questions and give some help > > > getting started. > > > 5. Depending on the circumstances, we may be able to grant permissions to > > > this person to let them approve pull requests and do other things. This > > > would be a good outcome, though I would have to discuss with Benjamin and > > > the CMU folks exactly what criteria we would use for granting this. > > > > > > Note that, completely independently, you can fork the project and make > > > whatever changes you like. I encourage this! But please try to publish > > your > > > changes as we have done, and do so under the same license so that we > > could > > > eventually merge changes back someday. Forking may still be the correct > > > thing to do even if we do steps #1-4 above, since I can't currently say > > > what the criteria for #5 would be. > > > > > > > > > Thanks, > > > > > > Adam > > > > > > > > > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > > > m.weihrauch at smartinmedia.com> wrote: > > > > > > > Dear Benjamin: > > > > > > > > I wanted to inquire, what the status of OpenSlide is. The last commit > > is > > > > almost 1 year old and there are some important pull requests (problem > > with > > > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > > > > > I guess that you may have not the time to maintain it currently, which > > > > would be sad and a problem for so many of us, who rely on it. > > > > > > > > Maybe some of the community here (me included) could throw in some > > money > > > > and we could pay you or someone else e. g. a quarter or a half of > > his/her > > > > salary to further maintain and expand this important library, which you > > > > created. > > > > > > > > Looking forward to hearing from you. > > > > > > > > Martin > > > > _______________________________________________ > > > > openslide-users mailing list > > > > openslide-users at lists.andrew.cmu.edu > > > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > > > > > > > > From m.weihrauch at smartinmedia.com Mon Mar 25 12:11:24 2019 From: m.weihrauch at smartinmedia.com (Martin Weihrauch) Date: Mon, 25 Mar 2019 16:11:24 +0000 Subject: AW: Status of OpenSlide support In-Reply-To: <201903251142.19679.satya@cs.cmu.edu> References: <201903251049.43799.satya@cs.cmu.edu> <201903251142.19679.satya@cs.cmu.edu> Message-ID: That's OK. However, many of us don't understand, why pull requests for a code change that contains exactly 2 lines of code wait since July 2018. Is there anything, which we can do to speed up that process specifically?: https://github.com/openslide/openslide/pull/246/files or https://github.com/openslide/openslide/pull/244/files Again, thanks for creating that valuable library!! Martin -----Urspr?ngliche Nachricht----- Von: Mahadev Satyanarayanan Gesendet: Montag, 25. M?rz 2019 16:42 An: Adam Goode Cc: Martin Weihrauch ; openslide-users at lists.andrew.cmu.edu Betreff: Re: Status of OpenSlide support Ah! Thank you for the clarification, Adam. I thought you meant a completely new fork with permanent independent life (e.g. OpenOffice and LibreOffice). -- Satya On Monday 25 March 2019 11:28:09 Adam Goode wrote: > Hi Satya, > > I agree it's best to always have a plan to bring forked changes into > the main openslide project. > GitHub is a little unusual in the sense that nearly all proposed > changes start out as a "fork": > https://github.com/openslide/openslide/pulls is a list of forks whose authors have proposed them to be merged. > https://github.com/openslide/openslide/network/members is a list of > some forks (folks who are doing some sort of development). > > It takes a good amount of time to review code and help get code into a > high quality, merge-ready state. I think it is to the benefit of > anyone using OpenSlide to help contribute to this. > > > Thanks, > > Adam > > > On Mon, Mar 25, 2019 at 10:50 Mahadev Satyanarayanan > > wrote: > > > Hi Adam and Martin, > > Is #5 (inability to do commit changes without the help of one of > > the original > > developers) really the showstopper at present? I don't have that > > impression, but > > if that's the case it is easily fixed by us granting permission to > > specific, > > carefully-vetted individuals. We don't have a community-developed > > process in place, but for a small number of individuals it shouldn't > > be a big deal. If you can convince Adam Goode, Benjamin Gilbert, > > and Jan Harkes that you can be trusted with this role (and they tell me so), > > I can work out the mechanism. There is no need to create a fork just to > > be able to commit changes to the OpenSlide code base. > > > > My understanding is that it is #1 and #2 (lack of time and > > expertise) that is the limiting factor to OpenSlide evolution at the > > moment. Adam's advice on #1 to #4 are right on target for > > addressing that. > > > > Cheers > > -- Satya > > > > On Monday 25 March 2019 10:23:15 Adam Goode wrote: > > > Hi Martin, > > > > > > Benjamin and I are are both quite busy with other things. I cannot > > > speak for Benjamin, but in my case I am not able to take money to > > > work on side projects like this. It is likely that Benjamin has a similar situation. > > > > > > Given this information, how should you move forward? The typical > > > advice I give to organizations interested in OpenSlide is this: > > > > > > 1. Please identify someone in your organization to work on OpenSlide. > > This > > > can be someone in your development group or research group, or > > > possibly even a grad student in some circumstances. > > > 2. Explicitly allocate some amount of time for this person to work > > > on OpenSlide (perhaps 15-20%, possibly more while getting started). > > > 3. Introduce this person to the list and me. > > > 4. I will provide some of my time to answer questions and give > > > some help getting started. > > > 5. Depending on the circumstances, we may be able to grant > > > permissions to this person to let them approve pull requests and > > > do other things. This would be a good outcome, though I would have > > > to discuss with Benjamin and the CMU folks exactly what criteria we would use for granting this. > > > > > > Note that, completely independently, you can fork the project and > > > make whatever changes you like. I encourage this! But please try > > > to publish > > your > > > changes as we have done, and do so under the same license so that > > > we > > could > > > eventually merge changes back someday. Forking may still be the > > > correct thing to do even if we do steps #1-4 above, since I can't > > > currently say what the criteria for #5 would be. > > > > > > > > > Thanks, > > > > > > Adam > > > > > > > > > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > > > m.weihrauch at smartinmedia.com> wrote: > > > > > > > Dear Benjamin: > > > > > > > > I wanted to inquire, what the status of OpenSlide is. The last > > > > commit > > is > > > > almost 1 year old and there are some important pull requests > > > > (problem > > with > > > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > > > > > I guess that you may have not the time to maintain it currently, > > > > which would be sad and a problem for so many of us, who rely on it. > > > > > > > > Maybe some of the community here (me included) could throw in > > > > some > > money > > > > and we could pay you or someone else e. g. a quarter or a half > > > > of > > his/her > > > > salary to further maintain and expand this important library, > > > > which you created. > > > > > > > > Looking forward to hearing from you. > > > > > > > > Martin > > > > _______________________________________________ > > > > openslide-users mailing list > > > > openslide-users at lists.andrew.cmu.edu > > > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > > > > > > > > From adam at spicenitz.org Mon Mar 25 15:28:11 2019 From: adam at spicenitz.org (Adam Goode) Date: Mon, 25 Mar 2019 15:28:11 -0400 Subject: Status of OpenSlide support In-Reply-To: <201903251142.19679.satya@cs.cmu.edu> References: <201903251049.43799.satya@cs.cmu.edu> <201903251142.19679.satya@cs.cmu.edu> Message-ID: Yup, nothing so extreme, sorry to alarm anybody! Take care, Adam On Mon, Mar 25, 2019 at 11:46 AM Mahadev Satyanarayanan wrote: > Ah! Thank you for the clarification, Adam. I thought you meant > a completely new fork with permanent independent life > (e.g. OpenOffice and LibreOffice). > -- Satya > > On Monday 25 March 2019 11:28:09 Adam Goode wrote: > > Hi Satya, > > > > I agree it's best to always have a plan to bring forked changes into the > > main openslide project. > > GitHub is a little unusual in the sense that nearly all proposed changes > > start out as a "fork": https://github.com/openslide/openslide/pulls is a > > list of forks whose authors have proposed them to be merged. > > https://github.com/openslide/openslide/network/members is a list of some > > forks (folks who are doing some sort of development). > > > > It takes a good amount of time to review code and help get code into a > high > > quality, merge-ready state. I think it is to the benefit of anyone using > > OpenSlide to help contribute to this. > > > > > > Thanks, > > > > Adam > > > > > > On Mon, Mar 25, 2019 at 10:50 Mahadev Satyanarayanan > > wrote: > > > > > Hi Adam and Martin, > > > Is #5 (inability to do commit changes without the help of one of the > > > original > > > developers) really the showstopper at present? I don't have that > > > impression, but > > > if that's the case it is easily fixed by us granting permission to > > > specific, > > > carefully-vetted individuals. We don't have a community-developed > > > process in place, but for a small number of individuals it shouldn't > be a > > > big deal. If you can convince Adam Goode, Benjamin Gilbert, and Jan > Harkes > > > that you can be trusted with this role (and they tell me so), > > > I can work out the mechanism. There is no need to create a fork just > to > > > be able to commit changes to the OpenSlide code base. > > > > > > My understanding is that it is #1 and #2 (lack of time and expertise) > that > > > is > > > the limiting factor to OpenSlide evolution at the moment. Adam's > advice > > > on #1 to #4 are right on target for addressing that. > > > > > > Cheers > > > -- Satya > > > > > > On Monday 25 March 2019 10:23:15 Adam Goode wrote: > > > > Hi Martin, > > > > > > > > Benjamin and I are are both quite busy with other things. I cannot > speak > > > > for Benjamin, but in my case I am not able to take money to work on > side > > > > projects like this. It is likely that Benjamin has a similar > situation. > > > > > > > > Given this information, how should you move forward? The typical > advice I > > > > give to organizations interested in OpenSlide is this: > > > > > > > > 1. Please identify someone in your organization to work on OpenSlide. > > > This > > > > can be someone in your development group or research group, or > possibly > > > > even a grad student in some circumstances. > > > > 2. Explicitly allocate some amount of time for this person to work on > > > > OpenSlide (perhaps 15-20%, possibly more while getting started). > > > > 3. Introduce this person to the list and me. > > > > 4. I will provide some of my time to answer questions and give some > help > > > > getting started. > > > > 5. Depending on the circumstances, we may be able to grant > permissions to > > > > this person to let them approve pull requests and do other things. > This > > > > would be a good outcome, though I would have to discuss with > Benjamin and > > > > the CMU folks exactly what criteria we would use for granting this. > > > > > > > > Note that, completely independently, you can fork the project and > make > > > > whatever changes you like. I encourage this! But please try to > publish > > > your > > > > changes as we have done, and do so under the same license so that we > > > could > > > > eventually merge changes back someday. Forking may still be the > correct > > > > thing to do even if we do steps #1-4 above, since I can't currently > say > > > > what the criteria for #5 would be. > > > > > > > > > > > > Thanks, > > > > > > > > Adam > > > > > > > > > > > > > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > > > > m.weihrauch at smartinmedia.com> wrote: > > > > > > > > > Dear Benjamin: > > > > > > > > > > I wanted to inquire, what the status of OpenSlide is. The last > commit > > > is > > > > > almost 1 year old and there are some important pull requests > (problem > > > with > > > > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > > > > > > > I guess that you may have not the time to maintain it currently, > which > > > > > would be sad and a problem for so many of us, who rely on it. > > > > > > > > > > Maybe some of the community here (me included) could throw in some > > > money > > > > > and we could pay you or someone else e. g. a quarter or a half of > > > his/her > > > > > salary to further maintain and expand this important library, > which you > > > > > created. > > > > > > > > > > Looking forward to hearing from you. > > > > > > > > > > Martin > > > > > _______________________________________________ > > > > > openslide-users mailing list > > > > > openslide-users at lists.andrew.cmu.edu > > > > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satya at cs.cmu.edu Mon Mar 25 16:25:59 2019 From: satya at cs.cmu.edu (Mahadev Satyanarayanan) Date: Mon, 25 Mar 2019 16:25:59 -0400 Subject: AW: Status of OpenSlide support In-Reply-To: References: <201903251142.19679.satya@cs.cmu.edu> Message-ID: <201903251625.59793.satya@cs.cmu.edu> Hi Martin, The reason is simple: no one has had the cycles to spare. This has not been a funded project for us for many years. Adam, Benjamin and Jan have contributed whatever time they could spare, when they could, on a best effort basis. This gets harder to do over time. Adam's advice on #1-#4 is exactly right. If a person of the right caliber who can make the time commitment is identified, we can work on the details of commit access to github. -- Satya On Monday 25 March 2019 12:11:24 Martin Weihrauch wrote: > That's OK. However, many of us don't understand, why pull requests for a code change that contains exactly 2 lines of code wait since July 2018. Is there anything, which we can do to speed up that process specifically?: > https://github.com/openslide/openslide/pull/246/files > > or > > https://github.com/openslide/openslide/pull/244/files > > Again, thanks for creating that valuable library!! > > Martin > > -----Urspr?ngliche Nachricht----- > Von: Mahadev Satyanarayanan > Gesendet: Montag, 25. M?rz 2019 16:42 > An: Adam Goode > Cc: Martin Weihrauch ; openslide-users at lists.andrew.cmu.edu > Betreff: Re: Status of OpenSlide support > > Ah! Thank you for the clarification, Adam. I thought you meant a completely new fork with permanent independent life (e.g. OpenOffice and LibreOffice). > -- Satya > > On Monday 25 March 2019 11:28:09 Adam Goode wrote: > > Hi Satya, > > > > I agree it's best to always have a plan to bring forked changes into > > the main openslide project. > > GitHub is a little unusual in the sense that nearly all proposed > > changes start out as a "fork": > > https://github.com/openslide/openslide/pulls is a list of forks whose authors have proposed them to be merged. > > https://github.com/openslide/openslide/network/members is a list of > > some forks (folks who are doing some sort of development). > > > > It takes a good amount of time to review code and help get code into a > > high quality, merge-ready state. I think it is to the benefit of > > anyone using OpenSlide to help contribute to this. > > > > > > Thanks, > > > > Adam > > > > > > On Mon, Mar 25, 2019 at 10:50 Mahadev Satyanarayanan > > > > wrote: > > > > > Hi Adam and Martin, > > > Is #5 (inability to do commit changes without the help of one of > > > the original > > > developers) really the showstopper at present? I don't have that > > > impression, but > > > if that's the case it is easily fixed by us granting permission to > > > specific, > > > carefully-vetted individuals. We don't have a community-developed > > > process in place, but for a small number of individuals it shouldn't > > > be a big deal. If you can convince Adam Goode, Benjamin Gilbert, > > > and Jan Harkes that you can be trusted with this role (and they tell me so), > > > I can work out the mechanism. There is no need to create a fork just to > > > be able to commit changes to the OpenSlide code base. > > > > > > My understanding is that it is #1 and #2 (lack of time and > > > expertise) that is the limiting factor to OpenSlide evolution at the > > > moment. Adam's advice on #1 to #4 are right on target for > > > addressing that. > > > > > > Cheers > > > -- Satya > > > > > > On Monday 25 March 2019 10:23:15 Adam Goode wrote: > > > > Hi Martin, > > > > > > > > Benjamin and I are are both quite busy with other things. I cannot > > > > speak for Benjamin, but in my case I am not able to take money to > > > > work on side projects like this. It is likely that Benjamin has a similar situation. > > > > > > > > Given this information, how should you move forward? The typical > > > > advice I give to organizations interested in OpenSlide is this: > > > > > > > > 1. Please identify someone in your organization to work on OpenSlide. > > > This > > > > can be someone in your development group or research group, or > > > > possibly even a grad student in some circumstances. > > > > 2. Explicitly allocate some amount of time for this person to work > > > > on OpenSlide (perhaps 15-20%, possibly more while getting started). > > > > 3. Introduce this person to the list and me. > > > > 4. I will provide some of my time to answer questions and give > > > > some help getting started. > > > > 5. Depending on the circumstances, we may be able to grant > > > > permissions to this person to let them approve pull requests and > > > > do other things. This would be a good outcome, though I would have > > > > to discuss with Benjamin and the CMU folks exactly what criteria we would use for granting this. > > > > > > > > Note that, completely independently, you can fork the project and > > > > make whatever changes you like. I encourage this! But please try > > > > to publish > > > your > > > > changes as we have done, and do so under the same license so that > > > > we > > > could > > > > eventually merge changes back someday. Forking may still be the > > > > correct thing to do even if we do steps #1-4 above, since I can't > > > > currently say what the criteria for #5 would be. > > > > > > > > > > > > Thanks, > > > > > > > > Adam > > > > > > > > > > > > > > > > On Mon, Mar 25, 2019 at 2:07 AM Martin Weihrauch < > > > > m.weihrauch at smartinmedia.com> wrote: > > > > > > > > > Dear Benjamin: > > > > > > > > > > I wanted to inquire, what the status of OpenSlide is. The last > > > > > commit > > > is > > > > > almost 1 year old and there are some important pull requests > > > > > (problem > > > with > > > > > bif, Motic and introduction of VMIC) waiting to be introduced. > > > > > > > > > > I guess that you may have not the time to maintain it currently, > > > > > which would be sad and a problem for so many of us, who rely on it. > > > > > > > > > > Maybe some of the community here (me included) could throw in > > > > > some > > > money > > > > > and we could pay you or someone else e. g. a quarter or a half > > > > > of > > > his/her > > > > > salary to further maintain and expand this important library, > > > > > which you created. > > > > > > > > > > Looking forward to hearing from you. > > > > > > > > > > Martin > > > > > _______________________________________________ > > > > > openslide-users mailing list > > > > > openslide-users at lists.andrew.cmu.edu > > > > > https://lists.andrew.cmu.edu/mailman/listinfo/openslide-users > > > > > > > > > > > > > > >