# Ibis-dev Meetings - October, 23rd Time: 3 PM EST ## Attendees Name (@github_user) * Ivan Ogasawara (@xmnlab) * Scott Hajek (@scottcode) * Jeff Reback (@jreback) * Li Jin (@icexelloss) * Hyonjee Joo (@hjoo) ## Agenda * **Next meetings:** biweekly, monthly, quarterly, ...? * quarterly for now * communication * gitter room: https://gitter.im/ibis-dev/Lobby * **Governance documents repo** * Would be good to have a repo for storing governance documents? * Who has permissions to do that? * Examples: * https://github.com/jupyter/governance * https://github.com/pyOpenSci/governance * Better communication between core developers and users related to the backends. * Maybe we could create github/teams for each backend * **NumFOCUS project affiliation** https://github.com/ibis-project/ibis/issues/1881 * Maybe would be good to add Ibis as a NumFOCUS affiliated project. It could increase the visibility of the project. * who can decide about that? could we vote that? * **Over-arching vision** * What purposes should ibis serve? Which should be considered out of scope? * How does ibis differentiate itself from other packages? * What guiding design principles do/should we have? * **Backend support:** * Ibis continues to grow in number of backends (yay!) * What is a sustainable strategy for maintaining support? What happens if community effort for a given backend wanes? * Should we keep backends as part of core ibis, or should it be a framework with a clear specification for building separate backend plugins? * Any other big-picture questions come to mind? * **Issues to discuss:** * Default Decimal Precision and Scale for Ibis Expressions (https://github.com/ibis-project/ibis/issues/1994) * Is there a reason for using the same default values? * cume_dist vs percent_rank https://github.com/ibis-project/ibis/issues/1975 * what could be the best approach for this problem? * CI instability * Builds fail fairly consistently, need more documentation on what service level to expect out of Azure https://github.com/ibis-project/ibis/issues/1980 * Impala could be removed from CI, and a warning message could be raised to tell people Impala is deprecated. Until we find someone to maitain impala backend. ## Next steps * Meeting quarterly calendar (@xmnlab) * Create a governance repo (@jeff)