2011/3/7 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/3/7 Peter Soetens <peter [..] ...>
>
> On Friday 04 March 2011 08:43:06 Willy Lambert wrote:
>> > Hi all,
>> >
>> > quote "Peter":
>> >
>> > I do see the shortcomings of our website, both in the sense of web
>> design
>> >
>> > > and in
>> > > the sense of usability/functionality. An upgrade to Drupal 6.x will
>> help,
>> > > if
>> > > we could combine this with a new 'theme', that would be great. This
>> *is*
>> > > on the roadmap for the coming months. Volunteers welcome to speed this
>> > > up.
>> >
>> > I am volunteer !
>>
>> Thanks ! We have already a very basic wiki page setup here:
>>
>> http://www.orocos.org/wiki/admins/migrating-drupal-6
>>
>> >
>> > I am curious to have details about what you have in mind for the
>> > possibility to review the web site. I am interested into participating,
>> to
>> > organize it and give the "user side", especially about package sharing.
>> I
>> > do not have any web design skills but I have a friend which agree to
>> help
>> > and have already help us in ours (http://www.team-ard.com, it's a
>> joomla
>> > with a retouched theme).
>> >
>> > How is the Orocos site made currently ? is it a Drupal website ? (which
>> > version ?)
>>
>> It's Drupal 5. We want to upgrade to 6 asap.
>
>
> Do you have anything against v7 ? stability issues ? long term work on v6
> going on at Orocos side that would be to reword ? lack of module support ?
> Is the module page up to date ?
>
>
>> Adding a package repository
>> counts as adding a 'Content Type' to the drupal system. You can choose how
>> a
>> content type is made up of 'fields'. For example, an url field, an image,
>> some
>> description etc. We tried to do so in the past for describing components,
>> with
>> this form : http://www.orocos.org/node/add/content-component
>>
>
> arg this is a private page, I can't read it. "You are not authorized to
> access this page. "
>
>
>> It's very rough, and having individual components described like this is a
>> laborous work. But it might make sense for package repositories. It does
>> not
>> provide the hosting of these repositories, only a place to collect the
>> information.
>>
>
> At the moment, after having discussed this on the mailing list, I think it
> is the only way to make this exists : give a free area for user to drop
> their informations (repositories, documentations, websites) with nothing
> hosted by Orocos.
>
>
>>
>> >
>> > I do not have concrete propositions yet, but before spending time into
>> > thinking, I'd rather know what's already in minds, so please say what
>> you
>> > have always dream on :p
>> >
>> > I put things into dev list because I think things have to be
>> pre-discussed
>> > before "spamming" every one, but I may do this on the user list if
>> someone
>> > prefers.
>>
>> The first thing to do is to download the latest drupal 6, unzip all
>> required
>> modules in the 'sites/all/modules' subdirectory. Once this is done, we can
>> import this in the git repository that I have and start applying the
>> patches
>> we have on 5 to this 6 version.
>>
>
> Is it a public repository ?
>
>
>>
>> A volunteer could at least create a tar ball of the version 6 + modules
>> and
>> make it available. We could create a private github repository that we
>> share
>> among the 'web dev' people and then start working on that, and follow the
>> test
>> plan of the wiki page.
>>
>>
> I think I can handle the tar ball.
>

