[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28684 [Core Tor/sbws]: Make sbws easy to understand and maintain
#28684: Make sbws easy to understand and maintain
---------------------------+-----------------------------------
Reporter: juga | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: sbws: unspecified
Component: Core Tor/sbws | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+-----------------------------------
Comment (by juga):
Replying to [comment:5 teor]:
> Replying to [comment:4 juga]:
> > Replying to [comment:3 teor]:
> > > But no-one is parsing the bandwidth file yet, so if we want to make
major changes, now would be a good time.
> >
> > We can create a child ticket for changing the keys in the bandwidth
file, do it after 1.0 and upgrade the other milestones to 2.X.
>
> We could change the keys in the bandwidth file, or we could leave them
as they are, and document the abbreviations.
> I am not sure if changing the keys is worth it. We would also have to
change the spec.
> Edit: and fix any bugs that we create in the change
>
> juga, do you think that changing the keys will make sbws a lot easier to
maintain?
> If it won't, or if it will take a lot of time, we should just focus on
fixing bugs and deploying sbws.
I agree that just changing the name of the keys doesn't affect much on the
maintainability of sbws and i agree will take some time, however as you
said, if we don't do it now we'll have those keys for longer time. I don't
know...
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28684#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs