Repository and code versioning tool

[ReneK]

Where do we want to store our version of the BBF? It has been suggested that this may or may not be the final tool. So, let's decide now, and if in the future we want to switch to another tool, his can be done by a vote.

There are thirteen options, but our board software only allows for 10.

Thus I deleted the option "Create our own based on O3" as we do not currently have it, but we need a tool now. I also deleted "decide now and make switching for later possible.

One more needs to be deleted, and I decided on "Sync one repository everywhere above". I will do a separate vote on this later on.

[Ivan Denisov]

Not voted: Krywult, Campbell, Kuzmitsky, OberonCore, Zinn, Berthnard.

[ReneK]

Still looking into the issue to make up my mind, sorry....

[Ivan Denisov]

Whats wrong with the voting? Rene, did you send the emails to the people who are not voted? If not, please do this.

[Robert]

I am going to abstain on the Tools as I don't know enough about them to have a valuable opinion.

To me the most important feature is that it is easy for general users to find the current BlackBox version, understand its status, and then download it.

Tracking changes from the previous version, I guess, is the next most important feature. Then there are other things such as bug tracking and "approving" changes or new features. Are these
Tools intended to do these tasks, and which ones are good at them?




Regarding versions I have more to say.

I think we should have a Center version zero which equals OMS 1.6 final.

This means that users have no reason to stay with "OMS versions" rather than switching to "Center versions". People can start using the Center repository with NO compatibility concerns.
OMS 1.6 final is also the best place to reference later changes from.


I also think we need clearer discussion and policy for later Center versions. Will we have stable and unstable releases? What is the planned frequency of stable releases? What is the policy for approving bug fixes in new releases?
What is the policy for adding new features?

These policies need to be clearly set out, agreed by the Centre members (sorry - I just naturally use the English spelling of Center!), and, importantly, accepted by a significant proportion of the BlackBox user community.


Regards

Robert

[DGDanforth]

I am in a similar position to Robert.
His comments are relevant and need to be considered.
-Doug

[Bernhard]

I don't have enough experience with the different options.

So I abstain ...
--
Bernhard

[Ivan Denisov]

10 from 11 members voted, most of members 6/10 agree that we need some repository and most consolidate opinion is that we need GitHub as public repository and Redmine for project tracking.

Public repository:
http://github.com/BlackBoxCenter

Center Issues Tracker:
http://redmine.blackboxframework.org
http://redmine.blackboxframework.org/pr ... der/issues