firebird-website — Everything about Firebird's web site

Re: [Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Paul V. <pa...@vi...>]

Hi Dmitry,

> I will send you my working copy (with the changed links) soon

OK, I'll wait for those sources and take it from there.

I still think we should recreate the /manual, /pdfmanual etc. symlinks on the new site, not only to make the transition easier but also to prevent future headaches. Working with paths like file/documentation/reference_manuals/user_manuals/html in the sources can easily lead to mistypings when adding new links, and is also a pain if the directory structure should ever change. (Yes, of course you can keep the old paths as symlinks, but I'd rather have those symlinks clean and simple in the document root than buried deep down in some forgotten, deserted tree.)

Have a nice holiday!


Paul Vinkenoog

Re: [Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Dmitry Y. <fir...@ya...>]

Hi Paul,

> It looks like you didn't commit any of your changes to CVS; is that correct?

Correct. As we were field testing the new site on firebirdtest.com and many links are absolute, my copy contained all the links changed to the new structire but prefixed with firebirdtest.com. As you see, this is not something to be committed :-) Now we have to change the prefix to firebirdsql.org and it could be comitted then.

I will send you my working copy (with the changed links) soon, so that you could validate the changes and move the work further. I won't be able to help in the next couple of weeks.

> Also, did you only modify the sources and upload the generated content as-is, or did you have to post-process the HTML as well?

I've modified only the sources and the generated files have been uploaded.

> Another thing: most <ulink>s that point to within the Firebird site are either relative (in which case they can stay as they are) or absolute local links into the /manual or /pdfmanual trees. /manual and /pdfmanual (and a couple more) are symlinks to the real locations. They were created for two reasons:
>
> a) to save use some typing
> b) to make them independent from the real paths
>
> I.e., by creating a handful of symlinks on the new site, these links don't have to be updated at all.

All the absolute paths have been changed to fit the new site structure. All the relative paths were left "as is". If they don't include the root folders (manual/pdf/etc) they are OK. Otherwise they need a correction as well.

> On the new site, in the web root directory, manual should point to file/documentation/reference_manuals/user_manuals/html, and pdfmanual to file/documentation/reference_manuals/user_manuals/

The locations were changed the folowing way:

firebirddocs -> /documentation/reference_manuals/user_manuals
refdocs -> /documentation/reference_manuals/reference_material
rlsnotes -> /documentation/release_notes
papers -> /documentation/papers_presentations

The PDFs are in the root location, HTMLs are in the /html subdirectory. The language specific versions are suffixed with the language ID and placed in the same location (similarly to the old site). All the file names are the same between old and new site versions.


Dmitry

Re: [Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Paul V. <pa...@vi...>]

Hi again, Dmitry,

>> It cannot be simply replaced, because the links in the old copy are wrong. I've spent time on adjusting all the links in the documentation sources to point to the new site structure.

It looks like you didn't commit any of your changes to CVS; is that correct?

Also, did you only modify the sources and upload the generated content as-is, or did you have to post-process the HTML as well?

Another thing: most <ulink>s that point to within the Firebird site are either relative (in which case they can stay as they are) or absolute local links into the /manual or /pdfmanual trees. /manual and /pdfmanual (and a couple more) are symlinks to the real locations. They were created for two reasons:

a) to save use some typing
b) to make them independent from the real paths

I.e., by creating a handful of symlinks on the new site, these links don't have to be updated at all.

On the new site, in the web root directory, manual should point to file/documentation/reference_manuals/user_manuals/html, and pdfmanual to file/documentation/reference_manuals/user_manuals/

