Re: [Debconf-team] Using the BTS as a summit issue tracker
Hi martin (2015.01.21_21:31:55_+0200) I would prefer if we had an actual package, but a pseudo one will do fine for now. While it would be good to have summit in Debian, of course, you would also want to have a place to track DebConf-specific issues. +1 to the BTS, and yes, a summit.debconf.org pseudo-package sounds like what we'd want. Running entirely from a packaged summit is probably a long way off, if even possible. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
On Wed, Jan 21, 2015 at 2:31 PM, martin f krafft madd...@debconf.org wrote: also sprach Richard Hartmann richih.mailingl...@gmail.com [2015-01-21 20:27 +0100]: I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I would prefer if we had an actual package, but a pseudo one will do fine for now. While it would be good to have summit in Debian, of course, you would also want to have a place to track DebConf-specific issues. Just to be clear, that if we are talking about using BTS to track feature requests and changes to Summit, I see no major issues, and would defer to those working on Summit. If we are looking beyond that, (e.g. sponsorship lead tracking), BTS would likely be suboptimal. -Brian ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
On Wed, Jan 21, 2015 at 07:56:31PM +0100, martin f krafft wrote: also sprach Eric Dantan Rzewnicki e...@zhevny.com [2015-01-21 19:18 +0100]: Honestly, I don't think we need a team discussion. This should be the infrastructure team's decision just like upstream choses the BTS/issue tracker for their software. I certainly don't disagree. But, -infra don't have our own mailing list and it was suggested to me (by bremner, i think?) that I point to some public evidence of team consensus when sending the request to the BTS admins. I wasn't sure the request would be accepted coming from me as a non-DD who's not really known in Debian outside of debconf-team. That said, I think the proposal is sane and would rather see it done sooner than later, unless of course there are good arguments against it. Thanks for weighing in. -edrz ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
also sprach Eric Dantan Rzewnicki e...@zhevny.com [2015-01-21 19:18 +0100]: I propose to wait 1 week for discussion. If there is consensus that this is a good idea I'll take the action item to request the psuedo-package from the BTS admins, pointing to this thread as rationale and evidence of team support. If there is no response or significant disagreement, I suggest it be added to the 2015-02-02 meeting agenda. Honestly, I don't think we need a team discussion. This should be the infrastructure team's decision just like upstream choses the BTS/issue tracker for their software. That said, I think the proposal is sane and would rather see it done sooner than later, unless of course there are good arguments against it. -- .''`. martin f. krafft madd...@debconf.org @martinkrafft : :' : DebConf orga team `. `'` `- DebConf15: Heidelberg, Germany: http://debconf15.debconf.org DebConf16: Cape Town or Montreal? https://wiki.debconf.org/wiki/DebConf16 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
On Wed, Jan 21, 2015 at 7:18 PM, Eric Dantan Rzewnicki e...@zhevny.com wrote: I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I would prefer if we had an actual package, but a pseudo one will do fine for now. Martin attempted to start a discussion[1] about a general solution for all of DebConf to replace rt. But, it didn't progress, yet. If there are suggestions for a general solution, please respond to that thread. I still don't think that scales, especially for sponsorship. I propose to wait 1 week for discussion. If there is consensus that this is a good idea I'll take the action item to request the psuedo-package from the BTS admins, pointing to this thread as rationale and evidence of team support. If there is no response or significant disagreement, I suggest it be added to the 2015-02-02 meeting agenda. With my infra team lead hat on, I would say we don't even need to wait a full week. As you say, this should not be very controversial and I would want to move sooner rather than later. Thanks for picking this up again, Richard ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
[Debconf-team] Using the BTS as a summit issue tracker
I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I find it confusing and difficult to use the wiki[0] to track bugs and development requests for summit. Determining who made a particular request in order to contact them for more information is cumbersome, at best. It's also non-optimal for tracking discussion of a given issue. For development requests, it's not clear if something is just a random idea or annoyance someone had in a particular moment or something that a given subteam has discussed, reached consensus about and signed off on. For these reasons and more, I think we need a real ticketing system for Summit. Martin attempted to start a discussion[1] about a general solution for all of DebConf to replace rt. But, it didn't progress, yet. If there are suggestions for a general solution, please respond to that thread. I've discussed the BTS idea with a number of people on irc several times. I don't recall opposition and there were a number of people positive about the idea. I don't recall anyone wanting to try to use rt for this. I do recall several people definitely _not_ wanting to use the alioth tracker. Probably not everyone who might care was present at those times and my memory is definitely fallible. So, please, discuss. I propose to wait 1 week for discussion. If there is consensus that this is a good idea I'll take the action item to request the psuedo-package from the BTS admins, pointing to this thread as rationale and evidence of team support. If there is no response or significant disagreement, I suggest it be added to the 2015-02-02 meeting agenda. Thanks for reading, edrz [0] https://wiki.debconf.org/wiki/Summit#TODO [1] http://lists.debconf.org/lurker/message/20141216.211326.9c02fa68.en.html ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
also sprach Richard Hartmann richih.mailingl...@gmail.com [2015-01-21 20:27 +0100]: I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I would prefer if we had an actual package, but a pseudo one will do fine for now. While it would be good to have summit in Debian, of course, you would also want to have a place to track DebConf-specific issues. -- .''`. martin f. krafft madd...@debconf.org @martinkrafft : :' : DebConf orga team `. `'` `- DebConf15: Heidelberg, Germany: http://debconf15.debconf.org DebConf16: Cape Town or Montreal? https://wiki.debconf.org/wiki/DebConf16 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
On Wed, Jan 21, 2015 at 08:27:23PM +0100, Richard Hartmann wrote: On Wed, Jan 21, 2015 at 7:18 PM, Eric Dantan Rzewnicki e...@zhevny.com wrote: I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I would prefer if we had an actual package, but a pseudo one will do fine for now. Oh. right. I had asked about that last year. Vorlon, i think it was, said something like packaging web aps is fraught with peril. So I let it go then. What packaging skills I had are very rusty, so I'm not sure I know what he meant. But, in principle, I agree if it can be done that it would be worthwhile to have summit and all the dependencies packaged in debian. I would even like to work on that. But, probably not right now given our more pressing needs. It's something to file a bug about, perhaps. ;) Martin attempted to start a discussion[1] about a general solution for all of DebConf to replace rt. But, it didn't progress, yet. If there are suggestions for a general solution, please respond to that thread. I still don't think that scales, especially for sponsorship. He mentioned that, particularly for sponsorship, some things need to be kept confidential. I'm only talking about summit right now. I propose to wait 1 week for discussion. If there is consensus that this is a good idea I'll take the action item to request the psuedo-package from the BTS admins, pointing to this thread as rationale and evidence of team support. If there is no response or significant disagreement, I suggest it be added to the 2015-02-02 meeting agenda. With my infra team lead hat on, I would say we don't even need to wait a full week. As you say, this should not be very controversial and I would want to move sooner rather than later. Thanks for picking this up again, Richard Certainly. I'm only sorry I didn't get to it sooner. Thanks for your response. -edrz ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Using the BTS as a summit issue tracker
Hi Brian, On Wed, Jan 21, 2015 at 02:57:13PM -0500, Brian Gupta wrote: On Wed, Jan 21, 2015 at 2:31 PM, martin f krafft madd...@debconf.org wrote: also sprach Richard Hartmann richih.mailingl...@gmail.com [2015-01-21 20:27 +0100]: I propose we use a psuedo-package in the BTS for summit isues. The BTS already exists and is a central piece of Debian culture, so it seems to me it would be a good fit. I would prefer if we had an actual package, but a pseudo one will do fine for now. While it would be good to have summit in Debian, of course, you would also want to have a place to track DebConf-specific issues. Just to be clear, that if we are talking about using BTS to track feature requests and changes to Summit, I see no major issues, and would defer to those working on Summit. If we are looking beyond that, (e.g. sponsorship lead tracking), BTS would likely be suboptimal. Right. I'm only talking here about tracking issues regarding summit development. -edrz ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
