From jerry at opendnssec.org  Thu Jan  2 07:01:50 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 2 Jan 2014 08:01:50 +0100
Subject: [Opendnssec-develop] RE: Move to git
In-Reply-To: <4822620B-D990-41AD-A079-CDF908165361@sinodun.com>
References: <4822620B-D990-41AD-A079-CDF908165361@sinodun.com>
Message-ID: <CAGTFMNazwmkfiRPyqWfHrM-godWAyY9fXuMFR7jY6dnW3FajSQ@mail.gmail.com>

On Fri, Dec 20, 2013 at 3:48 PM, Sara Dickinson <sara at sinodun.com> wrote:

> The email below is a draft of an announcement to the users list about the
> move to git? Comments? Anything I missed?
>

Some comments:
- Remove branch model info, there is really no need to know that.
- Add that we will still supply tarballs at dist.opendnssec.org.
- Maybe link to https://svn.opendnssec.org/trunk/README.git instead of
FishEye, less clutter around the text.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140102/61406fef/attachment.htm>

From jerry at opendnssec.org  Thu Jan  2 07:11:04 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 2 Jan 2014 08:11:04 +0100
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
	<979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
Message-ID: <CAGTFMNZ2o0RbO8pQjOTuJR5i5XqZCADyTHSJ_fewU48zWWguZA@mail.gmail.com>

On Fri, Dec 20, 2013 at 3:21 PM, Sara Dickinson <sara at sinodun.com> wrote:

>
> - (minor) in the setup section there is a note under the instructions for
> forking "You might the a option where the fork should be done, select
> yourself." I suppose this should be "You might get the option of where the
> fork should be done, select yourself"???
>

Fixed.


> - (minor) need to add a step cd into your cloned dir after cloning and
> before checkout
>

Fixed.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140102/756885ad/attachment.htm>

From sara at sinodun.com  Tue Jan  7 15:00:53 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 7 Jan 2014 15:00:53 +0000
Subject: [Opendnssec-develop] RE: Next Developer Workshop @ IETF 89
Message-ID: <986CC7FE-753F-4951-B730-8DDA21AF6CF7@sinodun.com>

Hi All, 

The next developer workshop is planned for Thursday 27th and Friday 28th February (just before IETF 89 which is being held in London). The aim would be to have a code sprint focussed on 2.0 development. 

Please could you fill in the doodle below to indicate your availability:

http://doodle.com/rwuattih7vqnt4mw

Exact location is still TBD, but will be either London or Oxford. If you are available, but funding is an issue then please contact me directly to discuss. Also, if you need a letter of invitation to support a visa application please let me know.

Sara.




From jerry at opendnssec.org  Thu Jan  9 08:38:53 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 9 Jan 2014 09:38:53 +0100
Subject: [Opendnssec-develop] All jenkins jobs will be temporarily turned off
Message-ID: <6990943457691073792@unknownmsgid>

Hi all,

All the jenkins jobs will be turned off today.

This is because I need to find a better way to handle Git then we do now.
The JGit we are using today, because the other one requires Git 1.7+ on all
nodes which we don't have, will not work with the pull request workflow we
have in the works.

Hopefully this will be done by the end of the day.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140109/358efbf0/attachment.htm>

From jerry at opendnssec.org  Thu Jan  9 12:29:12 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 9 Jan 2014 13:29:12 +0100
Subject: [Opendnssec-develop] Maintenance of dist.opendnssec.org and SVN
	today Thursday 15:00 - 15:30 CET
Message-ID: <1CF982E4-24E2-4448-AF7F-EDB0ABE99E87@opendnssec.org>

Hi,

I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140109/4c2231ed/attachment.bin>

From jerry at opendnssec.org  Thu Jan  9 14:16:01 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 9 Jan 2014 15:16:01 +0100
Subject: [Opendnssec-develop] Re: Maintenance of dist.opendnssec.org and SVN
	today Thursday 15:00 - 15:30 CET
In-Reply-To: <1CF982E4-24E2-4448-AF7F-EDB0ABE99E87@opendnssec.org>
References: <1CF982E4-24E2-4448-AF7F-EDB0ABE99E87@opendnssec.org>
Message-ID: <A91A0F5D-D494-42F1-812F-A003879B6D08@opendnssec.org>

On Jan 9, 2014, at 13:29 , Jerry Lundstr?m wrote:

> I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.


All done.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140109/56903877/attachment.bin>

From jerry at opendnssec.org  Thu Jan  9 16:16:42 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 9 Jan 2014 17:16:42 +0100
Subject: [Opendnssec-develop] Re: All jenkins jobs will be temporarily
	turned off
In-Reply-To: <6990943457691073792@unknownmsgid>
References: <6990943457691073792@unknownmsgid>
Message-ID: <EB2316BE-251E-44FA-8DC2-2756FB036567@opendnssec.org>

On Jan 9, 2014, at 09:38 , Jerry Lundstr?m wrote:

> All the jenkins jobs will be turned off today.


The jobs will be turned on tomorrow during the day.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140109/5dcfd22b/attachment.bin>

From jakob at kirei.se  Fri Jan 10 08:51:22 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Fri, 10 Jan 2014 09:51:22 +0100
Subject: [Opendnssec-develop] softhsm file permissions patch review
Message-ID: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>

I could use some additional review on the patch proposed in https://issues.opendnssec.org/browse/SUPPORT-95.

	jakob



From jakob at kirei.se  Fri Jan 10 09:08:12 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Fri, 10 Jan 2014 10:08:12 +0100
Subject: [Opendnssec-develop] Re: softhsm file permissions patch review
In-Reply-To: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>
References: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>
Message-ID: <A5F7F0FF-CD29-46F9-9622-8D70EF9D38A6@kirei.se>

