[PLANNING] Release 0.2.0: Hustle (and 0.1.1)

[Davey Shafik]

Alright folks,

Now that we've discussed code names, lets talk about using them!

Lets talk about our next milestone release: 0.2.0: Hustle

The original roadmap for 0.2.0 looks like this:

1. Better design and usability of the admin interface pages.
   
2. More documentation
   
3. Refactoring of the configuration handling. 
   
4. Improvement to the Tester (Visually)
   
5. Reverse Engineering of Actions to link errors and Action for the generated documentation (See demo)
   

This release is mostly about polishing the visuals and removing friction. 

I'm already working on #1, #4 was/is being facilitated by Philip's (CC'ed) work to bring the Mashery iodocs UI to our / documentation route.

As far as #2, I'd like to write more "This is how you achieve best practices in FRAPI" — implementing HATEOAS, caching etc using FRAPI. Educating on good REST, using FRAPI as a tool to do it.

#3 is going to require some sort of upgrade/migration tool — so I'd like to suggest we focus on this instead, for this release.

#5... well, I'd like to explore something a little larger than this.

The biggest problem we face is injecting things within the actions; that is, for example, interacting with HTTP headers and the like.

I'd like to look at writing some helper classes that can be used within actions to interact both the HTTP request life-cycle as well as to help automate HATEOAS-type functionality.

For example, maybe we can use the URI Templates to allow developers to give us a URL template for the data in collections and we can use the data returned + the template to inject href's?

Additionally, I'd like to look at our bug list and prioritize them into a 0.1.1 and 0.2.0 milestone (and beyond). I do not want to wait on 0.2.0 to get out a bug-fix release.

Can we schedule an IRC meeting before Sunday? I am on vacation from Sun-Sun next week.

- Davey

[Trevor Morse]

Hey Davey,

This all sounds good to me. I'm willing to work on 2, 3 and some bug
fixes specifically and help out with any of the others as I can/am
needed.

I'm available any time tomorrow or Saturday for an IRC meeting. Just
let me know when!

-tm

[Clay Hinson]

I can help with documentation and bug fixes, and I think especially the documentation tasks need to be broken down into individual github issues so it doesn't feel like trying to boil the ocean when approaching the documentation. 

Also, this can be discussed in more detail in the IRC meeting, but for tracking the 0.1.1 and 0.2.0 releases, it would be helpful to create milestones in Github and tag issues to them.

I can be available for an IRC meeting Friday or Sunday.

Clay Hinson