-
Notifications
You must be signed in to change notification settings - Fork 210
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
🌱 v2.25.0 #253
Conversation
@luxonauta I do not agree with your aggressiveness here. Who approved this? |
Hey 👋🏻 @dsifford, Zeno and I have been working on these updates for PRO for a while, and we wanted to port them to Classic as quickly as possible to bring the Dracula Classic theme closer to what we have in Dracula PRO. |
I do not agree here. I emailed zeno just now and I will say that if this is the practice that you are going to use moving forward then I'm forking this project and leaving. This is way too aggressive and is not in the spirit of OSS. A theme with 7+ million installs requires a lot more thought when making changes like this. I found out about this after seeing 10+ negative review this morning in the marketplace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luxonauta Why would you even do this? I don't have bun and don't plan to download bun. Most contributors likely don't have bun. Please revert this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this.
|
||
[[overrides]] | ||
files = '*.{yml,yaml}' | ||
[overrides.options] | ||
tabWidth = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change has nothing to do with the task here and should have been done in a separate PR.
"files.eol": "\n", | ||
"[md]": { | ||
"editor.wordWrap": "bounded", | ||
"editor.wordWrapColumn": 75 | ||
}, | ||
"[yml]": { | ||
"editor.insertSpaces": true, | ||
"editor.renderWhitespace": "boundary", | ||
"editor.tabSize": 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change has nothing to do with the task here and should have been done in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because you changed the formatting rules, this changeset has become effectively non-reviewable. How do you expect people to see what you've actually done here?
Hey 👋🏻 @dsifford, I understand your concern and would like to clarify a few points. 🧩 From our perspective, the repo seemed abandoned, with several issues and PRs dating back two years. Despite trying to email you and commenting on several PRs and Issues, we are still waiting to receive a response (which is not your obligation, and we understand and respect your time). However, the last commit was on July 15, 2023. One year later, with several updates to the PRO, we decided in December last year to bring Classic closer to what we have in Dracula PRO to facilitate support for both and actively support them closely. 😅 I agree with you, and I'll exercise more caution and thoughtfulness when making changes. If you agree, I will also look for your review on changes like this one. Our shared goal is to collaborate and improve the project constructively. ✅ Also, I'll make sure to open separate PRs with the changes you suggested here as comments. |
A few things here.
I understand that you're enthusiastic. That's very nice to see. But this is not how OSS works. Your changes here I do not agree with and unless they are rolled back and made in a way that is reviewable, then I'm forking this project and leaving. @zenorocha I would love to hear your thoughts here. Do you agree with how this change was performed? |
I'm sorry if there was any miscommunication. We attempted multiple times to reach out and get feedback on the PRs and issues, but I understand there may have been some misunderstandings. 😥 Our intention has always been to collaborate and improve the project constructively. I appreciate your work and dedication over the years, and I am committed to respecting and working together for the benefit of the project.
✅ I am available to discuss and review any necessary changes to ensure we are all aligned. |
Please show me. |
I think it will be more beneficial to iterate together from now on than to continue this discussion. ✅ I am available to discuss and review any necessary changes to ensure we are all aligned. 😅 |
Since there has been quite a bit of negative feedback and the change does not follow the contribution process, the immediate priority should be to roll back the code and release a new version to avoid disrupting more users. As for iteration and discussion, that is something that should be considered after this. |
I reverted the recent changes and will open separate PRs for review. Thank you all for the discussion and feedback! 🧩 |
Note: This update brings the Dracula Theme closer to what we have in Dracula PRO and thus facilitates support for both; it also prepares us to introduce the Light variant for the Classic in the future.