<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Forwarding this to -devel. Apologies, I sent it to Max only by mistake<br><br><hr id="stopSpelling">From: philipk79@hotmail.com<br>To: max@quendi.de<br>Subject: RE: [Scummvm-devel] What is happening to the ScummVM team?<br>Date: Fri, 13 Feb 2009 10:27:46 +0000<br><br>
<style>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</style>
> >> In the past, I very often tried to email scummvm-devel about <br>> >> something, to get feedback and help me decide how to do something. <br>> >> My experience is that usually this didn't work out at all, or if, <br>> >> then essentially with a tiny group (usually 1-3) of people actually <br>> >> talking.<br>> ><br>> > I remember some of those mails. But I think the small feedback is <br>> > not a reason to stop doing so. Especially when some of the then not <br>> > discussed changes would have more people interested for whatever <br>> > reason.<br>> <br>> Maybe, maybe not. I once was idealistic and wrote emails to scummvm- <br>> devel about almost every endeavor I planned. These days, I am rather <br>> disillusioned when it comes to that. So, while the small feedback <br>> might not be a reason to stop doing writing emails to scummvm-devels, <br>> I also ask myself what the reason is to continue writing them?<br>> <br><br>To be honest, not all people are familiar with the internals of the common<br>code. Some questions were aimed towards specific ports of ScummVM,<br>which not all people could answer. In such cases, I think that no answer<br>is better than a wrong answer, or something along the likes of "Nice<br>question, but I don't know how to answer it"<br><br>> <br>> >> I do think that we should talk about merge decisions etc. earlier <br>> >> on scummvm-devel -- out of politeness / courtesy, at the very <br>> >> least. Although I don't think this will actually change the way <br>> >> decisions are made much, because most people will stay silent, and <br>> >> we will not always end up with consensus decision either. But at <br>> >> least everybody can have the feeling of having been informed in due <br>> >> time.<br>> ><br>> > Maybe it would not change the decisions, but actually I think the <br>> > politeness / courtesy argument is rather strong here.<br>> <br><br>Agreed, at least the politeness / courtesy argument is quite strong here.<br>I personally don't have any objections against new engines, in fact I love<br>to see ScummVM grow and support new games, but at least it would be<br>great if small announcements are made about big new features or, more<br>importantly, new engines. It would also be nice to know which potential<br>engines will be added in the future.<br><br>Also, there are several engines in private repositories, which are in various<br>stages. What would be the best course of action concerning them? Add<br>them to the public repository in their current state? Or wait till they're<br>more mature? It wouldn't be nice to have cases like M4, igor or cruise all<br>over again :(<br><br>Regards<br>Filippos<br><br><hr>Windows Live™: E-mail. Chat. Share. Get more ways to connect. <a href="http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009">See how it works.</a><br /><hr />Windows Live™: Keep your life in sync. <a href='http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t1_allup_howitworks_022009' target='_new'>See how it works.</a></body>
</html>