Well...glad to here you are keeping busy.
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
>
> It's true that I've begun to transition vtcl to sourceforge. The 1.2 and
1.3 CVS trees have been
> imported. What's there is the most current stuff I have. I would also
like
> to transition the web site, mailing list and bug tracking facility. Since
> I haven't had a lot of contiguous time to devote it's taking longer than
> expected.
Can you put the faq that Joao sent into the doc section of the cvs tree?
> Over the last 2 years I've received a very low volume of patches. I
cannot
> judge from this the fluency of the vtcl user base as candidates for
active
> maintenance (update access to CVS). This and just a complete lack of time
> have been the biggest barriers to ongoing development.
Perhaps you can post something on any of the tcl/tk related newsgroups or
mailing lists (if such things exist - I'm afraid this is as far as I read on
the tcl/tk front) for those interested in maintaining it.
> It's true that I
> had much larger plans for vtcl than I ever got around to building. It's
> still my hope to get there (or somewhere like it) someday whether or not
> it's me who does the maintenance. Moving the site and source base to
> sourceforge guarantees that it can be maintained in my absence.
Do you think (I am not familiar with the sourceforge feature, but) that with
the Survey section a wish list could be included or would that be better in
the forum..or the bug tracking (say it's a bug in that the feature is
missing and doesn't get closed until the desired feature is included)
Perhaps in the forum and/or here, you could indicate your wish list also to
have some kind of ideas of the direction you were hopiong the project would
move towards. Fabien Coutant seem to have a nice todo/wish list started
already. Perhaps you could indicate you plans (if you have any more that
aren't already there) in the TODO
Since I am not familiar specifically with the bugs listed in the TODO...do
you think you can add these bugs to the bug tracking, in addition to those
you mentioned here? Or is they identifiable in the mailing list archives?
> I would be interested to hear your thoughts on how to select maintainers
> (no more than two) for vtcl. It may be obvious to those who track the
list
> in which case nominations are in order (or nominate yourself).
I think probable the best bet is to initially either have people send you
patches and update it yourself, minimizing who has access...(until you find
a co/replacement maintainer) but this can causes you extra work to validate
patches (unless you accept on faith - which seems a little risky)..
..or find a co maintainer to do that job..
..or give multiple people access (who have given patches or shown interest
in maintaining it) with an occasional change review, and accept or deny as
necessary, with denied ones being removed (but this might cause some
confusion).
..for criteria for picking...
(1) have they sent you patches
(2) do they post regularly on the mailing list?
(3) do they have free time to work on it?
(4) are they currently using vtcl on a regular basis?
(5) Are they using vtcl on an existing program?
(6) are they working or have they worked on any similar development (any
open source projects)?
> A word or two on the 1.3 source base. As it stands, 1.3 runs and saves
> but cannot re-load a project it has saved. I began to change the file
> format to something more modular. The UI has changed significantly. I was
> working on a tabbed panel for preferences and pluggable icon/widget bars.
> Do not use 1.3 unless you want to a) kick the tires or b) write code to
> fix it. Option 'b' will require a bit of investment to understand the
code.
> My apologies that is it not better commented.
Perhaps we should make sure the docs re-emphasize the (major.minor version
numbers with minor numbers being odd implies beta/development) - if they
don't already.
> Stewart
> On Mon, 20 Mar 2000, Eric Bresie wrote:
>
> > I was just noticing this...
> >
> > http://sourceforge.net/project/?group_id=285
Can we include this reference in the mailing list tail to access this site
instead of yours?
Eric Bresie
---------------------------------------------------------------------------
To unsubscribe from the Visual Tcl mailing list, please send a message
to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the
message body (where [EMAIL PROTECTED] is your e-mail address).
