Re: [Cgdb-devel] CGDB Development Methods (was Re: CGDB 1.0 Proposal)

[Bob R. <bo...@br...>]

Well, what's the current proposal?
(Keeeeppppp iiiiittttt gggooooiiiinnnnngggggg)

Bobby


On Fri, Aug 15, 2003 at 03:32:36PM -0400, Mike Mueller wrote:
> On Thu, 14 Aug 2003, Bob Rossi wrote:
>=20
> :   1. testing should be a key component in CGDB/TGDB.
> :      TGDB is poorly tested. It does have a testsuite, but it basically
> :      is a sanity checking device. For *every* new feature we add to
> :      either tool, we need to add a testsuite entry. I don't know how
> :      we are going to do this, but it will help with regressions.
>=20
> I agree, but I think this isn't really an issue right now.  It is=20
> definitely something to keep in mind during development.
>=20
> :   2. Documentation is also very important. CGDB/TGDB need to=20
> :      support 2 different types of documentation.=20
> :         a) Internal, describing algorithms, design decisions, interface=
s ...
> :            For the internal we could use doxygen ( of course ). If
> :            anyone recommends anything else, please bring it up.
> :         b) External, user manuals, HOWTO's, FAQ's, ...
> :            For external, we should probably use the GNU documentation
> :            standard.=20
> :            http://gnu.ghks.de/software/texinfo/texinfo.html
> :            I would defiantly be up to picking a different standard if
> :            anyone can suggest it.
>=20
> Ok.  I am not sure if doxygen is overkill or not, but I'm not=20
> opposed to using it.  We could also just comment header files well,=20
> and write a text file or two about the design (in the CVS=20
> repository).
>=20
> :   4. Coding standards.=20
> :      For this we can go two different routes. Pick a coding standard or
> :      don't. I prefer to have one. I don't really care which one it is,
> :      I would like to hear someone else's opinion on this topic.
> :
> :      I only know of 2 coding standards. The Linux kernel, and GNU's.
>=20
> We currently have differing styles of code in CGDB, and I don't see=20
> it as a problem.  As long as it's readable.
>=20
> :   5. Patch approval mailing list.
> :      I think all patches should be mailed in, and one of us can apply
> :      the patch. This way, we can make sure that the ChangeLog is done
> :      correct, the coding standard is correct, and none of us are
> :      getting lazy.
> :
> :
> :I understand that many of these ideas seem like overhead, but in the
> :end, there will be a good product thats well rounded, instead of just
> :another free software project.
> :
> :So, if you think that some of these are too much for a small project,
> :and that its overboard, let me know.
>=20
> My reaction to a lot of these suggestions is that they are overkill. =20
> However, if you don't mind putting the extra work in to make them=20
> happen, they don't hurt to have.
>=20
> This is a really small project, and I think it will always be (even=20
> if it becomes popular).  Also, a lot of these are bridges we can=20
> cross in the future if it is necessary.
>=20
> Mike
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/=
01
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel