Closed
Bug 1058074
Opened 10 years ago
Closed 10 years ago
Tracking bug for pkewisch@mozilla.com
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Fallen, Unassigned)
Details
jlin asked me to file a bug for tracking my moco account. I have both a community and a moco ldap account and am using both accounts for different activities. Aside from occasional email I still received on that account, I use the calendar for testing purposes. I manage the Mozilla Calendar Project and use the Zimbra Calendar for debugging issues when employees file bugs. As far as I remember, Thunderbird+Lightning is one of the suggested clients for employees. Especially with the upcoming Email changes, it is helpful to have my account enabled to assist with and reproduce issues employees may be having. I have been asked my expert opinion on the migration and was included in conference calls on that matter. If you are concerned about privacy, Mozilla has at least one signed NDA on file with me, one recently signed this year. This bug is just for tracking, there is nothing to be done in this bug other than to serve as a record in case someone would like to know what the status of my account is.
Comment 1•10 years ago
|
||
The 2 LDAP accounts for Phillip below. Both ldap accounts updated to reference this bug number. Dn: mail=mozilla@kewis.ch,o=net,dc=mozilla Dn: mail=pkewisch@mozilla.com,o=com,dc=mozilla
Comment 2•10 years ago
|
||
(In reply to Rick Bryce [:rbryce] from comment #1) > The 2 LDAP accounts for Phillip below. Both ldap accounts updated to > reference this bug number. > > Dn: mail=mozilla@kewis.ch,o=net,dc=mozilla > Dn: mail=pkewisch@mozilla.com,o=com,dc=mozilla AFter thinking about this more. No need to keep this open. If any question arises, your ldap account will point us here.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•