If this is feasible (and I don't see why not) I'll provide a full list of required symlinks. This will take care of most of the broken links. The others will have to be fixed by hand.


Cheers,
Paul Vinkenoog

Re: [Firebird-website] How is the new site going?

[marius a. p. <ma...@gm...>]

On Sun, Jun 5, 2011 at 3:46 PM, Carlos H. Cantu <li...@wa...> wrote:
> It is curious to see so many issues being reported to the tracker only
> now that the new site is officially on air. Those issues was already
> present for the latest months in firebirdtest.com domain but, like it
> seems to happen with official server releases, most of the people only
> cares to check things when they gets officially released...
I like to qute the vlc team People dont use the test builds or alphas
they report bugs only after
the official final builds are released
The same seems to be with the firebird official site (but some bugs
were reported )
The good news is that we are moving , the bad news is that there is
still a heavy burden : the full documentation
So instead of crying please send text to the doc area


>
> Anyway, better later than never.
>
> PS: before someone get mad with my comments, I'm not speaking about
> anyone specifically. It just seems to be a "cultural" thing.

OT ps: Fascinating creatures, phoenixes. They can carry immensely
heavy loads, their tears have healing powers, and they make highly
faithful pets

Re: [Firebird-website] How is the new site going?

[marius a. p. <ma...@gm...>]

On Sat, Jun 4, 2011 at 12:24 PM, Lester Caine <le...@ls...> wrote:
> ak...@ib... wrote:
>>
>> This design was available for review since December. Where were you
>> during last months with design suggestions?
>>
>> We will run it as is asap, all improvements will be done after launch
>> (and after thorough discussion, be prepared to protect your thoughts
>> with prooflinks and serious arguments).
>
> Well *I* have provided an alternative on the wiki.firebirdsql.org site for some
> years. All of this had already been done, but nobody was interested :(
> The fb copy is no longer working again, but have you even looked at
> http://fbwiki.lsces.co.uk/ which has all of the facilities that were being
> discussed.
People don't contribute that ofter they take documentation/product for granted
and only a few contribute back
but i think you can refresh your wiki and add more content
in time if people will ask we can point them to your wiki or whatever
becomes the official one

Re: [Firebird-website] How is the new site going?

[marius a. p. <ma...@gm...>]

On Sat, Jun 4, 2011 at 12:03 PM, ak...@ib... <ak...@ib...> wrote:
> Hello Lester,
>
> This design was available for review since December. Where were you during
> last months with design suggestions?
>
> We will run it as is asap, all improvements will be done after launch (and
> after thorough discussion, be prepared to protect your thoughts with
> prooflinks and serious arguments).

Lester send patches and css fixes and we will consider
Also if you find bugs and missings please report them to the tracker
For the wiki part seems that is good to have one , if the dqteam want
we can put the wiki on
main servers or on the old one
I see that jaybird is using docuwiki I think we can use docuwiki for
all other subprojects that want them
http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=info:start
tutorials can be easily written without knowing the docbook syntax

[Firebird-website] НА: about the new web site

[<ak...@ib...>]

Hello Paul,

How else we would involve so many people actively work for web site?

The same is true for x.x.0 releases of Firebird server itself, so I think this is life style of low budget open source projects.



It does not mean that we are not working at the site right now, trying to fix issues and synchronize outdate content.

Regards,
Alexey Kovyazin


----- Reply message -----
От: "Paul Vinkenoog" <pa...@vi...>
Кому: "Firebird Project Web Team" <fir...@li...>
Тема: [Firebird-website] about the new web site
Дата: вс, июн 5, 2011 15:32


Helen wrote:

> FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date)

If that is the case, wasn't the DNS change a bit premature?


Paul Vinkenoog

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
_______________________________________________
Firebird-website mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-website

Re: [Firebird-website] How is the new site going?

[Carlos H. C. <li...@wa...>]

It is curious to see so many issues being reported to the tracker only
now that the new site is officially on air. Those issues was already
present for the latest months in firebirdtest.com domain but, like it
seems to happen with official server releases, most of the people only
cares to check things when they gets officially released...

Anyway, better later than never.

PS: before someone get mad with my comments, I'm not speaking about
anyone specifically. It just seems to be a "cultural" thing.

[]s
Carlos H. Cantu
www.FireBase.com.br - www.firebirdnews.org
www.warmboot.com.br - blog.firebase.com.br

[Firebird-website] [FB-Tracker] Created: (WEB-73) Missing information in each Firebird sub-project from Firebird Development link

[Luciano M. (JIRA) <tr...@fi...>]

Missing information in each Firebird sub-project from Firebird Development link
-------------------------------------------------------------------------------

                 Key: WEB-73
                 URL: http://tracker.firebirdsql.org/browse/WEB-73
             Project: Web site
          Issue Type: Bug
         Environment: Chrome 11
            Reporter: Luciano Mendes
            Assignee: Pavel Cisar


1- Go to http://www.firebirdsql.org/en/development/ ; 
2- Open each sub-project link:
     - Firebird Server
     - Quality Assurance
     - Documentation
     - JDBC Driver
     - ODBC Driver
     - .NET Provider
     - Python Driver

Actual result:
The links are open but nothing information about each sub-project are displayed.

Expected result:
If there is not information to be displayed yet, then remove the link for while.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [Firebird-website] about the new web site

[Paul V. <pa...@vi...>]

Marius wrote:

> And i think we need access to the subsections as it was promised
> Also if the docs are wrong i think the links should pont to the right
> generated documents until they are fixed

That would work, were it not that the old docs contain links that are specific to the old site structure.

Pointing to the old docs would ensure that the content is correct and consistent, but would break those links.

Pointing to the newly-generated docs (as is done now) means the links are valid, but the content is not - at least in some essential manuals.

So it looks like we weren't ready to move yet. But... we'll fix it.


Paul Vinkenoog

Re: [Firebird-website] about the new web site

[marius a. p. <ma...@gm...>]

On Sun, Jun 5, 2011 at 2:32 PM, Paul Vinkenoog <pa...@vi...> wrote:
> Helen wrote:
>
>> FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date)
>
> If that is the case, wasn't the DNS change a bit premature?
Well i guess it's better that it happened (sooner than later) and we
have a lot of content to check , we all can submit bugs to the tracker
and i see they are fixed as we speak.

