Skip to content
Snippets Groups Projects
New look: Off

Add new Trac component for fog

    • Closed (moved) Issue created by Ximin Luo @infinity0

    Hi, please create a new component for "fog", the PT combiner.

    If there is a tree structure (not sure if there is), this can go under "pluggable transports".

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Ximin Luo added component::internal services/service - trac fog owner::erinn priority::medium resolution::wontfix severity::normal status::closed type::task labels

      added component::internal services/service - trac fog owner::erinn priority::medium resolution::wontfix severity::normal status::closed type::task labels

    • I
      Ximin Luo @infinity0 ·
      Author

      Trac:
      Component: Service - trac to Trac
      Owner: N/A to erinn

    • E
      Erinn Clark @erinn ·

      Hmm, I think we need to find a smarter way to this. As it currently stands, there are the following PT-related components: Pluggable transport, FTE, Flashproxy, Obfsproxy, meek, and obfsclient. The TBB team is moving towards collapsing TBB-related components into one ubercomponent and using tags, while having the bug reports go to a mailing list that people on the team are subscribed to. I don't know if that is a good solution in general, nor for the PT team specifically, but I think that we should consider whether there is a solution that does not create a longer list of components in trac.

      I suppose looking into whether a tree structure could be implemented (or mimicked) would be one way, but that is not the current situation. I'll look into that more, but if you have some other ideas about better organization please let me know. For now I'm going to hold off on creating this component.

    • A
      Damian Johnson @atagar ·

      I suppose looking into whether a tree structure could be implemented (or mimicked) would be one way

      A tree hierarchy is something I'd be curious to see as well (the flat structure we presently have only scales to a dozen or so components before making it a pita to find stuff). Components is one thing that could certainly due with being improved. :)

    • Q
      Jens Kubieziel @qbi ·

      Move all tickets from trac to "Service - trac" component.

      Trac:
      Component: Trac to Service - trac

    • Q
      Jens Kubieziel @qbi ·

      Do we still need that component? The last commit in the repository is over two years ago. Also there was no activity on this ticket. Thatswhy I close it for now. However if you think you need it, please reopen. Our trac now has some kind of tree structure.

      Trac:
      Reviewer: N/A to N/A
      Status: new to closed
      Sponsor: N/A to N/A
      Resolution: N/A to wontfix
      Severity: N/A to Normal

    • Trac closed

      closed

    Please register or sign in to reply