Hi Oswald,
I'm finding this project (isync) really neat and may be interested in
further contributing to it. And I would like to first clarify a few
things regarding the codebase and contributions if that's okay with you.
(0) Does the codebase use as reference any particular set of standards
or implementations when choosing what libraries and functions to use?
For example, does it only use standard system calls that are included in
POSIX.1 (and if so, which version?), or that are available on Linux,
FreeBSD, macOS, etc.?
(1) When sending patches, do you prefer each single change as its own
patch in an overall patchset, or multiple related changes squashed into
a single patch? I personally default to the former, but can do the
latter if desired.
(2) Would you be open to accepting patchsets whose sole purpose is to
refactor the code, such as for better modularity, extensibility,
flexibility, or just readability? I've already been doing some crude
changes just to understand the codebase. But if refined, I think some
could potentially help improve the code.
(3) Same as above, but for patches which mainly add function comments.
I do actually have a specific reason for this one. Many functions seem
to have a loosely defined purpose and behaviour, such that calls to them
sometimes depend on details of the function's implementation which need
not stay the same over time. Adding some comments outlining exactly
what behaviour should or should not be relied upon would (I think) be
beneficial for preventing such subtle misuse of functions.
(4) Would you prefer patchsets be sent in only after any previous
patchset was reviewed and (if accepted) pushed upstream, or patchsets be
sent in whenever they're ready? I don't want to overload development
with multiple patchsets at once if that's not desired.
Thank you so much for your time!
Take care,
Seth McDonald.
--
E9D1 26A5 F0D4 9DF7 792B C2E2 B4BF 4530 D39B 2D51
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
