[00:16] maxb: almost always will be @ 2200 UTC. Sometimes 2400 UTC, but that's the exception. [00:20] hi all [00:21] simple question [00:21] are there any plans on localization of Launchpad? [00:21] no [00:21] (simple answer) [00:30] jml, too bad. any simple reasons why? [00:32] kwah: yeah. we've planned so many other things already; making even more plans is counter-productive. [00:36] damn, I was kind hoping that LP may be suitable as a bug tracker for people not really knowing English, which I discussed here other day. [00:36] thanks [00:36] kwah: there is some localization support in our answer tracker [00:37] kwah: but not in bugs. [00:38] I see. [00:38] Thanks. [00:38] Will look further for possible solutions. === matsubara-dinner is now known as matsubara === matsubara is now known as matsubara-afk [04:49] Should I be concerned when almost the entire last screenful of a Launchpad bug is milestone deferrals? [04:52] wgrant: What bug? [04:53] wgrant: it means it isn't urgent enough [04:54] nhandler: Bug #204525 [04:54] Launchpad bug 204525 in soyuz "Error message when uploading packages with invalid epochs could be less useless" [Low,In progress] https://launchpad.net/bugs/204525 [04:54] It's certainly not urgent. [04:56] It even has a "trivial' tag. I wonder why they haven't fixed that. [05:10] nhandler: without looking at the bug, it could be any number of reasons: lack of time, lack of headspace, uncertainty over correct solution... [05:11] forgetfulness even. [05:11] perceived difficulty [05:11] stacks. [05:11] stacks of potential reasons :) [05:12] * nhandler likes the reason that nobody in a position to fix it is affected enough by it to care about fixing it right now [05:12] that's partly it. [05:13] but "in a position to fix it" is pretty broad [05:13] if you just mean "with access to the source code", well, plenty of open source projects have bugs like this that are much older. [05:14] The difference is, for those projects, I can go and fix a bug like this. [05:14] although I would wager they'd have fewer such bugs, once you got over the difficulty of defining fewer. [05:15] There are so many little bugs that I'll hopefully be able to fix in a few months. [05:15] :D [05:15] or at leat fewer users frustrated over the fact that they aren't authorized to attempt a fix ;-) [05:15] But not that one :( [05:15] (even if it does get deferred again, it's not being released...) [05:15] s/leat/least/ [05:16] Well, I personally don't care about that bug too much. I rarely am adding epochs to my package versions [05:16] * nhandler -> bed [05:16] Night. [05:17] SamB: I dunno, I always manage to find something to get frustrated about :) [05:18] jml: Not in that area in any open source project, I hope. [05:19] wgrant: not access to code, no. [05:20] wgrant: but often "my patch is being ignored" or the review process or code opacity or lack of test suite or some core devs major branch blocking work or ... [05:21] jml: I hope we won't see that with LP. [05:21] wgrant: so do I! [05:23] review processes in particular are a trade-off that directly (obviously) affects the ease of getting a patch landed. [05:23] But if not, I guess you'd get a fork. And I imagine you *really* don't want that. [05:23] But review processes can't really be done without... [05:23] and different people value the trade differently -- not much that can be done about that. === Andre_Gondim is now known as Andre_Gondim-afk === gmb` is now known as gmb [11:24] adiroiban: Hi! About the bug #352770, may I need to change the description for explicitly say it's a .desktop file issue? Thanks! [11:24] Launchpad bug 352770 in computer-janitor "Computer Janitor uses computerjanitor.mo, but .desktop uses computerjanitorapp.mo" [Undecided,New] https://launchpad.net/bugs/352770 [12:17] how do i close a bug report in launch[d [12:19] bromic94: you set its status to Fix Commited, Fix Released, Invalid or whatever other status is appropriate [12:19] k [12:19] how do i remove a bug [12:19] bromic94: you can't remove bugs [12:20] k [12:21] it says on the site about converting stuff from 1 bug tacker to another [12:21] how is that done and how much is it? [12:25] bromic94: we can import bugs from some bugtrackers for you, if you wish to move your project to launchpad, or you can link bugs in launchpad to an external bug tracker. using lauchpad is completely free for open source projects. proprietary products pay a modest fee [12:27] so other/open source would be free [12:28] yea i have one i am not sure if you guys have heard of it [12:28] its called flyspray [12:29] bromic94: ah yes, just saw the bug report about it [12:30] what do you mean the bug report about it [12:30] bromic94: unfortunately we don't currently support flyspray for bug watches. if there's a way to export bugs from it in some format we can still try to import them [12:31] what format would you need [12:32] bromic94: well, i think we only currently support the bugzilla format, but what i meant is that if the bugs are exported to _any_ format which is easily readable, it shouldn't be hard to write a script to import them [12:32] in fact you can even do this yourself using the REST web service API [12:32] i can export them in .sql format [12:33] bromic94: well, that's not really easy to read, since you need an SQL parser. maybe something like JSON or XML [12:33] k [12:33] yes ic an do that [12:33] gmb: do you remember what formats of bug dumps we currently know how to import? [12:34] if xml is def on i just did that [12:34] where would i send it or where can i find the REST web services API [12:34] intellectronica: We can't impersonate using the web service. [12:35] wgrant: can you guys use XML format/ [12:35] ? [12:35] bromic94: We have a standard XML bug interchange format. If you can coerce your flyspray data into that format, we can import it. [12:35] wgrant: no. that sort of solution would only be appropriate for some projects. if you have lots of history you want to preserve you'd want to do it at a lower level [12:37] gmb i just did xml [12:37] where would is end it to get it converted? [12:38] bromic94: Well, what normally happens is that we give you a copy of the format schema and you're responsible for transforming your XML into that format. If you'd rather we did that, it's going to take longer. You can open a question at answers.launchpad.net and we'll take it from there. [12:39] *what I mean is: "If you'd rather we did the transformation work for you" [12:39] bromic94: it would be best if you could file a question with the details. today everyone's busy readying tonight's release, but after that youre request will be dealt with promptly [12:40] tonight's release of what? [12:41] of updated launchpad? [12:41] bromic94: Launchpad. [12:41] whats new in this version? [12:42] bromic94: vastly improved capture and display of bug activity, official bug tags and lots more :) [12:42] * wgrant loves the new activity display. [12:42] bromic94: There'll be a blog post about it at blog.launchpad.net later with more details. [12:42] how much later just curious? [12:43] bromic94: http://blog.launchpad.net/notifications/launchpad-update-april-1st-maintenance-window-increased-to-3-hours [12:43] so my questions just post it at answers.launchpad.net? === bromic94 is now known as thewrath [12:44] bryce: answers.launchpad.net/malone [12:44] Grr. [12:44] Sorry bryce [12:44] thewrath: answers.launchpad.net/malone [12:44] whats does the malone mean? [12:45] sorry gmb i just saw taht my name was not right [12:45] bromic94 was my log in name to the server i ssh into and not for freenode [12:45] thewrath: malone is the codename for the Launchpad Bug Tracker. So by going to answers.launchpad.net/malone you're filing a question *about* malone. [12:45] thewrath: No worries. I fail at IRC anyway ;) [12:45] lol [12:46] uts = gmt right? [12:48] thewrath: UTC == GMT, yes. [12:48] k [12:51] maintenance is 5pm est - 8pm est right? [12:53] thewrath: Yes. === thekorn_ is now known as thekorn [14:25] <[pablo]> is there any way to get a list of all the coments i've written? [14:26] <[pablo]> i see the activity log with my comments but it doesn't say in which bugs it was [15:15] I'm not sure how to phrase my question... I basically need some help in understanding what would be the best way to manage multiple projects' bugs, that affect each other, but have different release schedules. I have an example bug that we could use to discuss it [15:16] https://bugs.launchpad.net/landscape/+bug/307314 my issue is how to track the different states for each project. There is the main one, then the client code, then the client package in each ubuntu distro [15:16] Ubuntu bug 307314 in landscape-client "Landscape client can't handle multiple graphs" [Critical,Fix committed] [15:16] so it's committed, but not yet released everywhere. Also, the fix was in the client, so I don't think having "committed" on the server is right, but it does affect the server, so... [15:17] someone available for a brainstorm or to give me a few hints? [15:43] hi all [15:44] what is normal reaction time on inappropriate content reported on help@launchpad.net ? [15:44] herb, ^ ? [15:45] mars: no idea. I don't get help@ [15:45] ik ook niet [15:45] o_O [15:46] kwah spam gerelateerd? [15:46] kwah, just to be clear, you mean the mailing list help@launchpad.net, and not the help.launchpad.net wiki? [15:46] nope, dirty wording in acc.name [15:47] ah [15:47] hmm [15:47] mars, yep [15:48] kwah, the fastest way is to go to https://answers.edge.launchpad.net/launchpad/+addquestion, and not the inappropriate content there [15:49] s/not/note/ [15:50] https://answers.edge.launchpad.net/launchpad/+question/66115 [15:51] kwah, thanks [15:54] So help@ on the page https://help.launchpad.net/HelpRotation is not really useful in such cases? [15:55] Although page mentions: "Each week day, a member of the Launchpad team is available to help you with _any Launchpad-related requests_." [15:57] kwah, well, It's more like help triage. I've forwarded your request to someone who can handle it. === mars changed the topic of #launchpad to: https://launchpad.net/ | Help contact: mars | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com [16:00] mars, thanks [16:27] If I commit a branch to junk, can I move it to a project later easily? [16:29] vadi2, one quick way is to use $ bzr push --remember lp:~user/project/branchname [16:29] right, thanks === noodles775 is now known as noodles775-afk === matsubara is now known as matsubara-lunch === salgado is now known as salgado-lunch [17:20] does vcsimports only support importing CVS HEAD? [17:23] skiquel, yes, as far as I know. [17:24] I put that in the whiteboard on my request [17:25] didn't see the option in original form === matsubara-lunch is now known as matsubara [18:06] ConjoinedBugTaskEditError: This task cannot be edited directly, it should be edited through its conjoined_master.
[18:07] that sounds awful [18:07] mdz: url? [18:07] https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/notify-osd/+bug/353263/+editstatus [18:07] it logged an oops [18:08] Error: Could not parse data returned by Ubuntu: The read operation timed out (https://launchpad.net/bugs/353263/+text) [18:08] it looks like what happened was that I loaded the page, then someone else added a bug task, then I submitted +editstatus [18:09] mdz: ok. the behaviour is sane, but it should be helpful rather than oops [18:22] intellectronica, mdz: looks like bug 106338. we're waiting the oops to be synced to devpad to confirm [18:22] Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/106338/+text) [18:23] gee, we must update ubottu to use the API. this is bad PR :) [18:25] :) === mikrox is now known as mikro [18:53] does the fact that Launchpad sets bugs as "Fix Released" when a source package is uploaded, not when it has been built or published already constitute a bug report somewhere? I couldn't find it [19:01] mdke: I would suggest it's not a bug. How would you choose which architecture mattered? === salgado-lunch is now known as salgado === bromic94 is now known as thewrath [19:10] can i set it up for what different bugs affect different things? [19:10] how do i create tehm> [19:10] *how do i create them? [19:11] thewrath, sorry, I don't understand the question? [19:18] https://bugs.launchpad.net/wasdats/+bug/351851 if you go there mars [19:18] Ubuntu bug 351851 in wasdats "Incorrect Links on pages" [Medium,Confirmed] [19:18] i haev affecting the entire package [19:19] why is that coming up ubuntu bug 351851 [19:19] how can i create sub pieces of that [19:20] bc i know ubuntu has it for like alda or sound or something like that that is not the entire thing with ubuntu but a sub peice [19:24] thewrath, do you mean splitting the project up into smaller projects? like how awn has "awn-core", and "awn-plugins"? [19:25] yes [19:25] or have it apply to a certain series [19:26] well, you can have a bug nominated to be /fixed/ in a specific series (Ats2 or Trunk, in this case) [19:26] maxb: I don't know, I think you'd need to wait until it was built in all architectures [19:27] oh ok === abentley1 is now known as abentley [19:28] https://bugs.launchpad.net/wasdats/+bug/351865 <-- Like that? [19:28] Ubuntu bug 351865 in wasdats "undefined constant usergroup modifyassets.php" [Medium,Fix committed] [19:29] thewrath, yes, that's assigned to a milestone within the Ats2 series. [19:30] k [19:30] perfect [19:30] is mentoring a big thing that people use? [19:30] and the maintenance today should not take longer than 3 hours? [19:31] and how do you close a bug report again or od you do that by fix release? [19:31] thewrath, I trust that it should be done inside of 3 hours - I'm sure our sysadmins gave themselves enough time [19:31] "fix released" closes the bug [19:32] ok [19:32] if i have it in the wasdats/ats2 will it be fix released in both if i only set fix release in series ats [19:33] I think it will only be fixed in the one. [19:33] most projects assume that "fix released" means "fix released in the trunk/ series" [19:34] k [19:34] a team is not necessary correct [19:35] mdke: I think, overall, that would be less desirable than the current situation. [19:35] after all, fixing it in 3.X trunk/ doesn't mean that it has been fixed in the 2.X and 1.X series. The bug should be closed for trunk/, but open for the other two. [19:36] Personally, I regard "Fix Released" on source upload to be the right thing to do, as at that point it's out of the hands of humans and merely waiting for automated processing [19:36] It's worth noting that builds on some architectures lag hugely behind [19:36] maxb: I've seen a lot of confusion today because the fix wasn't actually "released" but the bug was marked as such [19:37] https://bugs.launchpad.net/wasdats/+bug/351865 once again i have it in the main project then under ats2 so if i haev it say fix relreased under ats2 it could still not be fixed under WASD Asset Tracking System (WASD ATS) [19:37] Ubuntu bug 351865 in wasdats "undefined constant usergroup modifyassets.php" [Medium,Fix committed] [19:37] maxb: ideally, "fix committed" should relate to the source being uploaded, and "fix released" when it is published. It's a simple matter of plain language === Nicke_ is now known as Nicke [19:38] "Fix committed" means fixed in the packages's VCS - the fix isn't necessarily in the archive at that point [19:38] maxb: it only means that because you know that that is how it is used [19:38] thewrath, that's true. And the same idea is true whether you use series for different versions of the software, or projects for different versions of the software. [19:39] maxb: as a matter of language it could mean either [19:39] maxb: but it's more important that "fix released" is used accurately, because that is what takes the bug out of search results [19:39] thewrath, fixed in one version does not necessarily mean it was fixed in the other [19:40] maxb: and taking a bug out of search results before it is released means duplicate bugs and confused users [19:40] I see your point, *but* upload is a single discrete point that is actually definable. "available to users" is much more nebulous. Built? On which architectures? Accepted? Published? It still might not be on any given user's local mirror. [19:41] maxb: obviously mirrors are out of our hands, but when it is published is a good milestone [19:41] again, the which architectures question [19:42] maxb: I've answered that though [19:42] bc i am using the series as sub portions of my project [19:42] No. You haven't accounted for the fact that a package may FTBFS on some lesser-used ports architectures and remain so for months [19:43] maxb: ok, but that can be accounted for. I'd say that a fix which hasn't been released on supported architectures hasn't in fact been released [19:43] Once the source is uploaded, there's no more developer action required to fix *that bug*. (FTBFS may be another bug) So there's a real point to having *some* sort of state transition there. I agree that hiding it from the default search results immediately isn't good, though [19:45] I might raise this on a mailing list [19:46] thewrath, if the project is small, but you still want to label compoenents like "ui", "database", "website", then it is usually best to use bug tags [19:46] for reference, mpt has made some good related points on bug 163694, even if it's not quite the same thing [19:46] Launchpad bug 163694 in malone "Fix Committed/Released distinction is inconsistent and unproductive" [Undecided,New] https://launchpad.net/bugs/163694 [19:46] ok [19:47] mars: how do i use bug tags [19:47] like this mars : https://bugs.launchpad.net/wasdats/+bug/351865 [19:47] Ubuntu bug 351865 in wasdats "undefined constant usergroup modifyassets.php" [Medium,Fix committed] [19:49] thewrath, to use tags, click on "Update description/tags" under the bug summary, the Tags input field is under the summary on the page that shows up. [19:50] thewrath, series were originally intended for stable/unstable versions of the software, or other similar flavours of an entire software package [19:51] tags can be used to group bugs together for individual components, among other things [19:51] on Launchpad we use "ui", "javascript", and "database" tags, for instance. [19:52] where can i see hte tags that i use [19:54] they'll appear under the summary of individual bugs, and on the project's overall "Bugs" page, in the right-hand column [19:55] they are to be seperated by a space right [19:55] thewrath, so https://bugs.edge.launchpad.net/wasdats [19:55] yes [19:56] i see that on the main page [19:56] but not for the specific bug report [19:56] which report did you apply the tag to? 351865? [19:56] yes [19:57] nevermind [19:57] i am blind as a bat [19:57] thank god i am not driving a car today [19:57] :) [19:58] thewrath, they are faint at the moment. That's because of the "official tags" feature we are rolling out for larger projects and ubuntu. [19:59] can you show me an example of that? [19:59] we may have to look at it being an "opt-in" thing, because it really doesn't matter for projects with small teams. [19:59] lol [19:59] right now the people who report bugs are the users [19:59] the people who fix them are me [20:00] well, for large projects, people will start tagging bugs with incorrect spellings, or categories that the main project doesn't use [20:00] ah [20:01] what are some of the new features that are coming out tonight that affects small projects [20:03] thewrath, I can't say I know myself, beyond what intellectronica said earlier. LP is a big project, and I don't know what all the teams have in the pipe. [20:03] ok [20:04] i mean it is okay that i using this as a bug tracker for a system for a school but i am willing to give the source code to people who want to use the system and adapt it to their needs right? [20:08] thewrath: anything you're interested in in particular? [20:08] thewrath, as long as the project has an open source license it should be fine. [20:08] how can i release it under an open source licence [20:08] i was just curious intellectronica [20:08] cprov, were you ever able to see what was wrong with launchpad reporting the git ppa build failed when the build log says build successful? Hardy still shows a failure: https://launchpad.net/~git-core/+archive/ppa [20:09] thewrath: see https://edge.launchpad.net/launchpad-project/+milestone/2.2.3 [20:09] its under no licence right now. i would like to do it under an open source licence [20:09] right thanks intellectronica [20:09] any suggestions on how i do this [20:09] jsmidt: I will check. [20:09] mars: is creative commons licence okay? [20:10] or what licence would is better to release it under [20:10] i have to get going here in about 5 minutes for class [20:10] jsmidt: fixed. [20:10] cprov, thanks [20:11] thewrath, Creative Commons is OK, the academic licenses, MIT and BSD, are also popular [20:11] as is the ever-present GNU GPL [20:11] jsmidt: the problem causing all this mess (dispatching builds twice) is already fixes in production. [20:12] how do i release it under any of those open source licences? [20:12] * mars grabs the OSI page [20:12] bc really the only people wanting to use it is the district [20:12] i doubt anyone else would like to use my code [20:12] they might but who knows [20:13] thewrath, the Open Source requirement is for hosting the project itself on Launchpad. There is a for-pay option for closed-source proprietary software. [20:14] thewrath, http://opensource.org/licenses/category [20:14] since this is my senior project i have to release it under open source [20:14] ".:: Licenses that are popular and widely used or with strong communities ::." [20:14] oh, well, easy answer then :) [20:15] what licnece do you tihnk [20:15] I am thinking MIT [20:15] I like MIT personally. I release my own software under that. A simple, no hassle license. [20:15] how do i register it under there though? [20:17] i haev to get going and would like to here soon after class get it "officially registered" [20:18] thewrath, go to the "Change details" link on the project home page, upper right corner (https://launchpad.net/wasdats) [20:18] oh ok [20:18] that is how i register it [20:18] i was not sure if there is anything more than that? [20:19] i mean like when you register with microsoft i was not sure if there anything like that [20:19] thewrath, that's how you change the license. on the OSI page, you'll find instructions for releasing the code under the license [20:19] could you point me into the right direction [20:19] if i would want to take it off of launchpad how do i do that? [20:20] deleting projects is not as simple. We can deactivate it, and a warning will be displayed on the project's landing page [20:21] coul you ppoint me in the right direction for the osi page for releasing code under the MIT [20:21] and we ask that people update the project description with a notice and link to the new project home [20:21] or another licence [20:21] looking [20:21] okay [20:21] jsmidt, ? [20:22] mars: bc i think i have maybe not needed to do launchpad [20:22] hey mars i got go to class so i will talk to you later i will be on later [20:22] mars, sorry, I was saying okay to cprov [20:22] ah :) [20:54] mthaddon: let's chat about bug 325962 when i get back in town on monday [20:54] Launchpad bug 325962 in launchpad-registry "lp-mailman startup is blocking on a pid file in the wrong directory" [High,Triaged] https://launchpad.net/bugs/325962 [20:54] barry: sounds good === mthaddon changed the topic of #launchpad to: Launchpad is going down from 22:00 UTC April 1st until 01:00 UTC April 2nd for a code update | https://launchpad.net/ | Help contact: mars | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com [21:27] hey all [21:28] i have a project i am not sure what licence i want/require to use [21:28] it is used by the school district and really anyone who wants to use it i give them the code [21:28] so i would like someoen to deactivate my project here [21:28] who can i talk to me [21:28] *who can i talk to [21:28] wgrant, hi [21:29] beuno: do you have any idea [21:29] i was in here earlier talking with someone but i forget who htat was [21:29] mars: you here sir [21:29] thewrath, bac or sinzui are your guys [21:29] thewrath, yep. Just looking up one of the OSS license pickers, should help you with the decision [21:30] ok [21:31] is it time consuming, etc to be officially open source? [21:31] thewrath: I can deactivate it, but that may not be necessary if you know what who should use your project and the origin of your source [21:31] thewrath, regardless of the license you pick, the minimum requirement is to take the text of that license and place it in the project root, usually in a file called COPYRIGHT [21:31] sinzui: it is my sneior project that i am doing for college [21:32] it is for a school but if a school wants to use it tthey are more than welcome to [21:32] i knwo there are better ones than mine out htere [21:32] thewrath: what's your project's name [21:32] on launchpad [21:32] hold on [21:33] https://launchpad.net/wasdats [21:33] i would like to change hte wasdats to something else [21:34] thewrath: File a question at http://answers.launchpad.net/launchpad asking for a change and an admin will do it for you. [21:35] hold on [21:35] thank you though [21:35] thewrath, regarding picking a license, you can go with MIT if you want, or you can follow a questionnaire to help you pick: http://blogs.zdnet.com/Burnette/?p=130 [21:36] how do i ofifically register my code to be open source [21:36] thewrath: The free licenses strive to ensure that anyone who distributes your applicaiton also distribute the source for others to review and modify. They ensure you get credit. Most, maybe all, state you are not guarananteeing ths code [21:36] thewrath, you just have to add the copyright and license. There is no official registration. [21:37] okay so where is the copyright and licnece in for MIT [21:38] thewrath: licenses list BSD License (revised) or MIT are very relaxed, where are GNU GPL v3 strive to ensure the code is not used with closed code [21:39] ok [21:39] thewrath: if you want to use the MIT license, you only need to check MIT / X / Expat License for your project [21:39] i was just reading that [21:39] I want to do GPl [21:39] so i would have to get the licence and the copyright? [21:39] thewrath, http://www.gnu.org/licenses/gpl-howto.html [21:40] thewrath: You generally need to copy and paste the license code into a file in your project [21:41] k [21:41] thewrath, in a nutshell: put /* Copyright (c) 2009 my-name-here */ at the top of your source files, and copy-n-paste the GPL license text into a file in the project root called either LICENSE or COPYING [21:42] err, /* Copyright (c) 2009 my-name-here. All rights reserved */ [21:42] ok [21:42] that is all i ahve eto do [21:42] is do those two things? [21:42] mars: what about the copying permission? [21:43] that's handled by the GPL [21:43] the copyright states you own the code. The license are the terms under which others may modify and copy it. [21:43] so i only have to create the LICENCE.txt file and comment all of my source files [21:44] mars: You also need GPL headers in each file. [21:44] where can i find those wgrant ? [21:44] wgrant, ah true, for the GPL you do [21:44] I note that parts of LAZR are bad in that respect [21:44] mars: For any license. [21:45] i am using the GPL [21:45] where can i find the GPL licence headers [21:45] wgrant, I thought that was just to get the warranty into the file? [21:45] mars: No, it's also to specify that the file is under that license. [21:45] thewrath, it's all explained well on the GNU page: http://www.gnu.org/licenses/gpl-howto.html [21:45] In Ubuntu we require it to be explicit, and most other distros do too. [21:46] wgrant, cool, didn't know that [21:46] thewrath, forgive my ignorance, follow wgrant's advice :) [21:46] wgrant: i have the LICENCE.txt file that i need to edit [21:46] what else do i need [21:47] thewrath: See the link that mars gave you a few lines ago., [21:49] wgrant, hi again [21:49] beuno: Hi. [21:50] wgrant, I'm fixing up the dev.lp.net and help.lp.net themes [21:50] is there anything you'd like fixed specifically [21:51] beuno: Besides their obesity, I can't think of anything... but let's see... [21:52] wgrant or mars: could you please verify this information taht i ahve to do and make sure that i dont need to do anything else: http://pastebin.com/m64f02a0f [21:52] thewrath: I don't think you need mars' initial 'All rights reserved line' [21:52] ok [21:52] is everything else correct [21:52] and do i have to do anything else? [21:53] For one thing, that's implied by at least one of the global copyright conventions. [21:53] I think that should do. [21:53] ok [21:53] You should make sure that you are actually able to relicense the whole thing - you'll be fine as long as you haven't copied in source files from other projects. [21:53] * mars wonders if it's just an anachronism [21:53] this is all original owrk that i ahve done [21:54] wgrant: thsi is all original work for this proejct [21:54] mars: Are you sure it didn't just stay there from when the code was proprietary? [21:54] thewrath: That's fine then. [21:54] so what is int he pastebin is all i have to do then wgrant then change hte licence under details for my project on launchpad correct [21:54] beuno: I'm currently running at 1024x768 due to a broken laptop LCD, and some things in the header wrap. [21:54] when does maintenace begin in est [21:54] thewrath: To the best of my knowledge, yes. [21:55] I believe it's around one hour until the start of the downtime window. [21:55] ok [21:55] was the to the best of my knowledge, yes to which quesiton [21:55] my frist question or second question at 16:54? [21:55] where can i upload my source files to host at? [21:56] thewrath: The first question. [21:56] thewrath: If you have a code branch, you can push it to Launchpad. [21:56] If you have released files, you can also push it to Launchpad. [21:56] But I have to go and have breakfast now. [21:56]