[x] +1 yes, start using gitbox in general, start the migration to a writeable git repo with one svn repo (turbine archetypes or another one), connect to github and check using more github features, use this feature optionally for more git repos, if needed. [ ] 0 don't care [ ] -1 no, because
-Georg Von: "Georg Kallidis" <[email protected]> An: "Turbine Developers List" <[email protected]> Kopie: [email protected] Datum: 14.05.2018 11:47 Betreff: [VOTE][GIT] Use (writable) gitbox, start with for Turbine Archetypes Hi all, As I am in the process to get a GIT clone for Turbine webapp repo, cft. INFRA-16437 and reading the last comment https://issues.apache.org/jira/browse/INFRA-16437?focusedCommentId=16472623&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16472623 we might consider to migrate Turbine Webapp as a _writeable_ GIT repo to apache gitbox! (gitbox.apache.org = "GitHub Dual Master", not Git Wip, although only the latter is mentioned in https://www.apache.org/dev/writable-git). I think gitbox is just more git-centric, the release is done completely with git. Dind one example discussion here: https://mail-archives.apache.org/mod_mbox/infra-issues/201804.mbox/%3cjira.13152162.1523589032000.359092.1524717900...@atlassian.jira%3E This is just implemented as a self service, i.e. we could do this ourself (at one point of time), but we are completely free to do it as we like it (IMO), even as a SVN backed GIT, cft. https://wiki.apache.org/general/GitAtApache, which might not be the recommended way IMO. I would suggest to start with cloning/importing (not the main project) just the svn repo https://svn.apache.org/repos/asf/turbine/maven/archetypes to the gitbox as turbine-archetypes-git. The GitHub - Connection could then be done at any time later as far as I can see. We may decide to do it before the next release to perform a git release (@Jeffery)? Before more time is wasted, I would like to do this as a vote (procedural type, i.e. majority vote would apply). [ ] +1 yes, start using gitbox in general, start the migration to a writeable git repo with one svn repo (turbine archetypes or another one), connect to github and check using more github features, use this feature optionally for more git repos, if needed. [ ] 0 don't care [ ] -1 no, because. If there are any further compatible/consistent suggestions and they match the general direction, I would just continue the process. Thanks and... Best regards, Georg
smime.p7s
Description: S/MIME Cryptographic Signature
