Libification project (SoC)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 Hi Shawn,

 I'm going to apply for the libification project and, in order to help
me to get started, would be good to get some feedback regarding the
project's goal and your expectations.

 I'll just dump some thoughts/question I had, so that we can
start some discussion.

 1. This' a more complete todo list, based on the wiki and a
quick look at the code.

    o Remove static variables
    o Avoid dying when a function call fails (eg, malloc())
    o Input parameter checking (plus errno setting)
    o Documentation (eg, doxygen)
    o Unit-tests
    o Add prefix (eg, git_*) to public API functions

 Do we agree here? Is there more suggestions?

 2. What's the minimum amount of work that need to be done for
the SoC project to be considered successful?

 3. I don't code in Perl, is it a problem? I mean, the project's
goal is to have a Perl binding but I think it goes far from
that: we could have a python module, a C program, or anything
that shows the libgit is useful.

 Thanks,

-- 
Luiz Fernando N. Capitulino
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]