Roadmap for FTC.
-
Good post! Agreed!
-
agree too
-
I just been reading about the various open source tools for “Road Mapping” and found this may be informative to anyone who doesn’t know what that means …
[Ref:] https://mozillascience.github.io/working-open-workshop/roadmapping/
Roadmap
When you’re starting on an open source project, it’s important to record what your community (this might just be you at the beginning) decides to work on! A roadmap organizes the tasks that nees to be done on a project around milestones. This helps potential contributors understand the current status of your poject and where it’s going next.A roadmap can also express your vision for the project. Make sure you clearly state why you are implementing certain things to get people excited about joining.
This can be as simple as a collection of issues in your issue tracker, or a detailed timeline complete with milestones. It’s up to you to choose what works best for your community! At the Mozilla Science Lab, we break our Roadmaps into three sections:
Roadmap StructureIf your roadmap is more than a list of issues, we recommend three sections to welcome new contributors.
-
Project Mission & Summary (optional) - Welcome and orient visitors to your project. Users may have been linked directly to the Roadmap, it’s important to help them understand where they are.
-
How to Get Involved (optional) - New contributors might want to jump in right away! This points them to parts of the project they can immediately work on.
-
Timeline - The star of the roadmap!
This section organizes tasks needed to complete your project around milestones, mapping out what you’re working on now and where it’s going next. This can be as simple as a list of issues in your issue tracker.
-
-
I agree as well. Great idea and a good opportunity to help the world know how serious the Feathercoin community really is.
-
is anyone offering to help with the road map ? looking for Graphics people and copy writers.
-
I agree this should be probably the highest priority.
It provides the reasons to why people should invest their time or money into the project. Could the team just do a simple word document showing the roadmap and time lines first? After that, we could then think of making it look good and sounding better.
For me I want to know what the vision is. Will this be a coin that people could use in their day to day lives? How will this work together with bitcoin and litecoin? Atm and merchant rollouts. Rootstock, Segwit, Lightning network compatibility. What do the founders believe about the whole crypto space and where will feathercoin sit? Will you do any marketing activities? (I know someone in London in the Digital Marketing space if you need)
Again, basically, why should someone invest their time and money?
Happy to discuss with the team.
-
Sorry when I said highest priority, I don’t mean drop all the developing to do this. Thought I would just clarify.
I mean it’s just not clear what the business model is and where the project is heading apart from fixing bugs.
-
@peeet said in Roadmap for FTC.:
I agree this should be probably the highest priority.
It provides the reasons to why people should invest their time or money into the project. Could the team just do a simple word document showing the roadmap and time lines first?Sorry, but I have a bad feeling about defining time lines.
The whole development is done on voluntary basis and none of the team members is payed for their work. They simply donate some (or most) of their free time to Feathercoin.Based on that it is clear, that we don’t have resources guaranteed and therefore can’t define time lines, as it is done by company driven projects, where resources are payed and allocated to a project for a defined amount of hours per day/week/month.
I agree with a plan where we want to go, but I think it is very unprofessional to define time lines and later postpone milestones and deadlines, because the resources are not available.
-
I can’t wait to know what will happen to ftc in the future.
-
I understand the business model means no direct salary for developers as there is no revenue. I guess the team will just need to decide whether a sacrifice of time and effort will lead to the increase in the value of your personal coin holdings.
I do understand that this would mean a huge risk for anyone who decides to pursue the project full time without ‘pay.’ I also understand you guys are doing the best you can with extremely limited resources. So whatever resources you need, I can do my best to help or help you advertise.
-
@peeet said in Roadmap for FTC.:
I understand the business model means no direct salary for developers as there is no revenue. I guess the team will just need to decide whether a sacrifice of time and effort will lead to the increase in the value of your personal coin holdings.
You make it sound like the FTC team are a bunch of whales…which is NOT the case…as far as I know, none of the developers are major holders. All the major holders are private traders/speculators/investors.
I do understand that this would mean a huge risk for anyone who decides to pursue the project full time without ‘pay.’ I also understand you guys are doing the best you can with extremely limited resources. So whatever resources you need, I can do my best to help or help you advertise.
I agree with @Wellenreiter - defining a time line on an open source project is hard and with a cryptocurrency isn’t necessarily wise. I agree that there should be some kind of Historical log of what has happened so far and what the future plans could look like. But that’s all I’d personally want to see.
In the past I’ve seen bullshit roadmaps for shitcoins and they were only used to pump the coin. I am very ANTI pump and dump.
if you’re looking for a roadmap or info just so you can pump the coin…please go choose another coin :-)
-
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.
-
@peeet said in Roadmap for FTC.:
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!
-
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.
-
@thebaron thanks for you willing to help writing up a roadmap.I think the roadmap is good for ftc development.
-
@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.
-
@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.
-
@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.
-
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 -
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.
