Migrating the OpenSocial spec from Google Code for Github

[Matthew Marum]

Just wanted to let folks know that we've started migrating from our old Google Code project to Github.

You can find the spec repository here.

https://github.com/OpenSocial/spec

The spec is also now hosted using Github Pages.  For example,

http://opensocial.github.io/spec/2.5/Core-Gadget.xml

I've also migrated over all the old issues from the Google Code issue tracker as Github issues.

https://github.com/OpenSocial/spec/issues?state=open

I think using Github pull requests will make change reviews and change tracking easier to manage.  Also the Github community features should make it easier for us to collaborate on the spec changes.

Let me know what you guys think.

Matt Marum

Spec Release Manager

[Chris Geer]

Matt, I've been following the spec for a while now but haven't participated yet so this is an outside view. 

I like the idea of moving it to github since the google version was confusing, however, is there any way represent the various versions as tags/branches instead of folders? It would make it easier to track history of files through the lifetime and git makes it really easy to switch back and forth between them. Maybe it's not possible to recreate, but I think it would make things easier to maintain long term as the number of versions grows.

Thanks,

Chris

--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opensocial-and-gadg...@googlegroups.com.
To post to this group, send email to opensocial-an...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/opensocial-and-gadgets-spec/c7d0120a-cb96-44fd-868e-b0f244be3dbe%40googlegroups.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Matthew Marum]

Thanks for comments Chris.

Yeah, it would be cleaner from a development perspective to use tags/branches but right now the source tree pulls double duty as the content that we host.  If we could find a way to easily host all versions of the spec within the gh-pages branch (which is used by Github Pages).  Right now the easy/lazy way is just to merge master into gh-pages and that makes sure everything is published.

I'm open to finding better ways though.  Feel free to fork it and refactor it and we can find out how well works. :)

Matt

To view this discussion on the web visit https://groups.google.com/d/msgid/opensocial-and-gadgets-spec/CAFNO4HgFikGW%2BRXpb7NNbBUSPU48WAKbNyc-VMULAfvR8n659A%40mail.gmail.com?hl=en.

[Chris Geer]

Matt,

I'll give it some thought. I know the foundation has access to Confluence, do you also have access to a Bamboo instance?

Chris

To view this discussion on the web visit https://groups.google.com/d/msgid/opensocial-and-gadgets-spec/CAJoAmjqkPCd-OZkhdaA_PxjKiYD%2B%2BU7cDKEKxQihs3obDcFjTw%40mail.gmail.com?hl=en.

[Matthew Marum]

As far as I know we only have access to Confluence right now.

To view this discussion on the web visit https://groups.google.com/d/msgid/opensocial-and-gadgets-spec/CAFNO4Hgfd%3D_wHxhDddR0zf0bh8DD-gxyLq8HqjZpOkhxr3CeQQ%40mail.gmail.com?hl=en.