I was just noticing this...

http://sourceforge.net/project/?group_id=285

It seems like the cvs tree that's on there has a lot of 1.2 code imported,
however I am curious if any changes that may have been made on this one
differ from the 1.3 code?

Also..can we move the FAQ as part of the sourceforge.net cvs tree? perhaps
in the docs?  Then we can hopefully track it a little better.  And also have
it associated with a specific version also.

Stewart is the Project Administrator (is he still working on this or should
we have someone else take over).  To be a developer you apparently have to
contact Stewart.  As a developer you can have access via ssh cvs access.

I am not real familar with how sourceforge works...(but I am looking at
it)..This looks like a good place to put things though, with a message
forum, bug tracking, etc.

Althought it seems like we might want to see about getting this mailing list
included in the mailing list portion and/or moved over their.  And maybe
also move the home page their also.

Eric Bresie

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Joao Cardoso
> Sent: Friday, March 17, 2000 12:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [vtcl] anything new since 1.2.0?
>
>
> Uwe Koloska wrote:
> >
> > You wrote on Mit, 15 M�r 2000:
> ...
> >   a FAQ maintainer was there -- is he still involved?
>
> Not really. The FAQ hasn't been updated for centuries.
>
> Most of the FAQs in the mailing list are really tcl/tk ones, and for
> that that are excelent tcl/tk FAQs.
>
> Also, and nonelethess of the 'robots.txt' file the FAQ page is acessed
> from robots, and that is ruining my budget... I would be happy if
> someone hosted it. Perhaps vtcl.sourceforge.net?

> Joao Cardoso, [EMAIL PROTECTED]

---------------------------------------------------------------------------
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).

Reply via email to