tessel / project Goto Github PK
View Code? Open in Web Editor NEWThe open source Tessel Project. Start here!
Home Page: https://tessel.io/
The open source Tessel Project. Start here!
Home Page: https://tessel.io/
Moderator: @johnnyman727
Notes: @Frijol
@johnnyman727 can you comment with a video link?
Submitting for discussion:
Publicizing the existence of the Tessel Project as an organization.
Tasks
Open questions
Content of outgoing email
Non-essential
Needs to be discussed and a plan made
This issue is for tracking T2 features which must be completed before ship. Discuss below what should/shouldn't be on this list.
I'm not including t2 status
, t2 ap
, or t2 root
command because, although they are super awesome features, they aren't absolutely critical to shipping.
Moderator: @rwaldron
Notes: @tcr
t2-cli
integration into cli
We should discuss this point.
@johnnyman727 would you submit a PR upgrading yourself from moderator to SC status?
@Frijol do you agree with this nomination?
Tessel 2 is seeking FCC approval. Tessel 2 runs OpenWRT, a distribution of Linux designed as open firmware for routers with very granular control over wireless capabilities. Currently Tessel 2 is stuck in FCC approval pending its demonstration of being able to generate packets in the 802.11n range.
Installation on a Tessel 2:
opkg update
opkg install tcpdump
wget https://kevinmehall.net/tmp/packetspammer -O /usr/bin/packetspammer
chmod +x /usr/bin/packetspammer
To configure monitor on wlan0 (this goes away on each reset):
ifconfig wlan0 down
iw dev wlan0 interface add mon0 type monitor
ifconfig mon0 up
iw mon0 set channel 11
To set which transmit mode you want:
iw mon0 set bitrates legacy-2.4 1 2 11 # b
iw mon0 set bitrates legacy-2.4 6 12 24 # g
iw dev mon0 set bitrates ht-mcs-2.4 4 10 # n
# to reset these values:
iw mon0 set bitrates legacy-2.4
iw dev mon0 set bitrates ht-mcs-2.4
Lastly run the packetspammer
command, and see if the resulting output is being transmitted at a speed that correlates with the given spec:
packetspammer -d40000 mon0
Output may resemble:
1818:20:58.209712 1.0 Mb/s 2462 MHz 11b -38dB signal [bit 29] 0us 13:22:33:44:55:66
(oui Unknown) Unknown SSAP 0x60 > 13:22:33:44:55:66
(oui Unknown) Unknown DSAP 0x50 Unnumbered, ua, Flags [Response], length 72
Note the "1.0 Mb/s" indicating the output speed (1.0 Mb/s, 802.11g)
We observe that in spite of the iw dev mon0 set bitrates ht-mcs-2.4 4 10
command, Tessel 2 always transmits at b or g rates.
Possible diagnoses:
iw
documentation (slightly outdated): https://wireless.wiki.kernel.org/en/users/documentation/iwWe own the following email accounts:
As well as these shell accounts:
Zoho Mail has 10+ free users for one custom domain. From here on out, we should change all technical.io emails to tessel.io.
I propose we have a branding/assets/logo repository with all the the iconography that we have locally on Dropbox.
Anything directly pertinent to our trademark would go in this repository, but would not be the definitive source for imagery.
Tools we will be using to collaborate:
Open questions:
This will take about five minutes to accomplish.
Having a bot that corrects incorrect mentions is harder. Currently looking if there's any pre-existing demos of this.
The README for this project currently indicates some steps for people to collaborate and submit code. As we grow closer to when Tessel 2 ships, we should be ramping up avenues for involvement as much as possible.
We specced out a PR policy that ensures pull requests are attributed to their original author, but are augmented with any appropriate changes or fixes that should be done before they are merged into master.
This ensures attributing credit where it is due, but also giving examples of improving code quality in the future.
All of our modules are in Diptrace format, which is not a useful or open format.
There have been some attempts to convert these to Kicad, which should be completed / automated.
Our naming on Tessel project repositories is inconsistent. Here's a proposal:
(No longer included:)
We should maintain a list of infrastructure resources owned by the tessel project.
I'm moderating; I believe @rwaldron is taking notes. Should have the full team in attendance!
For discussion:
Following up on the other issue about resources, we have a bunch of social media accounts we should transfer to this org.
We should codify what the intent of each is for.
I propose
I would like to propose some rework of the mission statement:
Create a fully open source hardware & software platform that makes it easy and intuitive to develop connected devices. The Tessel platform will lead the way for an open web of hardware.
The main problem with this is that sentence number 2 is not a mission, it's a possible result. Further, I want to look up some literature around good mission statements / philosophies so we can spot check if ours measure up.
We have put a bunch of work into ensuring we use only open source tools. Do we have a stated commitment for what our work in open source tools should be? Is this a group we're interested in spinning up?
For instance, all of our modules listed on our open source page are in Diptrace. A while back I dallied in trying to convert them to Kicad projects, with some success.
We currently have a test rig with files in OnShape, which is a non-free project. It seems like FreeCAD is the best open alternative (very debatably). Should we make sure we are exporting to free tools?
We currently have all our logos in Illustrator files. Should those always be offered in free analogs?
Checking up on last week's action items:
@jonmckay: talk to Dylan, guy in charge of Dojo re: consent by contribution and avoiding a CLA
Jon: generate a list of tasks for onboarding
Jon: blog post about the background of RFCs
Jon: blog post about the new people and what they're bringing them to the team and they're excited about it and they're cool and everyone's happy
jon: ask Dylan about funding and how we pay
jon: rfc blog post cite rick
jon: next week meeting invite
@kelsey: Get in touch with people re licensing presentations
Kelsey: onboarding discussion
kelsey + tim : merge backers and twit lists on mailchimp
Tim: Send Jon a list of tasks for onboarding (cc Jon)
Tim: Add consent by contribution component.
@rwaldron: look over PRs for unit tests
@channel: look at, review, contribute to t2-start
Any new business?
Is collaboration on in-depth tasks (debugging, design, or community) best accomplished using the tools we have? Some combination of our channels:
For collaborating and development, we've historically used Zulip, which is not public.
We mention RFCs in the guidelines. I seek input on these items:
I propose tessel/licenses to document what licensing we usually go for (and encourage discussion if that's ever an issue). We should also link to appropriate documentation and describe what LICENSE-MIT LICENSE-ASL2 files should exist in properly-licensed repos.
Open questions:
Related to many of the ideas in #15 (Current guide)
The Steering Committee and contribution guide links are giving me 404s on this page:https://github.com/tessel/project/blob/master/TEAM.md
which is linked from here: https://tessel.io/about
Facilitator: @johnnyman727 Notes: @Frijol
The existing moderator guide is wholly software focused.
This document should better define the powers and responsibilities of a Moderator: not just repo commit power, but also moderator access on forums, what power a Moderator has in hardware developments, and what the expected responsibilities are for each of these areas.
I can work on some guidelines for community moderation. @ekolker can you outline how you would expect hardware discussion & design decisions to work?
Moderator: @tcr
Notetaker: @johnnyman727
What's going on with that?
Currently we have many legacy servers from Technical Machine. These should be trimmed down for the Tessel Project.
@HarleyKwyn put together this list of servers we are currently using:
Purpose | Provider | host-name | monthly cost |
---|---|---|---|
storefront | digital ocean | shop.tessel.io | $5 |
rampart | digital ocean | rampart.tessel.io | $5 |
whiplash | digital ocean | ??? | $5 |
projects portal | digital ocean | projects.tessel.io | $5 |
forums | digital ocean | forums.tessel.io | $20 |
tessel.io | heroku | technical-io. | $34.50 |
start.tessel.io | heroku | start.tessel.io | $20.00 |
stage | heroku | techinical-io-stage.tessel.io | $0 |
n/a | $80 | ||
total | $174.50 |
Goals:
Purpose | Provider | host-name | monthly cost |
---|---|---|---|
tessel.io | digital ocean | tessel.io | $20.00 |
rampart | rampart.tessel.io | ^^^ | |
start.tessel.io | start.tessel.io | ^^^ | |
stage | stage.tessel.io | ^^^ | |
forums | digital ocean | forums.tessel.io | $20 |
fastmail | n/a | ~$10 ($15/year per user) | |
total | $50 |
Sunsetting:
Purpose | Provider | host-name | monthly cost |
---|---|---|---|
storefront | digital ocean | shop.tessel.io | redirect |
whiplash | digital ocean | ??? | offline |
projects portal | digital ocean | projects.tessel.io | offline |
We need to automatically assign collaborators to issues on Tessel repos. Apparently the rust-lang group has open sourced the code they use to do that.
Since most of our web content is now static, we should consider open sourcing the website (even if it remains a dynamic website).
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.