[Greasemonkey] Greasemonkeyed.com, userscript.org, forums, source code, and the future of our community

[Jeremy Dunck]

On 8/2/05, Britt Selvitelle <anotherbritt at gmail.com> wrote:
> On 8/2/05, Alex Thomson <abthomson at gmail.com> wrote:
> > I had assumed a regular, centralized, versioning system would work
> > fine too, especially since the alternative seems to be a home-brewed
> > system that would (and do correct me if I'm wrong) probably not be
> > distributed either.  Store everything but the code in the main db and
> > use subversion (or an alternative) to store the code revisions and to
> > provide diffs and branches.
> 
> What jesse and I had discussed previously was simply storing script
> revisions in the database, and then displaying diff's via a little
> ruby magic in the html. For a good example of how this would work,
> check out http://instiki.org.

How will you handle branches?  Records have prior_script_id?  I took a
look around for ruby bindings to subversion, and didn't find anything
immediately useful.  You can of course compile from SWIG or use Ruby
DL, but I was hoping for a gem.  ;-)  So, it's probably more expedient
to do a schema that supports branching, but be aware that as we add
features, we'll reinvent source control within the relational DB...

> One of the big reasons is that we need to store additional information
> about each revision, such as whether or not it's trusted.

Storing everything -but- the source code in the DB would allow for
this, wouldn't it?

Still, you have the issue of queryable branches.  I want to see the
history of script X.  How do I do that?