| houkime | BTW neo900 can become the biggest pcb-related material source on peertube. | 00:10 |
|---|---|---|
| houkime | like, 10 videos and there will be a total media domination | 00:11 |
| houkime | there's only electube.nulled.network - a specialised instance, but it is a bit fragmented it seems and has almost no views | 00:13 |
| houkime | like, even my pcb tour is the most popular video with "pcb" in it | 00:14 |
| sicelo | :-) | 00:15 |
| houkime | the only problem is that Trending page is a bit broken now, because otherwise we might as well get into trends at some point | 00:30 |
| houkime | developers seem to be overwhelmed with issues as of now | 00:31 |
| houkime | btw I just thought - we miss a backer honorboard. | 00:34 |
| houkime | on the neo900.org | 00:34 |
| houkime | or at least in the repos somewhere. | 00:35 |
| houkime | Just looked at peertube's - they have quite a wall of names | 00:35 |
| houkime | ideally i might place it even on pcb itself | 00:37 |
| houkime | but i think it won't fit and will interfere with thechnical markup lines, and wrapping will be a pin | 00:38 |
| houkime | *pain | 00:38 |
| houkime | there is one more idea on this - one can include names into compoents references | 00:39 |
| houkime | this is quite hilarious | 00:39 |
| atk | houkime: how can you place 500 names on a pcb? | 00:40 |
| atk | or well | 00:40 |
| atk | it will end up being 800 names at this rate | 00:40 |
| houkime | I've seen similar stuff when gamers on youtube name characters and ingame stuff with backernames | 00:40 |
| pribib | a url? | 00:40 |
| houkime | url is ok, but a bit on a banal side. also not really useful if the address is long to type it | 00:43 |
| houkime | also from the filming view the reward effect will be stronger if i for example will call resistors by backernames out loud - like you, R15alsobacker, go here and connect | 00:47 |
| houkime | One just needs to leave the functional <PartLetter><SheetNumber>prefix untouched | 00:51 |
| atk | won't that affect the silkscreen? | 00:53 |
| houkime | hmmm... rechecked pcb real quick | 00:57 |
| houkime | seems like it will, but only for large/rare parts | 00:58 |
| houkime | it will affect fab layer however | 00:58 |
| houkime | fab layer is virtual though. | 00:59 |
| houkime | idk what pcbhouse will say though | 01:00 |
| houkime | technically it shouldn't be a real problem, it's just about how much additional trouble one wants to have to honor backers | 01:02 |
| houkime | there should be at least one non-standard cool honoring i think. Project is very long and backers deserve sth cool. | 01:09 |
| houkime | *honoring method employed | 01:09 |
| houkime | also one can theoretically engrave a wall of names with laser to a back of a case | 01:11 |
| houkime | even from an inner side this will be nice | 01:11 |
| houkime | laser engraving is not sth superduper complex to do afaik | 01:12 |
| houkime | but this is more for an actual production stage. | 01:13 |
| houkime | if anything, one can have a script to temporary reverse component naming just for production | 01:17 |
| houkime | and they will be still there somewhere on the case and all over internet files | 01:18 |
| houkime | prbib: if url it probably needs to be a qr code | 01:32 |
| houkime | prbib: case engraving still feels more direct though | 01:34 |
| * chomwitt watched houkime's video on peertube | 01:47 | |
| houkime | chomwitt: any advice? | 01:50 |
| chomwitt | aloxa! | 01:50 |
| houkime | hi (probably... the hawaian word is quite ambiguous) | 01:53 |
| chomwitt | really? aloxa.. is ambiguous?? | 01:55 |
| houkime | as far as i remember it is both greeting and bye | 01:56 |
| chomwitt | didnt know that! | 01:56 |
| chomwitt | kudos for the video | 01:56 |
| houkime | next time will try to be more structurised and fastpaced since it was edited together anyway | 01:57 |
| houkime | there was also a problem that obs ate some split seconds from the end of fragments | 01:58 |
| chomwitt | i aggree that 'lowering the barriers' angle could give a little 'push' and love to the project | 02:01 |
| chomwitt | the main problem i think is there a point in time where sourcing the materials cant be done , so in that case the project is from the implementation side dead? | 02:02 |
| houkime | joerg has a photo with loads of N900 boxes in his archive so there's at least some buffer | 02:03 |
| houkime | i don't know how big though | 02:03 |
| chomwitt | souldnt there be in a project a 'virtual' responsible for that aspect, and shouldnt 'his' knowledge be public so even the roles of the project can be passed around like the kicad schmeatics or the code? | 02:03 |
| chomwitt | i think an open hardware project, to keep alive needs open roles. | 02:05 |
| houkime | Joerg-Neo900:good call^^^^^ | 02:05 |
| chomwitt | ? | 02:06 |
| houkime | it is just how irc works - to grab someone's particular attention you include his nick in the message | 02:07 |
| houkime | I quess now the responsibility and money affairs are on joerg | 02:08 |
| houkime | *currently | 02:08 |
| chomwitt | i see. | 02:09 |
| chomwitt | peertube.social stalls a little , but is cool! | 02:10 |
| chomwitt | one moment to see sth | 02:10 |
| houkime | atk does web administration, joerg is sort of CEO, wpwrak did a motherload with actual development of sch and tools | 02:10 |
| houkime | number of contributors did footprints | 02:10 |
| chomwitt | https://system76.com/about <-- i like that page.. | 02:10 |
| houkime | pseudoanimations are nice) | 02:11 |
| chomwitt | i mean it's a company and seems open to the world | 02:11 |
| chomwitt | in a way that makes you feel nice.. | 02:11 |
| chomwitt | it makes you feel conected.. cyberconnected... | 02:12 |
| chomwitt | and open hardware project could have an about page with virtual roles, and images of people in each role and links to 'data-sets' related to each virtual-role . | 02:13 |
| chomwitt | thats my share of little ideas | 02:15 |
| houkime | hmmm... so that any virtual role might even have a contribution guide attached? | 02:15 |
| chomwitt | i was thinking an org file with notes, agendas, code , everything | 02:17 |
| houkime | how about an org git repo then& | 02:17 |
| houkime | ? | 02:17 |
| chomwitt | we need a file that contains even bug reports, code repository , and that could be passed along in ease | 02:18 |
| chomwitt | cool! | 02:18 |
| chomwitt | org git seem nice for know | 02:18 |
| houkime | We sort of have the embryo of it. sec | 02:18 |
| houkime | https://notabug.org/Houkime/Neo900-Planning | 02:19 |
| houkime | pure org repo | 02:19 |
| houkime | it just has a readme for now though | 02:19 |
| houkime | but it can be many things there | 02:19 |
| chomwitt | so it should be written in the dna of any open hardware project , that there should be a http accessible about page with the virtual roles and each role should have a link to a role-status org file rested in a git repository | 02:20 |
| houkime | btw what do you mean by role-status exactly? | 02:21 |
| chomwitt | each virtual role i think should have a task to accomplish , for example sourcing the materials. So a material-sourcer-status file should contain the status of all the related efforts and the outcome of all the real-persons that helped in that virtual-role's job | 02:24 |
| chomwitt | so we need a wiki page for the project. and an about page which i think should follow the layout of the system76's about page but with virtual-images linking to each roles status-org file. | 02:25 |
| houkime | hmmm... this is interesting. | 02:26 |
| houkime | Joerg also wants a wiki btw | 02:26 |
| houkime | can you please structurize your plan into an issue to the planning repo and post it there so it isn't lost? | 02:28 |
| houkime | https://notabug.org/Houkime/Neo900-Planning | 02:28 |
| chomwitt | well, it make sense to me , all the related info of the current state of each sub-job accessible from one central page | 02:28 |
| chomwitt | that also is a 'barrier lowering' cog. | 02:28 |
| chomwitt | i'll try to do the 'post' in the planning repo | 02:30 |
| houkime | just submit an issue | 02:31 |
| houkime | it is as simple as on github | 02:31 |
| houkime | exactly the same | 02:31 |
| houkime | About helping out with wiki you can talk with atk or Joerg-Neo900 on that. there's a real need here. | 02:34 |
| houkime | the websit is open-source so about page is moddable | 02:34 |
| houkime | repo is here https://neo900.org/git/www/ | 02:35 |
| houkime | it is not as simple as fork+pr to contribute though(( | 02:35 |
| houkime | basically now if one wants to make a patch he should make a patchfile and send it with email to atk probably | 02:36 |
| houkime | this was a point of my criticism of current git repos on neo900.org a while ago. | 02:38 |
| chomwitt | it says its a pelican static site generator | 02:38 |
| chomwitt | in python | 02:39 |
| chomwitt | so there's no wiki functionality in the site now i think | 02:40 |
| chomwitt | is there a thread about that criticism the currend git repos? | 02:42 |
| houkime | I linked "www" repo regarding "about" page. Wiki for now was intended not really a part of website itself (like archwiki which is tied to the rest of the site with links) | 02:44 |
| houkime | no, no thread yet. i probably need to make one | 02:45 |
| houkime | it is somewhat displayed in the readme of the planning repo though | 02:45 |
| chomwitt | i've read the Neo900-planning page. | 02:51 |
| houkime | there's a mention of fork+pr workflow there which I actually added earlier today for consistency but that's it for now. It obviously should be a repo issue | 02:54 |
| chomwitt | in a way u have 3 virtual-roles by know: the hardware guy.. the pcb layouter , the system admin (little fyzzu his job.. thought) and the pr guy! | 02:54 |
| houkime | it is fuzzy because it is a flamy topic mainly and thus the constructive discussion is somewhat hindered | 02:55 |
| chomwitt | but i think we need also the 'hardware sourcing guy..' and the 'economical' | 02:56 |
| * chomwitt asked diaspora channel if i can embed a peertube.social video in a post | 02:57 | |
| houkime | there's a possibility that Joerg has talked about sourcing somewhere in his maemo talks but better ask about it when he is around. | 03:07 |
| houkime | i have no troubles listing his responsibilities in the repo though | 03:08 |
| houkime | with an actual status of sourcing | 03:09 |
| chomwitt | i have the feeling thats a highly sensible subject .... | 03:09 |
| houkime | i don't really think it is that much sensible. Like, it is for sure not personal (whereas git-related stuff sometimes suddenly gets) | 03:10 |
| houkime | It's just that I don't know much more than we have a significant amount of n900s to experiment with | 03:13 |
| houkime | and the joerg is not currently around to talk numbers | 03:13 |
| chomwitt | i sense thats there are fears that either should be met , discussed and solved or there would be more stagnation . | 03:19 |
| houkime | I think what we need is an economical report | 03:19 |
| houkime | like any normal open project | 03:19 |
| chomwitt | +1 on that | 03:20 |
| chomwitt | we should put that on the plan you initiated | 03:20 |
| chomwitt | but as i said where money is involved things could become litte bumpy.. | 03:21 |
| chomwitt | :-) | 03:21 |
| chomwitt | but as i also said ...fears not met and discussed will consume the life of it | 03:22 |
| houkime | yeeep... Money is a thing that separates people from openly available neo900 layout btw | 03:23 |
| * chomwitt thinks .. a philosopher could be also usefull ... | 03:23 | |
| chomwitt | :-) | 03:23 |
| chomwitt | i should take a look at sparkfun model by the way | 03:24 |
| houkime | there's a strange piece of logic that joerg uses to justify semi-closed state that includes chinese copycats making cheap stuff | 03:25 |
| houkime | howeer i myself see it as a little paranoidal for an esoteric device like neo900. | 03:25 |
| houkime | also here's the thing that i don't think backers would really object if neo900 chinese clones will get done ahead of vanilla one | 03:26 |
| chomwitt | well ... if there was a choice in a semi-closed approach i think by know its weaknesses and strengths should have been made visible. | 03:27 |
| chomwitt | even the general approach of a project should be under git !! :-) | 03:28 |
| houkime | well, you won't have trouble accessing the layout now, it just involves talks with people. | 03:29 |
| chomwitt | leaders of neo900 surrander your memory banks to the RMS deity for update and upgrade or behold of his wrath!!! :-) | 03:30 |
| houkime | whatever, make issues, talk with us in here and we will see where it can go. | 03:34 |
| chomwitt | anyway serious job has been done and trying to protect it is reasonable and fair i think.. but that counter to an open approach that could keep a project afloat like a phoenix :-) | 03:35 |
| houkime | I think that securiy measures right now are unreasonable for the project current state | 03:36 |
| chomwitt | the middle ground should be reassesed and find its weaknesses and fix them. | 03:36 |
| houkime | Not just this, but in general have more community-centric approach | 03:37 |
| houkime | that's a thing that I'm trying to fix right now | 03:38 |
| houkime | basically now the community should defeat joerg | 03:39 |
| houkime | )) | 03:39 |
| houkime | well at least that part of him that might impede progress | 03:41 |
| houkime | need to note though that many problems right now arise just because of small people count | 03:42 |
| houkime | where is no community in place - many bad decisions happen | 03:44 |
| houkime | Sparkfun is wonderful | 03:45 |
| houkime | they try to educate people, have nice general pcb howtos and videos. | 03:46 |
| houkime | Basically they try to solve the main problem if open hardware - people being afraid to dive in | 03:47 |
| houkime | sicelo: sorry, your comment somehow got marked as review needed | 03:51 |
| houkime | sicelo: I don't really know why since i remember making more liberal settings | 03:52 |
| houkime | sicelo: and I recheck them now and there're no filters or limitations. | 03:55 |
| houkime | sicelo: it seems like a youTube glitch | 03:56 |
| chomwitt | on the other hand .. dragonbox seems to be semi-closed but more near to its goal... that could be a counterargument to open up.. | 03:56 |
| houkime | chomwitt: it is more complex than that | 03:57 |
| houkime | the thing is that now neo900 is severely undermanned | 03:57 |
| chomwitt | isnt dragonbox semi-closed or even more closed? | 03:57 |
| houkime | chomwitt: closed source hits undermanned groups more | 03:59 |
| chomwitt | i see. valid argument i think | 03:59 |
| houkime | if we had a nice full core team we would have almost zero problems with semiclosed. However if one relies on community, or forced to rely on it, closing up is not a real option i think | 04:02 |
| chomwitt | but in an undermanned project the 'mans' left dont have the power to hold the world still if their fears are not solved and have put their personal work in it? | 04:02 |
| chomwitt | i mean if that project is semi-closed then there is ownership ...period. you cant open that someone feels he owns it. | 04:05 |
| chomwitt | and then u need also a layer with the power of great alexander to resolve knots. | 04:06 |
| chomwitt | who 'owns' what and that kind of stuff that could also stagnate a project | 04:07 |
| chomwitt | so here i am speaking with no fear!! i hope that helps .. :-) | 04:07 |
| houkime | thx | 04:09 |
| houkime | now i need to go sleep since biology | 04:09 |
| houkime | then we will discuss the future of the planning repo and stuff | 04:10 |
| chomwitt | ok. | 04:10 |
| chomwitt | see u! | 04:10 |
| houkime | back | 11:52 |
| ^7heo | I really wonder what the autoban picks on. | 14:16 |
| enyc | hrrm | 14:18 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!