You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2011/11/30 22:12:05 UTC

(Draft) Email forwarding public announcement

Note this is draft. But I'd like to see if I'm heading in the right direction.

https://cwiki.apache.org/confluence/display/OOOUSERS/%28Draft%29+Public+Statement+on+Email+Forwarding

The idea would be to put this up on the blog, out to the mailing
lists, prominently linked from home page of podling and OOo websites,
and spread the word through social networks.

But not yet.  This is still draft.

I've thrown in the shut off date as January 31st, 2012.  This has not
been discussed, so consider that to be just a placeholder for now.
(Again, this is just draft).

Some specific points that could use more detail include project
services (lists, wikis, Bugzilla, etc.) that would be very commonly
used with openoffice.org email addresses.  I think I listed them all.

But can you think of others?

Also, if anyone knows what we should recommend for BZ and Wiki
accounts, feel free to fill in those details, either on the list or
directly on the wiki.

The other parts to this, if you recall, are:

1) Working with Infra@ on a bounce notification.  I have not started
this beyond some vigorous arm waving.

2) A wiki page that the bounce notification would point to, showing
the mapping of the various utility and mailing list addresses.  I
think we can recycle information already on the wiki page dealing with
the list migration.

3) Ideally, translation of the above, once finalized, into major user languages.

And obviously it will be easier to coordinate this if we can agree on
a date for retiring the forwarding service.  We're currently
out-of-policy with this, though I think no one wants to just pull the
plug without fair notice to users.

-Rob

Re: (Draft) Email forwarding public announcement

Posted by Dave Fisher <da...@comcast.net>.
There is a thread "Extensions and Templates" shouldn't this information be there?

After all Gavin is working on the issue, he might not notice this information.

Regards,
Dave

On Dec 8, 2011, at 8:31 PM, Raphael Bircher wrote:

