2013/1/11 Sergio Fernández <sergio.fernan...@salzburgresearch.at> > Ok, taking into account all comment, I'd update my proposal regarding > repository structure would look like: > > . > |-- pom.xml > |-- COPYING.txt > |-- DISCLAIMER.txt > |-- LICENSE.txt > |-- NOTICE.txt > |-- README.txt > |-- ... > `-- platform > `-- clients > `-- libs > `-- tools > `-- extras > `-- import > > Where 'import' could be remove whenever importation process would be > finish. >
+1 > > Regarding the issue with SKOSjs, I don't have a clear opinion. But we > should take into account that, if we leave it out at its independent > repository, the artifact should be available via Maven central before the > first Marmotta release. > > Yes, either this or it should be part of Marmotta. > BTW, as we already discussed internally, I'd suggest to use a branching > workflow where we have a stable "master" branch and a unstable "develop" > branch. Besides, optionally "topic" branches for each topic/issue, which > don't need to be pushed to the public repository. Further details about > this workflow at the Pro Git book: > > > http://git-scm.com/book/en/**Git-Branching-Branching-**Workflows<http://git-scm.com/book/en/Git-Branching-Branching-Workflows> > > +1 We will set this up next week after the proposal deadline on Tuesday. Greetings, Sebastian
