Hi Chris, I've taken a look at your post, very interesting! One thing is odd to me, you have all these modules that describe their functionality/values, and then you have "Jena database instance". It

(Complete aside, and not important, but: as a private person, you never need to use someone else copyright/trademark/whatever symbols. You aren't selling anything, there is no question over IP. People

Hello, the Bonsai enhancement proposal 0002 is now up for discussion:

Agreed, I wrote it for stressing the point not for IP concerns :) I'm not questioning here the technical choice re the software. My point is that you are "masking" the functionality you need with

I really like the idea of a beginner's toolbox, with a presentation of tools that are expected to be used to produce relevant outputs for BONSAI. I find myself sometimes dubitative as to where and how

The draft getting-started guide is here. It currently describes how I perceive the state-of-affairs to be now (regarding task management, prioritisation etc.). As such, it is not really yet

Dear all- I created the beginning of a BEP based on Tom's audit here: https://github.com/BONSAMURAIS/enhancements/blob/bep4-communications/beps/0004-bonsai-communication-strategy.md. My idea was to

Dear all- The legal entity BONSAI, a not for profit organization headquartered in Denmark, supports the efforts of the broader BONSAI project with fund-raising, substantial in-kind contributions, and

Great initiative! I think that a default time for discussion should be set and mentioned in the template. A default time could be 3 weeks from the publication of the BEP. The template might also

For clarity, this is a discussion on the BEP-0001 BONSAI (BEP) Enhancement Proposal Template. The following is a follow up of the discussion started (wrongly) here, where I proposed to include in the

Dear all- I have added some of these changes in https://github.com/BONSAMURAIS/enhancements/pull/6. However, I think we need to have a broader discussion on who and how to suggest changes. The

Hello, with Tom, we would like to suggest the use of Issues, Labels and the more general Project board features of GitHub to better visualize the long-term tasks described in the Wiki and benefit from

This looks great. Perhaps we could modify the boards to be more reflective of BONSAI stages? For example, I think we need something like "Concept-building" for the tasks text mining and data

Depending on the output of the communication plan, it might make sense to have this project board not be attached the "bonsai" repository, but for the entire BONSAMURAIS organization, i.e. here:

The BONSAI 2019 General Assembly will be held on Wednesday, May 8, from 17:00 to 18:00 Central European Time. Participation in the General Assembly requires membership in the BONSAI non profit

I second Chris’s suggestion to have the “High-level tasks, long run” project board as a project of the entire BONSAMURAIS organization (not in the “bonsai” repository). In general, good

OK then, we'll try to move that to the first level. /romain

The issue though with moving the Project board to the first level (BONSAMURAIS), is that BONSAMURAIS is not really a repo in itself (it's more a like front page) and hence, and one cannot create

>So the question is to know what the repository "bonsai" should really be about... I have filed an issue in that repo that is precisely about this problem, I.e making a more clear read me about that

Correct. My opinion is that the project board should be under the "Main" Bonsai directory because: it is becoming increasingly hard to figure what has been posted where; it will become even more so