Fix missing mailto schema that causes vite to barf.

static/issues.json

@@ -634,7 +634,7 @@
     "closed_at": null,
     "author_association": "CONTRIBUTOR",
     "active_lock_reason": null,
-    "body": "## Outline\r\n\r\nMake CSG Boolean evaluation work 100% of the time!\r\n\r\n## Details\r\n\r\nCentral to BRL-CAD's geometric representation is the ability to evaluate Constructive Solid Geometry (CSG) Boolean expressions on geometry (i.e., \"UNION\", \"INTERSECTION\", and \"SUBTRACTION\").  There are many possible techniques but BRL-CAD does not yet have an implementation that reliably works all the time except for ray tracing which is robust and numerically deterministic.\r\n\r\nYour goal will be to implement a new/unexplored method that will always work for evaluation to an explicit surface geometry representation (e.g., NURBS or polygonal mesh).  This can be something based on any existing method including BSP-based methods in polygonal space, intermediate evaluation in voxel space, interval arithmetic, NURBS evaluation, error tracking methods, or simply re-implementation an existing method (e.g., Weiler’s n-manifold method) with exhaustive unit testing.\r\n\r\nFor example, OpenVDB has a boolean evaluation method implementation that works in voxel space.  One could create an evaluator that voxelizes BRL-CAD geometry using ray tracing (which is 100% reliable), evaluates in OpenVDB, and then converts to polygons.\r\n\r\nAlternative example, BRL-CAD has NURBS boolean evaluation logic that works some of the time, but hasn't been extended to cover all cases of surface-surface intersection.  One could create a test suite that identifies all configurations and their current status, and work towards resolving failures one by one.\r\n\r\nYet another example, BRL-CAD has an implementation of n-manifold geometry boolean evaluation.  You could work on re-implementing the boolean evaluation from scratch with an eye towards unit testing and performance.\r\n\r\n## Expected Outcome\r\n\r\nRobust export of geometry to triangle mesh format using some method that reliably works every time.\r\n\r\n## Future Possibilities <!-- optional -->\r\n\r\n- Expanded unit testing, coverage testing.\r\n- Accelerate boolean evaluation on the GPU.\r\n- Create an online conversion service.\r\n\r\n## Project Properties\r\n\r\n### Skills\r\n\r\nC/C++\r\n\r\n### Difficulty <!-- easy, medium, hard -->\r\n\r\nhard\r\n\r\n### Size <!-- medium (175h), long (350h) -->\r\n\r\nlong (350h)\r\n\r\n### Additional Information\r\n\r\n* Potential mentor(s): [Sean Morrison]([email protected])\r\n* Organization website: https://brlcad.org\r\n* Communication channels: https://brlcad.zulipchat.com\r\n",
+    "body": "## Outline\r\n\r\nMake CSG Boolean evaluation work 100% of the time!\r\n\r\n## Details\r\n\r\nCentral to BRL-CAD's geometric representation is the ability to evaluate Constructive Solid Geometry (CSG) Boolean expressions on geometry (i.e., \"UNION\", \"INTERSECTION\", and \"SUBTRACTION\").  There are many possible techniques but BRL-CAD does not yet have an implementation that reliably works all the time except for ray tracing which is robust and numerically deterministic.\r\n\r\nYour goal will be to implement a new/unexplored method that will always work for evaluation to an explicit surface geometry representation (e.g., NURBS or polygonal mesh).  This can be something based on any existing method including BSP-based methods in polygonal space, intermediate evaluation in voxel space, interval arithmetic, NURBS evaluation, error tracking methods, or simply re-implementation an existing method (e.g., Weiler’s n-manifold method) with exhaustive unit testing.\r\n\r\nFor example, OpenVDB has a boolean evaluation method implementation that works in voxel space.  One could create an evaluator that voxelizes BRL-CAD geometry using ray tracing (which is 100% reliable), evaluates in OpenVDB, and then converts to polygons.\r\n\r\nAlternative example, BRL-CAD has NURBS boolean evaluation logic that works some of the time, but hasn't been extended to cover all cases of surface-surface intersection.  One could create a test suite that identifies all configurations and their current status, and work towards resolving failures one by one.\r\n\r\nYet another example, BRL-CAD has an implementation of n-manifold geometry boolean evaluation.  You could work on re-implementing the boolean evaluation from scratch with an eye towards unit testing and performance.\r\n\r\n## Expected Outcome\r\n\r\nRobust export of geometry to triangle mesh format using some method that reliably works every time.\r\n\r\n## Future Possibilities <!-- optional -->\r\n\r\n- Expanded unit testing, coverage testing.\r\n- Accelerate boolean evaluation on the GPU.\r\n- Create an online conversion service.\r\n\r\n## Project Properties\r\n\r\n### Skills\r\n\r\nC/C++\r\n\r\n### Difficulty <!-- easy, medium, hard -->\r\n\r\nhard\r\n\r\n### Size <!-- medium (175h), long (350h) -->\r\n\r\nlong (350h)\r\n\r\n### Additional Information\r\n\r\n* Potential mentor(s): [Sean Morrison](mailto:[email protected])\r\n* Organization website: https://brlcad.org\r\n* Communication channels: https://brlcad.zulipchat.com\r\n",
     "reactions": {
       "url": "https://api.github.com/repos/opencax/GSoC/issues/70/reactions",
       "total_count": 0,