On 2017-08-08 11:55, Steffen Möller wrote:

People on this thread take one of two positions:
  a) have it the way we always had it in BOINC, mostly in ignorance of
what git could do for BOINC
  b) have it the same way that git is used in any other larger Open
Source project

git by itself is just an SCM that supports easy branching and merging. This doesn't enforce a particular branch model or branch properties. Thee are quite a few projects even on github that use git without following e.g. gitflow or any other model specifically supported by github.

git, however, was developed to support a distributed, collaborative development process as used for the Linux kernel. This development model requires a stable 'master' branch. Most software developers involved in this discussion here (including me) have been developing software this way for, say, the past 10y - I don't really think that it's "impossible".

So the real decision to make would be whether to move from a centralized development model (1.) that hinders effective collaboration (e.g. by throwing everything into master without review, discussion, tests or anything) and distribution (everyone being constantly affected by what anyone else throws into master) to a model that allows distributed collaborative development (2.). The important thing to note is that these models of development are incompatible. A developer following 1. will inevitably ruin every effort of anyone else to do 2., that's why we need a decision. The branching model to use in (2.) is really just details and can be decided later.

This decision is to be made by the PCM (https://boinc.berkeley.edu/trac/wiki/ProjectGovernance). Depending on the outcome, people wanting to develop BOINC in their own style may do so by forking it. But before that official decision has been made, it doesn't make sense to split the community, resulting in doubling effort and halving the resources.


boinc_dev mailing list
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to