I believe this is is just perfect starting point for the "main" repository on github (or any other hosting).
First commit - just released latest official BB1.6.
Second commit - all suggested official patches.
All other existing "builds" - should be merged/branched from this main trunk.
You are right. That question should be discussed and performed soon.
But before we need to decide: What repository to choose? GitHub or maybe Bitbucket? Who will be the owner or there is a possibility of a group authorship. And so on.
Ivan Denisov wrote:You are right. That question should be discussed and performed soon.
But before we need to decide: What repository to choose? GitHub or maybe Bitbucket?
I suggest to make a voting. In this way it will be decided much sooner.
Ivan Denisov wrote:
Who will be the owner or there is a possibility of a group authorship. And so on.
The one who made the first commit and announced it here will be the owner. Then this person can grant appropriate access to the "center" group or whoever you'll decide. And while you'll be deciding all others can have desired "main" repository at least in the read-only mode.
Ivan Denisov wrote:Ok. Let's make the long voting with the discussion.
How long? One or two years?
OK, Ivan. The real proposal Just go to github (or bitbucket, whatever you like more) and make the repository. You are trusted and responsible person. If someone will make a better solution - it is not a big deal to move/delete this scratch.
In case we want to have back history, the option to create repository based on earlier BB versions. For example, start from BB 1.5, then 1.6 RC5, 1.6 RC6, 1.6.0.
I propose to tag OM's versions separate from community's versions and have separate branches. Thus, community can start his first version tagged, for example, as 0.9.
Josef Templ » 16 Oct 2013, 10:48 wrote:What are the advantages and disadvantages of the alternatves?
The Bitbucket welcome page says that it is free up to 5 users.
Isn't this a knock out criterion? Has anybody looked at this issue?
What about the other alternatves? Any experience with them?
In Github, as alternative:
GitHub wrote:Accounts are free for open source projects and include unlimited public repositories and unlimited public collaborators.
Since GitHub is in top list of code hosting solutions for teams, I would recommend it for community.
Regarding releases of BB distribution:
I recommend to refrain from putting binaries into code repository. Instead, as proposed in document Release Your Software, create binary releases.