On 10 jan 2014, at 09:51, Jakob Schlyter <jakob at kirei.se> wrote:

> I could use some additional review on the patch proposed in https://issues.opendnssec.org/browse/SUPPORT-95.

https://github.com/jschlyter/SoftHSMv1/compare/SOFTHSM-51

	jakob



From jerry at opendnssec.org  Fri Jan 10 11:15:12 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 10 Jan 2014 12:15:12 +0100
Subject: [Opendnssec-develop] Re: All jenkins jobs will be temporarily
	turned off
In-Reply-To: <EB2316BE-251E-44FA-8DC2-2756FB036567@opendnssec.org>
References: <6990943457691073792@unknownmsgid>
	<EB2316BE-251E-44FA-8DC2-2756FB036567@opendnssec.org>
Message-ID: <CAGTFMNZGmVeCAdXiw_kFE3neH4d=7QnTsHVQo2sj-zQBgH8c1w@mail.gmail.com>

On Thu, Jan 9, 2014 at 5:16 PM, Jerry Lundstr?m <jerry at opendnssec.org>wrote:

> The jobs will be turned on tomorrow during the day.
>

Jobs are enabled again.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140110/88758694/attachment.htm>

From rick at openfortress.nl  Fri Jan 10 18:49:10 2014
From: rick at openfortress.nl (Rick van Rein)
Date: Fri, 10 Jan 2014 19:49:10 +0100
Subject: [Opendnssec-develop] 
	SoftHSM2 docs, minimum OpenSSL version is 1.0.0
Message-ID: <B71CC669-65D6-4D79-9802-9D4A13991BAC@openfortress.nl>

Hello,

I tried building SoftHSM 2 against OpenSSL 0.9.8 and it failed to compile; the return values of the HMAC context operations cannot be mapped to boolean because they are void.  Using OpenSSL 1.0.0 should remedy this.  So did using Botan instead.

The instructions on this page therefore need updating where they name the minimum version:
https://wiki.opendnssec.org/display/SoftHSMDOCS/SoftHSM+Documentation+v2.0

Cheers,
 -Rick

From jakob at kirei.se  Mon Jan 13 07:58:54 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Mon, 13 Jan 2014 08:58:54 +0100
Subject: [Opendnssec-develop]  SoftHSM2 docs,
	minimum OpenSSL version is 1.0.0
In-Reply-To: <B71CC669-65D6-4D79-9802-9D4A13991BAC@openfortress.nl>
References: <B71CC669-65D6-4D79-9802-9D4A13991BAC@openfortress.nl>
Message-ID: <9C34BF09-2703-48FE-B48D-D1892CA40D95@kirei.se>

On 10 jan 2014, at 19:49, Rick van Rein <rick at openfortress.nl> wrote:

> I tried building SoftHSM 2 against OpenSSL 0.9.8 and it failed to compile; the return values of the HMAC context operations cannot be mapped to boolean because they are void.  Using OpenSSL 1.0.0 should remedy this.  So did using Botan instead.

Fixed.

	j



From sara at sinodun.com  Mon Jan 13 10:59:48 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 13 Jan 2014 10:59:48 +0000
Subject: [Opendnssec-develop] RE: Team meeting - Tuesday 14 Jan @ 14:00 CET
Message-ID: <966F837F-0A60-4FA9-90AB-B132FC8C061D@sinodun.com>

Hi All, 

Happy New Year everyone!  We have a team tomorrow (Tuesday):

Date:      Tuesday 14 Jan 2014
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-14+Agenda

Sara.



From jerry at opendnssec.org  Mon Jan 13 15:28:56 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Mon, 13 Jan 2014 16:28:56 +0100
Subject: [Opendnssec-develop] The build bot
Message-ID: <CAGTFMNZvYy4pZ+1+4Cfenv5z=sQ-uFERqAXqDg_BAqRV7_PCZw@mail.gmail.com>

Hi all,

Just a quick status update, the bot that will build pull requests is coming
along fine. You will find the code here
https://github.com/opendnssec/build-bot .

What it basically does is; checks periodically for pull requests with bot
commands from given reviewers (config option), creates jobs in Jenkins for
those pull requests and start a build chain and then updates the pull
request with the status of the build.

You can see this currently for
https://github.com/opendnssec/SoftHSMv1/pull/4 , if you look at the first
section you'll see "Waiting to hear about 7e1d5e6" in yellow as it is in
pending status waiting for the build status. It will later (that code is
not in yet), when the build has been done, update the issue with the status
of the build.

Also notice that I made a comment "bot build" below, that is what triggers
the process and that would fit nicely into the process after you have
reviewed the patch. The bot would later on also be able to auto merge the
pull request if the build was successful, if for example the command "bot
build merge" was given.

Anythings possible :)

You can also see the Jenkins jobs tried to this pull request at
https://jenkins.opendnssec.org/view/pull-requests/ (ignore pull-test*). If
a build has failed there will be a quick link from the pull request on
GitHub directly into the job that failed and the build, so it will be easy
to find out why it went red when it does.

Cheers,
Jerry

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140113/a73d270c/attachment.htm>

From sara at sinodun.com  Tue Jan 14 14:22:32 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 14 Jan 2014 14:22:32 +0000
Subject: [Opendnssec-develop] Team meeting - Tuesday 14 Jan @ 14:00 CET
In-Reply-To: <966F837F-0A60-4FA9-90AB-B132FC8C061D@sinodun.com>
References: <966F837F-0A60-4FA9-90AB-B132FC8C061D@sinodun.com>
Message-ID: <AB653392-748E-425A-8139-5451A88DF685@sinodun.com>

