VMD-L Mailing List
From: Josh Vermaas (vermaas2_at_illinois.edu)
Date: Wed Jul 09 2014 - 13:33:15 CDT
- Next message: John Stone: "Re: VMD 1.9.2a39_64 segmentation fault MacOS"
- Previous message: Axel Kohlmeyer: "Re: How to contribute to VMD?"
- In reply to: Vlastimil Zíma: "Re: How to contribute to VMD?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To be fair, very few people have commit privileges to the CVS, so there
aren't any benefits to using git or mercurial. cvs checkout and cvs
update are pretty much the only commands I ever use when keeping up with
VMD source, and if I have changes I'd like to see in VMD, I write them
up and go through the usual channels (vmd_at_ks.uiuc.edu). For small things
(Angstrom was misspelled once), the fixes are pretty much immediate, but
for new features, it can take a month or two for additions to make it
through quality/utility control to make sure it doesn't break anything
and that someone other than me might possibly find it useful.
-Josh Vermaas
On 7/9/14, 1:29 PM, Vlastimil Zíma wrote:
> Hi Axel,
>
> I have no intentions of (re-)distributing the source code of VMD, but
> I'm not into learning CVS. I believe it's understandable since last
> version was released in 2008.
>
> Anyway, thanks for your answers.
>
> Vlastik
>
> 2014-07-09 17:15 GMT+02:00 Axel Kohlmeyer <akohlmey_at_gmail.com
> <mailto:akohlmey_at_gmail.com>>:
>
> On Wed, Jul 9, 2014 at 7:35 AM, Vlastimil Zíma
> <zima_at_karlov.mff.cuni.cz <mailto:zima_at_karlov.mff.cuni.cz>> wrote:
> > Hi all,
> >
> > does anybody know how to contribute to VMD? I have found several
> minor bugs
> > in last years, but I never report them since I never find out
> how to do so.
> > I haven't found any document about contribution other than
> sparse notes in
> > FAQ.
> >
> > I'd like to know
> > * How do I find if bug was already reported?
>
> near impossible.
>
> > * How to report bug?
>
> send a bug report to vmd_at_ks.uiuc.edu <mailto:vmd_at_ks.uiuc.edu>
>
> > * How to check that my fix didn't break anything else? Are
> there any tests
> > available?
>
> depends on what kind of fix this is.
>
> > * How to share a patch?
>
> send an e-mail to vmd_at_ks.uiuc.edu <mailto:vmd_at_ks.uiuc.edu>
>
> > * Is there any official repository with VMD source code in git
> or other
> > modern VCS?
>
> VMD is (still) managed in CVS repository. a read-only version of that
> is available. please note the licensing conditions of VMD, which put
> restrictions on how the sources can be "exported".
>
> axel.
>
> > Thanks in advance
> > Vlastik
>
>
>
> --
> Dr. Axel Kohlmeyer akohlmey_at_gmail.com <mailto:akohlmey_at_gmail.com>
> http://goo.gl/1wk0
> College of Science & Technology, Temple University, Philadelphia
> PA, USA
> International Centre for Theoretical Physics, Trieste. Italy.
>
>
- Next message: John Stone: "Re: VMD 1.9.2a39_64 segmentation fault MacOS"
- Previous message: Axel Kohlmeyer: "Re: How to contribute to VMD?"
- In reply to: Vlastimil Zíma: "Re: How to contribute to VMD?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]