Editing Meetings/weekly/2010-11-13

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Meeting}}
 
 
== Meeting objective ==
 
== Meeting objective ==
  
Line 10: Line 9:
 
"Check"
 
"Check"
  
==Topic 1: We figure out OH development priorities for the next 4 weeks ==
+
==Topic 1: We figure out OH development priorities for the next n weeks ==
  
* Continue fixing the profile importer / converting to Twisted - code
+
* Continue fixing the profile importer / converting to Twisted
** Make the bug importer Twisted-y after that? - code
+
** Make the bug importer Twisted-y after that?
** Document changes!! - docs
 
 
* Better documentation? (Where? What?)
 
* Better documentation? (Where? What?)
** [https://openhatch.org/bugs/issue163 https://openhatch.org/bugs/issue163]
+
** [https://openhatch.org/bugs/issue163]
** Hudson is undocumented - docs
+
** Hudson is undocumented
** Graphical documentation - "How OH basically works (techwise)" -- sort of like a UML diagram - docs, design
+
* Hudson is broken post-Gitorious move! Someone should fix it maybe.
* Hudson is broken post-Gitorious move! Someone should fix it maybe. [https://openhatch.org/bugs/issue172 https://openhatch.org/bugs/issue172] - code
 
** "Someone" being Asheesh, since no one else is authorized :P
 
** If other people *are* going to be able to use Hudson, it should probably have more descriptive descriptions of its tests - docs
 
** Hudson should yell at us in IRC when we break things: [https://openhatch.org/bugs/issue173 https://openhatch.org/bugs/issue173] - code
 
* Missions!
 
** They should freaking stop being hidden and beta already -- what needs to happen to make that happen?
 
*** Fix [http://openhatch.org/bugs/issue126 http://openhatch.org/bugs/issue126] - bitesize, UI, docs
 
*** Write a Missions HOWTO - docs
 
*** Remove beta beta thing - bitesize, design
 
*** Make opening /missions/ page more exciting!! - design, ui
 
*** Write Missions [Devel] HOWTO -- basically, finish this: [http://openhatch.org/wiki/Write_a_new_training_mission http://openhatch.org/wiki/Write_a_new_training_mission] - docs, code
 
*** Reorganize directory structure of mission views, etc. so each mission has their own folder (see above link and/or [https://openhatch.org/bugs/issue170 https://openhatch.org/bugs/issue170]) - bitesize, code
 
** Copy [https://wiki.mozilla.org/Education/Learning/ModifyBrowser https://wiki.mozilla.org/Education/Learning/ModifyBrowser] and make a "mission"-type wiki page for HOWTO hack on OpenHatch - docs
 
*** [https://openhatch.org/bugs/issue163 https://openhatch.org/bugs/issue163] might be a good simple change for something like this - bitesize, ui, code
 
  
== Logs ==
+
[[Category:Meeting]]
* Start at http://irclogs.jackgrigg.com/irc.freenode.net/openhatch/2010-11-13#i_2470267
 
 
 
== Asheesh's post-meeting notes ==
 
 
 
* I thought the meeting went pretty well.
 
* I couldn't find the agenda. That was silly. In the future, we should put it on the wiki, since the wiki has good search.
 
* We didn't really have time for an IRC-based hack session, as I had wanted to. The discussion lasted too long. For future meetings, let's leave the hack session out.
 

Please note that all contributions to OpenHatch wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see OpenHatch wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

Templates used on this page: