/srv/irclogs.ubuntu.com/2009/02/13/#ubuntu-doc.txt

=== j1mc is now known as _j1mc
=== _j1mc is now known as j1mc
dsas_mdke: I wrote to the lp team about managing bugs twice, see https://answers.launchpad.net/launchpad/+question/6093720:13
dsas_mdke: please amend/clarify as neccessary :)20:13
Rocket2DMndsas_, i think bugs need to be filed against both22:16
Rocket2DMnubuntu-docs is for the system documentation which is also available at help.ubuntu.com22:16
Rocket2DMnubuntu-doc team covers more, like the community docs22:17
Rocket2DMnthe ubuntu-doc team is the parent of the committers as well22:18
Rocket2DMnit is confusing though :)22:18
dsas_Rocket2DMn: Yes. there's 3 things there.22:19
dsas_the ubuntu-docs ubuntu package, the ubuntu-doc team and the ubuntu-doc project22:19
dsas_Rocket2DMn: The wiki bugs should probably be filed against a different/sub project that the ubuntu-doc team also looks after. or something.22:20
dsas_Also there are various bugs the ubuntu-docs team should just be subscribed to...22:21
Rocket2DMnwell if the ubuntu-docs should be subscribed, then the bug should be filed under it22:22
Rocket2DMnsince it is a package which is installed on every ubuntu system22:22
dsas_Rocket2DMn: Not neccessarily,22:23
Rocket2DMndo you have an example?22:23
dsas_if there's a bug we've introduced into the gnome2-user-guide for example. ubuntu-docs should probably be subscribed to it, but the bug belongs with the gnome-user-guide not with the ubuntu-docs project22:23
dsas_Rocket2DMn: Though it doesn't currently work that way I think.22:24
dsas_The bug gets filed against gnome2-user-guide and eventually one of may notice it.22:24
Rocket2DMndo you have a link for such a bug?22:24
dsas_no, it's hypothetical.22:24
Rocket2DMni dont really see how it affects anybody subscribed to ubuntu-docs if its not in the ubuntu-docs package22:25
dsas_Rocket2DMn: because we make changes to that package too.22:25
Rocket2DMnif a change is made elsewhere, like during packaging, then it is a problem with our implementation of that package22:25
Rocket2DMn(like if we edit a man page)22:25
Rocket2DMnthat's literally a bug against the package, though its not one that travels upstream22:26
dsas_Rocket2DMn: Yes. perhaps the ubuntu-doc team ought to be subscribed to such bugs in the gnome-user-guide package which the ubuntu-doc team do modify from time to time22:26
Rocket2DMnfrom time to time huh?  I think in that case they should be manually added to the subscriber list22:28
dsas_Rocket2DMn: perhaps bug 201131 is an example of what I mean.22:28
ubot4Launchpad bug 201131 in gnome-user-docs "Documentation for gnome-control-center does not mention PolicyKit" [Medium,Confirmed] https://launchpad.net/bugs/20113122:28
dsas_Rocket2DMn: that is the current workflow. individual members subscribe to those bugs (they usually get wrongly reported against ubuntu-docs in the first place!)22:29
Rocket2DMnso the task is opened against Ubuntu Documentation22:31
Rocket2DMnthat seems correct to me22:31
dsas_Rocket2DMn: it shouldn't be. It's not a bug in ubuntu documentation. it's a bug in the ubuntu package of gnome-user-docs that is handled by the doc team22:31
Rocket2DMn"The Ubuntu Documentation Project (UDP) is a community-driven project that develops and maintains Ubuntu-specific documentation."22:34
Rocket2DMnah i see22:34
Rocket2DMni think its still appropriate22:36
dsas_heh, ok. I guess we'll just have to agree to differ on that.22:37
Rocket2DMnhehe, i think its easiest if you kinda ignore the ubuntu-doc team22:37
Rocket2DMnthat is to say, the project...22:37
Rocket2DMnoh man22:37
dsas_It still leaves the question that we have to manage the status of some bugs twice, or check in some locations twice.22:37
Rocket2DMnignore this - https://launchpad.net/~ubuntu-doc22:38
dsas_Rocket2DMn: Perhaps. That still leaves the issue above though!22:38
dsas_that should be "check two locations" not "check in some locations twice".22:39
Rocket2DMnhttps://launchpad.net/ubuntu-doc is like an upstream for https://launchpad.net/ubuntu/+source/ubuntu-docs22:39
Rocket2DMnso yes, you do have to check in 2 places :(22:39
dsas_Rocket2DMn: Yep, that's the main thing I don't want to have to do.22:40
Rocket2DMnheh, im not really sure there is any way around it.  the latter is the actual ubuntu package that users would file bugs to, say, if they use apport22:40
Rocket2DMnwhereas the former is where code is maintained22:41
dsas_Rocket2DMn: I couldn't think of anything either, that's why I asked the LP guys.22:41
dsas_probably a bit of a long-shot :)22:41
dsas_we're a bit of an edge case I imagine.22:41
Rocket2DMnyeah, thanks for taking interest though22:41
Rocket2DMnit's just that there isn't another upstream location, ubuntu-docs package upstream IS on launchpad as well22:42
dsas_Yes, and the package is maintained by us. and our "Fix released" is when a new package gets released etc.22:43
dsas_it's an artificial distinction that doesn't really help us.22:43
dsas_Though I suppose there is an argument that the case of someone deriving from ubuntu is currently catered for.22:44
dsas_not that I ever knew of a deriviative caring about the system docs22:44
Rocket2DMnwe can still use fix committed and fix released22:45
Rocket2DMnif fixed code is in a bzr branch, then it's committed, if it's pushed to the package and placed in a repository, then its released22:45
Rocket2DMnit is pretty trivial though22:46
dsas_Rocket2DMn: yes. that's the same for the ubuntu package and the "upstream" development.22:46
dsas_they both happen at the same time.22:46
Rocket2DMnyeah, though there is some delay22:46
dsas_we count fix committed for the upstream project and the source as when a fix is checked into bzr (this is similar to how the ubuntu-gnome desktop team work)22:47
dsas_we count fix released for the upstream project when a new package is in the ubuntu repos, we count fix released for the packages when a new package is in the repos22:48
Rocket2DMnyeah, i tend to think of Fix Comitted as  Work is Complete and available for download somewhere22:48
Rocket2DMnFix Released means its in the ubuntu repos (for ubuntu-docs) or is merged with the main branch of the upstream code22:49
dsas_Rocket2DMn: That's not how we manage that currently in our projet.22:49
dsas_oh wait sorry I misread. Yes it is. the or bit is for normal programs22:50
Rocket2DMnyeah i dont think i explained that very well22:50
Rocket2DMnyou get the idea though22:50
dsas_yeah. it's probably because I'm having two conversations at once22:51
Rocket2DMnthats ok im about to bump you down to one convo b/c im going afk22:51
Rocket2DMnwe'll see if matthew has anything to add, otherwise cheers :)22:51
dsas_heh yeah, thanks for the discussion.22:51
dsas_I'm going to get off soon myself22:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!