From Fedora Project Wiki
< Websites
(Created page with "= Introduction = Fedora Developer Portal would be a new place for developers providing information about tools, technology and other features that packaged in Fedora and rais...") |
|||
| Line 23: | Line 23: | ||
== Examples == | == Examples == | ||
=== Ruby === | === 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 === | === 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 === | === "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 = | = 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. | 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. | ||
Revision as of 09:51, 29 May 2015
Introduction
Fedora Developer Portal would be a new place for developers providing information about tools, technology and other features that packaged in Fedora and raise awareness about new and existing projects.
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.