Author Topic: BeerXML v2 and onwards  (Read 380 times)

jlochner

  • Newbie
  • *
  • Posts: 3
  • BeerXML Rocks!
    • View Profile
BeerXML v2 and onwards
« on: April 28, 2012, 08:37:41 PM »
Just wanted to take a minute to thank all of you who have worked hard on BeerXML.  Thanks!

I like the changes from v1 to v2 and would like to contribute to the future of this project.  Although there are some shortcomings to v2 I would suggest freezing all major changes at this point and incorporating all further major enhancements to v3.

I suggest this first and foremost because I am incorporating support for v1 and v2 (as it stands) into a ruby library.  It is difficult to write a library for a moving target and I believe that v2 is "good enough" to stand on it's own.  There were some pretty sweeping changes from 2.0 to 2.07 so when I am speaking of v2 I am referring to the latest.

As far as moving forward, it would be nice to come up with a roadmap and a way for people to contribute directly to the project rather than via forums.  I would suggest creating a project on GitHub for doing this.  Changes can be managed via direct access (for core contributors) and pull requests for the rest.  The other integrated features would come in handy as well and we may attract some more developers.  I know that this is not really a traditional "code base" but it would work well in this case.

For reference, the project I am working on (not my original work): https://github.com/BrewingHub/beerxml v1 support for now

Let me know what you guys think.

Thanks,
Jon

jlochner

  • Newbie
  • *
  • Posts: 3
  • BeerXML Rocks!
    • View Profile
Re: BeerXML v2 and onwards
« Reply #1 on: June 19, 2012, 03:09:11 PM »
Seems rather dead on this forum nowadays.  Anyway, I created a project on GitHub https://github.com/brewpoo/BeerXML-Standard to track for v2 and onwards.  Please take a look and let me know.

I also have a ruby library that is under developement https://github.com/brewpoo/brewser It currently supports v1.  I am going to add v2 support very soon.

Thanks,
Jon