Proposing k5wiki.kerberos.org for review and eventual adoption

Sam Hartman hartmans at MIT.EDU
Fri Nov 23 00:11:50 EST 2007



A day before the Kerberos Consortium launch, the staff at MIT and some
folks from Secure Endpoints get together to discuss how we can work
together.  Part of that discussion revolved around opening up the MIT
Kerberos development process and creating transparency and openness to
anyone who is willing to dedicate significant time contributing to the
project.

I took away an action item from that meeting to propose a set of
policies and guidelines as well as mechanisms for doing a better job
of tracking what we're doing.
I said I'd probably make that proposal in a form of a wiki.

I've done so.  I'd like to draw your attention to
http://k5wiki.kerberos.org/ .  This WIKI is not a general wiki for
Kerberos; it is a WIKI for development of MIT Kerberos.  We may also
need a general Kerberos WIKI.  We may hate the fact that I called this
wiki k5wiki.

I believe that the description of how projects and release pullups are
handled and how we plan to resolve disputes described there are
consistent with those two days of meetings.

I also believe I have put enough content into the wiki to propose layouts and ways we can expand what we're working on.

The one policy that we did discuss somewhat and that is missing is a
release planning policy.  We discussed some of what we want from such
a policy.  I didn't make a stab at it partially because I'm not
entirely sure that we're done thinking through that part and partly
because I'd already spent my entire thanks giving vacation working on
this.


There's a long todo list.  I think the content that is there is good,
but there is a lot I didn't get to.

Currently, anyone who confirms their email address can edit the wiki.
I expect we will get spam sooner or later from this.  When we do I
plan to move to a mode where anyone with an existing account can
create accounts for others.
That's probably sufficient for this purpose.
Anyone with an account can edit.

I'd like to ask the community to consider whether this is the right
direction and whether we want to adopt this wiki and the policies
contained there.

If there are specific problems that you believe you know how to fix,
then go for it and fix them.  If there are specific problems you'd
like to document then document them either on this list or the
appropriate talk page.



Thanks for your consideration,

Sam Hartman
Chief Technologist
MIT Kerberos Consortium



More information about the krbdev mailing list