On Saturday 07 March 2009 11:53:50 pm Michael Fox wrote:
On Sat, 2009-03-07 at 23:18 -0600, Rajko M. wrote:
On Saturday 07 March 2009 10:30:25 pm Michael Fox wrote:
...
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
true but passing fancies, or minor fixes, for example a little tweak to say a KDE4 widget (i know it not OpenSuSE) they can just put it in the tracker incase someone wants it, also with a tracker a patch that may not be needewd now would still be found when it is needed avoiding alot of hassle. and as such keps proposals and fixes from the community all organised and in one spot not scattered all over the web only being found by scouring the mailing lists.
We have bugzilla, as Christian said. The problem is only proper selection of options when you file (upload) an improvement patch, and later when you are looking for it. Bugzilla has everything in the URL, so for some functions there are already links on the openSUSE wiki. OK, here is example: http://en.opensuse.org/Bugs That kind of links can be prepared for any project. It is much easier than to setup another bugzilla, and at the end we would have to create such "Easy Links" anyway. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org