[csw-maintainers] ITP: opencsw-policy

[Maciej (Matchek) Blizinski]

No dia 31 de Dezembro de 2010 19:53, Ben Walton <bwalton at opencsw.org> escreveu:
> Can I suggest that we not (necessarily) use subversion to handle the
> the VCS needs of this though?  Git offers a 'notes' feature that would
> be quite useful for something like this, I think.  The commit message
> can describe the change that is made and then the change can be
> annotated with a note that references the mailing list thread that
> spurred the change.  It's meta-info about the commit.

Swinging Ockham's razor, I'd think twice before I created any new
source repositories.  I'm already tempted to create new repositories
(for gar, for checkpkg), but I've been curbing these temptations.  If
we decide that we need a new source repository, it will probably be
git, unless there's a specific reason to use another VCS.  If you
create a new VCS, you need to make sure that it'll be reliable,
access-controlled, backed up and integrated with the rest of our
infrastructure.

> I like this idea a lot.  While a package as the final output is
> certainly nice, it's pretty heavy-weight.  Do you envision the
> packaged files as the set of files that the website would display, or
> just something that anyone could fetch to peruse?

Both.  The package would be installed on our web zone and would be
served straight from these files.  Updating the live pages would be
done by upgrading the package.  At the same time, people who work on
the plane or behind a slow connection, would have a handy local
reference.  Including markup sources in the package would also
encourage people to edit them and submit patches.

> At work, we share a git repository of our docbook formatted system
> procedures and docs, etc.  On a push to the central repository, we
> validate the xml and if it passes, automatically publish the changes
> to a website where we reference it from.

That's a nice system.  In our case, people would still be able to pull
directly from the source code repository, and there will always be
easy network access to the newest version.  However, once this is
done, adding a script to transform sources and making a package is no
big deal.