There is lots of component that are not present, here is a proposal, if possible, do not create them right now, as we may wish to discuss a little. - mailling lists, for everything related to sympa - epoll, for epoll - mirror , for mirror stuff, mga::mirror and stuff related to mirror - transifex - ldap, for stuff related to ldap - servers, for hardware or general issue What about : - mail, for everything related to mail ( ie, postfix level ? ) - meetbot, for supybot and the website - svn/git ? Feel free to post other idea Reproducible: Steps to Reproduce:
I am not sure it is useful to create as many different components. We can keep the list of components short, with something like this : - Account requests - Buildsystem - Other infrastructure (mail, ldap, epoll, mailing lists, etc ...) Or we can add many components, one for each service. However I don't know if that's really useful. Many components makes it more difficult to select the right one. For example if you have a problem receiving email from epoll after changing something in your ldap account, you can add it to epoll, mail or ldap.
CC: (none) => boklm
Well, we can use this to have specific people in CC, for bug triage. This would also be used for stats. And why then would we have BuildSystem being separate for the rest ?
Ok, so maybe I was wrong when thinking it was not useful.
Well, maybe I am too eager to put stuff in small box too :)
It makes sense to compartiment a bit. Maybe we should use "role" components and let details (particular platform, domain name) to be filled or extracted from this: - mailing-lists - voting (=> epoll) - mirrors - translation (=> transifex) - user directory (=> ldap) - etc. Or is that too generic?
CC: (none) => rdalverny
Yes, I think using "role" components without too much details is better.
I think we should start by adding the "Others" component now. And add other components as needed, when we see that many items would fit in that component.
(In reply to comment #7) > I think we should start by adding the "Others" component now. And add other > components as needed, when we see that many items would fit in that component. That's looks optimal to me.
Ok, I have added the "Others" component.
This bug can be closed, isn't it ?
CC: (none) => stormi
Yes.
Status: NEW => RESOLVEDResolution: (none) => FIXED
CC: boklm => (none)