Code-Development collaboration through Bitbucket (GIT and Mercurial)

[Ton Plomp]

Hi All,

 

I would like to announce the  setup of a LAVAg group on Bitbucket. This will provide us with an easy-to-start collaboration platform. Any member of the group can create repositories for open source projects.

 

The first repository in this group is the JSON LabVIEW API.

My goal is to have a groups of repositories of code that are valuable to us all. By moving the repositories into a group it removes  the link to a person on the code. Now the code is owned by the group and the value reflects on the LAVA community.

 

If you want to join the group (or co-admin) drop me a message on LAVA or Bitbucket

 

I hope this will give our company a boost in cooperation and code development!

 

Have fun,

 

Ton

[mje]

Sounds like a great idea. I've tried and failed miserably a few times to get my brain around git's way of doing things. I had best figure it out. Until then good luck!

[Tom Fantasia]

Excellent idea.  

[TimVargo]

GREAT IDEA!  However, I'm confused.    The rules listed at <https://bitbucket.org/lavag/about/wiki/Home> include these two: 

• Preferably the code should be downloadable via the LAVA Code Repository
• Upload the build result (.VIP, .LLB or a zip) to the Files section of the repository on Bitbucket
  

This sounds backwards to me.  Shouldn't the source code reside on Bitbucket, so that Git and/or Mercurial SCC can be leveraged; and the build result placed on the LAVAcr?

[drjdpowell]

This sounds backwards to me.  Shouldn't the source code reside on Bitbucket, so that Git and/or Mercurial SCC can be leveraged; and the build result placed on the LAVAcr?

Yes.  Source code is on Bitbucket; it is the VIPM installers that are in the LAVA CR.   One should also upload the installer to the files section of Bitbucket (though I often forget that).  Source code should also be in an as early a LabVIEW version as reasonable (I use 2011), to maximize the number of people who can use it.  

[TimVargo]

Yes.  Source code is on Bitbucket; it is the VIPM installers that are in the LAVA CR.   One should also upload the installer to the files section of Bitbucket (though I often forget that).  Source code should also be in an as early a LabVIEW version as reasonable (I use 2011), to maximize the number of people who can use it.  

OK, so that clarifies the proper usage in my mind; but the wording quoted above makes it SOUND backward.  I recommend clarifying that wording.