[Gtkradiant] A few fixes

[Timothee Besset]

Afaik there is a bit of fragmentation happening already. Most of the
(previously|recently) active developers can be reached on #qeradiant on
irc.telefragged.com. But we can discuss things here as well.

There was a project to massage the 1.4 codebase into a GPL release next
to the 1.5 codebase. I wonder what happened to that.

As far as write access to SVN, I don't mind adding a few people, but I'd
rather see that worked out by people who already have write access. The
way this usually goes is that new contributors would start by sending
patches (like the one in this thread), and after applying a few of them
and looking at the code quality / responsiveness of the developer, we'd
setup direct write access.

TTimo

LinuxManMikeC wrote:
> Well as it says on qeradiant.com "without a development team it is not
> possible or sane to support GtkRadiant any longer."  I was quite
> saddened when I saw that, especially since it was part of the first
> substantial post to the new Wiki.  However, as this is an open source
> project, would interested developers (such as myself) be able to get
> write access to the SVN source tree, the Wiki, and the bug traker?  Of
> course there would need to be some chain of command and trust set up
> so things don't get too crazy.  I feel it would be better to continue
> this official GtkRadiant project rather than fork from it for further
> development.  It isn't productive to drown users in a sea of
> fragmented projects.  There are plenty of popular games (and likely
> new GPL ones to come) that use the Quake engines, so I'm sure there
> are enough interested people out there who could contribute.  Heck, we
> have this patch from Dunk here, thats 1 other interested geek.  So I
> guess I'll be the first to ask... can I ride on the coattails of your
> greatness and become an official part of the project? :-D
>
> For my own contributions, I was thinking of organizing some official
> documentation to post on the Wiki and maybe even a tutorial section.
> I would also be interested in dabbling with the source code in my
> spare time, but I need to finish learning it before I feel confident
> in submitting anything substantial.  Maybe we could get some of those
> missed features/fixes implemented for a 1.5.1 release?
>
> Mike
>
>
> On 6/27/07, Dunk Fordyce <dunkfordyce at googlemail.com> wrote:
>   
>> Hello,
>>
>> Ive attached two patches. The first is for radiant and provides the
>> following:
>>
>> - fixed mnemonics for MRU list
>> - fixed find functionality
>> - added option to always use caulk texture for new brushes
>> - made release the default build
>> - fixed(?) a small bug in install.py that was trying to copy msvc files on
>> linux
>>
>>
>> The second patch fixes the entities.def for warsow.
>>
>> Will there be a patch/bug tracker online for radiant soon?
>>
>> Cheers
>> Dunk
>>
>> Ultra-n00b: irc.quakenet.org
>> d1223m: irc.freenode.net
>>
>>
>> _______________________________________________
>> Gtkradiant mailing list
>> Gtkradiant at zerowing.idsoftware.com
>> http://zerowing.idsoftware.com/cgi-bin/mailman/listinfo/gtkradiant
>>
>>
>>     
>
> _______________________________________________
> Gtkradiant mailing list
> Gtkradiant at zerowing.idsoftware.com
> http://zerowing.idsoftware.com/cgi-bin/mailman/listinfo/gtkradiant
>