[srawn] SR(A)WN 2015 -- 12

[Tom Leese]

SR(A)WN 2015 — 12

This is the twelfth issue of the Student Robotics (Almost) Weekly Newsletter, a (roughly) fortnightly newsletter which summarises the goings‐on across Student Robotics. Emboldened items are ones which we believe could do with extra hands. An absence of emboldening does not necessarily mean that everything is done.

Internal Updates:

• Multiple tech days happened, with some interesting results—no teams turned up at Southampton. Attendance has started to be recorded as a result of this.
• Student Robotics was shown off at Southampton to prospective students.
• An update on the charity situation was posted. The charity application has been submitted and there has been a large objection to this, leading to two committee members announcing that they will resign.
• Team QMC were given a new power board.
• Numerous purchasing tickets were closed. [^0]
• Work on the tools continues and should be ready for public testing shortly.
• Some of the camera documentation has been discovered to be wrong.
• Duplicate asset codes were discovered in the inventory.
• A decision on how to proceed in terms of product searching in the tools has yet to be made.
• An update on team account creation was posted.
• An issue in the power board relating to I2C has been fixed.
• Output current reading measurements have been taken.
• An update to the rules fixing references to SR2014 has been uploaded.

Team Updates:

• HRS have been experiencing problems with the current limit on the power board.
• HRS may have a problem with their camera. They discovered that they could not take photos at certain resolutions.
• CLY have been getting a mysterious beeping noise.

Thanks to Tom Leese, Tyler Ward and Alistair Lynn for working on this issue. The previous issue can be foundhere.

[^0] See tickets closed on 6th December in the timeline.

[Peter Law]

Hi,

The embedded links in this edition render very pale for me (to the
point of being hard to read) -- could we try a more vivid colour in
future please?

Peter

> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Student Robotics" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to srobo+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Tom Leese]

Hi Peter,

On 18/12/14 18:03, Peter Law wrote:
> The embedded links in this edition render very pale for me (to the
> point of being hard to read) -- could we try a more vivid colour in
> future please?

You're right, it appears the tool[0] I use to convert the Markdown to
HTML (and then copy into Google Groups) has recently been updated and
the links are now coloured. I'll look into a replacement for next time,
perhaps using Pandoc or something with a small script—the process of
releasing a SRAWN is fairly manual at the moment.

Tom

[0]: http://dillinger.io/

[Peter Law]

Tom wrote:
> I'll look into a replacement for next time, perhaps using

> Pandoc or something with a small script--the process of releasing a SRAWN is

> fairly manual at the moment.

Here's an insane idea:
* We add an optional external parser to [lib]fritter (configured to be markdown)
* We create a new srobo.org/git/srawn.git repo
* Submissions to that repo get some review etc. then get sent on to the list

Thoughts?

Peter

On 18 December 2014 at 18:07, Tom Leese <in...@tomleese.me.uk> wrote:
> Hi Peter,
>
> On 18/12/14 18:03, Peter Law wrote:
>>
>> The embedded links in this edition render very pale for me (to the
>> point of being hard to read) -- could we try a more vivid colour in
>> future please?
>
>
> You're right, it appears the tool[0] I use to convert the Markdown to HTML
> (and then copy into Google Groups) has recently been updated and the links
> are now coloured. I'll look into a replacement for next time, perhaps using

> Pandoc or something with a small script--the process of releasing a SRAWN is

> fairly manual at the moment.
>
> Tom
>
> [0]: http://dillinger.io/
>
>

[Tom Leese]

Hi Peter,

On 18/12/14 18:23, Peter Law wrote:
> * We add an optional external parser to [lib]fritter (configured to be markdown)

Sounds like a good idea.

> * We create a new srobo.org/git/srawn.git repo

Definitely agree with this, even if we don't go for automated email
sending. I've actually got a local Git repo where I've been keeping the
raw SRAWNs that I've contributed to with the intention of becoming a Git
repo on Saffron. I simply haven't got round to getting the remote repo
created to push them.

> * Submissions to that repo get some review etc. then get sent on to the list

This sounds fine. Generally we write a SRAWN with a load of people on a
Firepad, so the Gerrit review process will probably be more of a
formality than anything else.

Basically agree with this idea, should make SRAWN easier to maintain and
possibly even get some non-Southampton-doing-goers contributing.

Tom

[Peter Law]

Hi,

I wrote:
> Here's an insane idea:
> * We add an optional external parser to [lib]fritter (configured to be markdown)
> * We create a new srobo.org/git/srawn.git repo
> * Submissions to that repo get some review etc. then get sent on to the list

I should note that I don't have time to look at this any time soon,
but I'll happily review patches & provide guidance if anyone else
would like to poke it.

Peter