Hi all.
I noticed that in most plugins there is no separate licence file, and in many
there
is no licence whatsoever.
I think this should be a requirement for accepting a plugin on the repo, and
should
ask authors to fix this.
Any objection about establishing a standard way to add it (e.g.
Great, Ii assume this solves the problem
Victor,
Will we have a new version of the Sextante plugin soon or do we have
to apply the patch ourselves?
Agus
On Fri, Oct 19, 2012 at 3:12 PM, Victor Olaya vola...@gmail.com wrote:
Thanks!
2012/10/19 rldhont rldh...@gmail.com:
Hi Victor,
Ticket
Il 20/10/2012 14:17, Agustin Lobo ha scritto:
Great, Ii assume this solves the problem
Victor,
Will we have a new version of the Sextante plugin soon or do we have
to apply the patch ourselves?
Hi all.
This is part of the larger problem: how do we set up a core plugin release cycle
Agustin,
There are a few importante changes since last version, but I would
like to close a couple of bugs before releasing a new version. The
patch, I will apply it today and it will be in the github repo.
In short, I guess you can count on a new version in less than a month
(there is not a
i understand the hassle, but from the point of view of R scripts in
Sextante this is not a bug, it is
that Sextante is totally unusable for this purpose. My intention was
to include this Sextante capability
within my (hopefully) forthcoming presentation on geospatial
capabilities of R in a R users
Agustin
2 quick things:
1) I am going to prepare a document with instructions to use the
latest version from git. That might help you and others as well.
2)If you are doing a presentation about SEXTANTE, that puts you in my
list of privileged users :-) That means that you can (and you
should)
Dnia piątek, 19 października 2012 o 19:55:01 Giuseppe Sucameli napisał(a):
Admin or Trusted author?
I'm enough mad to trust him :-) (done!) so he doesn't
need to ask for approval, but I cannot grant him any
admin permission.
If he also needs the admin privileges someone else will
grant
