Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Suggest to add "Documentation" as one more project, after "Maintenance and quality". Goal would be to write a PIG outlining documentation structure we should have at the time of v1.0 release, and then to work towards that documentation, one notebook and page at a time.
As mentioned here, I would suggest to put support for event classes on the roadmap, i.e. to mention it at least in the data project paragraph. And in modeling I would suggest to mention Bayesian priors and maybe also linked parameters if that is how you envision modeling to work.
The Gammapy paper in 2018 clearly didn't work out, so correct that sentence that it is for 2019. Also, we got the feedback that the most important thing to have is a plan / description of the design of Gammapy. So if we want to have that description in the paper, and to have a good design, we would have to defer the paper to later in 2019. Suggest to keep it short and vague for papers, OK to mention the Gammapy and HESS validation if you like as goals for 2019, but only very briefly.
The most important question is how to make this roadmap useful and to have an impact. I think it's important to have a shared vision what to build and to have it visible, so +1 to merge it. But maybe to actually lead to progress from existing and new contributors, some link concerning status and missing manpower for the different projects is needed? Updating the PIG all the time is not ideal. So either use https://github.com/gammapy/gammapy/projects or make a wiki page, and link to it from the PIG with some sentence encouraging people to contribute or lead projects listed on the roadmap has to exist. Maybe also a sentence how to get started concretely, IMO an email to the lead devs or mailing list is best. - so far we have not succeeded to describe the work to be done such that people just pick up tasks and start contributing, hopefully this roadmap will help focus the work of the exiting team, and help with onboarding in 2019.