> Am 09.12.11 05:25, schrieb Rob Weir:
>> On Thu, Dec 8, 2011 at 5:02 PM, Andrea Pescetti<pe...@openoffice.org>  wrote:
>>> On 30/11/2011 Rob Weir wrote:
>>>> Some specific points that could use more detail include project
>>>> services (lists, wikis, Bugzilla, etc.) that would be very commonly
>>>> used with openoffice.org email addresses.  I think I listed them all.
>>>> But can you think of others?
>>> 
>>> I just checked and I confirm what I wrote some days ago: the Extensions and
>>> Templates sites use single-sign-on with the @openoffice.org addresses, so
>>> only their @openoffice.org e-mail address is available in the system.
>>> 
>>> This means that extension publishers can be contacted only through their
>>> @openoffice.org address; the first thing to do in the possible future clones
>>> of the Extensions and Templates site would thus be to disable the
>>> single-sign-on (unfortunately) and send out password reset links before the
>>> @openoffice.org addresses and the single-sign-on expire, otherwise extension
>>> publishers will lose access to the website.
>>> 
>> A password reset doesn't fix it.    We need users to specify a
>> different email address, right?  Is that even possible?  Does the app
>> have a separate user-id and email address field?  Or does it assume
>> they are always the same?
> Realy good point. As I know the extension site use the Kenai Login. This is possible over LADP (If I'm not wrong) This would be a big issue.
>> 
>> Or is the idea that the password reset notification is the easiest way
>> to contact all of the users?
>> 
>> -Rob
>> 
>>> Regards,
>>>  Andrea.
> 
> 
> -- 
> My private Homepage: http://www.raphaelbircher.ch/


Re: (Draft) Email forwarding public announcement

Posted by Raphael Bircher <r....@gmx.ch>.
Am 09.12.11 05:25, schrieb Rob Weir:
> On Thu, Dec 8, 2011 at 5:02 PM, Andrea Pescetti<pe...@openoffice.org>  wrote:
>> On 30/11/2011 Rob Weir wrote:
>>> Some specific points that could use more detail include project
>>> services (lists, wikis, Bugzilla, etc.) that would be very commonly
>>> used with openoffice.org email addresses.  I think I listed them all.
>>> But can you think of others?
>>
>> I just checked and I confirm what I wrote some days ago: the Extensions and
>> Templates sites use single-sign-on with the @openoffice.org addresses, so
>> only their @openoffice.org e-mail address is available in the system.
>>
>> This means that extension publishers can be contacted only through their
>> @openoffice.org address; the first thing to do in the possible future clones
>> of the Extensions and Templates site would thus be to disable the
>> single-sign-on (unfortunately) and send out password reset links before the
>> @openoffice.org addresses and the single-sign-on expire, otherwise extension
>> publishers will lose access to the website.
>>
> A password reset doesn't fix it.    We need users to specify a
> different email address, right?  Is that even possible?  Does the app
> have a separate user-id and email address field?  Or does it assume
> they are always the same?
Realy good point. As I know the extension site use the Kenai Login. This 
is possible over LADP (If I'm not wrong) This would be a big issue.
>
> Or is the idea that the password reset notification is the easiest way
> to contact all of the users?
>
> -Rob
>
>> Regards,
>>   Andrea.


-- 
My private Homepage: http://www.raphaelbircher.ch/

Re: (Draft) Email forwarding public announcement

Posted by Andrea Pescetti <pe...@openoffice.org>.
Rob Weir wrote:
> On Thu, Dec 8, 2011 at 5:02 PM, Andrea Pescetti<pe...@...>  wrote:
>> This means that extension publishers can be contacted only through their
>> @openoffice.org address; the first thing to do in the possible future clones
>> of the Extensions and Templates site would thus be to disable the
>> single-sign-on (unfortunately) and send out password reset links before the
>> @openoffice.org addresses and the single-sign-on expire, otherwise extension
>> publishers will lose access to the website.
>>
> A password reset doesn't fix it.    We need users to specify a
> different email address, right?  Is that even possible?  Does the app
> have a separate user-id and email address field?  Or does it assume
> they are always the same?

I was skipping some steps. Again, I don't have access to the code, but 
the standard way of implementing in Drupal what the Extensions site does 
would be:
- All passwords are validated on the OOo single-sign-on in Kenai
- Upon successful validation, a local user is created on the Extensions 
site (i.e., after I login correctly as pescetti@ooo the user "pescetti" 
is created on the Extensions site, with e-mail set to pescetti@ooo; of 
course this is only done at the first login).
- I assume that passwords are not stored in the local database, since 
anyway they are always validated on the single-sign-on. But other user 
data are persistent.

Steps to do would thus be:

1) Disconnect Extensions from single-sign-on ; all users will still be 
there, but we only have their @openoffice.org e-mail address; so user 
"pescetti" will still exist, with the e-mail field set to pescetti@ooo 
and the password set to something meaningless.

2) Send a password reset link to all users; this will be notified to 
them through their @openoffice.org address and would include information 
on how to reset both the password and the e-mail address; possibly, the 
form validation would forbid to leave the e-mail address set to 
something@openoffice.org

3) People will then be able to login with the username they are using 
now (like "pescetti") and the new password.

This can only be done until OpenOffice.org addresses are in place.

As asked by Dave, I'll send a link to this thread in the one where Gavin 
is discussing migration, so it doesn't get lost.

Regards,
   Andrea.

Re: (Draft) Email forwarding public announcement

Posted by Rob Weir <ro...@apache.org>.
On Thu, Dec 8, 2011 at 5:02 PM, Andrea Pescetti <pe...@openoffice.org> wrote:
> On 30/11/2011 Rob Weir wrote:
>>
>> Some specific points that could use more detail include project
>> services (lists, wikis, Bugzilla, etc.) that would be very commonly
>> used with openoffice.org email addresses.  I think I listed them all.
>> But can you think of others?
>
>
> I just checked and I confirm what I wrote some days ago: the Extensions and
> Templates sites use single-sign-on with the @openoffice.org addresses, so
> only their @openoffice.org e-mail address is available in the system.
>
> This means that extension publishers can be contacted only through their
> @openoffice.org address; the first thing to do in the possible future clones
> of the Extensions and Templates site would thus be to disable the
> single-sign-on (unfortunately) and send out password reset links before the
> @openoffice.org addresses and the single-sign-on expire, otherwise extension
> publishers will lose access to the website.
>

