Re: [Sugar-devel] changes in trac and others
On Sat, Oct 9, 2010 at 08:46, Tabitha Roder tabi...@tabitha.net.nz wrote: What would be the difference between Owner and Developer then? I assumed that owner was the same as maintainer same as developer. Tom tells me that at his work the bug is assigned to an assignee or a team. In either case the team leader is officially the owner but often someone else takes on the owner duties that is not tracked. The other option at his work is cc list for those who want to know what happens. Language is complicated, and I speak English as a first language, must be hard for our friends who speak English as another language to work out what is going on with these titles. Yes, all the webapps we use have different terms for the roles, I'm afraid we cannot do much better than document it clearly in the wiki or so unless we fork them. Regards, Tomeu Tabitha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
What would be the difference between Owner and Developer then? I assumed that owner was the same as maintainer same as developer. Tom tells me that at his work the bug is assigned to an assignee or a team. In either case the team leader is officially the owner but often someone else takes on the owner duties that is not tracked. The other option at his work is cc list for those who want to know what happens. Language is complicated, and I speak English as a first language, must be hard for our friends who speak English as another language to work out what is going on with these titles. Tabitha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
On Mon, Oct 4, 2010 at 19:49, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Frederick Grose's message of Mon Oct 04 18:09:18 +0200 2010: The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan What would be the difference between Owner and Developer then? My guess is that Seeta wants to track which of their developers may work in a particular issue in the future, without actually taking ownership of the issue. I interpret being the owner as I'm working on this right now, so if you start working on it we may end up doing duplicated work. In any case, I think Seeta needs to explain what their intention was with this change, and the other organizations that are as well putting people to work on Sugar tickets are also welcome to do the same. Regards, Tomeu Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
On 10/04/2010 07:31 PM, Daniel Drake wrote: On 4 October 2010 17:09, Frederick Grosefgr...@gmail.com wrote: The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan On a community level, I don't think its right to assign a specific developer to the task. Anyone is welcome to come along and post a patch. If SEETA want to add their internal metadata to the tickets they should use the keywords field. e.g. add keyword seetadev:Ishan Daniel +1, I think using key words works quite ok. I have been handling it the same way with OLPC-tickets. And people can put themselves in cc when they are interested in a bug. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
Excerpts from Tomeu Vizoso's message of Fri Oct 08 10:01:37 +0200 2010: The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan What would be the difference between Owner and Developer then? My guess is that Seeta wants to track which of their developers may work in a particular issue in the future, without actually taking ownership of the issue. I interpret being the owner as I'm working on this right now, so if you start working on it we may end up doing duplicated work. That's how I interpret it as well. But then a single Developer field (which would supposedly only take a single value) wouldn't work as other organisations might want to assign one of their developers. In any case, I think Seeta needs to explain what their intention was with this change, and the other organizations that are as well putting people to work on Sugar tickets are also welcome to do the same. +1 on both counts Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
On 04.10.2010, at 12:56, Tomeu Vizoso wrote: Note that mentioning it in #sugar is not enough +1 - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
Excerpts from Tomeu Vizoso's message of Mon Oct 04 12:56:24 +0200 2010: A change that I think can be made without asking first is the addition of the 1.0 milestone, but I think we still need to agree on the meaning of moving a ticket to that milestone. You are faster to complain than I can write an email about the change. :-P The addition of Seeta-specific fields needs to be discussed before, because we have other organizations working together in Sugar Labs and some amount of coordination is needed. +1, I was quite surprised by it, but expected it to have been agreed upon by Aleksey, Simon and you. Seems that wasn't the case. It's OK if Seeta uses our bug tracker (especially since inter-bugtracker integration is still in its infancy in general and not supported by Trac at all AFAICT), but it would have been nice to discuss this on systems@ first (or at least announce it). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] changes in trac and others
Hi, have seen that recently some changes have been made to trac outside the normal adding of users and components. I would like to request that when making those changes, that the list was notified, if the change is presumed uncontroversial. If the change has a broader effect (such as adding a field), please ask in sugar-devel first for opinions. A change that I think can be made without asking first is the addition of the 1.0 milestone, but I think we still need to agree on the meaning of moving a ticket to that milestone. The addition of Seeta-specific fields needs to be discussed before, because we have other organizations working together in Sugar Labs and some amount of coordination is needed. Note that mentioning it in #sugar is not enough because not everybody is always present and because the channel is not logged. For other services, please notify the list as well when your changes will affect the other people's work. Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
On Mon, Oct 4, 2010 at 8:23 AM, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Tomeu Vizoso's message of Mon Oct 04 12:56:24 +0200 2010: A change that I think can be made without asking first is the addition of the 1.0 milestone, but I think we still need to agree on the meaning of moving a ticket to that milestone. You are faster to complain than I can write an email about the change. :-P The addition of Seeta-specific fields needs to be discussed before, because we have other organizations working together in Sugar Labs and some amount of coordination is needed. +1, I was quite surprised by it, but expected it to have been agreed upon by Aleksey, Simon and you. Seems that wasn't the case. It's OK if Seeta uses our bug tracker (especially since inter-bugtracker integration is still in its infancy in general and not supported by Trac at all AFAICT), but it would have been nice to discuss this on systems@ first (or at least announce it). The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
On 4 October 2010 17:09, Frederick Grose fgr...@gmail.com wrote: The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan On a community level, I don't think its right to assign a specific developer to the task. Anyone is welcome to come along and post a patch. If SEETA want to add their internal metadata to the tickets they should use the keywords field. e.g. add keyword seetadev:Ishan Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] changes in trac and others
Excerpts from Frederick Grose's message of Mon Oct 04 18:09:18 +0200 2010: The SEETA Developer: field might better be adjusted to Developer:, and we could use a convention to tag the developer's name, such as, [SEETA] Ishan What would be the difference between Owner and Developer then? Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
