Gabe and I have started work on a next generation version of the
Automated IP Log tool [1]. The new version is intended to ship as an
Eclipse plug-in.
With the new version running inside the Eclipse workbench, the developer
can decide where to store the log file: either somewhere on the project
website or elsewhere in CVS. The IP Log tool itself doesn't have to be
concerned with the issues of security (who gets to work on the log) as
that will be taken care of by the write access to CVS/SVN. By
encouraging (i.e. forcing) the user to explicitly store the IP Log, we
should mitigate the problem of IP Logs that go missing after approval.
It will also give us the ability to truly lock down an IP Log (the
automated IP Log always reflects the current reality which changes with
time).
So, no more automated generation - we've gone back to the old-school way
of manually maintaining a .csv file... but with better tooling than a
text file editor?
Thoughts?
Don't give people a choice where to store the logs. It should be a
standard location so it'll be easier to find and audit them. Since
you're providing web API to publish changes, why not store the
information in a sql database? Then all the committers will need is read
and write access to the db based on their LDAP credentials. Or is having
it in CVS better so that there are snapshots / slices in time for every
change? (Or... why not go wiki, which provides BOTH a database and
change history?)
+1 for a new Dash subproject. But only if Athena gets provisioned too. :P
https://bugs.eclipse.org/bugs/show_bug.cgi?id=275529 (waiting 2 months
to the day since I answered your last question)
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
