issues
search
waterloop
/
waterloop-website-old
Official website of Waterloop
https://teamwaterloop.ca
7
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
EMB-3 Message protocol between devices and back-end
#40
nikolaevra
closed
6 years ago
0
If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-
#39
nikolaevra
closed
6 years ago
0
For team-internal issues, use TMAN-<# of your issues>
#38
nikolaevra
closed
6 years ago
0
If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-
#37
nikolaevra
closed
6 years ago
0
EMB-3 Message protocol between devices and back-end
#36
nikolaevra
closed
6 years ago
0
EMB-4 Memory management solution
#35
nikolaevra
closed
6 years ago
0
EMB-6 STL Integration
#34
nikolaevra
closed
6 years ago
0
EMB-9 USART implementation
#33
nikolaevra
closed
6 years ago
0
For embedded issues, use EMB-<# of your issue>
#32
nikolaevra
closed
6 years ago
0
For Backend issues, use BCK-<# of your issue>
#31
nikolaevra
closed
6 years ago
0
For team-website issues, use TWEB-<# of your issue>
#30
nikolaevra
closed
6 years ago
0
EMB-1 Memory friendly String Classes
#29
nikolaevra
closed
6 years ago
0
EMB-9 USART implementation
#28
nikolaevra
closed
6 years ago
0
TWEB-3 Learning creating 3js render of the pod
#27
nikolaevra
closed
6 years ago
0
If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-
#26
nikolaevra
closed
6 years ago
0
For team-manager issues, use TMAN-<# of your issue>
#25
nikolaevra
closed
6 years ago
0
For VR issues, use VR-<# of your issue>
#24
nikolaevra
closed
6 years ago
0
For team-website issues, use TWEB-<# of your issue>
#23
nikolaevra
closed
6 years ago
0
For Backend issues, use BCK-<# of your issue>
#22
nikolaevra
closed
6 years ago
0
For embedded issues, use EMB-<# of your issue>
#21
nikolaevra
closed
6 years ago
0
BCK-6 Receive and send packets in I2C in GO
#20
nikolaevra
closed
6 years ago
1
[Setup] Go dev environment with Story HTML template
#19
Mogball
closed
6 years ago
0
EMB-1 Memory friendly String Classes
#18
nikolaevra
closed
6 years ago
0
EMB-6 STL Integration
#17
nikolaevra
closed
6 years ago
0
Wlib Code style consistency
#16
nikolaevra
closed
6 years ago
1
EMB-4 Memory management solution
#15
nikolaevra
closed
6 years ago
0
EMB-3 Message protocol between devices and back-end
#14
nikolaevra
closed
6 years ago
1
TMAN-1 Internal website
#13
nikolaevra
closed
6 years ago
0
BCK-5 Writing a sample server in GO
#12
nikolaevra
closed
6 years ago
0
Write server in GO
#11
nikolaevra
closed
6 years ago
0
BCK-2 Blackbox data logging
#10
nikolaevra
closed
6 years ago
0
Create a communication standard (using bits)
#9
nikolaevra
closed
6 years ago
1
BCK-3 Server Heartbeat
#8
nikolaevra
closed
6 years ago
0
BCK-4 Watchdogs
#7
nikolaevra
closed
6 years ago
0
http://www.techbitar.com/how-to-network-many-arduinos-with-sensors-using-i2c.html
#6
nikolaevra
closed
6 years ago
0
TWEB-1 Design the wireframe for the website
#5
nikolaevra
closed
6 years ago
1
TWEB-2 Building main team website
#4
nikolaevra
closed
6 years ago
2
Blockchains
#3
nikolaevra
closed
6 years ago
1
BCK-1 Checksums of packets
#2
nikolaevra
closed
6 years ago
0
Switching to UDP
#1
nikolaevra
closed
6 years ago
4
Previous