User:BBurd
(→Barry Burd) |
(→Barry Burd) |
||
| Line 9: | Line 9: | ||
Dr. Burd is an avid indoor enthusiast. In his spare time, he enjoys sleeping, eating, and talking. | Dr. Burd is an avid indoor enthusiast. In his spare time, he enjoys sleeping, eating, and talking. | ||
| − | + | === Notes from POSSE assignments === | |
== Sugar Labs notes== | == Sugar Labs notes== | ||
Revision as of 01:07, 16 October 2017
Contents |
Barry Burd
Professor of Mathematics and Computer Science at Drew University in Madison, NJ.
Author of Java For Dummies and other books in the For Dummies series.
Leader of the 2017 ITiCSE working group on IoT in Computer Science education.
Dr. Burd is an avid indoor enthusiast. In his spare time, he enjoys sleeping, eating, and talking.
Notes from POSSE assignments
Sugar Labs notes
Roles for participation are Educator, Content Writer, People Person, Developer, Designer, and Translator. Ideally, I'd like my students to be developers. Some of them could be translators because my university has many international students. Some students would fit best in the role of Designer, but I'm not the designer type, so I wouldn't be very useful as a mentor for them in that role.
To submit a bug for Sugar Labs, (1) Find the correct respository (with /sugarlabs/sugar being the default), (2) look for the Issues tab and click the New Issue button, (3) Write a note about the issue. The respositories for issues include, the default (sugar), the toolkit (gtk3), docs, artwork, sugarlabs, and build. I'm not absolutely sure, but I think the difference between "sugar" and "sugarlabs" is as follows: sugar is about the Sugar shell itself; sugarlabs is about the project's web site. Am I correct?
In the Sugar repository, the most recent commit (d3660ac) was 9 days ago (as of today, Oct 14, 2017).
Roadmap and release cycle: The roadmap is the plan for development, which includes release dates, freeze points, lists of module dependencies, and other items. (The Sugar roadmap page is currently empty.) The release cycle is the timing of releases. Each release includes development, beta, release candidate, and the final release.
Sahana Eden notes
Roles for participation are Developer, Tester, Bug Marshal, Newsletter Report Writer, Documentor, Translator, Designer, SysAdmin and GIS Specialist. Developer, designer, and translator are also in the Sugar Labs project. Now I'm noticing that Sugar labs doesn't have Tester, which would seem to be an important role. Sahana is heavy on testing because, in addition to Tester, Sahana also has a Bug Marshal role. In Sahana, there's also a distinction between Documentor and Newsletter Report writer. Interesting! Sugar Labs has an Educator role and Sahana doesn't but Sahana has this Newsletter Writer.
Superficial observation: Sugar uses Git for listing its issues; Sahana seems to use a page of its own devising. Another observation (probably also superficial) is that the Sahana report page is tree-shaped - with summaries at the root branching out to individual issues. The Sugar Labs page is flat so it has only the issues themselves.
Sahana Active Tickets page includes 141 tickets. They're grouped into major, minor and trivial. They're also classified as enhancement, defect/bug, documentation, and task. Information for each issue also includes a Summary, which component is involved, version (trunk or test) the issue's owner (very important), the issue's status and the date when the issue was created. Drilling down into an issue, I see a description of the issue with actual result versus expected result, attachments and a change history.
On the Sahana repository page, the most recent commit was today (October 15). It's coded d9f2502.
Ouch! The roadmap page says Milestone 0.9.0 is 6 years late! Features are listed for Milestones 1.0 and 2.0 but no dates have been set for those milestones.
