Roadmap for FTC.

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 / …

Mr_Metaphysical

@wellenreiter @AcidD Has there been any luck finding an iOS developer to modify Loaf Wallet or any wallet to get it submitted to App store?

Everyone i inquire to, starts then says no or just ignores me. I am still willing to support this development.

Mr_Metaphysical

@wellenreiter Do these two points need to be implemented before creating a ios wallet - fork of loaf wallet for example ?

wrapper

@tmetaphysical re : roadmap to associated developments.

The FTC team has core responsibility to the blockchain. Staff have researched, encouraged, planned and assisted potential developers (of any FTC associated technology) . In the case of Android wallet, “we” / Admin / @Wellenreiter has taken over long term management of the wallet, from the developer, in our own time for free.

With the current situation with coins and FTC market cap, there is certainly more of an incentive to get a ios, bread wallet out. We would certainly assist or answer what we can, start a chat group to pass info around. Use our facilities -the forum or slack can be used to document projects, you can request the wallet be under FTC change control and have it hosted at Github, even be a moderator for that projects.

Sorry the answer to every questions is go ahead and do it.

Wellenreiter

@tmetaphysical said in Roadmap for FTC.:

@wellenreiter Do these two points need to be implemented before creating a ios wallet - fork of loaf wallet for example ?

It is a problem to find an IOS developer. We also never had one in our team, therefore we don’t have an IOS wallet.

If any existing IOS Wallet from another coin can be forked, this can be done at any time.
The major task to accomplish is to get the FTC specific hashing algorithms implemented, including the block numbers to switch from one algo to another, and to implement the difficulty calculations also with the corresponding block numbers that apply the new parameter to this calculation.

The rollout of 0.13.2 does not contain a hard fork, so out current production releases will continue to work and if an IOS Wallet is created now, it also will continue to work.

Mr_Metaphysical

@wellenreiter Is there a site where reputable iOS developers monitor for extra work?

AcidD

@Mr_Metaphysical

I have successfully forked BreadWallet and implemented the necessary stuff to get us to the neoScrypt HardFork.

I just don’t have the C knowledge necessary to carry on. The encryption algo stuff is complex for me.

right now I have a version of BreadWallet that compiles and runs successfully, gets to the NeoScrypt hardfork block…and then restarts it’s sync.

I’m trying to get devs I know to look into the reset of the implementation of it…it’s hard and considering the amount of of work, they want me to pay them…which i’m looking into if I can afford it.