Roadmap for FTC.

peeet

Hey AcidD, I’m not looking for a pump and dump. I’m just doing due diligence and I’m asking what I think are fair questions. I would also just like to see future plans. Obviously the more specific, the better but like I said I understand their resource constraints.

I’m intrigued by this project because it’s been around for a while and it seems to have the potential for real world use like bitcoin and litecoin, two coins which I strongly believe and and I’m long on.

I’d just like to know more and I apologise if I have offended.

AcidD

@peeet said in Roadmap for FTC.:

@AcidD

Hey AcidD, I’m not looking for a pump and dump. I’m just doing due diligence and I’m asking what I think are fair questions. I would also just like to see future plans. Obviously the more specific, the better but like I said I understand their resource constraints.

I’m intrigued by this project because it’s been around for a while and it seems to have the potential for real world use like bitcoin and litecoin, two coins which I strongly believe and and I’m long on.

I’d just like to know more and I apologise if I have offended.

No offence taken at all! :-)

I think the due diligence is a good thing and yes your questions are 100% fair.

There was a post with some kind of historical log and we could use that as a base and then build on it.

For example I think the next steps with FTC are (super high level)

1 - move everyone on to 0.9.6.1
2 - move everyone to 0.11.2 when it’s ready.
3 - MOON?

We just released 0.9.6.1 - we are hoping to get a high adoption rate similar to 0.9.6. Once that happens we are in a really good place to move to 0.11.2 and beyond!

thebaron

I have worked as an editor, so I’m happy to help with writing copy and/or be a copy editor. I’ll try to schedule some time in to work on writing up a road map. I’m thinking the best way to do it as a team would be to make a slack channel and then link to it and do reports back into these forums, much like the dev stream.

I imagine there are going to be certain understandings that the engineers have that will set the parameters for a roadmap developmentally, but on an open-source project I should think that team roadmapping may also a good way to drive and inspire innovation.

If anyone would like to contribute their ideas, or would like an invite to a slack channel, please don’t hesitate to reply here or send me a message.

mkxjinshan

@thebaron thanks for you willing to help writing up a roadmap.I think the roadmap is good for ftc development.

thebaron

@mkxjinshan I’ve just created a slack channel for discussing the roadmap, if you or anyone else would like to join then let me know and I’ll send you an invite link.

wrapper

@thebaron, slack is not open source. FTC have already tried using it and found it diverted attention from the forum and bullies and psychos took it over. Whilst anyone is free to use it.

I personally will never go on slack again.

Any discussions on slack about FTC should be within the FTC code of contact and reported back to the forum.

The forum chat facility was included to be used for private chats and the forum for public discusions and posts.

thebaron

@wrapper
That’s fair enough. I was wondering that if the parameters were relatively narrow and the expectations within that space were made clear then it might be a productive way to speak rapidly without muddying up the FTC forums, and is the way I use it for other groups. The FTC forum chat doesn’t seem as fit for the purpose to me, but each to their own.

I aim to act in good faith and abide by the code of conduct on any forum when discussing FTC as behooves any of this projects’s members.

I have also started a separate thread on the topic to gather ideas. This thread seems to be a good meta discussion about how a roadmap is best developed, rather than what the content of that roadmap is.

wrapper

The forum chat is better than slack for quick discussions, you should try it.

Whilst it is fine having an opinion and convincing the community it is correct, it is much more interesting finding what the community thinks. That involves training them up to understand the issues.

I have posted and documented about FMECA and such in depth business analysis. In order to make sensible decisions on where to go you need to analyses where you are first not how fast to drive there.

Git clone and view the web site : the theory behind Task creation - Maintenance Analysis Techniques.
https://github.com/wrapperband/Open-Condition-Monitoring

thebaron

Ah yes, my gripe was limited to the pop out messenger, rather than the separate chat room setup, which looks pretty good - I was concerned that the messenger was just 1 - 1 communication but it seems that it can be run like a room for groups.

Regarding opinions, I’m not super interested in pushing mine (yet), as I don’t really have any. I’m more interested in facilitating discussions and capturing the intention of the group. The difficulty I perceive is the difference (and reconciling the difference) between those who really understand the philosophy and the internal workings of the technology and those who understand it in a much more superficial way, eg. the engineer’s view vs the layman’s view.

Not that people with a superficial understanding don’t have enormous value to contribute. Often being on the outside gives one a fresh perspective. Nevertheless, these positions need to be mediated when working on a group project.