Hi All, 

The minutes from the meeting today are available for review here:

https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-14+Agenda

Next meeting is scheduled for:

Date:      Thursday 30 Jan 2014
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC


Regards

Sara.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenDNSSEC team meeting.ics
Type: text/calendar
Size: 715 bytes
Desc: not available
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140114/ee32fc4d/attachment.bin>
-------------- next part --------------


On 13 Jan 2014, at 10:59, Sara Dickinson <sara at sinodun.com> wrote:

> Hi All, 
> 
> Happy New Year everyone!  We have a team tomorrow (Tuesday):
> 
> Date:      Tuesday 14 Jan 2014
> Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
> Method:  Teamspeak
> Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-14+Agenda
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop


From sara at sinodun.com  Wed Jan 15 11:43:53 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 15 Jan 2014 11:43:53 +0000
Subject: [Opendnssec-develop] RE: JIRA workflow
Message-ID: <5D4F0C3E-4003-4051-8867-7C3B34DCBE26@sinodun.com>

Hi All, 

I had an action from the developer workshop to see if we could improve our JIRA workflow with regard to back-porting issues to other branches. We currently clone issues for each branch a fix is ported to, which makes the sprint work boards very informative, but is somewhat cumbersome in practice. So I looked into whether we could use sub-tasks instead. 

Unfortunately this won't work as one of the agile restrictions is that sub-tasks must be in the same sprint as the parent task. I've looked again but nothing else available in JIRA makes things particularly easier, so I think we will have to stick with cloning issues for now :-(

Sara.

From jerry at opendnssec.org  Thu Jan 16 09:41:05 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 16 Jan 2014 10:41:05 +0100
Subject: [Opendnssec-develop] Maintenance of dist.opendnssec.org and SVN
	today Thursday 14:00 - 14:30 CET
Message-ID: <0BB30FC1-AD08-47A2-A68D-C9F10E26EDFA@opendnssec.org>

Hi,

I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140116/34bd9832/attachment.bin>

From jerry at opendnssec.org  Thu Jan 16 13:12:59 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 16 Jan 2014 14:12:59 +0100
Subject: [Opendnssec-develop] Re: Maintenance of dist.opendnssec.org and SVN
	today Thursday 14:00 - 14:30 CET
In-Reply-To: <0BB30FC1-AD08-47A2-A68D-C9F10E26EDFA@opendnssec.org>
References: <0BB30FC1-AD08-47A2-A68D-C9F10E26EDFA@opendnssec.org>
Message-ID: <98030751-93EC-429E-8C4E-C27AE550A4B0@opendnssec.org>

On 16 Jan 2014, at 10:41 , Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.

Very few updates so quick maintenance, all up now.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140116/93e09ce4/attachment.bin>

From jerry at opendnssec.org  Fri Jan 17 13:54:10 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 17 Jan 2014 14:54:10 +0100
Subject: [Opendnssec-develop] Re: The build bot
In-Reply-To: <CAGTFMNZvYy4pZ+1+4Cfenv5z=sQ-uFERqAXqDg_BAqRV7_PCZw@mail.gmail.com>
References: <CAGTFMNZvYy4pZ+1+4Cfenv5z=sQ-uFERqAXqDg_BAqRV7_PCZw@mail.gmail.com>
Message-ID: <58881456-747F-4E38-8740-5A3B67B57CC2@opendnssec.org>

Hi all,

The bot is finished and looking at the migration plan there isn?t a lot left to do.

SO PLEASE EVERYONE START TESTING!

:)

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140117/f42ce063/attachment.bin>

From jakob at kirei.se  Mon Jan 20 09:50:34 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Mon, 20 Jan 2014 10:50:34 +0100
Subject: [Opendnssec-develop] Re: softhsm file permissions patch review
In-Reply-To: <A5F7F0FF-CD29-46F9-9622-8D70EF9D38A6@kirei.se>
References: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>
	<A5F7F0FF-CD29-46F9-9622-8D70EF9D38A6@kirei.se>
Message-ID: <780333D2-AFCF-40C7-B87D-3D7B9B794025@kirei.se>

On 10 jan 2014, at 10:08, Jakob Schlyter <jakob at kirei.se> wrote:

> On 10 jan 2014, at 09:51, Jakob Schlyter <jakob at kirei.se> wrote:
> 
>> I could use some additional review on the patch proposed in https://issues.opendnssec.org/browse/SUPPORT-95.
> 
> https://github.com/jschlyter/SoftHSMv1/compare/SOFTHSM-51

please.

	jakob



From rickard at opendnssec.org  Mon Jan 20 10:24:54 2014
From: rickard at opendnssec.org (Rickard Bellgrim)
Date: Mon, 20 Jan 2014 11:24:54 +0100
Subject: [Opendnssec-develop] Re: softhsm file permissions patch review
In-Reply-To: <780333D2-AFCF-40C7-B87D-3D7B9B794025@kirei.se>
References: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>
	<A5F7F0FF-CD29-46F9-9622-8D70EF9D38A6@kirei.se>
	<780333D2-AFCF-40C7-B87D-3D7B9B794025@kirei.se>
Message-ID: <CAKFiofkv+0R0s3tEBveW17YxX6dnd=8cw1Wqq5rLheJFnko0sQ@mail.gmail.com>

On Mon, Jan 20, 2014 at 10:50 AM, Jakob Schlyter <jakob at kirei.se> wrote:

