Hi

I'm thinking about opening up the GIT repo for anyone who wants to track development more closely.

I've not had a lot of time to spend on talisman so things are going a
little slow, and I don't want to make releases for every small change.

I've just committed code to finish the sec_level stuff in menus (turns
out I half finished it, but must have forgotten about it).

Opening up the git repo will also make the issue tracker etc on gitlab available.

The reason I didn't to begin with was so people were always on the same version, which would be easier to debug (and I often commit broken
things), so perhaps instead we could say.. if you want an expectation of
a working system use a release, if you don't mind hiccups, you can use
git.

This is mainly aimed at Alpha. Although, Tiny you're free to build the
windows version, but it's a little bit more complicated than building the
linux one.

Andrew

--- Talisman v0.10-dev (Linux/armv7l)
* Origin: HappyLand v2.0 - telnet://happyland.zapto.org:11892/ (21:1/182)

On 01 Feb 2021 at 01:34p, apam pondered and said...

I'm thinking about opening up the GIT repo for anyone who wants to track development more closely.

This sounds like a good idea to me.

Perhaps there's a way commit data can be pushed to echomail as well? Not sure it's that the best idea but I'm coming at it from the point of view of just sharing/publishing changes more widely.

I note DM does this for an echo I see in Fido related to Synchronet.. so if
you wanted to do something similar in fsx that could be a starter for 10 perhaps?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Avon wrote (2021-02-01):

On 01 Feb 2021 at 01:34p, apam pondered and said...

I'm thinking about opening up the GIT repo for anyone who wants to
track development more closely.

This sounds like a good idea to me.

+1

Perhaps there's a way commit data can be pushed to echomail as well? Not sure it's that the best idea but I'm coming at it from the point of view
of just sharing/publishing changes more widely.

It's possible, but I'm not sure what the real benefits are. "git pull" is so much easier.

---
* Origin: . (21:3/102)

Re: Talisman Git Repo
By: Oli to Avon on Mon Feb 01 2021 10:38 am

Perhaps there's a way commit data can be pushed to echomail as well?
Not sure it's that the best idea but I'm coming at it from the point
of view of just sharing/publishing changes more widely.

It's possible, but I'm not sure what the real benefits are. "git pull" is so much easier.

I guess it let's folks know that things are being updated, and that they might want to catch up to those updates.

Ttyl :-),
Al

... Is fire supposed to shoot out of it like that!?
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Al wrote (2021-02-01):

Perhaps there's a way commit data can be pushed to echomail as well?
Not sure it's that the best idea but I'm coming at it from the point
of view of just sharing/publishing changes more widely.

It's possible, but I'm not sure what the real benefits are. "git
pull" is so much easier.

I guess it let's folks know that things are being updated, and that they might want to catch up to those updates.

I understood "commit data" as sending actual diffs over echomail. If the info of a commit is useful, depends on how often it happens. If there are several a day, it could get noisy. If it's only one every couple of weeks or months like with binkd, it's good to know that some bug has been fixed.

---
* Origin: . (21:3/102)

apam wrote to All <=-

This is mainly aimed at Alpha. Although, Tiny you're free to build the windows version, but it's a little bit more complicated than building
the linux one.

Unless every single step was written out for me I wouldn't be able to
even get the compiler installed. ;) I'm okay waiting for you to compile
a windows version. Heck if there's something you want tested just compile
and drop in my inbound via happynet.

I am enjoying a windows native package again though. My linux skills are
just not where they used to be and I'm no longer able to deal with it. ;)

Shawn

... Civil engineers do it behind schedule

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

Re: Talisman Git Repo
By: Oli to Al on Mon Feb 01 2021 12:02 pm

I understood "commit data" as sending actual diffs over echomail. If the info of a commit is useful, depends on how often it happens. If there are several a day, it could get noisy. If it's only one every couple of weeks or months like with binkd, it's good to know that some bug has been fixed.

I was thinking just announcements similar to the announcements in the SYNCPROG or the FIDOSOFT.HUSKY area. I've seen some changes in husky recently but I haven't updated yet.

It would be interesting to see what's going on in different projects like Talisman, Enigma or crashmail and you would know quickly if there are important changes so you know about them and can get updated if you need too.

Ttyl :-),
Al

... Drive not ready; (R)etry, (G)o to impulse, (C)all Geordi
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 01 Feb 2021 at 01:34p, apam pondered and said...

The reason I didn't to begin with was so people were always on the same version, which would be easier to debug (and I often commit broken things), so perhaps instead we could say.. if you want an expectation of
a working system use a release, if you don't mind hiccups, you can use git.

I think that's a great idea.

In case it might help, a workflow that I've settled on that I
really think works well is to try and keep the main branch clean,
but have a "wip" branch that I put all my intermediate commits
into. When I think that I'm happy with how things look, I just
squash-merge it into main. That way, I can make as many little
"checkpoint" commits as I want in various states of brokenness,
but main is always buildable with the latest "released" code.

I think I first saw something similar described here: https://sandofsky.com/workflow/git-workflow/

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'm thinking about opening up the GIT repo for anyone who wants to
track
development more closely.

That would be pretty cool! We could then easily log issues/feature
requests and you can prioritize, discuss, tag, etc.

I've not had a lot of time to spend on talisman so things are going a
little slow, and I don't want to make releases for every small change.

No worries! And that would take some of the pressure off of "releases" as
well, yeah? We could just 'git pull' when something is ready to test in
a pre-release state.

This is mainly aimed at Alpha. Although, Tiny you're free to build the windows version, but it's a little bit more complicated than building
the
linux one.

I'd certainly be game for that.

Cheers,


|04[] |11Alpha
|03The Drunken Gamer |08/ |14TheDrunkenGamer.com:2323
|07A Talisman BBS

--- Talisman v0.10-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158)

tenser wrote (2021-02-02):

I think I first saw something similar described here: https://sandofsky.com/workflow/git-workflow/

Great article. After struggling with git for some time I'm using it in a very similar way described in the article. Not much new now, but I wished I read it much earlier.

---
* Origin: . (21:3/102)