Hello Ward!

03 Feb 21 09:44, you wrote to Dallas Hinton:

I will nominate all of these people (if I'm allowed nominate more
than 1).

I would think that to be grossly inappropriate.

As far as I know only 3, so far, have expressed a willingness to
continue.

I have now also received word that Nick Andre is willing to accept another term. I am also willing to do so, should the RCs see fit to nominate/elect me.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Dallas Hinton to Andrew Leary on Tue Feb 02 2021 08:05 pm

Hi, Andrew -- on Feb 02 2021 at 02:33, you wrote:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

I will nominate all of these people (if I'm allowed nominate more than 1).

Cheers... Dallas
RC17

I think it's allowed! I know you aren't limited to just 1.

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Hello Carol!

** On Thursday 04.02.21 - 17:12, Carol Shenkenberger wrote to Dallas Hinton:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

What exactly have these people done wrt the FTSC activity since
the last elections?

--
../|ug

--- OpenXP 5.0.48
* Origin: (2:221/1.58)

Good ${greeting_time}, August!

04 Feb 2021 20:56:00, you wrote to Carol Shenkenberger:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

^^^^^^^
Please fix the quoting.

What exactly have these people done wrt the FTSC activity since
the last elections?

Well, let's see...

1. Andrew Leary
Served as an administrator, participated in most discussions (there were not really much of them, however).

2. mark lewis
Nothing, except chattering out technical discussions.

3. Richard Menedetter
Participated in some discussions.

4. Carol Shenkenberger
Nothing.

5. Ozz Nixon
Participated in one discussion about his 20+ years old software, found some typos in the existing documents, then disappeared.

6. Nick Andre
Nothing.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi
* Origin: ::1 (2:5020/545)

Carol,

I think it's allowed! I know you aren't limited to just 1.

Without asking the individuals what their intentions are?

C'mon Carol, the FTSC is dead. This election can go forward and if it is succesful, then this body of people will either again do as good as nothing and/or is composed of people without the desired background.

What is needed is more developers developing exciting new stuff which can then be documented. As it is other than checking punctuqtion, there's nothing to do.

I think the elements raised above were also raised the last 2-3 elections
with nothing happening.

But ... please dream on.

Have a good week-end.

\%/@rd

--- DB4 - Dec.21 2020
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hi, Ward!

05 䥢 21 14:19, Ward Dossche -> Carol Shenkenberger:

But ... please dream on.

Have a good week-end.

That's what you say very, very well. Today it is a completely dead structure that does nothing. All their recent activity is a big fart into a puddle...

Have nice nights.
Stas Mishchenkov.

--- “ ®¤­¨å «î¤¥©, ¯®«ãè à¨ï ¯à¨ªà뢠îâáï ª®áâﬨ ç¥à¥¯ , ã ¤à㣨å - èâ ­ ¬¨.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: August Abolins to Carol Shenkenberger on Thu Feb 04 2021 08:56 pm

Hello Carol!

** On Thursday 04.02.21 - 17:12, Carol Shenkenberger wrote to Dallas Hinton:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

What exactly have these people done wrt the FTSC activity since
the last elections?

--
../|ug

There hasn't been much going on be a couple of us have been helping folks understand how the standards got in place and how proposals work.

There are 2 in possible view in the not too distant future. One from Maurice on datestamps that may morf a bit to become msg-id area (not clear to me on where he's taking it but he's looking at the next Y2K type event) and you and Stas with Telegram working off smartphone/Notepads (assume I got that right).

Ozz has been developing a BBS with embedded mailer/tosser from what I can tell. In fact, I need to finish a project of my own then see if he wants to be added to the credits. He found a bit of my old nodelist FAQ (I recognize my own wording) and made some edits to it (jarring in style but not incorrect, just changes). I suspect Richard Menedetter will find this one up his ally and find what I am missing. Andrew is doing his best as coordinator but with little material to coordinate and Nick is new enough, nothing has really happened but he devlops a major mailer.

I think all are valid. I can't think who to suggest might want to join the FTSC but Stas might want to or you?

I have one other thought. If no one screams too hard, maybe we can mix the renewal election dates a bit so it's not so lop-sided? Just adjust some to further out. We've done that before. Twice that I know of.

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Stas Mishchenkov to Ward Dossche on Fri Feb 05 2021 11:04 pm

Hi, Ward!

05 䥢 21 14:19, Ward Dossche -> Carol Shenkenberger:

But ... please dream on.

Have a good week-end.

That's what you say very, very well. Today it is a completely dead structure that does nothing. All their recent activity is a big fart into a puddle...

Have nice nights.
Stas Mishchenkov.

Hey Stas, want to fart in a puddle with me?

Ok, joking aside, once you expand Telegram to delivery from 3 or more sites, when would a flag be appropriate in your view for folks to reach out easier for a link? I know you are not there yet (still developing) but does it sound like a need later down the road?

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Hello Carol,

On Sat Feb 06 2021 14:19:12, Carol Shenkenberger wrote to August Abolins:

There hasn't been much going on be a couple of us have been helping
folks understand how the standards got in place and how proposals
work.

That has nothing to do with the FTSC.

There are 2 in possible view in the not too distant future. One from Maurice on datestamps that may morf a bit to become msg-id area (not
clear to me on where he's taking it but he's looking at the next Y2K

Nothing has been drafted. Maybe another proposal, but can not be turned into a standard for another million years.

type event) and you and Stas with Telegram working off
smartphone/Notepads (assume I got that right).

Again, something has to be drafted, and in this case.. can it be? Another protocol/service is being used to "gate" into Fidonet.

Ozz has been developing a BBS with embedded mailer/tosser from what I
can tell.

Based off current standards and proposals, more than likely. If anything new is made, show the FTSC so they can document it.

and Nick is new enough, nothing has really happened but he devlops a
major mailer.

Nick as in Nick Andre? New Enough? Do you live in space?

I have one other thought. If no one screams too hard, maybe we can
mix the renewal election dates a bit so it's not so lop-sided? Just adjust some to further out. We've done that before. Twice that I
know of.

We basically have to support what's left, because by definition if we don't have 7? members, the FTSC is null and void.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi, Carol!

06 䥢 21 14:26, Carol Shenkenberger -> Stas Mishchenkov:

Hey Stas, want to fart in a puddle with me?

Why not? ;)

