Perl 6 - the future is here, just unevenly distributed

IRC log for #pdl, 2015-07-17

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
08:14 mohawk sivoais, ok
08:14 mohawk so where are we with any fixes and status for a next release?
08:16 mohawk i am very keen for us to gain a mentality of "release early, release often"
08:17 mohawk especially in not holding everything up for just one thing, so long as the rest of the codebase is no worse than it was before
08:17 mohawk we have got to get to continuous delivery
08:17 mohawk "stop everything, i don't like the font on the release notice"
11:15 sivoais mohawk: I agree, but we can't do that until we have buy-in from everyone.
11:15 sivoais chm: when you're available, we can discuss this
11:15 sivoais and then bring it up on the list
11:32 sivoais we still have the unmerged commits from pre-2.012 to handle and my tests rewrite
14:33 estrabd joined #pdl
19:59 sivoais btw, SF has been down for a couple days
20:00 vicash they're probably installing malware on the remaining projects
20:01 jberger SF has been down for a couple DAYS?!
20:02 jberger shows how irrelevant they have become
20:05 jberger good thing we have a mirror (primary?)
20:43 sivoais Once we begin the split, it would be best to move to GitHub for the code entirely. It's much easier there.
20:44 sivoais The PDL wiki is already there. And soon testing of builds will be much better -> faster turnover between releases
20:44 sivoais and less work for development
20:47 sivoais The same thing is happening with all the projects that used to be on Google Code
20:47 sivoais even the code created by Google engineers
21:03 sivoais The reason why SF is down is because of a "storage platform bug"
21:03 sivoais <https://twitter.com/sourceforge/status/622146013969649664>
21:05 vicash there is a way to back up all the git repos using the "git clone --mirror" command.
21:05 vicash Maybe the maintainer of PDL should also push the github stuff to Bitbucket .. just to be safe in case Github starts Sourceforging itself
21:05 jberger and don't forget this completely unacceptable behavior
21:05 jberger http://arstechnica.com/information-technology/2015/05/sourceforge-grabs-gimp-for-windows-account-wraps-installer-in-bundle-pushing-adware/
21:06 jberger vicash: I'm not sure I trust atlassian any more than I trust github
21:06 vicash yes but both will most likely not screw up together
21:07 jberger that said, atlassian certainly has more revenue streams already so perhaps they won't need to monitize bitbucket
21:07 vicash in any case, doing the git mirror on even your local server will be beneficial. i backup my github repos on my personal server as mirrors so that in case Github goes down, I have a backup on my local server that I can host myself
21:09 jberger what does --mirror do that a typical clone does not?
21:09 jberger all branches perhaps?
21:09 vicash yes but a clone checks out the master or a certain branch
21:10 vicash a mirror replicates the complete repo from which you can then clone further
21:10 vicash you cannot clone from a clone
21:10 vicash you can only branch from a clone
21:10 jberger ah. I didn't know that
21:11 vicash yea, so the way I backup is this. Let's say my repo "vic" needs backing up. There is a vic.mirror directory which has the files from a git clone --mirror, and then i have a "vic.local" directory that clones from the "vic.mirror" directory to verify that cloning/pull/fetch works.
21:11 vicash all of this is in a script that runs once a day for all my repos on github
21:22 sivoais hmm, I can do that with ingy's git-hub
21:22 sivoais $ (echo zmughal; git hub orgs -r) | xargs -n1 git hub repos -a -r # | xargs -n1 -I{} git clone --mirror git@github.com:{}.git {}
21:22 sivoais um, get rid of the # in the middle ;-)
21:25 vicash sivoais: sure you can... my point is that despite Github being primary, there should also be a cold backup on say PDL's personal server for unlikely scenarios
21:26 sivoais definitely
21:26 sivoais I'll make my own mirror soon
21:28 jberger I thought that the whole point of a distributed VCS was that any clone could be used to rebuild history in case of disaster, is this not completely true (working branches aside)
21:28 jberger ?
21:28 sivoais jberger: oh, it is still true
21:28 sivoais it's just that using --mirror just gets you a bare repo
21:28 sivoais which you can clone directly instead of having to point to the /.git/ directory
21:29 jberger ah, now that makes more sense
21:29 vicash yea it allows for hosting a git repo

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary