Edu Project Team
direkitteh
holtr94
NumbuhFour
milistisia2
Jules of Nature

No title available

pixel skylines

tannertan36
DEAR READER
Aqua Utopia|海の底で記憶を紡ぐ

Love Begins
wallacepolsom
Cosmic Funnies
2025 on Tumblr: Trends That Defined the Year
Sweet Seals For You, Always
Today's Document
noise dept.
I'd rather be in outer space 🛸
occasionally subtle

Kiana Khansmith
Mike Driver
we're not kids anymore.

oozey mess
he wasn't even looking at me and he found me

seen from United Kingdom

seen from Netherlands
seen from United Kingdom
seen from Egypt

seen from Dominican Republic
seen from United States
seen from Malaysia
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States

seen from United States
seen from United States

seen from United States
seen from United States

seen from United States
seen from United States
seen from United States
@direkitteh-blog
Edu Project Team
direkitteh
holtr94
NumbuhFour
milistisia2
PhoneGap & Synapp
PhoneGap is a handy tool for getting your website things into an app! It also happens to be open source. Here’s their github!
For my New Media Team Project class, my group is using PhoneGap for things. Their github is here.
Problems with Milestones
If you’re not a collaborator, you cannot make issues to associate your milestones with.
Team Proposal - Education
List your other team members below:
direkitteh -- [email protected]
milistisia2 -- [email protected]
NumbuhFour -- [email protected]
holtr94 -- [email protected]
Which project did your team choose?
Mini Game Mayhem
2-liner description of the project?
An application similar to Luminosity with a collection of math-themed games to teach various topics of the fourth grade curriculum. Users receive scores for their performance and can improve over time.
What will each team member's role be?
Each member will be the lead developer for one mini game. All members will also assist others on their mini games as needed.
Source Code Repository URL?
Github: https://github.com/milistisia2/MiniGameMayhem
Sugar labs build: https://github.com/sugarlabs/sugar-build
Sugarizer: https://github.com/llaske/Sugarizer
List your upstream Mentors below:
To be determined
How will you communicate with them? (i.e. IRC Channel, Email Addresss, mail lists, issue trackers, etc...)
IRC channel (irc://irc.freenode.net#sugar)
private message over IRC
Email sugar-devel mail list ([email protected])
What are the easy parts?
Adjusting to sugar lab development environment
Getting in contact with sugar lab developers
Testing
What are the hard parts?
Creating multiple small, fun games that teach concepts
Getting everything done in six weeks
Avoiding adding too many features that will make it too much work to complete, while still keeping it interesting
How will you overcome both?
We have already begun a document to begin coming up with concepts to teach different sections of our chosen topic (math). As for keeping the scope small, we will solidify our ideas as early on as possible (hopefully within the first week after spring break). From there, we will not make any major changes to our game design, and focus solely on creating it and testing it.
Commarch - Printrun
WORK IN PROGRESS - for now see RedTwo’s here
IRC: reprap
github: https://github.com/kliment/Printrun
documentation: https://github.com/kliment/Printrun/blob/master/README.md
other communication channels: http://reprap.org/wiki/Printrun
project website: http://www.pronterface.com/
THE PROJECT
HISTORY Patches approved by:
Commit access:
Total people with patches:
Total commits: Highest unique knowledge: Calloway Coefficient of Fail: 15
+5 for not announcing releases on mailing list
+10 for no mailing list
Core team turnover: No. BDFL/Lead Dev: Front end vs back end: J. What have been some of the major bugs/problems/issues that have arisen during development? Who is responsible for quality control and bug repair? K. How is the project's participation trending and why? L. In your opinion, does the project pass "The Raptor Test?" (i.e. Would the project survive if the BDFL, or most active contributor were eaten by a Velociraptor?) Why or why not? M. In your opinion, would the project survive if the core team, or most active 20% of contributors, were hit by a bus? Why or why not? N. Does the project have an official "on-boarding" process in place? (new contributor guides, quickstarts, communication leads who focus specifically on newbies, etc...) O. Does the project have Documentation available? Is it extensive? Does it include code examples? P. If you were going to contribute to this project, but ran into trouble or hit blockers, who would you contact, and how? Q. Based on these answers, how would you describe the decision making structure/process of this group? Is it hierarchical, consensus building, ruled by a small group, barely contained chaos, or ruled by a single or pair of individuals? R. Is this the kind of structure you would enjoy working in? Why, or why not?
Teaching 4th Graders to Math
ref: http://hfoss-fossrit.rhcloud.com/static/decks/MA-0111-grade4only.pdf
What seems interesting:
Number and Operations in Base Ten (4.NBT - 1-6)
teaching place value (to 1,000,000) (4.NBT-1)
estimation
rounding (4.NBT-3)
properties of operations (distributive property)
Number and Operations - Fractions (4.NF - 1-7)
comparison (4.NF- 1-2)
addition
subtraction
multiplication (4.NF-4)
fractions to decimals (4.NF - 5-6)
comparing decimals (4.NF-7)
Measurement and Data (4.MD)
measurement conversion (larger -> smaller) (4.MD-1)
represent and interpret data (4.MD-2?)
What seems super not interesting:
"Operations and Algebraic Thinking” (4.0A - 1-5)
geometry as a whole (4.G)
measuring angles
unit fractions (4.NF-3)
Possible Mechanics:
match measurement estimates with objects (rel:4.MD, 4.NBT-1)
building blocks (like legos) (rel:4.NF - 1-4)
speed/trivia games
simplify as many fractions as you can before 3 hit the bottom of the screen (4.NF-1)
estimate the number of places for the product of two multi-digit numbers (4.NBT-4)
within 60 seconds, choose the larger number in pairs of two measurements (sometimes in different units) as many times as possible (4.MD - 1-2)
How to Present Commarch
DOs
use images (logos, etc)
code examples, screen shots
give overview of software
DON'Ts
also white on black, smart alecs.
BONUS
Gource (as in multigource)
Logstalgia - not really for this, but it's cool
Commarch Team Proposal
Team Members:
William Russell -- RedTwo -- war9646 Laura Durant -- direkitteh -- [email protected] Robert Holt -- holtr94 -- rgh7614 Chosen Project:
Printrun
Project Description
Printrun is a 3D printing host software suite based in python. It is an open project licensed under the GNU General Public License, version 3.
Project Link
pronterface.com
Our Roles
Each member of the team will develop content for the analysis and presentation. Communication
Amongst ourselves, we will use irc, email, and phones to communicate where needed. To talk with pronterface developers, we will use irc on #reprap and on github at Kliment/printrun.
The Easy Part
It is a a small enough project that git-by-a-bus should have no problem parsing it. Answering the questions should be simple and communicating with the dev team should be straight forward.
The Hard Part
Meeting with team members, and keeping open lines of communication.
Overcoming Them
Stay aware of communication avenues, and work in advance instead of putting off work until it is due.
2048 - A small clone of 1024 (https://play.google.com/store/apps/details?id=com.veewo.a1024)
To do: fix one of these bugs, because 2048 is my addiction.
Friendship is HFOSS
direkitteh, holtr94, and RedTwo UNITE!
It's mostly because we sit in a line in class. It'll be cool.
My Little Laptop
Smoke testing went pretty well on the OLPC/XO/whatever laptop. The interface is a little confusing to get around sometimes, though. Also, my little guy icon has stopped producing a useful menu - it just brings up a black rectangle, which you can still click on to do things. It just doesn't let you know what you're clicking on, which is unhelpful. I will see if the problem persists.
P.S. his name is gir.
The Open Source Way
"In Chapter 3 of Stephen Weber's The Success of Open Source, there was a listing of eight 'General Principles' contained within the chapter. Last week, we discussed in class the five pillars of 'The Open Source Way.'"
1. What are the titles of each Pillar?
open exchange
participation
rapid prototyping
meritocracy
community
2. What are the titles of each General Principle?
make it interesting and make sure it happens
scratch an itch
minimize how many times you have to reinvent the wheel
solve problems through parallel work processes whenever possible
leverage the law of large numbers
document what you do
release early and release often
talk a lot
3. What are the similarities between Weber's eight principles, and the five pillars?
emphasis on interaction within communities of developers and users
open exchange, participation, and community
minimize how many times you have to reinvent the wheel, leverage the law of large numbers, and talk a lot
do things well and document them
meritocracy
minimize how many times you have to reinvent the wheel, solve problems through parallel work processes whenever possible, document what you do
fast, iterative process
rapid prototyping
solve problems through parallel work processes whenever possible, release early and release often
4. What are the differences?
the pillars do not emphasize getting people interested in your project
nothing comparable to "make it interesting and make sure it happens" or "scratch an itch"
the principles are much more specific than the pillars, which are more general (ironically, despite the principles being called "general")
the pillars focus on ideas while the principles focus more on execution
5. Whose "keen analysis" did Weber "Draw Heavily" upon?
Eric Raymond
6. What was the title of this "keen analysis?"
How To Become A Hacker
7. Where can this keen analysis be found?
http://www.catb.org/esr/faqs/hacker-howto.html
Steve Weber's "What Is Open Source and How Does It Work?"
[this chapter]
published: Nov 30, 2005
TL;DR: Open source got its big start when Linux became a big deal at the turn of the century. Open source does cool things for the programming world by bringing tons of people together under projects. Voluntary collaboration and loose hierarchies allow progress in a way conventional structures can't achieve.
Takeaways:
(learned) Linus Torvalds was too poor to afford Unix, so instead he got Minix, and then he built an open-source version of that called Linux. It became kiiind of a big deal, so much so that even the mainstream people started paying attention after a few years. That's a pretty cool story to kick off an educational chapter.
(question) I wonder if the Unix or Minix people had an issue with Torvalds making his software free. It seems like they would want to complain about him stealing market share.
(bad) Weber uses the old, boring strategy of explaining exactly how he was going to write the actual meat of the chapter. Yawn. He then goes into analogies justifying how he's approaching it, and I just want to get to the actual information.
(good) Software is poetry! I love the analogy.
(bad) Weber doesn't actually talk about specifically open source software for a long time after initially stating his intention to give us a simple version and then expand on it. I feel like this is unnecessarily drawn out.
(question) Would it be possible to distill the essence of open source software without going so in-depth into the concepts of software itself?
(learned) Traditionally, more people make more problems by requiring more communication, but large projects need more people. Open source's answer to this? People volunteer to work on what they want to work on, so there's no division of labor at all!
(bad) As great as the content is, getting through reading it is tedious. There are occasional anecdotes and stories that make it interesting, but for the most part it feels like unnecessary amounts of explanation or justification.
(question) How would someone move up the open source hierarchy to more heavily influence a particular project or organization?
My Thoughts:
Weber conveys the purpose and implementation of open source software in an understandable way. However, his voice and approach to writing the chapter is unengaging. There are moments of intrigue when Weber lapses into story, but for the most part he takes a very standard, flat approach on writing. Overall, the chapter does its job conveying both the meaningful content intended and the boring academic environment where you can find students forced to read books and tryhards that want to look smarter than they are.
First Flight
Today I learned that mIRC has a $20 registration fee. HexChat does not. I also spent more time than I really should have needed to figuring out how to connect to a channel properly. Whoops.
Also, I tried to play around with tumblr's RSS feeds, and I still can't figure out how to get it to display more than 20 items. You would think something like tagging on "?count=50" or "?limit=50" to the end of the URL would get you more results, but it doesn't. Unfortunate, that. I guess I'll have to either figure out a way to increase the limit, confirm that 20 is fine, or switch to a different blog. Such is life.
Now I submitted my yaml file, and we'll see if it actually works. Here's hoping!
Downloading the github client and locating the "Clone in Desktop" button took the most time for this. I will learn to properly use the github shell at some point, but right now I got things done and that's what matters. Yay committing!
Of course, I didn't actually do it properly so I had to go in with command line to push and then go and do the pull request, but I didn't mess up too badly for my first time using things.
Hi, IRC
Me: /msg NickServ [REDACTED]
NickServ: [basically "your registration information has been emailed to you.]
Me: [verification information]
NickServ: direkitteh has now been verified.