Ok, joking aside, once you expand Telegram to delivery from 3 or more sites, when would a flag be appropriate in your view for folks to reach out easier for a link? I know you are not there yet (still developing) but does it sound like a need later down the road?

For now the Talegram_BBS is so far from the moment when it can be runned by othe nodes.

Meanwhile, I have some other ideas that I have implemented on my node and it would be very easy to implement them on others. This would be especially easy if will properly documented by the FTSC. However, to date, the PKT and MSG standard is still documented in FTS-0001, which is now practically not used by anyone and the widely used corresponding formats are not documented. Does it make sense to offer something new?

Yes, I know there is now a very important new flag BEER in the nodelist. ;)

PS: For example Try send netmail

From : Carol Shenkenberger 1:275/100
To : Pind 2:460/58

Have nice nights.
Stas Mishchenkov.

---
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, All!

07 䥢 21 18:42, Stas Mishchenkov -> Carol Shenkenberger:

PS: For example Try send netmail

From : Carol Shenkenberger 1:275/100
To : Pind 2:460/58

Sorry. It MUST be Ping. My typo.

Have nice nights.
Stas Mishchenkov.

--- Œã¦ ¡¥§ ¦¥­ë - ª ª ¤ã¡ ¡¥§ ¤ïâ« .
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Carol!

*** Saturday 06.02.21 at 14:19:12, Carol Shenkenberger wrote to August Abolins:

[snip]

I can't think who to suggest might want to join
the FTSC but Stas might want to or you?

Fine but you're forgetting something.

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:250/1.333)

Servus Andrew!

Antwort auf eine Message von Andrew Leary an All:

The following members' terms expire on 11 Mar 2021:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

So I like to nominate:
Richard Menedetter 2:310/31

and in addition
Mark Lewis 1:3634/12
Carol Shenkenberger 1:275/100

if they want to do the work - I'm absolutely ok with that ;)

Baba
DonHelmi/2

--- FleetStreet 1.27.3.8d
* Origin: DonHelmi's Datendienst (2:313/41)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Nicholas Boel to Carol Shenkenberger on Sun Feb 07 2021 12:00 am

Hello Carol,

