- Case Number: a20120113.1
- Status: withdrawn
- Claimant: CAcert (Support - originally filed by Werner D)
- Respondent: Martin S
Initial Case Manager: UlrichSchroeter
Case Manager: PietStarreveld
- Date of arbitration start:
- Date of ruling:
- Case closed: 2016-10-22
- Complaint: CCA violation, Close Account
- Relief: account shall be closed and his certificates revoked.
Before: Arbitrator name arbitor (A), Respondent: Martin S (R), Claimant: CAcert (C1), Case: a20120113.1
Former parties: Werner D. for Support (C2).
2012-01-13 (issue.c.o) ticket s20120113.7
- 2012-01-19 (iCM): added to wiki, request for CM / A
- 2016-08-20 (CM): FrOSCon 2016 session:
- case selected for review as it fits the review criteria
- CAcert Support becomes new claimant (C1), original claimant dismissed (C2)
- CAcert Support withdraws case as claimant
- 2016-09-25 (CM): board confirms the executive decisions taken during FrOSCon 2016 session by board motion m20160921.2
- 2016-10-15 (CM): implement executive decisions taken during FrOSCon 2016 and send case withdrawal notification
- 2016-10-22 (CM): case closed as withdrawn
Link to Arbitration case a20120113.1 (Private Part), Access for (CM) + (A) only
EOT Private Part
- Original dispute (privacy sensitive data anonymized as [...]):
Hello arbitrators, I hereby file a dispute against [...], since he seemingly uses an account with fake data. His account shall be closed and his certificates revoked. -------- Original Message From: [...] -------- I've signed up certificates with the email [...]. I've only issued one certificate for the domain [...]. A few days ago I received an email from you warning us that the certificate is close to expire, so I decided to make a new one, but can remember my password nor which birth day I used to make the account. Can you help me?
FrOSCon 2016 session - future of 25 arbitration cases from leaving team members
At FrOSCon 2016 members of Arbitration, Board and Support took part in a session on possible withdrawal of cases by CAcert(Support)/CAcert and prior clarification about claimants. On 2016-08-23 the initial report of that FrOSCon 2016 session, Protocol - FrOSCon session - future of 25 arbitration cases from leaving team members, was posted on the board and arbitration mailing lists for review and discussion.
The executive "decisions" taken during the FrOSCon 2016 Session (and also regarding additional cases) were confirmed by board motion m20160921.2 on 2016-09-25:
Resolved, that board withdraws the cases as mentioned in the emails https://lists.cacert.org/wws/arc/cacert-board/2016-08/msg00009.html and https://lists.cacert.org/wws/arc/cacert-board/2016-08/msg00017.html acting for CAcert as claimant of that cases.
The detailed background, proceedings and the initial report of the FrOSCon 2016 session are publicly available as FrOSCon 2016 Session Report.
FrOSCon 2016 session - review of case a20120113.1 - "CCA violation, Close Account"
At the FrOSCon 2016 Session case a20120113.1 - "CCA violation, Close Account" was put up for review as all who were present at the session agreed that it fitted the criteria for review:
- dispute is filed by formerly active member
- dispute is filed as a role based dispute
For this case this meant that Support would now assume the role of claimant and that the original claimant should be considered as former claimant, having been dismissed from the dispute.
The subsequent review of this case at FrOSCon 2016 made Support decide to withdraw the case as claimant as shown by the relevant section of the FrOSCon 2016 report posted on the board and arbitration mailinglists on 2016-08-23:
3. https://wiki.cacert.org/Arbitrations/a20120113.1 ------------------------------------------------------------------- "CCA violation, Close Account" * summary of dispute: "Dispute against [a member] since he seemingly uses an account with fake data. His account shall be closed and his certificates revoked." - This was the reaction to a mail send by that member with the request to help to reset the password where the user had issues to enter the correct birth date in the automated process. * support: please hand back case to support, as there is another "policy" within Support that names a lot of other options in such situations to handle such situations (for example to propose request to close account so that another can be created, but maybe there were only some issues with entering the birth date). -> withdraw * board: ok
FrOSCon 2016 session - review of case a20120113.1 - "CCA violation, Close Account" - comments received
The review of this case as reported on the board and arbitration mailinglists didn't lead to comments.
None - claimant C1 withdrew case on 2016-08-20.