Ticket #2069 (assigned enhancement)

Opened 6 months ago

Last modified 4 months ago

Add Trac categories for the Bluetooth stack

Reported by: andreasf Owned by: nielx
Priority: normal Milestone: R1
Component: Website/Trac Version: R1 development
Cc: oruizdorantes Blocked By:
Platform: All Blocking:

Description

There is no Trac category for the Bluetooth Kit yet. There's also a bluetooth server without matching category.

The owner should probably be set to oruizdorantes?

Change History

  Changed 6 months ago by nielx

  • cc oruizdorantes added
  • owner changed from haiku-web to nielx
  • status changed from new to assigned

I suggest waiting for the components to mature a bit more, as soon as they are testable, I guess it's an idea to accept bug reports.

Anyway, CC'ing oruizdurantes. He can decide.

  Changed 6 months ago by oruizdorantes

I am not sure if I should note this from here.

But I prefer starting getting all possible feedback right now, tickets, bugs, enhancement requests. They will be useful during design.

As Last Ticket from Andreas about RSSI.

follow-up: ↓ 5   Changed 6 months ago by korli

the component : "Drivers/Bluetooth" has been added. Is it OK ?

  Changed 6 months ago by oruizdorantes

Yes, I think so.

in reply to: ↑ 3 ; follow-up: ↓ 7   Changed 6 months ago by nielx

Replying to korli:

the component : "Drivers/Bluetooth" has been added. Is it OK ?

Yes, about the Bluetooth kit: I think this one should be integrated with the device kit, as was done with the usb kit, So I think there should not be an extra category.

Also, I need to know the exact name of the bluetooth server so that it can be added.

P.S. Korli: I actually was looking into this ticket (I accepted it), so let's avoid double work.

  Changed 6 months ago by oruizdorantes

The libbluetooth.so where currently is held the bluetooth kit is gonna grow a lot for sure while reaching a basic stack with usual profiles, containing maybe even 3rd party libs.

So Merging the the Device kit would not be a good idea.

Regarding all BT there will be at least:

- Drivers, - Some kernel modules (BT and network) - Kit/lib - Server - Prefrences - Apps

and most likelye even media nodes...

So in order to clasify this, you should maybe get a more vertical point of view.

in reply to: ↑ 5   Changed 6 months ago by andreasf

Replying to nielx:

about the Bluetooth kit: I think this one should be integrated with the device kit, as was done with the usb kit, So I think there should not be an extra category.

The reason I filed this ticket was that with axeld as the default Kits owner, Oliver wasn't notified of my Bluetooth ticket. Adding new Bluetooth categories with oruizdorantes as owner would make him aware of anything filed against his code.

An alternative, to avoid tons of new categories, might be to create a single Bluetooth category under Network & Internet.

  Changed 4 months ago by nielx

I think I'll make a top-level Bluetooth category. Since Bluetooth is such a comprehensive set of modules it might be better just to group them under one heading.

Note: See TracTickets for help on using tickets.