Originally Posted by McBean
I'm no coder by nature, but rather a project manager. If you need some help with organization, defining scope and priortization - I'm more than willing to help with the work and test whatever is needed.
If not, I'll graciously back out of the thread and just keep my eyes open on the status of a revamp.
What's not clear to me is the consensus direction. Is it easier to strip down existing Mazzle infrastructure and modernize what's in place, or are we looking at all new source code with some public wiki for dev/mods/etc? There are pros and cons to each roadmap.
--McBean
|
Question: How about giving McBean really the lead?
And then you know, there is some coders here in this thread, just start with it.
I (who is N0 coder) would say, it is faster to update then to re-write. Even though, re-write has its merits for sure.
But somebody who opens a project saying
We need:
DUF (to do this and that)
HUD (having this error and that not working)
Geist (that button-menu to appear under youre mouse)
Art (working/not working)
Action Bars (Mazzlefier)
Mazzlefier itself
and so on. Who just names the issues and then the get fixed by one of the coders.
Curse-Forge has a ticket system, something like that. Some open issues with descriptions and people to fix that.