On Sat Feb 06 2021 14:19:12, Carol Shenkenberger wrote to August Abolins:

There hasn't been much going on be a couple of us have been helping folks understand how the standards got in place and how proposals
work.

That has nothing to do with the FTSC.

There are 2 in possible view in the not too distant future. One from Maurice on datestamps that may morf a bit to become msg-id area (not clear to me on where he's taking it but he's looking at the next Y2K

Nothing has been drafted. Maybe another proposal, but can not be turned into standard for another million years.

type event) and you and Stas with Telegram working off smartphone/Notepads (assume I got that right).

Again, something has to be drafted, and in this case.. can it be? Another protocol/service is being used to "gate" into Fidonet.

Ozz has been developing a BBS with embedded mailer/tosser from what I can tell.

Based off current standards and proposals, more than likely. If anything new made, show the FTSC so they can document it.

and Nick is new enough, nothing has really happened but he devlops a major mailer.

Nick as in Nick Andre? New Enough? Do you live in space?

I have one other thought. If no one screams too hard, maybe we can
mix the renewal election dates a bit so it's not so lop-sided? Just adjust some to further out. We've done that before. Twice that I
know of.

We basically have to support what's left, because by definition if we don't have 7? members, the FTSC is null and void.

Regards,
Nick

... "Take my advice, I don't use it anyway."

Well Nick B, With no propsals, our 'work' has been helping people understand how to MAKE one.

Ozz had a lot of problems with no modern guides. Modern developers aren't passing new guides to those who can follow suit. We have 'pipeline development' now. Modern tech tells us that is a dead end eventually.

Some of us are helping developers with how to get the 'word out' and then we see what works.

I'd really hope Stas will help at least with some tech to smartphones IOS if I got right. I'd like to see somthing from the Mystic developer and to see SBBS actually submit suggested implementation proposals would be excellent. Technically SBBS is open source but that doesnt mean others know the basics to find it.

So, any better ideas? With no repository on 'how-to' we leave all developers hanging and we die. It doesnt MATTER if it is a proposal or raised to a standard just now. It needs to be where they can find it.

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Stas Mishchenkov to Carol Shenkenberger on Sun Feb 07 2021 06:42 pm

Hi, Carol!

06 䥢 21 14:26, Carol Shenkenberger -> Stas Mishchenkov:

Hey Stas, want to fart in a puddle with me?

Why not? ;)

Ok, joking aside, once you expand Telegram to delivery from 3 or more sites, when would a flag be appropriate in your view for folks to reach out easier for a link? I know you are not there yet (still developing) but does it sound like a need later down the road?

For now the Talegram_BBS is so far from the moment when it can be runned by othe nodes.

Meanwhile, I have some other ideas that I have implemented on my node and it would be very easy to implement them on others. This would be especially eas if will properly documented by the FTSC. However, to date, the PKT and MSG standard is still documented in FTS-0001, which is now practically not used anyone and the widely used corresponding formats are not documented. Does it make sense to offer something new?

Yes, I know there is now a very important new flag BEER in the nodelist. ;)

PS: For example Try send netmail

From : Carol Shenkenberger 1:275/100
To : Pind 2:460/58

Have nice nights.
Stas Mishchenkov.

Lol! pass what you can to us. We can always take a proposal and work with you on it if formatting is a help. Many of us can help with technical wording if there is confusion.

Send us what we can use for now? Last I had from August seemed to indicate I needed to be a UNIX version to even start but others with that, can look and see what they can do?

Eventually you will hit a release level stage and documenting that will mean others can then help. They may be able to make '3rd party solutions' (add ons) to things you have not gotten to yet,

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Carol Shenkenberger to Nicholas Boel on Thu Feb 11 2021 10:03 pm

I'd really hope Stas will help at least with some tech to smartphones IOS if I got right. I'd like to see somthing from the Mystic developer and to see SBBS actually submit suggested implementation proposals would be excellent. Technically SBBS is open source but that doesnt mean others know the basics to find it.

To find... what exactly?

So, any better ideas? With no repository on 'how-to' we leave all developers hanging and we die. It doesnt MATTER if it is a proposal or raised to a standard just now. It needs to be where they can find it.

Here's my attempt at a modern FTN spec: https://wiki.synchro.net/ref:fidonet_packets
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hi Helmut!

