[bind10-dev] [sprint planning] tentative results + discussion for estimates for sprint ending 2013-something

[Michal 'vorner' Vaner]

Hello

On Mon, Dec 17, 2012 at 11:41:21AM +0100, Jelte Jansen wrote:
> #2552 (log output has two spaces after INFO):
> This is currently kind of intended behaviour; the format we set
> explicitely makes this happen (not just INFO, WARN as well). It is
> easy to change, but the question is, is easier output for split/cut
> more important than aligning the output?

We could come up with names that are of the same length, possibly?

> #2538 (Explain the format and purpose of ZoneTableSegment::create
> config parameter):
> Most estimates are 2/3 but one is 8; from the ticket I gather that
> this is just a bit of API documentation, are we wrong?

Yes, it is to be explained, but also possibly discussed, because personally (as
described in the ticket), I don't think that parameter makes much sense.

> #2279 (requirements for configuration framework improvements):
> Estimates range from 3 to 13. It is 'just' requirements, but we should
> probably make it around 8 anyway, as these can be tricky to get right
> (And should have quite a bit of discussion)

Agreed. It is one of the core systems of bind10 and it doesn't work. No matter
how many hack we gather around it, it'll always do funny things until we fix
this.

> #2073 (unified way to define zones with attributes):
> This probably needs a more specific ideas or proposals, and may be
> related to the config framework requirements (in the sense that those
> may offer some support for config abstraction).

Yes. And, also, we may want to unify it together with things like TSIG keys and
data sources and things like that. I've seen a proposal somewhere (in jabber,
possibly) to have a top-level /dns and put all these things there. It makes some
sense.

But also, I was wondering about something KDE uses for their menus. The menu is
described by some kind of xml and they can mark „Put any additional things here“
in the top-level one. Then, a plugin can come and say „Take the „Settings“ menu
and plug these items in there somewhere. They do it by some XML merging, but
these details are not very important. What I would like is being able for one
module to place some items somewhere deeper, not just at top level. Also it
would be nice to have all the things like offline configuration, etc, etc. But
that seems like another project year ‒ so I think these requirements may take
longer than just few minutes (even if we want to decide we don't have time for
it so we don't want to include all these things).

With regards

-- 
All flame and insults will go to /dev/null (if they fit)

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121217/ba882a00/attachment.bin>