CMDBuild Forum

Public Git Repository

Systems Engineering
#1

Hi,
the current source code available via git on sf.net is quite old and does not contain the latest release 3.1.
Will you update (and keep up-to-date) a public git repository, or only releases as zip files?
Cheers,
Fabian

1 Like
#2

You can download the 3.1 source code from here: http://www.cmdbuild.org/it/download

#3

My question was related to a source code repository, not a zip file to download.

#4

For every release on SF in the files section you can find the updated source code in the src zip file, in example for CMDBuild 3.1 you can find the updated source code in the file cmdbuild-3.1-src.zip

#5

The zip file does not contain the .git directory with commit logs, branches or informations for hot fixes etc. which are useful when investigating problems with CMDBuild.

#6

There’s source code in BitBucket, but is not up-to-date either. I would also like to see Tecnoteca maintain their source code on a Git repo as that is our method of preference. That way we could contribute with bug fixes too by tracking changes and commit logs.

#7

+1 for an up-to-date public SCM repository, be it bitbucket / github / gitlab or anything else.

Tecnoteca is doing an huge work (both on the application and on the data model side) with the cmdbuild/openmaint ecosystem and it provides this work to us according and open-source model. On the other hand, Tecnoteca’s business model based on service, support plans and add-on applications is fine too.

But, IMHO, the absence of a public source repository is counter-productive as it

  1. refrain people to help the project by submitting new feature or patches,
  2. speed down adoption of the software as people are now (we are in 2019) accostumed to find the source of applications publicly available and under configuration management.
  3. while a forum is great for communication, it’s not the best medium fo development related subjects such as signaling defects.

We can understand the overhead associated with the management of a dual private/public SCM though …

Regards,
J.-M.

#8

I think Tecnoteca would benefit a lot from an open development model (public development repository, public ticket system, etc.) and that there is no need for a dual private/public SCM (only speaking for CMDBuild of course).