> On 10 jan 2014, at 10:08, Jakob Schlyter <jakob at kirei.se> wrote:
>
> > On 10 jan 2014, at 09:51, Jakob Schlyter <jakob at kirei.se> wrote:
> >
> >> I could use some additional review on the patch proposed in
> https://issues.opendnssec.org/browse/SUPPORT-95.
> >
> > https://github.com/jschlyter/SoftHSMv1/compare/SOFTHSM-51
>
> please.


ACK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140120/1d071cf5/attachment.htm>

From yuri at nlnetlabs.nl  Mon Jan 20 11:06:43 2014
From: yuri at nlnetlabs.nl (Yuri Schaeffer)
Date: Mon, 20 Jan 2014 12:06:43 +0100
Subject: [Opendnssec-develop] Re: softhsm file permissions patch review
In-Reply-To: <780333D2-AFCF-40C7-B87D-3D7B9B794025@kirei.se>
References: <104CDE13-8FAF-4B1D-B3C2-22367061B62E@kirei.se>
	<A5F7F0FF-CD29-46F9-9622-8D70EF9D38A6@kirei.se>
	<780333D2-AFCF-40C7-B87D-3D7B9B794025@kirei.se>
Message-ID: <52DD0343.1080108@nlnetlabs.nl>

>>> I could use some additional review on the patch proposed in https://issues.opendnssec.org/browse/SUPPORT-95.
>> https://github.com/jschlyter/SoftHSMv1/compare/SOFTHSM-51
> please.

Being not familiar with the code, I see no problems with this patch.
softhsm.cpp:218 umask call could be casted to void though.

//Yuri

-- 
Composed on an actual keyboard: all typos genuine.


From sara at sinodun.com  Mon Jan 20 11:28:50 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 20 Jan 2014 11:28:50 +0000
Subject: [Opendnssec-develop] RE: XML element ordering in 1.4 vs 2.0
Message-ID: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>

Hi there, 

We have come across a difference between 1.4 and 2.0 that I would like to understand before we do our next release. 

In 1.4, the _ordering_ of elements within the xml files is constrained (see the .rnc definition). However Yuri would like to relax this requirement in 2.0 as it makes compatibility with the new database code much easier. 

I?d like to understand if there was a specific reason the order was constrained in 1.4 and if anyone foresees any problem with relaxing the order in 2.0. 

At the moment in 2.0 the impact is that the exported kasp/signconf files have some elements in the signature section in a different order compared to those in 1.4 (no changes in exported zonelist.xml). So I?ve run into a small amount of pain when porting regression tests, but this is manageable. 

Thoughts/comments?

Sara.

From jerry at opendnssec.org  Mon Jan 20 12:11:16 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Mon, 20 Jan 2014 13:11:16 +0100
Subject: [Opendnssec-develop] XML element ordering in 1.4 vs 2.0
In-Reply-To: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
References: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
Message-ID: <304C4C53-CCF8-49A0-ACC9-EBA51BEF7A96@opendnssec.org>

On 20 Jan 2014, at 12:28 , Sara Dickinson <sara at sinodun.com> wrote:

> In 1.4, the _ordering_ of elements within the xml files is constrained (see the .rnc definition). However Yuri would like to relax this requirement in 2.0 as it makes compatibility with the new database code much easier. 

It?s XML so I don?t see any problems having unordered elements.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140120/36c97cf7/attachment.bin>

From matthijs at nlnetlabs.nl  Mon Jan 20 12:21:45 2014
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Mon, 20 Jan 2014 13:21:45 +0100
Subject: [Opendnssec-develop] XML element ordering in 1.4 vs 2.0
In-Reply-To: <304C4C53-CCF8-49A0-ACC9-EBA51BEF7A96@opendnssec.org>
References: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
	<304C4C53-CCF8-49A0-ACC9-EBA51BEF7A96@opendnssec.org>
Message-ID: <52DD14D9.5060701@nlnetlabs.nl>

On 01/20/2014 01:11 PM, Jerry Lundstr?m wrote:
> On 20 Jan 2014, at 12:28 , Sara Dickinson <sara at sinodun.com> wrote:
> 
>> In 1.4, the _ordering_ of elements within the xml files is constrained (see the .rnc definition). However Yuri would like to relax this requirement in 2.0 as it makes compatibility with the new database code much easier. 
> 
> It?s XML so I don?t see any problems having unordered elements.

I don't see any problems with this relaxation either.

Best regards,
  Matthijs

> 
> --
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/
> 
> 
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 



From jakob at kirei.se  Tue Jan 21 07:12:16 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 21 Jan 2014 08:12:16 +0100
Subject: [Opendnssec-develop] XML element ordering in 1.4 vs 2.0
In-Reply-To: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
References: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
Message-ID: <CF75C959-E51F-4393-AC18-D12D7AB68FD7@kirei.se>

On 20 jan 2014, at 12:28, Sara Dickinson <sara at sinodun.com> wrote:

> In 1.4, the _ordering_ of elements within the xml files is constrained (see the .rnc definition). However Yuri would like to relax this requirement in 2.0 as it makes compatibility with the new database code much easier. 

Please elaborate - the ordering is schema-centric, pulling data out using XPath should not have any impact on the ordering. Writing data in the correct order shouldn't be a problem either, but I may be wrong here.

> I?d like to understand if there was a specific reason the order was constrained in 1.4 and if anyone foresees any problem with relaxing the order in 2.0. 

I enforced ordering to get a clean syntax, primary purpose is to ease support (aka "end user debugging").

> At the moment in 2.0 the impact is that the exported kasp/signconf files have some elements in the signature section in a different order compared to those in 1.4 (no changes in exported zonelist.xml). So I?ve run into a small amount of pain when porting regression tests, but this is manageable. 
> 
> Thoughts/comments?

