< Websites
No edit summary |
|||
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
Fedora Developer Portal would be a new place for developers providing information about tools, technology and other features that packaged in Fedora | Fedora Developer Portal would be a new place for developers, providing information about tools, technology and other features that are packaged in Fedora. It would raise awareness about new and existing projects among users. | ||
= Why is this project needed? = | |||
I may be a student choosing the best Linux distribution or even the best platform for my development. I also might be a current user of Fedora looking for new developer features I don't know about. I'm not looking for documentation about some particular tool or technology. There are plenty of those resources on the internet already. Let's say that I'm more discovering the possibilities that are out there. Are there any great developer tools? What technology should I use? How can I distribute my program or deploy the service I create? | |||
The Fedora Developer Portal would give me those insights and point me to the particular project/tool/technology I might be looking for. It would provide a description, links to other resources, information about how it's packaged in Fedora, guides, videos, blog posts, ... there are plenty of possibilities what we can include. | |||
= Content = | = Content = | ||
== Structure == | == Structure == | ||
Revision as of 10:10, 4 June 2015
Introduction
Fedora Developer Portal would be a new place for developers, providing information about tools, technology and other features that are packaged in Fedora. It would raise awareness about new and existing projects among users.
Why is this project needed?
I may be a student choosing the best Linux distribution or even the best platform for my development. I also might be a current user of Fedora looking for new developer features I don't know about. I'm not looking for documentation about some particular tool or technology. There are plenty of those resources on the internet already. Let's say that I'm more discovering the possibilities that are out there. Are there any great developer tools? What technology should I use? How can I distribute my program or deploy the service I create?
The Fedora Developer Portal would give me those insights and point me to the particular project/tool/technology I might be looking for. It would provide a description, links to other resources, information about how it's packaged in Fedora, guides, videos, blog posts, ... there are plenty of possibilities what we can include.
Content
Structure
The main categories could be something like these:
- Development tools:
- Vagrant, Developer Assistant, ...
- Which tools to use for development and how they can help me
- explain WHAT the project is and HOW to get it running
- Languages, technologies, runtimnes:
- Python, Ruby, Rails, Perl, ...
- Info about packages, the "I am a _ developer" view
- explain WHAT the project is and HOW to get it running
- Distribution/deployment:
- Copr, Docker, Openshift, ...
- How to get my project to people?
- explain WHAT the project is and HOW to get it running
- Docker images, Vagrant boxes, ...
- Blogs
Examples
Ruby
- Installation (both RPM and upstream)
- Explain them why we have ruby-mri bin and why we use rubypick
- Answers to how our Ruby differs from upstream
- Let users know we have a lot or RubyGems packaged
- Show them our https://github.com/zuhao/isitfedoraruby
- Let them know there is something like Fedora Ruby SIG that they can join
Vagrant
- how to get packaged Vagrant
- providers
- libvirt
- how to run libvirt with vagrant without sudo
- list of plugins we maintain
- troubleshooting, how to report problems
- Fedora Vagrant boxes (links)
"I am a Ruby developer" view
- combination/listing of pages we have and are relevant
- Ruby, Rails, Vagrant, docker, DevAssistant would show up
Possible Implementation
We would like to store the content on GitHub and use all it's features like forks, pull requests and easy collaboration. The individual pages could be written in markdown. The website would be consisting of static pages generated from the git repository.