And i think we need access to the subsections as it was promised
Also if the docs are wrong i think the links should pont to the right
generated documents until they are fixed

Re: [Firebird-website] about the new web site

[Paul V. <pa...@vi...>]

Helen wrote:

> FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date)

If that is the case, wasn't the DNS change a bit premature?


Paul Vinkenoog

Re: [Firebird-website] about the new web site

[marius a. p. <ma...@gm...>]

On Sun, Jun 5, 2011 at 2:01 PM, Philippe Makowski
<mak...@fi...> wrote:
> Helen Borrie  [05/06/2011 12:19] :
>> FYI, the "old" website (actually, CURRENT, since the "new" one is two
>> months out of date) is still accessible via
>> http://web.firebirdsql.org.
> thanks Helen, for now it is enough for me
>
>> I think Sergey needs to find a
>> way to let visitors to the new site know that the old site is still
>> available and has the up-to-date content.
> yes and this way links to snapshots builds is solved
> no need to push builds on another place than web.firebirdsql.org
> (209.183.20.105)
>
> that the easiest way to solve
> http://tracker.firebirdsql.org/browse/WEB-71
> and it is the best way to do it
> instead of http://www.firebirdsql.org/download/snapshot_builds/
> just put http://web.firebirdsql.org/download/snapshot_builds/

I agree also the python documentation should be kept on old web server
(i think it can be regenerated easily there)
http://www.firebirdsql.org/devel/python/docs/3.3.0/tutorial.html
should point to
http://web.firebirdsql.org/devel/python/docs/3.3.0/tutorial.html

Re: [Firebird-website] about the new web site

[Philippe M. <mak...@fi...>]

Helen Borrie  [05/06/2011 12:19] :
> FYI, the "old" website (actually, CURRENT, since the "new" one is two
> months out of date) is still accessible via
> http://web.firebirdsql.org.  
thanks Helen, for now it is enough for me

> I think Sergey needs to find a
> way to let visitors to the new site know that the old site is still
> available and has the up-to-date content.
yes and this way links to snapshots builds is solved
no need to push builds on another place than web.firebirdsql.org
(209.183.20.105)

that the easiest way to solve
http://tracker.firebirdsql.org/browse/WEB-71
and it is the best way to do it
instead of http://www.firebirdsql.org/download/snapshot_builds/
just put http://web.firebirdsql.org/download/snapshot_builds/

Re: [Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Paul V. <pa...@vi...>]

Hello Dmitry,

> > This should not have happened. The CVS source is currently in an "unstable" state, between versions, as can be seen right under the title:
> >
> >     ?? X....... 201?, document version 1.1 — covers Firebird 2.1–2.1.4
>
> And how could one know that? As a developer, I really expect CVS/SVN to contain the latest working version. Having it somewhere else (on the home hard disk) is not what can be expected from a distributed team working on the shared contents.

That's why we commit work even if the new version is not yet publishable. Try to look at it the other way round: suppose I built the Firebird binaries from HEAD and published them on the new website? I don't think the core team would be very enthusiastic.

> It cannot be simply replaced, because the links in the old copy are wrong. I've spent time on adjusting all the links in the documentation sources to point to the new site structure. And since nobody was willing to help that time and nobody has indicated that I shouldn't be looking in CVS for the actual sources, we have all the docs on the new site based on CVS. Like it or not.

