Re: [Ottoproject-devel] Planning

[Bruno C. <br...@wh...>]

  TJ> For release policies, do we want the "release early, release
  TJ> often" approach, where we basicially release everything we have
  TJ> now (don't know how many would download it, or where we'd
  TJ> announce it [I just registered ottoproject on freshmeat.net]),
  TJ> or we could have semi-definite roadmaps for each release.

I'm personally not a fan of the "new release every two weeks"
approach, and would rather just have real release schedules.  Just my
opinion, of course.

Speaking of where to announce, who would download, etc -- we probably
should start thinking of some evangelistic outlets to get people clued
into and interested in Otto.  Publishing is one easy way to accomplish
this, but we need at least one semi-solid release first, IMO.  Maybe
posting to some relevant lists would be helpful (not sure what those
would be)... but maybe having at least an initial release first is a
pre-requisite so people would have something to actually check out?

I'm a quasi-regular on the mod_perl list (which actually has a decent
amount of intelligent, clued regulars) which might be a decent place
to gauge others interest in Otto.

  TJ> The things, as I see them, that would probably be required for a
  TJ> first release:

  TJ>   - migration to Postgres and/or MySQL for the db backend stuff
  TJ>   - writing of installer scripts and/or instructions (RPMs?) for
  TJ>     installation
  TJ>   - basic usage docs/User Guide/Tutorials
  TJ>   - User ACLs
  TJ>   - fully breaking the Agent registration step out of the
  TJ>     Inventory module

Yep, all of the above are important.  There are quite a few things I'd
like to do with regard to the registration/inventory separation
pieces, but I'll wait until we have a bugzilla instance going again to
get discussion started on that -- or do we want to try and use the
sourceforge bug tracking system?

The things I see as the most important for an initial release (in no
particular order): migration away from Oracle (or support for an RDBMS
in addition to Oracle), Inventory/registration separation and
docs/guides/etc.

RE: packaging, I think there's a lot to talk about there as well.  I'm
somewhat envisioning a make-maker (typical Perl style release,
Makefile.PL, etc) and then some instructions for putting the other
pieces together (how to get an Apache instance ready, libraries
required, etc, etc).  ...not sure what you guys think, if you'd rather
try and take an autoconf route (would make sense if we eventually get
some non-Perl pieces in the core distribution), etc, etc.

  TJ> Other infrastructure stuff we'll probably want/need:
  [...]

Yes, we should get ottoproject.org.  Who wants to register it?  apogee
(ns{1,2}.whack.org) could happily do DNS for it (and even more if
necessary).

b.
--
/*  Bruno Connelly, <br...@wh...>  */