You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andrea Pescetti <pe...@openoffice.org> on 2011/12/29 21:21:28 UTC
Re: draft - Website migration(+) announcement - draft
On 29/12/2011 drew wrote:
> During this migration period community developers also made great
> progress with the application code. Ariel Constenla-Haile, one of the
> community developers, generated binary packages, suitable for early
> testing purposes, from the current Apache OpenOffice code repository.
> Available for download at http://people.apache.org/~arielch/packages
I wouldn't send out public announcements about Ariel's builds. The
interest is huge, and people might download them just out of curiosity
and damage their existing OpenOffice.org installation and extensions.
It's probably better to announce, at due time, development builds that
won't interfere with the installed version (and ideally, not even with
the user profile if the BerkeleyDB removal has implications on that).
Regards,
Andrea.
RE: draft - Website migration(+) announcement - draft
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1
-----Original Message-----
From: Dave Fisher [mailto:dave2wave@comcast.net]
Sent: Sunday, January 01, 2012 11:48
To: ooo-dev@incubator.apache.org
Subject: Re: draft - Website migration(+) announcement - draft
Hi,
On Jan 1, 2012, at 11:30 AM, Dennis E. Hamilton wrote:
[ ... ]
>
> 1.There should always be a web-location permalink (whether project blog or
> elsewhere)
I think it should be flexible - a choice between the blog and a podling page.
We should have a news directory - http://incubator.apache.org/openofficeorg/news/ then each announcement page is "annouce-YYYYMMDD.mdtext" and non-English versions are probably "announce-YYYYMMDD.LANG.mdtext". If we do this the url in the email needs to be "http://incubator.apache.org/openofficeorg/news/announce-YYYYMMDD" and the apache web servers will negotiate the best page for the user.
We can use staging to build announcements and co-ordinate publishing the site.
>
> 2. The announcement list should only carry plaintext messages with suitable
> links for archival web location, extended content, other-language versions,
> etc.
The more concise the announcement message is, the more likely it will be shared via social media.
Regards,
Dave
[ ... ]
Re: draft - Website migration(+) announcement - draft
Posted by Dave Fisher <da...@comcast.net>.
Hi,
On Jan 1, 2012, at 11:30 AM, Dennis E. Hamilton wrote:
> There are, of course, some cautious folks who still see their incoming mail as
> plaintext regardless of how it is sent. It matters, in that case, that the
> plaintext rendering be sufficient for the links to the full, formatted content
> to be seen and followed at the option of the recipient. The plaintext should
> also be a reasonable representation.
>
> I think a good compromise would be for the announcement to provide an abstract
> in the case when the full text is substantial, with appropriate links. And in
> that case, a plaintext-only form would be ideal, with a link to a web version.
> The web version can be internationalized in many ways, including via browser
> language detection as well as user selection.
>
> This musing has me think that
>
> 1.There should always be a web-location permalink (whether project blog or
> elsewhere)
I think it should be flexible - a choice between the blog and a podling page.
We should have a news directory - http://incubator.apache.org/openofficeorg/news/ then each announcement page is "annouce-YYYYMMDD.mdtext" and non-English versions are probably "announce-YYYYMMDD.LANG.mdtext". If we do this the url in the email needs to be "http://incubator.apache.org/openofficeorg/news/announce-YYYYMMDD" and the apache web servers will negotiate the best page for the user.
We can use staging to build announcements and co-ordinate publishing the site.
>
> 2. The announcement list should only carry plaintext messages with suitable
> links for archival web location, extended content, other-language versions,
> etc.
The more concise the announcement message is, the more likely it will be shared via social media.
Regards,
Dave
>
> - Dennis
>
> PS: One advantage of the always-open-the-plaintext approach is that it is
> generally easy to see the full URLs of hyperlinks, not just the linked text,
> and be satisfied that there is no phishing/tracking going on. It is also
> possible to archive/reforward plaintext more reliably (and it is amazing to me
> how many list-server setups do such a bad job of it after all these years).
>
> -----Original Message-----
> From: Andrea Pescetti [mailto:pescetti@apache.org]
> Sent: Sunday, January 01, 2012 10:56
> To: ooo-dev@incubator.apache.org
> Subject: Re: draft - Website migration(+) announcement - draft
>
> On 31/12/2011 Rob Weir wrote:
>> HTML is not very reliable in email. But maybe we could do this: Create
>> the newsletter as a webpage, either on the wiki, or via mdtext or the
>> blog. That has the full text of the newsletter. Then for the announce
>> list, we just include the table of contents or the first paragraph or some
>> other enticing lead-in, and then link to the full newsletter.
>
> We could also send the whole HTML newsletter with the usual initial link
> "If the newsletter does not display correctly, click here for the Web
> version", or similar text.
>
> This initial line could also be used to say that translated versions of
> the newsletter exist. They would not be sent until the time this project
> has native-language announce lists, but they would be linked from the
> online version.
>
> Regards,
> Andrea.
RE: draft - Website migration(+) announcement - draft
Posted by "Dennis E. Hamilton" <de...@acm.org>.
There are, of course, some cautious folks who still see their incoming mail as
plaintext regardless of how it is sent. It matters, in that case, that the
plaintext rendering be sufficient for the links to the full, formatted content
to be seen and followed at the option of the recipient. The plaintext should
also be a reasonable representation.
I think a good compromise would be for the announcement to provide an abstract
in the case when the full text is substantial, with appropriate links. And in
that case, a plaintext-only form would be ideal, with a link to a web version.
The web version can be internationalized in many ways, including via browser
language detection as well as user selection.
This musing has me think that
1.There should always be a web-location permalink (whether project blog or
elsewhere)
2. The announcement list should only carry plaintext messages with suitable
links for archival web location, extended content, other-language versions,
etc.
- Dennis
PS: One advantage of the always-open-the-plaintext approach is that it is
generally easy to see the full URLs of hyperlinks, not just the linked text,
and be satisfied that there is no phishing/tracking going on. It is also
possible to archive/reforward plaintext more reliably (and it is amazing to me
how many list-server setups do such a bad job of it after all these years).
-----Original Message-----
From: Andrea Pescetti [mailto:pescetti@apache.org]
Sent: Sunday, January 01, 2012 10:56
To: ooo-dev@incubator.apache.org
Subject: Re: draft - Website migration(+) announcement - draft
On 31/12/2011 Rob Weir wrote:
> HTML is not very reliable in email. But maybe we could do this: Create
> the newsletter as a webpage, either on the wiki, or via mdtext or the
> blog. That has the full text of the newsletter. Then for the announce
> list, we just include the table of contents or the first paragraph or some
> other enticing lead-in, and then link to the full newsletter.
We could also send the whole HTML newsletter with the usual initial link
"If the newsletter does not display correctly, click here for the Web
version", or similar text.
This initial line could also be used to say that translated versions of
the newsletter exist. They would not be sent until the time this project
has native-language announce lists, but they would be linked from the
online version.
Regards,
Andrea.
Re: draft - Website migration(+) announcement - draft
Posted by Andrea Pescetti <pe...@apache.org>.
On 31/12/2011 Rob Weir wrote:
> HTML is not very reliable in email. But maybe we could do this: Create
> the newsletter as a webpage, either on the wiki, or via mdtext or the
> blog. That has the full text of the newsletter. Then for the announce
> list, we just include the table of contents or the first paragraph or some
> other enticing lead-in, and then link to the full newsletter.
We could also send the whole HTML newsletter with the usual initial link
"If the newsletter does not display correctly, click here for the Web
version", or similar text.
This initial line could also be used to say that translated versions of
the newsletter exist. They would not be sent until the time this project
has native-language announce lists, but they would be linked from the
online version.
Regards,
Andrea.
Re: draft - Website migration(+) announcement - draft
Posted by Rob Weir <ro...@apache.org>.
On Sat, Dec 31, 2011 at 2:56 PM, drew <dr...@baseanswers.com> wrote:
> **
> On Thu, 2011-12-29 at 15:19 -0800, kay.schenk wrote:
>
>
>
> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>
> On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com> wrote:
> > On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
> >> On 29/12/2011 drew wrote:
> >> > During this migration period community developers also made great
> >> > progress with the application code. Ariel Constenla-Haile, one of the
> >> > community developers, generated binary packages, suitable for early
> >> > testing purposes, from the current Apache OpenOffice code repository.
> >> > Available for download at http://people.apache.org/~arielch/packages
> >>
> >> I wouldn't send out public announcements about Ariel's builds. The
> >> interest is huge, and people might download them just out of curiosity
> >> and damage their existing OpenOffice.org installation and extensions.
> >
> > Well, good point. I think it is important to be clear that the code (the
> > application and therefore the 'thing' of real importance to users) is
> > moving forward also however..not sure how to do that without something
> > concrete to point to - as you say though it is something that can
> > backfire badly, if people just install those files..
> >
> >> It's probably better to announce, at due time, development builds that
> >> won't interfere with the installed version (and ideally, not even with
> >> the user profile if the BerkeleyDB removal has implications on that).
> >
> > Then maybe the announcement should just chronicle the items of interest:
> >
> > - Developer snapshot's are becoming available - that's Ariel's page as
> > one
> > - Daily builds are happening and there is a real location for those
> > - others?
> >
> > and then point them to a page (website or wiki?) for those interested in
> > getting in on the bleeding edge of testing, maybe?
> >
>
>
> it is a good little snippet of info. But there is so much more to
> say, especially for an audience that we've haven't been
> (re-)introduced to yet. Where to start?
>
> I wonder whether it would be worth reviving the OpenOffice Newsletter?
> This was sent out to the old announce list. It was erratic toward
> the end, but at one point I think it was coming out every month.
>
> Some examples:
>
> March 2011:
> http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>
> December 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>
> September 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>
> A format like that allows us to bundle a few small posts, news
> clippings, announcements, etc., into a fuller package, maybe with
> greater impact.
>
> For example, we could a series of these over the next few months:
>
> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
> migration, copyleft-free build, start of test effort, links to blog,
> mailing lists, migration status, announcement of pending retirement of
> openoffice.org email addresses and lists, etc.
>
> Newsletter #2 (a month later): availability of test builds for 3.4
> (hopefully on Windows by then), how to help with test effort, reminder
> on mailing list migration and mail forwarding shutdown. Gathering
> proposals for AOO 4.0.
>
> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>
> A newsletter could be put together on the wiki and then the
> announcement can be a link to the online newsletter.
>
>
>
>
> Alright - well, without worry about a schedule beyond this one...
>
> Another draft..
>
> This is HTML and not sure what the list will do with it :-/ (is it a silly
> question to ask if the new announce list accepts html? )
>
HTML is not very reliable in email. But maybe we could do this: Create
the newsletter as a webpage, either on the wiki, or via mdtext or the
blog. That has the full text of the newsletter. Then for the announce
list, we just include the table of contents or the first paragraph or some
other enticing lead-in, and then link to the full newsletter. That way we
can also point users to the newsletter from Google+, Twitter, Facebook,
support Forums, etc. One newsletter, but multiple paths to lead users to
it.
-Rob
Re: draft - Website migration(+) announcement - draft
Posted by drew <dr...@baseanswers.com>.
On Sat, 2011-12-31 at 12:05 -0800, Dave Fisher wrote:
> Drew,
>
> HTML is not so good as there is no consistency in presentation.
well...
>
> Hagar's graphic gives me a missing plug-in message.
I suppose you mean the missing image in the email, just below the line
with Hagar's name?
That's just a png of the logo used on the forum, and like the others was
embedded in the mail, from copies on my local disc, using Evolution. I
suppose also it's the fact images are stripped for the missing gaphics..
*duh*.
Actually, the image/link to the forum shows another small issue - the
linked page still brands to Oracle.. I'll see if I can look after that
with a minimum of fuss.
Otherwise - the newsletters referenced by Kay, they where using HTML,
just not any graphics..hmm, maybe that's a blog version of the basic
content :)
//drew
>
> This is the weird html:
>
> <A HREF="http://incubator.apache.org/openofficeorg"><IMG SRC="cid:1325361222.3766.2.camel@sybil-gnome" ALIGN="bottom" ALT="Apache OpenOffice (uncubating) Logo " BORDER="0"></A>
>
> Apple Mail can't understand the IMG mime-type.
>
> The A tag links to another location ...
>
> I think plain text is best.
>
> I'm only commenting about form - I don't have time to comment about the content.
>
> Regards,
> Dave
>
> On Dec 31, 2011, at 11:56 AM, drew wrote:
>
> > On Thu, 2011-12-29 at 15:19 -0800, kay.schenk wrote:
> >>
> >>
> >> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
> >> On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com> wrote:
> >> > On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
> >> >> On 29/12/2011 drew wrote:
> >> >> > During this migration period community developers also made great
> >> >> > progress with the application code. Ariel Constenla-Haile, one of the
> >> >> > community developers, generated binary packages, suitable for early
> >> >> > testing purposes, from the current Apache OpenOffice code repository.
> >> >> > Available for download at http://people.apache.org/~arielch/packages
> >> >>
> >> >> I wouldn't send out public announcements about Ariel's builds. The
> >> >> interest is huge, and people might download them just out of curiosity
> >> >> and damage their existing OpenOffice.org installation and extensions.
> >> >
> >> > Well, good point. I think it is important to be clear that the code (the
> >> > application and therefore the 'thing' of real importance to users) is
> >> > moving forward also however..not sure how to do that without something
> >> > concrete to point to - as you say though it is something that can
> >> > backfire badly, if people just install those files..
> >> >
> >> >> It's probably better to announce, at due time, development builds that
> >> >> won't interfere with the installed version (and ideally, not even with
> >> >> the user profile if the BerkeleyDB removal has implications on that).
> >> >
> >> > Then maybe the announcement should just chronicle the items of interest:
> >> >
> >> > - Developer snapshot's are becoming available - that's Ariel's page as
> >> > one
> >> > - Daily builds are happening and there is a real location for those
> >> > - others?
> >> >
> >> > and then point them to a page (website or wiki?) for those interested in
> >> > getting in on the bleeding edge of testing, maybe?
> >> >
> >>
> >>
> >> it is a good little snippet of info. But there is so much more to
> >> say, especially for an audience that we've haven't been
> >> (re-)introduced to yet. Where to start?
> >>
> >> I wonder whether it would be worth reviving the OpenOffice Newsletter?
> >> This was sent out to the old announce list. It was erratic toward
> >> the end, but at one point I think it was coming out every month.
> >>
> >> Some examples:
> >>
> >> March 2011: http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
> >>
> >> December 2010:
> >> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
> >>
> >> September 2010:
> >> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
> >>
> >> A format like that allows us to bundle a few small posts, news
> >> clippings, announcements, etc., into a fuller package, maybe with
> >> greater impact.
> >>
> >> For example, we could a series of these over the next few months:
> >>
> >> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
> >> migration, copyleft-free build, start of test effort, links to blog,
> >> mailing lists, migration status, announcement of pending retirement of
> >> openoffice.org email addresses and lists, etc.
> >>
> >> Newsletter #2 (a month later): availability of test builds for 3.4
> >> (hopefully on Windows by then), how to help with test effort, reminder
> >> on mailing list migration and mail forwarding shutdown. Gathering
> >> proposals for AOO 4.0.
> >>
> >> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
> >>
> >> A newsletter could be put together on the wiki and then the
> >> announcement can be a link to the online newsletter.
> >>
> >
> >
> > Alright - well, without worry about a schedule beyond this one...
> >
> > Another draft..
> >
> > This is HTML and not sure what the list will do with it :-/ (is it a silly question to ask if the new announce list accepts html? )
> >
> > ******
> >
> > Newsletter
> >
> >
> > < ꝏ January 2012 ꝏ >
> >
> >
> >
> > Infrastructure
> >
> > The Apache OpenOffice podling project management committee (PPMC) is
> > pleased to present a new home for the OpenOffice.org website.
> >
> >
> >
> > The migration of such a large web presence could not happen without the
> > thoughtful dedication and commitment from many members of the
> > OpenOffice.org community, none more so then Dave Fisher, Kay Schenk, Joe
> > Schaefer and Gavin McDonald. The PPMC thanks all the community members
> > for your continued support and offers a special thank you to these
> > individuals for a job well done.
> >
> >
> > Development
> >
> > During this migration period community developers also made great
> > progress with the application code. Ariel Constenla-Haile, one of the
> > community developers, generated binary packages, suitable for early
> > testing purposes, from the current Apache OpenOffice code repository.
> >
> >
> > Community
> >
> > Hagar Delest put together a summary of of EN forum activity from the launch date to present.
> >
> >
> > http://user.services.openoffice.org/en/forum/viewtopic.php?f=50&t=46497.
> > A graph shows the number of posts, registered members, topics and
> > topics marked as solved. There is nothing very exciting, which is just
> > what one wants after changing hosts.
> >
> > F. C. Costero added this comment to the subject on the AOO development mailing list:
> > "My own experience is that there is no noticeable change in the forum
> > since the migration to ASF except for the feather on every page.
> > Thanks to the ASF infra folks for keeping all that magic stuff
> > invisible."
> >
> >
> > Start the new year right
> >
> > - visit the new Apache OpenOffice home now!
> > http://openoffice.org
> >
> >
> >
> > ******
> >
>
Re: draft - Website migration(+) announcement - draft
Posted by Dave Fisher <da...@comcast.net>.
Drew,
HTML is not so good as there is no consistency in presentation.
Hagar's graphic gives me a missing plug-in message.
This is the weird html:
<A HREF="http://incubator.apache.org/openofficeorg"><IMG SRC="cid:1325361222.3766.2.camel@sybil-gnome" ALIGN="bottom" ALT="Apache OpenOffice (uncubating) Logo " BORDER="0"></A>
Apple Mail can't understand the IMG mime-type.
The A tag links to another location ...
I think plain text is best.
I'm only commenting about form - I don't have time to comment about the content.
Regards,
Dave
On Dec 31, 2011, at 11:56 AM, drew wrote:
> On Thu, 2011-12-29 at 15:19 -0800, kay.schenk wrote:
>>
>>
>> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>> On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com> wrote:
>> > On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
>> >> On 29/12/2011 drew wrote:
>> >> > During this migration period community developers also made great
>> >> > progress with the application code. Ariel Constenla-Haile, one of the
>> >> > community developers, generated binary packages, suitable for early
>> >> > testing purposes, from the current Apache OpenOffice code repository.
>> >> > Available for download at http://people.apache.org/~arielch/packages
>> >>
>> >> I wouldn't send out public announcements about Ariel's builds. The
>> >> interest is huge, and people might download them just out of curiosity
>> >> and damage their existing OpenOffice.org installation and extensions.
>> >
>> > Well, good point. I think it is important to be clear that the code (the
>> > application and therefore the 'thing' of real importance to users) is
>> > moving forward also however..not sure how to do that without something
>> > concrete to point to - as you say though it is something that can
>> > backfire badly, if people just install those files..
>> >
>> >> It's probably better to announce, at due time, development builds that
>> >> won't interfere with the installed version (and ideally, not even with
>> >> the user profile if the BerkeleyDB removal has implications on that).
>> >
>> > Then maybe the announcement should just chronicle the items of interest:
>> >
>> > - Developer snapshot's are becoming available - that's Ariel's page as
>> > one
>> > - Daily builds are happening and there is a real location for those
>> > - others?
>> >
>> > and then point them to a page (website or wiki?) for those interested in
>> > getting in on the bleeding edge of testing, maybe?
>> >
>>
>>
>> it is a good little snippet of info. But there is so much more to
>> say, especially for an audience that we've haven't been
>> (re-)introduced to yet. Where to start?
>>
>> I wonder whether it would be worth reviving the OpenOffice Newsletter?
>> This was sent out to the old announce list. It was erratic toward
>> the end, but at one point I think it was coming out every month.
>>
>> Some examples:
>>
>> March 2011: http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>>
>> December 2010:
>> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>>
>> September 2010:
>> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>>
>> A format like that allows us to bundle a few small posts, news
>> clippings, announcements, etc., into a fuller package, maybe with
>> greater impact.
>>
>> For example, we could a series of these over the next few months:
>>
>> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
>> migration, copyleft-free build, start of test effort, links to blog,
>> mailing lists, migration status, announcement of pending retirement of
>> openoffice.org email addresses and lists, etc.
>>
>> Newsletter #2 (a month later): availability of test builds for 3.4
>> (hopefully on Windows by then), how to help with test effort, reminder
>> on mailing list migration and mail forwarding shutdown. Gathering
>> proposals for AOO 4.0.
>>
>> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>>
>> A newsletter could be put together on the wiki and then the
>> announcement can be a link to the online newsletter.
>>
>
>
> Alright - well, without worry about a schedule beyond this one...
>
> Another draft..
>
> This is HTML and not sure what the list will do with it :-/ (is it a silly question to ask if the new announce list accepts html? )
>
> ******
>
> Newsletter
>
>
> < ꝏ January 2012 ꝏ >
>
>
>
> Infrastructure
>
> The Apache OpenOffice podling project management committee (PPMC) is
> pleased to present a new home for the OpenOffice.org website.
>
>
>
> The migration of such a large web presence could not happen without the
> thoughtful dedication and commitment from many members of the
> OpenOffice.org community, none more so then Dave Fisher, Kay Schenk, Joe
> Schaefer and Gavin McDonald. The PPMC thanks all the community members
> for your continued support and offers a special thank you to these
> individuals for a job well done.
>
>
> Development
>
> During this migration period community developers also made great
> progress with the application code. Ariel Constenla-Haile, one of the
> community developers, generated binary packages, suitable for early
> testing purposes, from the current Apache OpenOffice code repository.
>
>
> Community
>
> Hagar Delest put together a summary of of EN forum activity from the launch date to present.
>
>
> http://user.services.openoffice.org/en/forum/viewtopic.php?f=50&t=46497.
> A graph shows the number of posts, registered members, topics and
> topics marked as solved. There is nothing very exciting, which is just
> what one wants after changing hosts.
>
> F. C. Costero added this comment to the subject on the AOO development mailing list:
> "My own experience is that there is no noticeable change in the forum
> since the migration to ASF except for the feather on every page.
> Thanks to the ASF infra folks for keeping all that magic stuff
> invisible."
>
>
> Start the new year right
>
> - visit the new Apache OpenOffice home now!
> http://openoffice.org
>
>
>
> ******
>
Re: draft - Website migration(+) announcement - draft
Posted by drew <dr...@baseanswers.com>.
On Thu, 2011-12-29 at 15:19 -0800, kay.schenk wrote:
>
>
> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>
> On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com>
> wrote:
> > On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
> >> On 29/12/2011 drew wrote:
> >> > During this migration period community developers also
> made great
> >> > progress with the application code. Ariel
> Constenla-Haile, one of the
> >> > community developers, generated binary packages, suitable
> for early
> >> > testing purposes, from the current Apache OpenOffice code
> repository.
> >> > Available for download at
> http://people.apache.org/~arielch/packages
> >>
> >> I wouldn't send out public announcements about Ariel's
> builds. The
> >> interest is huge, and people might download them just out
> of curiosity
> >> and damage their existing OpenOffice.org installation and
> extensions.
> >
> > Well, good point. I think it is important to be clear that
> the code (the
> > application and therefore the 'thing' of real importance to
> users) is
> > moving forward also however..not sure how to do that without
> something
> > concrete to point to - as you say though it is something
> that can
> > backfire badly, if people just install those files..
> >
> >> It's probably better to announce, at due time, development
> builds that
> >> won't interfere with the installed version (and ideally,
> not even with
> >> the user profile if the BerkeleyDB removal has implications
> on that).
> >
> > Then maybe the announcement should just chronicle the items
> of interest:
> >
> > - Developer snapshot's are becoming available - that's
> Ariel's page as
> > one
> > - Daily builds are happening and there is a real location
> for those
> > - others?
> >
> > and then point them to a page (website or wiki?) for those
> interested in
> > getting in on the bleeding edge of testing, maybe?
> >
>
>
> it is a good little snippet of info. But there is so much
> more to
> say, especially for an audience that we've haven't been
> (re-)introduced to yet. Where to start?
>
> I wonder whether it would be worth reviving the OpenOffice
> Newsletter?
> This was sent out to the old announce list. It was erratic
> toward
> the end, but at one point I think it was coming out every
> month.
>
> Some examples:
>
> March 2011:
> http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>
> December 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>
> September 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>
> A format like that allows us to bundle a few small posts, news
> clippings, announcements, etc., into a fuller package, maybe
> with
> greater impact.
>
> For example, we could a series of these over the next few
> months:
>
> Newsletter #1: Intro to OpenOffice @ Apache. Announcements
> on
> migration, copyleft-free build, start of test effort, links to
> blog,
> mailing lists, migration status, announcement of pending
> retirement of
> openoffice.org email addresses and lists, etc.
>
> Newsletter #2 (a month later): availability of test builds for
> 3.4
> (hopefully on Windows by then), how to help with test effort,
> reminder
> on mailing list migration and mail forwarding shutdown.
> Gathering
> proposals for AOO 4.0.
>
> Newsletter #3 -- coverage of 3.4 release, press clippings,
> etc.
>
> A newsletter could be put together on the wiki and then the
> announcement can be a link to the online newsletter.
>
>
Alright - well, without worry about a schedule beyond this one...
Another draft..
This is HTML and not sure what the list will do with it :-/ (is it a
silly question to ask if the new announce list accepts html? )
******
Apache OpenOffice (uncubating) Logo
Newsletter
< ꝏ January 2012 ꝏ >
Infrastructure
The Apache OpenOffice podling project management committee (PPMC) is
pleased to present a new home for the OpenOffice.org website.
OpenOffice.org Logo
The migration of such a large web presence could not happen without the
thoughtful dedication and commitment from many members of the
OpenOffice.org community, none more so then Dave Fisher, Kay Schenk, Joe
Schaefer and Gavin McDonald. The PPMC thanks all the community members
for your continued support and offers a special thank you to these
individuals for a job well done.
Development
During this migration period community developers also made great
progress with the application code. Ariel Constenla-Haile, one of the
community developers, generated binary packages, suitable for early
testing purposes, from the current Apache OpenOffice code repository.
Community
Hagar Delest put together a summary of of EN forum activity from the
launch date to present.
OpenOffice.org User Community Forums logo
http://user.services.openoffice.org/en/forum/viewtopic.php?f=50&t=46497.
A graph shows the number of posts, registered members, topics and
topics marked as solved. There is nothing very exciting, which is just
what one wants after changing hosts.
F. C. Costero added this comment to the subject on the AOO development
mailing list:
"My own experience is that there is no noticeable change in the
forum
since the migration to ASF except for the feather on every page.
Thanks to the ASF infra folks for keeping all that magic stuff
invisible."
Start the new year right
- visit the new Apache OpenOffice home now!
http://openoffice.org
******
Re: (OT) Re: draft - Website migration(+) announcement - draft
Posted by drew <dr...@baseanswers.com>.
On Fri, 2011-12-30 at 10:14 -0500, Rob Weir wrote:
> On Fri, Dec 30, 2011 at 10:02 AM, drew <dr...@baseanswers.com> wrote:
> >> >
> >>
> >> 1700 currently, and another 200 or so coming in every hour.
> >>
> >> > It is advertised on www.openoffice.org ...
> >> >
> >
> > Hi,
> >
> > Question - who would have the ability to generate a monthly (or so)
> > report on the mail list activity to the group as a whole?
> >
>
> We have these reports:
>
> http://pulse.apache.org/#ooo-announce_at_incubator.apache.org
>
> That gives subscriber and post stats.
Yes - that is what I was looking for, thanks
>
> I just noticed that the new Italian list, ooo-utenti-it, is off to a
> great start with over 600 subscribers (list + digest). That is
> amazing, considering we only have around 200 on the English list.
>
That's great not that amazing though, not unexpected would be my
response I think, looking at it from a user demographics perspective.
//drew
Re: (OT) Re: draft - Website migration(+) announcement - draft
Posted by Rob Weir <ro...@apache.org>.
On Fri, Dec 30, 2011 at 10:02 AM, drew <dr...@baseanswers.com> wrote:
>> >
>>
>> 1700 currently, and another 200 or so coming in every hour.
>>
>> > It is advertised on www.openoffice.org ...
>> >
>
> Hi,
>
> Question - who would have the ability to generate a monthly (or so)
> report on the mail list activity to the group as a whole?
>
We have these reports:
http://pulse.apache.org/#ooo-announce_at_incubator.apache.org
That gives subscriber and post stats.
I just noticed that the new Italian list, ooo-utenti-it, is off to a
great start with over 600 subscribers (list + digest). That is
amazing, considering we only have around 200 on the English list.
-Rob
> That would be a nice to have report.
>
> //drew
>
(OT) Re: draft - Website migration(+) announcement - draft
Posted by drew <dr...@baseanswers.com>.
> >
>
> 1700 currently, and another 200 or so coming in every hour.
>
> > It is advertised on www.openoffice.org ...
> >
Hi,
Question - who would have the ability to generate a monthly (or so)
report on the mail list activity to the group as a whole?
That would be a nice to have report.
//drew
Re: draft - Website migration(+) announcement - draft
Posted by Rob Weir <ro...@apache.org>.
On Thu, Dec 29, 2011 at 7:37 PM, Dave Fisher <da...@comcast.net> wrote:
>
> On Dec 29, 2011, at 3:52 PM, Rob Weir wrote:
>
>> On Thu, Dec 29, 2011 at 6:19 PM, kay.schenk <ka...@gmail.com> wrote:
>>
>>
>> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>>
>> <snip>
>>
>> I wonder whether it would be worth reviving the OpenOffice Newsletter?
>> This was sent out to the old announce list. It was erratic toward
>> the end, but at one point I think it was coming out every month.
>>
>> Some examples:
>>
>> March 2011: http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>>
>> December 2010:
>> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>>
>> September 2010:
>> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>>
>> A format like that allows us to bundle a few small posts, news
>> clippings, announcements, etc., into a fuller package, maybe with
>> greater impact.
>>
>> For example, we could a series of these over the next few months:
>>
>> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
>> migration, copyleft-free build, start of test effort, links to blog,
>> mailing lists, migration status, announcement of pending retirement of
>> openoffice.org email addresses and lists, etc.
>>
>> Newsletter #2 (a month later): availability of test builds for 3.4
>> (hopefully on Windows by then), how to help with test effort, reminder
>> on mailing list migration and mail forwarding shutdown. Gathering
>> proposals for AOO 4.0.
>>
>> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>>
>> A newsletter could be put together on the wiki and then the
>> announcement can be a link to the online newsletter.
>>
>> I think this has merit. Can we find a voluneteer?
>>
>> ps. My earlier attempt at trying to directly post to announce@openoffice.org is apparently SPAM and therefor rejected. I hope Andrew had some luck. I'll track this down in a bit.
>>
>>
>> It looks like it went out earlier to the announce list. I see it in the archives:
>>
>> http://openoffice.org/projects/www/lists/announce/archive/2011-12/message/0
>>
>> I'm also seeing large numbers of users now signed up to ooo-announce.
>
> What do you mean by large?
>
1700 currently, and another 200 or so coming in every hour.
> It is advertised on www.openoffice.org ...
>
Excellent.
> Regards,
> Dave
>
>
>>
>> -Rob
>>
>>
>>
>>
>>
>> > //drew
>> >
>> >
>> >
>>
>>
>>
>> --
>> ----------------------------------------------------------------------------------------
>> MzK
>>
>> "The greatness of a nation and its moral progress can be judged
>> by the way its animals are treated."
>> -- Mohandas Gandhi
>>
>>
>>
>>
>
Re: draft - Website migration(+) announcement - draft
Posted by Dave Fisher <da...@comcast.net>.
On Dec 29, 2011, at 3:52 PM, Rob Weir wrote:
> On Thu, Dec 29, 2011 at 6:19 PM, kay.schenk <ka...@gmail.com> wrote:
>
>
> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>
> <snip>
>
> I wonder whether it would be worth reviving the OpenOffice Newsletter?
> This was sent out to the old announce list. It was erratic toward
> the end, but at one point I think it was coming out every month.
>
> Some examples:
>
> March 2011: http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>
> December 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>
> September 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>
> A format like that allows us to bundle a few small posts, news
> clippings, announcements, etc., into a fuller package, maybe with
> greater impact.
>
> For example, we could a series of these over the next few months:
>
> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
> migration, copyleft-free build, start of test effort, links to blog,
> mailing lists, migration status, announcement of pending retirement of
> openoffice.org email addresses and lists, etc.
>
> Newsletter #2 (a month later): availability of test builds for 3.4
> (hopefully on Windows by then), how to help with test effort, reminder
> on mailing list migration and mail forwarding shutdown. Gathering
> proposals for AOO 4.0.
>
> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>
> A newsletter could be put together on the wiki and then the
> announcement can be a link to the online newsletter.
>
> I think this has merit. Can we find a voluneteer?
>
> ps. My earlier attempt at trying to directly post to announce@openoffice.org is apparently SPAM and therefor rejected. I hope Andrew had some luck. I'll track this down in a bit.
>
>
> It looks like it went out earlier to the announce list. I see it in the archives:
>
> http://openoffice.org/projects/www/lists/announce/archive/2011-12/message/0
>
> I'm also seeing large numbers of users now signed up to ooo-announce.
What do you mean by large?
It is advertised on www.openoffice.org ...
Regards,
Dave
>
> -Rob
>
>
>
>
>
> > //drew
> >
> >
> >
>
>
>
> --
> ----------------------------------------------------------------------------------------
> MzK
>
> "The greatness of a nation and its moral progress can be judged
> by the way its animals are treated."
> -- Mohandas Gandhi
>
>
>
>
Re: draft - Website migration(+) announcement - draft
Posted by Rob Weir <ro...@apache.org>.
On Thu, Dec 29, 2011 at 6:19 PM, kay.schenk <ka...@gmail.com> wrote:
>
>
> On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
>
>>
<snip>
I wonder whether it would be worth reviving the OpenOffice Newsletter?
>> This was sent out to the old announce list. It was erratic toward
>> the end, but at one point I think it was coming out every month.
>>
>> Some examples:
>>
>> March 2011:
>> http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>>
>> December 2010:
>>
>> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>>
>> September 2010:
>>
>> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>>
>> A format like that allows us to bundle a few small posts, news
>> clippings, announcements, etc., into a fuller package, maybe with
>> greater impact.
>>
>> For example, we could a series of these over the next few months:
>>
>> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
>> migration, copyleft-free build, start of test effort, links to blog,
>> mailing lists, migration status, announcement of pending retirement of
>> openoffice.org email addresses and lists, etc.
>>
>> Newsletter #2 (a month later): availability of test builds for 3.4
>> (hopefully on Windows by then), how to help with test effort, reminder
>> on mailing list migration and mail forwarding shutdown. Gathering
>> proposals for AOO 4.0.
>>
>> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>>
>> A newsletter could be put together on the wiki and then the
>> announcement can be a link to the online newsletter.
>>
>
> I think this has merit. Can we find a voluneteer? [?]
>
> ps. My earlier attempt at trying to directly post to
> announce@openoffice.org is apparently SPAM and therefor rejected. I hope
> Andrew had some luck. I'll track this down in a bit.
>
It looks like it went out earlier to the announce list. I see it in the
archives:
http://openoffice.org/projects/www/lists/announce/archive/2011-12/message/0
I'm also seeing large numbers of users now signed up to ooo-announce.
-Rob
>
>>
>> > //drew
>> >
>> >
>> >
>>
>
>
>
> --
>
> ----------------------------------------------------------------------------------------
> MzK
>
> "The greatness of a nation and its moral progress can be judged
> by the way its animals are treated."
> -- Mohandas Gandhi
>
>
>
>
Re: draft - Website migration(+) announcement - draft
Posted by "kay.schenk" <ka...@gmail.com>.
On Thu, Dec 29, 2011 at 2:55 PM, Rob Weir <ro...@apache.org> wrote:
> On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com> wrote:
> > On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
> >> On 29/12/2011 drew wrote:
> >> > During this migration period community developers also made great
> >> > progress with the application code. Ariel Constenla-Haile, one of the
> >> > community developers, generated binary packages, suitable for early
> >> > testing purposes, from the current Apache OpenOffice code repository.
> >> > Available for download at http://people.apache.org/~arielch/packages
> >>
> >> I wouldn't send out public announcements about Ariel's builds. The
> >> interest is huge, and people might download them just out of curiosity
> >> and damage their existing OpenOffice.org installation and extensions.
> >
> > Well, good point. I think it is important to be clear that the code (the
> > application and therefore the 'thing' of real importance to users) is
> > moving forward also however..not sure how to do that without something
> > concrete to point to - as you say though it is something that can
> > backfire badly, if people just install those files..
> >
> >> It's probably better to announce, at due time, development builds that
> >> won't interfere with the installed version (and ideally, not even with
> >> the user profile if the BerkeleyDB removal has implications on that).
> >
> > Then maybe the announcement should just chronicle the items of interest:
> >
> > - Developer snapshot's are becoming available - that's Ariel's page as
> > one
> > - Daily builds are happening and there is a real location for those
> > - others?
> >
> > and then point them to a page (website or wiki?) for those interested in
> > getting in on the bleeding edge of testing, maybe?
> >
>
> it is a good little snippet of info. But there is so much more to
> say, especially for an audience that we've haven't been
> (re-)introduced to yet. Where to start?
>
> I wonder whether it would be worth reviving the OpenOffice Newsletter?
> This was sent out to the old announce list. It was erratic toward
> the end, but at one point I think it was coming out every month.
>
> Some examples:
>
> March 2011:
> http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
>
> December 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
>
> September 2010:
> http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
>
> A format like that allows us to bundle a few small posts, news
> clippings, announcements, etc., into a fuller package, maybe with
> greater impact.
>
> For example, we could a series of these over the next few months:
>
> Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
> migration, copyleft-free build, start of test effort, links to blog,
> mailing lists, migration status, announcement of pending retirement of
> openoffice.org email addresses and lists, etc.
>
> Newsletter #2 (a month later): availability of test builds for 3.4
> (hopefully on Windows by then), how to help with test effort, reminder
> on mailing list migration and mail forwarding shutdown. Gathering
> proposals for AOO 4.0.
>
> Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
>
> A newsletter could be put together on the wiki and then the
> announcement can be a link to the online newsletter.
>
I think this has merit. Can we find a voluneteer? [?]
ps. My earlier attempt at trying to directly post to
announce@openoffice.orgis apparently SPAM and therefor rejected. I
hope Andrew had some luck. I'll
track this down in a bit.
>
>
> > //drew
> >
> >
> >
>
--
----------------------------------------------------------------------------------------
MzK
"The greatness of a nation and its moral progress can be judged
by the way its animals are treated."
-- Mohandas Gandhi
Re: draft - Website migration(+) announcement - draft
Posted by Rob Weir <ro...@apache.org>.
On Thu, Dec 29, 2011 at 3:49 PM, drew <dr...@baseanswers.com> wrote:
> On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
>> On 29/12/2011 drew wrote:
>> > During this migration period community developers also made great
>> > progress with the application code. Ariel Constenla-Haile, one of the
>> > community developers, generated binary packages, suitable for early
>> > testing purposes, from the current Apache OpenOffice code repository.
>> > Available for download at http://people.apache.org/~arielch/packages
>>
>> I wouldn't send out public announcements about Ariel's builds. The
>> interest is huge, and people might download them just out of curiosity
>> and damage their existing OpenOffice.org installation and extensions.
>
> Well, good point. I think it is important to be clear that the code (the
> application and therefore the 'thing' of real importance to users) is
> moving forward also however..not sure how to do that without something
> concrete to point to - as you say though it is something that can
> backfire badly, if people just install those files..
>
>> It's probably better to announce, at due time, development builds that
>> won't interfere with the installed version (and ideally, not even with
>> the user profile if the BerkeleyDB removal has implications on that).
>
> Then maybe the announcement should just chronicle the items of interest:
>
> - Developer snapshot's are becoming available - that's Ariel's page as
> one
> - Daily builds are happening and there is a real location for those
> - others?
>
> and then point them to a page (website or wiki?) for those interested in
> getting in on the bleeding edge of testing, maybe?
>
it is a good little snippet of info. But there is so much more to
say, especially for an audience that we've haven't been
(re-)introduced to yet. Where to start?
I wonder whether it would be worth reviving the OpenOffice Newsletter?
This was sent out to the old announce list. It was erratic toward
the end, but at one point I think it was coming out every month.
Some examples:
March 2011: http://openoffice.org/projects/www/lists/announce/archive/2011-03/message/0
December 2010:
http://openoffice.org/projects/www/lists/announce/archive/2010-12/message/0
September 2010:
http://openoffice.org/projects/www/lists/announce/archive/2010-09/message/0
A format like that allows us to bundle a few small posts, news
clippings, announcements, etc., into a fuller package, maybe with
greater impact.
For example, we could a series of these over the next few months:
Newsletter #1: Intro to OpenOffice @ Apache. Announcements on
migration, copyleft-free build, start of test effort, links to blog,
mailing lists, migration status, announcement of pending retirement of
openoffice.org email addresses and lists, etc.
Newsletter #2 (a month later): availability of test builds for 3.4
(hopefully on Windows by then), how to help with test effort, reminder
on mailing list migration and mail forwarding shutdown. Gathering
proposals for AOO 4.0.
Newsletter #3 -- coverage of 3.4 release, press clippings, etc.
A newsletter could be put together on the wiki and then the
announcement can be a link to the online newsletter.
> //drew
>
>
>
Re: draft - Website migration(+) announcement - draft
Posted by drew <dr...@baseanswers.com>.
On Thu, 2011-12-29 at 21:21 +0100, Andrea Pescetti wrote:
> On 29/12/2011 drew wrote:
> > During this migration period community developers also made great
> > progress with the application code. Ariel Constenla-Haile, one of the
> > community developers, generated binary packages, suitable for early
> > testing purposes, from the current Apache OpenOffice code repository.
> > Available for download at http://people.apache.org/~arielch/packages
>
> I wouldn't send out public announcements about Ariel's builds. The
> interest is huge, and people might download them just out of curiosity
> and damage their existing OpenOffice.org installation and extensions.
Well, good point. I think it is important to be clear that the code (the
application and therefore the 'thing' of real importance to users) is
moving forward also however..not sure how to do that without something
concrete to point to - as you say though it is something that can
backfire badly, if people just install those files..
> It's probably better to announce, at due time, development builds that
> won't interfere with the installed version (and ideally, not even with
> the user profile if the BerkeleyDB removal has implications on that).
Then maybe the announcement should just chronicle the items of interest:
- Developer snapshot's are becoming available - that's Ariel's page as
one
- Daily builds are happening and there is a real location for those
- others?
and then point them to a page (website or wiki?) for those interested in
getting in on the bleeding edge of testing, maybe?
//drew