Sylvain Beucler <b...@gnu.org>:
> > You might want to contact him directly. He did setup a new git
> > repository for the Savane code and started to work on that:
> > <http://savannah.nongnu.org/projects/savane-cleanup>
>
> Yes. I added links to the 2 repositories (the code that Savannah runs
> on, and the Python/Django rewrite).
I've lost some context. Links from where? That is, what page am I
supposed to be looking at to learn about these projects?
> > > I seem to be unnable to commit. I checked out source in the usual way,
> >
> > That's because you're not a member of the "savane" group on Gna!.
>
> Actually I introduced a bug when moving subversion.gna.org to a
> separate VServer, namely the absence of membership replication. This
> is fixed now.
Thank you, I will do another chekout and test my commit ability.
Note, however, that I am postponining serious work on Savane internals becaue
there is something else I think I should do first - that is, write a
data-extraction tool that will work on a variety of forges, including Savane.
I have already written code that extracts the tracker state of all
bugs, features, and patches associated with a given project from
Berlios. I am working on a similar capability for Savane. I plan to do
likewise for at least one more forge type, release the result, and
start up a project that will evolve this demonstration code into a
very general tool for extracting state from forges. (I plan to
extract more than just tracker state, that's just te obvious first
target.)
That tool will solve the export problem, and it will give me a good
start on defining a standard forge interchange format. Once it is functional,
I may very well come back to Savane and write an importer.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Savane-dev mailing list
Savane-dev@gna.org
https://mail.gna.org/listinfo/savane-dev
