-
Notifications
You must be signed in to change notification settings - Fork 52
2016 10 14 Meeting minutes
Attendees:
- Sebastian Benthall
- Davide Berra
- Nick Doty
We are considering new project Bylaws to transition towards a community governance model. The draft of these bylaws is here:
https://github.com/datactive/bigbang/wiki/Governance
It's based on several precedents. Karl Fogel's Producing Open Source Software, the governance documents of the NumPy and Jupyter projects, and also the GeoNode project. (This is detailed in the document itself.)
We opened the meeting to a discussion of the document and the suggestion of amendments.
Voting process is heavy, but only used in a major change (BBIP)
- Code review responsibility for Core Developers. -- come up with a code review guidelines document -- e.g. https://www.python.org/dev/peps/pep-0008/
Number of commits is a proxy for the kind of active participation we want, but certainly isn't perfect. It might be interesting if BigBang could one day provide us a better alternative for measuring community involvement. -- commits don't have to be code, because: -- include documentation in the repository -- contributions to public website : https://github.com/datactive/bigbang/tree/gh-pages , https://pages.github.com/
We will be using GitHub pages for the website.
https://github.com/datactive/bigbang/issues/264 http://datactive.github.io/bigbang/
Davide takes on website updates for BigBang 2.0
What chatroom to use?
- IRC, Slack, Gitter, Hipchat
Let's investigate. - Seb will look into it and send something to the dev list.
We're sticking with Tulip Revolution by Consensus of attendees.
https://gist.github.com/Chaser324/ce0505fbed06b947d962
-
Public image. Changes to the website, organizationals affiliations, new emphasis on Internet Governance.
- Lots of good development in the DMI workshop.
- remove the Summer School branding.
-
Gardening the examples notebooks. What to keep, what to remove, what to move to the core.
-
Documentation and installation. Switching to Anaconda environments?
- will it be able to install all the packages?
-
operating system compatibility.
There are a number of old tickets assigned to a "0.2. Rocksteady" milestone originally set for 2014. We will reassign these to the new, active 0.2 Tulip Revolution milestone. But we will also try not to block on these issues, because we really need to Release Early and Often