If we can capture those understandings and eventually come to some agreement as to the best way of putting them forward in a roadmap, then I think we’ll have a very significant document on our hands. I suspect it would be more valuable than a whitepaper to this group’s veterans, its newcomers, and indeed outsiders.

mkxjinshan

…

Bushstar

How about a road map without a specific time line, just the future developmental plan?

Probably the most important step is to work on a 0.13 client, this will include CSV/SegWit and BIP66 though that shows that it should be active in the 0.11 client though there will be no miner support for it so that needs to be considered. I was under contract with Hullcoin but as they’ve hit a funding hiatus and have breached contract I’m now free to roam the wilds of crypto again.

I will make an effort to start porting the 0.13.2 codebase to Feathercoin.

AcidD

@Bushstar said in Roadmap for FTC.:

How about a road map without a specific time line, just the future developmental plan?

Probably the most important step is to work on a 0.13 client, this will include CSV/SegWit and BIP66 though that shows that it should be active in the 0.11 client though there will be no miner support for it so that needs to be considered. I was under contract with Hullcoin but as they’ve hit a funding hiatus and have breached contract I’m now free to roam the wilds of crypto again.

I will make an effort to start porting the 0.13.2 codebase to Feathercoin.

Great to see you online again @Bushstar

+1 for this plan!

Wellenreiter

@Bushstar
Great to see you again here in the Forum

I’m pretty sure, that we don’t have SegWitt in 0.11.2, so that would be an enhancement in 0.13.
Not 100% sure, that BIP 66 is active in 0.9.6.x and 0.11.2 but I think so.

+1 :D

alowberg

This post is deleted!

mkxjinshan

@Bushstar glad to see you come back

AmDD

@Bushstar said in Roadmap for FTC.:

How about a road map without a specific time line, just the future developmental plan?

Probably the most important step is to work on a 0.13 client, this will include CSV/SegWit and BIP66 though that shows that it should be active in the 0.11 client though there will be no miner support for it so that needs to be considered. I was under contract with Hullcoin but as they’ve hit a funding hiatus and have breached contract I’m now free to roam the wilds of crypto again.

I will make an effort to start porting the 0.13.2 codebase to Feathercoin.

Welcome home!

Wellenreiter

9 posts moved to Segwit discussion

mkxjinshan

I can’t find the roadmap of ftc

Wellenreiter

@mkxjinshan

Due to the fact that Feathercoin is community driven and all coder work on free time and unpaid, there is a problem to publish a detailed road map.

At high level the plan for 2018 is:

import bitcoin code version 0.13.2 into feathercoin
implement Segwitt and BIP 66

Besides that there will be the ‘normal’ activities to maintain the current production release and bug fixing.

wrapper

Whilst every one like a roadmap and we have plenty of discusion on the way forward, it is an admin task. Whilst current vollenteers already spend a disproportional (free time) on administration tasks, this isn’t something you can make admins do.

It’s not even a very difficult task for someone to contribute who is artistic or has or wants to gain some business / management experience.

As that does not seem forthcoming, … FMECA

Mode of success :

Passing on future plans to forum members and users.
Enabling a D.A.O. to make a plan.

Modes of failure :

Unable to attract volunteers to perform administration tasks.
Journalists or “investors” expect FTC to be a bank
Bad vibe from members asking about lack of Admin documentation.

Causes of failure :

People won’t do some jobs for nothing
In open source the community needs to generally agree
Allowing easy “attacks” / “criticism” on forum by trolls or competitive coins.

Warning effects

New members asking for a roadmap
Moderators diverted from support
Developers diverted from development or research
Lack of fundemental knowledge of crypto by newbies

Remedial Tasks :

Perform a full mode of success / mode of failure analysis
Set up payment system to pay for admin jobs …

Feel free to complete the analysis

Contribute to the FTC Bounty fund :

https://forum.feathercoin.com/topic/9283/feathercoin-0-9-6-x-series-contributions-and-contributers-to-ftc

If anyone would like to write a proposal to do a Road Map and the cost to the Bounty?

Example draft proposal, completion markers / timeline…

Research one and two year future plan for FTC.
1 ---------
1.2 -------- etc …
Design a roadmap graphic
Get agreement on forum for roadmap
Create Github branch
4.1 Call for moderators ------
Donate roadmap and claim Bounty …

Reference : https://wrapperband.github.io/Open-Condition-Monitoring/MaintenanceTechniquesAnalysis/MaintenanceTechniquesAnalysis.html

knock up a proposed demonstration roadmap design / …