I prefer to keep the ordering, but I'd like to the see real reason for dropping it.

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From jerry at opendnssec.org  Tue Jan 21 08:00:27 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 21 Jan 2014 09:00:27 +0100
Subject: [Opendnssec-develop] XML element ordering in 1.4 vs 2.0
In-Reply-To: <CF75C959-E51F-4393-AC18-D12D7AB68FD7@kirei.se>
References: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
	<CF75C959-E51F-4393-AC18-D12D7AB68FD7@kirei.se>
Message-ID: <-3054030347635690937@unknownmsgid>

On 21 jan 2014, at 08:12, Jakob Schlyter <jakob at kirei.se> wrote:

I prefer to keep the ordering, but I'd like to the see real reason for
dropping it.


Looking at the code I still see that we are generating XML content by hand,
why when we already depend on libxml? :(

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140121/39bbf396/attachment.htm>

From sara at sinodun.com  Tue Jan 21 15:42:18 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 21 Jan 2014 15:42:18 +0000
Subject: [Opendnssec-develop] XML element ordering in 1.4 vs 2.0
In-Reply-To: <CF75C959-E51F-4393-AC18-D12D7AB68FD7@kirei.se>
References: <44AC025D-B965-4169-BF4B-80DC40460FAE@sinodun.com>
	<CF75C959-E51F-4393-AC18-D12D7AB68FD7@kirei.se>
Message-ID: <C40B758F-4BC4-4D82-BF3D-73A403987503@sinodun.com>


On 21 Jan 2014, at 07:12, Jakob Schlyter <jakob at kirei.se> wrote:

> On 20 jan 2014, at 12:28, Sara Dickinson <sara at sinodun.com> wrote:
> 
>> In 1.4, the _ordering_ of elements within the xml files is constrained (see the .rnc definition). However Yuri would like to relax this requirement in 2.0 as it makes compatibility with the new database code much easier. 
> 
> Please elaborate - the ordering is schema-centric, pulling data out using XPath should not have any impact on the ordering. Writing data in the correct order shouldn't be a problem either, but I may be wrong here.

I gather from Yuri that extracting the data from the database structures in a generic way that makes it easy to translate into XML is not actually straightforward?? Of course, we probably could code around it with extra effort but we are trying to take the path of least resistance in 2.0 at the moment to get to something that works with the limited resources we have :-)   So in that context it seems sensible to ask ?do we really need it?. 

I propose that for now (in alpha) we live with the change in ordering since it doesn?t actually break anything, but I will open an issue to be reviewed before we go beta to decide if we should expend effort on fixing it. 

Begin forwarded message:

> From: Jerry Lundstr?m <jerry at opendnssec.org>
> 
> Looking at the code I still see that we are generating XML content by hand, why when we already depend on libxml? :(

It is a very good questions, and on the list to ask Rene who wrote the original code. Similar to the above, since what we have works, re-writing it from scratch is a would be nice, but not a top priority at this stage? 

I anticipate a ?clean-up? phase for 2.0 where we can address these kind of issues, but at the moment we are concentrating on what is completely missing or not working :-)

Sara. 




From jerry at opendnssec.org  Wed Jan 22 06:50:23 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 22 Jan 2014 07:50:23 +0100
Subject: [Opendnssec-develop] Dasbot, buildfarm & Jenkins
Message-ID: <CAGTFMNam1cNFXWO98AdJUv7x=kLmjbO4oNwXR4G+GMmO9kH3sA@mail.gmail.com>

Hi,

I've started work on dasbot, a bot that will setup, update and maintain the
buildfarm platforms. Unless there are any major problems I expect this bot
to be finished some time next week.

I am developing and testing it on VMs locally with all the OS we picked so
when its done it just a matter of reinstalling the VMs at SURFnet, starting
the bot and waiting for it to finish. And that will actually only take a
day or two instead of the weeks I previous planned which is great.

With the new bot I will also make some changes to Jenkins, the LDNS and
SoftHSM build jobs that OpenDNSSEC depends on will be removed and that type
of dependency will be installed and managed by the bot.

This will reduce the overhead for OpenDNSSEC jobs, reduce the complexity
and greatly reduce the overhead for pull request builds since they do build
LDNS and SoftHSM for each pull request as that is our current build chain.

If we would need to test a different version of LDNS it is just a matter of
setting up the old build chain for a specific tag. This could be handled by
the build bot with special build commands, so for example you would make a
pull request updating the build-ldns.sh file and tell the bot maybe "build
+ldns" and it can setup the chain in Jenkins, build and test everything.

Anythings possible :)
/Jerry

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140122/269686e8/attachment.htm>

From jakob at kirei.se  Wed Jan 22 07:24:48 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 22 Jan 2014 08:24:48 +0100
Subject: [Opendnssec-develop] Dasbot, buildfarm & Jenkins
In-Reply-To: <CAGTFMNam1cNFXWO98AdJUv7x=kLmjbO4oNwXR4G+GMmO9kH3sA@mail.gmail.com>
References: <CAGTFMNam1cNFXWO98AdJUv7x=kLmjbO4oNwXR4G+GMmO9kH3sA@mail.gmail.com>
Message-ID: <03B6C588-1018-4D50-96C5-C495627C1920@kirei.se>

On 22 jan 2014, at 07:50, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> Anythings possible :)

and you're the gitwiz from oz.

	j



From sara at sinodun.com  Wed Jan 22 13:26:35 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 22 Jan 2014 13:26:35 +0000
Subject: [Opendnssec-develop] RE: Move to git
Message-ID: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>

All, 

Please try to make some time to test out the opendnssec test git repo at:

https://github.com/opendnssec/opendnssec-workflow-test