A password reset doesn't fix it.    We need users to specify a
different email address, right?  Is that even possible?  Does the app
have a separate user-id and email address field?  Or does it assume
they are always the same?

Or is the idea that the password reset notification is the easiest way
to contact all of the users?

-Rob

> Regards,
>  Andrea.

Re: (Draft) Email forwarding public announcement

Posted by Andrea Pescetti <pe...@openoffice.org>.
On 30/11/2011 Rob Weir wrote:
> Some specific points that could use more detail include project
> services (lists, wikis, Bugzilla, etc.) that would be very commonly
> used with openoffice.org email addresses.  I think I listed them all.
> But can you think of others?

I just checked and I confirm what I wrote some days ago: the Extensions 
and Templates sites use single-sign-on with the @openoffice.org 
addresses, so only their @openoffice.org e-mail address is available in 
the system.

This means that extension publishers can be contacted only through their 
@openoffice.org address; the first thing to do in the possible future 
clones of the Extensions and Templates site would thus be to disable the 
single-sign-on (unfortunately) and send out password reset links before 
the @openoffice.org addresses and the single-sign-on expire, otherwise 
extension publishers will lose access to the website.

Regards,
   Andrea.

Re: (Draft) Email forwarding public announcement

Posted by Louis Suárez-Potts <ls...@gmail.com>.
… back….
Thanks, Rob; will cast eye over this shortly.
Cheers,
Louis
PS then I'll bottom post ...

On 30 November 2011 16:12, Rob Weir <ro...@apache.org> wrote:
> Note this is draft. But I'd like to see if I'm heading in the right direction.
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/%28Draft%29+Public+Statement+on+Email+Forwarding
>
> The idea would be to put this up on the blog, out to the mailing
> lists, prominently linked from home page of podling and OOo websites,
> and spread the word through social networks.
>
> But not yet.  This is still draft.
>
> I've thrown in the shut off date as January 31st, 2012.  This has not
> been discussed, so consider that to be just a placeholder for now.
> (Again, this is just draft).
>
> Some specific points that could use more detail include project
> services (lists, wikis, Bugzilla, etc.) that would be very commonly
> used with openoffice.org email addresses.  I think I listed them all.
>
> But can you think of others?
>
> Also, if anyone knows what we should recommend for BZ and Wiki
> accounts, feel free to fill in those details, either on the list or
> directly on the wiki.
>
> The other parts to this, if you recall, are:
>
> 1) Working with Infra@ on a bounce notification.  I have not started
> this beyond some vigorous arm waving.
>
> 2) A wiki page that the bounce notification would point to, showing
> the mapping of the various utility and mailing list addresses.  I
> think we can recycle information already on the wiki page dealing with
> the list migration.
>
> 3) Ideally, translation of the above, once finalized, into major user languages.
>
> And obviously it will be easier to coordinate this if we can agree on
> a date for retiring the forwarding service.  We're currently
> out-of-policy with this, though I think no one wants to just pull the
> plug without fair notice to users.
>
> -Rob

Re: (Draft) Email forwarding public announcement

Posted by Donald Whytock <dw...@gmail.com>.
On Wed, Nov 30, 2011 at 4:12 PM, Rob Weir <ro...@apache.org> wrote:
> Note this is draft. But I'd like to see if I'm heading in the right direction.

Looks good.  Very clear; pretty much handles "...But nobody TOLD me!"

Grammarweenie:

- "have been able to migrate" -> "has been able to migrate"

Reminder:

- "[Specific instructions for ezmlm lists]" not yet linked.

Suggestion:

