Hi all.
What is the currently recommended method for downloading the source: the
old cvs or the new svn? I assumed svn, but on
http://grass.itc.it/download/index.php the first method appears still
the cvs.
We'll be grateful of a clarification.
All the best.
pc
--
Paolo Cavallini, see: http://www.faunalia.it/pc
Ciao,
2008/1/7, Paolo Cavallini <cavallini@faunalia.it>:
What is the currently recommended method for downloading the source: the
old cvs or the new svn? I assumed svn, but on
http://grass.itc.it/download/index.php the first method appears still
the cvs.
SVN of course, CVS is dead. Webpages are still not updated completely.
BTW it would be great to start migration webpages to Drupal. AFAIU we
are waiting for LDAP-Drupal synchronization(?).
Martin
We'll be grateful of a clarification.
All the best.
pc
--
Paolo Cavallini, see: http://www.faunalia.it/pc
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *
On Mon, 7 Jan 2008, Martin Landa wrote:
[...]
SVN of course, CVS is dead. Webpages are still not updated completely.
BTW it would be great to start migration webpages to Drupal. AFAIU we
are waiting for LDAP-Drupal synchronization(?).
Would that mean updates to the website would have to be done through a web-based interface? I'm not sure I'm keen on that. When making a change to the website it's good to be able to grep to see where the thing you are changing is mentioned, and change all occurences. But I don't update the website very often (hardly at all), so I guess my extra work isn't a big factor 
Paul
On Jan 7, 2008 11:30 AM, Paul Kelly <paul-grass@stjohnspoint.co.uk> wrote:
On Mon, 7 Jan 2008, Martin Landa wrote:
[...]
> SVN of course, CVS is dead. Webpages are still not updated completely.
> BTW it would be great to start migration webpages to Drupal. AFAIU we
> are waiting for LDAP-Drupal synchronization(?).Would that mean updates to the website would have to be done through a
web-based interface?
Yes.
I'm not sure I'm keen on that. When making a change
to the website it's good to be able to grep to see where the thing you are
changing is mentioned, and change all occurences. But I don't update the
website very often (hardly at all), so I guess my extra work isn't a big
factor
Agreed
Given my 10 years of GRASS Web site experience in which I still hold 90%
of all changes in average (!) I opt for a Web based solution to get more
people involved. The much liked "vim" approach apparently doesn't
scale.
Yet we are waiting to get Drupal enabled (temporarily
http://grass-dev.osgeo.net/).
Markus
Agreed
Given my 10 years of GRASS Web site experience in which I still hold 90%
of all changes in average (!) I opt for a Web based solution to get more
people involved. The much liked "vim" approach apparently doesn't
scale.Yet we are waiting to get Drupal enabled (temporarily
http://grass-dev.osgeo.net/).Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
And why not use Trac's wiki as a GRASS homepage?
--
Bc. Radek Bartoň
Faculty of Information Technology
Brno University of Technology
E-mail: xbarto33@stud.fit.vutbr.cz
Web: http://blackhex.no-ip.org
Jabber: blackhex@jabber.cz
On Jan 7, 2008 5:31 PM, Radek Bartoň <xbarto33@stud.fit.vutbr.cz> wrote:
> Agreed
> Given my 10 years of GRASS Web site experience in which I still hold 90%
> of all changes in average (!) I opt for a Web based solution to get more
> people involved. The much liked "vim" approach apparently doesn't
> scale.
>
> Yet we are waiting to get Drupal enabled (temporarily
> http://grass-dev.osgeo.net/).
>
> MarkusAnd why not use Trac's wiki as a GRASS homepage?
It is not powerful/aesthetically enough to generate a nice Web site for
users. As developers Wiki it is perfect.
Markus
Dne Tuesday 08 of January 2008 09:37:37 Markus Neteler napsal(a):
On Jan 7, 2008 5:31 PM
> And why not use Trac's wiki as a GRASS homepage?It is not powerful/aesthetically enough to generate a nice Web site for
users. As developers Wiki it is perfect.Markus
Ah, that's true. Although it can be styled with CSS and there is a lot of
project's sites [1, 2, 3, 4, ...] which has quite nice layout with Trac over
Web. Hopefully developers add skinning support to Trac soon, there is at
least [5] for now.
[1] - http://trac.alagad.com/Validat/wiki
[2] - http://dev.mootools.net/wiki
[3] - http://code.djangoproject.com/wiki
[4] - http://www.reductivelabs.com/trac/puppet/wiki
[5] - http://trac-hacks.org/wiki/ThemeEnginePlugin
--
Bc. Radek Bartoň
Faculty of Information Technology
Brno University of Technology
E-mail: xbarto33@stud.fit.vutbr.cz
Web: http://blackhex.no-ip.org
Jabber: blackhex@jabber.cz
Martin Landa wrote:
> BTW it would be great to start migration webpages to Drupal. AFAIU
> we are waiting for LDAP-Drupal synchronization(?).
Paul:
Would that mean updates to the website would have to be done through
a web-based interface? I'm not sure I'm keen on that. When making a
change to the website it's good to be able to grep to see where the
thing you are changing is mentioned, and change all occurences.
Before supporting a move to Drupal I would still like to see prototypes
of the GRASS frontpage, download page, and since it's already begun the
screenshots page implemented. How will the final product look?
Markus:
One thing I think is critical is that the changes are monitored in some
sort of SCM with change history including author, date, and commit log
message. Does drupal give access to change history?
Personally I prefer the exactitude of the 'vim' + raw html approach,
and don't like presenting a blog-like page style for a project
homepage. But I look forward to seeing what the Drupal prototype will
look like, or 3rd party examples, and hope my worries can be relieved.
Having said that I am all for lowering barriers to entry to allow more
helpers to contribute. But raw HTML is not very hard, and Markus's nice
CSS setup ensures a consistent and pretty look.
Hamish
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
On Tuesday 15 January 2008, Hamish wrote:
> Martin Landa wrote:
> > BTW it would be great to start migration webpages to Drupal. AFAIU
> > we are waiting for LDAP-Drupal synchronization(?).Paul:
> Would that mean updates to the website would have to be done through
> a web-based interface? I'm not sure I'm keen on that. When making a
> change to the website it's good to be able to grep to see where the
> thing you are changing is mentioned, and change all occurences.
This is an important downside to using a CMS like Drupal. A global find /
replace is not easily implemented by default. It may be possible to add this
functionality through a 3rd party module.
Before supporting a move to Drupal I would still like to see prototypes
of the GRASS frontpage, download page, and since it's already begun the
screenshots page implemented. How will the final product look?Markus:
> http://grass-dev.osgeo.netOne thing I think is critical is that the changes are monitored in some
sort of SCM with change history including author, date, and commit log
message. Does drupal give access to change history?
I think that it is possible to have revisioned edits with Drupal, possibly
after enabling some module.
Personally I prefer the exactitude of the 'vim' + raw html approach,
and don't like presenting a blog-like page style for a project
homepage. But I look forward to seeing what the Drupal prototype will
look like, or 3rd party examples, and hope my worries can be relieved.
Here is an example of a user-powered Drupal site. There are a couple of
add-ons present for pretty-printing code snippets, etc. I would be happy to
comment on any other Drupal related questions.
Having said that I am all for lowering barriers to entry to allow more
helpers to contribute. But raw HTML is not very hard, and Markus's nice
CSS setup ensures a consistent and pretty look.
I felt this way too. Although, now I am starting to like the ability to easily
define a pile of terms which can be used to index / cross-reference / sort
pages on a Drupal site. This allow rapid navigation by concept rather than
static navigation approaches commonly used on web pages.
It would be good to experiment a bit with the new Drupal site, and if it is
not suitable we can always switch to something else.
Cheers,
Dylan
Hamish
___________________________________________________________________________
_________ Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
> > Martin Landa wrote:
> > > BTW it would be great to start migration webpages to Drupal.
Hamish:
> One thing I think is critical is that the changes are monitored in
> some sort of SCM with change history including author, date, and
> commit log message. Does drupal give access to change history?
(Accountability and peer review is needed as the webpage is the
"official voice" of the GRASS project)
Dylan:
I think that it is possible to have revisioned edits with Drupal,
possibly after enabling some module.
...
Here is an example of a user-powered Drupal site. There are a couple
of add-ons present for pretty-printing code snippets, etc. I would be
happy to comment on any other Drupal related questions.
link? ( http://casoilresource.lawr.ucdavis.edu ) ?
....
I felt this way too. Although, now I am starting to like the ability
to easily define a pile of terms which can be used to index /
cross-reference / sort pages on a Drupal site. This allow rapid
navigation by concept rather than static navigation approaches
commonly used on web pages.
I guess the ideal is a good intuitive hierarchical structure with good
index/search/sort tools too- they aren't mutually exclusive. The
ability to limit the search to just the website or just a particular
mailing list would be nice (htDig?)
It would be good to experiment a bit with the new Drupal site, and if
it is not suitable we can always switch to something else.
agreed.
Hamish
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
On Tuesday 15 January 2008, Hamish wrote:
> > > Martin Landa wrote:
> > > > BTW it would be great to start migration webpages to Drupal.Hamish:
> > One thing I think is critical is that the changes are monitored in
> > some sort of SCM with change history including author, date, and
> > commit log message. Does drupal give access to change history?(Accountability and peer review is needed as the webpage is the
"official voice" of the GRASS project)
This is an important point. I am not necessarily advocating the use of Drupal
or any other CMS- rather pointing out that it can provide considerable
administrative convenience.
Dylan:
> I think that it is possible to have revisioned edits with Drupal,
> possibly after enabling some module....
maybe this a module based on:
http://groups.drupal.org/taxonomy/term/2408
???
> Here is an example of a user-powered Drupal site. There are a couple
> of add-ons present for pretty-printing code snippets, etc. I would be
> happy to comment on any other Drupal related questions.link? ( http://casoilresource.lawr.ucdavis.edu ) ?
Damn. I really shouldn't be posting on an empty stomach.
> I felt this way too. Although, now I am starting to like the ability
> to easily define a pile of terms which can be used to index /
> cross-reference / sort pages on a Drupal site. This allow rapid
> navigation by concept rather than static navigation approaches
> commonly used on web pages.I guess the ideal is a good intuitive hierarchical structure with good
index/search/sort tools too- they aren't mutually exclusive. The
ability to limit the search to just the website or just a particular
mailing list would be nice (htDig?)
This is also true. I was thinking about the annoyance of maintaining a
hierarchy manually: especially if categories and such are modified over time.
I had this page in mind (again from my own experiences with Drupal):
http://casoilresource.lawr.ucdavis.edu/drupal/taxonomy_dhtml
Dylan
> It would be good to experiment a bit with the new Drupal site, and if
> it is not suitable we can always switch to something else.agreed.
Hamish
--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
On 16.01.2008 01:18, Hamish wrote:
> Before supporting a move to Drupal I would still like to see prototypes
> of the GRASS frontpage, download page, and since it's already begun the
> screenshots page implemented. How will the final product look?
>
Sounds like a good idea. I'll take care of the galleries.
The thing with Drupal is that we *can* make the pages look *exactly* like they do in our current site, if we want to. But otoh it will be a bit easier to manage say screenshots as galleries, but I guess this is just my opinion.
> Markus:
>> http://grass-dev.osgeo.net
>
> One thing I think is critical is that the changes are monitored in some
> sort of SCM with change history including author, date, and commit log
> message. Does drupal give access to change history?
>
Yes Drupal has change history, and can even show you what has changed. Drupal also has content tracking, and can be set to send an email when new pages are created.
>
> Personally I prefer the exactitude of the 'vim' + raw html approach,
> and don't like presenting a blog-like page style for a project
> homepage. But I look forward to seeing what the Drupal prototype will
> look like, or 3rd party examples, and hope my worries can be relieved.
>
Ah, but in Drupal you can still make pages in raw html, or rather xhtml, which the template is coded in. In addition to that there is support for Wiki-like syntax, bbcode and even wysiwyg editors.
>
> Having said that I am all for lowering barriers to entry to allow more
> helpers to contribute. But raw HTML is not very hard, and Markus's nice
> CSS setup ensures a consistent and pretty look.
>
Well that is what Drupal does too.
--Wolf
--
<:3 )---- Wolf Bergenheim ----( 8:>
On 16.01.2008 03:34, Dylan Beaudette wrote:
On Tuesday 15 January 2008, Hamish wrote:
Martin Landa wrote:
BTW it would be great to start migration webpages to Drupal.
Hamish:
One thing I think is critical is that the changes are monitored in
some sort of SCM with change history including author, date, and
commit log message. Does drupal give access to change history?(Accountability and peer review is needed as the webpage is the
"official voice" of the GRASS project)This is an important point. I am not necessarily advocating the use of Drupal or any other CMS- rather pointing out that it can provide considerable administrative convenience.
Dylan:
I think that it is possible to have revisioned edits with Drupal,
possibly after enabling some module....
On the test site I have enabled the diff module (http://drupal.org/project/diff) which will show you the diff between two versions. There is also the Recent Changes module (http://drupal.org/project/recent_changes) installed.
Also drupal saves who made a page edit, and that can also be made visible.
maybe this a module based on:
http://groups.drupal.org/taxonomy/term/2408
This is for accessing a version control repository trough Drupal, a bit like webVC.
Don't be afraid of the new installation, just go in there and get your hands dirty! Send me an email if you need / want editing rights.
--Wolf
--
<:3 )---- Wolf Bergenheim ----( 8:>
On Wednesday 16 January 2008 12:16:32 am Wolf Bergenheim wrote:
On 16.01.2008 03:34, Dylan Beaudette wrote:
> On Tuesday 15 January 2008, Hamish wrote:
>>>>> Martin Landa wrote:
>>>>>> BTW it would be great to start migration webpages to Drupal.
>>
>> Hamish:
>>>> One thing I think is critical is that the changes are monitored in
>>>> some sort of SCM with change history including author, date, and
>>>> commit log message. Does drupal give access to change history?
>>
>> (Accountability and peer review is needed as the webpage is the
>> "official voice" of the GRASS project)
>
> This is an important point. I am not necessarily advocating the use of
> Drupal or any other CMS- rather pointing out that it can provide
> considerable administrative convenience.
>
>> Dylan:
>>> I think that it is possible to have revisioned edits with Drupal,
>>> possibly after enabling some module.
>>
>> ...On the test site I have enabled the diff module
(http://drupal.org/project/diff) which will show you the diff between
two versions. There is also the Recent Changes module
(http://drupal.org/project/recent_changes) installed.Also drupal saves who made a page edit, and that can also be made visible.
> maybe this a module based on:
> http://groups.drupal.org/taxonomy/term/2408This is for accessing a version control repository trough Drupal, a bit
like webVC.Don't be afraid of the new installation, just go in there and get your
hands dirty! Send me an email if you need / want editing rights.--Wolf
Thanks for the great clarifications Wolf. Once I turn in my MS thesis (March
3rd) I would like to start working on the GRASS Drupal site. I'll continue to
*mostly* lurk until then!
Dylan
Could people please stop sending mails to both grass-dev@lists.osgeo.org
_and_ grass-dev@grass.itc.it. Both point to the same list now, IIUC, and
so they all arrive twice in our mailboxes.
Moritz
On Wed, January 16, 2008 22:39, Dylan Beaudette wrote:
On Wednesday 16 January 2008 12:16:32 am Wolf Bergenheim wrote:
On 16.01.2008 03:34, Dylan Beaudette wrote:
> On Tuesday 15 January 2008, Hamish wrote:
>>>>> Martin Landa wrote:
>>>>>> BTW it would be great to start migration webpages to Drupal.
>>
>> Hamish:
>>>> One thing I think is critical is that the changes are monitored in
>>>> some sort of SCM with change history including author, date, and
>>>> commit log message. Does drupal give access to change history?
>>
>> (Accountability and peer review is needed as the webpage is the
>> "official voice" of the GRASS project)
>
> This is an important point. I am not necessarily advocating the use of
> Drupal or any other CMS- rather pointing out that it can provide
> considerable administrative convenience.
>
>> Dylan:
>>> I think that it is possible to have revisioned edits with Drupal,
>>> possibly after enabling some module.
>>
>> ...On the test site I have enabled the diff module
(http://drupal.org/project/diff) which will show you the diff between
two versions. There is also the Recent Changes module
(http://drupal.org/project/recent_changes) installed.Also drupal saves who made a page edit, and that can also be made
visible.> maybe this a module based on:
> http://groups.drupal.org/taxonomy/term/2408This is for accessing a version control repository trough Drupal, a bit
like webVC.Don't be afraid of the new installation, just go in there and get your
hands dirty! Send me an email if you need / want editing rights.--Wolf
Thanks for the great clarifications Wolf. Once I turn in my MS thesis
(March
3rd) I would like to start working on the GRASS Drupal site. I'll continue
to
*mostly* lurk until then!Dylan
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 16.01.2008 23:39, Dylan Beaudette wrote:
Thanks for the great clarifications Wolf. Once I turn in my MS thesis (March 3rd) I would like to start working on the GRASS Drupal site. I'll continue to *mostly* lurk until then!
Looking forward to any kind of help 
good luck with your MS thesis.
--W
--
<:3 )---- Wolf Bergenheim ----( 8:>