The full workflow instructions are here:

https://wiki.opendnssec.org/display/OpenDNSSEC/Git

but a great start is just to clone, make a branch, commit stuff and create a pull request. Then Jerry will do his stuff with the pull request and you can wash, rinse, repeat :-)

We need feedback to move forward with this project - up to now only Jakob and Jerry have been testing it out so please start playing!

**Important: if you haven?t done so already, please create a GitHub account and send your username to Jakob. You can?t join the git party without this ;-)

Sara. 

From jerry at opendnssec.org  Thu Jan 23 06:58:24 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 23 Jan 2014 07:58:24 +0100
Subject: [Opendnssec-develop] The build-bot's commands
Message-ID: <CAGTFMNYhWHdZCnBz=s+G0h901aS5RQkofx3v79CT=z0yfETjmA@mail.gmail.com>

Hi,

These are the build-bot commands that I have thought about so far. I've
tried to make something that is very simple and short but covers all our
needs.

build - Build and run all tests
test - Build and run only the modified tests, if there are no modified
tests then run all tests
merge - Run the build command and merge automatically if successful
build merge - Same as merge
test merge - Run the test command and merge automatically if successful

As some of you might have seen in the pull request is that I have entered
"bot build" to start the process. This can of course be changed to
something more simple and yesterday Jakob mentioned maybe doing something
like hash tags, ex #build #merge etc, and we can change to something like
that later on when the process is more finalized.

Also a note is that there will be fine grain access for each command per
repository. This is to make the option available for us to, for example,
give every developer access to build/test command so that if you want to
you could make a pull request and start the build process to test on every
test platform before handing it over to someone else to review and merge.

Comments/2c?

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140123/6be7ab70/attachment.htm>

From jad at sinodun.com  Thu Jan 23 11:34:29 2014
From: jad at sinodun.com (John Dickinson)
Date: Thu, 23 Jan 2014 11:34:29 +0000
Subject: [Opendnssec-develop] The build-bot's commands
In-Reply-To: <CAGTFMNYhWHdZCnBz=s+G0h901aS5RQkofx3v79CT=z0yfETjmA@mail.gmail.com>
References: <CAGTFMNYhWHdZCnBz=s+G0h901aS5RQkofx3v79CT=z0yfETjmA@mail.gmail.com>
Message-ID: <371F12DF-495A-4241-B2DE-59DA6C04DEA4@sinodun.com>

how about test performance? I am in the middle of developing performance test scripts that will run on titan only. They will be in test-cases-performance.d/

John

John
On 23 Jan 2014, at 06:58, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> Hi,
> 
> These are the build-bot commands that I have thought about so far. I've tried to make something that is very simple and short but covers all our needs.
> 
> build - Build and run all tests
> test - Build and run only the modified tests, if there are no modified tests then run all tests
> merge - Run the build command and merge automatically if successful
> build merge - Same as merge
> test merge - Run the test command and merge automatically if successful
> 
> As some of you might have seen in the pull request is that I have entered "bot build" to start the process. This can of course be changed to something more simple and yesterday Jakob mentioned maybe doing something like hash tags, ex #build #merge etc, and we can change to something like that later on when the process is more finalized.
> 
> Also a note is that there will be fine grain access for each command per repository. This is to make the option available for us to, for example, give every developer access to build/test command so that if you want to you could make a pull request and start the build process to test on every test platform before handing it over to someone else to review and merge.
> 
> Comments/2c?
> 
> -- 
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140123/bc0f974b/attachment.bin>

From jerry at opendnssec.org  Thu Jan 23 11:49:53 2014
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 23 Jan 2014 12:49:53 +0100
Subject: [Opendnssec-develop] The build-bot's commands
In-Reply-To: <371F12DF-495A-4241-B2DE-59DA6C04DEA4@sinodun.com>
References: <CAGTFMNYhWHdZCnBz=s+G0h901aS5RQkofx3v79CT=z0yfETjmA@mail.gmail.com>
	<371F12DF-495A-4241-B2DE-59DA6C04DEA4@sinodun.com>
Message-ID: <9F6FD33A-F7D3-4B86-AA49-967DFE2CF12B@opendnssec.org>

On 23 Jan 2014, at 12:34 , John Dickinson <jad at sinodun.com> wrote:

> how about test performance? I am in the middle of developing performance test scripts that will run on titan only. They will be in test-cases-performance.d/

Can be added but I think we need to play with performance testing a get a grip on what we want to do before we start looking at how to automate it.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140123/6d0b098f/attachment.bin>

From sara at sinodun.com  Sun Jan 26 15:28:22 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Sun, 26 Jan 2014 15:28:22 +0000
Subject: [Opendnssec-develop] RE: Changes to sandbox jobs
Message-ID: <271A5A3C-5CA3-4559-866A-84021020541D@sinodun.com>

Hi All,

The changes to the sandbox jobs to make them easier to use are now in all the branches:

https://wiki.opendnssec.org/display/OpenDNSSEC/How+To+Add+Tests+to+Jenkins

Sara. 

From sara at sinodun.com  Wed Jan 29 14:20:08 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 29 Jan 2014 14:20:08 +0000
Subject: [Opendnssec-develop] RE: Team meeting - Thursday 30 Jan @ 14:00 CET
Message-ID: <05BE6CB8-C8EB-48FE-A560-29EC0A5CAD16@sinodun.com>

Hi All, 

We have a team tomorrow (Thursday):

Date:      Thursday 30 Jan 2014
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-30+Agenda

Sara.



