EricssonResearch / EricssonResearch/bowser
Why the software history was not kept?
- Dominant language
- HTML
- Stars
- 208
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I'm a researcher studying software evolution. As part of my current research, I'm studying the implications of open-sourcing a proprietary software, for instance, if the project succeed in attracting newcomers. **bowser** was in my list. However, I observed that the software history of when the software was developed as a proprietary software was not kept after the transition to Github.
Knowing that software history is indispensable for developers (e.g., developers need to refer to history several times a day), I would like to ask **bowser** developers the following four brief questions:
1. Why did you decide to not keep the software history?
2. Do the _core developers_ faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
3. Do the _newcomers_ faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
4. How does the lack of history impacted on software evolution? Does it placed any burden in understanding and evolving the software?
Thanks in advance for your collaboration,
Gustavo Pinto, PhD
http://www.gustavopinto.org
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. This is a historical research questionnaire rather than an implementation task; it specifies no code change or testable completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100