Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create HISTORY.md #1786

Merged
merged 5 commits into from
Jul 21, 2024
Merged

Create HISTORY.md #1786

merged 5 commits into from
Jul 21, 2024

Conversation

emtiu
Copy link
Member

@emtiu emtiu commented Jul 7, 2024

Here's the result of some archaeology! :)

@buhtz
Copy link
Member

buhtz commented Jul 8, 2024

Nice!

EDIT: I tried to contact Oprea Dan, Bart de Koning and Richard Bailey for a review.

@buhtz
Copy link
Member

buhtz commented Jul 9, 2024

Richard Bailey replied to me, reviewed the history and had nothing to add or correct. He explained that he was not much involved and only round about 12 months within the project.

I am not able to contact Dan Oprea, the founder. It is also a common name so he is hard to track down. He seems to be offline for years.

HISTORY.md Outdated Show resolved Hide resolved
Co-authored-by: buhtz <[email protected]>
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
@buhtz
Copy link
Member

buhtz commented Jul 12, 2024

Just added some ideas and minor improvements.

What comes to my mind is if it isn't to technical in some paragraphs? I am not sure. Are you aware of the document about our Strategy Outline? I see some redundancy.

But what is missing in the Strategy Outline is the description about the permission-error-problem. It might can move into it from the HISTORY document?

EDIT: What I meant was. I think we have a lot of technical documents. It is not wrong to write about techncial details in HISTORY but it might not be so detailed or so deep. What I had in mind about a HISTORY document was a bit more "drama" and "emotions". 😄 It is about giving the project a face or faces. There are and where humans behind it. Knowing it or feeling it is different. And describing the long way of BIT would IMHO help with the emotional part. 😄

@emtiu
Copy link
Member Author

emtiu commented Jul 12, 2024

Feel free to copy the information on #988 and #994 into the Strategy Outline :) I think they also belong here, because these bugs shaped the history of the project.

I can see how the Third Era is maybe redundant with that document, and a bit too detailed. You're welcome to shorten it.

If you want "drama" and "emotion", then you also have to allow the "Dark Age" ;)

@buhtz
Copy link
Member

buhtz commented Jul 12, 2024

OK, you got me. 🤣 Drama, baby! 😭 🎉
Agree.

@emtiu
Copy link
Member Author

emtiu commented Jul 15, 2024

Having read this again after a few days, I think it's ready to commit. Feel free to merge, or enter the official "after creative pause" phase :)

@buhtz buhtz added the PR: Merge after creative-break Merge after creative-break (min. 1 week) label Jul 15, 2024
Copy link
Member

@buhtz buhtz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you seen the minor suggestions I made in the files?
I had other contributors in the past also missing it. Not sure if I do something wrong on the GitHub interface?

But beside that minor things I would suggest you to merge it yourself and earn the credits. 😄 ❤️

EDIT: Mhm... Maybe this comments appear only after I finishing a review?

HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
HISTORY.md Outdated Show resolved Hide resolved
@emtiu
Copy link
Member Author

emtiu commented Jul 15, 2024

Yes, the suggestions only showed up in this "conversation" after your comment, so you probably need to finish the "review" before others become aware. But it seems you can do many reviews after the other ;)

Sorry, I forgot to [skip ci] this time …

@emtiu emtiu merged commit 0d463d2 into dev Jul 21, 2024
2 checks passed
@emtiu emtiu deleted the emtiu-history branch July 21, 2024 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: Merge after creative-break Merge after creative-break (min. 1 week)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants