Hi,

I would like to see tiddlywiki moved to github.  However I have two
(well three) major concers:

--  What happens to the contributor code?  Chris indicated that
contributors can move their code as they wish.  For me that means some
will move, some will stay, and some may move elsewhere.
I think this contributes to the fragmentation of tiddlywiki even
more.  I often have difficulty locating plugins, but if also the
contributors archive from trac/svn diffuse, how am I able to find
components back?  If on github there are a lot of tiddlywiki
repositories, how do I know about them?  And how do I know which
dependencies I need to build a specific vertical?  I am really not
keen on fragmentation of the repository!

-- Lost history.  I think just moving to github without history is a
tremendous waste of knowledge and effort.  I can see two relatively
easy solutions:  1) Import history with svn2git and just continue with
development (my preference).  2) Ditch history, keep trac/svn online
AND start on github with a new MAJOR version of tiddlywiki.  Then it
is very clear for humans that a break in the source happened.

-- trac tickets etc.  Just loosing them would be a waste of work.
Unfortunately I don't know about a good, distributed ticket tracker
for git.  I think minimally the trac infomation needs to be mirrored
read-only into a git repository.  then it can be searched, and old
tickets can be referenced from a new ticket system.  Just keeping the
old trac system running is inferior I think because once it will stop
and the tickets are lost.  An option may be http://fossil-scm.org/ .
This has a distributed ticket tracker, and could even replace git.

yours,
Vlak

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Reply via email to