there are some modules whose names don't exactly match :
image
img_assist (best fit http://drupal.org/project/imagefield_assist)

could you have a look for those to choose the right one you need ?

We have done a shell script to download all the stuff and to create a
tar_ball, do you wish to have the script ? the tar ball ? the both ?
If you want to have a check you can create an account there, i'll put you
admin

http://88.191.124.77/drupal-6.20/

> It is also possible to me to host a test site (I have a dedicated server)
> before transition if you want to be sure it will work. It will be usefull to
> me to test if I have theme and/or content suggestion. Is it possible for me
> after having created a tarball to get the Orocos site content (or at least a
> sub part) to play with ?
>
>
>
>> Peter
>>
>
>

On Mon, Mar 7, 2011 at 8:33 PM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
>
>
> 2011/3/7 Peter Soetens <peter [..] ...>
>>
>> On Friday 04 March 2011 08:43:06 Willy Lambert wrote:
>> > Hi all,
>> >
>> > quote "Peter":
>> >
>> > I do see the shortcomings of our website, both in the sense of web
>> > design
>> >
>> > > and in
>> > > the sense of usability/functionality. An upgrade to Drupal 6.x will
>> > > help,
>> > > if
>> > > we could combine this with a new 'theme', that would be great. This
>> > > *is*
>> > > on the roadmap for the coming months. Volunteers welcome to speed this
>> > > up.
>> >
>> > I am volunteer !
>>
>> Thanks ! We have already a very basic wiki page setup here:
>>
>> http://www.orocos.org/wiki/admins/migrating-drupal-6
>>
>> >
>> > I am curious to have details about what you have in mind for the
>> > possibility to review the web site. I am interested into participating,
>> > to
>> > organize it and give the "user side", especially about package sharing.
>> > I
>> > do not have any web design skills but I have a friend which agree to
>> > help
>> > and have already help us in ours (http://www.team-ard.com, it's a joomla
>> > with a retouched theme).
>> >
>> > How is the Orocos site made currently ? is it a Drupal website ? (which
>> > version ?)
>>
>> It's Drupal 5. We want to upgrade to 6 asap.
>
> Do you have anything against v7 ? stability issues ? long term work on v6
> going on at Orocos side that would be to reword ? lack of module support ?
> Is the module page up to date ?

Only few of the modules we need have been ported to v7. The list is
up-to-date, so it clearly shows that v7 isn't there yet.

>
>>
>> Adding a package repository
>> counts as adding a 'Content Type' to the drupal system. You can choose how
>> a
>> content type is made up of 'fields'. For example, an url field, an image,
>> some
>> description etc. We tried to do so in the past for describing components,
>> with
>> this form : http://www.orocos.org/node/add/content-component
>
> arg this is a private page, I can't read it. "You are not authorized to
> access this page. "

Try again. I've given you the 'web admin' status. Be careful :-)

>
>>
>> It's very rough, and having individual components described like this is a
>> laborous work. But it might make sense for package repositories. It does
>> not
>> provide the hosting of these repositories, only a place to collect the
>> information.
>
> At the moment, after having discussed this on the mailing list, I think it
> is the only way to make this exists : give a free area for user to drop
> their informations (repositories, documentations, websites) with nothing
> hosted by Orocos.

Ack.

>
>>
>> >
>> > I do not have concrete propositions yet, but before spending time into
>> > thinking, I'd rather know what's already in minds, so please say what
>> > you
>> > have always dream on :p
>> >
>> > I put things into dev list because I think things have to be
>> > pre-discussed
>> > before "spamming" every one, but I may do this on the user list if
>> > someone
>> > prefers.
>>
>> The first thing to do is to download the latest drupal 6, unzip all
>> required
>> modules in the 'sites/all/modules' subdirectory. Once this is done, we can
>> import this in the git repository that I have and start applying the
>> patches
>> we have on 5 to this 6 version.
>
> Is it a public repository ?

It contains the site's database address, password and username. We can
share it with a few web admins that have a github account. It's not
common practice to put the site's sources online, although we could
omit the settings.php file from a public repos. I could put the
current repos online using such a method.

>
>>
>> A volunteer could at least create a tar ball of the version 6 + modules
>> and
>> make it available. We could create a private github repository that we
>> share
>> among the 'web dev' people and then start working on that, and follow the
>> test
>> plan of the wiki page.
>>
>
> I think I can handle the tar ball. It is also possible to me to host a test
> site (I have a dedicated server) before transition if you want to be sure it
> will work. It will be usefull to me to test if I have theme and/or content
> suggestion. Is it possible for me after having created a tarball to get the
> Orocos site content (or at least a sub part) to play with ?

Yes, but be aware that you need to go through the upgrade process of
the current database, which has always been a painful exercise in the
past. You don't want to do this on your own. That's why we propose to
do it on a public test website (but with not advertised sub-domain
name), such that we all can assist each other during the upgrade.

Peter