Page History
...
- Next steps (as decided in our meeting)
- We will be moving forward with Proposal #1, attempting to thoroughly review/test/improve upon it, to ensure that it will meet our initial DSpace 7 Use Cases.
- If at any time we hit a wall, or something that is not deemed acceptable, we still have time to "pivot" to a different solution (e.g. Proposal #2). However, at this point, all discussion will move towards improving/understanding Proposal #1.
- The codebase behind Proposal #1 will be made publicly available/accessible. It will be moved to a (collaborative) branch under the DSpace/DSpace github repository.
- Once it has been thoroughly reviewed and is found to meet our minimal use cases, a Pull Request from that branch will be created, so that it can be migrated into `master`
- Tim will notify all once this move has happened.
- The following additional organizations / individuals have promised to help chip in on improving Proposal #1 on this collaborative branch. Others are also welcome to chip in.
- EVERYONE: Help to fill out our use cases / user stories in: https://docs.google.com/document/d/1CJ8AkBtrY49rqn-WhYlP3kkZRVhCXGVgAIZHutJ-fas/edit
- Any questions/concerns about the implementation should ideally be expressed as a part of one of these user stories, as it will clarify the real need/use case behind the question.
- We will be moving forward with Proposal #1, attempting to thoroughly review/test/improve upon it, to ensure that it will meet our initial DSpace 7 Use Cases.
...
Overview
Content Tools