39
@ kc0maz
Thanks for the work with James and DJ helping to clarify our role. I was just a bit unsure what
solely for Project meant. Still not all that comfortable with the words
governed by Project Council, but that could just be me. As long as we make sure that everyone knows what everyone else needs, then no probs. Being basically a tool enabling clear and accurate passing on of requests from various groupings of the XOOPS community at large (devs are community members as much as are end-users), if a team decides to reject a request, that's not our decision, so there's not much that we'd need to be governed over, I'd imagine... except dereliction of duty perhaps.
Yup, once we're all set up, issue tracking on a wiki would work well, or possibly a ticketing system of some sort.
In the meantime, clutter or not, this is probably the best place to keep our discussions open and on record. I'll take on the recording of ideas here and post a weekly synopsis here if people think that would help us not lose track of anything important that gets posted here.
As for leadership, I think you're doing fine, kc0maz. Unless you'd rather not do it, I nominate you
Crip
Never let a man who does not believe something can be done, talk to a man that is doing it.
