Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)
On 24 September 2012 03:50, Rob Weir rabas...@gmail.com wrote: On Sep 23, 2012, at 10:15 PM, Dennis E. Hamilton orc...@apache.org wrote: Rob, I recently took a look at http://incubator.apache.org/projects/openofficeorg.html to see if I could derive that list from the Roster. What gave me pause is that the list is apparently maintained in XML. I could not find anywhere that MarkDown is used. Is that correct? Correct. It is XML. It used to require that I check out the whole directory, update the XML, run an ant script to generate the HTML and then check in both the XML and HTML. This is much simplified by the CMS which does the template generation behind the scenes. I could still mechanically derive the XML elements that are used now, although it is a bit more complicated than search and replace on a CSV of an extract of the roster. If I were to do that, I would also indicate who is on the PPMC. Any suggestions? I'm not sure we need to maintain that status file once we graduate. I think it is more of a podling tracking thing. So it might be Yes, it is for active podlings only. No need to update it once graduated, though it does need to be completed before graduation. The other file that needs to be updated by podlings is podlings.xml. Note that http://people.apache.org/committers-by-project.html#ooo is created automatically from the SVN authz file (where podling committers are listed) plus LDAP groups. simplest if we just manually update it for now. But longer term it would be good to be able to generate a page for the project website from the Roster. The ODF Toolkit has an XSLTRunner component that could be used for this. Not sure that's necessary. You could just link to the appropriate sections in the above file. -Rob - Dennis -Original Message- From: Rob Weir [mailto:robw...@apache.org] Sent: Sunday, September 23, 2012 17:41 To: ooo-dev@incubator.apache.org Subject: Re: New committer: Chen ZuoJun On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton orc...@apache.org wrote: The Apache OpenOffice PPMC announces the addition of committer Chen ZuoJun, zjchen@ apache.org The list of all current podling committers is at: http://people.apache.org/committers-by-project.html#ooo. And one other place: http://incubator.apache.org/projects/openofficeorg.html That page is part of the IPMC's tracking of podling status and feeds into their Status of the Clutch report: http://incubator.apache.org/clutch.html Some may recall that we had a reporter use the status of the clutch report to claim that the project was not growing. That was when we were not updating the report. Since that is the official IPMC view of the podlings, it is important that we keep this information up-to-date, until the project graduates. I was updating this status page whenever a new committer was voted in. It would be great if someone else could take this over now. When a new committer is added, the status file needs to be updated in two places. 1) Added as a News item. Automation depends on the wording, so don't be clever. Just follow the examples there. 2) Added in the list of committers. This can most easily be edited via the Apache CMS. [ ... ]
Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)
On 24 September 2012 13:50, Dave Fisher dave2w...@comcast.net wrote: On Sep 24, 2012, at 4:34 AM, Rob Weir wrote: On Mon, Sep 24, 2012 at 5:37 AM, sebb seb...@gmail.com wrote: On 24 September 2012 03:50, Rob Weir rabas...@gmail.com wrote: On Sep 23, 2012, at 10:15 PM, Dennis E. Hamilton orc...@apache.org wrote: Rob, I recently took a look at http://incubator.apache.org/projects/openofficeorg.html to see if I could derive that list from the Roster. What gave me pause is that the list is apparently maintained in XML. I could not find anywhere that MarkDown is used. Is that correct? Correct. It is XML. It used to require that I check out the whole directory, update the XML, run an ant script to generate the HTML and then check in both the XML and HTML. This is much simplified by the CMS which does the template generation behind the scenes. I could still mechanically derive the XML elements that are used now, although it is a bit more complicated than search and replace on a CSV of an extract of the roster. If I were to do that, I would also indicate who is on the PPMC. Any suggestions? I'm not sure we need to maintain that status file once we graduate. I think it is more of a podling tracking thing. So it might be Yes, it is for active podlings only. No need to update it once graduated, though it does need to be completed before graduation. The other file that needs to be updated by podlings is podlings.xml. Note that http://people.apache.org/committers-by-project.html#ooo is created automatically from the SVN authz file (where podling committers are listed) plus LDAP groups. simplest if we just manually update it for now. But longer term it would be good to be able to generate a page for the project website from the Roster. The ODF Toolkit has an XSLTRunner component that could be used for this. Not sure that's necessary. You could just link to the appropriate sections in the above file. Is there any easy way to track PMC membership? Maybe that be derived from the authz for the eventual /pmc/openoffice tree?Eventually we want an easy way to generate a roster that lists committers but also identifies PMC members. Sebb answered, but sometimes examples are needed. PMCs have authz as well. Here is the page for the POI PMC: http://people.apache.org/committers-by-project.html#poi-pmc Note that this is derived from the LDAP committee group, but AIUI the canonical location for PMC membership is https://svn.apache.org/repos/private/committers/board/committee-info.txt The LDAP group needs to be kept in sync with the above file; updating both is the responsibility of the PMC chair (who will have sufficient karma). Regards, Dave -Rob -Rob - Dennis -Original Message- From: Rob Weir [mailto:robw...@apache.org] Sent: Sunday, September 23, 2012 17:41 To: ooo-dev@incubator.apache.org Subject: Re: New committer: Chen ZuoJun On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton orc...@apache.org wrote: The Apache OpenOffice PPMC announces the addition of committer Chen ZuoJun, zjchen@ apache.org The list of all current podling committers is at: http://people.apache.org/committers-by-project.html#ooo. And one other place: http://incubator.apache.org/projects/openofficeorg.html That page is part of the IPMC's tracking of podling status and feeds into their Status of the Clutch report: http://incubator.apache.org/clutch.html Some may recall that we had a reporter use the status of the clutch report to claim that the project was not growing. That was when we were not updating the report. Since that is the official IPMC view of the podlings, it is important that we keep this information up-to-date, until the project graduates. I was updating this status page whenever a new committer was voted in. It would be great if someone else could take this over now. When a new committer is added, the status file needs to be updated in two places. 1) Added as a News item. Automation depends on the wording, so don't be clever. Just follow the examples there. 2) Added in the list of committers. This can most easily be edited via the Apache CMS. [ ... ]
Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)
On 24 September 2012 22:35, Shane Curcuru a...@shanecurcuru.org wrote: On 9/24/2012 7:34 AM, Rob Weir wrote: ...snip... Is there any easy way to track PMC membership? Maybe that be derived from the authz for the eventual /pmc/openoffice tree?Eventually we want an easy way to generate a roster that lists committers but also identifies PMC members. TLPs have a slightly different way to track PMC members, specified here: http://www.apache.org/dev/pmc.html#newpmc PMC membership is mostly an organizational thing, so I'm not sure there's a simple automated way to detect it. Strictly speaking, PMC members are those that have been agreed by the board. Either via TLP creation, or subsequent additions/removals which are done via board request/ACK mails. However, PMC chairs are supposed to keep the committee-info.txt and LDAP committee groups up to date. However committers can view some of the great tools at whimsy, and I'd bet someone could find the code there that auto-parses both committer and PMC lists, and repurpose it to create an AOO specific page that could be public: The people.apache.org pages (see else-thread) are public ... https://whimsy.apache.org/ There's a look under the hood link that takes you to the source in the infra SVN tree. - Shane
Re: [DISCUSS][PMC] Proposed PMC List
On 20 September 2012 07:45, Andrea Pescetti pesce...@apache.org wrote: RGB ES wrote: 2012/9/19 Dennis E. Hamilton I recommend that the process continue. My only objection is that having secret nominations is not compatible with the Apache Way ... I recommend that no one accept nominations privately and that those who have already sent theirs via any back-channel use ooo-private OK. The important thing is that the process can continue. It might well be that nobody prefers to state his preferences in private (meaning: somewhere else than ooo-dev): as I wrote, it was not a personal concern, I just wondered if allowing it would increase participation in this nomination phase (and at the same time I encouraged those, if any, who preferred secret nominations/lists to speak up, and nobody did so far, which probably means I was simply wrong and everybody is fine with public nominations/lists). +1 (Even if I see no point on hiding the vote). I was going to answer that secret ballot is a basic principle, but indeed, now that I think about it, it might be that there is no such thing as a secret ballot in the Apache way, at least for normal operations... http://www.apache.org/foundation/voting.html does not mention this possibility. AFAIK that applies to code and releases only, not people. Once a PMC exists, new members must be nominated and discussed on the private@tlp list. Votes are held on the private list, so is not secret, but it is not public either. ASF members are nominated on the members list (and in members-only files). ASF member voting is secret. Board members are nominated on the members list. Voting is secret. Good to know. But we can come back to this at a later stage and let the current nomination phase continue. Regards, Andrea.
Re: What is a good Project Management Committee?
On 7 September 2012 22:26, Rob Weir rabas...@gmail.com wrote: On Sep 7, 2012, at 8:42 AM, Andrew Rist andrew.r...@oracle.com wrote: I'm not particularly satisfied with current PMC selection process. I think the first pass was actually fairly reasonable, and fairly quickly resulted in a list that contains the people who are serious about the project. Unfortunately, we haven't been able to find consensus on the next step. I'd like to propose a different way to look at this which may lead us to a better way to move forward. I think we can avoid the need to organize the next step around '-1' (i.e. speaking out against potential PMC members - discussions around who to leave off), and instead create an affirmative process where we identify who we want on. What is a good Project Management Committee? Here's my start (please expand on this): * Representative of the diversity of tasks in the community (developers, web/wiki/forum, translators, testers, UX, release, marketing, press, ecosystem, infrastructure) * Representative of the geographical diversity in the community * Made up of the most involved members of the community * Able and Competent to perform required ASF functions (overseeing releases and developing the community) * Represents the community in the best possible light While on one hand I understand why so many of us want to be on the PMC, a large PMC is not necessarily in the best interest of the project. The PMC should not be making decisions about the direction of the project and on who gets to do what - the PMC should be mostly involved with voting in new committers and approving releases. The direction of the project should be determined on ooo-dev, and by the people who are active in the parts of the community listed above. My Proposal for the next step in the PMC selection process: I suggest that each of us provide up to 10 names for the PMC. no spreadsheet - no voting - no '-1s' for now. Just an affirmative list of the 10 people you think should be doing the work of the PMC. (the list of names we have produced so far is a great place to start for your list, but it is not exclusive) Anyone can play! PPMC members, committers, the community. Next we use this to produce a list of the group getting the most votes. (using PPMC and committer lists as more binding) We can use this to produce the next pass at the proposed PMC roster, hopefully a PMC of around 20 members. Interesting idea. Another way of keeping it small and focused would be to rotate all committers in over time, say 20 at a time for 6 months at a time. Everyone gets a turn, no one left out and power does not concentrate. Note that PMC additions and removals require board approval (currently via ACK request/reply and 72hr wait). AIUI this is because the board delegates certain responsibilities to the PMC, so the board must be involved. Also there is a file (committee-info.txt) and LDAP group that need to be maintained. == PMC members have binding votes on releases (and can vote new committers/PMC members), but otherwise don't have any additional powers compared with committers. I'm not sure I understand why a large PMC would be a problem, so I don't see why rotation should be desirable. AFAIK rotation does not happen in any existing TLP. == Podlings with smaller numbers of committers tend to graduate with a PMC consisting of all the still active committers, but there is no requirement for all TLP committers to be PMC members. Some TLPs automatically add new committers to the PMC, but some wait until the committer has been around for a while to prove themselves - no point adding someone to the PMC who is not going to stick around. [In the latter case there may be a lower barrier to inviting someone to committership.]
Re: 27MB odt file in svn
On 29 August 2012 15:43, Joost Andrae joost.and...@gmx.de wrote: Hi Rob, snip/ Quite probable multiple copies of the same binary are stored within the SVN system if you branch the source tree. SVN branches are cheap copies; they don't copy the contents. If the object does not change, then only one copy of it is ever stored. snip/
Re: [ANNOUNCEMENT] Apache OpenOffice 3.4.1 (incubating) released
On 24 August 2012 09:20, Rory O'Farrell ofarr...@iol.ie wrote: On Thu, 23 Aug 2012 18:01:42 -0400 Maurice Howe maur...@stny.rr.com wrote: Got a warning msg that your product was unsafe, so I deleted the download. Here's the msg. snip I have this morning scanned my Windows XP computer on which is installed yesterday's release of AOO 3.4.1 using AVG Free edition 2012.0.2197 (this morning's update) at the most detailed settings and it has received a clean bill of health. The question that might arise in connection with the original post is that of the filename/download site; if it is from a legitimate (i.e. Apache controlled site) there should be no worries. It was in the past not unusual for new releases of OOo to give false positives on many virus scanners - the hooks for online updating registered sometimes as poentialy unwanted programs/possible trojans. As another poster (Dan?) pointed out, it is possible to check the Md5Sums of the downloaded file against the MD5Sum list on the Apache site, to be certain that it is exactly the file prepared and released by Apache. If these sums check out then all should be well. AIUI that's not possible to be *certain* that the file is identical [1]. Hashes are fine for checking that a download has not been corrupted/truncated in transit, because the chance of a hash collision in such a case is vanishingly small. But they are not generally considered sufficiently robust to *prove* that the download is what it appears to be. It is theoretically possible to create two different downloads with the same hash. Obviously if the hash check fails, then there is a problem, but a successful check does not provide 100% proof. Checking the detached signature for the download is much more secure, but is of course a bit harder to do. [1] http://www.apache.org/dev/release-signing#secure-hash-algorithms -- Rory O'Farrell ofarr...@iol.ie
Re: proposed new directory structure for future releases
On 24 August 2012 10:08, Jürgen Schmidt jogischm...@gmail.com wrote: On 8/23/12 11:37 PM, Kay Schenk wrote: On 08/23/2012 01:14 PM, Marcus (OOo) wrote: Am 08/23/2012 10:02 PM, schrieb Rob Weir: On Thu, Aug 23, 2012 at 3:37 PM, RGB ESrgb.m...@gmail.com wrote: 2012/8/23 Kay Schenkkay.sch...@gmail.com: Way back in late April, Juergen proposed a new directory structure for release packs than what we have now which is essentially: /stable/VERSION/en-US items /localized/lang abbreviation/VERSION/lang items there are some other areas in SF as well and I don't know if they're still being used Could we restart the discussion, or just again send the proposed structure, on what the ideal structure would look like so we could get to work on modifying the download scripts? Thanks. -- MzK As a child my family's menu consisted of two choices: take it or leave it. -- Buddy Hackett Warning: Layman comment following. Even if en-US is the base for all the other builds, I see no need to completely separate it from the rest. IMO, a structure like /stable/VERSION/lang abbreviation/etcetera werelang abbreviation includes en-US at the same level of all the other localizations would be perfectly clear to anyone. +1 This weird split complicates scripting operations on the tree. We could probably also eliminate the base of /stable. We don't release unstable code, do we? correct, and I think the schema that RGB currently proposes without the /stable is what Juergen basically proposed if memory serves. (I'm too lazy to go look for it. :/ ) I don't know if it's wanted by us or allowed by ASF: We could release Beta versions or RCs in a different dir than stable/. Then it would make sense to keep it. Otherwise you are right. Right now, since we are not releasing betas and I don't see this happening in the future given the ASF definition of release, we have no need for a /stable vs anything else. more or less but with going back to my proposal I think Rob made a good proposal with some minimal but useful differentiation. The only thing I woudl change is src = source because we already have it ;-) /ooo/VERSION/source /ooo/VERSION/bin/LANG/ /ooo/VERSION/bin/SDK/ It might be better to use binaries. This is often used by ASF projects. It is plural because there are often multiple builds. It also cannot be confused with bin = wastebin. [In the US they use can == trashcan; the UK use bin == wastebin] Now -src and -bin are fine as part of a file name, but might be misinterpreted as a folder name. For developers, /bin/ has very different connotations (/usr/bin etc), but for end-users, they might be wary of downloading something that comes from what might as well be called: /ooo/VERSION/trash/ or /ooo/VERSION/waste/ Just a thought. At a level higher we have another split, between source and binaries, where binaries are in /files and source is in VERSION. So: /ooo/3.4.1/source here /ooo/files/stable/de/3.4.1/binaries here This might be harmonized as: /ooo/VERSION/src /ooo/VERSION/bin/LANG/ /ooo/VERSION/bin/SDK yes. Hopefully Juergen will weigh in soonish. not really necessary, I think we are more or less all on the same track ;-) Juergen (who is moving slowly over in vacation mode) Or just /ooo/VERSION/ to get the most flat structure. Maybe /ooo/VERSION/src/ /ooo/VERSION/bin/ if it's needed to separate source and binary files. Marcus
Re: [ANNOUNCEMENT] Apache OpenOffice 3.4.1 (incubating) released
On 24 August 2012 11:51, Rory O'Farrell ofarr...@iol.ie wrote: On Fri, 24 Aug 2012 11:31:05 +0100 sebb seb...@gmail.com wrote: On 24 August 2012 09:20, Rory O'Farrell ofarr...@iol.ie wrote: On Thu, 23 Aug 2012 18:01:42 -0400 Maurice Howe maur...@stny.rr.com wrote: Got a warning msg that your product was unsafe, so I deleted the download. Here's the msg. snip I have this morning scanned my Windows XP computer on which is installed yesterday's release of AOO 3.4.1 using AVG Free edition 2012.0.2197 (this morning's update) at the most detailed settings and it has received a clean bill of health. The question that might arise in connection with the original post is that of the filename/download site; if it is from a legitimate (i.e. Apache controlled site) there should be no worries. It was in the past not unusual for new releases of OOo to give false positives on many virus scanners - the hooks for online updating registered sometimes as poentialy unwanted programs/possible trojans. As another poster (Dan?) pointed out, it is possible to check the Md5Sums of the downloaded file against the MD5Sum list on the Apache site, to be certain that it is exactly the file prepared and released by Apache. If these sums check out then all should be well. AIUI that's not possible to be *certain* that the file is identical [1]. Hashes are fine for checking that a download has not been corrupted/truncated in transit, because the chance of a hash collision in such a case is vanishingly small. But they are not generally considered sufficiently robust to *prove* that the download is what it appears to be. It is theoretically possible to create two different downloads with the same hash. Obviously if the hash check fails, then there is a problem, but a successful check does not provide 100% proof. Checking the detached signature for the download is much more secure, but is of course a bit harder to do. [1] http://www.apache.org/dev/release-signing#secure-hash-algorithms -- Rory O'Farrell ofarr...@iol.ie I'm not doubting your remarks above about the possibility of duplicate hashes, but for most purposes the hash check is probably sufficient. Yes. In any event, the timescale involved of some few hours after release would make the possibility of a rogue hash matching file quite remote (I hope!). Actually there will be at least 3-4 days when the files and hashes are available during release votes. But more likely the rogue file would be published later when it would still catch some downloads. -- Rory O'Farrell ofarr...@iol.ie
Re: OOO: missing group write permissions under /dist
On 22 August 2012 18:50, Juergen Schmidt jogischm...@gmail.com wrote: On 8/22/12 5:20 PM, sebb wrote: Checking /www/www.apache.org/dist/incubator The following entries don't have group write enabled. This can cause problems later, so please fix, Thanks! 54214290 6 drwxr-sr-x 3 jsc incubator 3 Aug 21 19:32 ./ooo/3.4.1 54214291 6 drwxr-sr-x 2 jsc incubator 14 Aug 21 19:32 ./ooo/3.4.1/source I thought I had send it already, it is fixed A new one has appeared: 42619133 34535 -rwxr-xr-x 1 jsc jsc 17579189 Aug 23 13:33 ./ooo/files/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_MacOS_x86_langpack_en-US.dmg Check your umask. Juergen
Re: [DISCUSS] Proposed PMC Chair nomination process
On 23 August 2012 19:22, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I suggest that the initial Project Management Committee (PMC) needs to be identified before the election of a Chair from that body is undertaken. The initial proposed PMC for other podlings has usually been taken from the PPMC membership, but dropping any inactive (or unwilling) members. Also, this seems like a very good time to review, for the benefit of all here, what the duties of PMC members are and, with respect to that, what the specific responsibilities of the Chair are and what the special standing of the Chair is so its accountability can be carried out. http://www.apache.org/foundation/how-it-works.html#pmc-members http://www.apache.org/dev/pmc.html http://www.apache.org/dev/pmc.html#chair The PMC chair is a position of responsibility (to the PMC and Board) rather than authority over the PMC. - Dennis -Original Message- From: Rob Weir [mailto:robw...@apache.org] Sent: Thursday, August 23, 2012 10:36 To: ooo-dev@incubator.apache.org Subject: [DISCUSS] Proposed PMC Chair nomination process Now that the community graduation ballot has passed, one of our next tasks is to identify a PMC Chair. You can read about the duties of a PMC Chair here: http://www.apache.org/dev/pmc.html#chair How do we want to do this? A strawman proposal: 1) Nominations would be open for 72 hours. Anyone can nominate someone for the role. Self-nominations are fine. And of course nominations can be declined. 2) If there is only one nomination, then we are done, provided there are no sustained objections. 3) If there is more than one nomination we discuss on the list for another 72 hours. Discussion would primarily be on ooo-dev, but some subjects might be directed to ooo-private. 4) If after 72-hours discussion there are still two or more nominees then we vote. Everyone would be welcome to vote, but binding votes would be from PPMC members. If there are more than 2 candidates we would probably need to use a more complicated voting system, or have a run-off vote if none of the nominees receive an outright majority. Any improvements or alternatives to this basic scheme? Regards, -Rob
Re: proposed new directory structure for future releases
On 23 August 2012 21:14, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 08/23/2012 10:02 PM, schrieb Rob Weir: On Thu, Aug 23, 2012 at 3:37 PM, RGB ESrgb.m...@gmail.com wrote: 2012/8/23 Kay Schenkkay.sch...@gmail.com: Way back in late April, Juergen proposed a new directory structure for release packs than what we have now which is essentially: /stable/VERSION/en-US items /localized/lang abbreviation/VERSION/lang items there are some other areas in SF as well and I don't know if they're still being used Could we restart the discussion, or just again send the proposed structure, on what the ideal structure would look like so we could get to work on modifying the download scripts? Thanks. -- MzK As a child my family's menu consisted of two choices: take it or leave it. -- Buddy Hackett Warning: Layman comment following. Even if en-US is the base for all the other builds, I see no need to completely separate it from the rest. IMO, a structure like /stable/VERSION/lang abbreviation/etcetera werelang abbreviation includes en-US at the same level of all the other localizations would be perfectly clear to anyone. +1 This weird split complicates scripting operations on the tree. We could probably also eliminate the base of /stable. We don't release unstable code, do we? I don't know if it's wanted by us or allowed by ASF: We could release Beta versions or RCs in a different dir than stable/. Then it would make sense to keep it. Otherwise you are right. At a level higher we have another split, between source and binaries, where binaries are in /files and source is in VERSION. So: /ooo/3.4.1/source here /ooo/files/stable/de/3.4.1/binaries here This might be harmonized as: /ooo/VERSION/src /ooo/VERSION/bin/LANG/ /ooo/VERSION/bin/SDK Or just /ooo/VERSION/ to get the most flat structure. Maybe /ooo/VERSION/src/ /ooo/VERSION/bin/ if it's needed to separate source and binary files. Having a top-level version dir works well with svnpubsub. The staging directory is at https://dist.apache.org/repos/dist/dev/ and the release (live) dirs are at https://dist.apache.org/repos/dist/release/ This makes it particularly easy in to rename dev/version/ to release/version/ once a release vote passes, as there is a containing folder for everything. Other arrangements are possible, but are harder to promote from dev/ to release/ As to non-GA builds, several other TLPs release -ALPHA and -BETA versions; if such suffices are included in the folder and artifact version names it makes the status obvious. Marcus
Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/
On 22 August 2012 07:05, Andrea Pescetti pesce...@apache.org wrote: sebb wrote: On 21 August 2012 22:23, Daniel Shahaf wrote: Why? Could very well have a publish all changes mode (the current only option) alongside the cherry picking (publish only selected file) mode. This thread started because something was published inadvertently. No, this thread started because people (including me) who did want to publish their changes only, and who routinely used the Diff command in the CMS to examine what would be published, were forced to take the all or nothing approach (you will find me noting this in the log messages too). I was going by the following comments: Sorry but IMHO this process failed. Just today evening (Hamburg time) someone has published again website changes. If we rely on a process that is so fragile, then IMHO we shouldn't do this. Because there will be always somebody: If the purpose of the enhancement is to prevent this happening, then there needs to be some barrier that prevents inadvertent publication. This would be an extra guarantee, but probably an unnecessary complication for what we have seen so far. Ability to publish one directory only would already help a lot. Regards, Andrea.
OOO: missing group write permissions under /dist
Checking /www/www.apache.org/dist/incubator The following entries don't have group write enabled. This can cause problems later, so please fix, Thanks! 54214290 6 drwxr-sr-x 3 jsc incubator 3 Aug 21 19:32 ./ooo/3.4.1 54214291 6 drwxr-sr-x 2 jsc incubator 14 Aug 21 19:32 ./ooo/3.4.1/source
Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/
On 21 August 2012 13:43, Daniel Shahaf danie...@apache.org wrote: Jürgen Schmidt wrote on Tue, Aug 21, 2012 at 14:38:34 +0200: On 8/20/12 10:02 PM, Ariel Constenla-Haile wrote: On Mon, Aug 20, 2012 at 09:49:52PM +0200, Marcus (OOo) wrote: @all: Sorry but IMHO this process failed. Just today evening (Hamburg time) someone has published again website changes. If we rely on a process that is so fragile, then IMHO we shouldn't do this. Because there will be always somebody: - who doesn't know this - who isn't aware of the consequences of her/his changes (do you all know that a change on a NL webpage will also publish everything else in staging?) - who hasn't seen a please don't publish the website until further notice mail (to be honest, I haven't seen a clear note that is forbidden at the moment, too) - etc. The other solution would be to completely not change anything (incl. no commits) to the website until the release is, e.g., 1 hour away which is also nothing I would like to see as it's not flexible enough. Are there other opinions/suggestions? The ideal would be if the CMS could have an option to lock publishing so that no-one publishes the site, not even by mistake. Sure someone from knows if this is possible or just an ideal, though impossible solution. or even a more fine grained publishing process by marking the files explicitly. I think of 2 mode, publish all or selected files only. That would be easy to implement (given a list of filenames you'd just svnmucc copy those files from staging/ to production/); check with Joe what he thinks of such a potential feature? This may be obvious to all readers, but just in case: For this to be fool-proof, I think there would need to be some way to prevent anyone bypassing the selection. Juergen
Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/
On 21 August 2012 22:23, Daniel Shahaf danie...@apache.org wrote: sebb wrote on Tue, Aug 21, 2012 at 16:04:12 +0100: On 21 August 2012 13:43, Daniel Shahaf danie...@apache.org wrote: Jürgen Schmidt wrote on Tue, Aug 21, 2012 at 14:38:34 +0200: On 8/20/12 10:02 PM, Ariel Constenla-Haile wrote: On Mon, Aug 20, 2012 at 09:49:52PM +0200, Marcus (OOo) wrote: @all: Sorry but IMHO this process failed. Just today evening (Hamburg time) someone has published again website changes. If we rely on a process that is so fragile, then IMHO we shouldn't do this. Because there will be always somebody: - who doesn't know this - who isn't aware of the consequences of her/his changes (do you all know that a change on a NL webpage will also publish everything else in staging?) - who hasn't seen a please don't publish the website until further notice mail (to be honest, I haven't seen a clear note that is forbidden at the moment, too) - etc. The other solution would be to completely not change anything (incl. no commits) to the website until the release is, e.g., 1 hour away which is also nothing I would like to see as it's not flexible enough. Are there other opinions/suggestions? The ideal would be if the CMS could have an option to lock publishing so that no-one publishes the site, not even by mistake. Sure someone from knows if this is possible or just an ideal, though impossible solution. or even a more fine grained publishing process by marking the files explicitly. I think of 2 mode, publish all or selected files only. That would be easy to implement (given a list of filenames you'd just svnmucc copy those files from staging/ to production/); check with Joe what he thinks of such a potential feature? This may be obvious to all readers, but just in case: For this to be fool-proof, I think there would need to be some way to prevent anyone bypassing the selection. Why? Could very well have a publish all changes mode (the current only option) alongside the cherry picking (publish only selected file) mode. This thread started because something was published inadvertently. If the purpose of the enhancement is to prevent this happening, then there needs to be some barrier that prevents inadvertent publication. BTW Joe, the equivalent code in svn should be the commit harvester in the client. Juergen
Re: [DRAFT] AOO 3.4.1 Release Announcement for Review
On 16 August 2012 19:06, Rob Weir robw...@apache.org wrote: https://blogs.apache.org/preview/OOo/?previewEntry=announcing_apache_openoffice_3_4 Comments are welcome. I found Support for Windows XP-Windows 8 (32-bit) a bit difficult to read at first. Perhaps put Support for Windows from XP up to Windows 8 (32-bit) Some updates I know we'll need are: 1) The 11 million downloads claim will go to 12 or 13 depending on when we release 2) The defect fix count should be updated. Does anyone have an accurate count? I think we want to count only net bugs fixed compared to AOO 3.4.0, not bugs that we both introduced and fixed in AOO 3.4.1. Perhaps we can take comments for a day or so, and I'll update to reflect feedback. At that point volunteers might prepare translations. Any translations we have at release time I can link to from the blog post. Regards, -Rob
Re: OO Sold on eBay
On 12 August 2012 17:38, Max Merbald max.merb...@gmx.de wrote: Hi, I'd say it's not very fair because probably not everyone knows OOO is available for free. It's kind of weird that someone is trying to make money with something which is available for free. The page does actually say (near the bottom) Please note that this software is a very good application and can be downloaded free from the internet However it does not link to the ASF, nor does it mention Apache. Note: OOo itself is free, however Internet access is generally not free. There may be people who prefer to pay for a CD rather than download software. Max Am 12.08.2012 18:19, schrieb Kay Schenk: On Sun, Aug 12, 2012 at 5:48 AM, dan roch dan.gum.tree...@gmail.com wrote: FYI I don't know if this goes agaist OO rules but this user on eBay is selling copies of OO. ebay user: allsorts-est-2011 auction http://www.ebay.co.uk/itm/Office-for-Home-and-Student-2007-2010-2012-For-Microsoft-Windows-XP-Vista-7-/110922521399?pt=UK_Computing_Software_Software_SRhash=item19d37f5b37#ht_8329wt_1026 This has come up before...there is no issue with selling ANY copy of OpenOffice (old or new) as long as the vendor complies with licensing or trademark requirements. This bit at the bottom -- *Items contained on this CD are under the terms of the GNU License, the GNU Lesser General Public Licences (LPGL) or the Mozilla Public Licence* well let's hope it's right. see also, our local Distribution FAQ-- http://www.openoffice.org/distribution/
Re: OO Sold on eBay
On 13 August 2012 01:29, Rob Weir robw...@apache.org wrote: On Sun, Aug 12, 2012 at 5:50 PM, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Aug 12, 2012 at 10:49 AM, Rob Weir robw...@apache.org wrote: On Sun, Aug 12, 2012 at 12:38 PM, Max Merbald max.merb...@gmx.de wrote: Hi, I'd say it's not very fair because probably not everyone knows OOO is available for free. It's kind of weird that someone is trying to make money with something which is available for free. I wonder... is there anything that prevents one of us from offering the same thing on eBay, but at a near-zero price? For example, would it be within eBay policy to have an auction for instructions for downloading OpenOffice? Give all the same marketing plugs for features, etc., but set it as a Buy Now price of 1-cent or something. Some users want a CD, because of bandwidth limitations. But the cost of information, in this case, should be nearly zero. -Rob You might want to check out seller requirements first... http://pages.ebay.com/help/sell/questions/sell-requirements.html I would think if we're willing to do this -- and set this up somehow, the answer is no unless ASF precludes this, which it might. Drew mentioned another eBay policy that said you could not sell access to downloaded software. You could only sell the media. Looking at the ebay auctions, some of them seem reasonable. $3 or $5 for a CD and packaging, shipping, etc., is not outrageous. But I am concerned that several of the auctions seem to be selling old versions of OpenOffice including 3.2 and 3.1. These earlier versions lack important security fixes and those who distribute old versions, without a warning, are putting their customers at risk. As a project we take great pains to ensure the users who download from our website get authentic versions of our software, the latest versions, not tampered with. We give the downloader ways of verifying this, with MD5 hashes and PGP signatures. But there is no current way that we can offer similar assurances to users who purchase a CD. (Anyone who thinks users will verify checksums or signatures on a CD is deluded.) Our options: 1) Do nothing. Bandwidth and access is increasing and this problem will solve itself...sometime. 2) Define voluntary requirements for distributors of OpenOffice. Those who agree to these requirements would be allowed use of a special logo and would be listed on our website. 3) One or more community members, acting outside of Apache, could organize to sell CD's on eBay at cost, and have eBay auction listings that are upfront and honest, explaining that the software is open source and can be downloaded for free. We can give the URL right in the listing. We would make it clear that the charge is only for convenience of having a CD delivered. Is it worth approaching eBay with our concerns? - ensuring that sellers credit (and link to) the ASF - ensuring that sellers provide clear information on the version supplied - ensuring that sellers provide the current version. - etc. Note: the seller page mentioned in this thread says: Open Office 3.3 ... * This is the very latest version and fully updated. That would be a good example of one of our concerns. Max Am 12.08.2012 18:19, schrieb Kay Schenk: On Sun, Aug 12, 2012 at 5:48 AM, dan roch dan.gum.tree...@gmail.com wrote: FYI I don't know if this goes agaist OO rules but this user on eBay is selling copies of OO. ebay user: allsorts-est-2011 auction http://www.ebay.co.uk/itm/Office-for-Home-and-Student-2007-2010-2012-For-Microsoft-Windows-XP-Vista-7-/110922521399?pt=UK_Computing_Software_Software_SRhash=item19d37f5b37#ht_8329wt_1026 This has come up before...there is no issue with selling ANY copy of OpenOffice (old or new) as long as the vendor complies with licensing or trademark requirements. This bit at the bottom -- *Items contained on this CD are under the terms of the GNU License, the GNU Lesser General Public Licences (LPGL) or the Mozilla Public Licence* well let's hope it's right. see also, our local Distribution FAQ-- http://www.openoffice.org/distribution/ -- MzK Never express yourself more clearly than you are able to think. -- Niels Bohr
Re: Download URL of commons-logging
On 7 August 2012 09:00, Andre Fischer awf@gmail.com wrote: On 06.08.2012 21:20, sebb wrote: On 6 August 2012 16:31, Andre Fischer awf@gmail.com wrote: On 03.08.2012 12:45, sebb wrote: On 3 August 2012 09:09, Andre Fischer awf@gmail.com wrote: Hi all, I am currently cleaning up and improving the download mechanism of the external tarballs. Most of them (all that are used by the AOO34 branch) can now be found on apache-extras [1]. However, that is intended only as a fallback in case the tarballs can not be downloaded directly from their original download server. At the moment we use the SVN repository as a secondary fallback. I will remove that maybe next week. I need help regarding the original download site of one of the apache commons libraries. The general download page for commons-logging-1.1.1-src.tar.gz is [2]. I don't know how to produce a URL that does not contain a specific mirror but instead is resolved by the server. You could perhaps download from Maven Central instead: http://repo1.maven.org/maven2/commons-logging/ Is this an instance of maven that uses commons-logging or one that builds (and distributes) it? Not sure I understand the questions. That URL is where Maven projects will download Commons Logging from if they have a dependency (direct or indirect) on it. It is the default Maven repository which is embedded in Maven, but there's no reason why you should not download jars from it using Ant or any other build tool. So essentially this is the apache-extras of maven. Their own backup copy of commons-logging. No, it's not. It's the standard way of distributing Maven dependencies. In that case we can use our own where we can make sure that the right version is kept. You'll need to run that past infra. But why bother, when the Maven repository is available? It holds all released copies of commons-logging, and the servers are replicated to handle the bandwidth. -Andre Does anybody know how to do that? Andre [1] https://code.google.com/a/apache-extras.org/p/ooo-extras/ [2] http://commons.apache.org/logging/download_logging.cgi PS: I changed my email address from a...@a-w-f.de to awf@googlemail.com, but I am still the same person.
Re: Download URL of commons-logging
On 6 August 2012 16:31, Andre Fischer awf@gmail.com wrote: On 03.08.2012 12:45, sebb wrote: On 3 August 2012 09:09, Andre Fischer awf@gmail.com wrote: Hi all, I am currently cleaning up and improving the download mechanism of the external tarballs. Most of them (all that are used by the AOO34 branch) can now be found on apache-extras [1]. However, that is intended only as a fallback in case the tarballs can not be downloaded directly from their original download server. At the moment we use the SVN repository as a secondary fallback. I will remove that maybe next week. I need help regarding the original download site of one of the apache commons libraries. The general download page for commons-logging-1.1.1-src.tar.gz is [2]. I don't know how to produce a URL that does not contain a specific mirror but instead is resolved by the server. You could perhaps download from Maven Central instead: http://repo1.maven.org/maven2/commons-logging/ Is this an instance of maven that uses commons-logging or one that builds (and distributes) it? Not sure I understand the questions. That URL is where Maven projects will download Commons Logging from if they have a dependency (direct or indirect) on it. It is the default Maven repository which is embedded in Maven, but there's no reason why you should not download jars from it using Ant or any other build tool. Does anybody know how to do that? Andre [1] https://code.google.com/a/apache-extras.org/p/ooo-extras/ [2] http://commons.apache.org/logging/download_logging.cgi PS: I changed my email address from a...@a-w-f.de to awf@googlemail.com, but I am still the same person.
Re: Download URL of commons-logging
On 3 August 2012 09:09, Andre Fischer awf@gmail.com wrote: Hi all, I am currently cleaning up and improving the download mechanism of the external tarballs. Most of them (all that are used by the AOO34 branch) can now be found on apache-extras [1]. However, that is intended only as a fallback in case the tarballs can not be downloaded directly from their original download server. At the moment we use the SVN repository as a secondary fallback. I will remove that maybe next week. I need help regarding the original download site of one of the apache commons libraries. The general download page for commons-logging-1.1.1-src.tar.gz is [2]. I don't know how to produce a URL that does not contain a specific mirror but instead is resolved by the server. You could perhaps download from Maven Central instead: http://repo1.maven.org/maven2/commons-logging/ Does anybody know how to do that? Andre [1] https://code.google.com/a/apache-extras.org/p/ooo-extras/ [2] http://commons.apache.org/logging/download_logging.cgi PS: I changed my email address from a...@a-w-f.de to awf@googlemail.com, but I am still the same person.
Re: [VOTE][DISCUSS]: Release Apache OpenOffice 3.4.1 (incubating)
On 31 July 2012 14:59, O.Felka olaf-openoff...@gmx.de wrote: Am 31.07.2012 15:45, schrieb Rob Weir: The only issue I saw is that when we install over 3.3.0 or 3.4.0, we leave behind the older version's unpacked files on the desktop, the files from the earlier install. Those files could be deleted to save disk space. But this is not a regression and is not a critical issue. -Rob It's not a common software behavior to delete old installation files and we shouldn't do that too. Surely that depends on the installation options? If the install is replacing/updating an existing installation, then it should remove any obsolete files. If the install is a parallel installation, then of course it should leave files for existing installs alone. Groetjes, Olaf
Re: Archiving the AOO 3.4.0
On 30 July 2012 06:44, Andrea Pescetti pesce...@apache.org wrote: Raphael Bircher wrote: I working at the moment on the Archive for the AOO 3.4.0. The big question is: Is it enough to archive only the langpacks and a en-US Version? Same Question also for older Versions. We would save a load of disk space at Apache. It would be better to archive everything we distributed officially. I know there is a lot of redundancy, but this is due to the fact that we are redundant also in our official distribution. AFAIK, it is a requirement to archive everything that has been released. Note that everything under /www/www.apache.org/dist/ [i.e. 0] is automatically copied to the ASF archive server [1]. AFAICT all the source and binary releases for 3.4.0 are present on the ASF systems; so it looks to me as though this has already happened automatically. Check the files under [1] to see. [0] http://www.apache.org/dist/incubator/ooo/ - ASF backup mirror [0] http://archive.apache.org/dist/incubator/ooo/ - ASF archives Regards, Andrea.
Re: Archiving the AOO 3.4.0
On 30 July 2012 15:14, Raphael Bircher r.birc...@gmx.ch wrote: Am 30.07.12 16:00, schrieb Rob Weir: On Mon, Jul 30, 2012 at 1:44 AM, Andrea Pescetti pesce...@apache.org wrote: Raphael Bircher wrote: I working at the moment on the Archive for the AOO 3.4.0. The big question is: Is it enough to archive only the langpacks and a en-US Version? Same Question also for older Versions. We would save a load of disk space at Apache. It would be better to archive everything we distributed officially. I know there is a lot of redundancy, but this is due to the fact that we are redundant also in our official distribution. +1. Archive whatever we release. If we want to solve the size issue then we need to change how we package OpenOffice releases. That will require some engineering work. If it was easy then someone would have already done it. But also the old archive is not compleete. If you are referring to versions created before OO joined the ASF, I don't think we need to archive those. We archive the full version for a while, and then we reduce it to the english version only AFAIK, we never delete archive files. This time it's only about 16 GB. but I'm not happy with the solution. Greetings Raphael -- My private Homepage: http://www.raphaelbircher.ch/
Re: Coding guideline or common rules
On 20 July 2012 22:22, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I've seen the comment about SCMs being sufficient for tracing the provenance of code and the changes that are made. That puzzles me. - History doesn't appear in source-code tarballs. - It requires the original SCM repository or a history-preserving port of the SCN to be available to interested parties. Basically, it is not a durable form of the information. Indeed, especially since SVN log messages are not versioned. I think log messages should only be used to inform the reader of the commit message why the commit was done. They should not be used for comments that are useful / necessary to the reader of the code; those should be included as comments in the code itself. [Though of course such comments can go in the log message as well.] However, does the end user of the source need to know provenance and history? Just sayin' ... DItto. - Dennis -Original Message- From: Pedro Giffuni [mailto:p...@apache.org] Sent: Friday, July 20, 2012 12:52 To: ooo-dev@incubator.apache.org Subject: Re: Coding guideline or common rules FWIW; - Original Message - ... Hi, I just stumbled over a commit message for the new UOF filter. I think we should agree on a common guideline for our code and how we contribute changes and bring them in the code. SCM's manage the change sets and the information who made the change, that means we don't need further comments like this ///Begin Added by wangyumin for uof2-filter from cs2c ... /// End Added by wangyumin on 2012-2-22 14:32:18 It is somewhat redundant and makes the code not really better readable. Can we agree on the common understanding that we don't need such comments and that we don't want them in the code. We should remove such comments wherever we see or find them. Indeed, I did mention in our local svn tutorial that those comments should be avoided. SVN does a wonderful job maintaining the origin information. Any opinions? As a side note, I recently found similar prominent begin/end lines in another project and the culprit on that project was the GPLv2 section 2a: You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. It's probable that old code from GPLd derivatives still carry such notes. Someone will have to clean them ;). Pedro.
Re: Registration
On 16 July 2012 17:26, Rob Weir robw...@apache.org wrote: On Mon, Jul 16, 2012 at 12:06 PM, Barry Storah barrysto...@yahoo.com wrote: Hi, I keep getting a message to Register Your OpenOffice.org, it is not possible as I always get the message - Internet Explorer cannot display the webpage, or from OpenOffice welcome page - get more information the webpage cannot be found. Hi Barry, It sounds like you are installing an old version of OpenOffice. The current version is 3.4 and it does not have a registration screen. You can download the latest version from http://download.openoffice.org. If for some reason you need to install the older version, you will get the behavior you reported. The registration went to a Sun/Oracle website that no longer is up. You can safely ignore that error. Would it be possible to get the destination URL re-instated? Ideally this would redirect to an ASF page (easier to maintain), where the user could be informed that there is a new version. Alternatively, the target page could do the same, with a link to the ASF for further information. Regards, -Rob Regards, Barry Storah
Re: Registration
On 16 July 2012 19:01, Rob Weir robw...@apache.org wrote: On Mon, Jul 16, 2012 at 1:13 PM, sebb seb...@gmail.com wrote: On 16 July 2012 17:26, Rob Weir robw...@apache.org wrote: On Mon, Jul 16, 2012 at 12:06 PM, Barry Storah barrysto...@yahoo.com wrote: Hi, I keep getting a message to Register Your OpenOffice.org, it is not possible as I always get the message - Internet Explorer cannot display the webpage, or from OpenOffice welcome page - get more information the webpage cannot be found. Hi Barry, It sounds like you are installing an old version of OpenOffice. The current version is 3.4 and it does not have a registration screen. You can download the latest version from http://download.openoffice.org. If for some reason you need to install the older version, you will get the behavior you reported. The registration went to a Sun/Oracle website that no longer is up. You can safely ignore that error. Would it be possible to get the destination URL re-instated? The registration URL's for OOo 3.3 look like this: https://registration2.services.openoffice.org/RegistrationWeb/register/GUID?prduct=OpenOffice.orglocale=encid-926117 So we should be able to handle this entirely with ASF. Good. But I thought there was another version that went directly to an Oracle domain. Maybe that was OOo 3.4 beta 1? Should catch that too. The question is: what could we do if even a fraction of the 8 million downloads of AOO 3.4.0 led to a registration? Suggest they join the ooo-announce list? (Can ezmlm handle 100,000 subscribers?) Follow us on Twitter? At the very least we can point them to the FAQ's and support pages. I'm not suggesting that 3.4.0 be updated to include registration, merely that it would be helpful to direct users of 3.3 to the new version, and let them know that the registration step has not failed. If there is some way we can help users by having them view a post-install registration screen, then we might add the registration step back in future versions. In the meantime, avoiding the error message for users of earlier versions would be a kindness to end users. For every one person who bothered to report the error, there are presumably many others who also encountered the error. -Rob Ideally this would redirect to an ASF page (easier to maintain), where the user could be informed that there is a new version. Alternatively, the target page could do the same, with a link to the ASF for further information. Regards, -Rob Regards, Barry Storah
Re: SVN mistake, Sorry
On 2 July 2012 09:52, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/30/12 3:11 PM, sebb wrote: On 29 June 2012 20:54, Dennis E. Hamilton dennis.hamil...@acm.org wrote: @Risto, I recommend using a00-3.4.1-incubating-src.tar.gz if you have a Windows utility that will open it. There I see a total of 66,365 files requiring 1.6GB (uncompressed). There is apparently not a separate AOO341 branch or tag. But if the .tar.gz doesn't work for you, it appears that there is work going on at http://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34 as an alternative, depending what you are interested in. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Friday, June 29, 2012 12:32 To: ooo-dev@incubator.apache.org Subject: RE: SVN mistake, Sorry @Risto, I confirm your observation about the aoo-3.4.1 src.zip. I downloaded a00-3.4.1-incubating-src.zip and there is something peculiar. WinZip reports only 948 files for a total of 5,483kB. But the zip is 357MB. I did a WinZip test and received a warning about the central directory not having an end-of-directory signature. Also, in the test output I see many pointless entries for directories, most of which have no files. I am assuming that the .zip is defective in some way. I think it's Winzip that cannot handle the archive. I just tried using 7-Zip - test action - and that shows no errors. the zip file is created by the internal zip task of ant. I don't know if there is a problem with Winzip. I raised a bug about this: https://issues.apache.org/ooo/show_bug.cgi?id=120132 Juergen Folders: 6941 Files: 66365 It may be that using a different method of generating the zip file would allow Winzip to open the archive successfully. I am now downloading the tar.gz to see if that is any better. (WinZip will open these) - Dennis -Original Message- From: Risto Jääskeläinen [mailto:rjaas...@saunalahti.fi] Sent: Friday, June 29, 2012 11:38 To: AOOkehitys Subject: SVN mistake, Sorry [ ... ] I started first downloading file aoo-3.4.1-incubating-src.zip from page: https://cwiki.apache.org/OOOUSERS/development-snapshot-builds.html but this zip-file seems to consist mostly empty directories, so ... Sorry Risto
Re: SVN mistake, Sorry
On 29 June 2012 20:54, Dennis E. Hamilton dennis.hamil...@acm.org wrote: @Risto, I recommend using a00-3.4.1-incubating-src.tar.gz if you have a Windows utility that will open it. There I see a total of 66,365 files requiring 1.6GB (uncompressed). There is apparently not a separate AOO341 branch or tag. But if the .tar.gz doesn't work for you, it appears that there is work going on at http://svn.apache.org/repos/asf/incubator/ooo/branches/AOO34 as an alternative, depending what you are interested in. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Friday, June 29, 2012 12:32 To: ooo-dev@incubator.apache.org Subject: RE: SVN mistake, Sorry @Risto, I confirm your observation about the aoo-3.4.1 src.zip. I downloaded a00-3.4.1-incubating-src.zip and there is something peculiar. WinZip reports only 948 files for a total of 5,483kB. But the zip is 357MB. I did a WinZip test and received a warning about the central directory not having an end-of-directory signature. Also, in the test output I see many pointless entries for directories, most of which have no files. I am assuming that the .zip is defective in some way. I think it's Winzip that cannot handle the archive. I just tried using 7-Zip - test action - and that shows no errors. Folders: 6941 Files: 66365 It may be that using a different method of generating the zip file would allow Winzip to open the archive successfully. I am now downloading the tar.gz to see if that is any better. (WinZip will open these) - Dennis -Original Message- From: Risto Jääskeläinen [mailto:rjaas...@saunalahti.fi] Sent: Friday, June 29, 2012 11:38 To: AOOkehitys Subject: SVN mistake, Sorry [ ... ] I started first downloading file aoo-3.4.1-incubating-src.zip from page: https://cwiki.apache.org/OOOUSERS/development-snapshot-builds.html but this zip-file seems to consist mostly empty directories, so ... Sorry Risto
Re: [CODE]: update code signing for Windows
On 22 June 2012 12:03, Jürgen Schmidt jogischm...@googlemail.com wrote: Hi, I analyzed and played with code signing on Windows using a self signed test certificate. Thanks to Andre and his Perl skills I was able to fix a strange build problem with a too long command line triggered from a makefile to perl. Anyway this is solved now. I have now signed a full install set and would like to ask if somebody is interested to test it and give me feedback. You can find a signed download file under http://people.apache.org/~jsc/signing_test/Apache_OpenOffice_incubating_3.4.0_Win_x86_install_en-US.exe NOICE: this is a build based on AOO34 branch without the updated version numbers. It's no dev build, please be careful if you test it. Just a suggestion: since you are testing the signing process here, the actual content is irrelevant. So you could make a much smaller file that just installs a text file (or something like that). I have to check the whole process and probably have to improve some things to make it final. The last important step is triggered manual by now. I use a Personal Information Exchange file (*.pfx) of my self signed certificate with a passcode that is specified during the build process. This seems to be a good approach to handle a certificate in this scenario and during our build process. I will keep you informed... Juergen
Re: Commit message summaries
On 21 June 2012 19:10, Rob Weir robw...@apache.org wrote: On Thu, Jun 21, 2012 at 8:10 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/21/12 11:47 AM, Herbert Duerr wrote: On 21.06.2012 10:17, Jürgen Schmidt wrote: We have already introduced the Patch by, Review By .. fields for adding further information. How about logs like issuenumber:issue subject line I agree that the issue subject line is better than nothing, but I prefer that the subject line is about why the change was made. See e.g. the six different changes for issue 118923. Why would anyone want the same change header for each commit when you can have a description instead that matches the change much better? good point and I agree. That means we use something like ### issuenumber + 1_line_summary/description longer description_on_demand patch_by_on_demand ... ### where issuenumber is - either the plain number + : - or #number# - or #inumber# I can live with all but we should agree on one notation. My preference is the first and then the second. I don't think we need the lower case 'i' anymore. Older commit messages can be interpreted by knowing the older conventions and today we have only one bugtracker. It may also be possible to change a commit message using svn propedit. Does anyone know if this is enabled for committer access? AFAIK, if the login can commit, it can also change the log message; there's no separate karma needed. See: http://subversion.apache.org/faq.html#change-log-msg This could also be useful for older commits that used a different format for patch by: acknowledgements. -Rob Issues from other bugtracker systems should be ideally duplicated in our system. The other systems can be public or private bug tracking systems and issue numbers of the latter ones don't help anybody. I would like to hear other opinions of people who actually work with our code. Juergen I'm also against using a bare issue number, because having a number that can be reliably parsed by eventual tools (e.g. a tool that updates bugzilla with the revision number, a tool that links the revision commit to the corresponding bug URL, etc.) is no extra effort whereas it opens a whole world of opportunities. I prefer that computers do such work that can be automated because they are rather good at that. fix:short description/summary I like the commit conventions used in the linux kernel. Browse some commit links of the kernel shortlog at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog to see some examples. A common notation used by all would be of course helpful +1 Herbert
Re: [Proposal] Guidelines for list conduct policy
On 18 June 2012 13:30, RGB ES rgb.m...@gmail.com wrote: 2012/6/18 Rob Weir robw...@apache.org: 1. What Happens in Vegas, Stays in Vegas: Anything you read in the private list is by default a private PPMC affair and not to be spoken of, or copied to other people who are not in the PPMC. If you think about it, most topic threads probably should be in the public lists, except choosing committers and PPMC members, and a very few others. In fact, all email lists or email conversations have this aspect of privacy. Even if there are 23000 subscribers on the list, it is assumed that privacy will be maintained and a list member's name and location will not be published in a newspaper or some other public venue where personal privacy is not expected. I like it. You write well, with style. But I do wonder if What happens in Vegas... is well understood outside of the USA? Of course, everyone should watch The Hangover ;-) The phrase is clear from context... but not by itself. At least not for me. I think the phrase may give the wrong impression. I assumed it was akin to don't broadcast what happens on a stag night but having done an internet search I see it's perhaps not quite the same. Nevertheless, I suggest a change to something less culturally biased and with less likelihood of misinterpretation.
Re: Final look at art work ( Re: First Year Anniversary - party CD)
On 13 June 2012 01:33, drew d...@baseanswers.com wrote: On Wed, 2012-06-13 at 00:28 +0100, sebb wrote: On 12 June 2012 22:34, drew d...@baseanswers.com wrote: On Wed, 2012-06-06 at 18:48 -0400, drew wrote: I would like to propose that we treat the 13th of the month as our 1st Anniversary and would like to do the following for the occasion: snip I would like to release two CD iso images, Windows and Mac on the 13th of this month. Howdy, Alright - well, cutting it right down to the end on time here. I just want to be sure, as I'm not sure this is right branding wise - if you anyone sees a problem with this let me know, I don't mind re-working things. I also won't be offended if anyone says hold up.. Here is the final cut on five items: A disk label: http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Envelope/Sleeve cover: http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png Cut/Fold Envelope: http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png CD/DVD tall case cover: http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png A4 poster: http://lo-portal.us/aoo/temp/freeyourself.png I have a few hours ahead of me before I button this iso image up, if you see some glaring problem I missed do please yell. The only possible problem I see is the text MS Windows XP, Vista, Win 7 (c) 2012 Microsoft Corporation Should MS be spelt in full? Microsoft and Windows are both registered trademarks. Just space requirements.. All the software packages I have seen which target Windows either omit Microsoft or spell it out in full. AFAIK MS is not an official abbreviation for Microsoft; they may not be too happy. Also, when I first saw this, I briefly thought that the (c) statement applied to the content. In fact I'm not sure what the (c) does apply to. I suspect it should be removed. Hi Sebb, It should be a registered trademark glyph, there was a mistake earlier today and you may just need do a cache refresh. I can see the (R) now, however it is not appropriately used. AFAIK, the terms that are registered are Microsoft Windows Vista So the block should be: Microsoft (R) Windows (R) XP, Vista (R), Win 7 (or is it called Windows 7?) It might be OK to omit the (R) after Vista. The following line is misleading and should be removed: (R) 2012 Microsoft Corporation Have a look at some other recent products that are designed for/support Windows and see what they do. It would be helpful to make clear that MS Windows is the host OS, and is not actually supplied. e.g. Version for: or Designed for: or Supports: Microsoft (r) Windows (r) XP, Vista, Win 7 (or is it called Windows 7?) hmm - I suppose, though Alexandro is saying 'too much'... tis the normal way of things in other words ;) so... I'll see about trying to do both things at the same time - if I can tonight, add more white space and one that, actually it will be better for both. @Sebb - also if you don't mind me asking directly for you thought on something. Rob correctly pointed out that this is really a re-mix of official material, but not official itself - well, honestly looking at what I've produced, not sure that is easily discerned. Does use of the brand like this, without any notice on any of those pieces of who I am, who the actual publisher of the iso image is in other words, cause any concerns in your mind? That is a separate issue, which should be addressed to the ASF Branding / Trademarks team. Thanks much, //drew snip
Re: Final look at art work ( Re: First Year Anniversary - party CD)
On 13 June 2012 11:26, drew d...@baseanswers.com wrote: On Wed, 2012-06-13 at 11:11 +0100, sebb wrote: On 13 June 2012 01:33, drew d...@baseanswers.com wrote: On Wed, 2012-06-13 at 00:28 +0100, sebb wrote: On 12 June 2012 22:34, drew d...@baseanswers.com wrote: On Wed, 2012-06-06 at 18:48 -0400, drew wrote: I would like to propose that we treat the 13th of the month as our 1st Anniversary and would like to do the following for the occasion: snip I would like to release two CD iso images, Windows and Mac on the 13th of this month. Howdy, Alright - well, cutting it right down to the end on time here. I just want to be sure, as I'm not sure this is right branding wise - if you anyone sees a problem with this let me know, I don't mind re-working things. I also won't be offended if anyone says hold up.. Here is the final cut on five items: A disk label: http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Envelope/Sleeve cover: http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png Cut/Fold Envelope: http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png CD/DVD tall case cover: http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png A4 poster: http://lo-portal.us/aoo/temp/freeyourself.png I have a few hours ahead of me before I button this iso image up, if you see some glaring problem I missed do please yell. The only possible problem I see is the text MS Windows XP, Vista, Win 7 (c) 2012 Microsoft Corporation Should MS be spelt in full? Microsoft and Windows are both registered trademarks. Just space requirements.. All the software packages I have seen which target Windows either omit Microsoft or spell it out in full. AFAIK MS is not an official abbreviation for Microsoft; they may not be too happy. Also, when I first saw this, I briefly thought that the (c) statement applied to the content. In fact I'm not sure what the (c) does apply to. I suspect it should be removed. Hi Sebb, It should be a registered trademark glyph, there was a mistake earlier today and you may just need do a cache refresh. I can see the (R) now, however it is not appropriately used. AFAIK, the terms that are registered are Microsoft Windows Vista So the block should be: Microsoft (R) Windows (R) XP, Vista (R), Win 7 (or is it called Windows 7?) It might be OK to omit the (R) after Vista. The following line is misleading and should be removed: (R) 2012 Microsoft Corporation Have a look at some other recent products that are designed for/support Windows and see what they do. Actually I had seen it used on a package, though not with the abbreviation and it doesn't make it right per se, anyway..I suppose So - acted on Alexandro's comments and yours, and as usual, listening does end up with a better result...updated the file here http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png The CD still contains the line (R) 2012 Microsoft Corporation That does not make sense. (R) should only be used after a registered trademark The block should be Media for: Microsoft (R) Windows (R) XP, Vista, Windows 7 (note that MS does not call it Win 7) //drew
Re: Final look at art work ( Re: First Year Anniversary - party CD)
On 13 June 2012 18:51, Nancy K nancythirt...@yahoo.com wrote: Sorry for not posting the link - here it is https://cwiki.apache.org/confluence/download/attachments/27834929/freeyourself_PosterB.jpg The page footer is truncated on the RHS after Found - should be Foundation. Nancy Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Nancy K nancythirt...@yahoo.com To: ooo-dev@incubator.apache.org ooo-dev@incubator.apache.org; Nancy K nancythirt...@yahoo.com Cc: d...@baseanswers.com d...@baseanswers.com Sent: Wednesday, June 13, 2012 10:50 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) Hi Drew and all, Here is a quick jpg look at the poster Drew designed using a dark drop shadow instead of the white shadow on the features. I also placed the features in line with the lower text. I think I like Drew's large heading font better than the Bitstream Vera Sans that I used throughout. Nancy Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Nancy K nancythirt...@yahoo.com To: ooo-dev@incubator.apache.org ooo-dev@incubator.apache.org Sent: Wednesday, June 13, 2012 8:12 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) Drew, Can you align the word Media over a notch so it lines up with the words below? I think you will have a stronger look - as it will create that imaginary left line. This looks great - you have an eye for professional high quality! Nancy PS I was going to tackle the poster, but it is the last minute - I liked everything in your poster but did agree that the white shadow on the word processor, spreadsheet, vector drawing, etc. was hard to read. Have you tried it with a grey or black drop shadow instead of white? I think it would stand out clearer. What font style are you using? Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: drew d...@baseanswers.com To: ooo-dev@incubator.apache.org Sent: Wednesday, June 13, 2012 3:26 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) On Wed, 2012-06-13 at 11:11 +0100, sebb wrote: On 13 June 2012 01:33, drew d...@baseanswers.com wrote: On Wed, 2012-06-13 at 00:28 +0100, sebb wrote: On 12 June 2012 22:34, drew d...@baseanswers.com wrote: On Wed, 2012-06-06 at 18:48 -0400, drew wrote: I would like to propose that we treat the 13th of the month as our 1st Anniversary and would like to do the following for the occasion: snip I would like to release two CD iso images, Windows and Mac on the 13th of this month. Howdy, Alright - well, cutting it right down to the end on time here. I just want to be sure, as I'm not sure this is right branding wise - if you anyone sees a problem with this let me know, I don't mind re-working things. I also won't be offended if anyone says hold up.. Here is the final cut on five items: A disk label: http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Envelope/Sleeve cover: http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png Cut/Fold Envelope: http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png CD/DVD tall case cover: http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png A4 poster: http://lo-portal.us/aoo/temp/freeyourself.png I have a few hours ahead of me before I button this iso image up, if you see some glaring problem I missed do please yell. The only possible problem I see is the text MS Windows XP, Vista, Win 7 (c) 2012 Microsoft Corporation Should MS be spelt in full? Microsoft and Windows are both registered trademarks. Just space requirements.. All the software packages I have seen which target Windows either omit Microsoft or spell it out in full. AFAIK MS is not an official abbreviation for Microsoft; they may not be too happy. Also, when I first saw this, I briefly thought that the (c) statement applied to the content. In fact I'm not sure what the (c) does apply to. I suspect it should be removed. Hi Sebb, It should be a registered trademark glyph, there was a mistake earlier today and you may just need do a cache refresh. I can see the (R) now, however it is not appropriately used. AFAIK, the terms that are registered are Microsoft Windows Vista So the block should be: Microsoft (R) Windows (R) XP, Vista (R), Win 7 (or is it called Windows 7?) It might be OK to omit the (R) after Vista. The following line is misleading and should be removed: (R) 2012 Microsoft Corporation Have a look at some other recent products that are designed for/support Windows
Re: Final look at art work ( Re: First Year Anniversary - party CD)
On 13 June 2012 23:33, sebb seb...@gmail.com wrote: On 13 June 2012 18:51, Nancy K nancythirt...@yahoo.com wrote: Sorry for not posting the link - here it is https://cwiki.apache.org/confluence/download/attachments/27834929/freeyourself_PosterB.jpg The page footer is truncated on the RHS after Found - should be Foundation. Also the sentence an open office suite with freedom built inside ends much too close to the edge. Perhaps it should be centred? Further, built inside reads oddly to me, but maybe that is an Americanism. Nancy Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Nancy K nancythirt...@yahoo.com To: ooo-dev@incubator.apache.org ooo-dev@incubator.apache.org; Nancy K nancythirt...@yahoo.com Cc: d...@baseanswers.com d...@baseanswers.com Sent: Wednesday, June 13, 2012 10:50 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) Hi Drew and all, Here is a quick jpg look at the poster Drew designed using a dark drop shadow instead of the white shadow on the features. I also placed the features in line with the lower text. I think I like Drew's large heading font better than the Bitstream Vera Sans that I used throughout. Nancy Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Nancy K nancythirt...@yahoo.com To: ooo-dev@incubator.apache.org ooo-dev@incubator.apache.org Sent: Wednesday, June 13, 2012 8:12 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) Drew, Can you align the word Media over a notch so it lines up with the words below? I think you will have a stronger look - as it will create that imaginary left line. This looks great - you have an eye for professional high quality! Nancy PS I was going to tackle the poster, but it is the last minute - I liked everything in your poster but did agree that the white shadow on the word processor, spreadsheet, vector drawing, etc. was hard to read. Have you tried it with a grey or black drop shadow instead of white? I think it would stand out clearer. What font style are you using? Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: drew d...@baseanswers.com To: ooo-dev@incubator.apache.org Sent: Wednesday, June 13, 2012 3:26 AM Subject: Re: Final look at art work ( Re: First Year Anniversary - party CD) On Wed, 2012-06-13 at 11:11 +0100, sebb wrote: On 13 June 2012 01:33, drew d...@baseanswers.com wrote: On Wed, 2012-06-13 at 00:28 +0100, sebb wrote: On 12 June 2012 22:34, drew d...@baseanswers.com wrote: On Wed, 2012-06-06 at 18:48 -0400, drew wrote: I would like to propose that we treat the 13th of the month as our 1st Anniversary and would like to do the following for the occasion: snip I would like to release two CD iso images, Windows and Mac on the 13th of this month. Howdy, Alright - well, cutting it right down to the end on time here. I just want to be sure, as I'm not sure this is right branding wise - if you anyone sees a problem with this let me know, I don't mind re-working things. I also won't be offended if anyone says hold up.. Here is the final cut on five items: A disk label: http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Envelope/Sleeve cover: http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png Cut/Fold Envelope: http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png CD/DVD tall case cover: http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png A4 poster: http://lo-portal.us/aoo/temp/freeyourself.png I have a few hours ahead of me before I button this iso image up, if you see some glaring problem I missed do please yell. The only possible problem I see is the text MS Windows XP, Vista, Win 7 (c) 2012 Microsoft Corporation Should MS be spelt in full? Microsoft and Windows are both registered trademarks. Just space requirements.. All the software packages I have seen which target Windows either omit Microsoft or spell it out in full. AFAIK MS is not an official abbreviation for Microsoft; they may not be too happy. Also, when I first saw this, I briefly thought that the (c) statement applied to the content. In fact I'm not sure what the (c) does apply to. I suspect it should be removed. Hi Sebb, It should be a registered trademark glyph, there was a mistake earlier today and you may just need do a cache refresh. I can see the (R) now, however it is not appropriately used. AFAIK, the terms that are registered are Microsoft Windows Vista So the block should be: Microsoft (R) Windows (R
Re: Final look at art work ( Re: First Year Anniversary - party CD)
On 12 June 2012 22:34, drew d...@baseanswers.com wrote: On Wed, 2012-06-06 at 18:48 -0400, drew wrote: I would like to propose that we treat the 13th of the month as our 1st Anniversary and would like to do the following for the occasion: snip I would like to release two CD iso images, Windows and Mac on the 13th of this month. Howdy, Alright - well, cutting it right down to the end on time here. I just want to be sure, as I'm not sure this is right branding wise - if you anyone sees a problem with this let me know, I don't mind re-working things. I also won't be offended if anyone says hold up.. Here is the final cut on five items: A disk label: http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Envelope/Sleeve cover: http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png Cut/Fold Envelope: http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png CD/DVD tall case cover: http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png A4 poster: http://lo-portal.us/aoo/temp/freeyourself.png I have a few hours ahead of me before I button this iso image up, if you see some glaring problem I missed do please yell. The only possible problem I see is the text MS Windows XP, Vista, Win 7 (c) 2012 Microsoft Corporation Should MS be spelt in full? Microsoft and Windows are both registered trademarks. Also, when I first saw this, I briefly thought that the (c) statement applied to the content. In fact I'm not sure what the (c) does apply to. I suspect it should be removed. It would be helpful to make clear that MS Windows is the host OS, and is not actually supplied. e.g. Version for: or Designed for: or Supports: Microsoft (r) Windows (r) XP, Vista, Win 7 (or is it called Windows 7?) Otherwise - if you also think these would be a good resource for general reference (png and svg) will put them to the wiki or where ever folks think best Thanks, //drew
Re: User demographics
On 11 June 2012 03:27, Rob Weir robw...@apache.org wrote: On one of the UX threads there is ongoing discussion about a possible user survey. I mentioned that we have some info from users, from information collected by Google Analytics. There was some interest in this data, so I offered to put together a little report. Here it is. This is data collected from those who downloaded OpenOffice in the last month. This includes those who downloaded AOO 3.4, but also those who downloaded OOo 3.3 through the website as well. That's very interesting, and could be useful to other ASF projects as well. In particular the percentage using XP is still very substantial. [If you want to drop support for a Windows version, drop Vista rather than XP (joke)] Perhaps make it available as a web-page? BTW, does the data include information on Java versions? Regards, -Rob Locale (This is the locale as set in the browser used to download OpenOffice) 1. en-us 34.18% 2. ja 6.53% 3. fr 6.15% 4. de-de 5.42% 5. it 5.28% 6. es 4.87% 7. de 4.57% 8. pl 4.31% 9. ru 3.16% 10. en-gb 2.69% 11. it-it 2.60% 12. es-es 2.35% 13. nl 1.60% 14. zh-tw 1.42% 15. en 1.26% 16. ru-ru 1.12% 17. pt-br 1.04% 18. da 0.86% 19. sv 0.78% 20. ja-jp 0.77% 21. zh-cn 0.61% 22. tr 0.55% 23. fr-fr 0.48% 24. es-419 0.40% 25. sv-se 0.40% Browser used: 1. Firefox 30.33% 2. Internet Explorer 30.06% 3. Chrome 27.30% 4. Safari 8.41% 5. Opera 2.67% Most common browser versions: 1. Firefox 12.0 21.36% 2. Internet Explorer 9.0 14.41% 3. Chrome 19.0.1084.52 12.46% 4. Internet Explorer 8.0 12.10% 5. Chrome 18.0.1025.168 6.37% 6. Chrome 19.0.1084.46 5.41% 7. Safari 534.57.2 2.21% 8. Internet Explorer 7.0 2.20% 9. Opera 11.64 1.80% 10. Firefox 11.0 1.74% Most common operating systems: 1. Windows 83.74% 2. Macintosh 10.79% 3. Linux 3.41% Detail for Windows users (so all Windows users together == 100%) 1. 7 56.56% 2. XP 32.43% 3. Vista 9.85% 4. NT 0.58% 5. Server 2003 0.39% 6. 2000 0.16% 7. 98 0.02% 8. ME 0.00% Detail for Mac users (so all Mac users together == 100%) 1. Intel 10.7 55.46% 2. Intel 10.6 31.92% 3. Intel 10.5 7.70% 4. PPC 10.5 1.63% 5. PPC 10.4 1.57% 6. Intel 10.4 1.01% 7. PPC 0.38% 8. Intel 0.17% 9. Intel 10.8 0.16% 10. (not set) 0.00% Detail for Linux users (so all Linux users together == 100%) 1. i686 61.31% 2. x86_64 37.82% 3. (not set) 0.48% 4. zbov 0.15% 5. armv7l 0.13% 6. ppc 0.03% 7. x86 0.02% 8. i586 0.02% 9. zvav 0.01% 10. armv6l 0.01% Screen resolutions: 1. 1366x768 18.59% 2. 1280x800 12.90% 3. 1024x768 12.20% 4. 1280x1024 10.15% 5. 1920x1080 8.94% 6. 1440x900 7.20% 7. 1680x1050 5.32% 8. 1600x900 4.46% 9. 1024x600 3.04% 10. 1920x1200 2.04% Color Depth: 1. 24-bit 54.31% 2. 32-bit 43.73% 3. 16-bit 1.81% 4. 4-bit 0.11% 5. 8-bit 0.01% 6. 32-bit 0.01% Java support (in browser) 1. Yes 78.21% 2. No 21.78%
Re: Installation Experience and Feedback
On 11 June 2012 16:17, Andre Fischer a...@a-w-f.de wrote: On 11.06.2012 16:51, O.Felka wrote: Am 11.06.2012 16:37, schrieb Andre Fischer: On 11.06.2012 15:53, O.Felka wrote: AFAICT, the unpacked files are only needed for installation, and one still has the initial download, so why clutter up the disk? this is not true. The unpacked files are needed for the so called 'maintenance mode': Starting the setup from the control panel offers you a repair and a modify mode. That's what the unpacked files are needed for. What we might delete is the packed file. But do we really need the maintenance mode? There are not that many applications on my system that offer one. We are talking about 130 MB of additional disk space. As long as we don't install the complete office we need the maintenance mode. Applications that don't offer several modules as AOO does don't need a 'Modify' mode. If we want to offer to install e.g. only the Calc application we need the maintenance mode for these users that wants to use the Writer to a later time also. The 'Repair' option is also a part of the maintenance mode. The question is whether there are more people annoyed by a folder on their desktop that contains files that hardly ever used or users that install only a part of the application then change their mind later. As we don't have any information it would end up in wild guessing. comparing these two user groups is meaningless at this point. No not meaningless, just not easily possible. As we started with the self extracting installer we've had to decide where to place the unpacked files. The desktop is the place where you can't oversee them. That is one thing I still don't understand. Why is it important that the user has to find these files. The installation starts automatically after the downloaded archive has been extracted. A repair or change is triggered via a system dialog. What is the use case in which the user has to click on any of the downloaded files directly? Agreed. Every user has option to unpack these file at a different location. We still need a better default. Indeed. If the unpacked files do not need to be kept after installation (e.g. for full installation) then they should be created under TEMP and deleted after installation completes. If the unpacked files should be kept after installation (e.g. for maintenance) then they should be stored somewhere where the user is NOT likely be annoyed by them, and is less likely to delete (or move) them. Until I read this thread, I had assumed that the installation process was broken because it did not tidy up after itself, so I just deleted the directory containing the unpacked files. As I wrote earlier, there must be a standard location (or choice of location) where such maintenance files are supposed to be kept. Desktop is a bad choice in both cases. As have written before, it's an option to delete the unpacked file to save disk space. The unpacked files can be used easier to distribute the AOO without downloading. In times of hard disks with TB size saving 130 MB is not so important for me. Maybe not for you. As I have written. In another issue regarding extensions installed in the user directory you where not so forgiving about disk space. -Andre
Re: Installation Experience and Feedback
On 11 June 2012 16:33, Peter Brawley peter.braw...@earthlink.net wrote: On 2012-06-10 7:18 PM, sebb wrote: On 9 June 2012 14:57, O.Felkaolaf-openoff...@gmx.de wrote: Am 09.06.2012 14:22, schrieb sebb: AFAICT, the unpacked files are only needed for installation, and one still has the initial download, so why clutter up the disk? this is not true. The unpacked files are needed for the so called 'maintenance mode': Starting the setup from the control panel offers you a repair and a modify mode. That's what the unpacked files are needed for. In that case, they really should *not* be placed on the desktop. Nor under TEMP of course. I don't know what the Windows standard location for such things is, but it's certainly not the desktop. On Vista and 7 it could be c:\Users\user name\Downloads\. I don't think downloads is suitable either. It's not actually a download once it has been unpacked and installed - it's effectively part of the installation, and so should be somewhere where it is unlikely to be deleted. It should be probably somewhere like Documents and Settings, in a hidden directory such as Application Data or Local Settings\Application Data. It should be in the folder named by the TEMP environment variable. TEMP is for temporary files. That is OK for unpacking the download if the unpacked files are to be deleted later. It is not OK if the unpacked files are to be kept for maintenance. PB - Microsoft must have a convention for where such installation support files should go. Who remembers Win XP? I still use it. AIUI, many businesses still use it, partly because Vista was not very popular. And of course, if the user decides to remove the application, it should remove the unpacked files as well. I don't know any software behaving like that so I don't think that we need that. If the user is deinstalling for a new install he needs these files. And in case someone has installed from a CD it doesn't make sense. What we might delete is the packed file. Only if this is agreed by the user. As always when deleting useful files.
Re: Installation Experience and Feedback
On 9 June 2012 14:57, O.Felka olaf-openoff...@gmx.de wrote: Am 09.06.2012 14:22, schrieb sebb: AFAICT, the unpacked files are only needed for installation, and one still has the initial download, so why clutter up the disk? this is not true. The unpacked files are needed for the so called 'maintenance mode': Starting the setup from the control panel offers you a repair and a modify mode. That's what the unpacked files are needed for. In that case, they really should *not* be placed on the desktop. Nor under TEMP of course. I don't know what the Windows standard location for such things is, but it's certainly not the desktop. On Vista and 7 it could be c:\Users\user name\Downloads\. I don't think downloads is suitable either. It's not actually a download once it has been unpacked and installed - it's effectively part of the installation, and so should be somewhere where it is unlikely to be deleted. It should be probably somewhere like Documents and Settings, in a hidden directory such as Application Data or Local Settings\Application Data. Microsoft must have a convention for where such installation support files should go. Who remembers Win XP? I still use it. AIUI, many businesses still use it, partly because Vista was not very popular. And of course, if the user decides to remove the application, it should remove the unpacked files as well. I don't know any software behaving like that so I don't think that we need that. If the user is deinstalling for a new install he needs these files. And in case someone has installed from a CD it doesn't make sense. What we might delete is the packed file. Only if this is agreed by the user. As always when deleting useful files.
Re: First Year Anniversary - party CD
On 9 June 2012 08:24, drew d...@baseanswers.com wrote: On Fri, 2012-06-08 at 19:27 +0100, sebb wrote: On 8 June 2012 19:05, drew d...@baseanswers.com wrote: On Thu, 2012-06-07 at 21:13 -0400, Rob Weir wrote: On Thu, Jun 7, 2012 at 6:43 PM, drew d...@baseanswers.com wrote: On Thu, 2012-06-07 at 14:35 -0700, Nancy K wrote: I do like all of these, but have to show you folks what my friend Reya Mellicker is offering - and she is willing to let Apache Open Office use it as you see fit. If you need an email consent or something, I can get that as well from her. What do you think? https://cwiki.apache.org/confluence/download/attachments/27834929/CloudsReyaMellicker.jpg Hi Nancy Thanks - I'll see if there is something I can do with that. OK - I've updated all three pieces http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png will leave these as is for now - any ideas on better content, etc. appreciated. Missing 't' in Productivity in http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Also it looks like you have (C) for the MS Office, etc. I assume you want to acknowledge their trademark, not copyright. Alright, Productivity now has a 't' where it should be, on all three pieces. The (c) is now a (r) for the MS trademarks. Made the copy changes, per Nancy's recommendations - reads better now, thank you Nancy. It's not 100% clear to me if the CD contains just the Software Development Kit for the suite, or if it contains the SDK in addition to the suite. I suspect the latter, but perhaps consider adding includes before the SDK text. Howdy Sebb, Ok, well I tried to be more explicit when putting the first cut of the hard case cover together http://lo-portal.us/aoo/temp/AOO34-dvd-case-win.png That looks good. Alternatively, if the two lines are made to look like a list, then they are less likely to be confused with a longer line that has been wrapped. For example: * English Installer for full application suite * Software Development Kit or - English Installer for full application suite - Software Development Kit (or any other suitable list marker, such as +) That might work better on the CD which has less room for the extra line containing will go back and update the others to match, if that looks with everyone. //drew Pushed png with those changes to the URLs listed above. The clock/calendar tells me I need to call these done - unless someone sees a real issue with anything there. So - question - is this the point where I need to send an email to the ASF trademark mail list? //drew
Re: Installation Experience and Feedback
On 9 June 2012 08:57, O.Felka olaf-openoff...@gmx.de wrote: Am 08.06.2012 19:00, schrieb sebb: On 7 June 2012 03:57, Gavin McDonald ga...@16degrees.com.au wrote: Hi, b. The program 'Unpacks' to a folder on the 'Desktop' - Why? Really we should be choosing the 'Downloads' folder. We've decided to place them on the desktop so that every user can find them easily. Every user has the choice to unpack them into a different folder. Better yet, use a folder under %TEMP% and delete it after use. No! AFAICT, the unpacked files are only needed for installation, and one still has the initial download, so why clutter up the disk? this is not true. The unpacked files are needed for the so called 'maintenance mode': Starting the setup from the control panel offers you a repair and a modify mode. That's what the unpacked files are needed for. In that case, they really should *not* be placed on the desktop. Nor under TEMP of course. I don't know what the Windows standard location for such things is, but it's certainly not the desktop. And of course, if the user decides to remove the application, it should remove the unpacked files as well. What we might delete is the packed file. Only if this is agreed by the user. Groetjes, Olaf
Re: Installation Experience and Feedback
On 7 June 2012 03:57, Gavin McDonald ga...@16degrees.com.au wrote: Hi All, snip/ 1. Download OpenOffice 3.4 from openoffice.org mirror. -- Time: 2 minutes. 2. Unpack . -- Time: 1 minute. 3. Install. -- Time: 2 minutes. 4. Erm, nothing e4lse, we are done! It really was as painless and quick as that. Well Done Guys n Gals! I do have a few observations that someone might think Bugzilla worthy (all minor): snip/ b. The program 'Unpacks' to a folder on the 'Desktop' - Why? Really we should be choosing the 'Downloads' folder. Better yet, use a folder under %TEMP% and delete it after use. AFAICT, the unpacked files are only needed for installation, and one still has the initial download, so why clutter up the disk?
Re: First Year Anniversary - party CD
On 8 June 2012 19:05, drew d...@baseanswers.com wrote: On Thu, 2012-06-07 at 21:13 -0400, Rob Weir wrote: On Thu, Jun 7, 2012 at 6:43 PM, drew d...@baseanswers.com wrote: On Thu, 2012-06-07 at 14:35 -0700, Nancy K wrote: I do like all of these, but have to show you folks what my friend Reya Mellicker is offering - and she is willing to let Apache Open Office use it as you see fit. If you need an email consent or something, I can get that as well from her. What do you think? https://cwiki.apache.org/confluence/download/attachments/27834929/CloudsReyaMellicker.jpg Hi Nancy Thanks - I'll see if there is something I can do with that. OK - I've updated all three pieces http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png http://lo-portal.us/aoo/temp/AOO34-cd-sleeve-win.png http://lo-portal.us/aoo/temp/AOO34-cd-folded-win.png will leave these as is for now - any ideas on better content, etc. appreciated. Missing 't' in Productivity in http://lo-portal.us/aoo/temp/AOO34-cd-label-win.png Also it looks like you have (C) for the MS Office, etc. I assume you want to acknowledge their trademark, not copyright. Alright, Productivity now has a 't' where it should be, on all three pieces. The (c) is now a (r) for the MS trademarks. Made the copy changes, per Nancy's recommendations - reads better now, thank you Nancy. It's not 100% clear to me if the CD contains just the Software Development Kit for the suite, or if it contains the SDK in addition to the suite. I suspect the latter, but perhaps consider adding includes before the SDK text. Pushed png with those changes to the URLs listed above. The clock/calendar tells me I need to call these done - unless someone sees a real issue with anything there. So - question - is this the point where I need to send an email to the ASF trademark mail list? //drew
Re: [PROPOSAL] Starting the graduation process
On 30 May 2012 00:03, Pedro Giffuni p...@apache.org wrote: --- Mar 29/5/12, Rob Weir robw...@apache.org ha scritto: ... The idea that we have remaining issues with Category-B tarballs in the tree has been around since before the release, and one of our mentors (Ross I recall) did acknowledge my point of view. Again, I don't see an issue here. But if you feel strongly about this you are welcome to copy the ext_sources over to Apache Extras and do a trivial update of the build script. Whatever makes you happy. I am busy at the moment, plus doing this will mean I have to suspend the updates I was working on. I think I will start next week. I will only move Category-B code and I will disable it from the buildbots too: it's rather inconvenient to have the buildbot depend on downloading extra tarballs. This is admittedly a stop gap solution to comply better with the Apache policies, the real fix would be to work collectively on replacing the code that can be replaced: Alternatively, it is possible to include cat B [1] dependencies in binary form. Is there any need to include the source? [1] http://www.apache.org/legal/resolved.html#category-b rhino -- Google V8 nss -- openssl Seamonkey -- Mulberry library but that doesn't seem to be a priority for 4.0 :( . Pedro.
Re: [PROPOSAL] Starting the graduation process
On 30 May 2012 00:50, Rob Weir robw...@apache.org wrote: On Tue, May 29, 2012 at 7:34 PM, sebb seb...@gmail.com wrote: On 30 May 2012 00:03, Pedro Giffuni p...@apache.org wrote: --- Mar 29/5/12, Rob Weir robw...@apache.org ha scritto: ... The idea that we have remaining issues with Category-B tarballs in the tree has been around since before the release, and one of our mentors (Ross I recall) did acknowledge my point of view. Again, I don't see an issue here. But if you feel strongly about this you are welcome to copy the ext_sources over to Apache Extras and do a trivial update of the build script. Whatever makes you happy. I am busy at the moment, plus doing this will mean I have to suspend the updates I was working on. I think I will start next week. I will only move Category-B code and I will disable it from the buildbots too: it's rather inconvenient to have the buildbot depend on downloading extra tarballs. This is admittedly a stop gap solution to comply better with the Apache policies, the real fix would be to work collectively on replacing the code that can be replaced: Alternatively, it is possible to include cat B [1] dependencies in binary form. Is there any need to include the source? If the build did not consumer source then we would need to store, in SVN, category-b binaries files for each component, in each platform/architecture. That would be 4 platforms now, but I'd expect that go up to 7 in the near future. Surely at least Mozilla Rhino is written in Java, and tar balls are published in various locations (e.g. Maven Central) suitable for use as part of a build. If there are other non-Java dependencies that are not available for all platforms as binaries, then of course the source needs to be built. I don't think that solves any real problem. We'd still need access to the source to provide urgent security patches, etc. So we're then back to the same question: where to store the category-b source tarballs? If the dependency is provided as a binary by the maintainer, then surely it is up to them to apply patches and provide patched builds? Likewise, surely security fixes will be applied by the maintainers to their source? -Rob [1] http://www.apache.org/legal/resolved.html#category-b rhino -- Google V8 nss -- openssl Seamonkey -- Mulberry library but that doesn't seem to be a priority for 4.0 :( . Pedro.
Wikipedia pages
FYI: Just noticed that the Wikipedia office suite comparison page [1] has an entry for Apache OpenOffice. This says that the licence is LGPL, which is wrong. The correct license is mentioned on the AOO page [2]. [1] http://en.wikipedia.org/wiki/Comparison_of_office_suites [2] http://en.wikipedia.org/wiki/Apache_OpenOffice
Re: Feedback on the CMS
On 11 May 2012 21:23, Joe Schaefer joe_schae...@yahoo.com wrote: - Original Message - From: Rob Weir robw...@apache.org To: ooo-dev@incubator.apache.org; Joe Schaefer joe_schae...@yahoo.com Cc: Sent: Friday, May 11, 2012 2:32 PM Subject: Re: Feedback on the CMS On Fri, May 11, 2012 at 2:18 PM, Joe Schaefer joe_schae...@yahoo.com wrote: With 1100 builds so far the ooo-site CMS instance is only 350 builds behind www.apache.org as the most-used CMS tree so far. I monitor the CMS logs daily to evaluate usage and this project publishes about as often as all our other projects combined, which really makes me wonder where we'd be here if the org had never created the CMS in the first place. Wow. Impressive stats. I know I use it nearly on a daily basis. The ooo-site is far and away the largest instance at over 9GB total. The reason I'm writing here is to ask general questions about user satisfaction with the CMS: 1) Is there any aspect of the CMS that needs immediate improvement? It works for me. 2) Are you satisfied with the workflow, or are there areas that could stand improvement? For the novice, it would be useful to have more guidance text on what to do next. So maybe a streamlined easy interface, and then the full version. Ok, thanks. I dunno about a steamlined interface, but more inline documentation is probably called for. Perhaps add a header bar to the pages to make it easy to navigate between editing and build, staging and live. It's not immediately obvious how to get back to the CMS, as there are no back links (have to use the browser back button) Or display such external pages in a new window, rather than replacing the current page. 3) Is there anything that should be done to encourage more users who are not committers to use the CMS to submit patches to the list? There is a live markdown preview of changes, but none given for HTML pages. Since most of the openoffice.org site is still HTML, this would be very useful and help catch errors before staging. There are security implications about using a project's rendering code within the CMS- it complicates things well beyond my threshold for that sort of thing. When all else fails the Static view will render the core HTML natively with many of the linkages preserved, so you'll at least get some idea from that how things will look on staging post-build. 4) Are there any UI features you'd like to see implemented, either in the web interface or the publication script? In the web interface, something that would poll the build and automatically refresh to the staging server when the build is complete. Perhaps- I just added a similar feature to the publication script, and yes I'm having a hard time convincing users to pay attention to the build results before trying to publish.
Re: svn commit: r1336368 - /incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext
On 10 May 2012 07:17, Dennis E. Hamilton dennis.hamil...@acm.org wrote: 1. You can Save as UTF8 in Windows Notepad. 2. The BOM (Byte-Order-Mark) is a special two-byte prefix that is usually used with UTF16 to determine whether the two bytes of each 16-bit code are big-endian or little-endian. Some products (including Windows Notepad) also put a BOM on the front of UTF8 streams. Some software is hostile to it being there, other software accepts it and recognizes the following code as UTF8 anyhow. You ran into a hostile case. Since you don't see the BOM (it is on front of the file but is not treated as a character), and you are on Windows, you need a text editor that doesn't produce them and also discards any that it encounters. I recommend an HTML editor. If you prefer text raw editing, I think jEdit will work for. It is a Java application, available on SourceForge. The Windows version of gedit will also save text in UTF8. That probably doesn't produce a BOM. (It is difficult to know if one is there or not without looking at the beginning of the file in a hex editor/viewer.) My copy of Notepad++ (v5.9) has the following Encoding Menu options: Encode in ANSI Encode in UTF-8 without BOM Encode in UTF-8 ... Convert to ANSI Convert to UTF-8 without BOM Convert to UTF-8 ... - Dennis -Original Message- From: Reizinger Zoltán [mailto:zreizin...@hdsnet.hu] Sent: Wednesday, May 09, 2012 22:42 To: ooo-dev@incubator.apache.org Subject: Re: svn commit: r1336368 - /incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext 2012.05.09. 23:02 keltezéssel, Dave Fisher írta: On May 9, 2012, at 1:28 PM, Reizinger Zoltán wrote: I'm not programmer and try to change Hungarian site. What is the BOM? In this environment hard to me to do any useful work changing the Hungarian site to useful format. I will stop doing it. I'd like to understand how that bad character was added. You weren't the only one with the same problem and you won't be the last. What do you use to edit the mdtext files? I used win7 notepad first(it was coded as ASCII, which is wrong if I need to use accented characters, but I not was aware to this). In second case in Notepad ++ when I converted from ASCII coding to UTF-8, and I think it was correctly coded, possibly I needs to be aware to another settings, which I don't know. Zoltan But how can I proceed to do it? I've fixed these two files for you. It looks good at www.openoffice.org/hu/. You can proceed. Regards, Dave Thanks, Zoltan 2012.05.09. 21:49 keltezéssel, Dave Fisher írta: Same problem here - what are you using to cause BOM? On May 9, 2012, at 12:42 PM, r4z...@apache.org wrote: Author: r4zoli Date: Wed May 9 19:42:28 2012 New Revision: 1336368 URL: http://svn.apache.org/viewvc?rev=1336368view=rev Log: (empty) Modified: incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext Modified: incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext?rev=1336368r1=1336367r2=1336368view=diff == --- incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext (original) +++ incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext Wed May 9 19:42:28 2012 @@ -1,10 +1,10 @@ -home: home -search: keresés +home: home +search: keresés name: Apache OpenOffice (incubating) -tagline: (incubating) | Nyílt és ingyenes irodai programcsomag +tagline: (incubating) | NyÃlt és ingyenes irodai programcsomag logo: AOO_logos/OOo_Website_v2_copy.png domain: www.openoffice.org divid: bannera announce: Megjelent az Apache OpenOffice 3.4 announceurl: /hu/aoo34.html -announcetip: Olvassa el a bejelentést +announcetip: Olvassa el a bejelentést \ No newline at end of file
Re: svn commit: r1336368 - /incubator/ooo/ooo-site/trunk/content/hu/brand.mdtext
On 10 May 2012 19:52, Juan C. Sanz juancsa...@hotmail.com wrote: El 10/05/2012 20:36, Dave Fisher escribió: On May 10, 2012, at 11:15 AM, sebb wrote: On 10 May 2012 07:17, Dennis E. Hamiltondennis.hamil...@acm.org wrote: 1. You can Save as UTF8 in Windows Notepad. 2. The BOM (Byte-Order-Mark) is a special two-byte prefix that is usually used with UTF16 to determine whether the two bytes of each 16-bit code are big-endian or little-endian. Some products (including Windows Notepad) also put a BOM on the front of UTF8 streams. Some software is hostile to it being there, other software accepts it and recognizes the following code as UTF8 anyhow. You ran into a hostile case. Since you don't see the BOM (it is on front of the file but is not treated as a character), and you are on Windows, you need a text editor that doesn't produce them and also discards any that it encounters. I recommend an HTML editor. If you prefer text raw editing, I think jEdit will work for. It is a Java application, available on SourceForge. The Windows version of gedit will also save text in UTF8. That probably doesn't produce a BOM. (It is difficult to know if one is there or not without looking at the beginning of the file in a hex editor/viewer.) My copy of Notepad++ (v5.9) has the following Encoding Menu options: That's Notepad++, not Windows Notepad. Encode in ANSI Encode in UTF-8 without BOM Encode in UTF-8 ... Convert to ANSI Convert to UTF-8 without BOM Convert to UTF-8 ... Thanks! I've added a note to http://incubator.apache.org/openofficeorg/website-local.html In the note you say If you use Notepad on WIndows you have several options for saving or converting to UTF. Choose the UTF-8 without BOM option but this is not an option in notepad (at least in mine) but in Notepad++ which is not the windows one. Agreed, I was referring to the 3rd party Notepad++ app (which had already been mentioned). Regards Juan C. Regards, Dave
Re: [ML] Please state that the mail was approved and that the author is not subscribed to the ML
On 9 May 2012 02:01, Larry Gusaas larry.gus...@gmail.com wrote: On 2012-05-08 4:32 PM Marcus (OOo) wrote: Am 05/09/2012 12:07 AM, schrieb Simon Phipps: On 8 May 2012, at 22:55, Marcus (OOo) wrote: When you as ML moderator approve a post to a mailing list, please can you also state that the author is not subscribed to the ML and that everybody who wants to replay has to CC'ing the author? This would be very helpful from the start of the first posting. As a moderator, I am not aware of any way to do this; the moderator has no means to add a comment to an approved posting. It is possible to tell from the message headers that a message has been moderated, so perhaps you could add a rule/macro to your mail client to add the originator as a cc on any reply when this header is present? I remember that it was possible with the old OOo mailing lists. I cannot believe that this is gone even when here a different ML service is working. ;-) If you can tell me how to do it in Thnderbird I can give it a try. Marcus Messages from an unsubscribed poster contain the following header: Delivered-To: moderator for ooo-dev@incubator.apache.org You can create a filter on this header with Thunderbird for emails. If you follow this list as a newsgroup using, as I do, you can't create a filter. There were many complaints on the old OOo lists about allowing unsubscribed posters. Unless they are clearly identified in the Subject line, it is a pain in the ass to identify them. Nothing was ever done to rectify the problem. Possible solutions: - don't allow posts unless subscribed (e.g. reject the post with a link to the subscription page) - allow postings by unsubscribed users, but let them follow the replies via one of the archive services. It's a lot of work trying to ensure that unsubscribed posters are copied - much more work than the one-time effort of subscribing. -- _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-gusaas.com An artist is never ahead of his time but most people are far behind theirs. - Edgard Varese
update*.services.openoffice.org
I see there have been some attempts to understand and fix the update functionality. One aspect that does not seem to have been covered is that several of the host names embedded in existing releases currently point to what appears to be a 3rd party host, viz: sd-web4.staroffice.de This resolves to IP 192.18.197.105 but is not responding. Are there any plans to bring the hostnames in-house? The host names that are affected include the following: update.services.openoffice.org is an alias for sd-web4.staroffice.de. update30.services.openoffice.org is an alias for sd-web2.staroffice.de. update31.services.openoffice.org is an alias for sd-web2.staroffice.de. update32.services.openoffice.org is an alias for sd-web2.staroffice.de. update33.services.openoffice.org is an alias for sd-web2.staroffice.de. update34.services.openoffice.org is an alias for sd-web2.staroffice.de. update35.services.openoffice.org is an alias for sd-web2.staroffice.de. update36.services.openoffice.org is an alias for sd-web2.staroffice.de. I don't know if there are any others.
Re: Draft blog post: Avoiding OpenOffice Download Scams
On 30 April 2012 19:10, Rob Weir robw...@apache.org wrote: https://blogs.apache.org/preview/OOo/?previewEntry=draft_avoiding_openoffice_download_scams I know Louis and others have dealt with these things for longer. Anything else I should mention? I considered adding a discussion of the importance of MD5 hashes, etc., but that is not really the skill level of the end user who downloads OpenOffice. I'm also cc'ing trademarks@ since it may be of interest to them and/or they might have feedback. A few suggestions: The first paragraph should be quoted and / or in italic. s/the open source license/its open source license/ - there are several instances of this. If the end-user is likely to find the concept of MD5 difficult, won't they also find it difficult to use the provided e-mail link? i.e. mailto:ooo-private-AT-incubator.apache-DOT-org Also, do such reports need to go to the private mailing list? -Rob
Re: Draft blog post: Avoiding OpenOffice Download Scams
On 30 April 2012 19:41, Rob Weir robw...@apache.org wrote: On Mon, Apr 30, 2012 at 2:27 PM, sebb seb...@gmail.com wrote: On 30 April 2012 19:10, Rob Weir robw...@apache.org wrote: https://blogs.apache.org/preview/OOo/?previewEntry=draft_avoiding_openoffice_download_scams I know Louis and others have dealt with these things for longer. Anything else I should mention? I considered adding a discussion of the importance of MD5 hashes, etc., but that is not really the skill level of the end user who downloads OpenOffice. I'm also cc'ing trademarks@ since it may be of interest to them and/or they might have feedback. A few suggestions: The first paragraph should be quoted and / or in italic. s/the open source license/its open source license/ - there are several instances of this. Yes. If the end-user is likely to find the concept of MD5 difficult, won't they also find it difficult to use the provided e-mail link? It is a hyperlink so in most cases it will just launch their email. Sorry, was not clear - I meant that they might have difficulty de-mangling the anti-spam measure. Maybe it would be better to direct them to a web-page that can give more information on reporting such problems. That page could be updated as necessary (e.g. when the e-mail address changes on graduation). Or the page could use plain-text mail links to temporary mail aliases that are rotated (would need to involve infra on that). Having a separate reporting page would be much more flexible; just make sure that its URL does not change (or a redirect is used). i.e. mailto:ooo-private-AT-incubator.apache-DOT-org Also, do such reports need to go to the private mailing list? It is for the user's safety. Otherwise I can be sure we'll get their home phone numbers and credit card numbers posted to the public list. Remember, we're talking about the very end users who have already been scammed once. So we already know that they are not the most careful web users. OK, understood. Of course, we don't need to collect their reports if we don't want to. But they send them already. This particular one was sent to our security list. -Rob -Rob
Re: Mirroring both OOo and AOOo Fwd: [Daniel Shahaf: Opt-out from mirroring resource-intensive projects]
On 20 April 2012 13:26, Daniel Shahaf danie...@apache.org wrote: OOo PPMC: Several mirror operators have asked whether they are expected to carry both their preexisting/legacy OOo mirrors and the AOOo mirror. We're assuming the legacy OOo mirrors can be dropped once an AOOo release is Out There. If that's not the case, say so. Reminder: ASF's policy is that Apache mirrors may only carry the latest release from each minor line (1.5.x, 1.6.x, ...) which is still supported / developed by the community. It's not possible to ensure that the download page and all mirrors are simultaneously updated, so AFAIK it has also been policy to keep the previous release around for a few days before deleting it. Thus mirrors will temporarily need space for both old and new versions. Cheers, -- Apache Infrastructure - Forwarded message from Daniel Shahaf danie...@apache.org - From: Daniel Shahaf danie...@apache.org Subject: Opt-out from mirroring resource-intensive projects To: Apache Mirror Operators mirr...@apache.org Date: Fri, 20 Apr 2012 12:37:04 +0300 Reply-To: mirr...@apache.org Message-ID: 20120420093704.GA2976@lp-shahaf.local By popular demand, we have implemented an opt-out option: mirror operators that are unable to mirror Apache OpenOffice due to its disk or bandwidth requirements may do so by changing the rsync source from: rsync.apache.org::apache-dist to: rsync.apache.org::apache-dist-most http://www.apache.org/info/how-to-mirror has been updated to reflect this. Thanks as always for your continued support. Cheers, -- Daniel Shahaf Apache Infrastructure - End forwarded message -
[www] Website must display disclaimer text
The website clearly mentions that the podling is in the Incubator, but it also needs to prominently display the disclaimer, see: http://incubator.apache.org/guides/branding.html#disclaimers Please could this be added ASAP? Thanks!
