Welcome!

There are many creative and capable people in the dash community that can use this project to really make a difference, no matter where they fall on the technological spectrum. Seems like it will enable more of the community to be actively involved in bringing their ideas in.

I agree, and thanks for your support. I may take a while to get it user friendly enough for everyone to use, regardless of skillset, but that's the direction I'd like to see it go. And I also think it will help semi-technical people get into development and such with a much lower barrier to entry than say, contributing to the main dashpay repo (if contributing there is even possible). On top of that, it will incentivize technical folks who have dash-related code living on their personal repos to move it over to the dashcommunity organization

*it* may take a while, not "I"

I love this idea! Community building at its best. I would like to propose a collaboration of sorts. In order to market your idea, I would like to create a brochure to hand out at the For the Community Event in Houston coming up this November. Would you be interested in working with me to provide the appropriate information? I can do the design/graphics. We will be attending in the Dash Mobile.

Yes. I would be. Let's chat on Slack sometime about it (I'm rion there too)

I want to see more focus on decentralized infrastructure, have you seen the work that has been done on the steemit blockchain to provide web applications like GITHUB?
https://git.steem.network/
Have a look at this post:
https://steemit.com/steem/@someguy123/git-steem-decentralized-github-using-steem
Having an extra hosting bill, and maintenance against LAMP attacks and such should be something preventable by moving the backend to a decentralized platform, also more sustainable.

Thanks for those links JZA. I hadn't heard of that project, but I checked it out and it looks great. I see things like this being possible on the dash network as well (DashDrive when it comes to fruition).

i love this idea.. you've already done work. im voting yes for this.

Thank you for your support and excitement. I think this has huge potential.

Btw, from the start i would like to clarify, who would own this? I'm assuming if we fund it, the dash owns this and wont end up like the slack project?

The community would own this. I have no intention of monetizing or controlling this for personal gain. Every open project needs good security, curation, and moderation practices, so it's likely that some people will have admin rights to the organization, while most people will have contribution rights only. Those are details I'd like to work out through open discussions. Any thoughts?

By, "the dash" do you mean the Dash Foundation? Because there is no other legal entity that I am aware of. Just because people give themselves titles like 'VP Business Development' or 'CEO' or 'CTO' doesn't magically create a company or mean there actually is a company behind those titles. (What does that tell you?)

Besides, what exactly do you think happened to "the slack project"? Did you know that to date - it is by far the project with the most detailed monthly reporting and that every bit of funding went back to the community? It even paid partially for Amanda's 'Dash School' video series. (Balance was crowd sourced from personal funds from people running that Slack.) I use that as an example, because following your logic, the Slack group owns those videos, which is not true. The same applies for this proposal.

...and the Network paid for Dash Slack, which is now apparently Solarminer's own personal property (or at least, he believes it is). Get the Network to pay for something you want to develop, then take personal ownership of it and tell the Network to jump off a cliff. Not a bad gig if you can get it. (Sorry to OP, this has no direct relevance to your proposal per se.)

Did you know the slack was offered to core? Did you know that they did not even want it? No need to make up stories.

Best of luck on this proposal Rion.

It has some relevance. I, for one appreciated the efforts of the slack team. There seemed to be some loose cannons in the ranks, but it's a passionate group of people who I think have good intentions. I'd like to have a place where community can collaborate and communicate. Slack is one of those places, and this might be another. Two different functions.

The Slack ran for many months before the proposal. Further, the proposal didn't pay for the Slack account. (How could it? It is the free version.) The details of where the funds went were fully reported. For example, some of it went to a Slack logo contest. Hypocritically, (albeit perfectly fine) that logo is now being used by the other Slack. Please get your facts straight. Also, I'm pretty certain Solarminer doesn't own Slack. (Or Google, or Yahoo etc.)

This is a fantastic proposal.

