Repository history and size

[landsman]

Guys, I wanted to contribute on the doc, which I wasn't able to because of this issue anyway there is another topic that I want to mention.

Repository size, history

It's huge! I did a fresh git clone of the repository and there are some numbers:

1. The size of the raw repository is 831,3 MB right now
2. From this is 768,8 MB just .git folder
3. There are 53,265 commits in the main branch
4. There are 1700+ issues for several packages
5. There are 127 pull requests

Questions

Is this maintainable in the future? What about splitting it into more repositories for smaller packages and parts?

• easier to read and maintain issues
• smaller git repository size
• easier to contribute

Let's be honest - who is going to search among all these issues for something related to integration and answer it? Who will voluntarily clone such a huge repository and read such a huge git log every time?

I really like this project and the current state makes me think about these questions.

[shilman]

@landsman storybook is a big project and will always have a lot of issues because of its surface area/broad compatibility. I think we can get it down to 1000 but probably not much less.

Regarding repo size, perhaps we can archive the repo and start over from v7 or something to preserve some limited history. I think a lot of the large size is due to older versions where we included React Native, which has been factored out into its own repo years ago. @storybookjs/core WDYT?

[landsman]

making things as least as uncomplicated as possible should be the goal if there is interest in occasional contributors so that they are not afraid to get involved in my opinion

[ndelangen]

@landsman I bet rewriting history would be very disruptive to all existing branches & PRs, wouldn't it @landsman ?

[landsman]

@landsman I bet rewriting history would be very disruptive to all existing branches & PRs, wouldn't it @landsman ?

not necessarily, try doing it locally and check for conflicts / changed git commits sha

[JReinhold]

@ndelangen If we do the cutoff point at v6.5.X then surely a minimal amount of open branches/PRs would be affected? I'd argue that they should probably be redone anyway.

[ndelangen]

@JReinhold I would not be directly opposed, is there an easy way for us to find out, how to do this, without actually doing it on the main repo?