Thread:Taldin/@comment-24150802-20141010195905/@comment-24150802-20141011100134

Notes from watching http://vimeo.com/78936708 while washing the dishes (I hope the times are accurate):

00:00+ Wiki migration is finished. Bobbyroberts is no longer working with us. Ignore all this.

01:17 "3 sections" and onwards is relevant

01:33 some of the repos that we can ignore no longer exist so if you write a list of repos to ignore, ignore those ones ;) Derby is no longer in use. https://github.com/HabitRPG/

01:48 habitrpg-chrome extension is still in use  http://habitrpg.wikia.com/wiki/Chrome_Extension

02:40 "CSS" - all this around here is true but in addition there are other CSS styles in https://github.com/HabitRPG/habitrpg/tree/develop/public/css/ - See also around 08:50

02:55 "majority of stuff needing fixing" - yes for the back-end code (that does all the heavy programmy stuff). Fixes for the user interface (adding buttons, etc, etc) are in the "habitrpg" repo not "habitrpg-shared" (and hence the habitrpg public/css/ styles mentioned above)

04:00 reasons for Jade - there's a bit of info about this already on the current blacksmithery pages

04:40 locations of things (and a bit earlier about "view" directory) - THIS THIS THIS!!! This needs to be static for reference! PLEASE! :) Screenshots would be best taken from GitHub because all devs will use that but only some will use the GUI Tyler is using.

05:04 MongoDB collections - this UI is something Tyler has installed. I could probably get something similar running if you want clear recent screenshots. (Looks like it might be useful for me anyway.)

06:00 "tasks" in this programming context includes rewards (they're configured, stored, displayed just like to-dos etc)

07:45 tutorials - could be added to (or replace) the recommended Beginners resources for AngularJS in http://habitrpg.wikia.com/wiki/Setting_up_HabitRPG_locally

09:25 Refer also to "8. Work with habitrpg-shared" in http://habitrpg.wikia.com/wiki/Guidance_for_Blacksmiths 09:28-11:00+ "reason for that..." All this stuff helps to explain directory structures that seem weird and redundant

11:20 We are no longer converting from coffeescript to javascript. The coffeescript on the site now will stay as coffeescript. The javascript will stay as js (some is compiled from the coffeescript)

12:30 Tests! The more tests we have, the more stable the site becomes. Ideally, any new feature will have new tests added along with it. We've never really pushed that before (and we probably won't ever insist on it) but it would be good to highlight the existing tests and how exciting and fun it would be to write new ones. :) Contrib tiers are given for tests just as for features and bug fixes.

12:38 Not sure if they still use IRC and anyway we do NOT want every new programmer interrupting Tyler's server/database/critical-bug-fix work to ask Newbie questions. That's what the guilds are for (Aspiring Coders https://habitrpg.com/#/options/groups/guilds/68d4a01e-db97-4786-8ee3-05d612c5af6f or Aspiring Legends: HabitRPG Helpers https://habitrpg.com/#/options/groups/guilds/52f49529-58c1-4020-a59b-8bb8579e941f - I think the latter is a bit more of an official guild, but I'd really like to keep the heavy programming questions in the former guild for neatness and to not overwhelm the other kinds of contributors in the latter guild)

13:28 issue queue: https://github.com/HabitRPG/habitrpg/issues They could ask questions there I suppse, but probably still better in the guilds. If there's anything we can't handle in the guild, we'll tell them to log an issue. We have enough bugs cluttering up the issue queue and the more that goes in there, the harder it is to find anything. Probably best to NOT say that they can ask questions on github.

Note the Labels dropdown on the issues page. "Memorable" are bugs that people keep on asking about or issues that we want quick access to for other reasons. "entry level coding (text etc.)" is great for newbie programmers. "Priority - minor" - pretty much as Tyler says at 13:37, but the "entry level coding (text etc.)" was created more recently and is a better place to start.

14:29 Trello has been reorganised since then.

I think it would be okay if you put this onto the wiki piece by piece, not worrying about whether each piece was complete when you saved it (with an under construction banner). That gives you daily wiki points. :)