11 Feb 2021 21:36, from Helmut Renner -> Andrew Leary:

So I like to nominate:
Richard Menedetter 2:310/31

I accept.

CU, Ricsi

... Human history has become a race between education and catastrophe.
--- GoldED+/LNX
* Origin: Would I ask you a rhetorical question? (2:310/31)

Helmut wrote (2021-02-11):

if they want to do the work - I'm absolutely ok with that ;)

the work?

---
* Origin: . (2:280/464.47)

Hello Helmut!

11 Feb 21 21:36, you wrote to me:

So I like to nominate:
Richard Menedetter 2:310/31

ACK.

and in addition
Mark Lewis 1:3634/12

ACK.

Carol Shenkenberger 1:275/100

Carol has already been nominated and accepted.

Regards,

Andrew
FTSC Election Coordinator

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hello Richard!

12 Feb 21 11:28, you wrote to Helmut Renner:

So I like to nominate:
Richard Menedetter 2:310/31

I accept.

ACK.

Andrew
FTSC Election Coordinator

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Good ${greeting_time}, Richard!

12 Feb 2021 11:28:50, you wrote to Helmut Renner:

So I like to nominate:
Richard Menedetter 2:310/31

I accept.

You and Maurice seem to be the only "T" people in the coming FTSC... :-/


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... god@universe:~ # cvs up && make world
--- /bin/vi
* Origin: ::1 (2:5020/545)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Helmut Renner to Andrew Leary on Thu Feb 11 2021 21:36:26

Mark Lewis 1:3634/12

i accept this nomination...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark!

12 Feb 21 17:20, you wrote to Helmut Renner:

Mark Lewis 1:3634/12

i accept this nomination...

ACK.

Andrew
FTSC Election Coordinator

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Rob Swindell to Carol Shenkenberger on Thu Feb 11 2021 08:45 pm

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Carol Shenkenberger to Nicholas Boel on Thu Feb 11 2021 10:03 pm

I'd really hope Stas will help at least with some tech to smartphones IOS I got right. I'd like to see somthing from the Mystic developer and to s SBBS actually submit suggested implementation proposals would be excellen Technically SBBS is open source but that doesnt mean others know the basi to find it.

To find... what exactly?

So, any better ideas? With no repository on 'how-to' we leave all developers hanging and we die. It doesnt MATTER if it is a proposal or raised to a standard just now. It needs to be where they can find it.

Here's my attempt at a modern FTN spec: https://wiki.synchro.net/ref:fidonet_packets

Submit then!

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Andrew,

02 Feb 21 02:33, you wrote to All:

The following members' terms expire on 11 Mar 2021:
Nick Andre 1:229/426

I hereby nominate Nick Andre.



Tom

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: BrainDeath BBS (2:292/8125)

Hello Tom!

14 Feb 21 11:09, you wrote to me:

@TZUTC: 0100
@CHRS: CP437 2
@MSGID: 2:292/8125 6028f752
@REPLY: 1:320/219@fidonet 6019016a
Andrew,

02 Feb 21 02:33, you wrote to All:

The following members' terms expire on 11 Mar 2021:
Nick Andre 1:229/426

I hereby nominate Nick Andre.

ACK.

Andrew
FTSC Election Coordinator

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hello Carol,

On Thu Feb 11 2021 22:03:16, Carol Shenkenberger wrote to Nicholas Boel:

Well Nick B, With no propsals, our 'work' has been helping people understand how to MAKE one.

The last couple of proposals that I remember coming through here, ended up going through a rigorous spelling and grammar checking, and once they could not be almost completely reworded any more, they were forgotten and never brought up again.

Ozz had a lot of problems with no modern guides. Modern developers
aren't passing new guides to those who can follow suit. We have
'pipeline development' now.

Some of these modern developers (Synchronet, Husky, for example) have documented their own software fully. One only has to go to the wiki to see it all. Why would they want to burden themselves documenting their own software, and then writing up proposals and or documentation for the FTSC when they're not a member, and probably don't want to be one?

Modern tech tells us that is a dead end eventually.

I'm not sure what modern tech is telling you this, but "---SBBSecho 2.11-Win32" is 10-15 years old now. If you don't keep up with modern tech, I'm not sure how you can use it as an excuse for anything.