From sara at sinodun.com  Wed Jan 29 14:33:05 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 29 Jan 2014 14:33:05 +0000
Subject: [Opendnssec-develop] RE: Developer Workshop - 27 & 28 Feb
References: <986CC7FE-753F-4951-B730-8DDA21AF6CF7@sinodun.com>
Message-ID: <EC308834-79EB-4E20-ADEF-29A1F65A45D8@sinodun.com>

Hi All, 

The current list of attendees at the planned developer workshop is:

Both days:
Jakob
Jerry
Yuri
Sara
Masson (pending visa approval)

Thursday only:
Matthijs
Sion

I would like to confirm numbers by the end of tomorrow to:
a) confirm that the workshop will go ahead and
b) book a venue (we will book for only as many people are attending as this will affect the price) so please let me know if the above is not correct. 

We are trying to book a venue in London, near to the IETF hotel. Once we have a venue I will send out suggestions for hotels. 

There is no agenda yet, but if you have anything specific you would like to cover then please let me know!

Thanks

Sara. 


Begin forwarded message:

> From: Sara Dickinson <sara at sinodun.com>
> Subject: [Opendnssec-develop] RE: Next Developer Workshop @ IETF 89
> Date: 7 January 2014 15:00:53 GMT
> To: OpenDNSSEC Developers <Opendnssec-develop at lists.opendnssec.org>
> 
> Hi All, 
> 
> The next developer workshop is planned for Thursday 27th and Friday 28th February (just before IETF 89 which is being held in London). The aim would be to have a code sprint focussed on 2.0 development. 
> 
> Please could you fill in the doodle below to indicate your availability:
> 
> http://doodle.com/rwuattih7vqnt4mw
> 
> Exact location is still TBD, but will be either London or Oxford. If you are available, but funding is an issue then please contact me directly to discuss. Also, if you need a letter of invitation to support a visa application please let me know.
> 
> Sara.
> 
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop



From rickard at opendnssec.org  Wed Jan 29 14:48:18 2014
From: rickard at opendnssec.org (Rickard Bellgrim)
Date: Wed, 29 Jan 2014 15:48:18 +0100
Subject: [Opendnssec-develop] static analyzer
In-Reply-To: <7493205A-876C-4A25-90EA-543F601BCC79@opendnssec.org>
References: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>
	<92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>
	<34E1D1F9-C0E7-4F6A-BC19-FAFD4289E9E5@sinodun.com>
	<7493205A-876C-4A25-90EA-543F601BCC79@opendnssec.org>
Message-ID: <CAKFiofk7ds84DVk3Eczi1_=Fn72SCoqxHQ-+u_bhVTxSF5rYpA@mail.gmail.com>

On Tue, Dec 10, 2013 at 11:06 AM, Jerry Lundstr?m <jerry at opendnssec.org>wrote:

