feedback

[vjd]

what are your thoughts on the binning's in the roadmap @osmosisfoundation/leadership

We welcome feedback from community members!

• what should be the level of granularity included in the roadmap?

• what are realistic timelines for each roadmap product?

• Are issues the best way to get feedback from the community?

[MarcGastonguay]

Nice start to the roadmap.

Should we also include an initial objective, which would focus on creating a catalog of the ongoing open-source projects in our discipline... particularly those led by potential osmosis contributors? This could be done by category, such as NCA, ODE-based simulators, estimation engines, post-processing tools, etc.

A secondary objective could be to define logical collaboration oportunities within and between categories and to limit redundancy in the community's efforts.

[vjd]

@MarcGastonguay good suggestion. I can make a list in the roadmap today

[kylebaron]

• I wonder about a code incubator: people have developed code for their own work and think it might be useful out in the open, but the code needs some polish and they don't know how to build a package or otherwise get it into the community. Could we provide the space and expertise to help that along?

[dpastoor]

I don't know what bucket to put this in, but one additional thing osmosis should provide is a separate hosting platform package sources for at least incubating projects per @kylebmetrum 's request, but I would think the entire ecosystem. This is a big pain point for packages in development on github, as many corporate firewalls block github from being curled to install packages via install_github.

This would be handled by https://github.com/eddelbuettel/drat and could also provide a central place to navigate all ongoing projects.

This is done by most "modern" groups, for example ropensci - https://ropensci.org/blog/blog/2015/08/04/a-drat-repository-for-ropensci

Note, this is not supposed to replace cran, rather is supplementary.

[corrigb]

Thanks @vjd for making me part of the Osmosis Foundation Initiative. I see this as the future of our discipline!

In the roadmap parlance, I would see our path as follows

1. Outline the types of open-source tools needed by the discipline (let's think of this as the size/area of the map we need......). What is our Scope? @MarcGastonguay provides some of those categories above.

2. Prepare a quick inventory of the open-source projects ongoing as mentioned above (let's call them the known waypoints on our map).

3. Review the list and Identify where there are a) projects already underway that we should help support (ie the waypoints with sufficient or near sufficient resolution for use) b) where there are gaps that we need to fill in ( the "Thar be Dragons" regions of our map), and c) the quick wins we can finds on the map (ie areas we can quickly explore..these may be some of the current projects listed).

4. With a small influential group in the field (this may be your Scientific Committee), develop and get buy into the high level Map for Osmosis. While this may feel a bit less "organic", it will help us by a) socializing the ideas we have b) validating our plan with key external groups, and c) down the road (when we reach out to those folks for support) to have built the bridges to have those conversations. With that said, we should think carefully about who you may need there to fulfill that task. these may be the same "Kings or Queens of Spain" we may want to help fund our expeditions!

5. Once we have the plan, I think the level of granularity and the timelines we can provide will be more clear. In some areas where we agree the waypoints already exist or are already being built, we may be able to provide very granular details and timelines. In other areas, less so.

5) The specific projects listed in the road map fall into some of the new waypoints. We may want to think about how we can get move them from individual contributor projects into ones with a broader community involvement. That broader community can then provide support for maintenance, upgrades, and training, and so it is key we figure this out early on. I think many attempts in the past have been less successful than wished because the planning for "what's next?" was not optimal.

Enough rambling.....I am excited to work on this with all of you and happy to help with laying some of this out if you want.