I see the issues and respect what have been said.
I also trust that you do the best you can with what you've got - as I think many of us do. Time is a valuable ressource and very scarce.
I would love to say that I could step up, but I must admit that most months, I don't really have much to offer. Are there any boring "this should be done sometime"-jobs we could list in a shared "to-do" to help spread more of the workload?
//Daniel
Core Update Schedule frequency
- burt
- Core Team
- Posts: 4547
- Joined: Tue Oct 29, 2019 9:37 am
- Phoenix Version: v1.1.0.8
- : Buy Me A Beverage
- Has thanked: 252 times
- Been thanked: 412 times
Re: Core Update Schedule frequency
Thank you, Daniel - appreciate you taking the time to posting. Time is the biggest bottleneck for all of us.
If anyone has a minute or 10 or 30 to spare here or there, here is some things:
1. Triage the Support Board:
Jump into the "Community Help & Support" forum. Answer setup questions or try to reproduce reported bugs on a clean install to confirm if they are real core issues.
2. Audit Addons:
Pick an addon, test it on the latest core / PHP version, and post updated code or deprecation fixes etc.
3. Test GitHub Commits:
Grab the latest core code off GitHub, test it on a local environment, and drop a comment/thread etc.
Every thread answered or bug looked is one less thing on my plate.
Tiny bits of help soon add up.
--
Less specialized, but still super valuable
I know we have many users who are not so technical, just jump into a thread - any thread that interests you - and post your thoughts/ideas. We won't have innovation without ideas. And an idea, however wacky, might spark something.
If anyone has a minute or 10 or 30 to spare here or there, here is some things:
1. Triage the Support Board:
Jump into the "Community Help & Support" forum. Answer setup questions or try to reproduce reported bugs on a clean install to confirm if they are real core issues.
2. Audit Addons:
Pick an addon, test it on the latest core / PHP version, and post updated code or deprecation fixes etc.
3. Test GitHub Commits:
Grab the latest core code off GitHub, test it on a local environment, and drop a comment/thread etc.
Every thread answered or bug looked is one less thing on my plate.
Tiny bits of help soon add up.
--
Less specialized, but still super valuable
I know we have many users who are not so technical, just jump into a thread - any thread that interests you - and post your thoughts/ideas. We won't have innovation without ideas. And an idea, however wacky, might spark something.
I am not here to build for you.
I am here to build with you. Let's help each other.
I am here to build with you. Let's help each other.