> On Nov 25, 2013, at 16:20 , John Dickinson wrote:
>
> > I have been playing with the clang static analyzer. (
> http://clang-analyzer.llvm.org/)
> >
> > FYI - I ran it like this (On ubuntu 13.10)
>
>
> Nice, think I looked at this a year ago and you could only run it on OS X.
>
>
I have fixed the SoftHSM issue:
https://github.com/opendnssec/SoftHSMv1/pull/6

I used the packaged version of clang (3.0-6ubuntu3) on Ubuntu 12.04. That
version does however have some bugs/flaws compared to the one used by John.
See comment in the pull request.

// Rickard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140129/90366b48/attachment.htm>

From jakob at kirei.se  Wed Jan 29 21:38:06 2014
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 29 Jan 2014 22:38:06 +0100
Subject: [Opendnssec-develop] static analyzer
In-Reply-To: <CAKFiofk7ds84DVk3Eczi1_=Fn72SCoqxHQ-+u_bhVTxSF5rYpA@mail.gmail.com>
References: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>
	<92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>
	<34E1D1F9-C0E7-4F6A-BC19-FAFD4289E9E5@sinodun.com>
	<7493205A-876C-4A25-90EA-543F601BCC79@opendnssec.org>
	<CAKFiofk7ds84DVk3Eczi1_=Fn72SCoqxHQ-+u_bhVTxSF5rYpA@mail.gmail.com>
Message-ID: <E8230BBD-FBA4-463A-816B-A3A4D792C1D8@kirei.se>

On 29 jan 2014, at 15:48, Rickard Bellgrim <rickard at opendnssec.org> wrote:

> I have fixed the SoftHSM issue:
> https://github.com/opendnssec/SoftHSMv1/pull/6

merged.

	jakob



From rickard at opendnssec.org  Thu Jan 30 08:56:51 2014
From: rickard at opendnssec.org (Rickard Bellgrim)
Date: Thu, 30 Jan 2014 09:56:51 +0100
Subject: [Opendnssec-develop] RE: Move to git
In-Reply-To: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
References: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
Message-ID: <CAKFiofktJCT+veg+Q4EqcxG-F4dfLtecrC9SQUT7mTVu63jOuA@mail.gmail.com>

Hi

https://wiki.opendnssec.org/display/OpenDNSSEC/Git


I am getting those merge commits that you do not like, when following the
instructions. How should you avoid them?

// Rickard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140130/6d0c94b2/attachment.htm>

From rickard at opendnssec.org  Thu Jan 30 09:01:19 2014
From: rickard at opendnssec.org (Rickard Bellgrim)
Date: Thu, 30 Jan 2014 10:01:19 +0100
Subject: [Opendnssec-develop] RE: Move to git
In-Reply-To: <CAKFiofktJCT+veg+Q4EqcxG-F4dfLtecrC9SQUT7mTVu63jOuA@mail.gmail.com>
References: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
	<CAKFiofktJCT+veg+Q4EqcxG-F4dfLtecrC9SQUT7mTVu63jOuA@mail.gmail.com>
Message-ID: <CAKFiofnpMgNsxXQtx4ZAp9hjxv+hQvUFroWPNHzHSBqVdt=dPA@mail.gmail.com>

On Thu, Jan 30, 2014 at 9:56 AM, Rickard Bellgrim <rickard at opendnssec.org>wrote:

> Hi
>
> https://wiki.opendnssec.org/display/OpenDNSSEC/Git
>
>
> I am getting those merge commits that you do not like, when following the
> instructions. How should you avoid them?
>

Are you using this?

git config --global branch.autosetuprebase always

// Rickard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140130/de3cf639/attachment.htm>

From jerry at opendnssec.org  Thu Jan 30 10:02:28 2014
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 30 Jan 2014 11:02:28 +0100
Subject: [Opendnssec-develop] RE: Team meeting - Thursday 30 Jan @ 14:00
	CET
In-Reply-To: <05BE6CB8-C8EB-48FE-A560-29EC0A5CAD16@sinodun.com>
References: <05BE6CB8-C8EB-48FE-A560-29EC0A5CAD16@sinodun.com>
Message-ID: <851418299390145836@unknownmsgid>

Home sick, wont attend

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

On 29 jan 2014, at 15:17, Sara Dickinson <sara at sinodun.com> wrote:

Hi All,

We have a team tomorrow (Thursday):

Date:      Thursday 30 Jan 2014
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00
UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-30+Agenda

Sara.

_______________________________________________
Opendnssec-develop mailing list
Opendnssec-develop at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140130/0b901e26/attachment.htm>

From sara at sinodun.com  Thu Jan 30 14:12:08 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 30 Jan 2014 14:12:08 +0000
Subject: Fwd: [Opendnssec-develop] Team meeting - Thursday 30 Jan @ 14:00 CET
References: <05BE6CB8-C8EB-48FE-A560-29EC0A5CAD16@sinodun.com>
Message-ID: <5B13C7AC-BF6C-4BE5-A87F-9C17A2F7736B@sinodun.com>

Hi All, 

The minutes from the meeting today are available for review:

https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-30+Minutes

The next meeting is schedule for:

Date:      Friday 14 Feb 2014
Time:      11:00-12:00 CET, 10:00-11:00 GMT, 18:00-19:00 CST, 10:00-11:00 UTC

Please note the change of day and time compared to our normal meetings. 

Regards

Sara.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenDNSSEC team meeting.ics
Type: text/calendar
Size: 715 bytes
Desc: not available
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140130/a3672a72/attachment.bin>
-------------- next part --------------


Begin forwarded message:

> From: Sara Dickinson <sara at sinodun.com>
> Subject: [Opendnssec-develop] RE: Team meeting - Thursday 30 Jan @ 14:00 CET
> Date: 29 January 2014 14:20:08 GMT
> To: Opd Dev <Opendnssec-develop at lists.opendnssec.org>
> 
> Hi All, 
> 
> We have a team tomorrow (Thursday):
> 
> Date:      Thursday 30 Jan 2014
> Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
> Method:  Teamspeak
> Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2014-01-30+Agenda
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop


From yuri at nlnetlabs.nl  Fri Jan 31 12:56:33 2014
From: yuri at nlnetlabs.nl (Yuri Schaeffer)
Date: Fri, 31 Jan 2014 13:56:33 +0100
Subject: [Opendnssec-develop] RE: Move to git
In-Reply-To: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
References: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
Message-ID: <52EB9D81.6020306@nlnetlabs.nl>

> a great start is just to clone, make a branch, commit stuff and
> create a pull request.

Ok, I've played around a bit.

Some assertions:
- I should do all pull requests from my feature branch and keep it
around until it is successfully pulled.
- I should NOT do pull requests from my develop branch because requests
are on branches, not commits.
- After I finish a feature branch. I can/should merge it in to my
develop branch. I need not wait for the commit to be in the remote
develop branch, because git can uniquely identify commits.

Now, the thing I'm fussy on is the need for rebasing. I think I get what
it does (it falsifies history by changing the time of branching?) but I
don't know why we need it.

An other observation. I expected opendnssec-workflow-test/develop to by
enforcerNG branch (current svn trunk), but it is not.

//Yuri

-- 
Composed on an actual keyboard: all typos genuine.


From sara at sinodun.com  Fri Jan 31 15:00:50 2014
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 31 Jan 2014 15:00:50 +0000
Subject: [Opendnssec-develop] Re: Move to git
In-Reply-To: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
References: <ADA2F126-D828-4572-B761-F48AE4FEB8CD@sinodun.com>
Message-ID: <AC8478A9-FBF3-4C70-9BA2-C7CCE253F756@sinodun.com>

Hi All,

As agreed in the team meeting yesterday the target date for moving the OpenDNSSEC repo to git is Friday 14th February. 

Please test the workflow before then raise any questions, concerns or gotchas on the list. 

Sara. 


On 22 Jan 2014, at 13:26, Sara Dickinson <sara at sinodun.com> wrote:

> All, 
> 
> Please try to make some time to test out the opendnssec test git repo at:
> 
> https://github.com/opendnssec/opendnssec-workflow-test
> 
> The full workflow instructions are here:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Git
> 
> but a great start is just to clone, make a branch, commit stuff and create a pull request. Then Jerry will do his stuff with the pull request and you can wash, rinse, repeat :-)
> 
> We need feedback to move forward with this project - up to now only Jakob and Jerry have been testing it out so please start playing!
> 
> **Important: if you haven?t done so already, please create a GitHub account and send your username to Jakob. You can?t join the git party without this ;-)
> 
> Sara.