The sources for the published versions *are* in CVS, but in a number of cases there have been later commits while working toward a new doc version which is not yet publishable - just as happens with program code.

With the PDFs, there's an additional reason why they shouldn't be built blindly from the sources. PDFs are built in a two-step process: first from DocBook XML to XSL-FO, then from XSL-FO to PDF. Sometimes (depending on the type and the length of the document), the XSL-FO output has to be manually adjusted before the final PDF is built. However, in most cases this is done fore cosmetic reasons only, so this issue is not as pressing as the other one.

> Now, knowing all the facts, please suggest a solution.

I take it you committed all the <ulink> changes to CVS? I'll have a look and come up with a solution later today. Probably the best thing to do is, for each doc separately, to take your diffs and apply them to the latest published/publishable version, then rebuild and republish.

For many documents, the latest CVS version IS the latest published version, so in those cases there's nothing to do except perhaps embellish the PDF.

> As for me, I feel myself as having done a dumb useless work.

No, but it would have been better, once you had planned how to do the conversion work, to announce it in firebird-doc and/or web-redevel to see if there were any gotchas.

Anyway, I'll have a look at it and see what can be done. I'm also willing to do the necessary work myself, as I have a little more free time now. These last few months I haven't been able to do any substantial work for Firebird (except working on the 2.5 LRU behind the scenes), and although that's not my fault, it doesn't feel good :-(

Speaking about the 2.5 LRU, it's on the verge of being published, BTW :-)


Cheers,
Paul Vinkenoog

Re: [Firebird-website] about the new web site

[Helen B. <he...@ii...>]

At 09:48 PM 5/06/2011, Philippe wrote:
>Hi,
>
>First thanks to all for this good work
>
>
>I have now two questions :
>
>- How can we publish snapshots builds ?
>- On the old web site, developers can have a "rabbit hole" so they can
>publish drafts or others thinks they want (for example I publish on my
>rabbit hole results of QA test run)
>how can we have the same possibility ?
>I mean just a place to put files via ftp or ssh ?
>
>May be one solution is to keep the old web server for that and snapshots
>builds ?
>with just a front page with links to svn, snapshots, rabbit holes, main
>web site
>
>and give it a new name like dev.firebirdsql.org ?

FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date) is still accessible via http://web.firebirdsql.org.  For the present at least it is the only place where people can find the full and correct links to all the lists, the download pages, the driver pages and the up-to-date FF membership and sponsorship details.  I think Sergey needs to find a way to let visitors to the new site know that the old site is still available and has the up-to-date content.

We have a 2.5 point release coming up, with no clarity about how the Download page will be available, either.

Helen

[Firebird-website] about the new web site

[Philippe M. <mak...@fi...>]

Hi,

First thanks to all for this good work


I have now two questions :

- How can we publish snapshots builds ?
- On the old web site, developers can have a "rabbit hole" so they can
publish drafts or others thinks they want (for example I publish on my
rabbit hole results of QA test run)
how can we have the same possibility ?
I mean just a place to put files via ftp or ssh ?

May be one solution is to keep the old web server for that and snapshots
builds ?
with just a front page with links to svn, snapshots, rabbit holes, main
web site

and give it a new name like dev.firebirdsql.org ?

Re: [Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Dmitry Y. <fir...@ya...>]

Paul,

> Someone built the 2.1 Language Reference Update from the current DocBook source and published it on the new site.

It was me and it looked like the only logical solution possible.

> This should not have happened. The CVS source is currently in an "unstable" state, between versions, as can be seen right under the title:
>
>     ?? X....... 201?, document version 1.1 — covers Firebird 2.1–2.1.4

And how could one know that? As a developer, I really expect CVS/SVN to contain the latest working version. Having it somewhere else (on the home hard disk) is not what can be expected from a distributed team working on the shared contents.

> Please, let someone with proper access replace it with the last published HTML and PDF versions as found on the old site.

It cannot be simply replaced, because the links in the old copy are wrong. I've spent time on adjusting all the links in the documentation sources to point to the new site structure. And since nobody was willing to help that time and nobody has indicated that I shouldn't be looking in CVS for the actual sources, we have all the docs on the new site based on CVS. Like it or not.

