Got it, thanks. Layout should be the same, just a real content update.
And after todays news, I can also remove incubator, while I am at it :-) have a nice evening. jan On 18 October 2012 19:15, Alexandro Colorado <[email protected]> wrote: > On 10/18/12, jan iversen <[email protected]> wrote: > > I just learned something :-) > > > > I run windows7 for my "administrative" work, like browsing, but have > ubuntu > > 12.04 installed in virtualbox, together with a AOO trunk, where I do some > > development. > > > > I just did not know that the www was also in SVN, brilliant idea ! > > > > I will do svn co imitatively, and play with changes. > > > > That is no good, I get an error message from svn saying that the > repository > > is permanently relocated to <same address>, please relocate ? > > I might have messed up on the SVN URL Use the ooo-site trunk instead > of the main/trunk. (you will get all the projects so you can halt once > you get the trunk and just update the l10n folder). > https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/ > > and l10n is here > https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/l10n/ > > > > > my svn works, because I have done several source updates today due to a > > compile problem. > > > > > > The commit will have to go through a committer, but that is not a > problem. > > > > jan I. > > > > > > On 18 October 2012 18:54, Alexandro Colorado <[email protected]> wrote: > > > >> Well the process is not that hard, just need to do a site checkout. > >> http://incubator.apache.org/openofficeorg/source.html > >> > >> If you are on linux, installing subversion-client will do and checkout > >> > >> svn co > >> http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/ > >> localization > >> > >> A GUI app for KDE is kdesvn and for gnome is RapidSVN and windows > >> there is TortoiseSVN. > >> > >> Basically is a file explorer where you are able to update commit and > >> check the history of the file. > >> > >> will do. > >> > >> On 10/18/12, jan iversen <[email protected]> wrote: > >> > You are quite right. > >> > > >> > But then I will have a hard time helping to change > l10n.openoffice.org, > >> > even though it would be nice to get it done. > >> > > >> > jan. > >> > > >> > On 18 October 2012 18:31, Alexandro Colorado <[email protected]> wrote: > >> > > >> >> On 10/18/12, jan iversen <[email protected]> wrote: > >> >> > I had a deeper look there and got one good question. > >> >> > > >> >> > Why do we keep l10n.openoffice.org ? > >> >> > >> >> Wiki is to work, website is the front of the project. Most projects > >> >> just keep 2 or 3 pages on the www while having many on the wiki. > >> >> Usually people enter through the www and then redirect to the wiki > >> >> eventually. (likewise u will think on Apache.org -> > >> >> openoffice.apache.org) However OOo probably has more visibility than > >> >> Apache in the real world. > >> >> > >> >> Static content such as processes, FAQ, and others were kept on the > >> >> www. While more dynamic information like Translating campaigns for > >> >> each version releases are on the wiki. Translating campaigns like: > >> >> Release 3.4 > >> >> > >> >> > >> >> > It would be easier to use the l10n page in wiki, combine it with > >> >> > information from l10n.openOffice.org and the localize wiki page. > >> >> > > >> >> > Just as a side remark, that would make it possible for me and > others > >> to > >> >> > contribute. > >> >> > > >> >> > jan > >> >> > > >> >> > On 18 October 2012 18:07, Alexandro Colorado <[email protected]> > wrote: > >> >> > > >> >> >> On 10/18/12, jan iversen <[email protected]> wrote: > >> >> >> > Is there anyone left who feels "responsible" for > >> >> >> > l10n.openoffice.org, > >> >> >> > if > >> >> >> > not I will give it a go, since it is in the scope of what I work > >> on. > >> >> >> > > >> >> >> > The steps suggested seems quite fair, however I do not know who > >> >> consult > >> >> >> > with ? > >> >> >> > >> >> >> l10n was directed by Rafaela Braconi who was a Sun/Oracle employee > >> >> >> so > >> >> >> most of the direction got lost there. Most of the process was > >> >> >> concerted with the engineers like Eike Rathke and Pavel Janik > which > >> >> >> deal with the l10n cws. I think Pavel still around, but not very > >> >> >> active lately. > >> >> >> > >> >> >> > > >> >> >> > jan > >> >> >> > > >> >> >> > On 18 October 2012 15:46, Alexandro Colorado <[email protected]> > >> wrote: > >> >> >> > > >> >> >> >> On 10/18/12, jan iversen <[email protected]> wrote: > >> >> >> >> > I have already put links in place, both on the localization > >> >> >> >> > page > >> >> and > >> >> >> on > >> >> >> >> the > >> >> >> >> > original (not old :) ) document. > >> >> >> >> > > >> >> >> >> > It is now updated with you snippet. > >> >> >> >> > >> >> >> >> Since we are in this topic there is also another branch that > >> >> >> >> would > >> >> >> >> need to be updated -- eventually. Which is the > >> l10n.openoffice.org > >> >> >> >> website. This was updated back in 2010 and most of the update > >> >> >> >> process > >> >> >> >> was documented here: > >> >> >> >> http://wiki.openoffice.org/wiki/L10n_Web_Pages_Reloaded > >> >> >> >> > >> >> >> >> We should use this docs as a framework to see in what stages we > >> >> >> >> want > >> >> >> >> to update the infromation and also to what extend. There is > >> >> >> >> still > >> a > >> >> >> >> lot of infrastructure to be done specially on QA-Testing and > >> >> >> >> release > >> >> >> >> sync. > >> >> >> >> > >> >> >> >> > >> >> >> >> > > >> >> >> >> > jan > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > On 18 October 2012 15:05, Alexandro Colorado <[email protected]> > >> >> wrote: > >> >> >> >> > > >> >> >> >> >> On 10/16/12, jan iversen <[email protected]> wrote: > >> >> >> >> >> > Don´t misunderstand me, I think everybody does a nice job > >> >> >> >> >> > in > >> >> >> getting > >> >> >> >> us > >> >> >> >> >> in > >> >> >> >> >> > the right direction. > >> >> >> >> >> > > >> >> >> >> >> > I agree with the structure as such, it is just at the > >> >> >> >> >> > moment > >> a > >> >> >> >> >> > pain > >> >> >> >> >> > in > >> >> >> >> >> the > >> >> >> >> >> > neck when you search information (and not to forget, my > old > >> >> >> >> >> > horse, > >> >> >> >> >> > the > >> >> >> >> >> > multiple logins). > >> >> >> >> >> > >> >> >> >> >> Is called transitional period. It seems Apache people dont > >> >> >> >> >> want > >> >> >> >> >> to > >> >> >> >> >> deal with PHP, something that Sun didn't mind as much. So > >> >> >> >> >> most > >> >> >> >> >> infrastructure (Mediawiki, PHPBBs, Drupal) are in a virtual > >> >> >> >> >> environment at the moment. > >> >> >> >> >> > >> >> >> >> >> Multiple logins have always been an issue in OOo as a whole, > >> the > >> >> >> >> >> idea > >> >> >> >> >> of implementing OpenID came out several times, but many > >> >> >> >> >> people > >> >> >> >> >> didnt > >> >> >> >> >> seem to mind just having multiple accounts, so it never > >> >> >> >> >> gained > >> >> >> >> >> traction. > >> >> >> >> >> > >> >> >> >> >> Now at apache, doesnt seem that different except for pootle > >> that > >> >> >> share > >> >> >> >> >> your commit credentials with http://people.apache.org but > >> >> >> >> >> neither > >> >> >> >> >> forums, extensions or cwiki share these credentials. > >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> >> > I am just writing the last pages on "localization of AOO" > >> >> >> describing > >> >> >> >> >> > the > >> >> >> >> >> > current l10n process as ground work for a discussion on > >> >> >> >> >> > where > >> >> >> >> >> > we > >> >> >> >> >> > want > >> >> >> >> >> > to > >> >> >> >> >> > go. > >> >> >> >> >> > >> >> >> >> >> Again this should be included in MWiki IMO so there is no > >> >> >> >> >> 'old > >> >> >> >> >> localization' and 'new localization'. I suggest a good start > >> >> >> >> >> would > >> >> >> >> >> be > >> >> >> >> >> to create links between them and mark outdated information > as > >> >> such. > >> >> >> >> >> MWiki had special tags for this. > >> >> >> >> >> > >> >> >> >> >> <div> > >> >> >> >> >> <span style="border:1px solid #CC7777; background-color: > >> >> >> >> >> #FFEDED; > >> >> >> >> >> padding: 4px; text-align: left; font-weight: bold; > >> >> >> >> >> margin-bottom: > >> >> >> >> >> 20px;"> > >> >> >> >> >> [[image:documentation_exclamation.png|40px]] This article is > >> >> >> outdated. > >> >> >> >> >> </span> > >> >> >> >> >> </div> > >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> >> > I was suggested to make a subpage of the current page in > >> Wiki, > >> >> >> >> >> > that > >> >> >> >> >> > will > >> >> >> >> >> be > >> >> >> >> >> > easy for me, but at the same time shows, that we need to > >> >> >> >> >> > make > >> >> >> >> >> > a > >> >> >> >> >> > deadline, > >> >> >> >> >> > freeze the wiki for a couple of days and divide the pages. > >> >> >> >> >> > > >> >> >> >> >> > rgds > >> >> >> >> >> > JanI. > >> >> >> >> >> > > >> >> >> >> >> > On 16 October 2012 14:34, Rob Weir <[email protected]> > >> wrote: > >> >> >> >> >> > > >> >> >> >> >> >> On Tue, Oct 16, 2012 at 6:42 AM, RGB ES > >> >> >> >> >> >> <[email protected] > >> > > >> >> >> wrote: > >> >> >> >> >> >> > 2012/10/16 jan iversen <[email protected]> > >> >> >> >> >> >> > > >> >> >> >> >> >> >> I know...it is just a matter of how many accounts do > >> >> >> >> >> >> >> you > >> >> want > >> >> >> to > >> >> >> >> >> >> maintain > >> >> >> >> >> >> >> in order to help on AOO. > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> If I look for information regarding AOO I would look > in > >> >> >> >> >> >> >> wiki.openoffice.org, > >> >> >> >> >> >> >> I would not think of cwiki.apache.org > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> or have I misunderstood something ? > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> rgds > >> >> >> >> >> >> >> Jan I. > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> > If my memory do not betray me (I cannot find the > thread) > >> >> there > >> >> >> >> >> >> > was > >> >> >> >> >> >> > (sort-of) an agreement to use cwiki for development > >> matters > >> >> >> >> >> >> > and > >> >> >> >> >> >> > the > >> >> >> >> >> >> > traditional wiki for community support. But it is > better > >> to > >> >> >> >> >> >> > not > >> >> >> >> >> >> > trust > >> >> >> >> >> >> > my > >> >> >> >> >> >> > memory... ;) > >> >> >> >> >> >> > > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> Historically there was a single website, > >> >> >> >> >> >> www.openoffice.orgthat > >> >> >> >> >> >> was > >> >> >> >> >> >> both user-facing and project-facing. It was a single > >> >> >> >> >> >> domain > >> >> >> >> >> >> (openoffice.org) as well as subdomains for distinct > >> projects. > >> >> >> >> Behind > >> >> >> >> >> >> this domain were static web pages, a wiki, forums, > >> extensions > >> >> >> >> >> >> and > >> >> >> >> >> >> template libraries, etc. So behind the scenes it was > >> >> >> >> >> >> quite > >> >> >> >> >> >> complex, > >> >> >> >> >> >> but to everyone it looked like "openoffice.org". > >> >> >> >> >> >> > >> >> >> >> >> >> With the move to Apache the services were arranged > >> >> >> >> >> >> differently. > >> >> >> >> >> >> Bugzilla is under an apache.org domain. Apache > >> >> Infrastructure > >> >> >> >> >> >> supported CWiki and MoinMoin, but not MWiki. And all > >> >> >> >> >> >> Apache > >> >> >> >> >> >> projects > >> >> >> >> >> >> have an official page in the apache.org domain. > >> >> >> >> >> >> > >> >> >> >> >> >> So the idea was that we would have two different > >> experiences: > >> >> a > >> >> >> >> >> >> user-facing "product" website at openoffice.org, where > we > >> >> focus > >> >> >> on > >> >> >> >> >> >> user-facing tasks like product information, downloads and > >> >> >> >> >> >> support. > >> >> >> >> >> >> And a project-facing website, at an Apache domain, with > >> >> >> information > >> >> >> >> >> >> for volunteers participating on the project. So product > >> >> >> >> >> >> versus > >> >> >> >> >> >> project. The split is imperfect, since there is still a > >> >> >> >> >> >> lot > >> >> >> >> >> >> of > >> >> >> >> >> >> project-related content on the openoffice.org domain. > But > >> I > >> >> >> think > >> >> >> >> >> >> we've done a good job at making the user experience be > >> clean. > >> >> A > >> >> >> >> >> >> user > >> >> >> >> >> >> going to the www.openoffice.org home page does not > easily > >> >> >> >> >> >> find > >> >> >> >> >> >> outdated content. However, some of the native language > >> >> >> >> >> >> home > >> >> >> pages, > >> >> >> >> >> >> the ones not maintained yet, have a worse experience. > >> >> >> >> >> >> > >> >> >> >> >> >> -Rob > >> >> >> >> >> >> > >> >> >> >> >> >> > Regards > >> >> >> >> >> >> > Ricardo > >> >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> -- > >> >> >> >> >> Alexandro Colorado > >> >> >> >> >> PPMC Apache OpenOffice > >> >> >> >> >> http://es.openoffice.org > >> >> >> >> >> > >> >> >> >> > > >> >> >> >> > >> >> >> >> > >> >> >> >> -- > >> >> >> >> Alexandro Colorado > >> >> >> >> PPMC Apache OpenOffice > >> >> >> >> http://es.openoffice.org > >> >> >> >> > >> >> >> > > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Alexandro Colorado > >> >> >> PPMC Apache OpenOffice > >> >> >> http://es.openoffice.org > >> >> >> > >> >> > > >> >> > >> >> > >> >> -- > >> >> Alexandro Colorado > >> >> PPMC Apache OpenOffice > >> >> http://es.openoffice.org > >> >> > >> > > >> > >> > >> -- > >> Alexandro Colorado > >> PPMC Apache OpenOffice > >> http://es.openoffice.org > >> > > > > > -- > Alexandro Colorado > PPMC Apache OpenOffice > http://es.openoffice.org >
