In the spirit of https://github.com/datalad/datalad/issues/4490 we should maintain a central place with information that offers people the possibility to grasp what datalad is about -- which include the various side projects, efforts, and use cases that are floating around.
ATM we have lots of information, but it is scattered, and it needs one of us to manually explain what is around.
It makes sense to put that information on datalad.org
In the spirit of https://github.com/datalad/datalad/issues/4490 we should maintain a central place with information that offers people the possibility to grasp what datalad is about -- which include the various side projects, efforts, and use cases that are floating around.
ATM we have lots of information, but it is scattered, and it needs one of us to manually explain what is around.
It makes sense to put that information on datalad.org