<houkime>
on the north side where the buttons are, in the east-north region near the camera button
<houkime>
looks like ir stuff should be placed on the bottom surface like the buttons?
<houkime>
metacollin populated this region already, so need to think what to do.
<houkime>
on the pcb right now there's no clear markup for a window so need to calculate and draw it myself somehow
jonwil has quit [Quit: ChatZilla 0.9.93 [SeaMonkey 2.49.3/20180412182658]]
<houkime>
On case scans the chamber can be seen
<houkime>
ok, so just need to use existing transforms (good thing i made them).
<houkime>
however there're 2 more potential problems I noticed with the bottom sim card.
<houkime>
or 1... well, 1 for sure
<houkime>
the thing is that as i mentioned you can't protect all sim pins with one esd thing
crox has quit [Ping timeout: 240 seconds]
<houkime>
because for bottom sim they are in the different parts of the component (huge component)
<houkime>
and the problem that I've noticed now is that this sim is immovable, and there's actually no space under the modem to place esd for some sim pins.
<houkime>
and you also can't do this on another layer because of the modem
<houkime>
I now have a file with a list of layout issues in my branch.
<houkime>
Would be nice if they could be tracked
<houkime>
that would be quite easy to do using sth like self-hosted gitea instead of gitolite.
<houkime>
atk: what was the reasons behind choosing gitolite for repos?
<houkime>
*reason
illwieckz_ has joined #neo900
illwieckz has quit [Ping timeout: 256 seconds]
<houkime>
ir chamber placed
<houkime>
but IR issues are real.
<houkime>
it is conflicting with metacollin's placement of audio codec
<houkime>
and tbh i barely see now how to manage LOWER east wich needs to accomodate 2 sims and elaborate audio stuff.
<houkime>
and ir
<houkime>
and probably still have sth else.
<houkime>
ok. nap.
houkime has quit [Ping timeout: 264 seconds]
him-cesjf has quit [Quit: Quit]
jcarpenter2 has joined #neo900
knttl has quit [Ping timeout: 248 seconds]
knttl has joined #neo900
jabawok_ has joined #neo900
jabawok__ has quit [Ping timeout: 276 seconds]
him-cesjf has joined #neo900
jonsger has joined #neo900
jabawok_ has quit [Ping timeout: 260 seconds]
jabawok_ has joined #neo900
jabawok__ has joined #neo900
jabawok_ has quit [Ping timeout: 264 seconds]
jabawok_ has joined #neo900
jonsger has quit [Ping timeout: 260 seconds]
jabawok__ has quit [Ping timeout: 245 seconds]
threebar has joined #neo900
him-cesjf has quit [Remote host closed the connection]
him-cesjf has joined #neo900
xes has quit [Quit: bye..]
xes has joined #neo900
xes_ has joined #neo900
himcesjf_ has joined #neo900
him-cesjf has quit [Ping timeout: 240 seconds]
himcesjf_ is now known as him-cesjf
Kabouik_ has joined #neo900
Kabouik_ has quit [Remote host closed the connection]
Kabouik_ has joined #neo900
houkime has joined #neo900
him-cesjf has quit [Ping timeout: 256 seconds]
<houkime>
hmm... now that'm thinking about it... Let me try and write a simple tool to decide which parts go where.
<houkime>
because otherwise that could be quite troublesome.
illwieckz_ has quit [Ping timeout: 264 seconds]
houkime_ has joined #neo900
houkime has quit [Ping timeout: 260 seconds]
houkime_ is now known as houkime
him-cesjf has joined #neo900
houkime_ has joined #neo900
him-cesjf has quit [Ping timeout: 268 seconds]
houkime has quit [Ping timeout: 260 seconds]
chomwitt has joined #neo900
jonwil has joined #neo900
Kabouik_ has quit [Remote host closed the connection]
xes_ has quit [Quit: bye..]
xes_ has joined #neo900
xes_ has quit [Client Quit]
Chris_ has joined #neo900
_Chris_ has quit [Ping timeout: 268 seconds]
jkepler has joined #neo900
jkepler has quit [Ping timeout: 245 seconds]
jonwil has quit [Quit: ChatZilla 0.9.93 [SeaMonkey 2.49.3/20180412182658]]
jkepler has joined #neo900
him-cesjf has joined #neo900
Pali has joined #neo900
Kabouik has quit [Remote host closed the connection]
jkepler has quit [Ping timeout: 248 seconds]
jonsger has joined #neo900
jkepler has joined #neo900
chomwitt has quit [Ping timeout: 260 seconds]
<atk>
houkime_: I wasn't there to make a decision to use gitolite so I have no idea
houkime_ is now known as houkime
<atk>
Personally I'm not a great fan of it, it seems to add an unnecessary level of complexity
<houkime>
ok
<atk>
But that can be said about a lot of everything, people love unnecessary complexity for some reason.
<Joerg-Neo900>
don't get me started or I find -name .git -exec 'rm -rf {};'
<Joerg-Neo900>
afaik gitolite was needed for ublog
<atk>
er
<atk>
well, I can't confirm or deny that
<atk>
anyway
<Joerg-Neo900>
yeah, better stop providing my arguments why git is terrible
<Joerg-Neo900>
not a git lover here :-)
<Joerg-Neo900>
also I've seen that "if only we'd us Y instead of X tool, everythign would be a thousand times simpler" way too often meanwhile, with always devastating results
<Joerg-Neo900>
right now there's no manpower available to do basic maintenance on server, no way we gonna change anything in it
* Joerg-Neo900
idly checks if any urgent updates are pending
<atk>
Joerg-Neo900: gitolite is not git
<atk>
I have no problems with git personally
<Joerg-Neo900>
ooh great, then let's delete it immediately
<atk>
But I write lots of C
<atk>
Deleting it would mean replacing it and although replacing it would be quite easy, I don't currently want to screw around with that considering all the effort involved.
<atk>
I've had a really long stressful week
<Joerg-Neo900>
you said it's not git so I implied we don't need it, so why replace it then?
<Joerg-Neo900>
also I'm pretty sure it IS git
<enyc>
/join #maemo
<enyc>
'oops
<Joerg-Neo900>
Gitolite is an access control layer on top of git, which allows access control
<Joerg-Neo900>
down to the branch level, including specifying who can and cannot rewind a given
<Joerg-Neo900>
branch.
<houkime>
well, in our case it is a piece of software that makes us a remote.
<houkime>
and maybe fine-grain control justifies its usage
<houkime>
although i'm not sure it can't be achieved via other means.
<houkime>
my point was just that it is not really convenient for issue tracking
<houkime>
do we have means of issue tracking?
<houkime>
(also it impedes wide-community collaboration on an open part of files because interface)
<Joerg-Neo900>
shall I rm -rf / ?
<Joerg-Neo900>
there IS NO MANPOWER for taking care about such stuff
<houkime>
enyc: You asked what should we call a help for? ok, we need extra admin so that finally we can collaborate ok.
<Joerg-Neo900>
you first need to find somebody to collaborate with
<Joerg-Neo900>
this project was about collabpration for several years, that's why we got git and eeshow and whatnot
<Joerg-Neo900>
and, as already stated: [2018-06-08 Fri 19:31:37] <Joerg-Neo900> also I've seen that "if only we'd us Y instead of X tool, everythign would be a thousand times simpler" way too often meanwhile, with always devastating results
<Joerg-Neo900>
we had/have trello, gilab, wiki, microblog, a half a dozen others that I even forgot the names. Nothing of all that saved more time than wasted to set it up and try make everybody use it
<Joerg-Neo900>
Slack
<Joerg-Neo900>
slack via irc gateway, I wonder what's the purpose of THAT been, compared to plain irc
illwieckz has joined #neo900
joel_ has joined #neo900
jkepler has quit [Ping timeout: 256 seconds]
joel_ has quit [Ping timeout: 260 seconds]
jonsger has quit [Quit: jonsger]
<Joerg-Neo900>
sorry for soundfing grumpy, probably the 30h of tar-in my 2GB HDD and trying to prepare for system-upgrade did their damage on my nerves, in cooperation with the electrohammers they used to remove all plaster from my house's outer walls today, all day long, plus the dust that caused on a 30°C day
<houkime>
could you make a post on maemo-forums regarding lack of manpower?
joel_ has joined #neo900
<houkime>
it now sounds like "everything is ok, we're working and don't need help" which is not really the case at least anymore.
joel_ has quit [Ping timeout: 245 seconds]
<Joerg-Neo900>
it's way beyond the "we need help" state
<Joerg-Neo900>
it's in the "do it yourself or nothing gets done" state since start of year already
<houkime>
yes, I have seen this. Writing a more clear and apparent version in one minute.
ArturShaik has quit [Ping timeout: 248 seconds]
<atk>
Joerg-Neo900: gitolite is a control layer on top of git, and the thing to replace would be solving how houkime gets access to the repo
<atk>
Joerg-Neo900: it wouldn't be too hard to make it so the repo is read-only to him and just give him a unix account where he can host his own private repo
<atk>
but working out how to safely pull out gitolite requires learning more about gitolite
<atk>
although the simple solution would be to: git clone all repos
<atk>
remove gitolite
<atk>
put repos back
<atk>
at this point in time though, everything is sorted out and working, the tape has been stuck down now and things are staying together
<atk>
I'd rather not start tugging on the tape on a friday evening when I have a headache
<Joerg-Neo900>
the fuck, gitolite is there for a reason, and I don't see why houkime has a problem with git
<atk>
gitolite is there for a poorly construed reason at this point afaict, the thing it is implementing could have been done with much less hassle with some unix permissions
<Joerg-Neo900>
I spent over 76% of server admin time with fixing git issues, usually after somebody "fixed" things
<atk>
if you were on the server fixing git issues it was probably gitolite
<atk>
but I imagine most of the issues would have been introduced by incorrectly manually configuring gitolite when gitolite was configured to use a configuration repo
<Joerg-Neo900>
guess what? I hated git to start with, so do you really think this shit would be there if not absolutely needed?
<atk>
I see all sorts of things in my line of work writing software, people come up with all sorts of well meaning reasons to do things which aren't actually necessary.
<houkime>
guys, please calm down. nobody calls for immediate measures.
<Joerg-Neo900>
when somebody doesn't like the server and git on it works, clone it
<Joerg-Neo900>
I mean, it's git
<Joerg-Neo900>
strange thing: it worked (with quirks) for the project since... 4 years
<atk>
well yes, I'm not saying it doesn't work
<Joerg-Neo900>
I don't see how our tasks changed so massively so we can't cope with them with what's thre, anymore
<atk>
but from my point of view, when it falls upon me to fix things, it's made harder when there are things set up which don't appear to be necessary and which are misconfigured or barely working
<atk>
I'm not sure what houkime doesn't like about how gitolite is configured, he was asking me why it was being used, I just gave my perspective on the situation.
<Joerg-Neo900>
you're free to set up an alternative server
<atk>
Right now for all I care it all works well enough for now.
<atk>
It's just that if I was going to do it all from the beginning then I would make things a lot less complicated.
<Joerg-Neo900>
prolly until you get the idea that our website must be in git too, publicly available (for WHATEVER reason o.O), and that our website shall be based on pelican since pelican has a microblog
<Joerg-Neo900>
then you *might* come to the conclusion that gitolite is necessary
<atk>
no, all of this can be done without gitolite
<Joerg-Neo900>
TBH I don't give a fart. It took me 4 years to learn basics about this stuff, despite I never wanted to touch any git
* enyc
burps
<atk>
the only reason gitolite would be useful is if you had a complex structured hierarchy of developers working on a shared project and want to avoid people stepping on each other's toes
<atk>
here we have one layouter working on a project with one reviewer and the only requirement is that the layouter can't write to the main repo and that the layouter has git repo space on the server
<atk>
none of that requires gitolite
<Joerg-Neo900>
like ... a websote that is read-only on git for public, but a ee repo that is private with a mirror that is public but read-only and has some footprints and layout filtered?
<atk>
well the filtering isn't done by gitolite currently, making things private doesn't require gitolite, it's just a cgit config option (which gitolite happens to control which just makes gitolite a layer of indirection) and the read-only-to-public aspect of it is just the default, making things writable by the public is the hard part
<Joerg-Neo900>
you have no idrea how I +HATE* discussing this shit
<atk>
Well I have some idea :P
<Joerg-Neo900>
another 10 minutes and I quit the server at hetzner
<Joerg-Neo900>
hed up with it
<Joerg-Neo900>
fed up even
<Joerg-Neo900>
I don't see the sane rationale in me fighting a burnout, delaying a 6 months hospital treatment, to discuss *G*I*T* >:-(((
<atk>
there's no reason for you to discuss it, you should get your break, I was just answering houkime's question, there was no complaints being made to you personally about how things are set up
<houkime>
take a break, Joerg.
jonwil has joined #neo900
drrty has joined #neo900
<knttl>
it's probably a good time to remeber that by and large, we all want the project to be successfull.
him-cesjf has quit [Quit: Quit]
Kabouik has joined #neo900
him-cesjf has joined #neo900
jonwil has quit [Quit: ChatZilla 0.9.93 [SeaMonkey 2.49.3/20180412182658]]
<houkime>
here, I made a preview of what a status report and planning thing should PROBABLY look like.
<houkime>
atk, the problem is that if you give me a repo on a server it will be not really comfortable for people to contribute
<houkime>
unless you have gogs or gite or sth pleasant
<houkime>
*gitea
<atk>
Personally I would use email patches because I like them a lot more than the alternatives but if you want something "user friendly" then I guess other options would be better
<atk>
the main problem with gitlab is that it makes PRs even worse than github
<houkime>
notabug then?
<houkime>
used it?
<atk>
If I needed something "user friendly" though, github would be my first choice, although the stability of that platform is unsure so far
<atk>
I don't use anything but email patches anymore and sometimes I am forced to use github or gitlab
<atk>
so I don't know what notabug is like
<houkime>
notabug is gogs-based
<houkime>
sec
<atk>
no idea what gogs is like
<atk>
but I saw some pictures and it looked like github
<atk>
if the PR system works EXACTLY like github then that would be great, because as much as I hate github PRs gitlab made me appreciate just how much effort they went to when making PRs actually work for people who like email patches
<atk>
can I push --force new changes to a PR branch and have it handle it correctly
<atk>
also can gogs operate at a diminished-features mode when JS is disabled?
<atk>
those are basically two important factors for me personally, two things which gitlab severely lacks
<houkime>
never tried doing that. Can try though
<atk>
specifically: make a PR, comment on some of the changes, locally amend the commit and push --force, the interface should detect that the comments were made against old changes and should mark them as such and the interface should gracefully handle the push --force
<atk>
without LOTS of random weird glitches and/or complete failure
<atk>
but in the end, you don't have to cater specifically for me, it's your choice
<houkime>
looks like it works without java ok
<houkime>
prints a warning on the top of the screen and the only thing not working seems to be a "preview" button
<houkime>
animations are replaced by instant things and that's it.