Website management

[Jeremias Maerki <de...@greenmail.ch>]

Guys,

I'm not happy with the way our website is managed:
- Updating the website is a big job each time.
- Due to knowledge gaps some of the files in /www/xml.apache.org/fop are
not the most current ones from the CVS module.
- Uploading compiled changes into a version control system (though
propagated by some here at the ASF) seems not very elegant. Yes, it has
it's advantages in case of a mistake when you can simply go back to a
previous state, but you'll get my meaning.

For Barcode4J I have a very simple system which allows me to build and
deploy the whole site from the build system. The compiled website is
compressed into a tar.gz and uploaded using SCP and extracted at the
target using Ant's sshexec task. Once it is properly set up, this is
painless, provided everyone uses the same Forrest version.

If noone objects, I can implement this in the next 2 or 3 weeks and test
it by deploying the FOP website to xmlgraphics.apache.org/fop. When it
works we can then also remove the FOP website from the XML site and
instead do redirections there.

Jeremias Maerki

Re: Failed

[Simon Pepping <sp...@leverkruid.nl>]

Dear Guanglei,

On Wed, Jul 06, 2005 at 05:31:27PM -0700, guanglei song wrote:
> 
> Hi, sir
> 
> I was informed by google.com that the application for summer of code is failed.
> 
> Sorry to know and let me know what I need to do for the project, since I am still interested in.

I am sorry to hear that. Jeremias Märki, who is the mentor of this
project, is not available during this week. I suggest you wait until
early next week to hear his thoughts.

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

Re: Failed

[Jeremias Maerki <de...@greenmail.ch>]

Hi Guanglei

Yes, that's is unfortunate, but I'm happy to see that you're still
interested. Given that you're not bound to the project proposal anymore
you can do whatever you like in Apache FOP. Of course, you can still
have a look at RTF output which needs some polishing. You can also look
at the tasks on the Wiki page:
http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks

There are many things that you can choose from. We'd appreciate if you
notified us when you've decided what to work on so we can avoid any
duplicate work. If you need help while coding, just send a mail to this
mailing list.

On 07.07.2005 02:31:27 guanglei song wrote:
> I was informed by google.com that the application for summer of code is failed.
> Sorry to know and let me know what I need to do for the project, since I am still interested in.


Jeremias Maerki

Failed

[guanglei song <lu...@yahoo.com>]

Hi, sir

I was informed by google.com that the application for summer of code is failed.

Sorry to know and let me know what I need to do for the project, since I am still interested in.

 

Best regards

guanglei


		
---------------------------------
 Sell on Yahoo! Auctions  - No fees. Bid on great items.

Re: Website management

[Jeremias Maerki <de...@greenmail.ch>]

Thanks for the hint. But unless this happens soon and doesn't make a big
website refactoring necessary (i.e. provides an easy migration path from
Forrest), I will still push for what I proposed.

