<DocScrutinizer05>
yes, that's pretty much to the point, Nikolaus just neglecting that he uses his own proprietary macintosh-only router with eagle
<DocScrutinizer05>
and he been *very* reluctant so far to pick up on any schematics or layout work somebody else (here: me) had been doing for the Neo900
<DocScrutinizer05>
so when I start working on Neo900 layout myself, this seems to imply I need to do *all* layout until production then
<ravelo>
hmm
<ravelo>
looks for me like he can continue afterwards
<ravelo>
after he has finished current work
<DocScrutinizer05>
for the update-web-frontpage issue, I already asked hellekin to take care of that, a week ago
<ravelo>
i don't understand "macintosh-only router"
<DocScrutinizer05>
Nikolaus wrote an own router for eagle which is supposedly needed to do layout of such complexity with eagle. That router is Nikolaus' property and only works on macintosh
<ravelo>
ah, did not see next line "eagle"
<ravelo>
did you ask him if he could setup a multiuser pc and give you remote access?
<ravelo>
or is this not possible?
<ravelo>
ah, ok.
<DocScrutinizer05>
I did ask him for such stuff before and he outright rejected granting *any* access to his infra
<ravelo>
he does not offer you his proprietary eagle router?
<ravelo>
software?
<DocScrutinizer05>
he says it's not ready for getting "published" - whatever that means
<ravelo>
hmmm, ok. i can somehow imagine
<ravelo>
what he means
<DocScrutinizer05>
and it runs only on macOS
<DocScrutinizer05>
I have no mac and no eagle for mac
<Arch-TK>
We all know what that means.
<Arch-TK>
It's a work of genius but even he doesn't know how it works after he wrote it.
<DocScrutinizer05>
hehe
<ravelo>
hmmm, this is not so much of a problem. this is the easiest part to solve i think
<ravelo>
(mac)
<ravelo>
hehe Arch-TK
<DocScrutinizer05>
yes, more or less
<amatus>
more like he doesn't want to write any documentation or teach anyone how to use it, including how to avoid all the bugs
<DocScrutinizer05>
but using a software that's not "ready for publishing" also means there's no tutorial at all about how to use it
<ravelo>
actually the biggest problem could be your last statement before, that he does not pick up your work later
<ravelo>
looks like
<DocScrutinizer05>
amatus: 2 guys 1 tought
<DocScrutinizer05>
ravelo: yes this is exactly the core problem
<ravelo>
yes, that's the problem with a software that's only for his individual use
<ravelo>
Then you have mainly two options:
<ravelo>
in the first place:
<DocScrutinizer05>
I mean, proto_v2 layout is really "simple" compared to what comes next after that
<ravelo>
Decide if Nikolaus will finish it or someone else
<DocScrutinizer05>
...or have a company holiday of 6 months and get a job meanwhile :-)
<ravelo>
I would not recommend that "someone else" is you, as it looks like you cannot do the full work
<ravelo>
till the end
<ravelo>
yes
<ravelo>
if you decide that Nikolaus should do it, then you have to wait 6 months
<DocScrutinizer05>
no, I'm not experienced at this task, so me doing the whole layout introduces huge risk to the project
fling- has quit [Ping timeout: 260 seconds]
<ravelo>
yes
<ravelo>
so at least you do not have to think about the software anymore, only about "who", right? :)
<DocScrutinizer05>
I mean, I possibly could *learn* to do it, but if that's any faster and cheaper than waiting for Nikolaus is really another question
<DocScrutinizer05>
for now I'm thinking about proto_v2 and that we need that pretty fast
<ravelo>
yes, I thought so too
<DocScrutinizer05>
and I prolly could do proto_v2 layout
<DocScrutinizer05>
though I'm not 100% sure
<ravelo>
actually you could do a quick and dirty proto_v2 layout
<DocScrutinizer05>
that's the plan
<ravelo>
and then do it again by a professional company?
<ravelo>
s
<ravelo>
inclusive finish the project?
<DocScrutinizer05>
proto_v2 been defined as quick&dirty layout
<ravelo>
or: if you decide to do proto_v2 yourself, then no other company can jump in and finish?
<DocScrutinizer05>
since beginning
<ravelo>
ok, i have another idea: you finish proto_v2 fast and make a prototype
<DocScrutinizer05>
I think other company _could_ jump in and finish, since proto_v3 and final are only partially based on proto_v2 layout
<ravelo>
in the mean time Nikolaus has enough time (hopefully)
<DocScrutinizer05>
you know we got no SoC in proto_v2 and the UPPEr PCB is of arbitrary size and shape
<ravelo>
then Nikolaus jumps in and starts from scratch, so he does not base his next work on yours
<ravelo>
you might lose some time later but can do now the necessary next steps
<ravelo>
*now*
<DocScrutinizer05>
sounds like a plan, exactly what since maybe a week I'm inclined to do
<ravelo>
as this is only "quick and dirty" you could even outsource this if you notice it takes you too much time in the next weeks
<DocScrutinizer05>
actually I guess that's our best option, however I need to find a moment with optimistic mood to ask Nikolaus for a warranty that he will pick up again later
<ravelo>
it looks for me that not much time is lost if he is allowed to not base later work on yours
<DocScrutinizer05>
currently I'm pretty depressed from all the mess of last 6 months and the zombie state the project is in right now thanks to the layout issue
<ravelo>
as this does not look like a complicated step
<ravelo>
DocScrutinizer05: I understand this
<DocScrutinizer05>
yes
<ravelo>
For me it looks a bit easier now as I thought before
<DocScrutinizer05>
plus I suffer health issues from that 9 months of overload with shit
<DocScrutinizer05>
If I'd listen to my doctor, the project would get suspended for 6 months no matter what
<ravelo>
hm
<DocScrutinizer05>
I never listen to my doctor ;-)
<ravelo>
if it's a good doctor you should
<ravelo>
...
<DocScrutinizer05>
well, he's ok, and he's prolly right that I can't recover from an overload while still continuing to do same health abuse
<DocScrutinizer05>
I tried with 3 weeks holiday in December, which helped only partially and for maybe 2 weeks
<ravelo>
hmmm
<wpwrak>
DocScrutinizer05: regarding nik, perhaps you could outline that plan to him, and ask him how you'd have to work to avoid introducing unnecessary incompatibilities in your output. so that, in 6 months or whatever, when he _may_ want to _consider_ doing the next layout, there wouldn't be unnecessary obstacles
<ravelo>
for the next small step proto_v2 for me it looks like it's best to simply do it, best is if you find a company doing it quickly
<ravelo>
as this is a very small step technically
<ravelo>
so it looks to me
<DocScrutinizer05>
wpwrak: yes, that's the plan. Alas you know my recent productivity at writing emails
<wpwrak>
sounds like a nice easter holiday project ;-) (nik will probably be afk anyway)
<Arch-TK>
6 months.
<Arch-TK>
crikey, it sounds like this project is approaching a 1 year delay.
<Arch-TK>
And all because of paypal.
<wpwrak>
beautiful domino effect, yes :(
<Arch-TK>
well, hopefully no more slowdowns happen along the way.
<Arch-TK>
This gap also presents plenty of time to do fundraising.
<Arch-TK>
About this fundraising, where did that end up?
<DocScrutinizer05>
at proto_v2 needed urgently to show of something tangible
<DocScrutinizer05>
off, even
<DocScrutinizer05>
after that start kickstarter or whatever and then I can get another offtime
<DocScrutinizer05>
or maybe not, as usual
ravelo has quit [Ping timeout: 250 seconds]
vakkov has quit [Ping timeout: 248 seconds]
opa-ben has quit [Quit: Leaving.]
tomeff has quit [Ping timeout: 244 seconds]
tomeff has joined #neo900
vakkov has joined #neo900
raoulzecat has joined #neo900
tomeff has quit [Quit: tomeff]
pagurus has quit [Read error: Connection reset by peer]
<hellekin>
Meanwhile on #devuan:
<hellekin>
14:28 < Pali> hm.... devuan on n900?
<hellekin>
14:35 < parazyd> yup
jonsger1 has joined #neo900
jonsger1 has quit [Remote host closed the connection]