[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Equinox->Bundles component is getting crowded

For now I would stick with prefix in the summary (e.g. [prov]). This is
what I have been using in p2 and worked great so far, as I never see any
other bugs from the incubator. This is pretty clear and does not bring
forces us into to strict of a categorization. Also this way bugs can be
multiply categorized ([sec][prov], a security issue on provisioning).
As some work area because vast, we can try to create categories but for now
I don't see the need.

PaScaL


                                                                                                                    
  From:       Thomas Watson <tjwatson@xxxxxxxxxx>                                                                   
                                                                                                                    
  To:         Equinox development mailing list <equinox-dev@xxxxxxxxxxx>                                            
                                                                                                                    
  Date:       09/12/2007 02:50 PM                                                                                   
                                                                                                                    
  Subject:    Re: [equinox-dev] Equinox->Bundles component is getting crowded                                       
                                                                                                                    





There are two extreme positions to take. Lump a large number of loosely
related deliverables under one component or create a separate component for
each and every deliverable. I'm not sure I favor the latter extreme.
Currently the Equinox download page allows you to download each bundle
individually so each bundle is a separate downloadable item. Creating a
separate component for each and every bundle in Equinox may prove to be too
much overhead. It is my understanding that in Eclipse typically every
bugzilla component has its own set of commit rights in CVS. If we have a
very high number of components then we will be holding a very large number
of committer elections to get all the committers the access they need :-)

I think we a balance and create components as we see fit to split up the
different work areas in Equinox instead of creating a component for every
bundle.

Tom



(Embedded image moved to file: pic04828.gif)Inactive hide details for BJ
Hargrave---09/12/2007 12:31:35 PM---It would probably be best if each
separately downloadable itemBJ Hargrave---09/12/2007 12:31:35 PM---It would
probably be best if each separately downloadable item had its own
                                                                           
                         BJ                                                
                         Hargrave/Aus                                      
                         tin/IBM@IBMU                                      
                         S            (Embedded image moved to file:       
                         Sent by:     pic12496.gif)                        
                         equinox-dev-                                   To 
                         bounces@ecli         (Embedded image moved to     
                         pse.org              file: pic19700.gif)          
                                              Equinox development mailing  
                                              list                         
                         09/12/2007           <equinox-dev@xxxxxxxxxxx>    
                         12:30 PM     (Embedded image moved to file:       
                                      pic10719.gif)                        
                                                                        cc 
          Please respond to                   (Embedded image moved to     
   Equinox development mailing list           file: pic25593.gif)          
      <equinox-dev@xxxxxxxxxxx>       (Embedded image moved to file:       
                                      pic26588.gif)                        
                                                                   Subject 
                                              (Embedded image moved to     
                                              file: pic23207.gif)          
                                              Re: [equinox-dev]            
                                              Equinox->Bundles component   
                                              is getting crowded           
                                                                           
                                                                           
                                      (Embedded image moved to file:       
                                      pic26607.gif)                        
                                             (Embedded image moved to      
                                             file: pic15395.gif)           
                                                                           
                                                                           



It would probably be best if each separately downloadable item had its own
component against which people could file bugs.
--

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx

office: +1 386 848 1781
mobile: +1 386 848 3788




From:
Thomas Watson/Austin/IBM@IBMUS
To:
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date:
2007-09-12 12:34
Subject:
Re: [equinox-dev] Equinox->Bundles component is getting crowded



For the security stuff I was referring to the security-specific bundles
like login (JAAS integration etc.)

You are right there is a lot of cross-cutting concerns with the other
security related work that will not really fit into any one component.

Tom



John Arthorne ---09/12/2007 11:25:42 AM---Creating a new component for p2
definitely makes sense to me. I don't know much about the security work,
but that may be diffi

John Arthorne <John_Arthorne@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
09/12/2007 11:21 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>




To

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

cc


Subject

Re: [equinox-dev] Equinox->Bundles component is getting crowded






Creating a new component for p2 definitely makes sense to me. I don't know
much about the security work, but that may be difficult to partition into
its own component because it's an inherently cross-cutting concern. If
there end up being a number of security-specific bundles, it may make
sense.

Generally speaking, I think more components is a good thing. It's a great
way to bring in new committers who may not be able to make the large
commitment needed to contribute across a large part of Equinox.

John


Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
09/12/2007 11:42 AM


Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>



To
equinox-dev@xxxxxxxxxxx
cc

Subject
[equinox-dev] Equinox->Bundles component is getting crowded








The Equinox project continues to grow with new components and new
contributes being added. Thanks everyone!!

As new contributions are graduated into Equinox proper we need to place
them under one of the existing components. Currently we have the
"Framework" and "Bundles" components for Equinox proper in bugzilla/cvs. A
large majority of the new contributions will fall into the "Bundles"
component. For example, we have a few work areas in the equinox incubator
which are very active (e.g. p2, security etc). Once this work graduates it
will likely to be placed into the generic "Bundles" component. This will
make an already crowded component even more crowded.

Should we consider creating a more diverse set of components for the work
which is graduated into Equinox? I think the p2 and security work will
deserve their own component when they graduate. Thoughts?

Tom
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

(See attached file: pic01850.gif)
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
(See attached file: pic04528.gif)(See attached file: pic01850.gif)
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Attachment: pic04828.gif
Description: GIF image

Attachment: pic12496.gif
Description: GIF image

Attachment: pic19700.gif
Description: GIF image

Attachment: pic10719.gif
Description: GIF image

Attachment: pic25593.gif
Description: GIF image

Attachment: pic26588.gif
Description: GIF image

Attachment: pic23207.gif
Description: GIF image

Attachment: pic26607.gif
Description: GIF image

Attachment: pic15395.gif
Description: GIF image

Attachment: pic04528.gif
Description: GIF image

Attachment: pic01850.gif
Description: GIF image