Messages

1

General Discussion / Re: BeerXML v2 and onwards

« 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

2

BeerXML Standard Document / Re: BeerXML 3.0

« on: May 27, 2012, 09:22:48 AM »

I know the guys are busy working on other things so I am going to chime in here.

Regarding the BJCP style guidelines, although there is merit to bringing BeerXML in line with their schema, it may be a wild goose chase.  As the community at large we do not have much sway as how they present the schema.  They could change encodings, namespaces and the schema as a whole at will.

That being said, I do prefer the way they the BJCP guidelines are laid out.

I think it would benefit all to move this project to a more open forum to allow more direct contributors to the project, at this point it seems pretty dead here. To that end I have created a new repository on GitHub for tracking changes and allowing everyone to contribute to the project: https://github.com/brewpoo/BeerXML-Standard

I have not yet pushed the repo yet but will do so by the end of the weekend.

Thanks,
Jon (brewpoo)

3

General Discussion / 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