Some of us are helping developers with how to get the 'word out' and
then we see what works.

I'd really hope Stas will help at least with some tech to smartphones
IOS if I got right. I'd like to see somthing from the Mystic
developer and to see SBBS actually submit suggested implementation proposals would be excellent.

My point is, why should they have to submit anything? They're doing the work on their own softwares, and documenting it quite nicely. There is absolutely no reason to burden them with twice the amount of work. It's the FTSC's job to document for Fidonet, not theirs.

Technically SBBS is open source but that doesnt mean others know the basics to find it.

No but any current FTSC members should know how to find it. If they don't, they probably shouldn't be FTSC members.

So, any better ideas? With no repository on 'how-to' we leave all developers hanging and we die. It doesnt MATTER if it is a proposal
or raised to a standard just now. It needs to be where they can find
it.

It is where they can find it. They're just not looking.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Carol,

On Thu Feb 11 2021 22:18:38, Carol Shenkenberger wrote to Stas Mishchenkov:

Lol! pass what you can to us. We can always take a proposal and work with you on it if formatting is a help. Many of us can help with technical wording if there is confusion.

So are you saying the FTSC is basically a glorified spell/grammar/formatting checker now? And that the developers not only need to document their software, but also should do the leg work for the FTSC so all you have to do is look over it and add your suggestions? GTFOH.

If the FTSC "documents current practice", then he should only have to document what he's doing, for his software.

If you, or any other FTSC member thinks it's "current practice", then YOU/FTSC document it for Fidonet. Make sense?

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Carol,

On Sat Feb 13 2021 17:16:34, Carol Shenkenberger wrote to Rob Swindell:

Here's my attempt at a modern FTN spec:
https://wiki.synchro.net/ref:fidonet_packets

Submit then!

It was, 2+ years ago. :|

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Servus Oli!

Antwort auf eine Message von Oli an Helmut Renner:

if they want to do the work - I'm absolutely ok with that ;)

the work?

If you don't recognize their wort, they do it well :)


Baba
DonHelmi/2

--- FleetStreet 1.27.3.8d
* Origin: DonHelmi's Datendienst (2:313/41)

Hello, Nicholas!

Sunday February 14 2021 09:17, from Nicholas Boel -> Carol Shenkenberger:

Here's my attempt at a modern FTN spec:
https://wiki.synchro.net/ref:fidonet_packets

Submit then!

It was, 2+ years ago. :|

That's right. There's no fakken way to modify the baseline FTS-0001 document in order to cleanup that historical shut and make it a bit friendly for a new FTN developer when it comes to data structures, e.g. 72 bytes for subject line whether it includes the terminal zero byte or not.

Best Regards, Nil
--- GoldED+/LNX 1.1.5
* Origin: -=NIL BBS=- (2:5015/46)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Nicholas Boel to Carol Shenkenberger on Sun Feb 14 2021 08:33 am

Hello Carol,

On Thu Feb 11 2021 22:03:16, Carol Shenkenberger wrote to Nicholas Boel:

Well Nick B, With no propsals, our 'work' has been helping people understand how to MAKE one.

The last couple of proposals that I remember coming through here, ended up going through a rigorous spelling and grammar checking, and once they could be almost completely reworded any more, they were forgotten and never brough up again.

Ozz had a lot of problems with no modern guides. Modern developers aren't passing new guides to those who can follow suit. We have 'pipeline development' now.

Some of these modern developers (Synchronet, Husky, for example) have documented their own software fully. One only has to go to the wiki to see i all. Why would they want to burden themselves documenting their own software and then writing up proposals and or documentation for the FTSC when they're not a member, and probably don't want to be one?

Modern tech tells us that is a dead end eventually.

I'm not sure what modern tech is telling you this, but "---SBBSecho 2.11-Win is 10-15 years old now. If you don't keep up with modern tech, I'm not sure you can use it as an excuse for anything.

Some of us are helping developers with how to get the 'word out' and then we see what works.

I'd really hope Stas will help at least with some tech to smartphones IOS if I got right. I'd like to see somthing from the Mystic
developer and to see SBBS actually submit suggested implementation proposals would be excellent.

My point is, why should they have to submit anything? They're doing the work their own softwares, and documenting it quite nicely. There is absolutely no reason to burden them with twice the amount of work. It's the FTSC's job to document for Fidonet, not theirs.

