convore.json/groups/pyne/the-beginning-cohesive-and-small-or-disorganized-and-large/messages.json

[{"user_id": 30471, "stars": [], "topic_id": 20691, "date_created": 1303391188.7598219, "message": "So I know the initial thought was to take all of our research codes and plop them in a giant package namespace, and over time work toward some synthesis between the components. Is this how the other major scientific packages have started? We could have an \"experimental\" branch that contains everything, but have only a small subset of well-tested, well-integrated, stable code comprise the main namespace. That way we won't overwhelm new users by the initial size, and we won't frustrate old users when we end up changing the names, organization, file formats, etc. of our older code.", "group_id": 9127, "id": 769823}, {"user_id": 10411, "stars": [], "topic_id": 20691, "date_created": 1303400299.221101, "message": "And along with this comes the idea that you can do any development that you want in staging, but someone else has to look at and approve your code for it to make it into master.  (Even if it is just a cursory glance to ensure coding standards, docstrings, tests, etc,)", "group_id": 9127, "id": 771431}, {"user_id": 10411, "stars": [], "topic_id": 20691, "date_created": 1303399855.4804649, "message": "@sethrj That is a good idea actually.  I prefer the term 'staging' since 'experimental' is an overloaded word in science/engineering.  Still, users should expect rapid API chnages in anything less than a v1.0 release.", "group_id": 9127, "id": 771324}, {"user_id": 30469, "stars": [], "topic_id": 20691, "date_created": 1303480087.2932639, "message": "I think this a great idea. Given that we all have code scattered around that will not be very coherent once put together initially, this will give us time to slowly integrate things.", "group_id": 9127, "id": 781521}, {"user_id": 10421, "stars": [], "topic_id": 20691, "date_created": 1304342230.3053861, "message": "yes.", "group_id": 9127, "id": 882853}]