I've been a part of the community since Kura released Kore back in 2003, and an avid botter since Artforz created the first public bot for Ragnarok. I've seen Kore grow and become what it is today since
day one. OpenKore is at a crossroads on its downhill struggle, I seek to point it in the correct direction.
I try I demonstrate a rigid enough adherence to proper procedure, but allow room for change, modernization, and innovation (as it may be). Those who know me know that if nothing else, I'm a devoted to OpenKore and its community now as I was when it was in its infancy, and I've been offering support, both technical and otherwise, as far back as "the Apez days." In addition, I have been modding and contributing to Kore, both officially and unofficially, for almost as long. I have a firm grasp of many programming languages and paradigms, ideas, people, forward thinking, and
embracing new technologies to provide a richer experience for users and developers alike.
In the future, I see a tightly knit development team, collaborating over many mediums; not just forums, a wiki, SVN, or IRC, but through real project management, bug tracking, and an overall correct and professional inner agenda. And twice as many buzzwords.

Hang on, there's *sniff* ...there's something in my eye.
OpenKore has always lacked this sort of organization. It was never needed in the past as Kore was always one man writing one Perl script, and that was it. But OpenKore is modular, it's huge, it has a team, and it is in dire need of streamlining. OpenKore needs someone who will point at a single developer and say, "You, fix this bug," followed by pointing to another developer and saying, "You, commit this patch." Adding this
X-Factor will make OpenKore's rebirth not a matter of
if, but a matter of
when or
how long.