[MAGEEC] BEEBS website.

[James Pallister]

Hi Andrew,

>   * Breadboarded PIC32MX250F128B (with PICKIT2 as a programmer)
>   * SAM4L Xplained
>   * XMEGA-A3BU Xplained Pro
>   * MSP-EXP439F5529LP LaunchPad
>
These platforms aren't currently supported but will be in the near
future (the configs need to be rewritten with the restructuring of
BEEBS). If we'd like to keep these on there, I can try and add back the
support for them early next week - it looks good to support a wide range
of platforms.

> The opening paragraph should explicitly mention that beebs came out of
> MAGEEC.
It did however exist before MAGEEC - there are commits going back to Aug
2012. Though, the majority of benchmarks and work on it has been done as
part of MAGEEC.


Cheers,
James

On 04/09/14 11:11, Jeremy Bennett wrote:
> On 04/09/14 11:04, Andrew Back wrote:
>> Hi All,
>>
>> We now have a simple GitHub Pages-based website for BEEBS:
>>
>>   http://mageec.github.io/beebs/
>>
>> This will also be accessible via beebs.eu as soon as the DNS is updated.
>>
>> Questions:
>>
>> * Can you spot any error or omissions?
> "View on GitHub" should be "View Source on GitHub"
>
> The opening paragraph should explicitly mention that beebs came out of
> MAGEEC.
>
> Add a hyperlink for the GitHub Issue Tracker where it is mentioned at
> the bottom.
>
>> * Would it benefit from a graph or table with sample data?
>> * Do we want a GitHub Wiki, or shall we just stick with the page on mageec.org?
> I'm keen that we separate BEEBS from MAGEEC. This also means we need to
> create a BEEBS mailing list. Eventually I'd like it to have its own
> organization on GitHub.
>
>> * Should we have a Team section?
> Yes - good to give credit where it is due.
>
>> I'd like to get any updates made before the weekend, so if you have
>> any suggestions if you could let me know ASAP!
> HTH,
>
>
> Jeremy
>
>> Regards,
>>
>> Andrew
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mageec.org/pipermail/mageec/attachments/20140904/7cfc8c80/attachment.html>