Katie Capps Parlante wrote:
> We'd like to go ahead and make these changes in bugzilla, so please
> respond before Wednesday if you want to alter the proposal:
> http://wiki.osafoundation.org/bin/view/Projects/BugzillaComponentsZeroPointSeven

Uh, I seem to have issues with a lot of changes...

I am a fan of larger and fewer buckets. Therefore the change from
Accounts to Accounts Dialog gets a -1 from me. I think the it should
just be Accounts.

I don't like the change from Calendar to Calendar UI either. I'd prefer
just Calendar, as otherwise there is no catch-all for calendar bugs
even. But I see there is consistency on this so maybe I'll just need to
live with this.

Calendar: Minipreview sounds weird to me, I'd just keep it as minicalendar.

I am not so hot on the "service" in a component name, like Calendar:
Service. Some projects use front-end and back-end for these, but I am
not sure if they are any better for regular users. Maybe I'll just have
to live with UI and Services.

I think Presentation is going to cause confusion. I am not sure what
would characterize this correctly and with less confusion.

I don't think we need Documentation: Web. We already have the catch-all
Documentation and also Dev and User documentation components. I think
those could be used for web-related documentation as well.

If we are trying to get rid of "framework" in component names, then
Security Framework might be better as Security Services (ugh). (But what
about Security UI then...)

I think Collections is going to cause confusion. For the user, they only
deal with collections from the sidebar. Therefore I would guess they
would file the bug in the sidebar component.

I think Zanshin should have its own product.


We already have Tools component, which covers headless.py.



I would say that you should not create components until there are
actually bugs for that piece of code you are thinking about creating a
component for. And there should be several bugs (I'd say at least 10
bugs) and even then we should be reasonably sure that the piece of code
is not going away anytime soon.

-- 
  Heikki Toivonen


Attachment: signature.asc
Description: OpenPGP digital signature

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to