| Eickmeyer | OvenWerks, eylul: Just caught up. In my company, we have all of the passwords on a Google Drive account with a password we all share, but that's less than ideal for our situation. So, whatever solution you found using LP, you might have to explain it to me. | 04:14 |
|---|---|---|
| Eickmeyer | Unfortunately, I'm probably not going to get the meeting notes out until tomorrow since my brain doesn't seem to want to really function properly, and I have to get up early tomorrow anyways, so it's probably for the best that I'm tired.. | 04:15 |
| OvenWerks | Eickmeyer: https://code.launchpad.net/~ubuntustudio-core/+junk/ubuntustudio-core | 04:16 |
| OvenWerks | just a test. but anyone who is a part of ubuntustudio-core should be able to read it. | 04:16 |
| Eickmeyer | Yeah, I see that. Looks like it has to be done in bzr? | 04:16 |
| OvenWerks | I don't know I didn't even try git yet :) | 04:17 |
| Eickmeyer | Oh, haha! | 04:17 |
| OvenWerks | for just a few plain files... idon't see what difference it makes really. | 04:18 |
| Eickmeyer | I don't either. I'm okay using bzr, git, mercurial, or whatever. Actually, no. No mercurial. I'm not a masochist. XD | 04:19 |
| Eickmeyer | Either way, that seems to be a decent solution so long as nobody outside of core can see it. | 04:21 |
| OvenWerks | https://code.launchpad.net/~ubuntustudio-core/+git/ubuntustudio-core | 04:22 |
| OvenWerks | Eickmeyer: git works too | 04:23 |
| Eickmeyer | \o/ | 04:23 |
| Eickmeyer | Only thing I can see there is that bzr and git don't mix, so we should settle on one or the other, and my vote would be for git since it seems to be, for lack of a better term, "the way of the future." | 04:24 |
| OvenWerks | I don't know if you want to make it a "project" or not | 04:24 |
| Eickmeyer | Nah, doesn't need to be a project. | 04:24 |
| OvenWerks | not may be more secure... | 04:24 |
| Eickmeyer | Exactly. | 04:24 |
| OvenWerks | bzr has vanished | 04:25 |
| OvenWerks | err, the bzr branch above has vanished :P | 04:26 |
| Eickmeyer | Oh! Well, then that solves that! | 04:27 |
| * Eickmeyer needs to send eylul instructions on git on LP | 04:27 | |
| OvenWerks | Eickmeyer: I don't know if we should have all in one file or one file for each... "whatever" | 04:28 |
| Eickmeyer | I don't see any reason not to have it all in one file. Git is smart enough to figure out differences. | 04:28 |
| OvenWerks | I was thinking about being able to send one file to someone who only needs one. | 04:29 |
| OvenWerks | That is not having to change all the info if someone goes away who can't be trusted. | 04:29 |
| Eickmeyer | Ohhh... right. | 04:31 |
| Eickmeyer | Multiple files wouldn't be that much work either. | 04:32 |
| OvenWerks | Anyway, the repo is there do whatever :) | 04:33 |
| * OvenWerks figures he has done his part :) | 04:33 | |
| Eickmeyer | Thanks! That was something eylul was wondering last week, and it's nice to see the solution was under our noses. | 04:38 |
| Eickmeyer | Now we just need to figure out the dang web hosting issue. | 04:38 |
| eylul | Eickmeyer: OvenWerks i just said git over bzr for long term planning as we are transitioning to git overall it seems, and it is one less tool to keep track of/learn. In short term I don't care either. :) | 09:54 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!