Technically SBBS is open source but that doesnt mean others know the basics to find it.

No but any current FTSC members should know how to find it. If they don't, t probably shouldn't be FTSC members.

So, any better ideas? With no repository on 'how-to' we leave all developers hanging and we die. It doesnt MATTER if it is a proposal
or raised to a standard just now. It needs to be where they can find it.

It is where they can find it. They're just not looking.

Regards,
Nick

... "Take my advice, I don't use it anyway."

Nick, we are talking OTHER developers may not know where to find it.

xxcarol
--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Tom De Puysseleyr to Andrew Leary on Sun Feb 14 2021 11:09 am

Andrew,

02 Feb 21 02:33, you wrote to All:

The following members' terms expire on 11 Mar 2021:
Nick Andre 1:229/426

I hereby nominate Nick Andre.

Tom

Thanks! Needed that.
xxcarol

--- SBBSecho 2.11-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Re: 2021 FTSC Standing Member Election - Term Expirations
By: Nicholas Boel to Carol Shenkenberger on Sun Feb 14 2021 09:17 am

Hello Carol,

On Sat Feb 13 2021 17:16:34, Carol Shenkenberger wrote to Rob Swindell:

Here's my attempt at a modern FTN spec:
https://wiki.synchro.net/ref:fidonet_packets

Submit then!

It was, 2+ years ago. :|

Well, to be fair, that's a different document (though same subject matter). I didn't have a hand in Stephen Hurd's FSP.
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Alexey Vissarionov!

** On Friday 05.02.21 - 07:40, Alexey Vissarionov wrote to August Abolins:

Good ${greeting_time}, August!

04 Feb 2021 20:56:00, you wrote to Carol Shenkenberger:

Name Node
Andrew Leary 1:320/219
mark lewis 1:3634/12
Richard Menedetter 2:310/31
Carol Shenkenberger 1:275/100
Ozz Nixon 1:275/362
Nick Andre 1:229/426

^^^^^^^
Please fix the quoting.

What's wrong with it? The original that I replied to already
had one level of >'s. My Quoting added one more level of >'s,
and your's added another column of >'s. This reply generates a
4th. Things seem to work OK. ;)


--
../|ug

--- OpenXP 5.0.48
* Origin: (2:221/1.58)

Good ${greeting_time}, August!

14 Feb 2021 19:23:00, you wrote to me:

Nick Andre 1:229/426

^^^^^^^
Please fix the quoting.

What's wrong with it? The original that I replied to already
had one level of >'s. My Quoting added one more level of >'s,
and your's added another column of >'s. This reply generates a
4th. Things seem to work OK. ;)

More '>' symbols are normally added to the end of quoting prefix, before the quoted text. So "AA> text" becomes "AA>> text", not "> AA> text" or whatever.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi
* Origin: ::1 (2:5020/545)

What is needed is more developers developing exciting new stuff which can

then

be documented. As it is other than checking punctuqtion, there's nothing to >do.

I agree. I was interested in developing and documenting. Not waiting to
know if everyone agreed on grammar/punctuation ~ I have implemented the
ability to do MOUSE interactive MATRIX and GAMES, I have implemented
the ability to detect UTF8 or assume development codepage (437 in my
case). But, certain people come along bitching at me for how I develop
my software on my system - I receeded back to other networks.

Ozz
--- Legacy/X FTN Tosser/JAM v1-Alpha6
* Origin: Legacy/X WHQ (Legacy ANSI at Today's Speed) (1:1/123)

I agree. I was interested in developing and documenting. Not waiting to know if everyone agreed on grammar/punctuation ~ I have implemented the ability to do MOUSE interactive MATRIX and GAMES, I have implemented
the ability to detect UTF8 or assume development codepage (437 in my case). But, certain people come along bitching at me for how I develop
my software on my system - I receeded back to other networks.

You guys keep going, I appreciate your efforts, Let them Bitch Ozz
keep going and Ignor the bitching! Your doing a Great Job Guys!
Thanks Sam


Bye for now...
Sam
1:123/120.0@fidonet
Ezycom BBS Support

--- Ezycom V3.00 01FB064B
* Origin: Deep Space Gateway BBS Running EZYCOM V3.0 (1:123/120)