> Apart from the (intended!) garbage in the line cited above, there may be all kinds of inconsistencies and/or errors and/or visible comments in the content.

Now, knowing all the facts, please suggest a solution. As for me, I feel myself as having done a dumb useless work.


Dmitry

[Firebird-website] [FB-Tracker] Created: (WEB-72) Wrong Series 2.5.x Roadmap Track Details link

[Luciano M. (JIRA) <tr...@fi...>]

Wrong Series 2.5.x Roadmap Track Details link
---------------------------------------------

                 Key: WEB-72
                 URL: http://tracker.firebirdsql.org/browse/WEB-72
             Project: Web site
          Issue Type: Bug
            Reporter: Luciano Mendes
            Assignee: Pavel Cisar



1. Go to http://www.firebirdsql.org/en/roadmap/ ;
2. select v2.5.1 link ;

Actual Result:
"Release Notes - Firebird Core - Version 2.1.5 - HTML format" page is opened.

Expected Result:
"Release Notes - Firebird Core - Version 2.5.1 - HTML format" should be opened.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-website] [FB-Tracker] Created: (WEB-71) Empty folder in Snapshot Builds

[Claudio R. (JIRA) <tr...@fi...>]

Empty folder in Snapshot Builds
-------------------------------

                 Key: WEB-71
                 URL: http://tracker.firebirdsql.org/browse/WEB-71
             Project: Web site
          Issue Type: Bug
            Reporter: Claudio Romero
            Assignee: Pavel Cisar
            Priority: Trivial


Empty folder for

http://www.firebirdsql.org/download/snapshot_builds/win/

and

http://www.firebirdsql.org/download/snapshot_builds/linux/

Regards


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-website] Wrong Firebird 2.1 Language Reference Update published

[Paul V. <pa...@vi...>]

Hi,

Someone built the 2.1 Language Reference Update from the current DocBook source and published it on the new site.

This should not have happened. The CVS source is currently in an "unstable" state, between versions, as can be seen right under the title:

    ?? X....... 201?, document version 1.1 — covers Firebird 2.1–2.1.4

Please, let someone with proper access replace it with the last published HTML and PDF versions as found on the old site.

Apart from the (intended!) garbage in the line cited above, there may be all kinds of inconsistencies and/or errors and/or visible comments in the content.


Paul Vinkenoog

[Firebird-website] More missing lists

[Helen B. <he...@ii...>]

Lists also missing:

Sourceforge lists:
  firebird-net-provider (driver support)
  firebird-odbc-devel (driver support)
  firebird-test (Project)
  firebird-checkins (Project)

Yahoogroups:
  ib-conversions (general support)
  firebird-job-board (other)

Language
  Italian

Sergey/Alexey, I suggest that Olga picks up the .dat files from the ./lists subdirectory of the web.firebirdsql.org webserver.

Helen

[Firebird-website] [FB-Tracker] Created: (WEB-70) Firebird-website mailing list is missing

[Popa A. M. (JIRA) <tr...@fi...>]

Firebird-website mailing list is missing
----------------------------------------

                 Key: WEB-70
                 URL: http://tracker.firebirdsql.org/browse/WEB-70
             Project: Web site
          Issue Type: Bug
            Reporter: Popa Adrian Marius
            Assignee: Pavel Cisar


On the mailing list page the firebird-website is missing
http://www.firebirdsql.org/en/mailing-lists/

it should point to
https://lists.sourceforge.net/lists/listinfo/firebird-website

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-website] Firebird-website missing

[marius a. p. <ma...@gm...>]

On the mailing list page the firebird-website is missing
http://www.firebirdtest.com/en/mailing-lists/

it should point to
https://lists.sourceforge.net/lists/listinfo/firebird-website

[Firebird-website] [FB-Tracker] Created: (WEB-69) New site isn't update to show .NET provider 2.6.5 release

[Popa A. M. (JIRA) <tr...@fi...>]

New site isn't update to show .NET provider 2.6.5 release
---------------------------------------------------------

                 Key: WEB-69
                 URL: http://tracker.firebirdsql.org/browse/WEB-69
             Project: Web site
          Issue Type: Bug
            Reporter: Popa Adrian Marius
            Assignee: Pavel Cisar
            Priority: Critical


the new site doesn't contain new links added on Friday for 2.6.5
release of .NET provider. The old site has correct content. As it's
now hot, can you please fix it ASAP. Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira