I think point #2 is the bigger issue. We are pressed for time as far as reviews
go, and I’m happy to try and get sparrow reviewed, but cannot promise time for
sparrow.shiny.
You are welcome to submit though, but there is no guarantee that I will be
assigned to the package for review.
Nitesh
>
> You are having it ;) I’m the one assigned to your package.
>
Oh, sweet!
My last commit looks like it has resulted in a successful build across the
board, so I guess the hard part begins now: sorry in advance for any
headaches this particular review may cause ;-)
It would be great if I could
Hi Steve,
You are having it ;) I’m the one assigned to your package.
Best,
Nitesh
Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer Institute
> On Oct 4, 2021, at 5:42 PM, Steve Lianoglou wrote:
>
> Hi Nitesh,
>
> Thanks for working o
Hi Nitesh,
Thanks for working on this ... I've been able to push some changes I've
made up to the upstream/master, so I think we should be ok for now.
Waiting till the next cycle is fine if you think that is the best approach.
>
In all honesty, I'd prefer to attach the associated "shiny add-on p
Hi Steve,
This is resolved now. You should see access to your package.
Waiting till the next cycle is fine if you think that is the best approach.
Best,
Nitesh
Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer Institute
> On Oct 1, 2021,
Hello folks,
I think I may have a similar problem accessing the git repos as was
reported by Henrik back in August:
https://marc.info/?l=bioc-devel&m=162937494630582&w=2
My recently submitted package (sparrow) was just accepted for review:
https://github.com/Bioconductor/Contributions/issues/2342