- Include a link to the current homepage.

Don

Re: (Draft) Email forwarding public announcement

Posted by Rob Weir <ro...@apache.org>.
On Wed, Nov 30, 2011 at 5:46 PM, TJ Frazier <tj...@cfl.rr.com> wrote:
> Nice work. Wiki details added. /tj/
>

Great, thanks much.

If anyone is interested, I'm going to start a thread on
infrastructure@ on the mail bounce side of this, to scope out that
effort.  If anyone has thoughts on the technical details feel free to
follow the conversation there.

-Rob

>
> On 11/30/2011 16:12, Rob Weir wrote:
>>
>> Note this is draft. But I'd like to see if I'm heading in the right
>> direction.
>>
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/%28Draft%29+Public+Statement+on+Email+Forwarding
>>
>> The idea would be to put this up on the blog, out to the mailing
>> lists, prominently linked from home page of podling and OOo websites,
>> and spread the word through social networks.
>>
>> But not yet.  This is still draft.
>>
>> I've thrown in the shut off date as January 31st, 2012.  This has not
>> been discussed, so consider that to be just a placeholder for now.
>> (Again, this is just draft).
>>
>> Some specific points that could use more detail include project
>> services (lists, wikis, Bugzilla, etc.) that would be very commonly
>> used with openoffice.org email addresses.  I think I listed them all.
>>
>> But can you think of others?
>>
>> Also, if anyone knows what we should recommend for BZ and Wiki
>> accounts, feel free to fill in those details, either on the list or
>> directly on the wiki.
>>
>> The other parts to this, if you recall, are:
>>
>> 1) Working with Infra@ on a bounce notification.  I have not started
>> this beyond some vigorous arm waving.
>>
>> 2) A wiki page that the bounce notification would point to, showing
>> the mapping of the various utility and mailing list addresses.  I
>> think we can recycle information already on the wiki page dealing with
>> the list migration.
>>
>> 3) Ideally, translation of the above, once finalized, into major user
>> languages.
>>
>> And obviously it will be easier to coordinate this if we can agree on
>> a date for retiring the forwarding service.  We're currently
>> out-of-policy with this, though I think no one wants to just pull the
>> plug without fair notice to users.
>>
>> -Rob
>>
>>
>
>

Re: (Draft) Email forwarding public announcement

Posted by TJ Frazier <tj...@cfl.rr.com>.
Nice work. Wiki details added. /tj/

On 11/30/2011 16:12, Rob Weir wrote:
> Note this is draft. But I'd like to see if I'm heading in the right direction.
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/%28Draft%29+Public+Statement+on+Email+Forwarding
>
> The idea would be to put this up on the blog, out to the mailing
> lists, prominently linked from home page of podling and OOo websites,
> and spread the word through social networks.
>
> But not yet.  This is still draft.
>
> I've thrown in the shut off date as January 31st, 2012.  This has not
> been discussed, so consider that to be just a placeholder for now.
> (Again, this is just draft).
>
> Some specific points that could use more detail include project
> services (lists, wikis, Bugzilla, etc.) that would be very commonly
> used with openoffice.org email addresses.  I think I listed them all.
>
> But can you think of others?
>
> Also, if anyone knows what we should recommend for BZ and Wiki
> accounts, feel free to fill in those details, either on the list or
> directly on the wiki.
>
> The other parts to this, if you recall, are:
>
> 1) Working with Infra@ on a bounce notification.  I have not started
> this beyond some vigorous arm waving.
>
> 2) A wiki page that the bounce notification would point to, showing
> the mapping of the various utility and mailing list addresses.  I
> think we can recycle information already on the wiki page dealing with
> the list migration.
>
> 3) Ideally, translation of the above, once finalized, into major user languages.
>
> And obviously it will be easier to coordinate this if we can agree on
> a date for retiring the forwarding service.  We're currently
> out-of-policy with this, though I think no one wants to just pull the
> plug without fair notice to users.
>
> -Rob
>
>