Re: OpenDKIM Infrastructure (was: splitting configure.ac into libopendkim/configure.ac?)

From: Daniel Black <daniel.subs_at_internode.on.net>
Date: Sun, 11 Oct 2009 21:05:17 +1100

On Wednesday 07 October 2009 20:58:53 SM wrote:
> Hi Daniel,
>
> At 00:50 07-10-2009, Daniel Black wrote:
> >I meant to mention that gnutls library cascades configure.ac scripts well.
>
> Thanks. As always, patches are welcomed. That doesn't mean that we
> won't work on this if a patch is not submitted.

I'm happy to write it. Though with the patches I have in
http://sourceforge.net/tracker/?func=detail&aid=2873865&group_id=269812&atid=1147703
I'm avoiding going to fast as it will just create patching conflicts.

Also planned in the configure.ac relm:
- AC_DEFINE to define _FFR_ macros in an include
- man pages including FFR features noting when disabled
- deploy a pkg-config entry for libopendkim

> >ah - ok - its missing a link on http://lists.opendkim.org/
>
> We don't have a link on that web page as the CVS mailing list was set
> up to address an administrative need. It's a public mailing list
> even though we don't advertise it. We are open to any suggestions to
> build an open infrastructure for the OpenDKIM project.

Based on recent experiences with Gitorious (http://www.gitorious.org/about)
I've found it wonderfully inviting to contribute to and have a public review
process.
features I've found appealing:
1. openid registration
2. web based git cloning that is public read and private to write to
3. uploading public ssh key via web to gain access to your repository
4. review process where any user can create merge requests to the main branch
5. anyone registered person can comment on merge requests
6. has its own wiki for developing policy API's for instance.

git based has the ability to maintain forks for development APIs and other
things that needs not be merged in a short term. I'm currently using quilt
patches on the cvs repository which isn't as friendly.

btw this was my first real git experience and I wasn't off put by it.

> As it is a
> community effort, it's up to all of the developers (that includes you
> :-)) to agree on what should be done and how it should be done.
thanks

Thanks for the list archives too.
Received on Sun Oct 11 2009 - 10:05:42 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:32:29 PST