KDevelop Maintainership
Evgeniy Ivanov
powerfox at kde.ru
Fri Sep 5 09:06:54 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Neundorf wrote:
> On Monday 25 August 2008, Alexander Dymo wrote:
>> On Thursday 21 August 2008 18:23:39 David Nolden wrote:
>>> Is there actually something we need an official maintainer for? Else I
>>> propose that we go on like now, as you propose.
>> IMHO there's only one thing KDevelop 4 maintainer can do - is to release
>> 4.0 as a complete product, not just a collection of core + plugins.
>>
>> For that we need a person with a clear vision of KDevelop and the
>> willingness to enforce that vision. We have great people on the team and
>> great code in svn, we just need to put all this together. And yeah, this
>> means that maintainer should be (in my opinion) the one person, not a
>> group.
>
> I agree, the job of a maintainer is not only to care for released stuff and
> fix bugs, he can/should also give some direction to the project. This is
> necessary also before anything is released.
>
> Alex
>
http://dot.kde.org/1219926799/
I guess maintainer will have a lot of release job. But we will have a
better development scheme.
- --
Cheers, Evgeniy.
Key fingerprint: F316 B5A1 F6D2 054F CD18 B74A 9540 0ABB 1FE5 67A3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkjA9q4ACgkQlUAKux/lZ6MKAgCgjBM6CBclDuE1IUOW9rlzoB0i
J3kAnRP1XsZgXFvfKXorMtaZab1eapKj
=ssfm
-----END PGP SIGNATURE-----
More information about the KDevelop-devel
mailing list