Developer Meeting 2006 07 16

[Dalfy]

I uploaded the log of the meeting we had on july the 16 th. Fill free to comment it in this thread

http://www.cegui.org.uk/meetings/meetin ... 07-16.html

[jacmoe]

Nice read!

I like this:

0.5.0 is about customisation

0.6.0 is about speed

[spannerman]

It is indeed a very good thing to see the developers actively discussing the future of CEGUI.

I mean no disrespect by this, but with the fairly low public presence of the devs (e.g. News updates of progress, participation on the forums etc) over time it is difficult to tell whether any plans are being organised in the background or whether any real interest in its future remains. This does seem to be improving now though.

I just think that users who realise CEGUI is still moving forward towards set goals would be more willing to invest time in it. And I’m not just talking about new adopters, I mean with users submitting patches, giving constructive feedback, testing release candidate code etc.

So yes, it’s a good thing. The Development Roadmap is now updated too, that’s another big positive in my opinion.

[*side note*]
I think it’s a shame that little-to-no feedback is given when users submit patches, and sometimes patches can sit there forever without ever being touched. It wouldn’t compel me to contribute again, anyway. With these rare users being of the “give” disposition in a sea of “take” I’d imagine it’s a mutually beneficial relationship you’d want to keep relatively sweet.
[/*side note*]

I agree on what was said about the samples; more is better!
I always start by checking the samples to see how something is done. If you can demonstrate more advanced features with more complex examples, I bet you that you’ll get fewer questions in the help forums.

[Dalfy]

[*side note*]
I think it’s a shame that little-to-no feedback is given when users submit patches, and sometimes patches can sit there forever without ever being touched. It wouldn’t compel me to contribute again, anyway. With these rare users being of the “give” disposition in a sea of “take” I’d imagine it’s a mutually beneficial relationship you’d want to keep relatively sweet.
[/*side note*]

There is several reason for a patch not going into CEGUI:

• The patch does not go in the direction we want to make CEGUI evoluate in a near future. Integrating it would cause us problem in the short terme
• It's a quick hack that can be generalized and we are going to provide a more generic solution
• The patch do not apply anymore or is going to be inserted in CEGUI in a later release (next development branch)
• We forget this one (It's bad)
• We don't have yet looked at it.

Most of those reason does not explain why we are not giving feedback
At the moment we are learning and starting to put some effort in communication. No worries about it we will also put this effort in correctly giving feedback on patch and contribution. If the patch is in Mantis we will handle it on time. And give a feedback at least when closing ticket with a small description of what is the solution we have done. We will also try to associate commits with Mantis tickets.