DiM wrote:somebody comes in and brags an update is coming. he promises it will be important/nice/great/bring new innovative things. and months later after no feedback whatsoever we end up with an update that could very well be nice on its own but the problem is that during the waiting period, because we lack any sort of information each of us starts thinking, dreaming and hoping only to realise that in the end the update is not what we wanted.
This is important: I never said that a big, important, nice update is coming. I've just said that something is moving behind the scenes.
DiM you were on the Team as well, you know that volunteers don't know things years before they are realeased but just few time before the others.
Anyway I don't think it's matter of months in this case, but more few days, at least I hope.
About this, instead:
RjBeals wrote:why not just say what it is? Why does it have to be mysterious? Maybe you'll get feedback if you make it public?
1. I don't know why it has to be mysterious, but it's not my business and being part of the TeamCC i can't tell things before they are announced officially, specially because in most of the cases I don't know what they are! lol
2. The feedback part. I'm on your side here. There's no day in which I don't push in that direction and imo it should be the way to go. It's probably the worst part of my job as foreman. Gather people desires and achieve them. It's like I always find myself caught between the rock and a hard place. Sometimes is not simple to find a way to give people what they want, convince admins that you're speaking for a reason. On the opposite, sometimes is not simple to convince people that what they had is really what was possible to give them in that moment. Balance people expectations and desire with what is reality is 99 time on 100 an impossible mission and there's no day in which I don't ask to myself: "I'm really doing all I can do to serve the foundry people in the right way?"
Now, what I would like to do is create the right place, and I think this thread could be that place, for a serious discussion. What should be the perfect way to have things done? How we should manage updates and requests? I mean, it's clear that the xml suggestion thread is bullshit. Imo there's no point in post something there and wait without a serious discussion. Imo suggestion should go through a different way, it doesn't matter if a suggestion end up with a simple and sad: "no it can't be done, rejected". Imo it's 1000 times better than don't know. So for you guys what is a good way to manage suggestion, at least for the foundry?
But remember, they should be proposals, not orders...we're not here to rule the site but to make sure our voice is heard and things done taking into account what we say, even if it could mean that something is not always in the way we would like to have it.
Personally I think that there should be a sort of semi regular basis on which updates should work, considering the foundry slownwss i would say 1 every 4 months or 6 months, but in any case not less than 1 every year. I would say that CAs and admins should try to gather info during this period of time and try to understand and ponderate what updates could be beneficial for the foundry and in the same time what updates are possible and feasible from a technical point of view. When this is done I would go with the 3 best candidates to start a public review period and discussion, maybe with a public poll. To me this should be the wway to go, but I don't know if it matches your vision.
What are your thoughts about it? Remember, if I know how you would like to see this place running I can try to push things in a direction, try to create a democratic system where democracy is appliable since it's probably the best way to go.
It's your turn, I'll hand the discussion over to you