On Mon, 31 Jan 2011, Eric Shulman wrote:
There are tickets in the Trac system that have been repeatedly re-
scheduled to "sometime in a future release", usually as a result of
some short-term priorities at Osmosoft. This doesn't mean they aren't
important or 'actionable', just that there were other items that were
deemed, at the time, to be more immediately in need of attention.
I've seen this phrase "short-term priorities at Osmosoft" bounced
around this thread a few times. The implication is that Osmosoft is
making all the core decisions and core commits.
Since that is considered a problem let me restate one of the reasons
for a move to github:
Make it possible for the at large community surrounding TiddlyWiki
to make patches and other contributions to the core.
Once it happens Eric gets to choose which core code he contributes and
which pull requests he makes.
My concern is that, given how poorly people *currently* use the
information in Trac, I think they are unlikely to suddenly become more
rigorous in checking that information when it is not integrated into
the new ticket system.
I agree. I don't think saving the data will change that in any way.
Thus my desire for a reboot. There are bad habits and biases ingrained
in the current systems.
As I previously posted, I feel *very* strongly that the existing
tickets should be migrated into the new system (as *read-only*
information) so that the old ticket information is easily searchable
without having to search on two separate systems.
Have you done any research to see what tools are available to make
this possible?
--
Chris Dent http://burningchrome.com/
[...]
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywikidev?hl=en.
