DevJam
OP
August 26 2023, 4:06am, last edited September 30 2023, 11:58pm
Quarterly Goal Progress:
- Double the amount of existing SG-1000 sets (26 sets when DevJam started): COMPLETE! We're currently at 32 sets signed off.
- A set for every game released in 1983: COMPLETE! 20 out of 20 eligible sets have been signed off.
Serizawa Hachidan no Tsumeshogi (SG-1000) was removed from the list due to a language barrier.- A set for every game with a set request: 5 out of 8 sets so far!
- A set for every game on the Othello Multivision (clone console): 3 out of 9 sets so far!
📆 - There's still time to join! Launch is September 30th!
📆 - The next console will be chosen on September 15th!
You must log in before you can join this conversation.
July 2 2023, 8:55am, last edited August 30 2024, 10:42am
The sheet: https://docs.google.com/spreadsheets/d/e/2PACX-1vRZnChIEwZ-L7WhOPMKdYgz77K4nx3W-7LmM29qjxHUC93inbtOgTstOqxKPGzdCzloJ6428nlzGL4S/pubhtml
The first DevJam is currently in-progress!
- Selected Console(s): Sega SG-1000
- Start Date: 2023-07-01
- Launch Date: 2023-09-30
------------------------------
Basic Info
DevJam is an ongoing developer event that is heavily inspired by our console rollouts: Developers sign up, get locked into developing sets for a specific console, get signed off once completed, and then we release all the sets at once on the launch date. However, with DevJam, the primary focus will be rollouts for supported consoles that did not get them. Some DevJams will focus on a single console. Others may focus on two consoles.
Once we "break even" and run out of consoles, the focus will shift to quarterly goals, completing sets for hubs, genre-specific crunch times, etc.
Time and Duration
DevJams will take place quarterly. The first one started July 1st, 2023 with a launch date of September 30th, 2023, the second one will be October 1st, 2023 through December 31st, 2023, etc.
Guidelines
- Notify the event host(s) when you make a claim! As of now, it seems to just be televandalist and AuburnRDM
- Sets claimed for the event will be marked as "Free Rollout" claims so they will not count against a developer's claim total. However, like rollouts, these will be limited to one at a time.
- Once a set has been signed off, it will be marked as "Release Scheduled" and is to be promoted on the launch date. Sign-offs will also grant the event host(s) permission to promote your set(s) to core on the launch date if you are unavailable.
- If a set is promoted early, it will be disqualified from DevJam. The developer may make another submission if they wish.
The Badge
- The event badge consists of 24 achievements and each achievement will be unlocked for every point earned at the end of the quarter.
- Each participant may obtain up to 6 achievements per quarter. These can be split up and allows for devs to take part in the event at their own pace, but will require some dedication. They could get 1 achievement in the first quarter, 3 in the second quarter, 2 in the third quarter, etc.
- Point values may vary between quarters depending on the console(s) selected.
- A chart detailing the current quarter's point system is at the bottom of this page.
The point system is better explained via this table.
Quarterly goals can be seen here.
FAQ
Can I double-dip with DevQuest, CL100, and other events? - Yes.
Will there be a second badge? - If this goes well and there's enough demand for a 'Round Two' badge, sure.
Can Junior Devs participate? - The nature of the event goes against several aspects of the Junior Dev program so as of now, no.
- Junior Devs may feel encouraged to rush a set.
- The promotion of Junior Dev sets is a big part of the process so having a set be "Release Scheduled" would waste a lot of time.
- Code Reviewers would need to work around the DevJam schedule.
- The amount of Junior Devs that end up losing the role due to inactivity or do 1-2 sets and disappear far outnumber those who stick around to get full dev. This could result in locked claims!