Thanks noobkid (who I isn't much of a noob). It better be, after all it is a proposal partly about creating better proposals :)

Sorry for all the questions...last one...I'd like to know why the MN's voted no on this one? Not a valid need? Platform too hard to use? Some other reason?

I considered voting NO, because of dispersal of incentives on a first come first served basis. Thing is if you go through any proposal MN's are bound to find worrying aspects. I'm going to Vote YES because of the vision the owner has. I feel he doesn't fully know how it will develop, I like the fact that it will be down to the community. Also Non-coders like myself can be more involved and communicate our needs and wants to coders as software is being developed. So its going to be a YES from me.

Why did you choose Github and not some other content platform?

Github offers the best revision control system and team collaboration (built-in issue tracking, Trello-like project management, etc). This is primarily useful for coding projects, but offers transparency for such projects to everyone involved (including casual observers, PMs, MNOs, etc). Beyond software development, it offers free website hosting with built-in Jekyll support. This way every project (coding project, blog repo, guides repo, etc) can have its own landing site with a three(ish)-click launch that anyone can master. I've emphasized proposals, the blog, and guides initially (in the proposal and initial work) because they are areas anyone can participate in. There is yet to be an actual coding project hosted here, but I have that as a near-term future target. I've only scratched the surface of my vision for this project.

I love how specific the details are. This is a great example of how to make a proposal clear and organized. The blog you wrote is genius. https://github.com/dashcommunity/blog/blob/master/shift_to_decentralization.md

"Dash is centralized. Contrary to popular belief, every cryptocurrency starts out centralized. ...."
> I am not sure if I can support it

As soon as a project becomes public open source it is not centralized by definition anymore

I see centralization and decentralization as a spectrum. If you put time on another axis you can try to chart an "ideal" path for any given project. Like I said in my (rough) blog post, I see all original ideas starting out centralized, but for them to be successful they must decentralize over time, with prudence. Anyone who has followed the slack discussions has seen a struggle between core and community. We should openly acknowledge that, and then work together to solve it. I'm assuming good intentions on both sides, and I'm seeing merit to both positions, as well as the nuanced ones in between as well.

I disagree in the details. As soon as a project becomes public open source, the *source* is no longer centralized. The control over the most popular community around the project may still be centralized, and as this blog argues, should necessarily be centralized in order to get over initial barriers. But the whole point is that projects like these *become* decentralized through process and milestones such as those being presented in this proposal.

check out what happened after the first ETH hardfork - ETH was very centralized before. If the resources are available to anybody without restriction there is no real centralization

I just disagree with the term "Dash is centralized" - currently the driving factor may be centralized. But as soon as someone decide to try it a different way he is free to do so

Ah, I see. I thought you meant you could not support this proposal. I misunderstood you, sorry. Dash technology is not centralized. The current Dash community is centralized, however, and this is what I thought was meant from his blog post. We can always start over, but it would be excellent if the current community and real estate could transition to decentralized in order to preserve its value and sustainability. No community in the history of the world has been able to achieve this transition. Let's be the first.

How many people will have commit access to the git repo?

Github Organizations offer fine-tuned permission controls. Anyone will be able to have commit access to repositories and projects they wish to create. I haven't quite worked out the details of who will get admin rights to what parts of the organization; that's an open discussion.

Well done. If this gets voted down - that just proves there are people trying to game the system. That will hurt the Dash price.

That's what you say to every proposal that you support

Well submitted proposal.

I love the blog post as well. Well done.

Thanks for the proposal support and blog feedback. Much appreciated.

Thank you for taking the time to review my proposal. I'm happy to answer any questions you may have.

If I want to write a post, how do I get that post into the system?

https://github.com/dashcommunity/guides/blob/master/create_blog_post.md

What is the difference between writing on the forum and writing a post on the blog in the github?

If the proposal passes, you will *get paid* to post on the Dash Community blog. The blog can eventually be hosted on a separate domain (but through the same GitHub platform) using GitHub Pages. It could potentially even be monetized (ads, etc) just like any other blog site, which could be used to further incentivize content creators. We just take the project where we want it to go.