Open ghost opened 4 years ago
On Wed, Apr 08, 2020 at 05:56:17AM -0700, Joe wrote:
Once we settle on a list of activities to work with from #2 and #3, each student will post here their initial 4 task choices, as per https://github.com/ritjoe/hfoss/wiki/final-choosing-activities-2
OK, #2 and #3 haven't yet drawn the full participation I'd hoped for, but in order to move on using the discussion we have had, I'm going to ask everyone to submit, in this issue, a filled out task choices table as found near the end of the URL above.
Copy and paste your table into your reply email or into the text box of the GitHub web interface, either way.
Please note that using the web interface you can preview your entry, which may prove particularly helpful with table formatting.
Also as an option I've noted in the page linked above the option of using Dillinger for writing and previewing the table.
I'm looking for 6 task choices in total: Your four top choices and then two alternates. I'd hoped we could narrow down our Python and JavaScript projects through #2 and #3 more fully by now but I'll try this method of trying to narrow down to a consensus set.
So, please, at your earliest convenience, let us see your choices here.
As an example, I'll use Yann's comment on issue #3 earlier:
https://github.com/ritjoe/sugarizer-lite/issues/3#issuecomment-611513730
I'd like to work on describing MazeWeb if possible.
@ymoullec | Project name | Language (py or js) | analyze? (X for yes) \<-- either | or --> develop? (X for yes) |
---|---|---|---|---|
Choice 1 | MazeWeb | Python | X | |
Choice 2 | ||||
Choice 3 | ||||
Choice 4 | ||||
Alt 1 | ||||
Alt 2 |
I notice there's no good way to see the raw text of ritjoe/hfoss/wiki so I've made sure to push the wiki to its parallel full-fledged github repo
https://github.com/ritjoe/hfoss-wiki/blob/master/final-choosing-activities-2.md
which does allow a raw view:
https://raw.githubusercontent.com/ritjoe/hfoss-wiki/master/final-choosing-activities-2.md
which should be useful as another example of the input format for a GitHub-Flavored Markdown table.
Alas, format fail. Some email software along the way may have munged that, probably by wrapping the lines.
No matter, we have the wiki here to use:
https://github.com/ritjoe/sugarizer-lite/wiki/example-task-choice
Add your own to the wiki, substituting your GitHub username for the word "example" in the page name
In other words, make these wiki pages, please
https://github.com/ritjoe/sugarizer-lite/wiki/cja1093-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/eza5640-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/zsd7200-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/zethra-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/BlueJay89-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/jrtechs-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/DennisSSDev-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/iggyvolz-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/ymoullec-task-choice https://github.com/ritjoe/sugarizer-lite/wiki/iclare-task-choice
Several of you have yet to accept the invitation to collaborate on sugarizer-lite. Please check your notification method (within the web interface, or your email inbox) for the invitation if you haven't accepted already.
Accepting the invitation to collaborate gives you significant ability to work within the ritjoe/sugarizer-lite repo through the web interface, push branches to it directly without having to do PRs, etc.
I hope this is a valid set of choices. Also I should mention that being the one that comes first, I may restrict other people's choices. So if anyone feels strongly about a project and I have to change mine for some reason, that's perfectly fine. | Project name | Language (py or js) | analyze? (X for yes) \<-- either | or --> develop? (X for yes) | |
---|---|---|---|---|---|
Choice 1 | MazeWeb | JavaScript | X | ||
Choice 2 | Fractionauts | Python | X | ||
Choice 3 | FractionBounce | Python | X | ||
Choice 4 | Gears | JavaScript | X | ||
Alt 1 | Fractionauts | Python | X | ||
Alt 2 | FractionBounce | Python | X |
This is my selection. I'm pretty open to other projects if these don't make the cut.
Project name | Language (py or js) | analyze? (X for yes) \<-- either | or --> develop? (X for yes) | |
---|---|---|---|---|
Choice 1 | MazeWeb | JavaScript | X | |
Choice 2 | FoodChain | JavaScript | X | |
Choice 3 | Planetary | Python | X | |
Choice 4 | Lemonade-stand | Python | X | |
Alt 1 | Fractionauts | Python | X | |
Alt 2 | Lemonade-stand | Python | X |
On Sat, Apr 11, 2020 at 08:15:29AM -0700, Jeffery Russell wrote:
This is my selection. I'm pretty open to other projects if these don't make the cut.
[snip]
Great, thanks!
Looking forward to others getting theirs in.
I've found I don't get notifications for changes to the wiki so that's something to be aware of. If you put something in the wiki maybe just make a note of it in a relevant issue (eg, here for posting a choices table), maybe even a link?
OK, on the wiki I'm seeing:
https://github.com/ritjoe/sugarizer-lite/wiki/zsd7200-task-choice
Also on the wiki I'm seeing
https://github.com/ritjoe/sugarizer-lite/wiki/cja1093-task-choice
@ritjoe should we post our choices here, or creating the wiki page is good enough?
On Sun, Apr 12, 2020 at 03:06:46PM -0700, Dennis Slavinsky wrote:
@ritjoe should we post our choices here, or creating the wiki page is good enough?
Once one of us drops a link here, oh, like this ...
https://github.com/ritjoe/sugarizer-lite/wiki/DennisSSDev-task-choice
... then yeah that's good enough.
Thanks!
Here are my choices
Project name | Language (py or js) | analyze? (X for yes) \<-- either | or --> develop? (X for yes) | |
---|---|---|---|---|
Choice 1 | Fractionauts | py | X | |
Choice 2 | Mazeweb | js | X | |
Choice 3 | Game of life | js | X | |
Choice 4 | Anglegators | py | X | |
Alt 1 | Fractionauts | py | X | |
Alt 2 | Anglegators | py | X |
OK, I've got this sketched out as:
https://github.com/ritjoe/sugarizer-lite/wiki/final-projects-20200413
Please look at your own items and see if there are any glaring problems.
I've added some more projects to open things up. As it was, I only assigned each person three things instead of four.
@iggyvolz @BlueJay89 @eza5640 I still need selections from you.
Got my selections - https://github.com/ritjoe/sugarizer-lite/wiki/iggyvolz-task-choice - apologies for the delay.
On Tue, Apr 14, 2020 at 05:58:55PM -0700, iggyvolz wrote:
Got my selections - https://github.com/ritjoe/sugarizer-lite/wiki/ iggyvolz-task-choice - apologies for the delay.
So it goes for many of us these days.
But thanks.
I tried to incorporate it into
https://github.com/ritjoe/sugarizer-lite/wiki/final-projects-20200414
last night.
I've not been getting invites on github for the past few days (neither email nor github notification). I was able to join a repo after my team mate sent me a direct link to the invite, so I might just need that for this repo.
I see ? for 3 of my tasks in https://github.com/ritjoe/sugarizer-lite/wiki/final-projects-20200414 which I'm happy with. For the fourth task I'd be happy with describing AngleGators.
So my tasks would look like | Project name | Language (py or js) | analyze? (X for yes) <-- either | or --> develop? (X for yes) |
---|---|---|---|---|
Fractionauts | Python | X | ||
Lemonade-Stand | Python | X | ||
Fractionators | JavaScript | X | ||
AngleGators | Python | X |
I'll remove the ? from those three tasks.
As discussed in the synchronous IRC meeting that just finished, due to a number of factors we'll just be doing three assignments per person.
There is one case of four provisional assignments (asterisked) whose confirmation are pending discussion with the assignee.
Just in case anyone else was having issues with github invites, I was able to accept the invite by going directly to https://github.com/ritjoe/sugarizer-lite/invitations
Once we settle on a list of activities to work with from #2 and #3, each student will post here their initial 4 task choices, as per https://github.com/ritjoe/hfoss/wiki/final-choosing-activities-2
There may be some negotiation as to what tasks a student ends up working on, depending on coverage and timing.