On 29.06.2005 12:03:10 Renaud Richardet wrote:
> Bonjour FOP-dev's
> 
> FYI, there is a lot of talking on the Cocoon list about website 
> management and documentation management. Eventually, Daisy and/or Lenya 
> will be used for website content management (I don't know the current 
> state of the discussions). You might want to give an eye there.
> 
> HTH,
> Renaud
> 
> The Web Maestro wrote:
> 
> > BACKGROUND
> > Currently, one has to modify the src *.xml files, generate the output 
> > *.html files by running 'forrest' and achieve BUILD SUCCESSFUL, then 
> > move or copy them to a separate CVS, then COMMIT via CVS the updated 
> > *.html files.
> >
> > As the current Apache FOP Web Maestro ;-) I concur that the current 
> > system is not the best system. A change would be nice. The solution 
> > Jeremias outlines would be acceptable to me.
> >
> > Another idea would be to COMMIT the 'forrest' output directory 
> > build/site/*.* and have the automated process grab the files from 
> > there (instead of grabbing them from the separate CVS repository 
> > (which is actually /www/xml.apache.org/targets/fop).
> >
> > Web Maestro Clay
> >
> > On Jun 27, 2005, at 11:36 PM, Jeremias Maerki wrote:
> >
> >> Guys,
> >>
> >> I'm not happy with the way our website is managed:
> >> - Updating the website is a big job each time.
> >> - Due to knowledge gaps some of the files in /www/xml.apache.org/fop are
> >> not the most current ones from the CVS module.
> >> - Uploading compiled changes into a version control system (though
> >> propagated by some here at the ASF) seems not very elegant. Yes, it has
> >> it's advantages in case of a mistake when you can simply go back to a
> >> previous state, but you'll get my meaning.
> >>
> >> For Barcode4J I have a very simple system which allows me to build and
> >> deploy the whole site from the build system. The compiled website is
> >> compressed into a tar.gz and uploaded using SCP and extracted at the
> >> target using Ant's sshexec task. Once it is properly set up, this is
> >> painless, provided everyone uses the same Forrest version.
> >>
> >> If noone objects, I can implement this in the next 2 or 3 weeks and test
> >> it by deploying the FOP website to xmlgraphics.apache.org/fop. When it
> >> works we can then also remove the FOP website from the XML site and
> >> instead do redirections there.
> >>
> >> Jeremias Maerki
> >>
> >>
> >
> > Regards,
> >
> > Web Maestro Clay
> 



Jeremias Maerki

Re: Website management

[Renaud Richardet <re...@gmail.com>]

Bonjour FOP-dev's

FYI, there is a lot of talking on the Cocoon list about website 
management and documentation management. Eventually, Daisy and/or Lenya 
will be used for website content management (I don't know the current 
state of the discussions). You might want to give an eye there.

HTH,
Renaud

The Web Maestro wrote:

> BACKGROUND
> Currently, one has to modify the src *.xml files, generate the output 
> *.html files by running 'forrest' and achieve BUILD SUCCESSFUL, then 
> move or copy them to a separate CVS, then COMMIT via CVS the updated 
> *.html files.
>
> As the current Apache FOP Web Maestro ;-) I concur that the current 
> system is not the best system. A change would be nice. The solution 
> Jeremias outlines would be acceptable to me.
>
> Another idea would be to COMMIT the 'forrest' output directory 
> build/site/*.* and have the automated process grab the files from 
> there (instead of grabbing them from the separate CVS repository 
> (which is actually /www/xml.apache.org/targets/fop).
>
> Web Maestro Clay
>
> On Jun 27, 2005, at 11:36 PM, Jeremias Maerki wrote:
>
>> Guys,
>>
>> I'm not happy with the way our website is managed:
>> - Updating the website is a big job each time.
>> - Due to knowledge gaps some of the files in /www/xml.apache.org/fop are
>> not the most current ones from the CVS module.
>> - Uploading compiled changes into a version control system (though
>> propagated by some here at the ASF) seems not very elegant. Yes, it has
>> it's advantages in case of a mistake when you can simply go back to a
>> previous state, but you'll get my meaning.
>>
>> For Barcode4J I have a very simple system which allows me to build and
>> deploy the whole site from the build system. The compiled website is
>> compressed into a tar.gz and uploaded using SCP and extracted at the
>> target using Ant's sshexec task. Once it is properly set up, this is
>> painless, provided everyone uses the same Forrest version.
>>
>> If noone objects, I can implement this in the next 2 or 3 weeks and test
>> it by deploying the FOP website to xmlgraphics.apache.org/fop. When it
>> works we can then also remove the FOP website from the XML site and
>> instead do redirections there.
>>
>> Jeremias Maerki
>>
>>
>
> Regards,
>
> Web Maestro Clay

Re: Website management

[The Web Maestro <th...@gmail.com>]

BACKGROUND
Currently, one has to modify the src *.xml files, generate the output 
*.html files by running 'forrest' and achieve BUILD SUCCESSFUL, then 
move or copy them to a separate CVS, then COMMIT via CVS the updated 
*.html files.

As the current Apache FOP Web Maestro ;-) I concur that the current 
system is not the best system. A change would be nice. The solution 
Jeremias outlines would be acceptable to me.

Another idea would be to COMMIT the 'forrest' output directory 
build/site/*.* and have the automated process grab the files from there 
(instead of grabbing them from the separate CVS repository (which is 
actually /www/xml.apache.org/targets/fop).

Web Maestro Clay

On Jun 27, 2005, at 11:36 PM, Jeremias Maerki wrote:
> Guys,
>
> I'm not happy with the way our website is managed:
> - Updating the website is a big job each time.
> - Due to knowledge gaps some of the files in /www/xml.apache.org/fop 
> are
> not the most current ones from the CVS module.
> - Uploading compiled changes into a version control system (though
> propagated by some here at the ASF) seems not very elegant. Yes, it has
> it's advantages in case of a mistake when you can simply go back to a
> previous state, but you'll get my meaning.
>
> For Barcode4J I have a very simple system which allows me to build and
> deploy the whole site from the build system. The compiled website is
> compressed into a tar.gz and uploaded using SCP and extracted at the
> target using Ant's sshexec task. Once it is properly set up, this is
> painless, provided everyone uses the same Forrest version.
>
> If noone objects, I can implement this in the next 2 or 3 weeks and 
> test
> it by deploying the FOP website to xmlgraphics.apache.org/fop. When it
> works we can then also remove the FOP website from the XML site and
> instead do redirections there.
>
> Jeremias Maerki
>
>

Regards,

Web Maestro Clay
-- 
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet