Timeline for How do I motivate usage of Git for the next maintainer?
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 13, 2019 at 19:14 | history | edited | CShark | CC BY-SA 4.0 |
added 233 characters in body
|
| Sep 16, 2018 at 17:53 | history | edited | Monica Cellio | CC BY-SA 4.0 |
added info from comment -- that git is already in use is an important detail
|
| S Sep 16, 2018 at 14:05 | history | suggested | Peter Mortensen | CC BY-SA 4.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/Git_%28software%29> and <https://en.wiktionary.org/wiki/fail-safe#Noun>). Removed meta information (this belongs in comments).
|
| Sep 16, 2018 at 10:17 | review | Suggested edits | |||
| S Sep 16, 2018 at 14:05 | |||||
| Sep 16, 2018 at 0:01 | history | tweeted | twitter.com/StackWorkplace/status/1041114725579415560 | ||
| Sep 11, 2018 at 8:37 | comment | added | CShark | @jamesqf Because it is what I chose to use the last three years. My successor is of course free to change everything, but until then it is easier to just continue using it. | |
| S Sep 11, 2018 at 7:16 | history | suggested | ivan_pozdeev | CC BY-SA 4.0 |
fix the title to reflect the essence; as written, it rather sounded like promoting git to a dev team
|
| Sep 11, 2018 at 5:21 | comment | added | jamesqf | Why git in particular, rather than one of the dozens of other version control systems? | |
| Sep 11, 2018 at 0:57 | review | Suggested edits | |||
| S Sep 11, 2018 at 7:16 | |||||
| S Sep 10, 2018 at 22:05 | answer | added | Philip Oakley | timeline score: 3 | |
| S Sep 10, 2018 at 22:05 | history | protected | CommunityBot | ||
| Sep 10, 2018 at 19:59 | history | edited | David K |
edited tags
|
|
| S Sep 10, 2018 at 19:57 | history | suggested | Rich | CC BY-SA 4.0 |
Corrected grammar
|
| Sep 10, 2018 at 17:46 | review | Suggested edits | |||
| S Sep 10, 2018 at 19:57 | |||||
| Sep 10, 2018 at 17:32 | answer | added | Jamie Clinton | timeline score: -2 | |
| Sep 10, 2018 at 14:14 | answer | added | chris | timeline score: -4 | |
| Sep 10, 2018 at 13:21 | comment | added | David K | Related, possible duplicate: Convince the Company I Work for to Implement Version Control? | |
| Sep 10, 2018 at 10:59 | vote | accept | CShark | ||
| Sep 10, 2018 at 9:25 | answer | added | Elmy | timeline score: 145 | |
| Sep 10, 2018 at 9:15 | review | Close votes | |||
| Sep 11, 2018 at 10:29 | |||||
| Sep 10, 2018 at 8:40 | comment | added | CShark | @Walfrat well there is a high possibility that I will work on the project again for support or little/large requests on a short-term contract, so I do have a genuine interest that they use git. | |
| Sep 10, 2018 at 8:38 | comment | added | CShark | Currently the chapter on git isn't written yet, so I'm currently looking for what to write there to give a practical motivation. Making git part of the standard workflow was also my idea but as it does not contribute to a successful installer it might get skipped - thats what I want to motivate against. But maybe I'm overthinking this, that is also a possibility. | |
| Sep 10, 2018 at 8:36 | comment | added | user34587 | Apart from forcing them to do so, what makes you concerned that the steps you have mentioned won't be enough? Also, if you're the sole developer writing up this process, why can't you make it part of the standard process? | |
| Sep 10, 2018 at 8:25 | review | First posts | |||
| Sep 10, 2018 at 8:53 | |||||
| Sep 10, 2018 at 8:23 | history | asked | CShark | CC BY-SA 4.0 |