Menu
▾
▴
#6 mbse on github
SourceForge was down when I created this, but I checked in the latest 1.0.5 source via Sean Dennis on github, setup the gh-pages branch as well...
If you're at all interested and have a github account, I'd be happy to add you to the bbs.io org, and give you commit access for mbse there.
https://github.com/bbs-io/mbse
http://www.bbs.io/mbse/ (gh-pages branch content)
I also created a 1.0.5 tag for the initial checkin, so that release versions can be tracked.
I appreciate it but there is already a mirror of the Git repo here over at GitHub, at https://github.com/ftnapps/mbsebbs; although it is true that the default branch there is 'debian' rather than 'master' like it is here. If you weren't aware of it, I need to post about it more...
And yes, I do need to get the version v1.05 imported into the Git repo from the Hg repo. ; and/or at least import the v1.05 archive. (Haven't done the archive import because prefer to use the import, since that includes the history.)
The master branch in the git repository (which goes back to 2001), including at https://github.com/ftnapps/mbsebbs/tree/master, has been updated through version v1.0.5. Note that tags haven't been pushed yet as they need to be verified where they're set. But also note that version number tags with a leading "v" are not used, so your 'v1.0.5' tag should be all right.
You're also welcome both here and at https://github.com/ftnapps. See also separate email.
Are you suggesting that the repository at SF is being discontinued?
Coz, I am a simple old geezer who like things simple and one source tree
tends to be enough for most of us.
Vince
On 21/05/15 11:47, Robert James Clay wrote:
I'm hoping that this makes it back in, I don't seem to be able to comment
in the thread on the website for some reason.
The SourceForge mirror mentioned seems to be tracking specifically a debian
branch, not the entire repo, and it's specifically rooted with a "Debian"
directory as such. I'm not sure if this is intentional. SF was offline
when I created the repo... there was a discussion on Facebook about MBSE,
and the source file was uploaded, and mention of starting a wiki for MBSE
etc.... I figured it would be better to have the source in a central
location, and use a wiki related to that. I created bbs.io specifically as
an umbrella for BBS related sites, and projects. Today, github is where I
look first, and when SF was down, I didn't really wait around for it.
Personally, I find that SourceForge itself doesn't represent the
collaboration it once did... And the vast majority of those I work with,
and the projects I work on have moved to github at this point. Not to
mention I can't even reply to comments on an issue I created.
--
Michael J. Ryan - http://tracker1.info
On Thu, May 21, 2015 at 12:13 PM, Vincent (Bryan) Coen vcoen@users.sf.net
wrote:
Related
Tickets:
#6Vincent (Bryan) Coen wrote:
Not at all! The current primary code repository is still the Hg (Mercurial) repository at the MBSE BBS SourceForge project, which I've found a way to mirror to the git repository also at SourceForge.
It's simply that with distributed version control systems like git, it's easy to mirror to other public locations (it's just an extra 'git push') and having it also on GitHub is useful.
Michael J. Ryan wrote:
I'll look into that...
Michael J. Ryan wrote:
Were the other branches there even looked at? The branches of the SF git repository are the same as those in the GitHub repository; which branch is configured as the 'default' branch at a GitHub repository has no effect on which branches are there or their content. If it's causing confusion, it's easy enough to change the default back to 'master'.
Where was that?
Never received a follow up on this.
Note that the 'debian' branch is now an intergration branch of the 'master' branch that also includes the debian/ directory.
Closing.