Hello @sambitdash, and everyone else. Thank you @ScottPJones for flagging this up to me on the Gitter.
As an administrator and co-founder of BioJulia I have some responses and comments.
First of all @sambitdash, I want to thank you very much for the PR on IntervalTrees.jl updating the 0.7 changes.
The 0.7 transition is putting a large amount of pressure to get rid of breakages and warnings, but the fluidity of master is making this difficult. Several times 0.7 compatiblity PRs have been made to some of our other packages, only for them to have more issues a few days later.
I also acknowlege your comments on other issues in the same repo, in particularily regarding multi-dimensionality and Rectangles. From reading them this morning I can also see how the issue on AbstractIntervalTree might be relevant insofar as generalising the IntervalTrees. But by and large we’re biologists, so multidimensional intervals and some of the things you mention like CAD in the issue are a bit outside of our experience, but if someone steps up to be a dedicated maintaner of the package any such feautres could definately be worked on.
I’m sorry that the 11 or so hour delay caused you to question BioJulia’s activity or Maintainership.
We are a small community, with actually quite a large number of repositories to keep track of.
And some of our formerly active and founding members have left or have had to drastically reduce their activities due to personal and life circumstances I am not going to discuss.
This is in part why we decentralised the code base of BioJulia from the monolithic repo it was, to an ecosystem of packages each with dedicated mainainers, (who are specified in its readme and documentation).
Some BioJulia members are maintainers of multiple packages, some maintain one package, some maintain none. This is because different members have different scientific specialisations and knowledge, and so they maintain the packages they know and can maintain best.
And some packages, like IntervalTrees.jl, have no maintainers, this is largely a historical accident: if a package is not as recently created as others, and is largely stable and is not updated for a long time, then it’s simply that nobody has needed to take up the maintainer mantle for it yet. If you would like to do so, we absolutely welcome you on board in this role!
I’m currently investing some time and effort into making package maintainership much easier for everyone in BioJulia, I’m re-writing a much clearer and neater Contributing Guide this week. In addition to implementing a set of pull request and issue templates to help issues and PRs be resolved in a much more consistent way across all of BioJulia’s repos. I’m also experimenting in some tools to assist in the mundane tasks of BioJulia management, such as bots to ensure content (such as the contributing guide and templates I mentioned) is included and is consistent across all repositories. I’m also looking into some other fun things for our maintainers too, but more on that in the future.
So to summarise I apologise for the inconsistent management of some packages in the ecossytem, believe me I know it’s a problem. There are some solutions I’m working on, but I can only do that when I’m not doing my 9-to-5 job, doing pan-genome assembly research.
In the future, if you require quicker response, I suggest using the BioJulia gitter room here: https://gitter.im/BioJulia/Bio.jl#utm_source=notification&utm_medium=email&utm_campaign=unread-notifications, just because sometimes we miss things on this discourse, because it’s a very big and julia-general forum.
Best wishes to all and thank you all for your continued interest in what BioJulia is doing.