added software platforms file#7
Conversation
anton-firmware
left a comment
anton-firmware
left a comment
There was a problem hiding this comment.
just a few things :)
| * general general discussion not competition related | ||
| * meetings discussion on upcoming meetings | ||
| * getting-involved How to get involved with SourceBots organisation / development | ||
| * sb-2018 organisation for the 2018 competition |
There was a problem hiding this comment.
might be worth changing this to "sb-20xx" where xx finishes the year... it means we won't have to change this every time
| Github is the main storage location for our version controlled code. | ||
| It also provides issue tracking for the included repositories. | ||
|
|
||
| The SourceBots Github organisation can be found at https://github.com/sourcebots |
| Trello can be accessed at https://trello.com/smallpeice2016 | ||
|
|
||
|
|
||
| ## Github |
|
|
||
| ## Github | ||
|
|
||
| Github is the main storage location for our version controlled code. |
|
|
||
| ## Google Docs | ||
|
|
||
| The google docs folder is used to store information that cannot or should not be stored publicly. |
| ## Trello | ||
|
|
||
| Trello is mainly used for strategic planning. | ||
| Trello tasks will refer to things such as milestones on Github issues or other similar objectives, components of features, issues and bugs should be in the components issue tracker rather than Trello. |
| * soton discussion for Southampton specific things | ||
|
|
||
| ## Trello | ||
|
|
There was a problem hiding this comment.
Might it be worth noting that Trello tasks are assigned to people ?
There was a problem hiding this comment.
Trello tasks arent often assigned to people. Unless there's specific knowledge or access, theyre unassigned, so people can pick them up when they wish
| Sign up at https://sourcebots.slack.com | ||
|
|
||
| #### Some Notable channels | ||
| * general general discussion not competition related |
There was a problem hiding this comment.
I'd be interested in exploring setting these to links to the room URLs directly. Also, it might look nicer prefixed with a hash, although i'm not sure if markdown will format those incorrectly?
There was a problem hiding this comment.
Either way, room names need some kind of emphasis or seperation from their descriptions
There was a problem hiding this comment.
I quite like formatting slack room names like this: #general
There was a problem hiding this comment.
The hash prefix and hyperlink is nice, however does make the content noisy. Perhaps just bold and hash for now will do, and a shortcode helper later down the line might be nice!
trickeydan
left a comment
trickeydan
left a comment
There was a problem hiding this comment.
None of these links are screen-reader friendly. It would be good if these could be changed.
|
|
||
| Sign up at https://sourcebots.slack.com | ||
|
|
||
| #### Some Notable channels |
There was a problem hiding this comment.
Would this be better solved by making the "notable" channels the defaults for new people on slack? That avoids the need to keep two places in sync (both in terms of what the list is and the documentation of each element).
| sourcebots.co.uk | ||
|
|
||
| #organisations | ||
| Github |
There was a problem hiding this comment.
GitHub style their name with a capital H, which we should probably stick with.
|
|
||
| #organisations | ||
| Github | ||
| Trello |
There was a problem hiding this comment.
Isn't Google a common enough word to be picked up by spell checkers?
There was a problem hiding this comment.
If the spell checker doesn't complain about it, we can assume so!
5 participants
No description provided.