Github folder/file structure about panosc HOT 2 CLOSED

Thanks Jordi for the proposal. Here are some comments from my side:

• are the numbers going to be part of the directory names?
• what is meant by Plans. Maybe replace this with Planning
• do we need an Issues directory? The issues could be managed on github.
• I am not sure we need the pre-project directory. I would move the agreements to a single directory Agreement in Project.
• rename Submitted Deliverables to Deliverables
• not sure we need Post Project. Can be added later if necessary.

We are an Open Source project in github i.e. all documents are open to the public. This includes the grant and consortium agreements. That is not a problem for me but we should be aware of this and all participants should agree to this openness.

Andy

from panosc.

Hi Andy,

1. The numbers are to show the order, but are not needed.
2. By Plans I mean any document related to planning that we do. An example would be a Gantt chart with all the deliverables, but could be anything else related to Planning (e.g. we do not have a detailed plan for any of the work packages or if we need to build a plan to deal with an exceptional circumstance)
3. True. we can use that feature of GitHub
4. Pre-project is just for clarity, to show that the contents relate to pre-project work and to clearly separate them from the project deliverables
5. The "Submitted" part of the name is to highlight that this is just a snapshot of what we are providing, not for work in progress (that would be in the respective work package folder). However I do not mind about the name.
6. True, post-project is not require anytime soon.

from panosc.