GIT public Repository for NAV code

kine

I do not know if you know GIT, but it is tool for keeping version history in distributed development env. used e.g. for developing Linux kernels. It issimple but powerfull and I am trying to use it for NAV. Right now I have one subject for discussion:

Creating public GIT repository for NAV code for actual versions, where will be added all official/unofficial patches for known bugs. In this way we can keep actual code for different versions with possible bugs already solved, everyone can look at it, aply the patch in own code etc. We can have local branches for local NAV versions etc.

Things to solve:

1) Legal - if it will be allowed by MSFT to have something like that (may be biggest problem)
2) Where to place this repository
3) How to organise this (who, what etc.)

Git tree example screenshot: http://roscidus.com/screens/git-example.png

What is your opinion on this?

DenSter

I'm not sure if a public code repository is going to be useful, not in the least because MSFT is probably not going to be happy about that. The issue is how this is managed, who is in charge. If it is going to be open source then no I am not interested, I don't want to rely on a repository of code that anyone can modify.

What I am most interested in is a permanent repository of NAV versions, full product CD's, an FTP site that doesn't move around, that is easy to navigate. This should then contain all versions of Navision, with all patches, all localizations, all in one place. You're looking for Navision 2.6E for the German localisation with advanced distribution? No worries, it's all in the "2.6" folder. There used to be one for the US localization (at greatplains.com of all places ) when MSFT first purchased Navision, they put all versions on an FTP site, and that was killed in favor of partnersource. I am still amazed when you filter on specific versions and localizations that you have to wade through AX and SL links to maybe get what you are looking for.

I'd settle for a more comprehensive, easy to navigate partnersource by the way

kine

I thought public in way "read only". Managed e.g. by MVPs? (or someone with responsibility);-)

And yes, I know that biggest thing to have that is MSFT view on this...

generic

I would say that this made sense when NAV released patches a lot more in older versions. Now you have
5.0, 5.0 sp1, 2009, 2009 SP1.

This will just add an additional overhead.

I would be interested in a history of KB articles and short summary on when they were fixed and in what version it is implemented.


I like waldo list for hotfixes. We should have same for Codes fixes.

kine

The idea was that if somebody find out that there is some patch in the KB (you ave access to the KB on PartnerSource, but it is hard to find something there without searching for specific info) it will be added into the repository. Result will be objects with as most patches as possible (it seems that best will be to have only official patches applied). It means that it will be something like "Cronus" objects with most patches as possible, if people will send KB numbers, which are needed to apply.

generic

It is ridiculous that you are doing this because Partner source sucks.
And people are paying for it.