#foswiki 2014-08-26,Tue

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
gac410It's tough anyway. My ardunio & RPi are rather languishing right now. [00:00]
pharvey1RiskReward: I use the sparkfun eagle libraries, they've often drawn parts or footprints the standard library lacks
also they have nifty IDC header footprints which are deliberately wonky so that the pins bind up in the board, useful for locking the connectors in place by simple hole misalignment prior to soldering :)
[00:01]
RiskRewardThat's right. I forgot you mentioned you were laying out a new board the other day. [00:02]
pharvey1it helps that eagle files are basically xml [00:03]
RiskRewardI see. I do a lot of 3D CAD in SolidWorks. Sounds like it's not well suited. [00:04]
pharvey1I've used git to track TRIN wiki's (80GB? ) foswiki /pub before
it's not for the feint of heart
you can tell git to stop bother trying to find common parts of binaries/tracking diffs, etc. Under this config you end up with a new blob for every revision of an object in such a repo
http://foswiki.org/Support/BestPracticeTip29
hmm, that's where I tried to document configuring a git repo to hold binary blobs without completely bringing down your server hosting said git repo
[00:05]
RiskRewardVery nice.
Looks like the dabling in Git started well before last week's move from Subversion.
[00:09]
pharvey1the main magic is pack.depth, core.compression, core.loosecompression, pack.compression
Yeah, I wouldn't recommend this setup unless you were really trying to break to a large foswiki site all day long :)
It was quite useful to quickly reproduce the production servers onto a dev machine, run some possibly destructive stuff, then reset and try again.
[00:10]
RiskRewardYeah, can see that. I think it's quicker to break and fix offline than make small safer steps online.
Guess I'll start small and build up.
[00:12]
pharvey1I never had a reason to hate systemd, but it just doesn't support keyfile param in crypttab
heh, I mean keyscript
[00:18]
......................... (idle for 2h0mn)
RiskRewardBTW, I gave up on the in-topic changes to the table, and settled on a change in the CSS. The line is:
.foswikiTable,.foswikiTable td,.foswikiTable th {
border-color:#000
}
It's a little severe for the whole site, but too bad I guess.
[02:22]
..................... (idle for 1h41mn)
***ChanServ sets mode: +o pharvey
ChanServ sets mode: +o pharvey
[04:03]
.................. (idle for 1h27mn)
ChanServ sets mode: +o CDot [05:31]
....... (idle for 31mn)
ChanServ sets mode: +o MichaelDaum [06:02]
.... (idle for 15mn)
GithubBot[distro] MichaelDaum pushed 1 new commit to master: http://git.io/lwIxtg
distro/master 7c5c390 MichaelDaum: Item11267: be local-perl friendly...
[06:17]
***GithubBot has left [06:17]
.................................................. (idle for 4h6mn)
ChanServ sets mode: +o pharvey [10:23]
............................ (idle for 2h17mn)
SvenDowideitmmm, http://foswiki.org/Development/HowToStartExtensionDevelopmentInGit feels a little wrong to me
it git clones github/foswiki/distro (which becomes origin
but doesn't go on to get the user to make a fork on github so that they then can make PR's
the more normal GH workflow is to make a fork, clone it then add the main repo as upstream
though lots of people are going the other way - checking out the main repo as origin, and then adding their GH fork as a separate remote
SvenDowideit follows along tho :)
[12:40]
........ (idle for 36mn)
MichaelDaumSvenDowideit, hey
well for non-core developers that would be normal (fork and file a pull request)
core developers just push to the foswiki/distro
[13:20]
SvenDowideity, thats what i was thinking too
thought is often better to have core devs also PR
so that there's a review cycle for everyone
[13:21]
MichaelDaumwhat is PR? [13:21]
SvenDowideitpull request :) [13:21]
MichaelDaumtoo much red tape
branches are fine for dev cycles
[13:22]
SvenDowideitSvenDowideit shrugs [13:23]
MichaelDaumforking too much hurts collaboration [13:24]
.............................. (idle for 2h29mn)
***ChanServ sets mode: +o gac410 [15:53]
gac410Hit & run today. ...
If updated Dev docs feel wrong Pls update. They are early drafts / first attempts.
Maybe we need "track" documents: Ext dev, Core dev, "CoreDevelopers"
Gotta run. Bye
[15:54]
....... (idle for 33mn)
CDot(14:26:26) MichaelDaum: forking too much hurts collaboration - +1 to that. [16:31]
.... (idle for 15mn)
MichaelDaum:) [16:46]
......................................... (idle for 3h24mn)
TarboxI've got an interaction here I'm not sure how to report. I had an outgoing editor who would make pages using something like <ul><li>%TWISTY{whatever}% stuff to twisty %ENDTWISTY%</li><li>more stuff, usually more twisties</li></ul> which worked great, because she always edited markup directly. Now the new editors want to use the wysiwyg, and it's converting the <li> to " * %TWISTY{}%" and this breaks the twisty.
I want that to be a problem. Is that a problem? With twisties, with the wysiwyg, with lists in general? Is there a workaround?
[20:10]
..................................... (idle for 3h0mn)
***ChanServ sets mode: +o pharvey [23:11]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)