[Simulavr-devel] Undo the fork ...

[ThomasK]

Hi @all,

sorry, that I answer late, but I had much to think about it. And I don't 
want to reopen all the discussions from last days. I think, Onno wrote 
about his and my point of view and so I havn't to write it again.

I can read in last postings (I hope, that I'm not mistaken) that we 
agree to continue in working on simulavr and not to continue our fork. 
That wasn't our plan originally. We decided to fork to stop with that 
unlucky situation, that we had. Ok, this fork will not live longer, if 
we have a agreement here. Maybe this was necessary to push a solution, 
maybe not ...

So, I will continue next days with the following steps:

- create GIT repo. I'm sure, that this is a good choice. (and I hope, 
that this isn't too painfull for you, Michael!) "Old" CVS repo will stay 
untouched. If it is possible, we could set it to read-only (I havn't 
looked on admin permissions page, so I'm not sure, if this is possible)

- upload the master branch from our current GIT repo state as starting 
point, I revert the name-change from simulavr to avrs. One question for 
that step is, what version should I set, in the moment we have set in 
our fork "0.10rc1", but I'm not fixed on that. Proposals welcome!

- one task should we do next time (next means next weeks, not years!): 
make a release - content: documentation, tarball, maybe bin-package, 
maybe deb-package (for ubuntu this should not be a problem for me), 
maybe windows-package (I could make it, I have sometimes access to a 
windows box)

- in our fork we have marked TCL interface deprecated! In the current 
state it looks awful (hi Petr, I agree with you for gitk and this is the 
same, I think ;-) ) and we have nobody to maintain it! If anybody out 
there, which wants to maintain it, then I agree to hold it!

- work on web page. We started in our fork to make documentation with 
Sphinx (documentation tool developed for python documentation, but not 
only for python), this creates both html and pdf documentation (if 
somebody want to see a ROUGH preview of pdf, write me) And this tool can 
also be used to generate web page (as you can see on 
http://avrs.sourceforge.net!) In a first step I would "translate" 
current web page to this system. The (unsolved) question for this is: 
where to store the sources? It would be possible to store it too in GIT 
repo. Case a) in a special branch, which is independend from other 
sources or case b) also in normal source tree (in this case we had the 
possibility to share doc source files between web page and simulavr 
docu!) Case c) would be to store it too in Web-CVS repo, but here it 
would be possible to have access to source files, scripts, config and so 
one by normal HTTP access - it depends on how Savannah copies files from 
CVS to web page tree, there is no description available, how this works!

This is MY imagination, how to proceed! Proposals welcome! (especially 
for content of web page, we HAVE to show, that simulavr isn't dead, what 
we plan to make, that we invite anybody to work on it - and how!)

And, if anybody want to tell: "he act's like a king, he want to tell 
everybody, what to do or not!" No, I don't want! But sometimes it's 
necessary to make clear and hard statements to make a development. If 
somebody else wants to do the job - no problem, lets go! But: go! ;-)

cu, Thomas